Author: nico.ben Date: 2009-03-31 17:31:32 -0400 (Tue, 31 Mar 2009) New Revision: 10259 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-03-31 21:19:40 UTC (rev 10258) +++ trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-03-31 21:31:32 UTC (rev 10259) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-03-17 20:34+0000\n" -"PO-Revision-Date: 2009-02-06 18:27+0100\n" +"PO-Revision-Date: 2009-03-31 23:31+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -22,20 +22,8 @@ #. 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 use seam-gen to start your application or you " -"can copy and paste from the example applications!" -msgstr "" -"La configurazione è un argomento molto noioso ed un passatempo estremamente " -"tedioso. Sfortunatamente sono richieste parecchie linee di XML per integrare " -"Seam con l'implementazione JSF ed il servlet container. Non c'è alcun " -"bisogno di soffermarsi sulle seguenti sezioni; non si dovrà mai scrivere " -"queste cose a mano, poiché basta usare seam-gen per iniziare l'applicazione " -"oppure basta copiare ed incollare il codice dagli esempi di applicazione!" +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 use seam-gen to start your application or you can copy and paste from the example applications!" +msgstr "La configurazione è un argomento molto noioso ed un passatempo estremamente tedioso. Sfortunatamente sono richieste parecchie linee di XML per integrare Seam con l'implementazione JSF ed il servlet container. Non c'è alcun bisogno di soffermarsi sulle seguenti sezioni; non si dovrà mai scrivere queste cose a mano, poiché basta usare seam-gen per iniziare l'applicazione oppure basta copiare ed incollare il codice dagli esempi di applicazione!" #. Tag: title #: Configuration.xml:12 @@ -46,12 +34,8 @@ #. 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 "" -"In primo luogo si comincia a guardare alla configurazione base che server " -"ogni volta che si usa Seam con JSF." +msgid "First, let's look at the basic configuration that is needed whenever we use Seam with JSF." +msgstr "In primo luogo si comincia a guardare alla configurazione base che server ogni volta che si usa Seam con JSF." #. Tag: title #: Configuration.xml:17 @@ -100,12 +84,8 @@ #. Tag: para #: Configuration.xml:25 #, no-c-format -msgid "" -"In addition, Seam requires the following entry in your <literal>web.xml</" -"literal> file:" -msgstr "" -"In aggiunta, Seam richiede la seguente voce nel file <literal>web.xml</" -"literal>:" +msgid "In addition, Seam requires the following entry in your <literal>web.xml</literal> file:" +msgstr "In aggiunta, Seam richiede la seguente voce nel file <literal>web.xml</literal>:" #. Tag: programlisting #: Configuration.xml:27 @@ -122,29 +102,14 @@ #. Tag: para #: Configuration.xml:29 #, no-c-format -msgid "" -"This listener is responsible for bootstrapping Seam, and for destroying " -"session and application contexts." -msgstr "" -"Questo listener è responsabile dell'avvio di Seam e della distruzione dei " -"contesti di sessione e di applicazione." +msgid "This listener is responsible for bootstrapping Seam, and for destroying session and application contexts." +msgstr "Questo listener è responsabile dell'avvio di Seam e della distruzione dei contesti di sessione e di applicazione." #. 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 "" -"Alcune implementazioni JSF hanno un'implementazione erronea della " -"conservazione dello stato lato server, che interferisce con la propagazione " -"della conversazione di Seam. Se si hanno problemi con la propagazione della " -"conversazione durante l'invio di form, si provi a cambiare impostanto la " -"conservazione lato client. Occorre impostare questo in <literal>web.xml</" -"literal>:" +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 "Alcune implementazioni JSF hanno un'implementazione erronea della conservazione dello stato lato server, che interferisce con la propagazione della conversazione di Seam. Se si hanno problemi con la propagazione della conversazione durante l'invio di form, si provi a cambiare impostanto la conservazione lato client. Occorre impostare questo in <literal>web.xml</literal>:" #. Tag: programlisting #: Configuration.xml:36 @@ -163,31 +128,8 @@ #. Tag: para #: Configuration.xml:38 #, no-c-format -msgid "" -"There is a minor gray area in the JSF specification regarding the mutability " -"of view state values. Since Seam uses the JSF view state to back its PAGE " -"scope this can become an issue in some cases. If you're using server side " -"state saving with the JSF-RI and you want a PAGE scoped bean to keep its " -"exact value for a given view of a page you will need to specify the " -"following context-param. Otherwise if a user uses the \"back\" button a PAGE " -"scoped component will have the latest value if it has changed not the value " -"of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public." -"dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This " -"setting is not enabled by default because of the performance hit of " -"serializing the JSF view with every request." -msgstr "" -"C'è una piccola parte grigia nella specifica JSF riguardante la mutabilità " -"dei valore dello stato della vista. Poiché Seam usa lo stato della vista JSF " -"per tornare allo scope PAGE, questo in alcuni casi può diventare un " -"problema. Se si usa la conservazione dello stato lato server con JSF-RI e si " -"vuole che il bean con scope PAGE mantenga l'esatto valore per una data vista " -"di pagina, occorre specificare il seguente parametro di contesto. Altrimenti " -"se un utente usa il pulsante \"indietro\" un componente con scope PAGE avrà " -"l'ultimo valore se questo non è cambiato nella pagina \"indietro\". (si veda " -"<ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/" -"show_bug.cgi?id=295\"> Spec Issue </ulink> ). Quest'impostazione non è " -"abilitata di default a causa della performance nella serializzazione della " -"vista JSF ad ogni richiesta." +msgid "There is a minor gray area in the JSF specification regarding the mutability of view state values. Since Seam uses the JSF view state to back its PAGE scope this can become an issue in some cases. If you're using server side state saving with the JSF-RI and you want a PAGE scoped bean to keep its exact value for a given view of a page you will need to specify the following context-param. Otherwise if a user uses the \"back\" button a PAGE scoped component will have the latest value if it has changed not the value of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_b... Spec Issue </ulink> ). This setting is not enabled by default because of the performance hit of serializing the JSF view with every request." +msgstr "C'è una piccola parte grigia nella specifica JSF riguardante la mutabilità dei valore dello stato della vista. Poiché Seam usa lo stato della vista JSF per tornare allo scope PAGE, questo in alcuni casi può diventare un problema. Se si usa la conservazione dello stato lato server con JSF-RI e si vuole che il bean con scope PAGE mantenga l'esatto valore per una data vista di pagina, occorre specificare il seguente parametro di contesto. Altrimenti se un utente usa il pulsante \"indietro\" un componente con scope PAGE avrà l'ultimo valore se questo non è cambiato nella pagina \"indietro\". (si veda <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_b... Spec Issue </ulink> ). Quest'impostazione non è abilitata di default a causa della performance nella serializzazione della vista JSF ad ogni richiesta." #. Tag: programlisting #: Configuration.xml:52 @@ -212,12 +154,8 @@ #. Tag: para #: Configuration.xml:58 #, 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 "" -"Se si vuole seguire il consiglio ed usare Facelets invece di JSP, si " -"aggiungano le seguenti linee a <literal>faces-config.xml</literal>:" +msgid "If you want follow our advice and use Facelets instead of JSP, add the following lines to <literal>faces-config.xml</literal>:" +msgstr "Se si vuole seguire il consiglio ed usare Facelets invece di JSP, si aggiungano le seguenti linee a <literal>faces-config.xml</literal>:" #. Tag: programlisting #: Configuration.xml:61 @@ -254,26 +192,8 @@ #. Tag: para #: Configuration.xml:67 #, no-c-format -msgid "" -"If you are using facelets in JBoss AS, you'll find that Facelets logging is " -"broken (the log messages don't make it to the server log). Seam provides a " -"bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</" -"literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/" -"jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in " -"the <literal>WEB-INF/lib</literal> of your application. The Facelets logging " -"catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/" -"nonav/docs/dev/docbook.html#config-logging\">Facelets Developer " -"Documentation</ulink>." -msgstr "" -"Se si usa facelets in JBoss AS, si noterà che il logging di Facelets è " -"guasto (i messaggi di log non appaiono nel log del server). Seam fornisce un " -"modo per sistemare questo problema, per usarlo si copi <literal>lib/interop/" -"jboss-seam-jul.jar</literal> in <literal>$JBOSS_HOME/server/default/deploy/" -"jboss-web.deployer/jsf-libs/</literal> e si includa <literal>jboss-seam-ui." -"jar</literal> nel <literal>WEB-INF/lib</literal> dell'applicazione. Le " -"categorie di logging di Facelets sono elencate nella <ulink url=\"https://" -"facelets.dev.java.net/nonav/docs/dev/docbook.html#config-logging" -"\">Documentazione per lo sviluppatore Facelets</ulink>." +msgid "If you are using facelets in JBoss AS, you'll find that Facelets logging is broken (the log messages don't make it to the server log). Seam provides a bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/lib</literal> of your application. The Facelets logging catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/nonav/docs/dev/docbook.html#conf... Developer Documentation</ulink>." +msgstr "Se si usa facelets in JBoss AS, si noterà che il logging di Facelets è guasto (i messaggi di log non appaiono nel log del server). Seam fornisce un modo per sistemare questo problema, per usarlo si copi <literal>lib/interop/jboss-seam-jul.jar</literal> in <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/jsf-libs/</literal> e si includa <literal>jboss-seam-ui.jar</literal> nel <literal>WEB-INF/lib</literal> dell'applicazione. Le categorie di logging di Facelets sono elencate nella <ulink url=\"https://facelets.dev.java.net/nonav/docs/dev/docbook.html#conf... per lo sviluppatore Facelets</ulink>." #. Tag: title #: Configuration.xml:81 @@ -284,11 +204,8 @@ #. Tag: para #: Configuration.xml:83 #, 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 "" +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 "Seam Resource Servlet fornisce le risorse usate da Seam Remoting, captchas (si veda il capitolo sulla sicurezza) ed altri controlli JSF UI. Configurare Seam Resource Servlet richiede la seguente riga in <literal>web.xml</literal>:" #. Tag: programlisting #: Configuration.xml:87 @@ -323,13 +240,8 @@ #. Tag: para #: Configuration.xml:93 #, 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 "" +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 "Seam non ha bisogno di filtri servlet per le operazioni base. Comunque ci sono parecchie caratteristiche che dipendono dall'uso dei filtri. Per facilitare le cose, Seam lascia aggiungere e configurare i filtri servlet così come si configurano gli altri componenti predefiniti di Seam. Per sfruttare questa caratteristica occorre installa un filtro master in <literal>web.xml</literal>:" #. Tag: programlisting #: Configuration.xml:98 @@ -358,53 +270,37 @@ #. Tag: para #: Configuration.xml:100 #, 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 "" +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 "Il filtro master di Seam <emphasis>deve</emphasis> essere il primo filtro specificato in <literal>web.xml</literal>. Questo assicura che venga eseguito per primo." #. Tag: para #: Configuration.xml:103 #, 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 "" +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 "I filtri Seam condividono un numero di attributi comuni, si possono impostare questi in <literal>components.xml</literal> in aggiunto ai parametri discussi sotto:" #. Tag: para #: Configuration.xml:111 #, 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 "" +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 "<literal>url-pattern</literal> &#8212; Usato per specificare quali richieste vengono filtrate, il default è tutte le richieste. <literal>url-pattern</literal> è un pattern di stile di Tomcat che consente un suffisso wildcard." #. Tag: para #: Configuration.xml:118 #, 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." -msgstr "" +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." +msgstr "<literal>regex-url-pattern</literal> &#8212; Usato per specificare quali richieste vengono filtrate, il default è tutte le richieste. <literal>regex-url-pattern</literal> è una vera espressione regolare per il percorso di richiesta." #. Tag: para #: Configuration.xml:125 #, no-c-format msgid "<literal>disabled</literal> &#8212; Used to disable a built in filter." -msgstr "" -"<literal>disabled</literal> &#8212; Usato per disabilitare il filtro " -"predefinito." +msgstr "<literal>disabled</literal> &#8212; Usato per disabilitare il filtro predefinito." #. Tag: para #: Configuration.xml:131 #, no-c-format -msgid "" -"Note that the patterns are matched against the URI path of the request (see " -"<literal>HttpServletRequest.getURIPath()</literal>) and that the name of the " -"servlet context is removed before matching." +msgid "Note that the patterns are matched against the URI path of the request (see <literal>HttpServletRequest.getURIPath()</literal>) and that the name of the servlet context is removed before matching." msgstr "" #. Tag: para @@ -422,24 +318,13 @@ #. Tag: para #: Configuration.xml:141 #, 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.)" +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:147 #, 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:" +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 @@ -464,23 +349,18 @@ #: Configuration.xml:157 #, no-c-format msgid "Conversation propagation with redirects" -msgstr "" +msgstr "Propagazione delle conversazioni con i redirect" #. Tag: para #: Configuration.xml:158 #, 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." +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:162 #, 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>:" +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 @@ -498,11 +378,7 @@ #. Tag: para #: Configuration.xml:171 #, no-c-format -msgid "" -"This filter allows Seam to apply URL rewriting for views based on " -"configuration in the <literal>pages.xml</literal> file. This filter is not " -"activate by default, but can be activated by adding the configuration to " -"<literal>components.xml</literal>:" +msgid "This filter allows Seam to apply URL rewriting for views based on configuration in the <literal>pages.xml</literal> file. This filter is not activate by default, but can be activated by adding the configuration to <literal>components.xml</literal>:" msgstr "" #. Tag: programlisting @@ -514,10 +390,7 @@ #. Tag: para #: Configuration.xml:179 #, no-c-format -msgid "" -"The <literal>view-mapping</literal> parameter must match the servlet mapping " -"defined for the Faces Servlet in the <literal>web.xml</literal> file. If " -"ommitted, the rewrite filter assumes the pattern <literal>*.seam</literal>." +msgid "The <literal>view-mapping</literal> parameter must match the servlet mapping defined for the Faces Servlet in the <literal>web.xml</literal> file. If ommitted, the rewrite filter assumes the pattern <literal>*.seam</literal>." msgstr "" #. Tag: title @@ -529,11 +402,7 @@ #. Tag: para #: Configuration.xml:187 #, 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>:" +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 @@ -551,21 +420,13 @@ #. Tag: para #: Configuration.xml:195 #, 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>." +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:202 #, 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)." +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 @@ -581,11 +442,10 @@ msgstr "" #. Tag: para -#: Configuration.xml:214 Configuration.xml:309 +#: Configuration.xml:214 +#: Configuration.xml:309 #, no-c-format -msgid "" -"This filter is not installed by default and requires an entry in " -"<literal>components.xml</literal> to enable it:" +msgid "This filter is not installed by default and requires an entry in <literal>components.xml</literal> to enable it:" msgstr "" #. Tag: programlisting @@ -609,13 +469,7 @@ #. Tag: para #: Configuration.xml:225 #, 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>." +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 @@ -627,28 +481,19 @@ #. Tag: para #: Configuration.xml:238 #, 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." +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:246 #, no-c-format -msgid "" -"The RichFaces Ajax filter is only installed if the RichFaces jars are " -"present in your project." +msgid "The RichFaces Ajax filter is only installed if the RichFaces jars are present in your project." msgstr "" #. Tag: para #: Configuration.xml:251 #, 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:" +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 @@ -668,56 +513,37 @@ #. Tag: para #: Configuration.xml:257 #, 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." +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:265 #, 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." +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:271 #, 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." +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:281 #, no-c-format msgid "Identity Logging" -msgstr "" +msgstr "Log delle identità" #. Tag: para #: Configuration.xml:283 #, 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." +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:289 #, 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:" +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 @@ -743,22 +569,13 @@ #. Tag: para #: Configuration.xml:299 #, 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." +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:303 #, 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." +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 @@ -770,19 +587,13 @@ #. Tag: para #: Configuration.xml:314 #, 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." +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:318 #, 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>." +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 @@ -794,13 +605,7 @@ #. Tag: para #: Configuration.xml:327 #, 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>):" +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 @@ -824,12 +629,7 @@ #. Tag: para #: Configuration.xml:334 #, 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&gt;(a)Filter(within=\&quot;org.&quot; -"jboss.seam.web.ajax4jsfFilter\")</literal>)." +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&gt;(a)Filter(within=\&quot;org.jboss.seam.web.ajax4jsfFilter\&quot;)&lt;/literal&gt;).&quot; msgstr "" #. Tag: title @@ -841,24 +641,13 @@ #. Tag: para #: Configuration.xml:345 #, no-c-format -msgid "" -"In a Seam application, EJB components have a certain duality, as they are " -"managed by both the EJB container and Seam. Actually, it's more that Seam " -"resolves EJB component references, manages the lifetime of stateful session " -"bean components, and also participates in each method call via interceptors. " -"Let's start with the configuration of the Seam interceptor chain." +msgid "In a Seam application, EJB components have a certain duality, as they are managed by both the EJB container and Seam. Actually, it's more that Seam resolves EJB component references, manages the lifetime of stateful session bean components, and also participates in each method call via interceptors. Let's start with the configuration of the Seam interceptor chain." msgstr "" #. Tag: para #: Configuration.xml:350 #, no-c-format -msgid "" -"We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB " -"components. This interceptor delegates to a set of built-in server-side " -"interceptors that handle such concerns as bijection, conversation " -"demarcation, and business process signals. The simplest way to do this " -"across an entire application is to add the following interceptor " -"configuration in <literal>ejb-jar.xml</literal>:" +msgid "We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB components. This interceptor delegates to a set of built-in server-side interceptors that handle such concerns as bijection, conversation demarcation, and business process signals. 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 @@ -867,32 +656,28 @@ msgid "" "<![CDATA[<interceptors>\n" " <interceptor>\n" -" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-" -"class>\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-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n" " </interceptor-binding>\n" "</assembly-descriptor>\n" "]]>" msgstr "" "<![CDATA[<interceptors>\n" " <interceptor>\n" -" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-" -"class>\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-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n" " </interceptor-binding>\n" "</assembly-descriptor>\n" "]]>" @@ -900,15 +685,7 @@ #. Tag: para #: Configuration.xml:357 #, 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 (and may depend " -"on your own naming conventions as well). We usually specify this option in " -"<literal>components.xml</literal>." +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 (and may depend on your own naming conventions as well). We usually specify this option in <literal>components.xml</literal>." msgstr "" #. Tag: para @@ -926,20 +703,13 @@ #. Tag: para #: Configuration.xml:368 #, no-c-format -msgid "" -"In this case, <literal>earName</literal> is the name of the EAR in which the " -"bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name " -"of the EJB, and the final segment represents the type of interface (local or " -"remote)." +msgid "In this case, <literal>earName</literal> is the name of the EAR in which the bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name of the EJB, and the final segment represents the type of interface (local or remote)." msgstr "" #. Tag: para #: Configuration.xml:372 #, no-c-format -msgid "" -"Outside the context of an EAR (when using the JBoss Embeddable EJB3 " -"container), the first segment is dropped since there is no EAR, leaving us " -"with the following pattern:" +msgid "Outside the context of an EAR (when using the JBoss Embeddable EJB3 container), the first segment is dropped since there is no EAR, leaving us with the following pattern:" msgstr "" #. Tag: programlisting @@ -951,36 +721,25 @@ #. Tag: para #: Configuration.xml:377 #, no-c-format -msgid "" -"How these JNDI names are resolved and somehow locate an EJB component might " -"appear a bit like black magic at this point, so let's dig into the details. " -"First, let's talk about how the EJB components get into JNDI." +msgid "How these JNDI names are resolved and somehow locate an EJB component might appear a bit like black magic at this point, so let's dig into the details. First, let's talk about how the EJB components get into JNDI." msgstr "" #. Tag: para #: Configuration.xml:381 #, no-c-format -msgid "" -"The folks at JBoss don't care much for XML, if you can't tell. So when they " -"designed JBoss AS, they decided that EJB components would get assigned a " -"global JNDI name automatically, using the pattern just described (i.e., EAR " -"name/EJB name/interface type). The EJB name is the first non-empty value " -"from the following list:" +msgid "The folks at JBoss don't care much for XML, if you can't tell. So when they designed JBoss AS, they decided that EJB components would get assigned a global JNDI name automatically, using the pattern just described (i.e., EAR name/EJB name/interface type). The EJB name is the first non-empty value from the following list:" msgstr "" #. Tag: para #: Configuration.xml:387 #, no-c-format -msgid "" -"The value of the <literal>&lt;ejb-name&gt;</literal> element in ejb-jar.xml" +msgid "The value of the <literal>&lt;ejb-name&gt;</literal> element in ejb-jar.xml" msgstr "" #. Tag: para #: Configuration.xml:390 #, no-c-format -msgid "" -"The value of the <literal>name</literal> attribute in the @Stateless or " -"@Stateful annotation" +msgid "The value of the <literal>name</literal> attribute in the @Stateless or @Stateful annotation" msgstr "" #. Tag: para @@ -992,9 +751,7 @@ #. Tag: para #: Configuration.xml:397 #, no-c-format -msgid "" -"Let's look at an example. Assume that you have the following EJB bean and " -"interface defined." +msgid "Let's look at an example. Assume that you have the following EJB bean and interface defined." msgstr "" #. Tag: programlisting @@ -1048,36 +805,19 @@ #. Tag: para #: Configuration.xml:401 #, no-c-format -msgid "" -"Assuming your EJB bean class is deployed in an EAR named myapp, the global " -"JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. " -"As you learned, you can reference this EJB component as a Seam component " -"with the name <literal>authenticator</literal> and Seam will take care of " -"finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</" -"literal> annotation)." +msgid "Assuming your EJB bean class is deployed in an EAR named myapp, the global JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. As you learned, you can reference this EJB component as a Seam component with the name <literal>authenticator</literal> and Seam will take care of finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</literal> annotation)." msgstr "" #. Tag: para #: Configuration.xml:407 #, no-c-format -msgid "" -"So what about the rest of the application servers? Well, according to the " -"Java EE spec, which most vendors try to adhere to religiously, you have to " -"declare an EJB reference for your EJB in order for it to be assigned a JNDI " -"name. That requires some XML. It also means that it is up to you to " -"establish a JNDI naming convention so that you can leverage the Seam JNDI " -"pattern. You might find the JBoss convention a good one to follow." +msgid "So what about the rest of the application servers? Well, according to the Java EE spec, which most vendors try to adhere to religiously, you have to declare an EJB reference for your EJB in order for it to be assigned a JNDI name. That requires some XML. It also means that it is up to you to establish a JNDI naming convention so that you can leverage the Seam JNDI pattern. You might find the JBoss convention a good one to follow." msgstr "" #. Tag: para #: Configuration.xml:413 #, no-c-format -msgid "" -"There are two places you have to define the EJB reference when using Seam on " -"non-JBoss application servers. If you are going to be looking up the Seam " -"EJB component through JSF (in a JSF view or as a JSF action listener) or a " -"Seam JavaBean component, then you must declare the EJB reference in web.xml. " -"Here is the EJB reference for the example component just shown:" +msgid "There are two places you have to define the EJB reference when using Seam on non-JBoss application servers. If you are going to be looking up the Seam EJB component through JSF (in a JSF view or as a JSF action listener) or a Seam JavaBean component, then you must declare the EJB reference in web.xml. Here is the EJB reference for the example component just shown:" msgstr "" #. Tag: programlisting @@ -1101,50 +841,25 @@ #. Tag: para #: Configuration.xml:420 #, no-c-format -msgid "" -"This reference will cover most uses of the component in a Seam application. " -"However, if you want to be able to inject a Seam EJB component into another " -"Seam EJB component using <literal>@In</literal>, you need to define this EJB " -"reference in another location. This time, it must be defined in ejb-jar.xml, " -"and it's a bit tricker." +msgid "This reference will cover most uses of the component in a Seam application. However, if you want to be able to inject a Seam EJB component into another Seam EJB component using <literal>@In</literal>, you need to define this EJB reference in another location. This time, it must be defined in ejb-jar.xml, and it's a bit tricker." msgstr "" #. Tag: para #: Configuration.xml:425 #, no-c-format -msgid "" -"Within the context of an EJB method call, you have to deal with a somewhat " -"sheltered JNDI context. When Seam attempts to find another Seam EJB " -"component to satisfy an injection point defined using <literal>@In</" -"literal>, whether or not it finds it depends on whether an EJB reference " -"exists in JNDI. Strictly speaking, you cannot simply resolve JNDI names as " -"you please. You have to define the references explicitly. Fortunately, JBoss " -"recognized how aggrevating this would be for the developer and all versions " -"of JBoss automatically register EJBs so they are always available in JNDI, " -"both to the web container and the EJB container. So if you are using JBoss, " -"you can skip the next few paragraphs. However, if you are deploying to " -"GlassFish, pay close attention." +msgid "Within the context of an EJB method call, you have to deal with a somewhat sheltered JNDI context. When Seam attempts to find another Seam EJB component to satisfy an injection point defined using <literal>@In</literal>, whether or not it finds it depends on whether an EJB reference exists in JNDI. Strictly speaking, you cannot simply resolve JNDI names as you please. You have to define the references explicitly. Fortunately, JBoss recognized how aggrevating this would be for the developer and all versions of JBoss automatically register EJBs so they are always available in JNDI, both to the web container and the EJB container. So if you are using JBoss, you can skip the next few paragraphs. However, if you are deploying to GlassFish, pay close attention." msgstr "" #. Tag: para #: Configuration.xml:434 #, no-c-format -msgid "" -"For application servers that stubbornly adhere to the EJB specification, EJB " -"references must always be defined explicitly. But unlike with the web " -"context, where a single resource reference covers all uses of the EJB from " -"the web environment, you cannot declare EJB references globally in the EJB " -"container. Instead, you have to specify the JNDI resources for a given EJB " -"component one-by-one." +msgid "For application servers that stubbornly adhere to the EJB specification, EJB references must always be defined explicitly. But unlike with the web context, where a single resource reference covers all uses of the EJB from the web environment, you cannot declare EJB references globally in the EJB container. Instead, you have to specify the JNDI resources for a given EJB component one-by-one." msgstr "" #. Tag: para #: Configuration.xml:439 #, no-c-format -msgid "" -"Let's assume that we have an EJB named RegisterAction (the name is resolved " -"using the three steps mentioned previously). That EJB has the following Seam " -"injection:" +msgid "Let's assume that we have an EJB named RegisterAction (the name is resolved using the three steps mentioned previously). That EJB has the following Seam injection:" msgstr "" #. Tag: programlisting @@ -1162,9 +877,7 @@ #. Tag: para #: Configuration.xml:444 #, no-c-format -msgid "" -"In order for this injection to work, the link must be established in the ejb-" -"jar.xml file as follows:" +msgid "In order for this injection to work, the link must be established in the ejb-jar.xml file as follows:" msgstr "" #. Tag: programlisting @@ -1176,8 +889,7 @@ " <session>\n" " <ejb-name>RegisterAction</ejb-name>\n" " <ejb-local-ref>\n" -" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-" -"name>\n" +" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n" " <ejb-ref-type>Session</ejb-ref-type>\n" " <local>com.example.myapp.Authenticator</local>\n" " </ejb-local-ref>\n" @@ -1194,8 +906,7 @@ " <session>\n" " <ejb-name>RegisterAction</ejb-name>\n" " <ejb-local-ref>\n" -" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-" -"name>\n" +" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n" " <ejb-ref-type>Session</ejb-ref-type>\n" " <local>com.example.myapp.Authenticator</local>\n" " </ejb-local-ref>\n" @@ -1210,66 +921,31 @@ #. Tag: para #: Configuration.xml:448 #, no-c-format -msgid "" -"Notice that the contents of the <literal>&lt;ejb-local-ref&gt;</literal> are " -"identical to what we defined in web.xml. What we are doing is bringing the " -"reference into the EJB context where it can be used by the RegisterAction " -"bean. You will need to add one of these references for any injection of a " -"Seam EJB compoenent into another Seam EJB component using <literal>@In</" -"literal>. (You can see an example of this setup in the jee5/booking example)." +msgid "Notice that the contents of the <literal>&lt;ejb-local-ref&gt;</literal> are identical to what we defined in web.xml. What we are doing is bringing the reference into the EJB context where it can be used by the RegisterAction bean. You will need to add one of these references for any injection of a Seam EJB compoenent into another Seam EJB component using <literal>@In</literal>. (You can see an example of this setup in the jee5/booking example)." msgstr "" #. Tag: para #: Configuration.xml:454 #, no-c-format -msgid "" -"But what about <literal>@EJB</literal>? It's true that you can inject one " -"EJB into another using <literal>@EJB</literal>. However, by doing so, you " -"are injecting the actual EJB reference rather than the Seam EJB component " -"instance. In this case, some Seam features will work, while others won't. " -"That's because Seam's interceptor is invoked on any method call to an EJB " -"component. But that only invokes Seam's server-side interceptor chain. What " -"you lose is Seam's state management and Seam's client-side interceptor " -"chain. Client-side interceptors handle concerns such as security and " -"concurrency. Also, when injecting a SFSB, there is no guarantee that you " -"will get the SFSB bound to the active session or conversation, whatever the " -"case may be. Thus, you definitely want to inject the Seam EJB component " -"using <literal&gt;(a)In&lt;/literal&gt;.&quot; +msgid "But what about <literal>@EJB</literal>? It's true that you can inject one EJB into another using <literal>@EJB</literal>. However, by doing so, you are injecting the actual EJB reference rather than the Seam EJB component instance. In this case, some Seam features will work, while others won't. That's because Seam's interceptor is invoked on any method call to an EJB component. But that only invokes Seam's server-side interceptor chain. What you lose is Seam's state management and Seam's client-side interceptor chain. Client-side interceptors handle concerns such as security and concurrency. Also, when injecting a SFSB, there is no guarantee that you will get the SFSB bound to the active session or conversation, whatever the case may be. Thus, you definitely want to inject the Seam EJB component using <literal&gt;(a)In&lt;/literal&gt;.&quot; msgstr "" #. Tag: para #: Configuration.xml:464 #, no-c-format -msgid "" -"That covers how JNDI names are defined and used. The lesson is that with " -"some application servers, such as GlassFish, you are going to have to " -"specify JNDI names for all EJB components explicitly, and sometimes twice! " -"And even if you are following the same naming convention as JBoss AS, the " -"JNDI pattern in Seam may need to be altered. For instance, the global JNDI " -"names are automatically prefixed with java:comp/env on GlassFish, so you " -"need to define the JNDI pattern as follows:" +msgid "That covers how JNDI names are defined and used. The lesson is that with some application servers, such as GlassFish, you are going to have to specify JNDI names for all EJB components explicitly, and sometimes twice! And even if you are following the same naming convention as JBoss AS, the JNDI pattern in Seam may need to be altered. For instance, the global JNDI names are automatically prefixed with java:comp/env on GlassFish, so you need to define the JNDI pattern as follows:" msgstr "" #. Tag: programlisting #: Configuration.xml:470 #, no-c-format -msgid "" -"<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]" -">" -msgstr "" -"<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]" -">" +msgid "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>" +msgstr "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>" #. Tag: para #: Configuration.xml:472 #, no-c-format -msgid "" -"Finally, let's talk about transactions. 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:" +msgid "Finally, let's talk about transactions. 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 @@ -1287,43 +963,25 @@ #. Tag: para #: Configuration.xml:486 #, 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." +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:491 #, 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." +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:494 #, 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!" +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:497 #, 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." +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 @@ -1335,10 +993,7 @@ #. Tag: para #: Configuration.xml:510 #, 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." +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 @@ -1350,41 +1005,31 @@ #. Tag: para #: Configuration.xml:517 #, 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." +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:524 #, no-c-format -msgid "" -"Telling seam about a different JPA provider can be be done in one of two " -"ways:" +msgid "Telling seam about a different JPA provider can be be done in one of two ways:" msgstr "" #. Tag: para #: Configuration.xml:525 #, 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:" +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:530 #, no-c-format msgid "" -"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider" -"\" \n" +"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n" " class=\"org.jboss.seam.persistence.PersistenceProvider\"\n" " scope=\"stateless\">\n" "</component>]]>" msgstr "" -"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider" -"\" \n" +"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n" " class=\"org.jboss.seam.persistence.PersistenceProvider\"\n" " scope=\"stateless\">\n" "</component>]]>" @@ -1392,37 +1037,25 @@ #. Tag: para #: Configuration.xml:531 #, 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." +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:538 #, no-c-format msgid "" -"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider" -"\" \n" +"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n" " class=\"org.your.package.YourPersistenceProvider\">\n" "</component>]]>" msgstr "" -"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider" -"\" \n" +"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n" " class=\"org.your.package.YourPersistenceProvider\">\n" "</component>]]>" #. Tag: para #: Configuration.xml:539 #, 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." +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 @@ -1434,14 +1067,14 @@ #. Tag: para #: Configuration.xml:558 #, no-c-format -msgid "" -"If you're running in a Java EE 5 environment, this is all the configuration " -"required to start using Seam!" +msgid "If you're running in a Java EE 5 environment, this is all the configuration required to start using Seam!" msgstr "" # come tradurre? #. Tag: title -#: Configuration.xml:561 Configuration.xml:656 Configuration.xml:794 +#: Configuration.xml:561 +#: Configuration.xml:656 +#: Configuration.xml:794 #: Configuration.xml:827 #, no-c-format msgid "Packaging" @@ -1450,9 +1083,7 @@ #. Tag: para #: Configuration.xml:563 #, no-c-format -msgid "" -"Once you've packaged all this stuff together into an EAR, the archive " -"structure will look something like this:" +msgid "Once you've packaged all this stuff together into an EAR, the archive structure will look something like this:" msgstr "" #. Tag: programlisting @@ -1532,65 +1163,43 @@ #. Tag: para #: Configuration.xml:568 #, 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." +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:573 #, no-c-format -msgid "" -"If you want to use jBPM or Drools, you must include the needed jars in the " -"EAR's lib directory." +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:575 #, 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." +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:578 #, 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>." +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:583 #, 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." +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:586 #, no-c-format -msgid "" -"Seam ships with several example applications that are deployable in any Java " -"EE container that supports EJB 3.0." +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:589 #, 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." +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 @@ -1602,35 +1211,19 @@ #. Tag: para #: Configuration.xml:600 #, 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." +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:615 #, 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." +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:621 #, 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." +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 @@ -1642,29 +1235,19 @@ #. Tag: para #: Configuration.xml:628 #, 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:" +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:631 #, no-c-format -msgid "" -"<![CDATA[<persistence:hibernate-session-factory name=" -"\"hibernateSessionFactory\"/>]]>" -msgstr "" -"<![CDATA[<persistence:hibernate-session-factory name=" -"\"hibernateSessionFactory\"/>]]>" +msgid "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>" +msgstr "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>" #. Tag: para #: Configuration.xml:633 #, 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." +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 @@ -1672,12 +1255,10 @@ #, no-c-format msgid "" "<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n" -" session-factory=\"#{hibernateSessionFactory}\"/" -">]]>" +" session-factory=\"#{hibernateSessionFactory}\"/>]]>" msgstr "" "<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n" -" session-factory=\"#{hibernateSessionFactory}\"/" -">]]>" +" session-factory=\"#{hibernateSessionFactory}\"/>]]>" #. Tag: title #: Configuration.xml:641 @@ -1688,29 +1269,19 @@ #. Tag: para #: Configuration.xml:643 #, 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:" +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:646 #, no-c-format -msgid "" -"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/" -">]]>" -msgstr "" -"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/" -">]]>" +msgid "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>" +msgstr "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>" #. Tag: para #: Configuration.xml:648 #, 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." +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 @@ -1718,12 +1289,10 @@ #, no-c-format msgid "" "<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n" -" entity-manager-factory=\"#{entityManagerFactory}" -"\"/>]]>" +" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>" msgstr "" "<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n" -" entity-manager-factory=\"#{entityManagerFactory}" -"\"/>]]>" +" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>" #. Tag: para #: Configuration.xml:658 @@ -1802,9 +1371,7 @@ #. Tag: para #: Configuration.xml:662 #, 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." +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 @@ -1816,37 +1383,26 @@ #. Tag: para #: Configuration.xml:671 #, 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:" +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:675 #, no-c-format -msgid "" -"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/" -">]]>" -msgstr "" -"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/" -">]]>" +msgid "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>" +msgstr "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>" #. Tag: para #: Configuration.xml:677 #, no-c-format -msgid "" -"If you're using Hibernate, you can tell Seam to use the Hibernate " -"transaction API like this:" +msgid "If you're using Hibernate, you can tell Seam to use the Hibernate transaction API like this:" msgstr "" #. Tag: programlisting #: Configuration.xml:679 #, no-c-format msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>" -msgstr "" -"<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>" +msgstr "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>" #. Tag: para #: Configuration.xml:681 @@ -1857,8 +1413,7 @@ #. Tag: para #: Configuration.xml:683 #, no-c-format -msgid "" -"A better alternative is to use JBoss Embedded to get access to the EE APIs." +msgid "A better alternative is to use JBoss Embedded to get access to the EE APIs." msgstr "" #. Tag: title @@ -1870,18 +1425,13 @@ #. Tag: para #: Configuration.xml:690 #, 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." +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:693 #, no-c-format -msgid "" -"The Seam booking example application includes a TestNG integration test " -"suite that runs on JBoss Embedded via <literal>SeamTest</literal>." +msgid "The Seam booking example application includes a TestNG integration test suite that runs on JBoss Embedded via <literal>SeamTest</literal>." msgstr "" #. Tag: para @@ -1899,49 +1449,31 @@ #. Tag: para #: Configuration.xml:720 #, no-c-format -msgid "" -"Embedded JBoss must by installed into Tomcat for Seam applications to run " -"correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend=" -"\"jdk_dependencies\"/> for details on using JDK 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." +msgid "Embedded JBoss must by installed into Tomcat for Seam applications to run correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend=\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=22866&am...;. 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:734 #, 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." +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:741 #, no-c-format -msgid "" -"Remove the <literal>annotations-api.jar</literal> file from the Tomcat " -"<literal>lib</literal> directory." +msgid "Remove the <literal>annotations-api.jar</literal> file from the Tomcat <literal>lib</literal> directory." msgstr "" #. Tag: para #: Configuration.xml:747 #, no-c-format -msgid "" -"Next, two configuration files need to be updated to add Embedded JBoss-" -"specific functionality." +msgid "Next, two configuration files need to be updated to add Embedded JBoss-specific functionality." msgstr "" #. Tag: para #: Configuration.xml:753 #, no-c-format -msgid "" -"Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</" -"literal> to <literal>conf/server.xml</literal>. It must appear after all " -"other listeners in the file:" +msgid "Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</literal> to <literal>conf/server.xml</literal>. It must appear after all other listeners in the file:" msgstr "" #. Tag: programlisting @@ -1950,48 +1482,36 @@ msgid "" "<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n" "\n" -" <!-- Comment these entries out to disable JMX MBeans support used for " -"the \n" +" <!-- Comment these entries out to disable JMX MBeans support used for the \n" " administration web application -->\n" " <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n" -" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener" -"\" />\n" -" <Listener className=\"org.apache.catalina.mbeans." -"GlobalResourcesLifecycleListener\" />\n" -" <Listener className=\"org.apache.catalina.storeconfig." -"StoreConfigLifecycleListener\" />]]>" +" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n" +" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n" +" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>" msgstr "" "<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n" "\n" -" <!-- Comment these entries out to disable JMX MBeans support used for " -"the \n" +" <!-- Comment these entries out to disable JMX MBeans support used for the \n" " administration web application -->\n" " <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n" -" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener" -"\" />\n" -" <Listener className=\"org.apache.catalina.mbeans." -"GlobalResourcesLifecycleListener\" />\n" -" <Listener className=\"org.apache.catalina.storeconfig." -"StoreConfigLifecycleListener\" />]]>" +" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n" +" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n" +" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>" #. Tag: programlisting #: Configuration.xml:757 #, no-c-format msgid "" "<![CDATA[ <!-- Add this listener -->\n" -" <Listener className=\"org.jboss.embedded.tomcat." -"EmbeddedJBossBootstrapListener\" />]]>" +" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>" msgstr "" "<![CDATA[ <!-- Add this listener -->\n" -" <Listener className=\"org.jboss.embedded.tomcat." -"EmbeddedJBossBootstrapListener\" />]]>" +" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>" #. Tag: para #: Configuration.xml:761 #, no-c-format -msgid "" -"WAR file scanning should be enabled by adding the <literal>WebinfScanner</" -"literal> listener to <literal>conf/context.xml</literal>:" +msgid "WAR file scanning should be enabled by adding the <literal>WebinfScanner</literal> listener to <literal>conf/context.xml</literal>:" msgstr "" #. Tag: programlisting @@ -2002,8 +1522,7 @@ " <!-- Default set of monitored resources -->\n" " <WatchedResource>WEB-INF/web.xml</WatchedResource>\n" " \n" -" <!-- Uncomment this to disable session persistence across Tomcat " -"restarts -->\n" +" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n" " <!--\n" " <Manager pathname=\"\" />\n" " -->]]>" @@ -2012,8 +1531,7 @@ " <!-- Default set of monitored resources -->\n" " <WatchedResource>WEB-INF/web.xml</WatchedResource>\n" " \n" -" <!-- Uncomment this to disable session persistence across Tomcat " -"restarts -->\n" +" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n" " <!--\n" " <Manager pathname=\"\" />\n" " -->]]>" @@ -2037,32 +1555,20 @@ #. Tag: para #: Configuration.xml:770 #, no-c-format -msgid "" -"If you are using Sun JDK 6, you need to set the Java option <literal>sun." -"lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in " -"the JAVA_OPTS environment variable used by the Catalina startup script " -"(catalina.bat on Windows or catalina.sh on Unix)." +msgid "If you are using Sun JDK 6, you need to set the Java option <literal>sun.lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in the JAVA_OPTS environment variable used by the Catalina startup script (catalina.bat on Windows or catalina.sh on Unix)." msgstr "" #. Tag: para #: Configuration.xml:775 #, no-c-format -msgid "" -"Open the script appropriate for your operating system in a text editor. Add " -"a new line immediately below the comments at the top of the file where you " -"will define the JAVA_OPTS environment variable. On Windows, use the " -"following syntax:" +msgid "Open the script appropriate for your operating system in a text editor. Add a new line immediately below the comments at the top of the file where you will define the JAVA_OPTS environment variable. On Windows, use the following syntax:" msgstr "" #. Tag: programlisting #: Configuration.xml:779 #, no-c-format -msgid "" -"<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader." -"allowArraySyntax=true]]>" -msgstr "" -"<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader." -"allowArraySyntax=true]]>" +msgid "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>" +msgstr "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>" #. Tag: para #: Configuration.xml:781 @@ -2073,28 +1579,19 @@ #. Tag: programlisting #: Configuration.xml:783 #, no-c-format -msgid "" -"<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true" -"\"]]>" -msgstr "" -"<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true" -"\"]]>" +msgid "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>" +msgstr "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>" #. Tag: para #: Configuration.xml:788 #, 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>." +msgid "For more configuration options, please see the Embedded JBoss Tomcat integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat\&qu... entry</ulink>." msgstr "" #. Tag: para #: Configuration.xml:796 #, no-c-format -msgid "" -"The archive structure of a WAR-based deployment on an servlet engine like " -"Tomcat will look something like this:" +msgid "The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something like this:" msgstr "" #. Tag: programlisting @@ -2170,9 +1667,7 @@ #. Tag: para #: Configuration.xml:801 #, no-c-format -msgid "" -"Most of the Seam example applications may be deployed to Tomcat by running " -"<literal>ant deploy.tomcat</literal>." +msgid "Most of the Seam example applications may be deployed to Tomcat by running <literal>ant deploy.tomcat</literal>." msgstr "" #. Tag: title @@ -2184,11 +1679,7 @@ #. Tag: para #: Configuration.xml:810 #, 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>:" +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 @@ -2220,12 +1711,7 @@ #. Tag: para #: Configuration.xml:816 #, 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:" +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 @@ -2237,22 +1723,17 @@ " <jbpm-context>\n" " <service name=\"persistence\">\n" " <factory>\n" -" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory" -"\">\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=\"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" +" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n" " </jbpm-context>\n" "\n" "</jbpm-configuration>]]>" @@ -2262,22 +1743,17 @@ " <jbpm-context>\n" " <service name=\"persistence\">\n" " <factory>\n" -" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory" -"\">\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=\"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" +" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n" " </jbpm-context>\n" "\n" "</jbpm-configuration>]]>" @@ -2285,20 +1761,13 @@ #. Tag: para #: Configuration.xml:823 #, 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." +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:829 #, 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:" +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 @@ -2398,22 +1867,13 @@ #. Tag: para #: Configuration.xml:843 #, 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)." +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:849 #, 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:" +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 @@ -2421,8 +1881,7 @@ #, no-c-format msgid "" "<![CDATA[<container-cache-conf>\n" -" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-" -"policy>\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" @@ -2441,8 +1900,7 @@ "</container-cache-conf>]]>" msgstr "" "<![CDATA[<container-cache-conf>\n" -" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-" -"policy>\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" @@ -2463,12 +1921,7 @@ #. Tag: para #: Configuration.xml:854 #, 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:" +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 @@ -2488,9 +1941,7 @@ #. Tag: para #: Configuration.xml:861 #, 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>." +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 @@ -2502,12 +1953,7 @@ #. Tag: para #: Configuration.xml:869 #, 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." +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.jbos... for more." msgstr "" #. Tag: title @@ -2519,22 +1965,13 @@ #. Tag: para #: Configuration.xml:882 #, no-c-format -msgid "" -"Seam scans all jars containing <literal>/seam.properties</literal>, " -"<literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam." -"properties</literal> on startup for resources. For example, all classes " -"annotated with <literal>@Name</literal> are registered with Seam as Seam " -"components." +msgid "Seam scans all jars containing <literal>/seam.properties</literal>, <literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam.properties</literal> on startup for resources. For example, all classes annotated with <literal>@Name</literal> are registered with Seam as Seam components." msgstr "" #. Tag: para #: Configuration.xml:889 #, no-c-format -msgid "" -"You may also want Seam to handle custom resources. A common use case is to " -"handle a specific annotation and Seam provides specific support for this. " -"First, tell Seam which annotations to handle in <literal>/META-INF/seam-" -"deployment.properties</literal>:" +msgid "You may also want Seam to handle custom resources. A common use case is to handle a specific annotation and Seam provides specific support for this. First, tell Seam which annotations to handle in <literal>/META-INF/seam-deployment.properties</literal>:" msgstr "" #. Tag: programlisting @@ -2550,9 +1987,7 @@ #. Tag: para #: Configuration.xml:898 #, no-c-format -msgid "" -"Then, during application startup you can get hold of all classes annotated " -"with <literal>@Foo</literal>:" +msgid "Then, during application startup you can get hold of all classes annotated with <literal>@Foo</literal>:" msgstr "" #. Tag: programlisting @@ -2608,10 +2043,7 @@ #. Tag: para #: Configuration.xml:905 #, no-c-format -msgid "" -"You can also handle <emphasis>any</emphasis> resource. For example, you " -"process any files with the extension <literal>.foo.xml</literal>. To do " -"this, we need to write a custom deployment handler:" +msgid "You can also handle <emphasis>any</emphasis> resource. For example, you process any files with the extension <literal>.foo.xml</literal>. To do this, we need to write a custom deployment handler:" msgstr "" #. Tag: programlisting @@ -2659,17 +2091,13 @@ #. Tag: para #: Configuration.xml:913 #, no-c-format -msgid "" -"Here we are just building a list of any files with the suffix <literal>.foo." -"xml</literal>." +msgid "Here we are just building a list of any files with the suffix <literal>.foo.xml</literal>." msgstr "" #. Tag: para #: Configuration.xml:918 #, no-c-format -msgid "" -"Then, we need to register the deployment handler with Seam. In <literal>/" -"META-INF/seam-deployment.properties</literal>:" +msgid "Then, we need to register the deployment handler with Seam. In <literal>/META-INF/seam-deployment.properties</literal>:" msgstr "" #. Tag: programlisting @@ -2679,31 +2107,23 @@ "<![CDATA[# For standard deployment\n" "org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n" "# For hot deployment\n" -"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme." -"FooDeploymentHandler]]>" +"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>" msgstr "" "<![CDATA[# For standard deployment\n" "org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n" "# For hot deployment\n" -"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme." -"FooDeploymentHandler]]>" +"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>" #. Tag: para #: Configuration.xml:925 #, no-c-format -msgid "" -"You can register multiple deployment handler using a comma separated list." +msgid "You can register multiple deployment handler using a comma separated list." msgstr "" #. Tag: para #: Configuration.xml:930 #, no-c-format -msgid "" -"Seam uses deployment handlers internally to install components and " -"namespaces, therefore the <literal>handle()</literal> is called too early in " -"inside Seam bootstrap to normally be useful. However, you can easily access " -"the deployment handler during an <literal>APPLICATION</literal> scoped " -"component's startup:" +msgid "Seam uses deployment handlers internally to install components and namespaces, therefore the <literal>handle()</literal> is called too early in inside Seam bootstrap to normally be useful. However, you can easily access the deployment handler during an <literal>APPLICATION</literal> scoped component's startup:" msgstr "" #. Tag: programlisting @@ -2755,3 +2175,4 @@ " }\n" "\n" "}]]>" +