# Language mr-IN translations for PACKAGE package.
# Automatically generated, 2008.
#
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-05-03 11:34+0000\n"
"PO-Revision-Date: 2008-04-04 01:24+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#: Configuration.xml:5
#, no-c-format
msgid "Configuring Seam and packaging Seam applications"
msgstr ""

#. Tag: para
#: Configuration.xml:6
#, no-c-format
msgid ""
"Configuration is a very boring topic and an extremely tedious pastime. "
"Unfortunately, several lines of XML are required to integrate Seam into your "
"JSF implementation and servlet container. There's no need to be too put off "
"by the following sections; you'll never need to type any of this stuff "
"yourself, since you can just copy and paste from the example applications!"
msgstr ""

#. Tag: title
#: Configuration.xml:12
#, no-c-format
msgid "Basic Seam configuration"
msgstr ""

#. Tag: para
#: Configuration.xml:14
#, no-c-format
msgid ""
"First, let's look at the basic configuration that is needed whenever we use "
"Seam with JSF."
msgstr ""

#. Tag: title
#: Configuration.xml:17
#, no-c-format
msgid "Integrating Seam with JSF and your servlet container"
msgstr ""

#. Tag: para
#: Configuration.xml:19
#, no-c-format
msgid "Of course, you need a faces servlet!"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:21
#, no-c-format
msgid ""
"<![CDATA[<servlet>\n"
"    <servlet-name>Faces Servlet</servlet-name>\n"
"    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
"    <load-on-startup>1</load-on-startup>\n"
"</servlet>\n"
"\n"
"<servlet-mapping>\n"
"    <servlet-name>Faces Servlet</servlet-name>\n"
"    <url-pattern>*.seam</url-pattern>\n"
"</servlet-mapping>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:23
#, no-c-format
msgid "(You can adjust the URL pattern to suit your taste.)"
msgstr ""

#. Tag: para
#: Configuration.xml:25
#, no-c-format
msgid ""
"In addition, Seam requires the following entry in your <literal>web.xml</"
"literal> file:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:27
#, no-c-format
msgid ""
"<![CDATA[<listener>\n"
"    <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
"</listener>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:29
#, no-c-format
msgid ""
"This listener is responsible for bootstrapping Seam, and for destroying "
"session and application contexts."
msgstr ""

#. Tag: para
#: Configuration.xml:32
#, no-c-format
msgid ""
"Some JSF implementations have a broken implementation of server-side state "
"saving that interferes with Seam's conversation propagation. If you have "
"problems with conversation propagation during form submissions, try "
"switching to client-side state saving. You'll need this in <literal>web.xml</"
"literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:36
#, no-c-format
msgid ""
"<![CDATA[<context-param>\n"
"    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>\n"
"    <param-value>client</param-value>\n"
"</context-param>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:41
#, no-c-format
msgid "Using facelets"
msgstr ""

#. Tag: para
#: Configuration.xml:43
#, no-c-format
msgid ""
"If you want follow our advice and use facelets instead of JSP, add the "
"following lines to <literal>faces-config.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:46
#, no-c-format
msgid ""
"<![CDATA[<application>\n"
"    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>\n"
"</application>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:48
#, no-c-format
msgid "And the following lines to <literal>web.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:50
#, no-c-format
msgid ""
"<![CDATA[<context-param>\n"
"    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
"    <param-value>.xhtml</param-value>\n"
"</context-param>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:55
#, no-c-format
msgid "Seam Resource Servlet"
msgstr ""

#. Tag: para
#: Configuration.xml:57
#, no-c-format
msgid ""
"The Seam Resource Servlet provides resources used by Seam Remoting, captchas "
"(see the security chapter) and some JSF UI controls. Configuring the Seam "
"Resource Servlet requires the following entry in <literal>web.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:61
#, no-c-format
msgid ""
"<![CDATA[<servlet>\n"
"  <servlet-name>Seam Resource Servlet</servlet-name>\n"
"  <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>\n"
"</servlet>\n"
"    \n"
"<servlet-mapping>\n"
"  <servlet-name>Seam Resource Servlet</servlet-name>\n"
"  <url-pattern>/seam/resource/*</url-pattern>\n"
"</servlet-mapping>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:65
#, no-c-format
msgid "Seam servlet filters"
msgstr ""

#. Tag: para
#: Configuration.xml:67
#, no-c-format
msgid ""
"Seam doesn't need any servlet filters for basic operation. However, there "
"are several features which depend upon the use of filters. To make things "
"easier, Seam lets you add and configure servlet filters just like you would "
"configure other built-in Seam components. To take advantage of this feature, "
"we must first install a master filter in <literal>web.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:72
#, no-c-format
msgid ""
"<![CDATA[<filter>\n"
"    <filter-name>Seam Filter</filter-name>\n"
"    <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>\n"
"</filter>\n"
"\n"
"<filter-mapping>\n"
"    <filter-name>Seam Filter</filter-name>\n"
"    <url-pattern>/*</url-pattern>\n"
"</filter-mapping>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:74
#, no-c-format
msgid ""
"The Seam master filter <emphasis>must</emphasis> be the first filter "
"specified in <literal>web.xml</literal>. This ensures it is run first."
msgstr ""

#. Tag: para
#: Configuration.xml:77
#, no-c-format
msgid ""
"The Seam filters share a number of common attributes, you can set these in "
"<literal>components.xml</literal> in addition to any parameters discussed "
"below:"
msgstr ""

#. Tag: para
#: Configuration.xml:85
#, no-c-format
msgid ""
"<literal>url-pattern</literal> &#8212; Used to specify which requests are "
"filtered, the default is all requests. <literal>url-pattern</literal> is a "
"Tomcat style pattern which allows a wildcard suffix."
msgstr ""

#. Tag: para
#: Configuration.xml:92
#, no-c-format
msgid ""
"<literal>regex-url-pattern</literal> &#8212; Used to specify which requests "
"are filtered, the default is all requests. <literal>regex-url-pattern</"
"literal> is a true regular expression match for request path. It's worth "
"noting when composing the regular expression that the request path does not "
"contain the server or request context path."
msgstr ""

#. Tag: para
#: Configuration.xml:100
#, no-c-format
msgid "<literal>disabled</literal> &#8212; Used to disable a built in filter."
msgstr ""

#. Tag: para
#: Configuration.xml:106
#, no-c-format
msgid "Adding the master filter enables the following built-in filters."
msgstr ""

#. Tag: title
#: Configuration.xml:109
#, no-c-format
msgid "Exception handling"
msgstr ""

#. Tag: para
#: Configuration.xml:110
#, no-c-format
msgid ""
"This filter provides the exception mapping functionality in <literal>pages."
"xml</literal> (almost all applications will need this). It also takes care "
"of rolling back uncommitted transactions when uncaught exceptions occur. "
"(According to the Java EE specification, the web container should do this "
"automatically, but we've found that this behavior cannot be relied upon in "
"all application servers. And it is certainly not required of plain servlet "
"engines like Tomcat.)"
msgstr ""

#. Tag: para
#: Configuration.xml:116
#, no-c-format
msgid ""
"By default, the exception handling filter will process all requests, however "
"this behavior may be adjusted by adding a <literal>&lt;web:exception-"
"filter&gt;</literal> entry to <literal>components.xml</literal>, as shown in "
"this example:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:120
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
"            xmlns:web=\"http://jboss.com/products/seam/web\">\n"
"\n"
"    <web:exception-filter url-pattern=\"*.seam\"/>\n"
"\n"
"</components>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:126
#, no-c-format
msgid "Conversation propagation with redirects"
msgstr ""

#. Tag: para
#: Configuration.xml:127
#, no-c-format
msgid ""
"This filter allows Seam to propagate the conversation context across browser "
"redirects. It intercepts any browser redirects and adds a request parameter "
"that specifies the Seam conversation identifier."
msgstr ""

#. Tag: para
#: Configuration.xml:131
#, no-c-format
msgid ""
"The redirect filter will process all requests by default, but this behavior "
"can also be adjusted in <literal>components.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:134
#, no-c-format
msgid "<![CDATA[<web:redirect-filter url-pattern=\"*.seam\"/>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:138
#, no-c-format
msgid "Multipart form submissions"
msgstr ""

#. Tag: para
#: Configuration.xml:139
#, no-c-format
msgid ""
"This feature is necessary when using the Seam file upload JSF control. It "
"detects multipart form requests and processes them according to the "
"multipart/form-data specification (RFC-2388). To override the default "
"settings, add the following entry to <literal>components.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:143
#, no-c-format
msgid ""
"<![CDATA[<web:multipart-filter create-temp-files=\"true\" \n"
"                      max-request-size=\"1000000\" \n"
"                      url-pattern=\"*.seam\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:147
#, no-c-format
msgid ""
"<literal>create-temp-files</literal> &#8212; If set to <literal>true</"
"literal>, uploaded files are written to a temporary file (instead of held in "
"memory). This may be an important consideration if large file uploads are "
"expected. The default setting is <literal>false</literal>."
msgstr ""

#. Tag: para
#: Configuration.xml:154
#, no-c-format
msgid ""
"<literal>max-request-size</literal> &#8212; If the size of a file upload "
"request (determined by reading the <literal>Content-Length</literal> header "
"in the request) exceeds this value, the request will be aborted. The default "
"setting is 0 (no size limit)."
msgstr ""

#. Tag: title
#: Configuration.xml:163
#, no-c-format
msgid "Character encoding"
msgstr ""

#. Tag: para
#: Configuration.xml:164
#, no-c-format
msgid "Sets the character encoding of submitted form data."
msgstr ""

#. Tag: para
#: Configuration.xml:166 Configuration.xml:261
#, no-c-format
msgid ""
"This filter is not installed by default and requires an entry in "
"<literal>components.xml</literal> to enable it:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:169
#, no-c-format
msgid ""
"<![CDATA[<web:character-encoding-filter encoding=\"UTF-16\" \n"
"                               override-client=\"true\" \n"
"                               url-pattern=\"*.seam\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:173
#, no-c-format
msgid "<literal>encoding</literal> &#8212; The encoding to use."
msgstr ""

#. Tag: para
#: Configuration.xml:177
#, no-c-format
msgid ""
"<literal>override-client</literal> &#8212; If this is set to <literal>true</"
"literal>, the request encoding will be set to whatever is specified by "
"<literal>encoding</literal> no matter whether the request already specifies "
"an encoding or not. If set to <literal>false</literal>, the request encoding "
"will only be set if the request doesn't already specify an encoding. The "
"default setting is <literal>false</literal>."
msgstr ""

#. Tag: title
#: Configuration.xml:188
#, no-c-format
msgid "RichFaces"
msgstr ""

#. Tag: para
#: Configuration.xml:190
#, no-c-format
msgid ""
"If RichFaces is used in your project, Seam will install the RichFaces Ajax "
"filter for you, making sure to install it before all other built-in filters. "
"You don't need to install the RichFaces Ajax filter in <literal>web.xml</"
"literal> yourself."
msgstr ""

#. Tag: para
#: Configuration.xml:198
#, no-c-format
msgid ""
"The RichFaces Ajax filter is only installed if the RichFaces jars are "
"present in your project."
msgstr ""

#. Tag: para
#: Configuration.xml:203
#, no-c-format
msgid ""
"To override the default settings, add the following entry to "
"<literal>components.xml</literal>. The options are the same as those "
"specified in the RichFaces Developer Guide:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:206
#, no-c-format
msgid ""
"<![CDATA[<web:ajax4jsf-filter force-parser=\"true\" \n"
"                     enable-cache=\"true\" \n"
"                     log4j-init-file=\"custom-log4j.xml\"\n"
"                     url-pattern=\"*.seam\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:209
#, no-c-format
msgid ""
"<literal>force-parser</literal> &#8212; forces all JSF pages to be validated "
"by Richfaces's XML syntax checker. If <literal>false</literal>, only AJAX "
"responses are validated and converted to well-formed XML. Setting "
"<literal>force-parser</literal> to <literal>false</literal> improves "
"performance, but can provide visual artifacts on AJAX updates."
msgstr ""

#. Tag: para
#: Configuration.xml:217
#, no-c-format
msgid ""
"<literal>enable-cache</literal> &#8212; enables caching of framework-"
"generated resources (e.g. javascript, CSS, images, etc). When developing "
"custom javascript or CSS, setting to true prevents the browser from caching "
"the resource."
msgstr ""

#. Tag: para
#: Configuration.xml:223
#, no-c-format
msgid ""
"<literal>log4j-init-file</literal> &#8212; is used to setup per-application "
"logging. A path, relative to web application context, to the log4j.xml "
"configuration file should be provided."
msgstr ""

#. Tag: title
#: Configuration.xml:233
#, no-c-format
msgid "Identity Logging"
msgstr ""

#. Tag: para
#: Configuration.xml:235
#, no-c-format
msgid ""
"This filter adds the authenticated user name to the log4j mapped diagnostic "
"context so that it can be included in formatted log output if desired, by "
"adding %X{username} to the pattern."
msgstr ""

#. Tag: para
#: Configuration.xml:241
#, no-c-format
msgid ""
"By default, the logging filter will process all requests, however this "
"behavior may be adjusted by adding a <literal>&lt;web:logging-filter&gt;</"
"literal> entry to <literal>components.xml</literal>, as shown in this "
"example:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:245
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
"            xmlns:web=\"http://jboss.com/products/seam/web\">\n"
"    <web:logging-filter url-pattern=\"*.seam\"/>\n"
"</components>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:250
#, no-c-format
msgid "Context management for custom servlets"
msgstr ""

#. Tag: para
#: Configuration.xml:251
#, no-c-format
msgid ""
"Requests sent direct to some servlet other than the JSF servlet are not "
"processed through the JSF lifecycle, so Seam provides a servlet filter that "
"can be applied to any other servlet that needs access to Seam components."
msgstr ""

#. Tag: para
#: Configuration.xml:255
#, no-c-format
msgid ""
"This filter allows custom servlets to interact with the Seam contexts. It "
"sets up the Seam contexts at the beginning of each request, and tears them "
"down at the end of the request. You should make sure that this filter is "
"<emphasis>never</emphasis> applied to the JSF <literal>FacesServlet</"
"literal>. Seam uses the phase listener for context management in a JSF "
"request."
msgstr ""

#. Tag: programlisting
#: Configuration.xml:264
#, no-c-format
msgid "<![CDATA[<web:context-filter url-pattern=\"/media/*\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:266
#, no-c-format
msgid ""
"The context filter expects to find the conversation id of any conversation "
"context in a request parameter named <literal>conversationId</literal>. You "
"are responsible for ensuring that it gets sent in the request."
msgstr ""

#. Tag: para
#: Configuration.xml:270
#, no-c-format
msgid ""
"You are also responsible for ensuring propagation of any new conversation id "
"back to the client. Seam exposes the conversation id as a property of the "
"built in component <literal>conversation</literal>."
msgstr ""

#. Tag: title
#: Configuration.xml:277
#, no-c-format
msgid "Adding custom filters"
msgstr ""

#. Tag: para
#: Configuration.xml:278
#, no-c-format
msgid ""
"Seam can install your filters for you, allowing you to specify "
"<emphasis>where</emphasis> in the chain your filter is placed (the servlet "
"specification doesn't provide a well defined order if you specify your "
"filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</"
"literal> annotation to your Seam component (which must implement "
"<literal>javax.servlet.Filter</literal>):"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:283
#, no-c-format
msgid ""
"<![CDATA[@Startup\n"
"@Scope(APPLICATION)\n"
"@Name(\"org.jboss.seam.web.multipartFilter\")\n"
"@BypassInterceptors\n"
"@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")\n"
"public class MultipartFilter extends AbstractFilter {]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:285
#, no-c-format
msgid ""
"Adding the <literal>@Startup</literal> annotation means thar the component "
"is available during Seam startup; bijection isn't available here "
"(<literal>@BypassInterceptors</literal>); and the filter should be further "
"down the chain than the RichFaces filter (<literal>@Filter(within=\"org."
"jboss.seam.web.ajax4jsfFilter\")</literal>)."
msgstr ""

#. Tag: title
#: Configuration.xml:294
#, no-c-format
msgid "Integrating Seam with your EJB container"
msgstr ""

#. Tag: para
#: Configuration.xml:296
#, no-c-format
msgid ""
"We need to apply the <literal>SeamInterceptor</literal> to our Seam "
"components. The simplest way to do this across an entire application is to "
"add the following interceptor configuration in <literal>ejb-jar.xml</"
"literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:300
#, no-c-format
msgid ""
"<![CDATA[<interceptors>\n"
"    <interceptor>\n"
"        <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
"class>\n"
"    </interceptor>\n"
"</interceptors>\n"
"   \n"
"<assembly-descriptor>\n"
"    <interceptor-binding>\n"
"        <ejb-name>*</ejb-name>\n"
"        <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
"class>\n"
"    </interceptor-binding>\n"
"</assembly-descriptor>\n"
"]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:302
#, no-c-format
msgid ""
"Seam needs to know where to go to find session beans in JNDI. One way to do "
"this is specify the <literal>@JndiName</literal> annotation on every session "
"bean Seam component. However, this is quite tedious. A better approach is to "
"specify a pattern that Seam can use to calculate the JNDI name from the EJB "
"name. Unfortunately, there is no standard mapping to global JNDI defined in "
"the EJB3 specification, so this mapping is vendor-specific. We usually "
"specify this option in <literal>components.xml</literal>."
msgstr ""

#. Tag: para
#: Configuration.xml:308
#, no-c-format
msgid "For JBoss AS, the following pattern is correct:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:310
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"myEarName/#{ejbName}/local\" />]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:312
#, no-c-format
msgid ""
"Where <literal>myEarName</literal> is the name of the EAR in which the bean "
"is deployed."
msgstr ""

#. Tag: para
#: Configuration.xml:314
#, no-c-format
msgid ""
"Outside the context of an EAR (when using the JBoss Embeddable EJB3 "
"container), the following pattern is the one to use:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:317
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:319
#, no-c-format
msgid ""
"You'll have to experiment to find the right setting for other application "
"servers. Note that some servers (such as GlassFish) require you to specify "
"JNDI names for all EJB components explicitly (and tediously). In this case, "
"you can pick your own pattern ;-)"
msgstr ""

#. Tag: para
#: Configuration.xml:323
#, no-c-format
msgid ""
"In an EJB3 environment, we recommend the use of a special built-in component "
"for transaction management, that is fully aware of container transactions, "
"and can correctly process transaction success events registered with the "
"<literal>Events</literal> component. If you don't add this line to your "
"<literal>components.xml</literal> file, Seam won't know when container-"
"managed transactions end:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:330
#, no-c-format
msgid "<![CDATA[<transaction:ejb-transaction/>]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:335
#, no-c-format
msgid "Don't forget!"
msgstr ""

#. Tag: para
#: Configuration.xml:337
#, no-c-format
msgid ""
"There is one final item you need to know about. You must place a "
"<literal>seam.properties</literal>, <literal>META-INF/seam.properties</"
"literal> or <literal>META-INF/components.xml</literal> file in any archive "
"in which your Seam components are deployed (even an empty properties file "
"will do). At startup, Seam will scan any archives with <literal>seam."
"properties</literal> files for seam components."
msgstr ""

#. Tag: para
#: Configuration.xml:342
#, no-c-format
msgid ""
"In a web archive (WAR) file, you must place a <literal>seam.properties</"
"literal> file in the <literal>WEB-INF/classes</literal> directory if you "
"have any Seam components included here."
msgstr ""

#. Tag: para
#: Configuration.xml:345
#, no-c-format
msgid ""
"That's why all the Seam examples have an empty <literal>seam.properties</"
"literal> file. You can't just delete this file and expect everything to "
"still work!"
msgstr ""

#. Tag: para
#: Configuration.xml:348
#, no-c-format
msgid ""
"You might think this is silly and what kind of idiot framework designers "
"would make an empty file affect the behavior of their software?? Well, this "
"is a workaround for a limitation of the JVM&#8212;if we didn't use this "
"mechanism, our next best option would be to force you to list every "
"component explicitly in <literal>components.xml</literal>, just like some "
"other competing frameworks do! I think you'll like our way better."
msgstr ""

#. Tag: title
#: Configuration.xml:359
#, no-c-format
msgid "Using Alternate JPA Providers"
msgstr ""

#. Tag: para
#: Configuration.xml:361
#, no-c-format
msgid ""
"Seam comes packaged and configured with Hibernate as the default JPA "
"provider. If you require using a different JPA provider you must tell "
"<literal>seam</literal> about it."
msgstr ""

#. Tag: title
#: Configuration.xml:367
#, no-c-format
msgid "This is a workaround"
msgstr ""

#. Tag: para
#: Configuration.xml:368
#, no-c-format
msgid ""
"Configuration of the JPA provider will be easier in the future and will not "
"require configuration changes, unless you are adding a custom persistence "
"provider implementation."
msgstr ""

#. Tag: para
#: Configuration.xml:375
#, no-c-format
msgid ""
"Telling seam about a different JPA provider can be be done in one of two "
"ways:"
msgstr ""

#. Tag: para
#: Configuration.xml:376
#, no-c-format
msgid ""
"Update your application's <literal>components.xml</literal> so that the "
"generic <literal>PersistenceProvider</literal> takes precedence over the "
"hibernate version. Simply add the following to the file:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:381
#, no-c-format
msgid ""
"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
"\" \n"
"           class=\"org.jboss.seam.persistence.PersistenceProvider\"\n"
"           scope=\"stateless\">\n"
"</component>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:382
#, no-c-format
msgid ""
"If you want to take advantage of your JPA provider's non-standard features "
"you will need to write you own implementation of the "
"<literal>PersistenceProvider</literal>. Use "
"<literal>HibernatePersistenceProvider</literal> as a starting point (don't "
"forget to give back to the community :). Then you will need to tell "
"<literal>seam</literal> to use it as before."
msgstr ""

#. Tag: programlisting
#: Configuration.xml:389
#, no-c-format
msgid ""
"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
"\" \n"
"           class=\"org.your.package.YourPersistenceProvider\">\n"
"</component>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:390
#, no-c-format
msgid ""
"All that is left is updating the <literal>persistence.xml</literal> file "
"with the correct provider class, and what ever properties your provider "
"needs. Don't forget to package your new provider's jar files in the "
"application if they are needed."
msgstr ""

#. Tag: title
#: Configuration.xml:398
#, no-c-format
msgid "Configuring Seam in Java EE 5"
msgstr ""

#. Tag: para
#: Configuration.xml:409
#, no-c-format
msgid ""
"If you're running in a Java EE 5 environment, this is all the configuration "
"required to start using Seam!"
msgstr ""

#. Tag: title
#: Configuration.xml:412 Configuration.xml:507 Configuration.xml:623
#: Configuration.xml:656
#, no-c-format
msgid "Packaging"
msgstr ""

#. Tag: para
#: Configuration.xml:414
#, no-c-format
msgid ""
"Once you've packaged all this stuff together into an EAR, the archive "
"structure will look something like this:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:417
#, no-c-format
msgid ""
"<![CDATA[my-application.ear/\n"
"    jboss-seam.jar\n"
"    lib/\n"
"        jboss-el.jar\n"
"    META-INF/\n"
"        MANIFEST.MF\n"
"        application.xml\n"
"    my-application.war/\n"
"        META-INF/\n"
"            MANIFEST.MF\n"
"        WEB-INF/\n"
"            web.xml\n"
"            components.xml\n"
"            faces-config.xml\n"
"            lib/\n"
"                jsf-facelets.jar\n"
"                jboss-seam-ui.jar\n"
"        login.jsp\n"
"        register.jsp\n"
"        ...\n"
"    my-application.jar/\n"
"        META-INF/\n"
"            MANIFEST.MF\n"
"            persistence.xml\n"
"        seam.properties\n"
"        org/\n"
"            jboss/\n"
"                myapplication/\n"
"                    User.class\n"
"                    Login.class\n"
"                    LoginBean.class\n"
"                    Register.class\n"
"                    RegisterBean.class\n"
"                    ...]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:419
#, no-c-format
msgid ""
"You should declare <literal>jboss-seam.jar</literal> as an ejb module in "
"<literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> "
"should be placed in the EAR's lib directory (putting it in the EAR classpath."
msgstr ""

#. Tag: para
#: Configuration.xml:424
#, no-c-format
msgid ""
"If you want to use jBPM or Drools, you must include the needed jars in the "
"EAR's lib directory."
msgstr ""

#. Tag: para
#: Configuration.xml:426
#, no-c-format
msgid ""
"If you want to use facelets (our recommendation), you must include "
"<literal>jsf-facelets.jar</literal> in the <literal>WEB-INF/lib</literal> "
"directory of the WAR."
msgstr ""

#. Tag: para
#: Configuration.xml:429
#, no-c-format
msgid ""
"If you want to use the Seam tag library (most Seam applications do), you "
"must include <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/"
"lib</literal> directory of the WAR. If you want to use the PDF or email tag "
"libraries, you need to put <literal>jboss-seam-pdf.jar</literal> or "
"<literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
msgstr ""

#. Tag: para
#: Configuration.xml:434
#, no-c-format
msgid ""
"If you want to use the Seam debug page (only works for applications using "
"facelets), you must include <literal>jboss-seam-debug.jar</literal> in the "
"<literal>WEB-INF/lib</literal> directory of the WAR."
msgstr ""

#. Tag: para
#: Configuration.xml:437
#, no-c-format
msgid ""
"Seam ships with several example applications that are deployable in any Java "
"EE container that supports EJB 3.0."
msgstr ""

#. Tag: para
#: Configuration.xml:440
#, no-c-format
msgid ""
"I really wish that was all there was to say on the topic of configuration "
"but unfortunately we're only about a third of the way there. If you're too "
"overwhelmed by all this tedious configuration stuff, feel free to skip over "
"the rest of this section and come back to it later."
msgstr ""

#. Tag: title
#: Configuration.xml:449
#, no-c-format
msgid "Configuring Seam in J2EE"
msgstr ""

#. Tag: para
#: Configuration.xml:451
#, no-c-format
msgid ""
"Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. "
"In this case you would use Hibernate3 or JPA instead of EJB 3.0 persistence, "
"and plain JavaBeans instead of session beans. You'll miss out on some of the "
"nice features of session beans but it will be very easy to migrate to EJB "
"3.0 when you're ready and, in the meantime, you'll be able to take advantage "
"of Seam's unique declarative state management architecture."
msgstr ""

#. Tag: para
#: Configuration.xml:466
#, no-c-format
msgid ""
"Seam JavaBean components do not provide declarative transaction demarcation "
"like session beans do. You <emphasis>could</emphasis> manage your "
"transactions manually using the JTA <literal>UserTransaction</literal> or "
"declaratively using Seam's <literal>@Transactional</literal> annotation. But "
"most applications will just use Seam managed transactions when using "
"Hibernate with JavaBeans."
msgstr ""

#. Tag: para
#: Configuration.xml:472
#, no-c-format
msgid ""
"The Seam distribution includes a version of the booking example application "
"that uses Hibernate3 and JavaBeans instead of EJB3, and another version that "
"uses JPA and JavaBeans. These example applications are ready to deploy into "
"any J2EE application server."
msgstr ""

#. Tag: title
#: Configuration.xml:477
#, no-c-format
msgid "Boostrapping Hibernate in Seam"
msgstr ""

#. Tag: para
#: Configuration.xml:479
#, no-c-format
msgid ""
"Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your "
"<literal>hibernate.cfg.xml</literal> file if you install a built-in "
"component:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:482
#, no-c-format
msgid ""
"<![CDATA[<persistence:hibernate-session-factory name="
"\"hibernateSessionFactory\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:484
#, no-c-format
msgid ""
"You will also need to configure a <emphasis>managed session</emphasis> if "
"you want a Seam managed Hibernate <literal>Session</literal> to be available "
"via injection."
msgstr ""

#. Tag: programlisting
#: Configuration.xml:487
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n"
"                            session-factory=\"#{hibernateSessionFactory}\"/"
">]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:492
#, no-c-format
msgid "Boostrapping JPA in Seam"
msgstr ""

#. Tag: para
#: Configuration.xml:494
#, no-c-format
msgid ""
"Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your "
"<literal>persistence.xml</literal> file if you install this built-in "
"component:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:497
#, no-c-format
msgid ""
"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/"
">]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:499
#, no-c-format
msgid ""
"You will also need to configure a <emphasis>managed persistence context</"
"emphasis> if you want a Seam managed JPA <literal>EntityManager</literal> to "
"be available via injection."
msgstr ""

#. Tag: programlisting
#: Configuration.xml:502
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
"                            entity-manager-factory=\"#{entityManagerFactory}"
"\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:509
#, no-c-format
msgid "We can package our application as a WAR, in the following structure:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:511
#, no-c-format
msgid ""
"<![CDATA[my-application.war/\n"
"    META-INF/\n"
"        MANIFEST.MF\n"
"    WEB-INF/\n"
"        web.xml\n"
"        components.xml\n"
"        faces-config.xml\n"
"        lib/\n"
"            jboss-seam.jar\n"
"            jboss-seam-ui.jar\n"
"            jboss-el.jar\n"
"            jsf-facelets.jar\n"
"            hibernate3.jar\n"
"            hibernate-annotations.jar\n"
"            hibernate-validator.jar\n"
"            ...\n"
"            my-application.jar/\n"
"                META-INF/\n"
"                   MANIFEST.MF\n"
"                seam.properties\n"
"                hibernate.cfg.xml\n"
"                org/\n"
"                    jboss/\n"
"                        myapplication/\n"
"                            User.class\n"
"                            Login.class\n"
"                            Register.class\n"
"                            ...\n"
"    login.jsp\n"
"    register.jsp\n"
"    ...]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:513
#, no-c-format
msgid ""
"If we want to deploy Hibernate in a non-EE environment like Tomcat or "
"TestNG, we need to do a little bit more work."
msgstr ""

#. Tag: title
#: Configuration.xml:520
#, no-c-format
msgid "Configuring Seam in Java SE, without JBoss Embedded"
msgstr ""

#. Tag: para
#: Configuration.xml:522
#, no-c-format
msgid ""
"It is possible to use Seam completely outside of an EE environment. In this "
"case, you need to tell Seam how to manage transactions, since there will be "
"no JTA available. If you're using JPA, you can tell Seam to use JPA resource-"
"local transactions, ie. <literal>EntityTransaction</literal>, like so:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:526
#, no-c-format
msgid ""
"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/"
">]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:528
#, no-c-format
msgid ""
"If you're using Hibernate, you can tell Seam to use the Hibernate "
"transaction API like this:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:530
#, no-c-format
msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:532
#, no-c-format
msgid "Of course, you'll also need to define a datasource."
msgstr ""

#. Tag: para
#: Configuration.xml:534
#, no-c-format
msgid ""
"A better alternative is to use JBoss Embedded to get access to the EE APIs."
msgstr ""

#. Tag: title
#: Configuration.xml:539
#, no-c-format
msgid "Configuring Seam in Java SE, with JBoss Embedded"
msgstr ""

#. Tag: para
#: Configuration.xml:541
#, no-c-format
msgid ""
"JBoss Embedded lets you run EJB3 components outside the context of the Java "
"EE 5 application server. This is especially, but not only, useful for "
"testing."
msgstr ""

#. Tag: para
#: Configuration.xml:544
#, no-c-format
msgid ""
"The Seam booking example application includes a TestNG integration test "
"suite that runs on JBoss Embedded via <literal>SeamTest</literal>."
msgstr ""

#. Tag: para
#: Configuration.xml:556
#, no-c-format
msgid "The booking example application may even be deployed to Tomcat."
msgstr ""

#. Tag: title
#: Configuration.xml:568
#, no-c-format
msgid "Installing Embedded JBoss"
msgstr ""

#. Tag: para
#: Configuration.xml:571
#, no-c-format
msgid ""
"Embedded JBoss must by installed into Tomcat for Seam applications to run "
"correctly on it. Embedded JBoss only runs on JDK 1.5 (not JDK 1.6). Embedded "
"JBoss can be downloaded <ulink url=\"http://sourceforge.net/project/"
"showfiles.php?group_id=22866&amp;package_id=228977\">here</ulink>. The "
"process for installing Embedded JBoss into Tomcat 6 is quite simple. First, "
"you should copy the Embedded JBoss JARs and configuration files into Tomcat."
msgstr ""

#. Tag: para
#: Configuration.xml:584
#, no-c-format
msgid ""
"Copy all files and directories under the Embedded JBoss <literal>bootstrap</"
"literal> and <literal>lib</literal> directories, except for the "
"<literal>jndi.properties</literal> file, into the Tomcat <literal>lib</"
"literal> directory."
msgstr ""

#. Tag: para
#: Configuration.xml:591
#, no-c-format
msgid ""
"Remove the <literal>annotations-api.jar</literal> file from the Tomcat "
"<literal>lib</literal> directory."
msgstr ""

#. Tag: para
#: Configuration.xml:597
#, no-c-format
msgid ""
"Next, two configuration files need to be updated to add Embedded JBoss-"
"specific functionality."
msgstr ""

#. Tag: para
#: Configuration.xml:603
#, no-c-format
msgid ""
"Add the Embedded JBoss listener to <literal>conf/server.xml</literal>. It "
"should appear after all other listeners in the file."
msgstr ""

#. Tag: programlisting
#: Configuration.xml:606
#, no-c-format
msgid ""
"<![CDATA[<Listener className=\"org.jboss.embedded.tomcat."
"EmbeddedJBossBootstrapListener\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:610
#, no-c-format
msgid ""
"WAR file scanning should be enabled by adding a listener to <literal>conf/"
"context.xml</literal>."
msgstr ""

#. Tag: programlisting
#: Configuration.xml:613
#, no-c-format
msgid ""
"<![CDATA[<Listener className=\"org.jboss.embedded.tomcat.WebinfScanner\"/>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:617
#, no-c-format
msgid ""
"For more configuration options, please see the Embedded JBoss Tomcat "
"integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
"page=EmbeddedAndTomcat\">wiki entry</ulink>."
msgstr ""

#. Tag: para
#: Configuration.xml:625
#, no-c-format
msgid ""
"The archive structure of a WAR-based deployment on an servlet engine like "
"Tomcat will look something like this:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:628
#, no-c-format
msgid ""
"<![CDATA[my-application.war/\n"
"    META-INF/\n"
"        MANIFEST.MF\n"
"    WEB-INF/\n"
"        web.xml\n"
"        components.xml\n"
"        faces-config.xml\n"
"        lib/\n"
"            jboss-seam.jar\n"
"            jboss-seam-ui.jar\n"
"            jboss-el.jar\n"
"            jsf-facelets.jar\n"
"            jsf-api.jar\n"
"            jsf-impl.jar\n"
"            ...\n"
"            my-application.jar/\n"
"                META-INF/\n"
"                    MANIFEST.MF\n"
"                    persistence.xml\n"
"                seam.properties\n"
"                org/\n"
"                    jboss/\n"
"                        myapplication/\n"
"                            User.class\n"
"                            Login.class\n"
"                            LoginBean.class\n"
"                            Register.class\n"
"                            RegisterBean.class\n"
"                            ...\n"
"    login.jsp\n"
"    register.jsp\n"
"    ...]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:630
#, no-c-format
msgid ""
"Most of the Seam example applications may be deployed to Tomcat by running "
"<literal>ant deploy.tomcat</literal>."
msgstr ""

#. Tag: title
#: Configuration.xml:638
#, no-c-format
msgid "Configuring jBPM in Seam"
msgstr ""

#. Tag: para
#: Configuration.xml:639
#, no-c-format
msgid ""
"Seam's jBPM integration is not installed by default, so you'll need to "
"enable jBPM by installing a built-in component. You'll also need to "
"explicitly list your process and pageflow definitions. In "
"<literal>components.xml</literal>:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:643
#, no-c-format
msgid ""
"<![CDATA[<bpm:jbpm>\n"
"    <bpm:pageflow-definitions>\n"
"        <value>createDocument.jpdl.xml</value>\n"
"        <value>editDocument.jpdl.xml</value>\n"
"        <value>approveDocument.jpdl.xml</value>\n"
"    </bpm:pageflow-definitions>\n"
"    <bpm:process-definitions>\n"
"        <value>documentLifecycle.jpdl.xml</value>\n"
"    </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:645
#, no-c-format
msgid ""
"No further special configuration is needed if you only have pageflows. If "
"you do have business process definitions, you need to provide a jBPM "
"configuration, and a Hibernate configuration for jBPM. The Seam DVD Store "
"demo includes example <literal>jbpm.cfg.xml</literal> and <literal>hibernate."
"cfg.xml</literal> files that will work with Seam:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:650
#, no-c-format
msgid ""
"<![CDATA[<jbpm-configuration>\n"
"\n"
"  <jbpm-context>\n"
"    <service name=\"persistence\">\n"
"       <factory>\n"
"          <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory"
"\">\n"
"             <field name=\"isTransactionEnabled\"><false/></field>\n"
"          </bean>\n"
"       </factory>\n"
"    </service>\n"
"    <service name=\"tx\" factory=\"org.jbpm.tx.TxServiceFactory\" />\n"
"    <service name=\"message\" factory=\"org.jbpm.msg.db."
"DbMessageServiceFactory\" />\n"
"    <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db."
"DbSchedulerServiceFactory\" />\n"
"    <service name=\"logging\" factory=\"org.jbpm.logging.db."
"DbLoggingServiceFactory\" />\n"
"    <service name=\"authentication\" \n"
"             factory=\"org.jbpm.security.authentication."
"DefaultAuthenticationServiceFactory\" />\n"
"  </jbpm-context>\n"
"\n"
"</jbpm-configuration>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:652
#, no-c-format
msgid ""
"The most important thing to notice here is that jBPM transaction control is "
"disabled. Seam or EJB3 should control the JTA transactions."
msgstr ""

#. Tag: para
#: Configuration.xml:658
#, no-c-format
msgid ""
"There is not yet any well-defined packaging format for jBPM configuration "
"and process/pageflow definition files. In the Seam examples we've decided to "
"simply package all these files into the root of the EAR. In future, we will "
"probably design some other standard packaging format. So the EAR looks "
"something like this:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:663
#, no-c-format
msgid ""
"<![CDATA[my-application.ear/\n"
"    jboss-seam.jar\n"
"    lib/\n"
"       jboss-el.jar\n"
"       jbpm-3.1.jar\n"
"    META-INF/\n"
"        MANIFEST.MF\n"
"        application.xml\n"
"    my-application.war/\n"
"        META-INF/\n"
"            MANIFEST.MF\n"
"        WEB-INF/\n"
"            web.xml\n"
"            components.xml\n"
"            faces-config.xml\n"
"            lib/\n"
"                jsf-facelets.jar\n"
"                jboss-seam-ui.jar\n"
"        login.jsp\n"
"        register.jsp\n"
"        ...\n"
"    my-application.jar/\n"
"        META-INF/\n"
"            MANIFEST.MF\n"
"            persistence.xml\n"
"        seam.properties\n"
"        org/\n"
"            jboss/\n"
"                myapplication/\n"
"                    User.class\n"
"                    Login.class\n"
"                    LoginBean.class\n"
"                    Register.class\n"
"                    RegisterBean.class\n"
"                    ...\n"
"    jbpm.cfg.xml\n"
"    hibernate.cfg.xml\n"
"    createDocument.jpdl.xml\n"
"    editDocument.jpdl.xml\n"
"    approveDocument.jpdl.xml\n"
"    documentLifecycle.jpdl.xml]]>"
msgstr ""

#. Tag: title
#: Configuration.xml:670
#, no-c-format
msgid "Configuring SFSB and Session Timeouts in JBoss AS"
msgstr ""

#. Tag: para
#: Configuration.xml:672
#, no-c-format
msgid ""
"It is very important that the timeout for Stateful Session Beans is set "
"higher than the timeout for HTTP Sessions, otherwise SFSB's may time out "
"before the user's HTTP session has ended. JBoss Application Server has a "
"default session bean timeout of 30 minutes, which is configured in "
"<literal>server/default/conf/standardjboss.xml</literal> (replace "
"<emphasis>default</emphasis> with your own configuration)."
msgstr ""

#. Tag: para
#: Configuration.xml:678
#, no-c-format
msgid ""
"The default SFSB timeout can be adjusted by modifying the value of "
"<literal>max-bean-life</literal> in the "
"<literal>LRUStatefulContextCachePolicy</literal> cache configuration:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:681
#, no-c-format
msgid ""
"<![CDATA[<container-cache-conf>\n"
"    <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-"
"policy>\n"
"    <cache-policy-conf>\n"
"        <min-capacity>50</min-capacity>\n"
"        <max-capacity>1000000</max-capacity>\n"
"        <remover-period>1800</remover-period>\n"
"\n"
"        <!-- SFSB timeout in seconds; 1800 seconds == 30 minutes -->\n"
"        <max-bean-life>1800</max-bean-life>  \n"
"\n"
"        <overager-period>300</overager-period>\n"
"        <max-bean-age>600</max-bean-age>\n"
"        <resizer-period>400</resizer-period>\n"
"        <max-cache-miss-period>60</max-cache-miss-period>\n"
"        <min-cache-miss-period>1</min-cache-miss-period>\n"
"        <cache-load-factor>0.75</cache-load-factor>\n"
"    </cache-policy-conf>\n"
"</container-cache-conf>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:683
#, no-c-format
msgid ""
"The default HTTP session timeout can be modified in <literal>server/default/"
"deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in "
"<literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for "
"JBoss 4.2.x. The following entry in this file controls the default session "
"timeout for all web applications:"
msgstr ""

#. Tag: programlisting
#: Configuration.xml:688
#, no-c-format
msgid ""
"<![CDATA[<session-config>\n"
"    <!-- HTTP Session timeout, in minutes -->\n"
"    <session-timeout>30</session-timeout>\n"
"</session-config>]]>"
msgstr ""

#. Tag: para
#: Configuration.xml:690
#, no-c-format
msgid ""
"To override this value for your own application, simply include this entry "
"in your application's own <literal>web.xml</literal>."
msgstr ""

#. Tag: title
#: Configuration.xml:696
#, no-c-format
msgid "Running Seam in a Portlet"
msgstr ""

#. Tag: para
#: Configuration.xml:698
#, no-c-format
msgid ""
"If you want to run your Seam application in a portlet, take a look at the "
"JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within "
"a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://"
"labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> "
"for more."
msgstr ""
