[seam-commits] Seam SVN: r10424 - trunk/doc/Seam_Reference_Guide/it-IT.

Author: nico.ben Date: 2009-04-15 10:06:05 -0400 (Wed, 15 Apr 2009) New Revision: 10424 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Cache.po trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po trunk/doc/Seam_Reference_Guide/it-IT/Dependencies.po trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po trunk/doc/Seam_Reference_Guide/it-IT/Guice.po trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po trunk/doc/Seam_Reference_Guide/it-IT/Spring.po trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Cache.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Cache.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Cache.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: Cache\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-01-18 15:00+0000\n" -"PO-Revision-Date: 2009-01-18 16:10+0100\n" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" +"PO-Revision-Date: 2009-04-15 15:57+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: Italian <stefano.travelli(a)gmail.com&gt;\n&quot; "MIME-Version: 1.0\n" @@ -102,8 +102,8 @@ #. Tag: term #: Cache.xml:121 #, no-c-format -msgid "JBoss Cache 1.x (suitable for use in JBoss 4.2.x and other containers)" -msgstr "JBoss Cache 1.x (adatto per l'uso in JBoss 4.2.x e altri container)" +msgid "JBoss Cache 1.x (suitable for use in JBoss 4.2.x or later and other containers)" +msgstr "JBoss Cache 1.x (adatto per l'uso in JBoss 4.2.x o successivo e altri container)" #. Tag: literal #: Cache.xml:127 @@ -126,8 +126,8 @@ #. Tag: term #: Cache.xml:143 #, no-c-format -msgid "JBoss POJO Cache 1.x (suitable for use in JBoss 4.2.x and other containers)" -msgstr "JBoss POJO Cache 1.x (adatto per l'uso in JBoss 4.2.x e altri container)" +msgid "JBoss POJO Cache 1.x (suitable for use in JBoss 4.2.x or later and other containers)" +msgstr "JBoss POJO Cache 1.x (adatto per l'uso in JBoss 4.2.x o successivo e altri container)" #. Tag: literal #: Cache.xml:149 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,7 +5,7 @@ msgstr "" "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" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" "PO-Revision-Date: 2009-04-05 17:57+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" @@ -22,8 +22,20 @@ #. 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 @@ -34,8 +46,12 @@ #. 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 @@ -84,8 +100,12 @@ #. 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 @@ -102,14 +122,29 @@ #. 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 @@ -128,8 +163,31 @@ #. 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_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." +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." #. Tag: programlisting #: Configuration.xml:52 @@ -154,8 +212,12 @@ #. 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 @@ -192,8 +254,26 @@ #. 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#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>." +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>." #. Tag: title #: Configuration.xml:81 @@ -204,8 +284,15 @@ #. 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 "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>:" +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 @@ -240,8 +327,19 @@ #. 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 "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>:" +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 @@ -270,37 +368,66 @@ #. 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 "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." +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 "I filtri Seam condividono un numero di attributi comuni, si possono impostare questi in <literal>components.xml</literal> in aggiunto ai parametri discussi sotto:" +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 "<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." +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 "<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." +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 @@ -318,13 +445,24 @@ #. 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 @@ -354,13 +492,18 @@ #. 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 @@ -378,7 +521,11 @@ #. 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 @@ -390,7 +537,10 @@ #. 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 @@ -402,7 +552,11 @@ #. 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 @@ -420,13 +574,21 @@ #. 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 @@ -442,10 +604,11 @@ 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 @@ -469,7 +632,13 @@ #. 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 @@ -481,19 +650,28 @@ #. 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 @@ -513,19 +691,31 @@ #. 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 @@ -537,13 +727,20 @@ #. 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 @@ -569,13 +766,22 @@ #. 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 @@ -587,13 +793,19 @@ #. 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 @@ -605,7 +817,13 @@ #. 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 @@ -629,7 +847,12 @@ #. 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.jboss.seam.web.ajax4jsfFilter\&quot;)&lt;/literal&gt;).&quot; +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>)." msgstr "" #. Tag: title @@ -641,13 +864,24 @@ #. 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 @@ -656,28 +890,32 @@ 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" "]]>" @@ -685,7 +923,15 @@ #. 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 @@ -703,13 +949,20 @@ #. 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 @@ -721,25 +974,36 @@ #. 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 @@ -751,8 +1015,12 @@ #. 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." -msgstr "Guardiamo un esempio. Si assuma di avere definiti il seguente bean EJB ed un'interfaccia." +msgid "" +"Let's look at an example. Assume that you have the following EJB bean and " +"interface defined." +msgstr "" +"Guardiamo un esempio. Si assuma di avere definiti il seguente bean EJB ed " +"un'interfaccia." #. Tag: programlisting #: Configuration.xml:399 @@ -805,19 +1073,36 @@ #. 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 @@ -841,25 +1126,50 @@ #. 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 @@ -877,7 +1187,9 @@ #. 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 @@ -889,7 +1201,8 @@ " <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" @@ -906,7 +1219,8 @@ " <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" @@ -921,31 +1235,66 @@ #. 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 @@ -963,25 +1312,43 @@ #. 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 @@ -993,7 +1360,10 @@ #. 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 @@ -1005,31 +1375,41 @@ #. 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>]]>" @@ -1037,25 +1417,37 @@ #. 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 @@ -1067,14 +1459,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" @@ -1083,7 +1475,9 @@ #. 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 @@ -1163,43 +1557,65 @@ #. 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 @@ -1211,19 +1627,35 @@ #. 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 @@ -1235,19 +1667,29 @@ #. 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 @@ -1255,10 +1697,12 @@ #, 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 @@ -1269,19 +1713,29 @@ #. 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 @@ -1289,10 +1743,12 @@ #, 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 @@ -1371,7 +1827,9 @@ #. 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 @@ -1383,26 +1841,37 @@ #. 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 @@ -1413,7 +1882,8 @@ #. 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 @@ -1425,13 +1895,18 @@ #. 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 @@ -1449,31 +1924,49 @@ #. 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&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." +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." 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 @@ -1482,36 +1975,48 @@ 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 @@ -1522,7 +2027,8 @@ " <!-- 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" " -->]]>" @@ -1531,7 +2037,8 @@ " <!-- 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" " -->]]>" @@ -1555,20 +2062,32 @@ #. 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 @@ -1579,19 +2098,28 @@ #. 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\&qu... 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\">wiki 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 @@ -1667,7 +2195,9 @@ #. 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 @@ -1679,7 +2209,11 @@ #. 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 @@ -1711,7 +2245,12 @@ #. 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 @@ -1723,17 +2262,22 @@ " <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>]]>" @@ -1743,17 +2287,22 @@ " <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>]]>" @@ -1761,13 +2310,20 @@ #. 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 @@ -1867,13 +2423,22 @@ #. 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 @@ -1881,7 +2446,8 @@ #, 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" @@ -1900,7 +2466,8 @@ "</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" @@ -1921,7 +2488,12 @@ #. 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 or later. The following entry in this file controls the default " +"session timeout for all web applications:" msgstr "" #. Tag: programlisting @@ -1941,7 +2513,9 @@ #. 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 @@ -1953,7 +2527,12 @@ #. 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.jbos... 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.jboss.com/portletbridge</ulink> " +"for more." msgstr "" #. Tag: title @@ -1965,13 +2544,22 @@ #. 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 @@ -1987,7 +2575,9 @@ #. 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 @@ -2043,7 +2633,10 @@ #. 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 @@ -2091,13 +2684,17 @@ #. 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 @@ -2107,23 +2704,31 @@ "<![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 @@ -2175,4 +2780,3 @@ " }\n" "\n" "}]]>" - Modified: trunk/doc/Seam_Reference_Guide/it-IT/Dependencies.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Dependencies.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Dependencies.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: JBoss Seam - Italian Version\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-04-07 12:39+0000\n" -"PO-Revision-Date: 2009-04-07 14:46+0100\n" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" +"PO-Revision-Date: 2009-04-15 15:58+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none <nico.benaz(a)gmail.com&gt;\n&quot; "MIME-Version: 1.0\n" @@ -60,8 +60,8 @@ #. Tag: para #: Dependencies.xml:44 #, no-c-format -msgid "This section both lists the compile-time and runtime dependencies for Seam. Where the type is listed as <literal>ear</literal>, the library should be included in the /lib directory of your application's ear file. Where the type is listed as <literal>war</literal>, the library should be placed in the <literal>/WEB-INF/lib</literal> directory of your application's war file. The scope of the dependency is either all, runtime or provided (by JBoss AS 4.2)." -msgstr "Questa sezione elenca le dipendenze di Seam sia a compile-time sia a runtime. Laddove il tipo viene elencato come <literal>ear</literal>, la libreria deve essere inclusa nella directory /lib del proprio ear dell'applicazione. Laddove il tipo viene elencato come <literal>war</literal>, la libreria deve essere collocata nella directory <literal>/WEB-INF/lib</literal> del proprio file war. Lo scope della dipendenze è tutto, runtime o provided (da JBoss AS 4.2)." +msgid "This section both lists the compile-time and runtime dependencies for Seam. Where the type is listed as <literal>ear</literal>, the library should be included in the /lib directory of your application's ear file. Where the type is listed as <literal>war</literal>, the library should be placed in the <literal>/WEB-INF/lib</literal> directory of your application's war file. The scope of the dependency is either all, runtime or provided (by JBoss AS 4.2 or 5.0)." +msgstr "Questa sezione elenca le dipendenze di Seam sia a compile-time sia a runtime. Laddove il tipo viene elencato come <literal>ear</literal>, la libreria deve essere inclusa nella directory /lib del proprio ear dell'applicazione. Laddove il tipo viene elencato come <literal>war</literal>, la libreria deve essere collocata nella directory <literal>/WEB-INF/lib</literal> del proprio file war. Lo scope della dipendenze è tutto, runtime o provided (da JBoss AS 4.2 o 5.0)." #. Tag: para #: Dependencies.xml:54 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: seam 2_0\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-01-18 15:00+0000\n" -"PO-Revision-Date: 2009-02-21 14:57+0100\n" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" +"PO-Revision-Date: 2009-04-15 16:01+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -46,391 +46,394 @@ #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:29 #, no-c-format -msgid "Make sure you have JDK 5, JBoss AS 4.2, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting." -msgstr "Assicurarsi di avere JDK 5, JBoss AS 4.2, Eclipse 3.3, i plugin di JBoss Tool (almeno Seam Tools, Visual Page Editor, jBPM Tools e JBoss AS Tools) ed il plugin TestNG per Eclipse correttamente installati prima di partire." +msgid "Make sure you have JDK 5, JBoss AS 4.2 or 5.0, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting." +msgstr "Assicurarsi di avere JDK 5, JBoss AS 4.2 o 5.0, Eclipse 3.3, i plugin di JBoss Tool (almeno Seam Tools, Visual Page Editor, jBPM Tools e JBoss AS Tools) ed il plugin TestNG per Eclipse correttamente installati prima di partire." #. Tag: para #: Getting_Started_With_JBoss_Tools.xml:36 #, no-c-format -msgid "TODO - detail where the update sites are." -msgstr "TODO - dettaglio su dove si trovano i siti per l'update." +msgid "Please see the official <ulink url=\"http://www.jboss.org/tools/download/installation\">JBoss Tools installation</ulink> page for the quickest way to get JBoss Tools setup in Eclipse. You can also check out the <ulink url=\"http://www.jboss.org/community/wiki/InstallingJBossTools\"... JBoss Tools</ulink> page on the JBoss community wiki for the gory details and a set of alternative installation approaches." +msgstr "Vedere la pagina ufficiale <ulink url=\"http://www.jboss.org/tools/download/installation\">JBoss Tools installation</ulink> per configurare velocemente JBoss Tools in Eclipse. Controllare anche la pagina <ulink url=\"http://www.jboss.org/community/wiki/InstallingJBossTools\"... JBoss Tools</ulink> nella community wiki di JBoss per altri dettagli e per approcci di installazioni alternative." #. Tag: title -#: Getting_Started_With_JBoss_Tools.xml:41 +#: Getting_Started_With_JBoss_Tools.xml:49 #, no-c-format msgid "Setting up a new Seam project" msgstr "Configurare un nuovo progetto Seam" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:43 +#: Getting_Started_With_JBoss_Tools.xml:51 #, no-c-format msgid "Start up Eclipse and select the <emphasis>Seam</emphasis> perspective." msgstr "Avviare Eclipse e selezionare la prospettiva <emphasis>Seam</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:47 +#: Getting_Started_With_JBoss_Tools.xml:55 #, no-c-format msgid "Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Web Project</emphasis>." msgstr "Si vada in <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Web Project</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:63 +#: Getting_Started_With_JBoss_Tools.xml:71 #, no-c-format msgid "First, enter a name for your new project. For this tutorial, we're going to use <literal>helloworld</literal> ." msgstr "Primo, inserire un nome per il nuovo progetto. Per questo tutorial si userà <literal>helloworld</literal> ." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:71 +#: Getting_Started_With_JBoss_Tools.xml:79 #, no-c-format -msgid "Now, we need to tell JBoss Tools about JBoss AS. This is a two stage process, first we need to define a runtime, make sure you select JBoss AS 4.2:" -msgstr "Ora, occorre dire a JBoss Tools dell'esistenza di JBoss AS. Questo è un processo in due fasi, primo occorre definire un runtime, assicurarsi di selezionare JBoss AS 4.2:" +msgid "Now, we need to tell JBoss Tools about JBoss AS. In this example we are using JBoss AS 4.2, though you can certainly use JBoss AS 5.0 as well. Selecting JBoss AS is a two step process. First we need to define a runtime. Again, we'll choose JBoss AS 4.2 in this case:" +msgstr "Ora, occorre dire a JBoss Tools dell'esistenza di JBoss AS. In questo esempio si usa JBoss AS 4.2, anche se è certamente possibile usare anche JBoss AS 5.0. Questo è un processo in due fasi, primo occorre definire un runtime, assicurarsi di selezionare JBoss AS 4.2:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:88 +#: Getting_Started_With_JBoss_Tools.xml:97 #, no-c-format msgid "Enter a name for the runtime, and locate it on your hard drive:" msgstr "Inserire un nome per il runtime, e localizzarlo sul proprio hard disk:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:103 +#: Getting_Started_With_JBoss_Tools.xml:112 #, no-c-format msgid "Next, we need to define a server JBoss Tools can deploy the project to. Make sure to again select JBoss AS 4.2, and also the runtime you just defined:" msgstr "Poi, occorre definire un server in cui JBoss Tools possa fare il deploy. Assicurarsi di selezionare ancora JBoss AS 4.2, ed anche il runtime appena definito:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:118 +#: Getting_Started_With_JBoss_Tools.xml:127 #, no-c-format msgid "On the next screen give the server a name, and hit <emphasis>Finish</emphasis>:" msgstr "Alla successiva schermata si dia un nome al server e si prema <emphasis>Finish</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:134 +#: Getting_Started_With_JBoss_Tools.xml:143 #, no-c-format msgid "Make sure the runtime and server you just created are selected, select <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> and hit <emphasis>Next</emphasis>:" msgstr "Assicurarsi che siano selezionati il runtime ed il server appena creati, selezionare <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> e premere <emphasis>Next</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:151 +#: Getting_Started_With_JBoss_Tools.xml:160 #, no-c-format msgid "The next 3 screens allow you to further customize your new project, but for us the defaults are fine. So just hit <emphasis>Next</emphasis> until you reach the final screen." msgstr "Le prossime 3 schermate consentono di personalizzare ulteriormente il proprio progetto, ma per noi i valori di default vanno bene. Si prema <emphasis>Next</emphasis> fino ad arrivare alla schermata finale." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:157 +#: Getting_Started_With_JBoss_Tools.xml:166 #, no-c-format msgid "The first step here is to tell JBoss Tools about the Seam download you want to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - make sure to give it a name, and select <emphasis>2.0</emphasis> as the version:" msgstr "Il primo passo è dire a JBoss Tools quale download di Seam si vuole usare. <emphasis>Aggiungere</emphasis> un nuovo <emphasis>Seam Runtime</emphasis> - assicurarsi di dare un nome, e selezionare <emphasis>2.0</emphasis> come versione:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:175 +#: Getting_Started_With_JBoss_Tools.xml:184 #, no-c-format msgid "The most important choice you need to make is between EAR deployment and WAR deployment of your project. EAR projects support EJB 3.0 and require Java EE 5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE environment. The packaging of a WAR is also simpler to understand. If you installed an EJB3-ready application server like JBoss, choose <emphasis>EAR</emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that you've chosen a WAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a EAR deployment." msgstr "La scelta più importante da fare è tra deploy EAR e deploy WAR del proprio progetto. I progetti EAR supportano EJB 3.0 e richiede Java EE 5. I progetti WAR non supportano EJB 3.0, ma possono essere deployati in ambiente J2EE. Anche l'impacchettamento di un WAR è semplice da capire. Se si è installato un application server pronto per EJB3 come JBoss, si scelga <emphasis>EAR</emphasis>. Altrimenti, si scelga <emphasis>WAR</emphasis>. Assumeremo per il resto del tutorial che si sia scelto il deploy WAR, ma si possono seguire gli stessi passi per un deploy EAR." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:187 +#: Getting_Started_With_JBoss_Tools.xml:196 #, no-c-format msgid "Next, select your database type. We'll assume you have MySQL installed, with an existing schema. You'll need to tell JBoss Tools about the database, select <emphasis>MySQL</emphasis> as the database, and create a new connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:" msgstr "Poi, si selezioni il tipo di database. Assumeremo di avere installato MySQL, con uno schema esistente. Occorrerà dire a JBoss Tools del database, selezionare <emphasis>MySQL</emphasis> come database, e creare un nuovo profilo di connessione. Selezionare <emphasis>Generic JDBC Connection</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:206 +#: Getting_Started_With_JBoss_Tools.xml:215 #, no-c-format msgid "Give it a name:" msgstr "Si metta un nome:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:221 +#: Getting_Started_With_JBoss_Tools.xml:230 #, no-c-format msgid "JBoss Tools doesn't come with drivers for any databases, so you need to tell JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by clicking <emphasis>...</emphasis>." msgstr "JBoss Tools non è fornito assieme ai driver dei database, quindi occorre specificare dove è collocato il driver MySQL JDBC. Si prema il pulsante <emphasis>...</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:227 +#: Getting_Started_With_JBoss_Tools.xml:236 #, no-c-format msgid "Locate MySQL 5, and hit <emphasis>Add...</emphasis>:" msgstr "Trovare MySQL 5 e premere <emphasis>Add...</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:242 +#: Getting_Started_With_JBoss_Tools.xml:251 #, no-c-format msgid "Choose the <emphasis>MySQL JDBC Driver</emphasis> template:" msgstr "Scegliere il template <emphasis>MySQL JDBC Driver</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:257 +#: Getting_Started_With_JBoss_Tools.xml:266 #, no-c-format msgid "Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</emphasis>:" msgstr "Trovare il jar sul proprio computer scegliendo <emphasis>Edit Jar/Zip</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:273 +#: Getting_Started_With_JBoss_Tools.xml:282 #, no-c-format msgid "Review the username and password used to connect, and if correct, hit <emphasis>Ok</emphasis>." msgstr "Riguardare lo username e la password usate per la connessione, e se corretti, premere <emphasis>Ok</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:278 +#: Getting_Started_With_JBoss_Tools.xml:287 #, no-c-format msgid "Finally, choose the newly created driver:" msgstr "Infine scegliere il driver appena creato: " #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:293 +#: Getting_Started_With_JBoss_Tools.xml:302 #, no-c-format msgid "If you are working with an existing data model, make sure you tell JBoss Tools that the tables already exist in the database." msgstr "Se si sta lavorando con un modello di dati esistenti, assicurarsi di segnalare a JBoss Tools che le tabelle esistono già nel database." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:298 +#: Getting_Started_With_JBoss_Tools.xml:307 #, no-c-format msgid "Review the username and password used to connect, test the connection using the <emphasis>Test Connection</emphasis> button, and if it works, hit <emphasis>Finish</emphasis>:" msgstr "Riguardare lo username e la password usate per la connessione, testare la connessione usando il pulsante <emphasis>Test Connection</emphasis>, e se funzionante, premere <emphasis>Finish</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:304 +#: Getting_Started_With_JBoss_Tools.xml:313 #, no-c-format msgid "Finally, review the package names for your generated beans, and if you are happy, click <emphasis>Finish</emphasis>:" msgstr "Infine, rivedere i nomi dei pacchetti per i bean generati, e se si è soddisfatti, cliccare su <emphasis>Finish</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:320 +#: Getting_Started_With_JBoss_Tools.xml:329 #, no-c-format msgid "JBoss has sophisticated support for hot re-deployment of WARs and EARs. Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which is common during development—eventually causes the JVM to run out of perm gen space. For this reason, we recommend running JBoss in a JVM with a large perm gen space at development time. We suggest the following values:" msgstr "JBoss ha un supporto molto sofisticato per il redeploy a caldo (hot deploy) di WAR e EAR. Sfortunatamente, a causa di alcuni bug nella JVM, ripetuti redeploy di un EAR - comuni durante lo sviluppo - possono portare eventualmente ad errori di perm gen space nella JVM. Per questa ragione, raccomandiamo di eseguire JBoss in fase di sviluppo dentro una JVM con un ampio perm gen space. Suggeriamo i seguenti valori:" #. Tag: programlisting -#: Getting_Started_With_JBoss_Tools.xml:329 +#: Getting_Started_With_JBoss_Tools.xml:338 #, no-c-format msgid "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512" msgstr "-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:331 +#: Getting_Started_With_JBoss_Tools.xml:340 #, no-c-format msgid "If you don't have so much memory available, the following is our minimum recommendation:" msgstr "Se la memoria disponibile è poca, questa è la quantità minima suggerita:" #. Tag: programlisting -#: Getting_Started_With_JBoss_Tools.xml:336 +#: Getting_Started_With_JBoss_Tools.xml:345 #, no-c-format msgid "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256" msgstr "-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:338 +#: Getting_Started_With_JBoss_Tools.xml:347 #, no-c-format msgid "Locate the server in the <emphasis>JBoss Server View</emphasis>, right click on the server and select <emphasis>Edit Launch Configuration</emphasis>:" msgstr "Trovare il server in <emphasis>JBoss Server View</emphasis>, cliccare col tasto destro sul server e selezionare <emphasis>Edit Launch Configuration</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:355 +#: Getting_Started_With_JBoss_Tools.xml:364 #, no-c-format msgid "Then, alter the VM arguements:" msgstr "Poi si cambino gli argomenti VM:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:370 +#: Getting_Started_With_JBoss_Tools.xml:379 #, no-c-format msgid "If you don't want to bother with this stuff now, you don't have to—come back to it later, when you get your first <literal>OutOfMemoryException</literal>." msgstr "Se non si vuole avere a che fare con queste configurazioni, non occorre farlo - si ritorni in questa sezione quando si vedrà la prima <literal>OutOfMemoryException</literal>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:376 +#: Getting_Started_With_JBoss_Tools.xml:385 #, no-c-format msgid "To start JBoss, and deploy the project, just right click on the server you created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</emphasis> to start in debug mode):" msgstr "Per avviare JBoss, e fare il deploy del progetto, cliccare col destro sul server creato e cliccare quindi <emphasis>Start</emphasis>, (o <emphasis>Debug</emphasis> per avviare in modalità Debug):" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:393 +#: Getting_Started_With_JBoss_Tools.xml:402 #, no-c-format msgid "Don't get scared by the XML configuration documents that were generated into the project directory. They are mostly standard Java EE stuff, the stuff you need to create once and then never look at again, and they are 90% the same between all Seam projects." msgstr "Non si abbia paura dei documenti di configurazione in XML che sono stati creati nella directory di progetto. La maggior parte riguardano Java EE, e sono creati la prima volta e poi non vengono più toccati. Al 90% sono sempre gli stessi nei vari progetti Seam." #. Tag: title -#: Getting_Started_With_JBoss_Tools.xml:403 +#: Getting_Started_With_JBoss_Tools.xml:412 #, no-c-format msgid "Creating a new action" msgstr "Creazione di una nuova azione" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:405 +#: Getting_Started_With_JBoss_Tools.xml:414 #, no-c-format msgid "If you're used to traditional action-style web frameworks, you're probably wondering how you can create a simple web page with a stateless action method in Java." msgstr "Se si è abituati ai tradizionali framework web action-style, probabilmente ci si sta domandando come si crea una semplice pagina web con un metodo d'azione stateless in Java." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:411 +#: Getting_Started_With_JBoss_Tools.xml:420 #, no-c-format msgid "First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:" msgstr "Innanzitutto selezionare <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:426 -#: Getting_Started_With_JBoss_Tools.xml:492 +#: Getting_Started_With_JBoss_Tools.xml:435 +#: Getting_Started_With_JBoss_Tools.xml:501 #, no-c-format msgid "Now, enter the name of the Seam component. JBoss Tools selects sensible defaults for other fields:" msgstr "Ora, si inserisca il nome del componente Seam. JBoss Tools seleziona i valori di default sensibili per gli altri campi:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:442 +#: Getting_Started_With_JBoss_Tools.xml:451 #, no-c-format msgid "Finally, hit <emphasis>Finish</emphasis>." msgstr "Infine di prema <emphasis>Finish</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:446 +#: Getting_Started_With_JBoss_Tools.xml:455 #, no-c-format msgid "Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and click the button. You can see the code behind this action by looking in the project <literal>src</literal> directory. Put a breakpoint in the <literal>ping()</literal> method, and click the button again." msgstr "Ora si vada in <literal>http://localhost:8080/helloworld/ping.seam</literal> e si clicchi il pulsante. Si può vedere il codice dietro l'azione guardando nel progetto alla directory <literal>src</literal>. Si metta un breakpoint nel metodo <literal>ping()</literal>, e si clicchi di nuovo il pulsante." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:454 +#: Getting_Started_With_JBoss_Tools.xml:463 #, no-c-format msgid "Finally, open the <literal>helloworld-test</literal> project, locate <literal>PingTest</literal> class, right click on it, and choose <emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:" msgstr "Infine, si apra il progetto <literal>helloworld-test</literal>, si cerchi la classe <literal>PingTest</literal>, si clicchi su di essa col tasto destro e si scelga <emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:" #. Tag: title -#: Getting_Started_With_JBoss_Tools.xml:474 +#: Getting_Started_With_JBoss_Tools.xml:483 #, no-c-format msgid "Creating a form with an action" msgstr "Creazione di una form con un'azione" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:476 +#: Getting_Started_With_JBoss_Tools.xml:485 #, no-c-format msgid "The first step is to create a form. Select <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>:" msgstr "Il primo passo è creare una form. Selezionare <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:508 +#: Getting_Started_With_JBoss_Tools.xml:517 #, no-c-format msgid "Go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then take a look at the generated code. Run the test. Try adding some new fields to the form and Seam component (note, you don't need to restart the app server each time you change the code in <literal>src/action</literal> as Seam hot reloads the component for you <xref linkend=\"gettingstartedwithjbosstools.hotdeployment\"/>)." msgstr "Si vada in <literal>http://localhost:8080/helloworld/hello.seam</literal>. Quindi si guardi il codice generato. Si esegua il test. Provare ad aggiungere alcuni nuovi campi nella form e nel componente Seam (si noti che non serve riavviare l'application server ogni volta che cambia il codice in <literal>src/action</literal> poiché Seam ricarica a caldo il componente per voi, vedere <xref linkend=\"gettingstartedwithjbosstools.hotdeployment\"/>)." #. Tag: title -#: Getting_Started_With_JBoss_Tools.xml:519 +#: Getting_Started_With_JBoss_Tools.xml:528 #, no-c-format msgid "Generating an application from an existing database" msgstr "Generare un'applicazione da un database esistente" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:521 +#: Getting_Started_With_JBoss_Tools.xml:530 #, no-c-format msgid "Manually create some tables in your database. (If you need to switch to a different database, create a new project, and select the correct database). Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>:" msgstr "Si creino manualmente alcune tabelle nel database. (Se serve passare ad un database differente, si crei un nuovo progetto e si selezioni il database corretto). Poi, selezionare <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:539 +#: Getting_Started_With_JBoss_Tools.xml:548 #, no-c-format msgid "JBoss Tools gives you the option to either reverse engineer entities, components and views from a database schema or to reverse engineer components and views from existing JPA entities. We're going to do <emphasis>Reverse engieneer from database</emphasis>." msgstr "JBoss Tools fornisce l'opzione per eseguire il reverse engineering di entità, componenti, e viste da uno schema di database o da entità JPA esistenti. Ora eseguiremo un <emphasis>Reverse engineering da database</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:546 +#: Getting_Started_With_JBoss_Tools.xml:555 #, no-c-format msgid "Restart the deployment:" msgstr "Riavviare il deploy:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:561 +#: Getting_Started_With_JBoss_Tools.xml:570 #, no-c-format msgid "Then go to <literal>http://localhost:8080/helloworld</literal>. You can browse the database, edit existing objects, and create new objects. If you look at the generated code, you'll probably be amazed how simple it is! Seam was designed so that data access code is easy to write by hand, even for people who don't want to cheat by using reverse engineering." msgstr "Andare in <literal>http://localhost:8080/helloworld</literal>. Si può sfogliare il database, modificare gli oggetti e creane di nuovi. Se si guarda il codice generato, probabilmente ci si meraviglierà della sua semplicità! Seam è stato progettato per rendere semplice la scrittura del codice, anche per persone che non vogliono imbrogliare usando il reverse engineering." #. Tag: title -#: Getting_Started_With_JBoss_Tools.xml:572 +#: Getting_Started_With_JBoss_Tools.xml:581 #, no-c-format msgid "Seam and incremental hot deployment with JBoss Tools" msgstr "Seam ed l'hot deploy incrementale con JBoss Tools" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:574 +#: Getting_Started_With_JBoss_Tools.xml:583 #, no-c-format msgid "JBoss Tools supports incremental hot deployment of:" msgstr "JBoss Tools supporta il deploy a caldo incrementale di:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:580 +#: Getting_Started_With_JBoss_Tools.xml:589 #, no-c-format msgid "any facelets page" msgstr "qualsiasi pagina facelets" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:584 +#: Getting_Started_With_JBoss_Tools.xml:593 #, no-c-format msgid "any <literal>pages.xml</literal> file" msgstr "qualsiasi file <literal>pages.xml</literal>" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:590 +#: Getting_Started_With_JBoss_Tools.xml:599 #, no-c-format msgid "out of the box." msgstr "out of the box." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:594 +#: Getting_Started_With_JBoss_Tools.xml:603 #, no-c-format msgid "But if we want to change any Java code, we still need to do a full restart of the application by doing a <emphasis>Full Publish</emphasis>." msgstr "Ma se si volesse cambiare il codice Java, servirebbe eseguire un riavvio completo dell'applicazione facendo un <emphasis>Full Publish</emphasis>." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:600 +#: Getting_Started_With_JBoss_Tools.xml:609 #, no-c-format msgid "But if you really want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean components. To make use of this functionality, you must deploy the JavaBean components into the <literal>WEB-INF/dev</literal> directory, so that they will be loaded by a special Seam classloader, instead of by the WAR or EAR classloader." msgstr "Ma sesi vuole veramente un ciclo veloce modifica/compila/testa, Seam supporta il redeploy incrementale dei componenti JavaBean. Per usare questa funzionalità, occorre fare il deploy dei componenti JavaBean nella directory <literal>WEB-INF/dev</literal>, affinché vengano caricati da uno speciale classloader di Seam, anziché dal classloader dei WAR e EAR." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:609 +#: Getting_Started_With_JBoss_Tools.xml:618 #, no-c-format msgid "You need to be aware of the following limitations:" msgstr "Occorre essere consapevoli delle seguenti limitazioni:" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:613 +#: Getting_Started_With_JBoss_Tools.xml:622 #, no-c-format msgid "the components must be JavaBean components, they cannot be EJB3 beans (we are working on fixing this limitation)" msgstr "i componenti devono essere componenti JavaBean, non possono essere EJB3 (stiamo lavorando per risolvere questa limitazione)" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:620 +#: Getting_Started_With_JBoss_Tools.xml:629 #, no-c-format msgid "entities can never be hot-deloyed" msgstr "gli entity non possono mai essere deployati a caldo" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:626 +#: Getting_Started_With_JBoss_Tools.xml:635 #, no-c-format msgid "components deployed via <literal>components.xml</literal> may not be hot-deployed" msgstr "i componenti deployati via <literal>components.xml</literal> non possono essere deployati a caldo" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:633 +#: Getting_Started_With_JBoss_Tools.xml:642 #, no-c-format msgid "the hot-deployable components will not be visible to any classes deployed outside of <literal>WEB-INF/dev</literal>" msgstr "i componenti hot-deployabili non saranno visibili alle classi deployate fuori da <literal>WEB-INF/dev</literal>" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:640 +#: Getting_Started_With_JBoss_Tools.xml:649 #, no-c-format msgid "Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> must be in <literal>WEB-INF/lib</literal>" msgstr "La modalità debug di Seam deve essere abilitata e <literal>jboss-seam-debug.jar</literal> deve essere in <literal>WEB-INF/lib</literal>" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:648 +#: Getting_Started_With_JBoss_Tools.xml:657 #, no-c-format msgid "You must have the Seam filter installed in web.xml" msgstr "Occorre avere il filtro Seam installato in web.xml" #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:654 +#: Getting_Started_With_JBoss_Tools.xml:663 #, no-c-format msgid "You may see errors if the system is placed under any load and debug is enabled." msgstr "Si potrebbero vedere errori se il sistema è sotto carico ed è abilitato il debug." #. Tag: para -#: Getting_Started_With_JBoss_Tools.xml:662 +#: Getting_Started_With_JBoss_Tools.xml:671 #, no-c-format msgid "If you create a WAR project using JBoss Tools, incremental hot deployment is available out of the box for classes in the <literal>src/action</literal> source directory. However, JBoss Tools does not support incremental hot deployment for EAR projects." msgstr "Sesi crea un progetto WAR usando JBoss Tools, l'hot deploy incrementale è disponibile di default per le classi contenute nella directory sorgente <literal>src/action</literal>. Comunque, JBoss Tools non supporta il deploy incrementale a caldo per progetti EAR." +#~ msgid "TODO - detail where the update sites are." +#~ msgstr "TODO - dettaglio su dove si trovano i siti per l'update." + Modified: trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-11-06 00:23+0000\n" -"PO-Revision-Date: 2009-04-07 15:28+0100\n" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" +"PO-Revision-Date: 2009-04-15 16:03+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -46,8 +46,8 @@ #. Tag: para #: Gettingstarted.xml:21 #, no-c-format -msgid "Seam-gen is basically just a big ugly Ant script wrapped around Hibernate Tools, together with some templates. That makes it easy to customize if you need to." -msgstr "Seam-gen è essenzialmente uno script Ant avvolto attorno a Hibernate Tools, assieme a qualche template. Questo facilita la sua personalizzazione nel caso ce ne sia bisogno." +msgid "seam-gen is basically just an intricate Ant script wrapped around Hibernate Tools, together with some templates. That makes it easy to customize if you need to." +msgstr "Seam-gen è essenzialmente uno script Ant avvolto attorno a Hibernate Tools, assieme a qualche template. Questo facilita la sua personalizzazione in caso di bisogno." #. Tag: title #: Gettingstarted.xml:25 @@ -58,8 +58,8 @@ #. Tag: para #: Gettingstarted.xml:27 #, no-c-format -msgid "Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> for details), JBoss AS 4.2 and Ant 1.6, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before starting. Add your JBoss installation to the JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution." -msgstr "Assicurarsi di avere JDK 5 o JDK 6 (vedere <xref linkend=\"jdk_dependencies\"/> per maggiori dettagli), JBoss AS 4.2 e Ant 1.6, con una versione recente di Eclipse, il plugin JBoss IDE di Eclipse ed il plugin TestNG per Eclipse correttamente installati prima di avviare. Aggiungere l'installazione di JBoss alla vista di JBoss Server in Eclipse. Avviare JBoss in modalità debug. Infine, avviare da comando all'interno della directory dove si è scompattato la distribuzione Seam." +msgid "Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> for details), JBoss AS 4.2 or 5.0 and Ant 1.7.0, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before starting. Add your JBoss installation to the JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution." +msgstr "Assicurarsi di avere JDK 5 o JDK 6 (vedere <xref linkend=\"jdk_dependencies\"/> per maggiori dettagli), JBoss AS 4.2 o 5.0 e Ant 1.7.0, con una versione recente di Eclipse, il plugin JBoss IDE di Eclipse ed il plugin TestNG per Eclipse correttamente installati prima di avviare. Aggiungere l'installazione di JBoss alla vista di JBoss Server in Eclipse. Avviare JBoss in modalità debug. Infine, avviare da comando all'interno della directory dove si è scompattato la distribuzione Seam." #. Tag: para #: Gettingstarted.xml:33 @@ -100,14 +100,14 @@ #. Tag: title #: Gettingstarted.xml:53 #, no-c-format -msgid "Setting up a new Eclipse project" -msgstr "Comfigurare un nuovo progetto Eclipse" +msgid "Setting up a new project" +msgstr "Comfigurare un nuovo progetto" #. Tag: para #: Gettingstarted.xml:55 #, no-c-format -msgid "The first thing we need to do is configure seam-gen for your environment: JBoss AS installation directory, Eclipse workspace, and database connection. It's easy, just type:" -msgstr "La prima cosa da fare è configurare seam-gen per il proprio ambiente: la directory di installazione JBoss AS, il workspace di Eclipse, e la connessione del database. E' facile, si digiti:" +msgid "The first thing we need to do is configure seam-gen for your environment: JBoss AS installation directory, project workspace, and database connection. It's easy, just type:" +msgstr "La prima cosa da fare è configurare seam-gen per il proprio ambiente: la directory di installazione JBoss AS, il workspace, e la connessione del database. E' facile, si digiti:" #. Tag: programlisting #: Gettingstarted.xml:58 @@ -136,10 +136,10 @@ "\n" "setup:\n" " [echo] Welcome to seam-gen :-)\n" -" [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n" +" [input] Enter your project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n" "/Users/pmuir/workspace\n" -" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2.GA] [C:/Program Files/jboss-4.2.2.GA]\n" -"/Applications/jboss-4.2.2.GA\n" +" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA]\n" +"/Applications/jboss-4.2.3.GA\n" " [input] Enter the project name [myproject] [myproject]\n" "helloworld\n" " [echo] Accepted project name as: helloworld\n" @@ -191,10 +191,10 @@ "\n" "setup:\n" " [echo] Welcome to seam-gen :-)\n" -" [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n" +" [input] Enter your project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n" "/Users/pmuir/workspace\n" -" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2.GA] [C:/Program Files/jboss-4.2.2.GA]\n" -"/Applications/jboss-4.2.2.GA\n" +" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA]\n" +"/Applications/jboss-4.2.3.GA\n" " [input] Enter the project name [myproject] [myproject]\n" "helloworld\n" " [echo] Accepted project name as: helloworld\n" @@ -330,7 +330,7 @@ #. Tag: para #: Gettingstarted.xml:98 #, no-c-format -msgid "Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome page. This is a facelets page, <literal>view/home.xhtml</literal>, using the template <literal>view/layout/template.xhtml</literal>. You can edit this page, or the template, in eclipse, and see the results <emphasis>immediately</emphasis>, by clicking refresh in your browser." +msgid "Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome page. This is a facelets page, <literal>view/home.xhtml</literal>, using the template <literal>view/layout/template.xhtml</literal>. You can edit this page, or the template, in Eclipse, and see the results <emphasis>immediately</emphasis>, by clicking refresh in your browser." msgstr "Si vada in <literal>http://localhost:8080/helloworld</literal> per vedere la pagina di benvenuto. Questa è una pagina facelets, <literal>view/home.xhtml</literal>, che utilizza il template <literal>view/layout/template.xhtml</literal>. In Eclipse si può modificare questa pagina, oppure il template, e vedere <emphasis>immediatamente</emphasis> i risultati, cliccando il pulsante aggiorna del browser." #. Tag: para @@ -745,8 +745,8 @@ #. Tag: para #: Gettingstarted.xml:282 #, no-c-format -msgid "Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss AS, we recommend using JBoss 4.2, which bundles the JSF 1.2 reference implementation. However, it is still possible to use Seam 2.0 on the JBoss 4.0 platform. There are two basic steps required to do this: install an EJB3-enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference implementation. Once you complete these steps, Seam 2.0 applications can be deployed to JBoss 4.0." -msgstr "Seam 2.0 è stato sviluppato per JavaServer Faces 1.2. Usando JBoss AS, si raccomanda di usare JBoss 4.2, che incorpora l'implementazione di riferimento JSF 1.2. Comunque è possibile usare Seam 2.0 su piattaforma JBoss 4.0. Ci sono due passi base richiesti per farlo: installare la versione JBoss 4.0 con EJB3 abilitato e sostituire MyFaces con l'implementazione di riferimento JSF 1.2. Una volta completati questi passi, le applicazioni Seam 2.0 possono essere deployate in JBoss 4.0." +msgid "Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss AS, we recommend using JBoss 4.2 or JBoss 5.0, both of which bundle the JSF 1.2 reference implementation. However, it is still possible to use Seam 2.0 on the JBoss 4.0 platform. There are two basic steps required to do this: install an EJB3-enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference implementation. Once you complete these steps, Seam 2.0 applications can be deployed to JBoss 4.0." +msgstr "Seam 2.0 è stato sviluppato per JavaServer Faces 1.2. Usando JBoss AS, si raccomanda di usare JBoss 4.2 o JBoss 5.0, che incorpora l'implementazione di riferimento JSF 1.2. Comunque è possibile usare Seam 2.0 su piattaforma JBoss 4.0. Ci sono due passi base richiesti per farlo: installare la versione JBoss 4.0 con EJB3 abilitato e sostituire MyFaces con l'implementazione di riferimento JSF 1.2. Una volta completati questi passi, le applicazioni Seam 2.0 possono essere deployate in JBoss 4.0." #. Tag: title #: Gettingstarted.xml:289 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Guice.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Guice.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Guice.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -1,36 +1,48 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2009-04-12 01:20-0400\n" -"PO-Revision-Date: 2009-04-14 07:05+0100\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" +"PO-Revision-Date: 2009-04-15 16:03+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: LANGUAGE <LL(a)li.org&gt;\n&quot; "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:6(title) +#. Tag: title +#: Guice.xml:6 +#, no-c-format msgid "Guice integration" msgstr "Integrazione con Guice" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:8(para) +#. Tag: para +#: Guice.xml:8 +#, no-c-format msgid "Google Guice is a library that provides lightweight dependency injection through type-safe resolution. The Guice integration (part of the Seam IoC module) allows use of Guice injection for all Seam components annotated with the <literal>@Guice</literal> annotation. In addition to the regular bijection that Seam performs (which becomes optional), Seam also delegates to known Guice injectors to satisify the dependencies of the component. Guice may be useful to tie non-Seam parts of large or legacy applications together with Seam." msgstr "Google Guice è una libreria che fornisce una dependency injection leggera attraverso la risoluzione type-safe. L'integrazione con Guice (parte del modulo Seam IoC) consente l'uso dell'iniezione Guice per tutti i componenti Seam annotati con l'annotazione <literal>@Guice</literal>. In aggiunta alla regolare bijection, fornita da Seam (che diviene opzionale), Seam delega agli injector Guice noti di soddisfare le dipendenze del componente. Guice può essere utile per legare parti non-Seam di applicazione grosse o legacy assieme a Seam." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:17(note) +#. Tag: note +#: Guice.xml:17 +#, no-c-format msgid "The Guice integration is bundled in the jboss-seam-ioc library. This dependency is required for all integration techniques covered in this chapter. You will also need the Guice JAR file on the classpath." msgstr "L'integrazione Guice è messa nella libreria jboss-seam-ioc. Questa dipendenza è richiesta per tutte le tecniche di integrazione coperta in questo capitolo. Occorre anche il file JAR Guice nel classpath." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:24(title) +#. Tag: title +#: Guice.xml:24 +#, no-c-format msgid "Creating a hybrid Seam-Guice component" msgstr "Creazione di un componente ibrido Seam-Guice" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:26(para) +#. Tag: para +#: Guice.xml:26 +#, no-c-format msgid "The goal is to create a hybrid Seam-Guice component. The rule for how to do this is very simple. If you want to use Guice injection in your Seam component, annotate it with the <literal>@Guice</literal> annotation (after importing the type <literal>org.jboss.seam.ioc.guice.Guice</literal>)." msgstr "L'obiettivo è creare un componente ibrido Seam-Guice. La regola per come realizzare ciò è molto semplice. Se si vuole usare l'injection Guice nel proprio componente Seam, annotarlo con l'annotazione <literal>@Guice</literal> (dopo l'importazione del tipo <literal>org.jboss.seam.ioc.guice.Guice</literal>)." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:33(programlisting) -#, no-wrap +#. Tag: programlisting +#: Guice.xml:33 +#, no-c-format msgid "" "@Name(\"myGuicyComponent\")\n" "@Guice public class MyGuicyComponent\n" @@ -48,12 +60,15 @@ " ...\n" "}" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:41(para) +#. Tag: para +#: Guice.xml:35 +#, no-c-format msgid "This Guice injection will happen on every method call, just like with bijection. Guice injects based on type and binding. To satisify the dependencies in the previous example, you might have bound the following implementations in a Guice module, where <literal>@Special</literal> is an annotation you define in your application." msgstr "Quest'iniezione Guice avverrà ad ogni chiamata di metodo, come con la bijection. Guice inietta in base a tipo e binding. Per soddisfare le dipendenze nel precedente esempio, si possono associare le seguenti implementazioni in un modulo Guice, dove <literal>@Special</literal> è un'annotazione definita nella propria applicazione." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:48(programlisting) -#, no-wrap +#. Tag: programlisting +#: Guice.xml:42 +#, no-c-format msgid "" "public class MyGuicyModule implements Module\n" "{\n" @@ -79,32 +94,93 @@ " }\n" "}" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:60(para) +#. Tag: para +#: Guice.xml:44 +#, no-c-format msgid "Great, but which Guice injector will be used to inject the dependencies? Well, you need to perform some setup first." msgstr "Bene, ma quanle injector Guice verrà usato per iniettare le dipendenze? Occorre fare prima qualche settaggio." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:69(title) +#. Tag: title +#: Guice.xml:53 +#, no-c-format msgid "Configuring an injector" msgstr "Configurare un injector" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:71(para) +#. Tag: para +#: Guice.xml:55 +#, no-c-format msgid "You tell Seam which Guice injector to use by hooking it into the injection property of the Guice initization component in the Seam component descriptor (components.xml):" msgstr "Dire a Seam quale injector Guice usare agganciandolo alla proprietà injection del componente Guice di inizializzazione nel descrittore del componente Seam (components.xml):" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:89(para) +#. Tag: programlisting +#: Guice.xml:60 +#, no-c-format +msgid "" +"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xmlns:guice=\"http://jboss.org/products/seam/guice\"\n" +" xsi:schemaLocation=\"\n" +" http://jboss.com/products/seam/guice\n" +" http://jboss.com/products/seam/guice-2.1.xsd\n" +" http://jboss.com/products/seam/components\n" +" http://jboss.com/products/seam/components-2.1.xsd\">\n" +"\n" +" <guice:init injector=\"#{myGuiceInjector}\"/>\n" +"\n" +"</components>]]>" +msgstr "" +"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xmlns:guice=\"http://jboss.org/products/seam/guice\"\n" +" xsi:schemaLocation=\"\n" +" http://jboss.com/products/seam/guice\n" +" http://jboss.com/products/seam/guice-2.1.xsd\n" +" http://jboss.com/products/seam/components\n" +" http://jboss.com/products/seam/components-2.1.xsd\">\n" +"\n" +" <guice:init injector=\"#{myGuiceInjector}\"/>\n" +"\n" +"</components>]]>" + +#. Tag: para +#: Guice.xml:62 +#, no-c-format msgid "<literal>myGuiceInjector</literal> must resolve to a Seam component that implements the Guice <literal>Injector</literal> interface." msgstr "<literal>myGuiceInjector</literal> deve risolvere ad un componente Seam che implementi l'interfaccia Guice <literal>Injector</literal>." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:94(para) +#. Tag: para +#: Guice.xml:67 +#, no-c-format msgid "Having to create an injector is boiler-plate code, though. What you really want to be able to do is simply hook up Seam to your Guice modules. Fortunately, there is a built-in Seam component that implements the <literal>Injector</literal> interface to do exactly that. You can configure it in the Seam component descriptor with this additional stanza." msgstr "Tuttavia dover creare un injector è pura scrittura di codice. Ciò che si vuole essere in grado di fare è semplicemente agganciare Seam ai propri moduli Guice. Fortunamente c'è un componente Seam predefinito che implementa l'interfaccia <literal>Injector</literal> per fare ciò. Si può configurarlo nel descrittore del componente Seam con il seguente codice." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:108(para) +#. Tag: programlisting +#: Guice.xml:74 +#, no-c-format +msgid "" +"<![CDATA[<guice:injector name=\"myGuiceInjector\">\n" +" <guice:modules> \n" +" <value>com.example.guice.GuiceModule1</value> \n" +" <value>com.example.guice.GuiceModule2</value> \n" +" </guice:modules> \n" +"</guice:injector>]]>" +msgstr "" +"<![CDATA[<guice:injector name=\"myGuiceInjector\">\n" +" <guice:modules> \n" +" <value>com.example.guice.GuiceModule1</value> \n" +" <value>com.example.guice.GuiceModule2</value> \n" +" </guice:modules> \n" +"</guice:injector>]]>" + +#. Tag: para +#: Guice.xml:76 +#, no-c-format msgid "Of course you can also use an injector that is already used in other, possibly non-Seam part of you application. That's one of the main motivations for creating this integration. Since the injector is defined with EL expression, you can obtain it in whatever way you like. For instance, you may use the Seam factory component pattern to provide injector." msgstr "Certamente si può anche usare un injector che viene già usato in un'altra parte anche non-Seam della proria applicazione. Questa è una delle principali motivazioni per creare quest'integrazione. Poiché l'injector è definito con un'espressione EL, si può ottenerlo in un qualsiasi modo si voglia. Per esempio si può usare il pattern del componente factory di Seam per fornire l'injector." -#: doc/Seam_Reference_Guide/en-US/Guice.xml:115(programlisting) -#, no-wrap +#. Tag: programlisting +#: Guice.xml:83 +#, no-c-format msgid "" "@Name(\"myGuiceInjectorFactory\")\n" "public InjectorFactory\n" @@ -126,16 +202,21 @@ " }\n" "}" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:128(title) +#. Tag: title +#: Guice.xml:88 +#, no-c-format msgid "Using multiple injectors" msgstr "Uso di injector multipli" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:130(para) +#. Tag: para +#: Guice.xml:90 +#, no-c-format msgid "By default, an injector configured in the Seam component descriptor is used. If you really need to use multiple injectors (AFAIK, you should use multiple modules instead), you can specify different injector for every Seam component in the <literal>@Guice</literal> annotation." msgstr "Di default viene usato un injector configurato nel descrittore di componente Seam. Se occorre usare più injector (in alternativa, si possono anche usare più moduli), si può specificare un injector per ogni componente Seam nell'annotazione <literal&gt;(a)Guice&lt;/literal&gt;.&quot; -#: doc/Seam_Reference_Guide/en-US/Guice.xml:137(programlisting) -#, no-wrap +#. Tag: programlisting +#: Guice.xml:97 +#, no-c-format msgid "" "@Name(\"myGuicyComponent\")\n" "@Guice(\"myGuiceInjector\")\n" @@ -153,12 +234,12 @@ " ...\n" "}" -#: doc/Seam_Reference_Guide/en-US/Guice.xml:147(para) +#. Tag: para +#: Guice.xml:101 +#, no-c-format msgid "That's all there is to it! Check out the guice example in the Seam distribution to see the Seam Guice integration in action!" msgstr "Ecco tutto! Si controlli l'esempio guice nella distribuzione Seam per vedere in azione l'integrazione Guice!" -#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2. -#: doc/Seam_Reference_Guide/en-US/Guice.xml:0(None) -msgid "translator-credits" -msgstr "translator-credits" +#~ msgid "translator-credits" +#~ msgstr "translator-credits" Modified: trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-10-14 11:38+0000\n" -"PO-Revision-Date: 2008-12-27 12:47+0100\n" +"POT-Creation-Date: 2009-04-15 13:51+0000\n" +"PO-Revision-Date: 2009-04-15 16:03+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -97,8 +97,8 @@ #. Tag: para #: Hsearch.xml:45 #, no-c-format -msgid "If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded into JBoss AS 4.2.GA), you also need to configure the appropriate event listeners." -msgstr "Se si pensa di usare Hibernate Annotation o EntityManager 3.2.x (incorporato in JBoss AS 4.2.GA), occorre configurare anche gli opportuni event listener." +msgid "If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded into JBoss AS 4.2.x and later), you also need to configure the appropriate event listeners." +msgstr "Se si pensa di usare Hibernate Annotation o EntityManager 3.2.x (incorporato in JBoss AS 4.2.x e successivi), occorre configurare anche gli opportuni event listener." #. Tag: programlisting #: Hsearch.xml:49 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Spring.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Spring.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Spring.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,9 +5,9 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" -"PO-Revision-Date: 2008-04-04 01:24+0000\n" -"Last-Translator: Automatically generated\n" +"POT-Creation-Date: 2009-04-15 13:52+0000\n" +"PO-Revision-Date: 2009-04-15 16:05+0100\n" +"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,25 +17,18 @@ #: Spring.xml:6 #, no-c-format msgid "Spring Framework integration" -msgstr "" +msgstr "Integrazione con il framework Spring" #. Tag: para #: Spring.xml:8 #, no-c-format -msgid "" -"The Spring integration module allows easy migration of Spring-based projects " -"to Seam and allows Spring applications to take advantage of key Seam " -"features like conversations and Seam's more sophisticated persistence " -"context management." +msgid "The Spring integration (part of the Seam IoC module) allows easy migration of Spring-based projects to Seam and allows Spring applications to take advantage of key Seam features like conversations and Seam's more sophisticated persistence context management." msgstr "" #. Tag: para #: Spring.xml:12 #, no-c-format -msgid "" -"Note! The Spring integration code is included in the jboss-seam-ioc library. " -"This dependency is required for all seam-spring integration techniques " -"covered in this chapter." +msgid "Note! The Spring integration code is included in the jboss-seam-ioc library. This dependency is required for all seam-spring integration techniques covered in this chapter." msgstr "" #. Tag: para @@ -83,18 +76,13 @@ #. Tag: para #: Spring.xml:37 #, no-c-format -msgid "" -"provides a Seam managed replacement for Spring's " -"<literal>OpenEntityManagerInViewFilter</literal> and " -"<literal>OpenSessionInViewFilter</literal>" +msgid "provides a Seam managed replacement for Spring's <literal>OpenEntityManagerInViewFilter</literal> and <literal>OpenSessionInViewFilter</literal>" msgstr "" #. Tag: para #: Spring.xml:40 #, no-c-format -msgid "" -"Support for Spring <literal>TaskExecutors</literal> to back " -"<literal>@Asynchronous</literal> calls" +msgid "Support for Spring <literal>TaskExecutors</literal> to back <literal>@Asynchronous</literal> calls" msgstr "" #. Tag: title @@ -106,11 +94,7 @@ #. Tag: para #: Spring.xml:47 #, no-c-format -msgid "" -"Injecting Seam component instances into Spring beans is accomplished using " -"the <literal>&lt;seam:instance/&gt;</literal> namespace handler. To enable " -"the Seam namespace handler, the Seam namespace must be added to the Spring " -"beans definition file:" +msgid "Injecting Seam component instances into Spring beans is accomplished using the <literal>&lt;seam:instance/&gt;</literal> namespace handler. To enable the Seam namespace handler, the Seam namespace must be added to the Spring beans definition file:" msgstr "" #. Tag: programlisting @@ -121,12 +105,17 @@ " xmlns:seam=\"http://jboss.com/products/seam/spring-seam\"\n" " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" " xsi:schemaLocation=\"http://www.springframework.org/schema/beans\n&q... -" http://www.springframework.org/schema/beans/spring-" -"beans-2.0.xsd\n" +" http://www.springframework.org/schema/beans/spring-beans-2.0.xsd\n" " http://jboss.com/products/seam/spring-seam\n" -" http://jboss.com/products/seam/spring-seam-2.1.xsd" -"\">]]>" +" http://jboss.com/products/seam/spring-seam-2.1.xsd\">]]>" msgstr "" +"<![CDATA[<beans xmlns=\"http://www.springframework.org/schema/beans\"\n" +" xmlns:seam=\"http://jboss.com/products/seam/spring-seam\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://www.springframework.org/schema/beans\n&q... +" http://www.springframework.org/schema/beans/spring-beans-2.0.xsd\n" +" http://jboss.com/products/seam/spring-seam\n" +" http://jboss.com/products/seam/spring-seam-2.1.xsd\">]]>" #. Tag: para #: Spring.xml:53 @@ -138,13 +127,17 @@ #: Spring.xml:55 #, no-c-format msgid "" -"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=" -"\"prototype\">\n" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" " <property name=\"someProperty\">\n" " <seam:instance name=\"someComponent\"/>\n" " </property>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" +" <property name=\"someProperty\">\n" +" <seam:instance name=\"someComponent\"/>\n" +" </property>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:57 @@ -156,35 +149,41 @@ #: Spring.xml:59 #, no-c-format msgid "" -"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=" -"\"prototype\">\n" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" " <property name=\"someProperty\">\n" " <seam:instance name=\"#{someExpression}\"/>\n" " </property>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" +" <property name=\"someProperty\">\n" +" <seam:instance name=\"#{someExpression}\"/>\n" +" </property>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:61 #, no-c-format -msgid "" -"Seam component instances may even be made available for injection into " -"Spring beans by a Spring bean id." +msgid "Seam component instances may even be made available for injection into Spring beans by a Spring bean id." msgstr "" #. Tag: programlisting #: Spring.xml:63 #, no-c-format msgid "" -"<![CDATA[<seam:instance name=\"someComponent\" id=\"someSeamComponentInstance" -"\"/>\n" +"<![CDATA[<seam:instance name=\"someComponent\" id=\"someSeamComponentInstance\"/>\n" "\n" -"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype" -"\">\n" +"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" " <property name=\"someProperty\" ref=\"someSeamComponentInstance\">\n" "</bean>\n" "]]>" msgstr "" +"<![CDATA[<seam:instance name=\"someComponent\" id=\"someSeamComponentInstance\"/>\n" +"\n" +"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" +" <property name=\"someProperty\" ref=\"someSeamComponentInstance\">\n" +"</bean>\n" +"]]>" #. Tag: para #: Spring.xml:65 @@ -195,51 +194,35 @@ #. Tag: para #: Spring.xml:67 #, no-c-format -msgid "" -"Seam was designed from the ground up to support a stateful component model " -"with multiple contexts. Spring was not. Unlike Seam bijection, Spring " -"injection does not occur at method invocation time. Instead, injection " -"happens only when the Spring bean is instantiated. So the instance available " -"when the bean is instantiated will be the same instance that the bean uses " -"for the entire life of the bean. For example, if a Seam " -"<literal>CONVERSATION</literal>-scoped component instance is directly " -"injected into a singleton Spring bean, that singleton will hold a reference " -"to the same instance long after the conversation is over! We call this " -"problem <emphasis>scope impedance</emphasis>. Seam bijection ensures that " -"scope impedance is maintained naturally as an invocation flows through the " -"system. In Spring, we need to inject a proxy of the Seam component, and " -"resolve the reference when the proxy is invoked." +msgid "Seam was designed from the ground up to support a stateful component model with multiple contexts. Spring was not. Unlike Seam bijection, Spring injection does not occur at method invocation time. Instead, injection happens only when the Spring bean is instantiated. So the instance available when the bean is instantiated will be the same instance that the bean uses for the entire life of the bean. For example, if a Seam <literal>CONVERSATION</literal>-scoped component instance is directly injected into a singleton Spring bean, that singleton will hold a reference to the same instance long after the conversation is over! We call this problem <emphasis>scope impedance</emphasis>. Seam bijection ensures that scope impedance is maintained naturally as an invocation flows through the system. In Spring, we need to inject a proxy of the Seam component, and resolve the reference when the proxy is invoked." msgstr "" #. Tag: para #: Spring.xml:77 #, no-c-format -msgid "" -"The <literal>&lt;seam:instance/&gt;</literal> tag lets us automatically " -"proxy the Seam component." +msgid "The <literal>&lt;seam:instance/&gt;</literal> tag lets us automatically proxy the Seam component." msgstr "" #. Tag: programlisting #: Spring.xml:79 #, no-c-format msgid "" -"<![CDATA[<seam:instance id=\"seamManagedEM\" name=\"someManagedEMComponent\" " -"proxy=\"true\"/>\n" +"<![CDATA[<seam:instance id=\"seamManagedEM\" name=\"someManagedEMComponent\" proxy=\"true\"/>\n" "\n" "<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\">\n" " <property name=\"entityManager\" ref=\"seamManagedEM\">\n" "</bean>]]>" msgstr "" +"<![CDATA[<seam:instance id=\"seamManagedEM\" name=\"someManagedEMComponent\" proxy=\"true\"/>\n" +"\n" +"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\">\n" +" <property name=\"entityManager\" ref=\"seamManagedEM\">\n" +"</bean>]]>" #. Tag: para #: Spring.xml:81 #, no-c-format -msgid "" -"This example shows one way to use a Seam-managed persistence context from a " -"Spring bean. (For a more robust way to use Seam-managed persistence contexts " -"as a replacement for the Spring <literal>OpenEntityManagerInView</literal> " -"filter see section on <link linkend=\"spring-persistence\">Using a Seam " -"Managed Persistence Context in Spring</link>)" +msgid "This example shows one way to use a Seam-managed persistence context from a Spring bean. (For a more robust way to use Seam-managed persistence contexts as a replacement for the Spring <literal>OpenEntityManagerInView</literal> filter see section on <link linkend=\"spring-persistence\">Using a Seam Managed Persistence Context in Spring</link>)" msgstr "" #. Tag: title @@ -251,9 +234,7 @@ #. Tag: para #: Spring.xml:90 #, no-c-format -msgid "" -"It is even easier to inject Spring beans into Seam component instances. " -"Actually, there are two possible approaches:" +msgid "It is even easier to inject Spring beans into Seam component instances. Actually, there are two possible approaches:" msgstr "" #. Tag: para @@ -271,21 +252,13 @@ #. Tag: para #: Spring.xml:102 #, no-c-format -msgid "" -"We'll discuss the second option in the next section. The easiest approach is " -"to access the Spring beans via EL." +msgid "We'll discuss the second option in the next section. The easiest approach is to access the Spring beans via EL." msgstr "" #. Tag: para #: Spring.xml:105 #, no-c-format -msgid "" -"The Spring <literal>DelegatingVariableResolver</literal> is an integration " -"point Spring provides for integrating Spring with JSF. This " -"<literal>VariableResolver</literal> makes all Spring beans available in EL " -"by their bean id. You'll need to add the " -"<literal>DelegatingVariableResolver</literal> to <literal>faces-config.xml</" -"literal>:" +msgid "The Spring <literal>DelegatingVariableResolver</literal> is an integration point Spring provides for integrating Spring with JSF. This <literal>VariableResolver</literal> makes all Spring beans available in EL by their bean id. You'll need to add the <literal>DelegatingVariableResolver</literal> to <literal>faces-config.xml</literal>:" msgstr "" #. Tag: programlisting @@ -298,6 +271,11 @@ " </variable-resolver>\n" "</application>]]>" msgstr "" +"<![CDATA[<application>\n" +" <variable-resolver>\n" +" org.springframework.web.jsf.DelegatingVariableResolver\n" +" </variable-resolver>\n" +"</application>]]>" #. Tag: para #: Spring.xml:112 @@ -312,14 +290,13 @@ "<![CDATA[@In(\"#{bookingService}\")\n" "private BookingService bookingService;]]>" msgstr "" +"<![CDATA[@In(\"#{bookingService}\")\n" +"private BookingService bookingService;]]>" #. Tag: para #: Spring.xml:116 #, no-c-format -msgid "" -"The use of Spring beans in EL is not limited to injection. Spring beans may " -"be used anywhere that EL expressions are used in Seam: process and pageflow " -"definitions, working memory assertions, etc..." +msgid "The use of Spring beans in EL is not limited to injection. Spring beans may be used anywhere that EL expressions are used in Seam: process and pageflow definitions, working memory assertions, etc..." msgstr "" #. Tag: title @@ -331,46 +308,31 @@ #. Tag: para #: Spring.xml:124 #, no-c-format -msgid "" -"The <literal>&lt;seam:component/&gt;</literal> namespace handler can be used " -"to make any Spring bean a Seam component. Just place the <literal>&lt;seam:" -"component/&gt;</literal> tag within the declaration of the bean that you " -"wish to be a Seam component:" +msgid "The <literal>&lt;seam:component/&gt;</literal> namespace handler can be used to make any Spring bean a Seam component. Just place the <literal>&lt;seam:component/&gt;</literal> tag within the declaration of the bean that you wish to be a Seam component:" msgstr "" #. Tag: programlisting #: Spring.xml:128 #, no-c-format msgid "" -"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=" -"\"prototype\">\n" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" " <seam:component/>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"prototype\">\n" +" <seam:component/>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:130 #, no-c-format -msgid "" -"By default, <literal>&lt;seam:component/&gt;</literal> will create a " -"<literal>STATELESS</literal> Seam component with class and name provided in " -"the bean definition. Occasionally, such as when a <literal>FactoryBean</" -"literal> is used, the class of the Spring bean may not be the class " -"appearing in the bean definition. In such cases the <literal>class</literal> " -"should be explicitly specified. A Seam component name may be explicitly " -"specified in cases where there is potential for a naming conflict." +msgid "By default, <literal>&lt;seam:component/&gt;</literal> will create a <literal>STATELESS</literal> Seam component with class and name provided in the bean definition. Occasionally, such as when a <literal>FactoryBean</literal> is used, the class of the Spring bean may not be the class appearing in the bean definition. In such cases the <literal>class</literal> should be explicitly specified. A Seam component name may be explicitly specified in cases where there is potential for a naming conflict." msgstr "" #. Tag: para #: Spring.xml:136 #, no-c-format -msgid "" -"The <literal>scope</literal> attribute of <literal>&lt;seam:component/&gt;</" -"literal> may be used if you wish the Spring bean to be managed in a " -"particular Seam scope. The Spring bean must be scoped to <literal>prototype</" -"literal> if the Seam scope specified is anything other than " -"<literal>STATELESS</literal>. Pre-existing Spring beans usually have a " -"fundamentally stateless character, so this attribute is not usually needed." +msgid "The <literal>scope</literal> attribute of <literal>&lt;seam:component/&gt;</literal> may be used if you wish the Spring bean to be managed in a particular Seam scope. The Spring bean must be scoped to <literal>prototype</literal> if the Seam scope specified is anything other than <literal>STATELESS</literal>. Pre-existing Spring beans usually have a fundamentally stateless character, so this attribute is not usually needed." msgstr "" #. Tag: title @@ -382,25 +344,13 @@ #. Tag: para #: Spring.xml:147 #, no-c-format -msgid "" -"The Seam integration package also lets you use Seam's contexts as Spring 2.0 " -"style custom scopes. This lets you declare any Spring bean in any of Seam's " -"contexts. However, note once again that Spring's component model was never " -"architected to support statefulness, so please use this feature with great " -"care. In particular, clustering of session or conversation scoped Spring " -"beans is deeply problematic, and care must be taken when injecting a bean or " -"component from a wider scope into a bean of a narrower scope." +msgid "The Seam integration package also lets you use Seam's contexts as Spring 2.0 style custom scopes. This lets you declare any Spring bean in any of Seam's contexts. However, note once again that Spring's component model was never architected to support statefulness, so please use this feature with great care. In particular, clustering of session or conversation scoped Spring beans is deeply problematic, and care must be taken when injecting a bean or component from a wider scope into a bean of a narrower scope." msgstr "" #. Tag: para #: Spring.xml:153 #, no-c-format -msgid "" -"By specifying <literal>&lt;seam:configure-scopes/&gt;</literal> once in a " -"Spring bean factory configuration, all of the Seam scopes will be available " -"to Spring beans as custom scopes. To associate a Spring bean with a " -"particular Seam scope, specify the Seam scope in the <literal>scope</" -"literal> attribute of the bean definition." +msgid "By specifying <literal>&lt;seam:configure-scopes/&gt;</literal> once in a Spring bean factory configuration, all of the Seam scopes will be available to Spring beans as custom scopes. To associate a Spring bean with a particular Seam scope, specify the Seam scope in the <literal>scope</literal> attribute of the bean definition." msgstr "" #. Tag: programlisting @@ -412,52 +362,38 @@ "\n" "...\n" "\n" -"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"seam." -"CONVERSATION\"/>]]>" +"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"seam.CONVERSATION\"/>]]>" msgstr "" +"<![CDATA[<!-- Only needs to be specified once per bean factory-->\n" +"<seam:configure-scopes/>\n" +"\n" +"...\n" +"\n" +"<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"seam.CONVERSATION\"/>]]>" #. Tag: para #: Spring.xml:160 #, no-c-format -msgid "" -"The prefix of the scope name may be changed by specifying the " -"<literal>prefix</literal> attribute in the <literal>configure-scopes</" -"literal> definition. (The default prefix is <literal>seam.</literal>)" +msgid "The prefix of the scope name may be changed by specifying the <literal>prefix</literal> attribute in the <literal>configure-scopes</literal> definition. (The default prefix is <literal>seam.</literal>)" msgstr "" #. Tag: para #: Spring.xml:163 #, no-c-format -msgid "" -"By default an instance of a Spring Component registered in this way is not " -"automatically created when referenced using <literal>@In</literal>. To have " -"an instance auto-created you must either specify <literal>@In(create=true)</" -"literal> at the injection point to identify a specific bean to be auto " -"created or you can use the <literal>default-auto-create</literal> attribute " -"of <literal>configure-scopes</literal> to make all spring beans who use a " -"seam scope auto created." +msgid "By default an instance of a Spring Component registered in this way is not automatically created when referenced using <literal>@In</literal>. To have an instance auto-created you must either specify <literal>@In(create=true)</literal> at the injection point to identify a specific bean to be auto created or you can use the <literal>default-auto-create</literal> attribute of <literal>configure-scopes</literal> to make all spring beans who use a seam scope auto created." msgstr "" #. Tag: para #: Spring.xml:168 #, no-c-format -msgid "" -"Seam-scoped Spring beans defined this way can be injected into other Spring " -"beans without the use of <literal>&lt;seam:instance/&gt;</literal>. However, " -"care must be taken to ensure scope impedance is maintained. The normal " -"approach used in Spring is to specify <literal>&lt;aop:scoped-proxy/&gt;</" -"literal> in the bean definition. However, Seam-scoped Spring beans are " -"<emphasis>not</emphasis> compatible with <literal>&lt;aop:scoped-proxy/&gt;</" -"literal>. So if you need to inject a Seam-scoped Spring bean into a " -"singleton, <literal>&lt;seam:instance/&gt;</literal> must be used:" +msgid "Seam-scoped Spring beans defined this way can be injected into other Spring beans without the use of <literal>&lt;seam:instance/&gt;</literal>. However, care must be taken to ensure scope impedance is maintained. The normal approach used in Spring is to specify <literal>&lt;aop:scoped-proxy/&gt;</literal> in the bean definition. However, Seam-scoped Spring beans are <emphasis>not</emphasis> compatible with <literal>&lt;aop:scoped-proxy/&gt;</literal>. So if you need to inject a Seam-scoped Spring bean into a singleton, <literal>&lt;seam:instance/&gt;</literal> must be used:" msgstr "" #. Tag: programlisting #: Spring.xml:176 #, no-c-format msgid "" -"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=" -"\"seam.CONVERSATION\"/>\n" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"seam.CONVERSATION\"/>\n" "\n" "...\n" "\n" @@ -467,6 +403,15 @@ " </property>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"someSpringBean\" class=\"SomeSpringBeanClass\" scope=\"seam.CONVERSATION\"/>\n" +"\n" +"...\n" +"\n" +"<bean id=\"someSingleton\">\n" +" <property name=\"someSeamScopedSpringBean\">\n" +" <seam:instance name=\"someSpringBean\" proxy=\"true\"/>\n" +" </property>\n" +"</bean>]]>" #. Tag: title #: Spring.xml:180 @@ -477,41 +422,25 @@ #. Tag: para #: Spring.xml:182 #, no-c-format -msgid "" -"Spring provides an extensible transaction management abstraction with " -"support for many transaction APIs (JPA, Hibernate, JDO, and JTA) Spring also " -"provides tight integrations with many application server TransactionManagers " -"such as Websphere and Weblogic. Spring transaction management exposes " -"support for many advanced features such as nested transactions and supports " -"full Java EE transaction propagation rules like REQUIRES_NEW and " -"NOT_SUPPORTED. For more information see the spring documentation <ulink url=" -"\"http://static.springframework.org/spring/docs/2.0.x/reference/transaction." -"html\">here</ulink>." +msgid "Spring provides an extensible transaction management abstraction with support for many transaction APIs (JPA, Hibernate, JDO, and JTA) Spring also provides tight integrations with many application server TransactionManagers such as Websphere and Weblogic. Spring transaction management exposes support for many advanced features such as nested transactions and supports full Java EE transaction propagation rules like REQUIRES_NEW and NOT_SUPPORTED. For more information see the spring documentation <ulink url=\"http://static.springframework.org/spring/docs/2.0.x/reference/... msgstr "" #. Tag: para #: Spring.xml:190 #, no-c-format -msgid "" -"To configure Seam to use Spring transactions enable the SpringTransaction " -"component like so:" +msgid "To configure Seam to use Spring transactions enable the SpringTransaction component like so:" msgstr "" #. Tag: programlisting #: Spring.xml:192 #, no-c-format -msgid "" -"<![CDATA[<spring:spring-transaction platform-transaction-manager=\"#" -"{transactionManager}\"/>]]>" -msgstr "" +msgid "<![CDATA[<spring:spring-transaction platform-transaction-manager=\"#{transactionManager}\"/>]]>" +msgstr "<![CDATA[<spring:spring-transaction platform-transaction-manager=\"#{transactionManager}\"/>]]>" #. Tag: para #: Spring.xml:194 #, no-c-format -msgid "" -"The <literal>spring:spring-transaction</literal> component will utilize " -"Springs transaction synchronization capabilities for synchronization " -"callbacks." +msgid "The <literal>spring:spring-transaction</literal> component will utilize Springs transaction synchronization capabilities for synchronization callbacks." msgstr "" #. Tag: title @@ -523,27 +452,13 @@ #. Tag: para #: Spring.xml:202 #, no-c-format -msgid "" -"One of the most powerful features of Seam is its conversation scope and the " -"ability to have an EntityManager open for the life of a conversation. This " -"eliminates many of the problems associated with the detachment and re-" -"attachment of entities as well as mitigates occurrences of the dreaded " -"<literal>LazyInitializationException</literal>. Spring does not provide a " -"way to manage an persistence context beyond the scope of a single web " -"request (<literal>OpenEntityManagerInViewFilter</literal>). So, it would be " -"nice if Spring developers could have access to a Seam managed persistence " -"context using all of the same tools Spring provides for integration with JPA" -"(e.g. <literal>PersistenceAnnotationBeanPostProcessor</literal>, " -"<literal>JpaTemplate</literal>, etc.)" +msgid "One of the most powerful features of Seam is its conversation scope and the ability to have an EntityManager open for the life of a conversation. This eliminates many of the problems associated with the detachment and re-attachment of entities as well as mitigates occurrences of the dreaded <literal>LazyInitializationException</literal>. Spring does not provide a way to manage an persistence context beyond the scope of a single web request (<literal>OpenEntityManagerInViewFilter</literal>). So, it would be nice if Spring developers could have access to a Seam managed persistence context using all of the same tools Spring provides for integration with JPA(e.g. <literal>PersistenceAnnotationBeanPostProcessor</literal>, <literal>JpaTemplate</literal>, etc.)" msgstr "" #. Tag: para #: Spring.xml:212 #, no-c-format -msgid "" -"Seam provides a way for Spring to access a Seam managed persistence context " -"with Spring's provided JPA tools bringing conversation scoped persistence " -"context capabilities to Spring applications." +msgid "Seam provides a way for Spring to access a Seam managed persistence context with Spring's provided JPA tools bringing conversation scoped persistence context capabilities to Spring applications." msgstr "" #. Tag: para @@ -555,97 +470,75 @@ #. Tag: para #: Spring.xml:220 #, no-c-format -msgid "" -"transparent access to a Seam managed persistence context using Spring " -"provided tools" +msgid "transparent access to a Seam managed persistence context using Spring provided tools" msgstr "" #. Tag: para #: Spring.xml:223 #, no-c-format -msgid "" -"access to Seam conversation scoped persistence contexts in a non web request " -"(e.g. asynchronous quartz job)" +msgid "access to Seam conversation scoped persistence contexts in a non web request (e.g. asynchronous quartz job)" msgstr "" #. Tag: para #: Spring.xml:227 #, no-c-format -msgid "" -"allows for using Seam managed persistence contexts with Spring managed " -"transactions (will need to flush the persistence context manually)" +msgid "allows for using Seam managed persistence contexts with Spring managed transactions (will need to flush the persistence context manually)" msgstr "" #. Tag: para #: Spring.xml:232 #, no-c-format -msgid "" -"Spring's persistence context propagation model allows only one open " -"EntityManager per EntityManagerFactory so the Seam integration works by " -"wrapping an EntityManagerFactory around a Seam managed persistence context." +msgid "Spring's persistence context propagation model allows only one open EntityManager per EntityManagerFactory so the Seam integration works by wrapping an EntityManagerFactory around a Seam managed persistence context." msgstr "" #. Tag: programlisting #: Spring.xml:236 #, no-c-format msgid "" -"<![CDATA[<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc." -"spring.SeamManagedEntityManagerFactoryBean\">\n" -" <property name=\"persistenceContextName\" value=\"entityManager\"/" -">\n" +"<![CDATA[<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean\">\n" +" <property name=\"persistenceContextName\" value=\"entityManager\"/>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean\">\n" +" <property name=\"persistenceContextName\" value=\"entityManager\"/>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:238 #, no-c-format -msgid "" -"Where 'persistenceContextName' is the name of the Seam managed persistence " -"context component. By default this EntityManagerFactory has a unitName equal " -"to the Seam component name or in this case 'entityManager'. If you wish to " -"provide a different unitName you can do so by providing a " -"persistenceUnitName like so:" +msgid "Where 'persistenceContextName' is the name of the Seam managed persistence context component. By default this EntityManagerFactory has a unitName equal to the Seam component name or in this case 'entityManager'. If you wish to provide a different unitName you can do so by providing a persistenceUnitName like so:" msgstr "" #. Tag: programlisting #: Spring.xml:243 #, no-c-format msgid "" -"<![CDATA[<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc." -"spring.SeamManagedEntityManagerFactoryBean\">\n" -" <property name=\"persistenceContextName\" value=\"entityManager\"/" -">\n" -" <property name=\"persistenceUnitName\" value=\"bookingDatabase:" -"extended\"/>\n" +"<![CDATA[<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean\">\n" +" <property name=\"persistenceContextName\" value=\"entityManager\"/>\n" +" <property name=\"persistenceUnitName\" value=\"bookingDatabase:extended\"/>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean\">\n" +" <property name=\"persistenceContextName\" value=\"entityManager\"/>\n" +" <property name=\"persistenceUnitName\" value=\"bookingDatabase:extended\"/>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:245 #, no-c-format -msgid "" -"This EntityManagerFactory can then be used in any Spring provided tools. For " -"example, using Spring's <literal>PersistenceAnnotationBeanPostProcessor</" -"literal> is the exact same as before." +msgid "This EntityManagerFactory can then be used in any Spring provided tools. For example, using Spring's <literal>PersistenceAnnotationBeanPostProcessor</literal> is the exact same as before." msgstr "" #. Tag: programlisting #: Spring.xml:248 #, no-c-format -msgid "" -"<![CDATA[<bean class=\"org.springframework.orm.jpa.support." -"PersistenceAnnotationBeanPostProcessor\"/>]]>" -msgstr "" +msgid "<![CDATA[<bean class=\"org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor\"/>]]>" +msgstr "<![CDATA[<bean class=\"org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor\"/>]]>" #. Tag: para #: Spring.xml:250 #, no-c-format -msgid "" -"If you define your real EntityManagerFactory in Spring but wish to use a " -"Seam managed persistence context you can tell the " -"<literal>PersistenceAnnotationBeanPostProcessor</literal> which " -"persistenctUnitName you wish to use by default by specifying the " -"<literal>defaultPersistenceUnitName</literal> property." +msgid "If you define your real EntityManagerFactory in Spring but wish to use a Seam managed persistence context you can tell the <literal>PersistenceAnnotationBeanPostProcessor</literal> which persistenctUnitName you wish to use by default by specifying the <literal>defaultPersistenceUnitName</literal> property." msgstr "" #. Tag: para @@ -658,23 +551,27 @@ #: Spring.xml:256 #, no-c-format msgid "" -"<![CDATA[<bean id=\"entityManagerFactory\" class=\"org.springframework.orm." -"jpa.LocalEntityManagerFactoryBean\">\n" +"<![CDATA[<bean id=\"entityManagerFactory\" class=\"org.springframework.orm.jpa.LocalEntityManagerFactoryBean\">\n" " <property name=\"persistenceUnitName\" value=\"bookingDatabase\"/>\n" "</bean>\n" -"<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring." -"SeamManagedEntityManagerFactoryBean\">\n" -" <property name=\"persistenceContextName\" value=\"entityManager\"/" -">\n" -" <property name=\"persistenceUnitName\" value=\"bookingDatabase:" -"extended\"/>\n" +"<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean\">\n" +" <property name=\"persistenceContextName\" value=\"entityManager\"/>\n" +" <property name=\"persistenceUnitName\" value=\"bookingDatabase:extended\"/>\n" "</bean>\n" -"<bean class=\"org.springframework.orm.jpa.support." -"PersistenceAnnotationBeanPostProcessor\">\n" -" <property name=\"defaultPersistenceUnitName\" value=" -"\"bookingDatabase:extended\"/>\n" +"<bean class=\"org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor\">\n" +" <property name=\"defaultPersistenceUnitName\" value=\"bookingDatabase:extended\"/>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"entityManagerFactory\" class=\"org.springframework.orm.jpa.LocalEntityManagerFactoryBean\">\n" +" <property name=\"persistenceUnitName\" value=\"bookingDatabase\"/>\n" +"</bean>\n" +"<bean id=\"seamEntityManagerFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean\">\n" +" <property name=\"persistenceContextName\" value=\"entityManager\"/>\n" +" <property name=\"persistenceUnitName\" value=\"bookingDatabase:extended\"/>\n" +"</bean>\n" +"<bean class=\"org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor\">\n" +" <property name=\"defaultPersistenceUnitName\" value=\"bookingDatabase:extended\"/>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:258 @@ -687,29 +584,28 @@ #, no-c-format msgid "" "<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n" -" auto-create=\"true\" entity-manager-factory=\"#{entityManagerFactory}" -"\"/>]]>" +" auto-create=\"true\" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>" msgstr "" +"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n" +" auto-create=\"true\" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>" #. Tag: para #: Spring.xml:262 #, no-c-format -msgid "" -"<literal>JpaTemplate</literal> and <literal>JpaDaoSupport</literal> are " -"configured the same way for a Seam managed persistence context as they would " -"be fore a Seam managed persistence context." +msgid "<literal>JpaTemplate</literal> and <literal>JpaDaoSupport</literal> are configured the same way for a Seam managed persistence context as they would be fore a Seam managed persistence context." msgstr "" #. Tag: programlisting #: Spring.xml:265 #, no-c-format msgid "" -"<![CDATA[<bean id=\"bookingService\" class=\"org.jboss.seam.example.spring." -"BookingService\">\n" -" <property name=\"entityManagerFactory\" ref=" -"\"seamEntityManagerFactory\"/>\n" +"<![CDATA[<bean id=\"bookingService\" class=\"org.jboss.seam.example.spring.BookingService\">\n" +" <property name=\"entityManagerFactory\" ref=\"seamEntityManagerFactory\"/>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"bookingService\" class=\"org.jboss.seam.example.spring.BookingService\">\n" +" <property name=\"entityManagerFactory\" ref=\"seamEntityManagerFactory\"/>\n" +"</bean>]]>" #. Tag: title #: Spring.xml:268 @@ -720,44 +616,31 @@ #. Tag: para #: Spring.xml:270 #, no-c-format -msgid "" -"The Seam Spring integration also provides support for complete access to a " -"Seam managed Hibernate session using spring's tools. This integration is " -"very similar to the <link linkend=\"spring-persistence\">JPA integration</" -"link>." +msgid "The Seam Spring integration also provides support for complete access to a Seam managed Hibernate session using spring's tools. This integration is very similar to the <link linkend=\"spring-persistence\">JPA integration</link>." msgstr "" #. Tag: para #: Spring.xml:273 #, no-c-format -msgid "" -"Like Spring's JPA integration spring's propagation model allows only one " -"open EntityManager per EntityManagerFactory per transaction??? to be " -"available to spring tools. So, the Seam Session integration works by " -"wrapping a proxy SessionFactory around a Seam managed Hibernate session " -"context." +msgid "Like Spring's JPA integration spring's propagation model allows only one open EntityManager per EntityManagerFactory per transaction??? to be available to spring tools. So, the Seam Session integration works by wrapping a proxy SessionFactory around a Seam managed Hibernate session context." msgstr "" #. Tag: programlisting #: Spring.xml:278 #, no-c-format msgid "" -"<![CDATA[<bean id=\"seamSessionFactory\" class=\"org.jboss.seam.ioc.spring." -"SeamManagedSessionFactoryBean\">\n" +"<![CDATA[<bean id=\"seamSessionFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean\">\n" " <property name=\"sessionName\" value=\"hibernateSession\"/>\n" "</bean>]]>" msgstr "" +"<![CDATA[<bean id=\"seamSessionFactory\" class=\"org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean\">\n" +" <property name=\"sessionName\" value=\"hibernateSession\"/>\n" +"</bean>]]>" #. Tag: para #: Spring.xml:280 #, no-c-format -msgid "" -"Where 'sessionName' is the name of the <literal>persistence:managed-" -"hibernate-session</literal> component. This SessionFactory can then be used " -"in any Spring provided tools. The integration also provides support for " -"calls to <literal>SessionFactory.getCurrentInstance()</literal> as long as " -"you call getCurrentInstance() on the <literal>SeamManagedSessionFactory</" -"literal>." +msgid "Where 'sessionName' is the name of the <literal>persistence:managed-hibernate-session</literal> component. This SessionFactory can then be used in any Spring provided tools. The integration also provides support for calls to <literal>SessionFactory.getCurrentInstance()</literal> as long as you call getCurrentInstance() on the <literal>SeamManagedSessionFactory</literal>." msgstr "" #. Tag: title @@ -769,40 +652,25 @@ #. Tag: para #: Spring.xml:288 #, no-c-format -msgid "" -"Although it is possible to use the Spring <literal>ContextLoaderListener</" -"literal> to start your application's Spring ApplicationContext there are a " -"couple of limitations." +msgid "Although it is possible to use the Spring <literal>ContextLoaderListener</literal> to start your application's Spring ApplicationContext there are a couple of limitations." msgstr "" #. Tag: para #: Spring.xml:293 #, no-c-format -msgid "" -"the Spring ApplicationContext must be started <emphasis>after</emphasis> the " -"<literal>SeamListener</literal>" +msgid "the Spring ApplicationContext must be started <emphasis>after</emphasis> the <literal>SeamListener</literal>" msgstr "" #. Tag: para #: Spring.xml:297 #, no-c-format -msgid "" -"it can be tricky starting a Spring ApplicationContext for use in Seam unit " -"and integration tests" +msgid "it can be tricky starting a Spring ApplicationContext for use in Seam unit and integration tests" msgstr "" #. Tag: para #: Spring.xml:302 #, no-c-format -msgid "" -"To overcome these two limitations the Spring integration includes a Seam " -"component that will start a Spring ApplicationContext. To use this Seam " -"component place the <literal>&lt;spring:context-loader/&gt;</literal> " -"definition in the <literal>components.xml</literal>. Specify your Spring " -"context file location in the <literal>config-locations</literal> attribute. " -"If more than one config file is needed you can place them in the nested " -"<literal>&lt;spring:config-locations/&gt;</literal> element following " -"standard <literal>components.xml</literal> multi value practices." +msgid "To overcome these two limitations the Spring integration includes a Seam component that will start a Spring ApplicationContext. To use this Seam component place the <literal>&lt;spring:context-loader/&gt;</literal> definition in the <literal>components.xml</literal>. Specify your Spring context file location in the <literal>config-locations</literal> attribute. If more than one config file is needed you can place them in the nested <literal>&lt;spring:config-locations/&gt;</literal> element following standard <literal>components.xml</literal> multi value practices." msgstr "" #. Tag: programlisting @@ -813,17 +681,25 @@ " xmlns:spring=\"http://jboss.com/products/seam/spring\"\n" " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" " xsi:schemaLocation=\"http://jboss.com/products/seam/components\n" -" http://jboss.com/products/seam/components-" -"2.1.xsd\n" +" http://jboss.com/products/seam/components-2.1.xsd\n" " http://jboss.com/products/seam/spring\n" -" http://jboss.com/products/seam/spring-2.1.xsd" -"\">\n" +" http://jboss.com/products/seam/spring-2.1.xsd\">\n" "\n" -" <spring:context-loader config-locations=\"/WEB-INF/" -"applicationContext.xml\"/>\n" +" <spring:context-loader config-locations=\"/WEB-INF/applicationContext.xml\"/>\n" "\n" "</components>]]>" msgstr "" +"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n" +" xmlns:spring=\"http://jboss.com/products/seam/spring\"\n" +" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" +" xsi:schemaLocation=\"http://jboss.com/products/seam/components\n" +" http://jboss.com/products/seam/components-2.1.xsd\n" +" http://jboss.com/products/seam/spring\n" +" http://jboss.com/products/seam/spring-2.1.xsd\">\n" +"\n" +" <spring:context-loader config-locations=\"/WEB-INF/applicationContext.xml\"/>\n" +"\n" +"</components>]]>" #. Tag: title #: Spring.xml:313 @@ -834,42 +710,34 @@ #. Tag: para #: Spring.xml:315 #, no-c-format -msgid "" -"Spring provides an abstraction for executing code asynchronously called a " -"<literal>TaskExecutor</literal>. The Spring Seam integration allows for the " -"use of a Spring <literal>TaskExecutor</literal> for executing immediate " -"<literal>@Asynchronous</literal> method calls. To enable this functionality " -"install the <literal>SpringTaskExecutorDispatchor</literal> and provide a " -"spring bean defined taskExecutor like so:" +msgid "Spring provides an abstraction for executing code asynchronously called a <literal>TaskExecutor</literal>. The Spring Seam integration allows for the use of a Spring <literal>TaskExecutor</literal> for executing immediate <literal>@Asynchronous</literal> method calls. To enable this functionality install the <literal>SpringTaskExecutorDispatchor</literal> and provide a spring bean defined taskExecutor like so:" msgstr "" #. Tag: programlisting #: Spring.xml:320 #, no-c-format -msgid "" -"<![CDATA[<spring:task-executor-dispatcher task-executor=\"#" -"{springThreadPoolTaskExecutor}\"/>]]>" -msgstr "" +msgid "<![CDATA[<spring:task-executor-dispatcher task-executor=\"#{springThreadPoolTaskExecutor}\"/>]]>" +msgstr "<![CDATA[<spring:task-executor-dispatcher task-executor=\"#{springThreadPoolTaskExecutor}\"/>]]>" #. Tag: para #: Spring.xml:322 #, no-c-format -msgid "" -"Because a Spring <literal>TaskExecutor</literal> does not support scheduling " -"of an asynchronous event a fallback Seam <literal>Dispatcher</literal> can " -"be provided to handle scheduled asynchronous event like so:" +msgid "Because a Spring <literal>TaskExecutor</literal> does not support scheduling of an asynchronous event a fallback Seam <literal>Dispatcher</literal> can be provided to handle scheduled asynchronous event like so:" msgstr "" #. Tag: programlisting #: Spring.xml:325 #, no-c-format msgid "" -"<![CDATA[<!-- Install a ThreadPoolDispatcher to handle scheduled " -"asynchronous event -->\n" +"<![CDATA[<!-- Install a ThreadPoolDispatcher to handle scheduled asynchronous event -->\n" "<core:thread-pool-dispatcher name=\"threadPoolDispatcher\"/>\n" "\n" "<!-- Install the SpringDispatcher as default -->\n" -"<spring:task-executor-dispatcher task-executor=\"#" -"{springThreadPoolTaskExecutor}\" schedule-dispatcher=\"#" -"{threadPoolDispatcher}\"/>]]>" +"<spring:task-executor-dispatcher task-executor=\"#{springThreadPoolTaskExecutor}\" schedule-dispatcher=\"#{threadPoolDispatcher}\"/>]]>" msgstr "" +"<![CDATA[<!-- Install a ThreadPoolDispatcher to handle scheduled asynchronous event -->\n" +"<core:thread-pool-dispatcher name=\"threadPoolDispatcher\"/>\n" +"\n" +"<!-- Install the SpringDispatcher as default -->\n" +"<spring:task-executor-dispatcher task-executor=\"#{springThreadPoolTaskExecutor}\" schedule-dispatcher=\"#{threadPoolDispatcher}\"/>]]>" + Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2009-04-15 11:19:36 UTC (rev 10423) +++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2009-04-15 14:06:05 UTC (rev 10424) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-04-07 12:40+0000\n" -"PO-Revision-Date: 2009-04-07 14:46+0100\n" +"POT-Creation-Date: 2009-04-15 13:52+0000\n" +"PO-Revision-Date: 2009-04-15 16:05+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com&gt;\n&quot; "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -70,8 +70,8 @@ #. Tag: para #: Tutorial.xml:47 #, no-c-format -msgid "The examples are configured for use on JBoss 4.2. You'll need to set <literal>jboss.home</literal>, in the shared <literal>build.properties</literal> file in the root folder of your Seam installation, to the location of your JBoss AS installation." -msgstr "Gli esempi sono configurati per usare JBoss 4.2. Dovrai impostare la variabile <literal>jboss.home</literal> affinché punti alla locazione dell'installazione di JBoss AS. Questa variabile si trova nel file condiviso <literal>build.properties</literal> nella cartella radice dell'installazione di Seam." +msgid "The examples are configured for use on JBoss AS 4.2 or 5.0. You'll need to set <literal>jboss.home</literal>, in the shared <literal>build.properties</literal> file in the root folder of your Seam installation, to the location of your JBoss AS installation." +msgstr "Gli esempi sono configurati per usare JBoss 4.2 o 5.0. Dovrai impostare la variabile <literal>jboss.home</literal> affinché punti alla locazione dell'installazione di JBoss AS. Questa variabile si trova nel file condiviso <literal>build.properties</literal> nella cartella radice dell'installazione di Seam." #. Tag: para #: Tutorial.xml:51