[seam-commits] Seam SVN: r9786 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Tue Dec 16 06:19:04 EST 2008
Author: nico.ben
Date: 2008-12-16 06:19:03 -0500 (Tue, 16 Dec 2008)
New Revision: 9786
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po
trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:22+0000\n"
-"PO-Revision-Date: 2008-12-12 00:02+0100\n"
+"PO-Revision-Date: 2008-12-16 11:25+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -409,7 +409,7 @@
#: Annotations.xml:303
#, no-c-format
msgid "Annotations for bijection"
-msgstr ""
+msgstr "Annotazioni per la bijection"
#. Tag: para
#: Annotations.xml:304
@@ -632,7 +632,7 @@
#: Annotations.xml:478
#, no-c-format
msgid "<![CDATA[@Factory(\"processInstance\", scope=CONVERSATION) public ProcessInstance createProcessInstance() { ... }]]>"
-msgstr ""
+msgstr "<![CDATA[@Factory(\"processInstance\", scope=CONVERSATION) public ProcessInstance createProcessInstance() { ... }]]>"
#. Tag: para
#: Annotations.xml:479
@@ -722,7 +722,7 @@
#: Annotations.xml:579
#, no-c-format
msgid "Annotations for component lifecycle methods"
-msgstr ""
+msgstr "Annotazioni per i metodi del ciclo di vita dei componenti"
#. Tag: para
#: Annotations.xml:580
@@ -806,7 +806,7 @@
#: Annotations.xml:645
#, no-c-format
msgid "Annotations for context demarcation"
-msgstr ""
+msgstr "Annotazioni per la demarcazione del contesto"
#. Tag: para
#: Annotations.xml:646
@@ -916,13 +916,13 @@
#: Annotations.xml:739
#, no-c-format
msgid "@End"
-msgstr ""
+msgstr "@End"
#. Tag: programlisting
#: Annotations.xml:742
#, no-c-format
msgid "<![CDATA[@End]]>"
-msgstr ""
+msgstr "<![CDATA[@End]]>"
#. Tag: para
#: Annotations.xml:743
@@ -947,13 +947,13 @@
#: Annotations.xml:775
#, no-c-format
msgid "@StartTask"
-msgstr ""
+msgstr "@StartTask"
#. Tag: programlisting
#: Annotations.xml:778
#, no-c-format
msgid "<![CDATA[@StartTask]]>"
-msgstr ""
+msgstr "<![CDATA[@StartTask]]>"
#. Tag: para
#: Annotations.xml:779
@@ -978,13 +978,13 @@
#: Annotations.xml:824
#, no-c-format
msgid "@BeginTask"
-msgstr ""
+msgstr "@BeginTask"
#. Tag: programlisting
#: Annotations.xml:827
#, no-c-format
msgid "<![CDATA[@BeginTask]]>"
-msgstr ""
+msgstr "<![CDATA[@BeginTask]]>"
#. Tag: para
#: Annotations.xml:828
@@ -1002,13 +1002,13 @@
#: Annotations.xml:870
#, no-c-format
msgid "@EndTask"
-msgstr ""
+msgstr "@EndTask"
#. Tag: programlisting
#: Annotations.xml:873
#, no-c-format
msgid "<![CDATA[@EndTask]]>"
-msgstr ""
+msgstr "<![CDATA[@EndTask]]>"
#. Tag: para
#: Annotations.xml:874
@@ -1020,7 +1020,7 @@
#: Annotations.xml:883
#, no-c-format
msgid "<![CDATA[@EndTask(transition=\"transitionName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@EndTask(transition=\"transitionName\")]]>"
#. Tag: para
#: Annotations.xml:884
@@ -1038,13 +1038,13 @@
#: Annotations.xml:911
#, no-c-format
msgid "@CreateProcess"
-msgstr ""
+msgstr "@CreateProcess"
#. Tag: programlisting
#: Annotations.xml:914
#, no-c-format
msgid "<![CDATA[@CreateProcess(definition=\"process definition name\")]]>"
-msgstr ""
+msgstr "<![CDATA[@CreateProcess(definition=\"process definition name\")]]>"
#. Tag: para
#: Annotations.xml:915
@@ -1062,13 +1062,13 @@
#: Annotations.xml:935
#, no-c-format
msgid "@ResumeProcess"
-msgstr ""
+msgstr "@ResumeProcess"
#. Tag: programlisting
#: Annotations.xml:938
#, no-c-format
msgid "<![CDATA[@ResumeProcess(processIdParameter=\"processId\")]]>"
-msgstr ""
+msgstr "<![CDATA[@ResumeProcess(processIdParameter=\"processId\")]]>"
#. Tag: para
#: Annotations.xml:939
@@ -1086,13 +1086,13 @@
#: Annotations.xml:960
#, no-c-format
msgid "@Transition"
-msgstr ""
+msgstr "@Transition"
#. Tag: programlisting
#: Annotations.xml:963
#, no-c-format
msgid "<![CDATA[@Transition(\"cancel\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Transition(\"cancel\")]]>"
#. Tag: para
#: Annotations.xml:964
@@ -1116,13 +1116,13 @@
#: Annotations.xml:984
#, no-c-format
msgid "@Transactional"
-msgstr ""
+msgstr "@Transactional"
#. Tag: programlisting
#: Annotations.xml:987
#, no-c-format
msgid "<![CDATA[@Transactional]]>"
-msgstr ""
+msgstr "<![CDATA[@Transactional]]>"
#. Tag: para
#: Annotations.xml:988
@@ -1140,13 +1140,13 @@
#: Annotations.xml:1004
#, no-c-format
msgid "@ApplicationException"
-msgstr ""
+msgstr "@ApplicationException"
#. Tag: programlisting
#: Annotations.xml:1007
#, no-c-format
msgid "<![CDATA[@ApplicationException]]>"
-msgstr ""
+msgstr "<![CDATA[@ApplicationException]]>"
#. Tag: para
#: Annotations.xml:1008
@@ -1176,13 +1176,13 @@
#: Annotations.xml:1041
#, no-c-format
msgid "@Interceptors"
-msgstr ""
+msgstr "@Interceptors"
#. Tag: programlisting
#: Annotations.xml:1044
#, no-c-format
msgid "<![CDATA[@Interceptors({DVDInterceptor, CDInterceptor})]]>"
-msgstr ""
+msgstr "<![CDATA[@Interceptors({DVDInterceptor, CDInterceptor})]]>"
#. Tag: para
#: Annotations.xml:1045
@@ -1206,7 +1206,7 @@
#: Annotations.xml:1068
#, no-c-format
msgid "Annotations for exceptions"
-msgstr ""
+msgstr "Annotazioni per le eccezioni"
#. Tag: para
#: Annotations.xml:1070
@@ -1285,7 +1285,7 @@
#: Annotations.xml:1146
#, no-c-format
msgid "Annotations for Seam Remoting"
-msgstr ""
+msgstr "Annotazioni per Seam Remoting"
#. Tag: para
#: Annotations.xml:1147
@@ -1315,7 +1315,7 @@
#: Annotations.xml:1173
#, no-c-format
msgid "Annotations for Seam interceptors"
-msgstr ""
+msgstr "Annotazioni per gli interceptor di Seam"
#. Tag: para
#: Annotations.xml:1174
@@ -1333,7 +1333,7 @@
#: Annotations.xml:1185
#, no-c-format
msgid "@Interceptor"
-msgstr ""
+msgstr "@Interceptor"
#. Tag: programlisting
#: Annotations.xml:1188
@@ -1387,7 +1387,7 @@
#: Annotations.xml:1215
#, no-c-format
msgid "Annotations for asynchronicity"
-msgstr ""
+msgstr "Annotazioni per l'asincronicità"
#. Tag: para
#: Annotations.xml:1216
@@ -1489,7 +1489,7 @@
#: Annotations.xml:1278
#, no-c-format
msgid "Annotations for use with JSF"
-msgstr ""
+msgstr "Annotazioni per l'uso di JSF"
#. Tag: para
#: Annotations.xml:1279
@@ -1736,7 +1736,7 @@
#: Annotations.xml:1535
#, no-c-format
msgid "@Filter"
-msgstr ""
+msgstr "@Filter"
#. Tag: para
#: Annotations.xml:1538
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-04 00:58+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-16 11:34+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,27 +22,19 @@
#. 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!"
+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 ""
#. Tag: title
#: Configuration.xml:12
#, no-c-format
msgid "Basic Seam configuration"
-msgstr ""
+msgstr "Configurazione base di Seam"
#. 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."
+msgid "First, let's look at the basic configuration that is needed whenever we use Seam with JSF."
msgstr ""
#. Tag: title
@@ -72,6 +64,16 @@
" <url-pattern>*.seam</url-pattern>\n"
"</servlet-mapping>]]>"
msgstr ""
+"<![CDATA[<servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+"</servlet>\n"
+"\n"
+"<servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.seam</url-pattern>\n"
+"</servlet-mapping>]]>"
#. Tag: para
#: Configuration.xml:23
@@ -82,9 +84,7 @@
#. Tag: para
#: Configuration.xml:25
#, no-c-format
-msgid ""
-"In addition, Seam requires the following entry in your <literal>web.xml</"
-"literal> file:"
+msgid "In addition, Seam requires the following entry in your <literal>web.xml</literal> file:"
msgstr ""
#. Tag: programlisting
@@ -95,24 +95,20 @@
" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
"</listener>]]>"
msgstr ""
+"<![CDATA[<listener>\n"
+" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
+"</listener>]]>"
#. Tag: para
#: Configuration.xml:29
#, no-c-format
-msgid ""
-"This listener is responsible for bootstrapping Seam, and for destroying "
-"session and application contexts."
+msgid "This listener is responsible for bootstrapping Seam, and for destroying session and application contexts."
msgstr ""
#. Tag: para
#: Configuration.xml:32
#, no-c-format
-msgid ""
-"Some JSF implementations have a broken implementation of server-side state "
-"saving that interferes with Seam's conversation propagation. If you have "
-"problems with conversation propagation during form submissions, try "
-"switching to client-side state saving. You'll need this in <literal>web.xml</"
-"literal>:"
+msgid "Some JSF implementations have a broken implementation of server-side state saving that interferes with Seam's conversation propagation. If you have problems with conversation propagation during form submissions, try switching to client-side state saving. You'll need this in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -124,22 +120,15 @@
" <param-value>client</param-value>\n"
"</context-param>]]>"
msgstr ""
+"<![CDATA[<context-param>\n"
+" <param-name>javax.faces.STATE_SAVING_METHOD</param-name>\n"
+" <param-value>client</param-value>\n"
+"</context-param>]]>"
#. Tag: para
#: Configuration.xml:38
#, no-c-format
-msgid ""
-"There is a minor gray area in the JSF specification regarding the mutability "
-"of view state values. Since Seam uses the JSF view state to back its PAGE "
-"scope this can become an issue in some cases. If you're using server side "
-"state saving with the JSF-RI and you want a PAGE scoped bean to keep its "
-"exact value for a given view of a page you will need to specify the "
-"following context-param. Otherwise if a user uses the \"back\" button a PAGE "
-"scoped component will have the latest value if it has changed not the value "
-"of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public."
-"dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This "
-"setting is not enabled by default because of the performance hit of "
-"serializing the JSF view with every request."
+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 ""
#. Tag: programlisting
@@ -151,6 +140,10 @@
" <param-value>true</param-value>\n"
"</context-param>]]>"
msgstr ""
+"<![CDATA[<context-param>\n"
+" <param-name>com.sun.faces.serializeServerState</param-name>\n"
+" <param-value>true</param-value>\n"
+"</context-param>]]>"
#. Tag: title
#: Configuration.xml:56
@@ -161,9 +154,7 @@
#. 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>:"
+msgid "If you want follow our advice and use Facelets instead of JSP, add the following lines to <literal>faces-config.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -174,6 +165,9 @@
" <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>\n"
"</application>]]>"
msgstr ""
+"<![CDATA[<application>\n"
+" <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>\n"
+"</application>]]>"
#. Tag: para
#: Configuration.xml:63
@@ -190,20 +184,15 @@
" <param-value>.xhtml</param-value>\n"
"</context-param>]]>"
msgstr ""
+"<![CDATA[<context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+"</context-param>]]>"
#. Tag: para
#: Configuration.xml:67
#, no-c-format
-msgid ""
-"If you are using facelets in JBoss AS, you'll find that Facelets logging is "
-"broken (the log messages don't make it to the server log). Seam provides a "
-"bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</"
-"literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/"
-"jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in "
-"the <literal>WEB-INF/lib</literal> of your application. The Facelets logging "
-"catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/"
-"nonav/docs/dev/docbook.html#config-logging\">Facelets Developer "
-"Documentation</ulink>."
+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 ""
#. Tag: title
@@ -215,10 +204,7 @@
#. 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>:"
+msgid "The Seam Resource Servlet provides resources used by Seam Remoting, captchas (see the security chapter) and some JSF UI controls. Configuring the Seam Resource Servlet requires the following entry in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -235,6 +221,15 @@
" <url-pattern>/seam/resource/*</url-pattern>\n"
"</servlet-mapping>]]>"
msgstr ""
+"<![CDATA[<servlet>\n"
+" <servlet-name>Seam Resource Servlet</servlet-name>\n"
+" <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>\n"
+"</servlet>\n"
+" \n"
+"<servlet-mapping>\n"
+" <servlet-name>Seam Resource Servlet</servlet-name>\n"
+" <url-pattern>/seam/resource/*</url-pattern>\n"
+"</servlet-mapping>]]>"
#. Tag: title
#: Configuration.xml:91
@@ -245,12 +240,7 @@
#. 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>:"
+msgid "Seam doesn't need any servlet filters for basic operation. However, there are several features which depend upon the use of filters. To make things easier, Seam lets you add and configure servlet filters just like you would configure other built-in Seam components. To take advantage of this feature, we must first install a master filter in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -267,40 +257,38 @@
" <url-pattern>/*</url-pattern>\n"
"</filter-mapping>]]>"
msgstr ""
+"<![CDATA[<filter>\n"
+" <filter-name>Seam Filter</filter-name>\n"
+" <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>\n"
+"</filter>\n"
+"\n"
+"<filter-mapping>\n"
+" <filter-name>Seam Filter</filter-name>\n"
+" <url-pattern>/*</url-pattern>\n"
+"</filter-mapping>]]>"
#. 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."
+msgid "The Seam master filter <emphasis>must</emphasis> be the first filter specified in <literal>web.xml</literal>. This ensures it is run first."
msgstr ""
#. Tag: para
#: Configuration.xml: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:"
+msgid "The Seam filters share a number of common attributes, you can set these in <literal>components.xml</literal> in addition to any parameters discussed below:"
msgstr ""
#. Tag: para
#: Configuration.xml:111
#, no-c-format
-msgid ""
-"<literal>url-pattern</literal> — 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."
+msgid "<literal>url-pattern</literal> — Used to specify which requests are filtered, the default is all requests. <literal>url-pattern</literal> is a Tomcat style pattern which allows a wildcard suffix."
msgstr ""
#. Tag: para
#: Configuration.xml:118
#, no-c-format
-msgid ""
-"<literal>regex-url-pattern</literal> — 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."
+msgid "<literal>regex-url-pattern</literal> — 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 ""
#. Tag: para
@@ -312,10 +300,7 @@
#. 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
@@ -333,24 +318,13 @@
#. Tag: para
#: Configuration.xml:141
#, no-c-format
-msgid ""
-"This filter provides the exception mapping functionality in <literal>pages."
-"xml</literal> (almost all applications will need this). It also takes care "
-"of rolling back uncommitted transactions when uncaught exceptions occur. "
-"(According to the Java EE specification, the web container should do this "
-"automatically, but we've found that this behavior cannot be relied upon in "
-"all application servers. And it is certainly not required of plain servlet "
-"engines like Tomcat.)"
+msgid "This filter provides the exception mapping functionality in <literal>pages.xml</literal> (almost all applications will need this). It also takes care of rolling back uncommitted transactions when uncaught exceptions occur. (According to the Java EE specification, the web container should do this automatically, but we've found that this behavior cannot be relied upon in all application servers. And it is certainly not required of plain servlet engines like Tomcat.)"
msgstr ""
#. Tag: para
#: Configuration.xml:147
#, no-c-format
-msgid ""
-"By default, the exception handling filter will process all requests, however "
-"this behavior may be adjusted by adding a <literal><web:exception-"
-"filter></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><web:exception-filter></literal> entry to <literal>components.xml</literal>, as shown in this example:"
msgstr ""
#. Tag: programlisting
@@ -364,6 +338,12 @@
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:web=\"http://jboss.com/products/seam/web\">\n"
+"\n"
+" <web:exception-filter url-pattern=\"*.seam\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: title
#: Configuration.xml:157
@@ -374,55 +354,43 @@
#. 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
#: Configuration.xml:165
#, no-c-format
msgid "<![CDATA[<web:redirect-filter url-pattern=\"*.seam\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<web:redirect-filter url-pattern=\"*.seam\"/>]]>"
#. Tag: title
#: Configuration.xml:170
#, no-c-format
msgid "URL rewriting"
-msgstr ""
+msgstr "Riscrittura dell'URL"
#. 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
#: Configuration.xml:176
#, no-c-format
msgid "<![CDATA[<web:rewrite-filter view-mapping=\"*.seam\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<web:rewrite-filter view-mapping=\"*.seam\"/>]]>"
#. 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
@@ -434,11 +402,7 @@
#. Tag: para
#: Configuration.xml:187
#, no-c-format
-msgid ""
-"This feature is necessary when using the Seam file upload JSF control. It "
-"detects multipart form requests and processes them according to the "
-"multipart/form-data specification (RFC-2388). To override the default "
-"settings, add the following entry to <literal>components.xml</literal>:"
+msgid "This feature is necessary when using the Seam file upload JSF control. It detects multipart form requests and processes them according to the multipart/form-data specification (RFC-2388). To override the default settings, add the following entry to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -449,25 +413,20 @@
" max-request-size=\"1000000\" \n"
" url-pattern=\"*.seam\"/>]]>"
msgstr ""
+"<![CDATA[<web:multipart-filter create-temp-files=\"true\" \n"
+" max-request-size=\"1000000\" \n"
+" url-pattern=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:195
#, no-c-format
-msgid ""
-"<literal>create-temp-files</literal> — 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> — 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> — 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> — 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
@@ -483,11 +442,10 @@
msgstr ""
#. Tag: para
-#: Configuration.xml:214 Configuration.xml:309
+#: Configuration.xml:214
+#: Configuration.xml:309
#, no-c-format
-msgid ""
-"This filter is not installed by default and requires an entry in "
-"<literal>components.xml</literal> to enable it:"
+msgid "This filter is not installed by default and requires an entry in <literal>components.xml</literal> to enable it:"
msgstr ""
#. Tag: programlisting
@@ -498,6 +456,9 @@
" override-client=\"true\" \n"
" url-pattern=\"*.seam\"/>]]>"
msgstr ""
+"<![CDATA[<web:character-encoding-filter encoding=\"UTF-16\" \n"
+" override-client=\"true\" \n"
+" url-pattern=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:221
@@ -508,46 +469,31 @@
#. Tag: para
#: Configuration.xml:225
#, no-c-format
-msgid ""
-"<literal>override-client</literal> — 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> — If this is set to <literal>true</literal>, the request encoding will be set to whatever is specified by <literal>encoding</literal> no matter whether the request already specifies an encoding or not. If set to <literal>false</literal>, the request encoding will only be set if the request doesn't already specify an encoding. The default setting is <literal>false</literal>."
msgstr ""
#. Tag: title
#: Configuration.xml:236
#, no-c-format
msgid "RichFaces"
-msgstr ""
+msgstr "RichFaces"
#. 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
@@ -559,35 +505,27 @@
" log4j-init-file=\"custom-log4j.xml\"\n"
" url-pattern=\"*.seam\"/>]]>"
msgstr ""
+"<![CDATA[<web:ajax4jsf-filter force-parser=\"true\" \n"
+" enable-cache=\"true\" \n"
+" log4j-init-file=\"custom-log4j.xml\"\n"
+" url-pattern=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:257
#, no-c-format
-msgid ""
-"<literal>force-parser</literal> — 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> — 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> — 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> — 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> — 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> — 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
@@ -599,20 +537,13 @@
#. 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><web:logging-filter></"
-"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><web:logging-filter></literal> entry to <literal>components.xml</literal>, as shown in this example:"
msgstr ""
#. Tag: programlisting
@@ -624,6 +555,10 @@
" <web:logging-filter url-pattern=\"*.seam\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:web=\"http://jboss.com/products/seam/web\">\n"
+" <web:logging-filter url-pattern=\"*.seam\"/>\n"
+"</components>]]>"
#. Tag: title
#: Configuration.xml:298
@@ -634,46 +569,31 @@
#. 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
#: Configuration.xml:312
#, no-c-format
msgid "<![CDATA[<web:context-filter url-pattern=\"/media/*\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<web:context-filter url-pattern=\"/media/*\"/>]]>"
#. 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
@@ -685,13 +605,7 @@
#. Tag: para
#: Configuration.xml:327
#, no-c-format
-msgid ""
-"Seam can install your filters for you, allowing you to specify "
-"<emphasis>where</emphasis> in the chain your filter is placed (the servlet "
-"specification doesn't provide a well defined order if you specify your "
-"filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</"
-"literal> annotation to your Seam component (which must implement "
-"<literal>javax.servlet.Filter</literal>):"
+msgid "Seam can install your filters for you, allowing you to specify <emphasis>where</emphasis> in the chain your filter is placed (the servlet specification doesn't provide a well defined order if you specify your filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</literal> annotation to your Seam component (which must implement <literal>javax.servlet.Filter</literal>):"
msgstr ""
#. Tag: programlisting
@@ -705,16 +619,17 @@
"@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")\n"
"public class MultipartFilter extends AbstractFilter {]]>"
msgstr ""
+"<![CDATA[@Startup\n"
+"@Scope(APPLICATION)\n"
+"@Name(\"org.jboss.seam.web.multipartFilter\")\n"
+"@BypassInterceptors\n"
+"@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")\n"
+"public class MultipartFilter extends AbstractFilter {]]>"
#. 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>@Filter(within=\"org."
-"jboss.seam.web.ajax4jsfFilter\")</literal>)."
+msgid "Adding the <literal>@Startup</literal> annotation means thar the component is available during Seam startup; bijection isn't available here (<literal>@BypassInterceptors</literal>); and the filter should be further down the chain than the RichFaces filter (<literal>@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")</literal>)."
msgstr ""
#. Tag: title
@@ -726,24 +641,13 @@
#. Tag: para
#: Configuration.xml:345
#, no-c-format
-msgid ""
-"In a Seam application, EJB components have a certain duality, as they are "
-"managed by both the EJB container and Seam. Actually, it's more that Seam "
-"resolves EJB component references, manages the lifetime of stateful session "
-"bean components, and also participates in each method call via interceptors. "
-"Let's start with the configuration of the Seam interceptor chain."
+msgid "In a Seam application, EJB components have a certain duality, as they are managed by both the EJB container and Seam. Actually, it's more that Seam resolves EJB component references, manages the lifetime of stateful session bean components, and also participates in each method call via interceptors. Let's start with the configuration of the Seam interceptor chain."
msgstr ""
#. Tag: para
#: Configuration.xml:350
#, no-c-format
-msgid ""
-"We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB "
-"components. This interceptor delegates to a set of built-in server-side "
-"interceptors that handle such concerns as bijection, conversation "
-"demarcation, and business process signals. The simplest way to do this "
-"across an entire application is to add the following interceptor "
-"configuration in <literal>ejb-jar.xml</literal>:"
+msgid "We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB components. This interceptor delegates to a set of built-in server-side interceptors that handle such concerns as bijection, conversation demarcation, and business process signals. The simplest way to do this across an entire application is to add the following interceptor configuration in <literal>ejb-jar.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -752,33 +656,36 @@
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>\n"
+"</interceptors>\n"
+" \n"
+"<assembly-descriptor>\n"
+" <interceptor-binding>\n"
+" <ejb-name>*</ejb-name>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" </interceptor-binding>\n"
+"</assembly-descriptor>\n"
+"]]>"
#. 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
@@ -791,66 +698,48 @@
#: Configuration.xml:366
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"earName/#{ejbName}/local\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<core:init jndi-name=\"earName/#{ejbName}/local\" />]]>"
#. 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
#: Configuration.xml:375
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
#. 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><ejb-name></literal> element in ejb-jar.xml"
+msgid "The value of the <literal><ejb-name></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
@@ -862,9 +751,7 @@
#. Tag: para
#: Configuration.xml:397
#, no-c-format
-msgid ""
-"Let's look at an example. Assume that you have the following EJB bean and "
-"interface defined."
+msgid "Let's look at an example. Assume that you have the following EJB bean and interface defined."
msgstr ""
#. Tag: programlisting
@@ -893,40 +780,44 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[package com.example.myapp;\n"
+"\n"
+"import javax.ejb.Local;\n"
+"\n"
+"@Local\n"
+"public class Authenticator\n"
+"{\n"
+" boolean authenticate();\n"
+"}\n"
+"\n"
+"package com.example.myapp;\n"
+"\n"
+"import javax.ejb.Stateless;\n"
+"\n"
+"@Stateless\n"
+"@Name(\"authenticator\")\n"
+"public class AuthenticatorBean implements Authenticator\n"
+"{ \n"
+" public boolean authenticate() { ... }\n"
+"}\n"
+"]]>"
#. 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
@@ -940,40 +831,29 @@
"</ejb-local-ref>\n"
"]]>"
msgstr ""
+"<![CDATA[<ejb-local-ref>\n"
+" <ejb-ref-name>myapp/AuthenticatorBean/local</ejb-ref-name>\n"
+" <ejb-ref-type>Session</ejb-ref-type>\n"
+" <local>org.example.vehicles.action.Authenticator</local>\n"
+"</ejb-local-ref>\n"
+"]]>"
#. 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>, it isn't going to be successful looking up the component in JNDI. "
-"You cannot simply resolve JNDI names as you please. You have to define those "
-"references explicitly. Unlike with the web context, however, you cannot "
-"declare EJB references globally for all EJB components. Instead, you have to "
-"specify the JNDI resources for a given EJB component one-by-one (this "
-"applies to JBoss AS 5 in addition to non-JBoss application servers)."
+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>, it isn't going to be successful looking up the component in JNDI. You cannot simply resolve JNDI names as you please. You have to define those references explicitly. Unlike with the web context, however, you cannot declare EJB references globally for all EJB components. Instead, you have to specify the JNDI resources for a given EJB component one-by-one (this applies to JBoss AS 5 in addition to non-JBoss application servers)."
msgstr ""
#. Tag: para
#: Configuration.xml:433
#, 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
@@ -984,13 +864,14 @@
"Authenticator authenticator;\n"
"]]>"
msgstr ""
+"<![CDATA[@In(create = true)\n"
+"Authenticator authenticator;\n"
+"]]>"
#. Tag: para
#: Configuration.xml:438
#, 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
@@ -1002,8 +883,7 @@
" <session>\n"
" <ejb-name>RegisterAction</ejb-name>\n"
" <ejb-local-ref>\n"
-" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-"
-"name>\n"
+" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n"
" <ejb-ref-type>Session</ejb-ref-type>\n"
" <local>com.example.myapp.Authenticator</local>\n"
" </ejb-local-ref>\n"
@@ -1015,122 +895,87 @@
"</ejb-jar>\n"
"]]>"
msgstr ""
+"<![CDATA[<ejb-jar>\n"
+" <enterprise-beans>\n"
+" <session>\n"
+" <ejb-name>RegisterAction</ejb-name>\n"
+" <ejb-local-ref>\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"
+" </session>\n"
+" </enterprise-beans>\n"
+"\n"
+" ...\n"
+" \n"
+"</ejb-jar>\n"
+"]]>"
#. Tag: para
#: Configuration.xml:442
#, no-c-format
-msgid ""
-"Notice that the contents of the <literal><ejb-local-ref></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><ejb-local-ref></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:448
#, 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>@In</literal>."
+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>@In</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:458
#, 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:464
#, no-c-format
-msgid ""
-"<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]"
-">"
-msgstr ""
+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:466
#, 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
#: Configuration.xml:473
#, no-c-format
msgid "<![CDATA[<transaction:ejb-transaction/>]]>"
-msgstr ""
+msgstr "<![CDATA[<transaction:ejb-transaction/>]]>"
#. Tag: title
#: Configuration.xml:478
#, no-c-format
msgid "Don't forget!"
-msgstr ""
+msgstr "Non dimenticare!"
#. Tag: para
#: Configuration.xml:480
#, 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:485
#, 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:488
#, 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:491
#, 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—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—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
@@ -1142,85 +987,69 @@
#. Tag: para
#: Configuration.xml:504
#, 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
#: Configuration.xml:510
#, no-c-format
msgid "This is a workaround"
-msgstr ""
+msgstr "Questo è un workaround"
#. Tag: para
#: Configuration.xml:511
#, 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:518
#, 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:519
#, 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:524
#, 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"
+" class=\"org.jboss.seam.persistence.PersistenceProvider\"\n"
+" scope=\"stateless\">\n"
+"</component>]]>"
#. Tag: para
#: Configuration.xml:525
#, 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:532
#, 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"
+" class=\"org.your.package.YourPersistenceProvider\">\n"
+"</component>]]>"
#. Tag: para
#: Configuration.xml:533
#, 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
@@ -1232,24 +1061,23 @@
#. Tag: para
#: Configuration.xml:552
#, 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:555 Configuration.xml:650 Configuration.xml:788
+#: Configuration.xml:555
+#: Configuration.xml:650
+#: Configuration.xml:788
#: Configuration.xml:821
#, no-c-format
msgid "Packaging"
-msgstr ""
+msgstr "Packaging"
#. Tag: para
#: Configuration.xml:557
#, 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
@@ -1291,141 +1119,129 @@
" RegisterBean.class\n"
" ...]]>"
msgstr ""
+"<![CDATA[my-application.ear/\n"
+" jboss-seam.jar\n"
+" lib/\n"
+" jboss-el.jar\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" application.xml\n"
+" my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jsf-facelets.jar\n"
+" jboss-seam-ui.jar\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" persistence.xml\n"
+" seam.properties\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" LoginBean.class\n"
+" Register.class\n"
+" RegisterBean.class\n"
+" ...]]>"
#. Tag: para
#: Configuration.xml:562
#, 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:567
#, 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:569
#, 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:572
#, 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:577
#, 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:580
#, 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:583
#, 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
#: Configuration.xml:592
#, no-c-format
msgid "Configuring Seam in J2EE"
-msgstr ""
+msgstr "Configurare Seam in J2EE"
#. Tag: para
#: Configuration.xml:594
#, 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:609
#, 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:615
#, 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
#: Configuration.xml:620
#, no-c-format
msgid "Boostrapping Hibernate in Seam"
-msgstr ""
+msgstr "Boostrapping di Hibernate in Seam"
#. Tag: para
#: Configuration.xml:622
#, 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:625
#, no-c-format
-msgid ""
-"<![CDATA[<persistence:hibernate-session-factory name="
-"\"hibernateSessionFactory\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
+msgstr "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
#. Tag: para
#: Configuration.xml:627
#, 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
@@ -1433,40 +1249,33 @@
#, 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}\"/>]]>"
#. Tag: title
#: Configuration.xml:635
#, no-c-format
msgid "Boostrapping JPA in Seam"
-msgstr ""
+msgstr "Boostrapping di JPA in Seam"
#. Tag: para
#: Configuration.xml:637
#, 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:640
#, no-c-format
-msgid ""
-"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
+msgstr "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
#. Tag: para
#: Configuration.xml:642
#, 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
@@ -1474,9 +1283,10 @@
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
-" entity-manager-factory=\"#{entityManagerFactory}"
-"\"/>]]>"
+" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
msgstr ""
+"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
+" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
#. Tag: para
#: Configuration.xml:652
@@ -1520,13 +1330,42 @@
" register.jsp\n"
" ...]]>"
msgstr ""
+"<![CDATA[my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jboss-seam.jar\n"
+" jboss-seam-ui.jar\n"
+" jboss-el.jar\n"
+" jsf-facelets.jar\n"
+" hibernate3.jar\n"
+" hibernate-annotations.jar\n"
+" hibernate-validator.jar\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" seam.properties\n"
+" hibernate.cfg.xml\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" Register.class\n"
+" ...\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...]]>"
#. Tag: para
#: Configuration.xml:656
#, 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
@@ -1538,34 +1377,26 @@
#. Tag: para
#: Configuration.xml:665
#, 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:669
#, no-c-format
-msgid ""
-"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
+msgstr "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
#. Tag: para
#: Configuration.xml:671
#, 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:673
#, no-c-format
msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
#. Tag: para
#: Configuration.xml:675
@@ -1576,8 +1407,7 @@
#. Tag: para
#: Configuration.xml:677
#, 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
@@ -1589,18 +1419,13 @@
#. Tag: para
#: Configuration.xml:684
#, 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:687
#, 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
@@ -1618,49 +1443,31 @@
#. Tag: para
#: Configuration.xml:714
#, 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&package_id=228977\">here</ulink>. The process for "
-"installing Embedded JBoss into Tomcat 6 is quite simple. First, you should "
-"copy the Embedded JBoss JARs and configuration files into Tomcat."
+msgid "Embedded JBoss must by installed into Tomcat for Seam applications to run correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend=\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=22866&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:728
#, 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:735
#, 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:741
#, 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:747
#, 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
@@ -1669,33 +1476,36 @@
msgid ""
"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
"\n"
-" <!-- Comment these entries out to disable JMX MBeans support used for "
-"the \n"
+" <!-- Comment these entries out to disable JMX MBeans support used for the \n"
" administration web application -->\n"
" <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener"
-"\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans."
-"GlobalResourcesLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.storeconfig."
-"StoreConfigLifecycleListener\" />]]>"
+" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>"
msgstr ""
+"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
+"\n"
+" <!-- Comment these entries out to disable JMX MBeans support used for the \n"
+" 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\" />]]>"
#. Tag: programlisting
#: Configuration.xml:751
#, 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\" />]]>"
#. Tag: para
#: Configuration.xml:755
#, 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
@@ -1706,12 +1516,19 @@
" <!-- 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"
" -->]]>"
msgstr ""
+"<![CDATA[<Context>\n"
+" <!-- Default set of monitored resources -->\n"
+" <WatchedResource>WEB-INF/web.xml</WatchedResource>\n"
+" \n"
+" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n"
+" <!--\n"
+" <Manager pathname=\"\" />\n"
+" -->]]>"
#. Tag: programlisting
#: Configuration.xml:759
@@ -1720,40 +1537,32 @@
"<![CDATA[ <!-- Add this listener -->\n"
" <Listener className=\"org.jboss.embedded.tomcat.WebinfScanner\" />]]>"
msgstr ""
+"<![CDATA[ <!-- Add this listener -->\n"
+" <Listener className=\"org.jboss.embedded.tomcat.WebinfScanner\" />]]>"
#. Tag: programlisting
#: Configuration.xml:760
#, no-c-format
msgid "<![CDATA[</Context>]]>"
-msgstr ""
+msgstr "<![CDATA[</Context>]]>"
#. Tag: para
#: Configuration.xml:764
#, 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:769
#, 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:773
#, no-c-format
-msgid ""
-"<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader."
-"allowArraySyntax=true]]>"
-msgstr ""
+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:775
@@ -1764,26 +1573,19 @@
#. Tag: programlisting
#: Configuration.xml:777
#, no-c-format
-msgid ""
-"<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true"
-"\"]]>"
-msgstr ""
+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:782
#, no-c-format
-msgid ""
-"For more configuration options, please see the Embedded JBoss Tomcat "
-"integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=EmbeddedAndTomcat\">wiki entry</ulink>."
+msgid "For more configuration options, please see the Embedded JBoss Tomcat integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat\">wiki entry</ulink>."
msgstr ""
#. Tag: para
#: Configuration.xml:790
#, 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
@@ -1823,29 +1625,55 @@
" register.jsp\n"
" ...]]>"
msgstr ""
+"<![CDATA[my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jboss-seam.jar\n"
+" jboss-seam-ui.jar\n"
+" jboss-el.jar\n"
+" jsf-facelets.jar\n"
+" jsf-api.jar\n"
+" jsf-impl.jar\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" persistence.xml\n"
+" seam.properties\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" LoginBean.class\n"
+" Register.class\n"
+" RegisterBean.class\n"
+" ...\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...]]>"
#. Tag: para
#: Configuration.xml:795
#, 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
#: Configuration.xml:803
#, no-c-format
msgid "Configuring jBPM in Seam"
-msgstr ""
+msgstr "Configurazione jBPM in Seam"
#. Tag: para
#: Configuration.xml:804
#, 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
@@ -1863,16 +1691,21 @@
" </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:pageflow-definitions>\n"
+" <value>createDocument.jpdl.xml</value>\n"
+" <value>editDocument.jpdl.xml</value>\n"
+" <value>approveDocument.jpdl.xml</value>\n"
+" </bpm:pageflow-definitions>\n"
+" <bpm:process-definitions>\n"
+" <value>documentLifecycle.jpdl.xml</value>\n"
+" </bpm:process-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: para
#: Configuration.xml:810
#, 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
@@ -1884,44 +1717,51 @@
" <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>]]>"
msgstr ""
+"<![CDATA[<jbpm-configuration>\n"
+"\n"
+" <jbpm-context>\n"
+" <service name=\"persistence\">\n"
+" <factory>\n"
+" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory\">\n"
+" <field name=\"isTransactionEnabled\"><false/></field>\n"
+" </bean>\n"
+" </factory>\n"
+" </service>\n"
+" <service name=\"tx\" factory=\"org.jbpm.tx.TxServiceFactory\" />\n"
+" <service name=\"message\" factory=\"org.jbpm.msg.db.DbMessageServiceFactory\" />\n"
+" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db.DbSchedulerServiceFactory\" />\n"
+" <service name=\"logging\" factory=\"org.jbpm.logging.db.DbLoggingServiceFactory\" />\n"
+" <service name=\"authentication\" \n"
+" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n"
+" </jbpm-context>\n"
+"\n"
+"</jbpm-configuration>]]>"
#. Tag: para
#: Configuration.xml:817
#, 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:823
#, 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
@@ -1970,6 +1810,47 @@
" approveDocument.jpdl.xml\n"
" documentLifecycle.jpdl.xml]]>"
msgstr ""
+"<![CDATA[my-application.ear/\n"
+" jboss-seam.jar\n"
+" lib/\n"
+" jboss-el.jar\n"
+" jbpm-3.1.jar\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" application.xml\n"
+" my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jsf-facelets.jar\n"
+" jboss-seam-ui.jar\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" persistence.xml\n"
+" seam.properties\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" LoginBean.class\n"
+" Register.class\n"
+" RegisterBean.class\n"
+" ...\n"
+" jbpm.cfg.xml\n"
+" hibernate.cfg.xml\n"
+" createDocument.jpdl.xml\n"
+" editDocument.jpdl.xml\n"
+" approveDocument.jpdl.xml\n"
+" documentLifecycle.jpdl.xml]]>"
#. Tag: title
#: Configuration.xml:835
@@ -1980,22 +1861,13 @@
#. Tag: para
#: Configuration.xml:837
#, 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:843
#, 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
@@ -2003,8 +1875,7 @@
#, no-c-format
msgid ""
"<![CDATA[<container-cache-conf>\n"
-" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-"
-"policy>\n"
+" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>\n"
" <cache-policy-conf>\n"
" <min-capacity>50</min-capacity>\n"
" <max-capacity>1000000</max-capacity>\n"
@@ -2022,16 +1893,29 @@
" </cache-policy-conf>\n"
"</container-cache-conf>]]>"
msgstr ""
+"<![CDATA[<container-cache-conf>\n"
+" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>\n"
+" <cache-policy-conf>\n"
+" <min-capacity>50</min-capacity>\n"
+" <max-capacity>1000000</max-capacity>\n"
+" <remover-period>1800</remover-period>\n"
+"\n"
+" <!-- SFSB timeout in seconds; 1800 seconds == 30 minutes -->\n"
+" <max-bean-life>1800</max-bean-life> \n"
+"\n"
+" <overager-period>300</overager-period>\n"
+" <max-bean-age>600</max-bean-age>\n"
+" <resizer-period>400</resizer-period>\n"
+" <max-cache-miss-period>60</max-cache-miss-period>\n"
+" <min-cache-miss-period>1</min-cache-miss-period>\n"
+" <cache-load-factor>0.75</cache-load-factor>\n"
+" </cache-policy-conf>\n"
+"</container-cache-conf>]]>"
#. Tag: para
#: Configuration.xml:848
#, no-c-format
-msgid ""
-"The default HTTP session timeout can be modified in <literal>server/default/"
-"deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in "
-"<literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for "
-"JBoss 4.2.x. The following entry in this file controls the default session "
-"timeout for all web applications:"
+msgid "The default HTTP session timeout can be modified in <literal>server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in <literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for JBoss 4.2.x. The following entry in this file controls the default session timeout for all web applications:"
msgstr ""
#. Tag: programlisting
@@ -2043,13 +1927,15 @@
" <session-timeout>30</session-timeout>\n"
"</session-config>]]>"
msgstr ""
+"<![CDATA[<session-config>\n"
+" <!-- HTTP Session timeout, in minutes -->\n"
+" <session-timeout>30</session-timeout>\n"
+"</session-config>]]>"
#. Tag: para
#: Configuration.xml:855
#, 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
@@ -2061,12 +1947,7 @@
#. Tag: para
#: Configuration.xml:863
#, no-c-format
-msgid ""
-"If you want to run your Seam application in a portlet, take a look at the "
-"JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within "
-"a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://"
-"labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> "
-"for more."
+msgid "If you want to run your Seam application in a portlet, take a look at the JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> for more."
msgstr ""
#. Tag: title
@@ -2078,22 +1959,13 @@
#. Tag: para
#: Configuration.xml:876
#, 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:883
#, 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
@@ -2103,13 +1975,13 @@
"<![CDATA[# A colon-separated list of annotation types to handle\n"
"org.jboss.seam.deployment.annotationTypes=com.acme.Foo:com.acme.Bar]]>"
msgstr ""
+"<![CDATA[# A colon-separated list of annotation types to handle\n"
+"org.jboss.seam.deployment.annotationTypes=com.acme.Foo:com.acme.Bar]]>"
#. Tag: para
#: Configuration.xml:892
#, 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
@@ -2139,14 +2011,33 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"fooStartup\")\n"
+"@Scope(APPLICATION)\n"
+"@Startup\n"
+"public class FooStartup {\n"
+"\n"
+" @In(\"#{deploymentStrategy.annotatedClasses['com.acme.Foo']}\")\n"
+" private Set<Class<Object>> fooClasses;\n"
+" \n"
+" @In(\"#{hotDeploymentStrategy.annotatedClasses['com.acme.Foo']}\")\n"
+" private Set<Class<Object>> hotFooClasses;\n"
+"\n"
+" @Create\n"
+" public void create() {\n"
+" for (Class clazz : fooClasses) {\n"
+" handleClass(clazz);\n"
+" }\n"
+" for (Class clazz : hotFooClasses) {\n"
+" handleClass(clazz);\n"
+" }\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: para
#: Configuration.xml:899
#, 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
@@ -2172,21 +2063,35 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[public class FooDeploymentHandler implements DeploymentHandler {\n"
+" \n"
+" private Set<InputStream> files = new HashSet<InputStream>();\n"
+" \n"
+" public String getName() {\n"
+" return \"fooDeploymentHandler\";\n"
+" }\n"
+" \n"
+" public Set<InputStream> getFiles() {\n"
+" return files;\n"
+" }\n"
+" \n"
+" public void handle(String name, ClassLoader classLoader) {\n"
+" if (name.endsWith(\".foo.xml\")) {\n"
+" files.add(classLoader.getResourceAsStream(name));\n"
+" }\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Configuration.xml:907
#, 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:912
#, 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
@@ -2196,26 +2101,23 @@
"<![CDATA[# For standard deployment\n"
"org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n"
"# For hot deployment\n"
-"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme."
-"FooDeploymentHandler]]>"
+"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
msgstr ""
+"<![CDATA[# For standard deployment\n"
+"org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n"
+"# For hot deployment\n"
+"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
#. Tag: para
#: Configuration.xml:919
#, 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:924
#, 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
@@ -2245,3 +2147,26 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"fooStartup\")\n"
+"@Scope(APPLICATION)\n"
+"@Startup\n"
+"public class FooStartup {\n"
+"\n"
+" @In(\"#{deploymentStrategy['fooDeploymentHandler']}\")\n"
+" private MyDeploymentHandler myDeploymentHandler;\n"
+" \n"
+" @In(\"#{hotDeploymentStrategy['fooDeploymentHandler']}\")\n"
+" private MyDeploymentHandler myHotDeploymentHandler;\n"
+"\n"
+" @Create\n"
+" public void create() {\n"
+" for (InputStream is : myDeploymentHandler.getFiles()) {\n"
+" handleFooXml(is);\n"
+" }\n"
+" for (InputStream is : myHotDeploymentHandler.getFiles()) {\n"
+" handleFooXml(is);\n"
+" }\n"
+" }\n"
+"\n"
+"}]]>"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,8 +6,8 @@
"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: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-16 11:29+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -28,34 +28,19 @@
#. Tag: para
#: Conversations.xml:12
#, no-c-format
-msgid ""
-"Historically, the notion of a Seam \"conversation\" came about as a merger "
-"of three different ideas:"
+msgid "Historically, the notion of a Seam \"conversation\" came about as a merger of three different ideas:"
msgstr ""
#. Tag: para
#: Conversations.xml:19
#, no-c-format
-msgid ""
-"The idea of a <emphasis>workspace</emphasis>, which I encountered in a "
-"project for the Victorian government in 2002. In this project I was forced "
-"to implement workspace management on top of Struts, an experience I pray "
-"never to repeat."
+msgid "The idea of a <emphasis>workspace</emphasis>, which I encountered in a project for the Victorian government in 2002. In this project I was forced to implement workspace management on top of Struts, an experience I pray never to repeat."
msgstr ""
#. Tag: para
#: Conversations.xml:28
#, no-c-format
-msgid ""
-"The idea of an <emphasis>application transaction</emphasis> with optimistic "
-"semantics, and the realization that existing frameworks based around a "
-"stateless architecture could not provide effective management of extended "
-"persistence contexts. (The Hibernate team is truly fed up with copping the "
-"blame for <literal>LazyInitializationException</literal>s, which are not "
-"really Hibernate's fault, but rather the fault of the extremely limiting "
-"persistence context model supported by stateless architectures such as the "
-"Spring framework or the traditional <emphasis>stateless session facade</"
-"emphasis> (anti)pattern in J2EE.)"
+msgid "The idea of an <emphasis>application transaction</emphasis> with optimistic semantics, and the realization that existing frameworks based around a stateless architecture could not provide effective management of extended persistence contexts. (The Hibernate team is truly fed up with copping the blame for <literal>LazyInitializationException</literal>s, which are not really Hibernate's fault, but rather the fault of the extremely limiting persistence context model supported by stateless architectures such as the Spring framework or the traditional <emphasis>stateless session facade</emphasis> (anti)pattern in J2EE.)"
msgstr ""
#. Tag: para
@@ -67,116 +52,80 @@
#. Tag: para
#: Conversations.xml:49
#, no-c-format
-msgid ""
-"By unifying these ideas and providing deep support in the framework, we have "
-"a powerful construct that lets us build richer and more efficient "
-"applications with less code than before."
+msgid "By unifying these ideas and providing deep support in the framework, we have a powerful construct that lets us build richer and more efficient applications with less code than before."
msgstr ""
#. Tag: title
#: Conversations.xml:56
#, no-c-format
msgid "Seam's conversation model"
-msgstr ""
+msgstr "Il modello di conversazioni di Seam"
#. Tag: para
#: Conversations.xml:58
#, no-c-format
-msgid ""
-"The examples we have seen so far make use of a very simple conversation "
-"model that follows these rules:"
+msgid "The examples we have seen so far make use of a very simple conversation model that follows these rules:"
msgstr ""
#. Tag: para
#: Conversations.xml:65
#, no-c-format
-msgid ""
-"There is always a conversation context active during the apply request "
-"values, process validations, update model values, invoke application and "
-"render response phases of the JSF request lifecycle."
+msgid "There is always a conversation context active during the apply request values, process validations, update model values, invoke application and render response phases of the JSF request lifecycle."
msgstr ""
#. Tag: para
#: Conversations.xml:73
#, no-c-format
-msgid ""
-"At the end of the restore view phase of the JSF request lifecycle, Seam "
-"attempts to restore any previous long-running conversation context. If none "
-"exists, Seam creates a new temporary conversation context."
+msgid "At the end of the restore view phase of the JSF request lifecycle, Seam attempts to restore any previous long-running conversation context. If none exists, Seam creates a new temporary conversation context."
msgstr ""
#. Tag: para
#: Conversations.xml:81
#, no-c-format
-msgid ""
-"When an <literal>@Begin</literal> method is encountered, the temporary "
-"conversation context is promoted to a long running conversation."
+msgid "When an <literal>@Begin</literal> method is encountered, the temporary conversation context is promoted to a long running conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:88
#, no-c-format
-msgid ""
-"When an <literal>@End</literal> method is encountered, any long-running "
-"conversation context is demoted to a temporary conversation."
+msgid "When an <literal>@End</literal> method is encountered, any long-running conversation context is demoted to a temporary conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:95
#, no-c-format
-msgid ""
-"At the end of the render response phase of the JSF request lifecycle, Seam "
-"stores the contents of a long running conversation context or destroys the "
-"contents of a temporary conversation context."
+msgid "At the end of the render response phase of the JSF request lifecycle, Seam stores the contents of a long running conversation context or destroys the contents of a temporary conversation context."
msgstr ""
#. Tag: para
#: Conversations.xml:103
#, no-c-format
-msgid ""
-"Any faces request (a JSF postback) will propagate the conversation context. "
-"By default, non-faces requests (GET requests, for example) do not propagate "
-"the conversation context, but see below for more information on this."
+msgid "Any faces request (a JSF postback) will propagate the conversation context. By default, non-faces requests (GET requests, for example) do not propagate the conversation context, but see below for more information on this."
msgstr ""
#. Tag: para
#: Conversations.xml:111
#, no-c-format
-msgid ""
-"If the JSF request lifecycle is foreshortened by a redirect, Seam "
-"transparently stores and restores the current conversation context—"
-"unless the conversation was already ended via <literal>@End"
-"(beforeRedirect=true)</literal>."
+msgid "If the JSF request lifecycle is foreshortened by a redirect, Seam transparently stores and restores the current conversation context—unless the conversation was already ended via <literal>@End(beforeRedirect=true)</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:120
#, no-c-format
-msgid ""
-"Seam transparently propagates the conversation context (including the "
-"temporary conversation context) across JSF postbacks and redirects. If you "
-"don't do anything special, a <emphasis>non-faces request</emphasis> (a GET "
-"request for example) will not propagate the conversation context and will be "
-"processed in a new temporary conversation. This is usually - but not always "
-"- the desired behavior."
+msgid "Seam transparently propagates the conversation context (including the temporary conversation context) across JSF postbacks and redirects. If you don't do anything special, a <emphasis>non-faces request</emphasis> (a GET request for example) will not propagate the conversation context and will be processed in a new temporary conversation. This is usually - but not always - the desired behavior."
msgstr ""
#. Tag: para
#: Conversations.xml:129
#, no-c-format
-msgid ""
-"If you want to propagate a Seam conversation across a non-faces request, you "
-"need to explicitly code the Seam <emphasis>conversation id</emphasis> as a "
-"request parameter:"
+msgid "If you want to propagate a Seam conversation across a non-faces request, you need to explicitly code the Seam <emphasis>conversation id</emphasis> as a request parameter:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:135
#, no-c-format
-msgid ""
-"<![CDATA[<a href=\"main.jsf?#{manager.conversationIdParameter}=#"
-"{conversation.id}\">Continue</a>]]>"
-msgstr ""
+msgid "<![CDATA[<a href=\"main.jsf?#{manager.conversationIdParameter}=#{conversation.id}\">Continue</a>]]>"
+msgstr "<![CDATA[<a href=\"main.jsf?#{manager.conversationIdParameter}=#{conversation.id}\">Continue</a>]]>"
#. Tag: para
#: Conversations.xml:137
@@ -189,14 +138,18 @@
#, no-c-format
msgid ""
"<![CDATA[<h:outputLink value=\"main.jsf\">\n"
-" <f:param name=\"#{manager.conversationIdParameter}\" value=\"#"
-"{conversation.id}\"/>\n"
+" <f:param name=\"#{manager.conversationIdParameter}\" value=\"#{conversation.id}\"/>\n"
" <h:outputText value=\"Continue\"/>\n"
"</h:outputLink>]]>"
msgstr ""
+"<![CDATA[<h:outputLink value=\"main.jsf\">\n"
+" <f:param name=\"#{manager.conversationIdParameter}\" value=\"#{conversation.id}\"/>\n"
+" <h:outputText value=\"Continue\"/>\n"
+"</h:outputLink>]]>"
#. Tag: para
-#: Conversations.xml:143 Conversations.xml:156
+#: Conversations.xml:143
+#: Conversations.xml:156
#, no-c-format
msgid "If you use the Seam tag library, this is equivalent:"
msgstr ""
@@ -210,13 +163,15 @@
" <h:outputText value=\"Continue\"/>\n"
"</h:outputLink>]]>"
msgstr ""
+"<![CDATA[<h:outputLink value=\"main.jsf\">\n"
+" <s:conversationId/>\n"
+" <h:outputText value=\"Continue\"/>\n"
+"</h:outputLink>]]>"
#. Tag: para
#: Conversations.xml:149
#, no-c-format
-msgid ""
-"If you wish to disable propagation of the conversation context for a "
-"postback, a similar trick is used:"
+msgid "If you wish to disable propagation of the conversation context for a postback, a similar trick is used:"
msgstr ""
#. Tag: programlisting
@@ -227,6 +182,9 @@
" <f:param name=\"conversationPropagation\" value=\"none\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Exit\">\n"
+" <f:param name=\"conversationPropagation\" value=\"none\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:160
@@ -236,22 +194,20 @@
" <s:conversationPropagation type=\"none\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Exit\">\n"
+" <s:conversationPropagation type=\"none\"/>\n"
+"</h:commandLink>]]>"
#. Tag: para
#: Conversations.xml:162
#, no-c-format
-msgid ""
-"Note that disabling conversation context propagation is absolutely not the "
-"same thing as ending the conversation."
+msgid "Note that disabling conversation context propagation is absolutely not the same thing as ending the conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:167
#, no-c-format
-msgid ""
-"The <literal>conversationPropagation</literal> request parameter, or the "
-"<literal><s:conversationPropagation></literal> tag may even be used to "
-"begin and end conversation, or begin a nested conversation."
+msgid "The <literal>conversationPropagation</literal> request parameter, or the <literal><s:conversationPropagation></literal> tag may even be used to begin and end conversation, or begin a nested conversation."
msgstr ""
#. Tag: programlisting
@@ -262,6 +218,9 @@
" <s:conversationPropagation type=\"end\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Exit\">\n"
+" <s:conversationPropagation type=\"end\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:176
@@ -271,6 +230,9 @@
" <s:conversationPropagation type=\"nested\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Select Child\">\n"
+" <s:conversationPropagation type=\"nested\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:178
@@ -280,6 +242,9 @@
" <s:conversationPropagation type=\"begin\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Select Hotel\">\n"
+" <s:conversationPropagation type=\"begin\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:180
@@ -289,34 +254,26 @@
" <s:conversationPropagation type=\"join\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Select Hotel\">\n"
+" <s:conversationPropagation type=\"join\"/>\n"
+"</h:commandLink>]]>"
#. Tag: para
#: Conversations.xml:182
#, no-c-format
-msgid ""
-"This conversation model makes it easy to build applications which behave "
-"correctly with respect to multi-window operation. For many applications, "
-"this is all that is needed. Some complex applications have either or both of "
-"the following additional requirements:"
+msgid "This conversation model makes it easy to build applications which behave correctly with respect to multi-window operation. For many applications, this is all that is needed. Some complex applications have either or both of the following additional requirements:"
msgstr ""
#. Tag: para
#: Conversations.xml:191
#, no-c-format
-msgid ""
-"A conversation spans many smaller units of user interaction, which execute "
-"serially or even concurrently. The smaller <emphasis>nested conversations</"
-"emphasis> have their own isolated set of conversation state, and also have "
-"access to the state of the outer conversation."
+msgid "A conversation spans many smaller units of user interaction, which execute serially or even concurrently. The smaller <emphasis>nested conversations</emphasis> have their own isolated set of conversation state, and also have access to the state of the outer conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:200
#, no-c-format
-msgid ""
-"The user is able to switch between many conversations within the same "
-"browser window. This feature is called <emphasis>workspace management</"
-"emphasis>."
+msgid "The user is able to switch between many conversations within the same browser window. This feature is called <emphasis>workspace management</emphasis>."
msgstr ""
#. Tag: title
@@ -328,97 +285,55 @@
#. Tag: para
#: Conversations.xml:213
#, no-c-format
-msgid ""
-"A nested conversation is created by invoking a method marked <literal>@Begin"
-"(nested=true)</literal> inside the scope of an existing conversation. A "
-"nested conversation has its own conversation context, but can read values "
-"from the outer conversation's context. The outer conversation's context is "
-"read-only within a nested conversation, but because objects are obtained by "
-"reference, changes to the objects themselves will be reflected in the outer "
-"context."
+msgid "A nested conversation is created by invoking a method marked <literal>@Begin(nested=true)</literal> inside the scope of an existing conversation. A nested conversation has its own conversation context, but can read values from the outer conversation's context. The outer conversation's context is read-only within a nested conversation, but because objects are obtained by reference, changes to the objects themselves will be reflected in the outer context."
msgstr ""
#. Tag: para
#: Conversations.xml:226
#, no-c-format
-msgid ""
-"Nesting a conversation through initializes a context that is stacked on the "
-"context of the original, or outer, conversation. The outer conversation is "
-"considered the parent."
+msgid "Nesting a conversation through initializes a context that is stacked on the context of the original, or outer, conversation. The outer conversation is considered the parent."
msgstr ""
#. Tag: para
#: Conversations.xml:233
#, no-c-format
-msgid ""
-"Any values outjected or directly set into the nested conversation’s context "
-"do not affect the objects accessible in the parent conversation’s context."
+msgid "Any values outjected or directly set into the nested conversation’s context do not affect the objects accessible in the parent conversation’s context."
msgstr ""
#. Tag: para
#: Conversations.xml:240
#, no-c-format
-msgid ""
-"Injection or a context lookup from the conversation context will first "
-"lookup the value in the current conversation context and, if no value is "
-"found, will proceed down the conversation stack if the conversation is "
-"nested. As you will see in moment, this behavior can be overriden."
+msgid "Injection or a context lookup from the conversation context will first lookup the value in the current conversation context and, if no value is found, will proceed down the conversation stack if the conversation is nested. As you will see in moment, this behavior can be overriden."
msgstr ""
#. Tag: para
#: Conversations.xml:250
#, no-c-format
-msgid ""
-"When an <literal>@End</literal> is subsequently encountered, the nested "
-"conversation will be destroyed, and the outer conversation will resume, by "
-"\"popping\" the conversation stack. Conversations may be nested to any "
-"arbitrary depth."
+msgid "When an <literal>@End</literal> is subsequently encountered, the nested conversation will be destroyed, and the outer conversation will resume, by \"popping\" the conversation stack. Conversations may be nested to any arbitrary depth."
msgstr ""
#. Tag: para
#: Conversations.xml:257
#, no-c-format
-msgid ""
-"Certain user activity (workspace management, or the back button) can cause "
-"the outer conversation to be resumed before the inner conversation is ended. "
-"In this case it is possible to have multiple concurrent nested conversations "
-"belonging to the same outer conversation. If the outer conversation ends "
-"before a nested conversation ends, Seam destroys all nested conversation "
-"contexts along with the outer context."
+msgid "Certain user activity (workspace management, or the back button) can cause the outer conversation to be resumed before the inner conversation is ended. In this case it is possible to have multiple concurrent nested conversations belonging to the same outer conversation. If the outer conversation ends before a nested conversation ends, Seam destroys all nested conversation contexts along with the outer context."
msgstr ""
#. Tag: para
#: Conversations.xml:267
#, no-c-format
-msgid ""
-"The conversation at the bottom of the conversation stack is the root "
-"conversation. Destroying this conversation always destroy all of its "
-"descendents. You can achieve this declaratively by specifying <literal>@End"
-"(root=true)</literal>."
+msgid "The conversation at the bottom of the conversation stack is the root conversation. Destroying this conversation always destroy all of its descendents. You can achieve this declaratively by specifying <literal>@End(root=true)</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:274
#, no-c-format
-msgid ""
-"A conversation may be thought of as a <emphasis>continuable state</"
-"emphasis>. Nested conversations allow the application to capture a "
-"consistent continuable state at various points in a user interaction, thus "
-"ensuring truly correct behavior in the face of backbuttoning and workspace "
-"management."
+msgid "A conversation may be thought of as a <emphasis>continuable state</emphasis>. Nested conversations allow the application to capture a consistent continuable state at various points in a user interaction, thus ensuring truly correct behavior in the face of backbuttoning and workspace management."
msgstr ""
#. Tag: para
#: Conversations.xml:282
#, no-c-format
-msgid ""
-"As mentioned previously, if a component exists in a parent conversation of "
-"the current nested conversation, the nested conversation will use the same "
-"instance. Occasionally, it is useful to have a different instance in each "
-"nested conversation, so that the component instance that exists in the "
-"parent conversation is invisible to its child conversations. You can achieve "
-"this behavior by annotating the component <literal>@PerNestedConversation</"
-"literal>."
+msgid "As mentioned previously, if a component exists in a parent conversation of the current nested conversation, the nested conversation will use the same instance. Occasionally, it is useful to have a different instance in each nested conversation, so that the component instance that exists in the parent conversation is invisible to its child conversations. You can achieve this behavior by annotating the component <literal>@PerNestedConversation</literal>."
msgstr ""
#. Tag: title
@@ -430,39 +345,25 @@
#. Tag: para
#: Conversations.xml:296
#, no-c-format
-msgid ""
-"JSF does not define any kind of action listener that is triggered when a "
-"page is accessed via a non-faces request (for example, a HTTP GET request). "
-"This can occur if the user bookmarks the page, or if we navigate to the page "
-"via an <literal><h:outputLink></literal>."
+msgid "JSF does not define any kind of action listener that is triggered when a page is accessed via a non-faces request (for example, a HTTP GET request). This can occur if the user bookmarks the page, or if we navigate to the page via an <literal><h:outputLink></literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:303
#, no-c-format
-msgid ""
-"Sometimes we want to begin a conversation immediately the page is accessed. "
-"Since there is no JSF action method, we can't solve the problem in the usual "
-"way, by annotating the action with <literal>@Begin</literal>."
+msgid "Sometimes we want to begin a conversation immediately the page is accessed. Since there is no JSF action method, we can't solve the problem in the usual way, by annotating the action with <literal>@Begin</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:309
#, no-c-format
-msgid ""
-"A further problem arises if the page needs some state to be fetched into a "
-"context variable. We've already seen two ways to solve this problem. If that "
-"state is held in a Seam component, we can fetch the state in a "
-"<literal>@Create</literal> method. If not, we can define a "
-"<literal>@Factory</literal> method for the context variable."
+msgid "A further problem arises if the page needs some state to be fetched into a context variable. We've already seen two ways to solve this problem. If that state is held in a Seam component, we can fetch the state in a <literal>@Create</literal> method. If not, we can define a <literal>@Factory</literal> method for the context variable."
msgstr ""
#. Tag: para
#: Conversations.xml:317
#, no-c-format
-msgid ""
-"If none of these options works for you, Seam lets you define a "
-"<emphasis>page action</emphasis> in the <literal>pages.xml</literal> file."
+msgid "If none of these options works for you, Seam lets you define a <emphasis>page action</emphasis> in the <literal>pages.xml</literal> file."
msgstr ""
#. Tag: programlisting
@@ -474,24 +375,21 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/messageList.jsp\" action=\"#{messageManager.list}\"/>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:325
#, no-c-format
-msgid ""
-"This action method is called at the beginning of the render response phase, "
-"any time the page is about to be rendered. If a page action returns a non-"
-"null outcome, Seam will process any appropriate JSF and Seam navigation "
-"rules, possibly resulting in a completely different page being rendered."
+msgid "This action method is called at the beginning of the render response phase, any time the page is about to be rendered. If a page action returns a non-null outcome, Seam will process any appropriate JSF and Seam navigation rules, possibly resulting in a completely different page being rendered."
msgstr ""
#. Tag: para
#: Conversations.xml:333
#, no-c-format
-msgid ""
-"If <emphasis>all</emphasis> you want to do before rendering the page is "
-"begin a conversation, you could use a built-in action method that does just "
-"that:"
+msgid "If <emphasis>all</emphasis> you want to do before rendering the page is begin a conversation, you could use a built-in action method that does just that:"
msgstr ""
#. Tag: programlisting
@@ -503,23 +401,21 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/messageList.jsp\" action=\"#{conversation.begin}\"/>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:341
#, no-c-format
-msgid ""
-"Note that you can also call this built-in action from a JSF control, and, "
-"similarly, you can use <literal>#{conversation.end}</literal> to end "
-"conversations."
+msgid "Note that you can also call this built-in action from a JSF control, and, similarly, you can use <literal>#{conversation.end}</literal> to end conversations."
msgstr ""
#. Tag: para
#: Conversations.xml:347
#, no-c-format
-msgid ""
-"If you want more control, to join existing conversations or begin a nested "
-"conversion, to begin a pageflow or an atomic conversation, you should use "
-"the <literal><begin-conversation></literal> element."
+msgid "If you want more control, to join existing conversations or begin a nested conversion, to begin a pageflow or an atomic conversation, you should use the <literal><begin-conversation></literal> element."
msgstr ""
#. Tag: programlisting
@@ -533,6 +429,12 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/messageList.jsp\">\n"
+" <begin-conversation nested=\"true\" pageflow=\"AddItem\"/>\n"
+" <page>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:356
@@ -551,6 +453,12 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/home.jsp\">\n"
+" <end-conversation/>\n"
+" <page>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:363
@@ -561,16 +469,13 @@
#. Tag: para
#: Conversations.xml:369
#, no-c-format
-msgid ""
-"Annotate the <literal>@Create</literal> method with <literal>@Begin</literal>"
+msgid "Annotate the <literal>@Create</literal> method with <literal>@Begin</literal>"
msgstr ""
#. Tag: para
#: Conversations.xml:375
#, no-c-format
-msgid ""
-"Annotate the <literal>@Factory</literal> method with <literal>@Begin</"
-"literal>"
+msgid "Annotate the <literal>@Factory</literal> method with <literal>@Begin</literal>"
msgstr ""
#. Tag: para
@@ -582,76 +487,49 @@
#. Tag: para
#: Conversations.xml:387
#, no-c-format
-msgid ""
-"Use <literal><begin-conversation></literal> in <literal>pages.xml</"
-"literal>."
+msgid "Use <literal><begin-conversation></literal> in <literal>pages.xml</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:393
#, no-c-format
-msgid ""
-"Use <literal>#{conversation.begin}</literal> as the Seam page action method"
+msgid "Use <literal>#{conversation.begin}</literal> as the Seam page action method"
msgstr ""
#. Tag: title
#: Conversations.xml:403
#, no-c-format
-msgid ""
-"Using <literal><s:link></literal> and <literal><s:button></"
-"literal>"
+msgid "Using <literal><s:link></literal> and <literal><s:button></literal>"
msgstr ""
#. Tag: para
#: Conversations.xml:405
#, no-c-format
-msgid ""
-"JSF command links always perform a form submission via JavaScript, which "
-"breaks the web browser's \"open in new window\" or \"open in new tab\" "
-"feature. In plain JSF, you need to use an <literal><h:outputLink></"
-"literal> if you need this functionality. But there are two major limitations "
-"to <literal><h:outputLink></literal>."
+msgid "JSF command links always perform a form submission via JavaScript, which breaks the web browser's \"open in new window\" or \"open in new tab\" feature. In plain JSF, you need to use an <literal><h:outputLink></literal> if you need this functionality. But there are two major limitations to <literal><h:outputLink></literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:415
#, no-c-format
-msgid ""
-"JSF provides no way to attach an action listener to an <literal><h:"
-"outputLink></literal>."
+msgid "JSF provides no way to attach an action listener to an <literal><h:outputLink></literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:421
#, no-c-format
-msgid ""
-"JSF does not propagate the selected row of a <literal>DataModel</literal> "
-"since there is no actual form submission."
+msgid "JSF does not propagate the selected row of a <literal>DataModel</literal> since there is no actual form submission."
msgstr ""
#. Tag: para
#: Conversations.xml:428
#, no-c-format
-msgid ""
-"Seam provides the notion of a <emphasis>page action</emphasis> to help solve "
-"the first problem, but this does nothing to help us with the second problem. "
-"We <emphasis>could</emphasis> work around this by using the RESTful approach "
-"of passing a request parameter and requerying for the selected object on the "
-"server side. In some cases—such as the Seam blog example "
-"application—this is indeed the best approach. The RESTful style "
-"supports bookmarking, since it does not require server-side state. In other "
-"cases, where we don't care about bookmarks, the use of <literal>@DataModel</"
-"literal> and <literal>@DataModelSelection</literal> is just so convenient "
-"and transparent!"
+msgid "Seam provides the notion of a <emphasis>page action</emphasis> to help solve the first problem, but this does nothing to help us with the second problem. We <emphasis>could</emphasis> work around this by using the RESTful approach of passing a request parameter and requerying for the selected object on the server side. In some cases—such as the Seam blog example application—this is indeed the best approach. The RESTful style supports bookmarking, since it does not require server-side state. In other cases, where we don't care about bookmarks, the use of <literal>@DataModel</literal> and <literal>@DataModelSelection</literal> is just so convenient and transparent!"
msgstr ""
#. Tag: para
#: Conversations.xml:441
#, no-c-format
-msgid ""
-"To fill in this missing functionality, and to make conversation propagation "
-"even simpler to manage, Seam provides the <literal><s:link></literal> "
-"JSF tag."
+msgid "To fill in this missing functionality, and to make conversation propagation even simpler to manage, Seam provides the <literal><s:link></literal> JSF tag."
msgstr ""
#. Tag: para
@@ -664,54 +542,43 @@
#: Conversations.xml:451
#, no-c-format
msgid "<![CDATA[<s:link view=\"/login.xhtml\" value=\"Login\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:link view=\"/login.xhtml\" value=\"Login\"/>]]>"
#. Tag: para
#: Conversations.xml:453
#, no-c-format
-msgid ""
-"Or, it may specify an action method (in which case the action outcome "
-"determines the page that results):"
+msgid "Or, it may specify an action method (in which case the action outcome determines the page that results):"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:458
#, no-c-format
msgid "<![CDATA[<s:link action=\"#{login.logout}\" value=\"Logout\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:link action=\"#{login.logout}\" value=\"Logout\"/>]]>"
#. Tag: para
#: Conversations.xml:460
#, no-c-format
-msgid ""
-"If you specify <emphasis>both</emphasis> a JSF view id and an action method, "
-"the 'view' will be used <emphasis>unless</emphasis> the action method "
-"returns a non-null outcome:"
+msgid "If you specify <emphasis>both</emphasis> a JSF view id and an action method, the 'view' will be used <emphasis>unless</emphasis> the action method returns a non-null outcome:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:466
#, no-c-format
-msgid ""
-"<![CDATA[<s:link view=\"/loggedOut.xhtml\" action=\"#{login.logout}\" value="
-"\"Logout\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<s:link view=\"/loggedOut.xhtml\" action=\"#{login.logout}\" value=\"Logout\"/>]]>"
+msgstr "<![CDATA[<s:link view=\"/loggedOut.xhtml\" action=\"#{login.logout}\" value=\"Logout\"/>]]>"
#. Tag: para
#: Conversations.xml:468
#, no-c-format
-msgid ""
-"The link automatically propagates the selected row of a <literal>DataModel</"
-"literal> using inside <literal><h:dataTable></literal>:"
+msgid "The link automatically propagates the selected row of a <literal>DataModel</literal> using inside <literal><h:dataTable></literal>:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:473
#, no-c-format
-msgid ""
-"<![CDATA[<s:link view=\"/hotel.xhtml\" action=\"#{hotelSearch.selectHotel}\" "
-"value=\"#{hotel.name}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<s:link view=\"/hotel.xhtml\" action=\"#{hotelSearch.selectHotel}\" value=\"#{hotel.name}\"/>]]>"
+msgstr "<![CDATA[<s:link view=\"/hotel.xhtml\" action=\"#{hotelSearch.selectHotel}\" value=\"#{hotel.name}\"/>]]>"
#. Tag: para
#: Conversations.xml:475
@@ -723,7 +590,7 @@
#: Conversations.xml:479
#, no-c-format
msgid "<![CDATA[<s:link view=\"/main.xhtml\" propagation=\"none\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:link view=\"/main.xhtml\" propagation=\"none\"/>]]>"
#. Tag: para
#: Conversations.xml:481
@@ -734,42 +601,36 @@
#. Tag: programlisting
#: Conversations.xml:485
#, no-c-format
-msgid ""
-"<![CDATA[<s:link action=\"#{issueEditor.viewComment}\" propagation=\"nest\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<s:link action=\"#{issueEditor.viewComment}\" propagation=\"nest\"/>]]>"
+msgstr "<![CDATA[<s:link action=\"#{issueEditor.viewComment}\" propagation=\"nest\"/>]]>"
#. Tag: para
#: Conversations.xml:487
#, no-c-format
-msgid ""
-"If the link begins a conversation, you can even specify a pageflow to be "
-"used:"
+msgid "If the link begins a conversation, you can even specify a pageflow to be used:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:491
#, no-c-format
msgid ""
-"<![CDATA[<s:link action=\"#{documentEditor.getDocument}\" propagation=\"begin"
-"\"\n"
+"<![CDATA[<s:link action=\"#{documentEditor.getDocument}\" propagation=\"begin\"\n"
" pageflow=\"EditDocument\"/>]]>"
msgstr ""
+"<![CDATA[<s:link action=\"#{documentEditor.getDocument}\" propagation=\"begin\"\n"
+" pageflow=\"EditDocument\"/>]]>"
#. Tag: para
#: Conversations.xml:493
#, no-c-format
-msgid ""
-"The <literal>taskInstance</literal> attribute if for use in jBPM task lists:"
+msgid "The <literal>taskInstance</literal> attribute if for use in jBPM task lists:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:497
#, no-c-format
-msgid ""
-"<![CDATA[<s:link action=\"#{documentApproval.approveOrReject}\" taskInstance="
-"\"#{task}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<s:link action=\"#{documentApproval.approveOrReject}\" taskInstance=\"#{task}\"/>]]>"
+msgstr "<![CDATA[<s:link action=\"#{documentApproval.approveOrReject}\" taskInstance=\"#{task}\"/>]]>"
#. Tag: para
#: Conversations.xml:499
@@ -780,16 +641,14 @@
#. Tag: para
#: Conversations.xml:503
#, no-c-format
-msgid ""
-"Finally, if you need the \"link\" to be rendered as a button, use "
-"<literal><s:button></literal>:"
+msgid "Finally, if you need the \"link\" to be rendered as a button, use <literal><s:button></literal>:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:507
#, no-c-format
msgid "<![CDATA[<s:button action=\"#{login.logout}\" value=\"Logout\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:button action=\"#{login.logout}\" value=\"Logout\"/>]]>"
#. Tag: title
#: Conversations.xml:512
@@ -800,22 +659,13 @@
#. Tag: para
#: Conversations.xml:513
#, no-c-format
-msgid ""
-"It is quite common to display a message to the user indicating success or "
-"failure of an action. It is convenient to use a JSF <literal>FacesMessage</"
-"literal> for this. Unfortunately, a successful action often requires a "
-"browser redirect, and JSF does not propagate faces messages across "
-"redirects. This makes it quite difficult to display success messages in "
-"plain JSF."
+msgid "It is quite common to display a message to the user indicating success or failure of an action. It is convenient to use a JSF <literal>FacesMessage</literal> for this. Unfortunately, a successful action often requires a browser redirect, and JSF does not propagate faces messages across redirects. This makes it quite difficult to display success messages in plain JSF."
msgstr ""
#. Tag: para
#: Conversations.xml:522
#, no-c-format
-msgid ""
-"The built in conversation-scoped Seam component named "
-"<literal>facesMessages</literal> solves this problem. (You must have the "
-"Seam redirect filter installed.)"
+msgid "The built in conversation-scoped Seam component named <literal>facesMessages</literal> solves this problem. (You must have the Seam redirect filter installed.)"
msgstr ""
#. Tag: programlisting
@@ -835,15 +685,23 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"editDocumentAction\")\n"
+"@Stateless\n"
+"public class EditDocumentBean implements EditDocument {\n"
+" @In EntityManager em;\n"
+" @In Document document;\n"
+" @In FacesMessages facesMessages;\n"
+" \n"
+" public String update() {\n"
+" em.merge(document);\n"
+" facesMessages.add(\"Document updated\");\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Conversations.xml:530
#, no-c-format
-msgid ""
-"Any message added to <literal>facesMessages</literal> is used in the very "
-"next render response phase for the current conversation. This even works "
-"when there is no long-running conversation since Seam preserves even "
-"temporary conversation contexts across redirects."
+msgid "Any message added to <literal>facesMessages</literal> is used in the very next render response phase for the current conversation. This even works when there is no long-running conversation since Seam preserves even temporary conversation contexts across redirects."
msgstr ""
#. Tag: para
@@ -855,9 +713,8 @@
#. Tag: programlisting
#: Conversations.xml:542
#, no-c-format
-msgid ""
-"<![CDATA[facesMessages.add(\"Document #{document.title} was updated\");]]>"
-msgstr ""
+msgid "<![CDATA[facesMessages.add(\"Document #{document.title} was updated\");]]>"
+msgstr "<![CDATA[facesMessages.add(\"Document #{document.title} was updated\");]]>"
#. Tag: para
#: Conversations.xml:544
@@ -869,7 +726,7 @@
#: Conversations.xml:548
#, no-c-format
msgid "<![CDATA[<h:messages globalOnly=\"true\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<h:messages globalOnly=\"true\"/>]]>"
#. Tag: title
#: Conversations.xml:553
@@ -880,10 +737,7 @@
#. Tag: para
#: Conversations.xml:554
#, no-c-format
-msgid ""
-"When working with conversations that deal with persistent objects, it may be "
-"desirable to use the natural business key of the object instead of the "
-"standard, \"surrogate\" conversation id:"
+msgid "When working with conversations that deal with persistent objects, it may be desirable to use the natural business key of the object instead of the standard, \"surrogate\" conversation id:"
msgstr ""
#. Tag: emphasis
@@ -895,23 +749,13 @@
#. Tag: para
#: Conversations.xml:563
#, no-c-format
-msgid ""
-"It can be useful to redirect to an existing conversation if the user "
-"requests the same operation twice. Take this example: <quote> You are on "
-"ebay, half way through paying for an item you just won as a Christmas "
-"present for your parents. Lets say you're sending it straight to them - you "
-"enter your payment details but you can't remember their address. You "
-"accidentally reuse the same browser window finding out their address. Now "
-"you need to return to the payment for the item. </quote>"
+msgid "It can be useful to redirect to an existing conversation if the user requests the same operation twice. Take this example: <quote> You are on ebay, half way through paying for an item you just won as a Christmas present for your parents. Lets say you're sending it straight to them - you enter your payment details but you can't remember their address. You accidentally reuse the same browser window finding out their address. Now you need to return to the payment for the item. </quote>"
msgstr ""
#. Tag: para
#: Conversations.xml:576
#, no-c-format
-msgid ""
-"With a natural conversation its really easy to have the user rejoin the "
-"existing conversation, and pick up where they left off - just have them to "
-"rejoin the payForItem conversation with the itemId as the conversation id."
+msgid "With a natural conversation its really easy to have the user rejoin the existing conversation, and pick up where they left off - just have them to rejoin the payForItem conversation with the itemId as the conversation id."
msgstr ""
#. Tag: emphasis
@@ -923,30 +767,20 @@
#. Tag: para
#: Conversations.xml:587
#, no-c-format
-msgid ""
-"For me this consists of a navigable hierarchy (I can navigate by editing the "
-"url) and a meaningful URL (like this Wiki uses - so don't identify things by "
-"random ids). For some applications user friendly URLs are less important, of "
-"course."
+msgid "For me this consists of a navigable hierarchy (I can navigate by editing the url) and a meaningful URL (like this Wiki uses - so don't identify things by random ids). For some applications user friendly URLs are less important, of course."
msgstr ""
#. Tag: para
#: Conversations.xml:595
#, no-c-format
-msgid ""
-"With a natural conversations, when you are building your hotel booking "
-"system (or, of course, whatever your app is) you can generate a URL like "
-"<literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> "
-"(of course, whatever parameter <literal>hotel</literal> maps to on your "
-"domain model must be unique) and with URLRewrite easily transform this to "
-"http://seam-hotels/book/BestWesternAntwerpen."
+msgid "With a natural conversations, when you are building your hotel booking system (or, of course, whatever your app is) you can generate a URL like <literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> (of course, whatever parameter <literal>hotel</literal> maps to on your domain model must be unique) and with URLRewrite easily transform this to http://seam-hotels/book/BestWesternAntwerpen."
msgstr ""
#. Tag: para
#: Conversations.xml:606
#, no-c-format
msgid "Much better!"
-msgstr ""
+msgstr "Molto meglio!"
#. Tag: title
#: Conversations.xml:612
@@ -968,66 +802,57 @@
" parameter-name=\"auctionId\"\n"
" parameter-value=\"#{auction.auctionId}\"/>]]>"
msgstr ""
+"<![CDATA[ <conversation name=\"PlaceBid\"\n"
+" parameter-name=\"auctionId\"\n"
+" parameter-value=\"#{auction.auctionId}\"/>]]>"
#. Tag: para
#: Conversations.xml:619
#, no-c-format
-msgid ""
-"The first thing to note from the above definition is that the conversation "
-"has a name, in this case <literal>PlaceBid</literal>. This name uniquely "
-"identifies this particular named conversation, and is used by the "
-"<literal>page</literal> definition to identify a named conversation to "
-"participate in."
+msgid "The first thing to note from the above definition is that the conversation has a name, in this case <literal>PlaceBid</literal>. This name uniquely identifies this particular named conversation, and is used by the <literal>page</literal> definition to identify a named conversation to participate in."
msgstr ""
#. Tag: para
#: Conversations.xml:627
#, no-c-format
-msgid ""
-"The next attribute, <literal>parameter-name</literal> defines the request "
-"parameter that will contain the natural conversation id, in place of the "
-"default conversation id parameter. In this example, the <literal>parameter-"
-"name</literal> is <literal>auctionId</literal>. This means that instead of a "
-"conversation parameter like <literal>cid=123</literal> appearing in the URL "
-"for your page, it will contain <literal>auctionId=765432</literal> instead."
+msgid "The next attribute, <literal>parameter-name</literal> defines the request parameter that will contain the natural conversation id, in place of the default conversation id parameter. In this example, the <literal>parameter-name</literal> is <literal>auctionId</literal>. This means that instead of a conversation parameter like <literal>cid=123</literal> appearing in the URL for your page, it will contain <literal>auctionId=765432</literal> instead."
msgstr ""
#. Tag: para
#: Conversations.xml:636
#, no-c-format
-msgid ""
-"The last attribute in the above configuration, <literal>parameter-value</"
-"literal>, defines an EL expression used to evaluate the value of the natural "
-"business key to use as the conversation id. In this example, the "
-"conversation id will be the primary key value of the <literal>auction</"
-"literal> instance currently in scope."
+msgid "The last attribute in the above configuration, <literal>parameter-value</literal>, defines an EL expression used to evaluate the value of the natural business key to use as the conversation id. In this example, the conversation id will be the primary key value of the <literal>auction</literal> instance currently in scope."
msgstr ""
#. Tag: para
#: Conversations.xml:643
#, no-c-format
-msgid ""
-"Next, we define which pages will participate in the named conversation. This "
-"is done by specifying the <literal>conversation</literal> attribute for a "
-"<literal>page</literal> definition:"
+msgid "Next, we define which pages will participate in the named conversation. This is done by specifying the <literal>conversation</literal> attribute for a <literal>page</literal> definition:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:649
#, no-c-format
msgid ""
-"<![CDATA[ <page view-id=\"/bid.xhtml\" conversation=\"PlaceBid\" login-"
-"required=\"true\">\n"
+"<![CDATA[ <page view-id=\"/bid.xhtml\" conversation=\"PlaceBid\" login-required=\"true\">\n"
" <navigation from-action=\"#{bidAction.confirmBid}\"> \n"
" <rule if-outcome=\"success\">\n"
" <redirect view-id=\"/auction.xhtml\">\n"
-" <param name=\"id\" value=\"#{bidAction.bid.auction."
-"auctionId}\"/>\n"
+" <param name=\"id\" value=\"#{bidAction.bid.auction.auctionId}\"/>\n"
" </redirect>\n"
" </rule> \n"
" </navigation>\n"
" </page>]]>"
msgstr ""
+"<![CDATA[ <page view-id=\"/bid.xhtml\" conversation=\"PlaceBid\" login-required=\"true\">\n"
+" <navigation from-action=\"#{bidAction.confirmBid}\"> \n"
+" <rule if-outcome=\"success\">\n"
+" <redirect view-id=\"/auction.xhtml\">\n"
+" <param name=\"id\" value=\"#{bidAction.bid.auction.auctionId}\"/>\n"
+" </redirect>\n"
+" </rule> \n"
+" </navigation>\n"
+" </page>]]>"
#. Tag: title
#: Conversations.xml:654
@@ -1038,10 +863,7 @@
#. Tag: para
#: Conversations.xml:656
#, no-c-format
-msgid ""
-"When starting, or redirecting to, a natural conversation there are a number "
-"of options for specifying the natural conversation name. Let's start by "
-"looking at the following page definition:"
+msgid "When starting, or redirecting to, a natural conversation there are a number of options for specifying the natural conversation name. Let's start by looking at the following page definition:"
msgstr ""
#. Tag: programlisting
@@ -1056,17 +878,18 @@
" </navigation>\n"
" </page>]]>"
msgstr ""
+"<![CDATA[ <page view-id=\"/auction.xhtml\">\n"
+" <param name=\"id\" value=\"#{auctionDetail.selectedAuctionId}\"/>\n"
+" \n"
+" <navigation from-action=\"#{bidAction.placeBid}\">\n"
+" <redirect view-id=\"/bid.xhtml\"/>\n"
+" </navigation>\n"
+" </page>]]>"
#. Tag: para
#: Conversations.xml:664
#, no-c-format
-msgid ""
-"From here, we can see that invoking the action <literal>#{bidAction.placeBid}"
-"</literal> from our auction view (by the way, all these examples are taken "
-"from the seamBay example in Seam), that we will be redirected to <literal>/"
-"bid.xhtml</literal>, which, as we saw previously, is configured with the "
-"natural conversation <literal>PlaceBid</literal>. The declaration for our "
-"action method looks like this:"
+msgid "From here, we can see that invoking the action <literal>#{bidAction.placeBid}</literal> from our auction view (by the way, all these examples are taken from the seamBay example in Seam), that we will be redirected to <literal>/bid.xhtml</literal>, which, as we saw previously, is configured with the natural conversation <literal>PlaceBid</literal>. The declaration for our action method looks like this:"
msgstr ""
#. Tag: programlisting
@@ -1076,46 +899,38 @@
"<![CDATA[ @Begin(join = true)\n"
" public void placeBid()]]>"
msgstr ""
+"<![CDATA[ @Begin(join = true)\n"
+" public void placeBid()]]>"
#. Tag: para
#: Conversations.xml:674
#, no-c-format
-msgid ""
-"When named conversations are specified in the <literal><page/></"
-"literal> element, redirection to the named conversation occurs as part of "
-"navigation rules, after the action method has already been invoked. This is "
-"a problem when redirecting to an existing conversation, as redirection needs "
-"to be occur before the action method is invoked. Therefore it is necessary "
-"to specify the conversation name when the action is invoked. One way of "
-"doing this is by using the <literal>s:conversationName</literal> tag:"
+msgid "When named conversations are specified in the <literal><page/></literal> element, redirection to the named conversation occurs as part of navigation rules, after the action method has already been invoked. This is a problem when redirecting to an existing conversation, as redirection needs to be occur before the action method is invoked. Therefore it is necessary to specify the conversation name when the action is invoked. One way of doing this is by using the <literal>s:conversationName</literal> tag:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:684
#, no-c-format
msgid ""
-"<![CDATA[ <h:commandButton id=\"placeBidWithAmount\" styleClass=\"placeBid"
-"\" action=\"#{bidAction.placeBid}\">\n"
+"<![CDATA[ <h:commandButton id=\"placeBidWithAmount\" styleClass=\"placeBid\" action=\"#{bidAction.placeBid}\">\n"
" <s:conversationName value=\"PlaceBid\"/>\n"
" </h:commandButton>]]>"
msgstr ""
+"<![CDATA[ <h:commandButton id=\"placeBidWithAmount\" styleClass=\"placeBid\" action=\"#{bidAction.placeBid}\">\n"
+" <s:conversationName value=\"PlaceBid\"/>\n"
+" </h:commandButton>]]>"
#. Tag: para
#: Conversations.xml:686
#, no-c-format
-msgid ""
-"Another alternative is to specify the <literal>conversationName</literal> "
-"attribute when using either <literal>s:link</literal> or <literal>s:button</"
-"literal>:"
+msgid "Another alternative is to specify the <literal>conversationName</literal> attribute when using either <literal>s:link</literal> or <literal>s:button</literal>:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:691
#, no-c-format
-msgid ""
-"<![CDATA[ <s:link value=\"Place Bid\" action=\"#{bidAction.placeBid}\" "
-"conversationName=\"PlaceBid\"/>]]>"
-msgstr ""
+msgid "<![CDATA[ <s:link value=\"Place Bid\" action=\"#{bidAction.placeBid}\" conversationName=\"PlaceBid\"/>]]>"
+msgstr "<![CDATA[ <s:link value=\"Place Bid\" action=\"#{bidAction.placeBid}\" conversationName=\"PlaceBid\"/>]]>"
#. Tag: title
#: Conversations.xml:697
@@ -1126,28 +941,19 @@
#. Tag: para
#: Conversations.xml:699
#, no-c-format
-msgid ""
-"Workspace management is the ability to \"switch\" conversations in a single "
-"window. Seam makes workspace management completely transparent at the level "
-"of the Java code. To enable workspace management, all you need to do is:"
+msgid "Workspace management is the ability to \"switch\" conversations in a single window. Seam makes workspace management completely transparent at the level of the Java code. To enable workspace management, all you need to do is:"
msgstr ""
#. Tag: para
#: Conversations.xml:708
#, no-c-format
-msgid ""
-"Provide <emphasis>description</emphasis> text for each view id (when using "
-"JSF or Seam navigation rules) or page node (when using jPDL pageflows). This "
-"description text is displayed to the user by the workspace switchers."
+msgid "Provide <emphasis>description</emphasis> text for each view id (when using JSF or Seam navigation rules) or page node (when using jPDL pageflows). This description text is displayed to the user by the workspace switchers."
msgstr ""
#. Tag: para
#: Conversations.xml:716
#, no-c-format
-msgid ""
-"Include one or more of the standard workspace switcher JSP or facelets "
-"fragments in your pages. The standard fragments support workspace management "
-"via a drop down menu, a list of conversations, or breadcrumbs."
+msgid "Include one or more of the standard workspace switcher JSP or facelets fragments in your pages. The standard fragments support workspace management via a drop down menu, a list of conversations, or breadcrumbs."
msgstr ""
#. Tag: title
@@ -1159,12 +965,7 @@
#. Tag: para
#: Conversations.xml:727
#, no-c-format
-msgid ""
-"When you use JSF or Seam navigation rules, Seam switches to a conversation "
-"by restoring the current <literal>view-id</literal> for that conversation. "
-"The descriptive text for the workspace is defined in a file called "
-"<literal>pages.xml</literal> that Seam expects to find in the <literal>WEB-"
-"INF</literal> directory, right next to <literal>faces-config.xml</literal>:"
+msgid "When you use JSF or Seam navigation rules, Seam switches to a conversation by restoring the current <literal>view-id</literal> for that conversation. The descriptive text for the workspace is defined in a file called <literal>pages.xml</literal> that Seam expects to find in the <literal>WEB-INF</literal> directory, right next to <literal>faces-config.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1173,8 +974,7 @@
msgid ""
"<![CDATA[<pages>\n"
" <page view-id=\"/main.xhtml\">\n"
-" <description>Search hotels: #{hotelBooking.searchString}</"
-"description>\n"
+" <description>Search hotels: #{hotelBooking.searchString}</description>\n"
" </page>\n"
" <page view-id=\"/hotel.xhtml\">\n"
" <description>View hotel: #{hotel.name}</description>\n"
@@ -1187,14 +987,25 @@
" </page>\n"
" </pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/main.xhtml\">\n"
+" <description>Search hotels: #{hotelBooking.searchString}</description>\n"
+" </page>\n"
+" <page view-id=\"/hotel.xhtml\">\n"
+" <description>View hotel: #{hotel.name}</description>\n"
+" </page>\n"
+" <page view-id=\"/book.xhtml\">\n"
+" <description>Book hotel: #{hotel.name}</description>\n"
+" </page>\n"
+" <page view-id=\"/confirm.xhtml\">\n"
+" <description>Confirm: #{booking.description}</description>\n"
+" </page>\n"
+" </pages>]]>"
#. Tag: para
#: Conversations.xml:738
#, no-c-format
-msgid ""
-"Note that if this file is missing, the Seam application will continue to "
-"work perfectly! The only missing functionality will be the ability to switch "
-"workspaces."
+msgid "Note that if this file is missing, the Seam application will continue to work perfectly! The only missing functionality will be the ability to switch workspaces."
msgstr ""
#. Tag: title
@@ -1206,13 +1017,7 @@
#. Tag: para
#: Conversations.xml:748
#, no-c-format
-msgid ""
-"When you use a jPDL pageflow definition, Seam switches to a conversation by "
-"restoring the current jBPM process state. This is a more flexible model "
-"since it allows the same <literal>view-id</literal> to have different "
-"descriptions depending upon the current <literal><page></literal> "
-"node. The description text is defined by the <literal><page></literal> "
-"node:"
+msgid "When you use a jPDL pageflow definition, Seam switches to a conversation by restoring the current jBPM process state. This is a more flexible model since it allows the same <literal>view-id</literal> to have different descriptions depending upon the current <literal><page></literal> node. The description text is defined by the <literal><page></literal> node:"
msgstr ""
#. Tag: programlisting
@@ -1243,6 +1048,29 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<pageflow-definition name=\"shopping\">\n"
+"\n"
+" <start-state name=\"start\">\n"
+" <transition to=\"browse\"/>\n"
+" </start-state>\n"
+" \n"
+" <page name=\"browse\" view-id=\"/browse.xhtml\">\n"
+" <description>DVD Search: #{search.searchPattern}</description>\n"
+" <transition to=\"browse\"/>\n"
+" <transition name=\"checkout\" to=\"checkout\"/>\n"
+" </page>\n"
+" \n"
+" <page name=\"checkout\" view-id=\"/checkout.xhtml\">\n"
+" <description>Purchase: $#{cart.total}</description>\n"
+" <transition to=\"checkout\"/>\n"
+" <transition name=\"complete\" to=\"complete\"/>\n"
+" </page>\n"
+" \n"
+" <page name=\"complete\" view-id=\"/complete.xhtml\">\n"
+" <end-conversation />\n"
+" </page>\n"
+" \n"
+"</pageflow-definition>]]>"
#. Tag: title
#: Conversations.xml:764
@@ -1253,10 +1081,7 @@
#. Tag: para
#: Conversations.xml:766
#, no-c-format
-msgid ""
-"Include the following fragment in your JSP or facelets page to get a drop-"
-"down menu that lets you switch to any current conversation, or to any other "
-"page of the application:"
+msgid "Include the following fragment in your JSP or facelets page to get a drop-down menu that lets you switch to any current conversation, or to any other page of the application:"
msgstr ""
#. Tag: programlisting
@@ -1270,22 +1095,23 @@
"</h:selectOneMenu>\n"
"<h:commandButton action=\"#{switcher.select}\" value=\"Switch\"/>]]>"
msgstr ""
+"<![CDATA[<h:selectOneMenu value=\"#{switcher.conversationIdOrOutcome}\">\n"
+" <f:selectItem itemLabel=\"Find Issues\" itemValue=\"findIssue\"/>\n"
+" <f:selectItem itemLabel=\"Create Issue\" itemValue=\"editIssue\"/>\n"
+" <f:selectItems value=\"#{switcher.selectItems}\"/>\n"
+"</h:selectOneMenu>\n"
+"<h:commandButton action=\"#{switcher.select}\" value=\"Switch\"/>]]>"
#. Tag: para
#: Conversations.xml:774
#, no-c-format
-msgid ""
-"In this example, we have a menu that includes an item for each conversation, "
-"together with two additional items that let the user begin a new "
-"conversation."
+msgid "In this example, we have a menu that includes an item for each conversation, together with two additional items that let the user begin a new conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:780
#, no-c-format
-msgid ""
-"Only conversations with a description (specified in <literal>pages.xml</"
-"literal>) will be included in the drop-down menu."
+msgid "Only conversations with a description (specified in <literal>pages.xml</literal>) will be included in the drop-down menu."
msgstr ""
#. Tag: title
@@ -1297,9 +1123,7 @@
#. Tag: para
#: Conversations.xml:800
#, no-c-format
-msgid ""
-"The conversation list is very similar to the conversation switcher, except "
-"that it is displayed as a table:"
+msgid "The conversation list is very similar to the conversation switcher, except that it is displayed as a table:"
msgstr ""
#. Tag: programlisting
@@ -1310,8 +1134,7 @@
" rendered=\"#{not empty conversationList}\">\n"
" <h:column>\n"
" <f:facet name=\"header\">Workspace</f:facet>\n"
-" <h:commandLink action=\"#{entry.select}\" value=\"#{entry."
-"description}\"/>\n"
+" <h:commandLink action=\"#{entry.select}\" value=\"#{entry.description}\"/>\n"
" <h:outputText value=\"[current]\" rendered=\"#{entry.current}\"/>\n"
" </h:column>\n"
" <h:column>\n"
@@ -1326,19 +1149,39 @@
" </h:column>\n"
" <h:column>\n"
" <f:facet name=\"header\">Action</f:facet>\n"
-" <h:commandButton action=\"#{entry.select}\" value=\"#{msg.Switch}\"/"
-">\n"
-" <h:commandButton action=\"#{entry.destroy}\" value=\"#{msg.Destroy}"
-"\"/>\n"
+" <h:commandButton action=\"#{entry.select}\" value=\"#{msg.Switch}\"/>\n"
+" <h:commandButton action=\"#{entry.destroy}\" value=\"#{msg.Destroy}\"/>\n"
" </h:column>\n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{conversationList}\" var=\"entry\"\n"
+" rendered=\"#{not empty conversationList}\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Workspace</f:facet>\n"
+" <h:commandLink action=\"#{entry.select}\" value=\"#{entry.description}\"/>\n"
+" <h:outputText value=\"[current]\" rendered=\"#{entry.current}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Activity</f:facet>\n"
+" <h:outputText value=\"#{entry.startDatetime}\">\n"
+" <f:convertDateTime type=\"time\" pattern=\"hh:mm a\"/>\n"
+" </h:outputText>\n"
+" <h:outputText value=\" - \"/>\n"
+" <h:outputText value=\"#{entry.lastDatetime}\">\n"
+" <f:convertDateTime type=\"time\" pattern=\"hh:mm a\"/>\n"
+" </h:outputText>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Action</f:facet>\n"
+" <h:commandButton action=\"#{entry.select}\" value=\"#{msg.Switch}\"/>\n"
+" <h:commandButton action=\"#{entry.destroy}\" value=\"#{msg.Destroy}\"/>\n"
+" </h:column>\n"
+"</h:dataTable>]]>"
#. Tag: para
#: Conversations.xml:807
#, no-c-format
-msgid ""
-"We imagine that you will want to customize this for your own application."
+msgid "We imagine that you will want to customize this for your own application."
msgstr ""
#. Tag: para
@@ -1362,10 +1205,7 @@
#. Tag: para
#: Conversations.xml:834
#, no-c-format
-msgid ""
-"Breadcrumbs are useful in applications which use a nested conversation "
-"model. The breadcrumbs are a list of links to conversations in the current "
-"conversation stack:"
+msgid "Breadcrumbs are useful in applications which use a nested conversation model. The breadcrumbs are a list of links to conversations in the current conversation stack:"
msgstr ""
#. Tag: programlisting
@@ -1374,10 +1214,13 @@
msgid ""
"<![CDATA[<ui:repeat value=\"#{conversationStack}\" var=\"entry\">\n"
" <h:outputText value=\" | \"/> \n"
-" <h:commandLink value=\"#{entry.description}\" action=\"#{entry.select}\"/"
-">\n"
+" <h:commandLink value=\"#{entry.description}\" action=\"#{entry.select}\"/>\n"
"</ui:repeat]]>"
msgstr ""
+"<![CDATA[<ui:repeat value=\"#{conversationStack}\" var=\"entry\">\n"
+" <h:outputText value=\" | \"/> \n"
+" <h:commandLink value=\"#{entry.description}\" action=\"#{entry.select}\"/>\n"
+"</ui:repeat]]>"
#. Tag: title
#: Conversations.xml:855
@@ -1388,22 +1231,13 @@
#. Tag: para
#: Conversations.xml:857
#, no-c-format
-msgid ""
-"Conversational components have one minor limitation: they cannot be used to "
-"hold bindings to JSF components. (We generally prefer not to use this "
-"feature of JSF unless absolutely necessary, since it creates a hard "
-"dependency from application logic to the view.) On a postback request, "
-"component bindings are updated during the Restore View phase, before the "
-"Seam conversation context has been restored."
+msgid "Conversational components have one minor limitation: they cannot be used to hold bindings to JSF components. (We generally prefer not to use this feature of JSF unless absolutely necessary, since it creates a hard dependency from application logic to the view.) On a postback request, component bindings are updated during the Restore View phase, before the Seam conversation context has been restored."
msgstr ""
#. Tag: para
#: Conversations.xml:865
#, no-c-format
-msgid ""
-"To work around this use an event scoped component to store the component "
-"bindings and inject it into the conversation scoped component that requires "
-"it."
+msgid "To work around this use an event scoped component to store the component bindings and inject it into the conversation scoped component that requires it."
msgstr ""
#. Tag: programlisting
@@ -1420,6 +1254,15 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"grid\")\n"
+"@Scope(ScopeType.EVENT)\n"
+"public class Grid\n"
+"{\n"
+" private HtmlPanelGrid htmlPanelGrid;\n"
+"\n"
+" // getters and setters\n"
+" ...\n"
+"}]]>"
#. Tag: programlisting
#: Conversations.xml:873
@@ -1435,25 +1278,26 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"gridEditor\")\n"
+"@Scope(ScopeType.CONVERSATION)\n"
+"public class GridEditor\n"
+"{\n"
+" @In(required=false)\n"
+" private Grid grid;\n"
+" \n"
+" ...\n"
+"}]]>"
#. Tag: para
#: Conversations.xml:875
#, no-c-format
-msgid ""
-"Also, you can't inject a conversation scoped component into an event scoped "
-"component which you bind a JSF control to. This includes Seam built in "
-"components like <literal>facesMessages</literal>."
+msgid "Also, you can't inject a conversation scoped component into an event scoped component which you bind a JSF control to. This includes Seam built in components like <literal>facesMessages</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:881
#, no-c-format
-msgid ""
-"Alternatively, you can access the JSF component tree through the implicit "
-"<literal>uiComponent</literal> handle. The following example accesses "
-"<literal>getRowIndex()</literal>of the <literal>UIData</literal> component "
-"which backs the data table during iteration, it prints the current row "
-"number:"
+msgid "Alternatively, you can access the JSF component tree through the implicit <literal>uiComponent</literal> handle. The following example accesses <literal>getRowIndex()</literal>of the <literal>UIData</literal> component which backs the data table during iteration, it prints the current row number:"
msgstr ""
#. Tag: programlisting
@@ -1461,20 +1305,25 @@
#, no-c-format
msgid ""
"<![CDATA[\n"
-"<h:dataTable id=\"lineItemTable\" var=\"lineItem\" value=\"#{orderHome."
-"lineItems}\">\n"
+"<h:dataTable id=\"lineItemTable\" var=\"lineItem\" value=\"#{orderHome.lineItems}\">\n"
" <h:column>\n"
" Row: #{uiComponent['lineItemTable'].rowIndex}\n"
" </h:column>\n"
" ...\n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[\n"
+"<h:dataTable id=\"lineItemTable\" var=\"lineItem\" value=\"#{orderHome.lineItems}\">\n"
+" <h:column>\n"
+" Row: #{uiComponent['lineItemTable'].rowIndex}\n"
+" </h:column>\n"
+" ...\n"
+"</h:dataTable>]]>"
#. Tag: para
#: Conversations.xml:890
#, no-c-format
-msgid ""
-"JSF UI components are available with their client identifier in this map."
+msgid "JSF UI components are available with their client identifier in this map."
msgstr ""
#. Tag: title
@@ -1486,61 +1335,37 @@
#. Tag: para
#: Conversations.xml:899
#, no-c-format
-msgid ""
-"A general discussion of concurrent calls to Seam components can be found in "
-"<xref linkend=\"concurrency\"/>. Here we will discuss the most common "
-"situation in which you will encounter concurrency — accessing "
-"conversational components from AJAX requests. We're going to discuss the "
-"options that a Ajax client library should provide to control events "
-"originating at the client — and we'll look at the options RichFaces "
-"gives you."
+msgid "A general discussion of concurrent calls to Seam components can be found in <xref linkend=\"concurrency\"/>. Here we will discuss the most common situation in which you will encounter concurrency — accessing conversational components from AJAX requests. We're going to discuss the options that a Ajax client library should provide to control events originating at the client — and we'll look at the options RichFaces gives you."
msgstr ""
#. Tag: para
#: Conversations.xml:909
#, no-c-format
-msgid ""
-"Conversational components don't allow real concurrent access therefore Seam "
-"queues each request to process them serially. This allows each request to be "
-"executed in a deterministic fashion. However, a simple queue isn't that "
-"great — firstly, if a method is, for some reason, taking a very long "
-"time to complete, running it over and over again whenever the client "
-"generates a request is bad idea (potential for Denial of Service attacks), "
-"and, secondly, AJAX is often to used to provide a quick status update to the "
-"user, so continuing to run the action after a long time isn't useful."
+msgid "Conversational components don't allow real concurrent access therefore Seam queues each request to process them serially. This allows each request to be executed in a deterministic fashion. However, a simple queue isn't that great — firstly, if a method is, for some reason, taking a very long time to complete, running it over and over again whenever the client generates a request is bad idea (potential for Denial of Service attacks), and, secondly, AJAX is often to used to provide a quick status update to the user, so continuing to run the action after a long time isn't useful."
msgstr ""
#. Tag: para
#: Conversations.xml:921
#, no-c-format
-msgid ""
-"Therefore, when you are working inside a long running conversation, Seam "
-"queues the action event for a period of time (the concurrent request "
-"timeout); if it can't process the event in time, it creates a temporary "
-"conversation and prints out a message to the user to let them know what's "
-"going on. It's therefore very important not to flood the server with AJAX "
-"events!"
+msgid "Therefore, when you are working inside a long running conversation, Seam queues the action event for a period of time (the concurrent request timeout); if it can't process the event in time, it creates a temporary conversation and prints out a message to the user to let them know what's going on. It's therefore very important not to flood the server with AJAX events!"
msgstr ""
#. Tag: para
#: Conversations.xml:930
#, no-c-format
-msgid ""
-"We can set a sensible default for the concurrent request timeout (in ms) in "
-"components.xml:"
+msgid "We can set a sensible default for the concurrent request timeout (in ms) in components.xml:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:935
#, no-c-format
msgid "<![CDATA[<core:manager concurrent-request-timeout=\"500\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<core:manager concurrent-request-timeout=\"500\" />]]>"
#. Tag: para
#: Conversations.xml:937
#, no-c-format
-msgid ""
-"We can also fine tune the concurrent request timeout on a page-by-page basis:"
+msgid "We can also fine tune the concurrent request timeout on a page-by-page basis:"
msgstr ""
#. Tag: programlisting
@@ -1552,29 +1377,21 @@
" login-required=\"true\"\n"
" concurrent-request-timeout=\"2000\" />]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/book.xhtml\" \n"
+" conversation-required=\"true\" \n"
+" login-required=\"true\"\n"
+" concurrent-request-timeout=\"2000\" />]]>"
#. Tag: para
#: Conversations.xml:944
#, no-c-format
-msgid ""
-"So far we've discussed AJAX requests which appear serial to the user - the "
-"client tells the server that an event has occur, and then rerenders part of "
-"the page based on the result. This approach is great when the AJAX request "
-"is lightweight (the methods called are simple e.g. calculating the sum of a "
-"column of numbers). But what if we need to do a complex computation thats "
-"going to take a minute?"
+msgid "So far we've discussed AJAX requests which appear serial to the user - the client tells the server that an event has occur, and then rerenders part of the page based on the result. This approach is great when the AJAX request is lightweight (the methods called are simple e.g. calculating the sum of a column of numbers). But what if we need to do a complex computation thats going to take a minute?"
msgstr ""
#. Tag: para
#: Conversations.xml:953
#, no-c-format
-msgid ""
-"For heavy computation we should use a poll based approach — the client "
-"sends an AJAX request to the server, which causes action to be executed "
-"asynchronously on the server (the response to the client is immediate) and "
-"the client then polls the server for updates. This is good approach when you "
-"have a long-running action for which it is important that every action "
-"executes (you don't want some to timeout)."
+msgid "For heavy computation we should use a poll based approach — the client sends an AJAX request to the server, which causes action to be executed asynchronously on the server (the response to the client is immediate) and the client then polls the server for updates. This is good approach when you have a long-running action for which it is important that every action executes (you don't want some to timeout)."
msgstr ""
#. Tag: title
@@ -1586,41 +1403,25 @@
#. Tag: para
#: Conversations.xml:965
#, no-c-format
-msgid ""
-"Well first, you need to decide whether you want to use the simpler \"serial"
-"\" request or whether you want to use a polling approach."
+msgid "Well first, you need to decide whether you want to use the simpler \"serial\" request or whether you want to use a polling approach."
msgstr ""
#. Tag: para
#: Conversations.xml:970
#, no-c-format
-msgid ""
-"If you go for a \"serial\" requests, then you need to estimate how long your "
-"request will take to complete - is it much shorter than the concurrent "
-"request timeout? If not, you probably want to alter the concurrent request "
-"timeout for this page (as discussed above). You probably want a queue on the "
-"client side to prevent flooding the server with requests. If the event "
-"occurs often (e.g. a keypress, onblur of input fields) and immediate update "
-"of the client is not a priority you should set a request delay on the client "
-"side. When working out your request delay, factor in that the event may also "
-"be queued on the server side."
+msgid "If you go for a \"serial\" requests, then you need to estimate how long your request will take to complete - is it much shorter than the concurrent request timeout? If not, you probably want to alter the concurrent request timeout for this page (as discussed above). You probably want a queue on the client side to prevent flooding the server with requests. If the event occurs often (e.g. a keypress, onblur of input fields) and immediate update of the client is not a priority you should set a request delay on the client side. When working out your request delay, factor in that the event may also be queued on the server side."
msgstr ""
#. Tag: para
#: Conversations.xml:983
#, no-c-format
-msgid ""
-"Finally, the client library may provide an option to abort unfinished "
-"duplicate requests in favor of the most recent."
+msgid "Finally, the client library may provide an option to abort unfinished duplicate requests in favor of the most recent."
msgstr ""
#. Tag: para
#: Conversations.xml:988
#, no-c-format
-msgid ""
-"Using a poll-style design requires less fine-tuning. You just mark your "
-"action method <literal>@Asynchronous</literal> and decide on a polling "
-"interval:"
+msgid "Using a poll-style design requires less fine-tuning. You just mark your action method <literal>@Asynchronous</literal> and decide on a polling interval:"
msgstr ""
#. Tag: programlisting
@@ -1642,6 +1443,20 @@
" return total;\n"
"}]]>"
msgstr ""
+"<![CDATA[int total;\n"
+"\n"
+"// This method is called when an event occurs on the client\n"
+"// It takes a really long time to execute\n"
+"@Asynchronous \n"
+"public void calculateTotal() {\n"
+" total = someReallyComplicatedCalculation();\n"
+"}\n"
+"\n"
+"// This method is called as the result of the poll\n"
+"// It's very quick to execute\n"
+"public int getTotal() {\n"
+" return total;\n"
+"}]]>"
#. Tag: title
#: Conversations.xml:998
@@ -1652,39 +1467,31 @@
#. Tag: para
#: Conversations.xml:1000
#, no-c-format
-msgid ""
-"However carefully you design your application to queue concurrent requests "
-"to your conversational component, there is a risk that the server will "
-"become overloaded and be unable to process all the requests before the "
-"request will have to wait longer than the <literal>concurrent-request-"
-"timeout</literal>. In this case Seam will throw a "
-"<literal>ConcurrentRequestTimeoutException</literal> which can be handled in "
-"<literal>pages.xml</literal>. We recommend sending an HTTP 503 error:"
+msgid "However carefully you design your application to queue concurrent requests to your conversational component, there is a risk that the server will become overloaded and be unable to process all the requests before the request will have to wait longer than the <literal>concurrent-request-timeout</literal>. In this case Seam will throw a <literal>ConcurrentRequestTimeoutException</literal> which can be handled in <literal>pages.xml</literal>. We recommend sending an HTTP 503 error:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:1011
#, no-c-format
msgid ""
-"<![CDATA[ <exception class=\"org.jboss.seam."
-"ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
" <http-error error-code=\"503\" />\n"
" </exception>]]>"
msgstr ""
+"<![CDATA[ <exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
+" <http-error error-code=\"503\" />\n"
+" </exception>]]>"
#. Tag: title
#: Conversations.xml:1014
#, no-c-format
msgid "503 Service Unavailable (HTTP/1.1 RFC)"
-msgstr ""
+msgstr "503 Service Unavailable (HTTP/1.1 RFC)"
#. Tag: para
#: Conversations.xml:1016
#, no-c-format
-msgid ""
-"The server is currently unable to handle the request due to a temporary "
-"overloading or maintenance of the server. The implication is that this is a "
-"temporary condition which will be alleviated after some delay."
+msgid "The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay."
msgstr ""
#. Tag: para
@@ -1697,25 +1504,24 @@
#: Conversations.xml:1028
#, no-c-format
msgid ""
-"<![CDATA[<exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException"
-"\" logLevel=\"trace\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message>The server is too busy to process your request, please try "
-"again later</message>\n"
+" <message>The server is too busy to process your request, please try again later</message>\n"
" </redirect>\n"
"</exception>]]>"
msgstr ""
+"<![CDATA[<exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>The server is too busy to process your request, please try again later</message>\n"
+" </redirect>\n"
+"</exception>]]>"
#. Tag: para
#: Conversations.xml:1030
#, no-c-format
-msgid ""
-"ICEfaces, RichFaces Ajax and Seam Remoting can all handle HTTP error codes. "
-"Seam Remoting will pop up a dialog box showing the HTTP error and ICEfaces "
-"will indicate the error in it's connection status component. RichFaces Ajax "
-"provides the most complete support for handling HTTP errors by providing a "
-"user definable callback. For example, to show the error message to the user:"
+msgid "ICEfaces, RichFaces Ajax and Seam Remoting can all handle HTTP error codes. Seam Remoting will pop up a dialog box showing the HTTP error and ICEfaces will indicate the error in it's connection status component. RichFaces Ajax provides the most complete support for handling HTTP errors by providing a user definable callback. For example, to show the error message to the user:"
msgstr ""
#. Tag: programlisting
@@ -1728,6 +1534,11 @@
" };\n"
"</script>]]>"
msgstr ""
+"<![CDATA[<script type=\"text/javascript\">\n"
+" A4J.AJAX.onError = function(req,status,message) { \n"
+" alert(\"message\"); \n"
+" };\n"
+"</script>]]>"
#. Tag: title
#: Conversations.xml:1044
@@ -1738,66 +1549,42 @@
#. Tag: para
#: Conversations.xml:1046
#, no-c-format
-msgid ""
-"RichFaces Ajax is the AJAX library most commonly used with Seam, and "
-"provides all the controls discussed above:"
+msgid "RichFaces Ajax is the AJAX library most commonly used with Seam, and provides all the controls discussed above:"
msgstr ""
#. Tag: para
#: Conversations.xml:1053
#, no-c-format
-msgid ""
-"<literal>eventsQueue</literal> — provide a queue in which events are "
-"placed. All events are queued and requests are sent to the server serially. "
-"This is useful if the request can to the server can take some time to "
-"execute (e.g. heavy computation, retrieving information from a slow source) "
-"as the server isn't flooded."
+msgid "<literal>eventsQueue</literal> — provide a queue in which events are placed. All events are queued and requests are sent to the server serially. This is useful if the request can to the server can take some time to execute (e.g. heavy computation, retrieving information from a slow source) as the server isn't flooded."
msgstr ""
#. Tag: para
#: Conversations.xml:1063
#, no-c-format
-msgid ""
-"<literal>ignoreDupResponses</literal> — ignore the response produced "
-"by the request if a more recent 'similar' request is already in the queue. "
-"ignoreDupResponses=\"true\" does <emphasis>not cancel</emphasis> the the "
-"processing of the request on the server side — just prevents "
-"unnecessary updates on the client side."
+msgid "<literal>ignoreDupResponses</literal> — ignore the response produced by the request if a more recent 'similar' request is already in the queue. ignoreDupResponses=\"true\" does <emphasis>not cancel</emphasis> the the processing of the request on the server side — just prevents unnecessary updates on the client side."
msgstr ""
#. Tag: para
#: Conversations.xml:1070
#, no-c-format
-msgid ""
-"This option should be used with care with Seam's conversations as it allows "
-"multiple concurrent requests to be made."
+msgid "This option should be used with care with Seam's conversations as it allows multiple concurrent requests to be made."
msgstr ""
#. Tag: para
#: Conversations.xml:1076
#, no-c-format
-msgid ""
-"<literal>requestDelay</literal> — defines the time (in ms.) that the "
-"request will be remain on the queue. If the request has not been processed "
-"by after this time the request will be sent (regardless of whether a "
-"response has been received) or discarded (if there is a more recent similar "
-"event on the queue)."
+msgid "<literal>requestDelay</literal> — defines the time (in ms.) that the request will be remain on the queue. If the request has not been processed by after this time the request will be sent (regardless of whether a response has been received) or discarded (if there is a more recent similar event on the queue)."
msgstr ""
#. Tag: para
#: Conversations.xml:1083
#, no-c-format
-msgid ""
-"This option should be used with care with Seam's conversations as it allows "
-"multiple concurrent requests to be made. You need to be sure that the delay "
-"you set (in combination with the concurrent request timeout) is longer than "
-"the action will take to execute."
+msgid "This option should be used with care with Seam's conversations as it allows multiple concurrent requests to be made. You need to be sure that the delay you set (in combination with the concurrent request timeout) is longer than the action will take to execute."
msgstr ""
#. Tag: para
#: Conversations.xml:1091
#, no-c-format
-msgid ""
-"<literal><a:poll reRender=\"total\" interval=\"1000\" /></literal> "
-"— Polls the server, and rerenders an area as needed"
+msgid "<literal><a:poll reRender=\"total\" interval=\"1000\" /></literal> — Polls the server, and rerenders an area as needed"
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,7 +6,7 @@
"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-06 21:25+0100\n"
+"PO-Revision-Date: 2008-12-16 12:18+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -35,7 +35,7 @@
#: Drools.xml:15
#, no-c-format
msgid "The first step is to make an instance of <literal>org.drools.RuleBase</literal> available in a Seam context variable. For testing purposes, Seam provides a built-in component that compiles a static set of rules from the classpath. You can install this component via <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Il primo passo è creare un'istanza di <literal>org.drools.RuleBase</literal> disponibile in una variabile del contesto di Seam. Per testare Seam fornisce un componente interno che compila un set statico di regole dal classpath. Puoi installare questo componente tramite <literal>components.xml</literal>:"
#. Tag: programlisting
#: Drools.xml:22
@@ -57,7 +57,7 @@
#: Drools.xml:24
#, no-c-format
msgid "This component compiles rules from a set of <literal>.drl</literal> files and caches an instance of <literal>org.drools.RuleBase</literal> in the Seam <literal>APPLICATION</literal> context. Note that it is quite likely that you will need to install multiple rule bases in a rule-driven application."
-msgstr ""
+msgstr "Questo componente compila le regole da un set di file <literal>.drl</literal> e mette in cache un'istanza di <literal>org.drools.RuleBase</literal> nel contesto <literal>APPLICATION</literal> di Seam. Notare che è abbastanza probabile che in un'applicazione guidata dalle regole occorra installare altre basi di regole."
#. Tag: para
#: Drools.xml:32
@@ -85,7 +85,7 @@
#: Drools.xml:39
#, no-c-format
msgid "In most rules-driven applications, rules need to be dynamically deployable, so a production application will want to use a Drools RuleAgent to manage the RuleBase. The RuleAgent can connect to a Drools rule server (BRMS) or hot deploy rules packages from a local file repository. The RulesAgent-managed RuleBase is also configurable in <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Nella maggior parte delle applicazioni guidate dalle regole, le regole devono essere dinamicamente deployabili, e quindi un'applicazione in produzione dovrà usare un Drools RuleAgent per gestire la RuleBase. Il RuleAgent può connettersi al server di regole Drool (BRMS) od eseguire l'hot deploy dei pacchetti di regole dal repository locale. La RuleBase gestita dal RulesAgen è configurabile in <literal>components.xml</literal>:"
#. Tag: programlisting
#: Drools.xml:47
@@ -101,7 +101,7 @@
#: Drools.xml:49
#, no-c-format
msgid "The properties file contains properties specific to the RulesAgent. Here is an example configuration file from the Drools example distribution."
-msgstr ""
+msgstr "Il file delle proprietà contiene proprietà specifiche per RulesAgent. Ecco un file di configurazione d'esempio proveniente dalla distribuzione Drools."
#. Tag: programlisting
#: Drools.xml:52
@@ -113,12 +113,17 @@
"poll=30\n"
"name=insuranceconfig"
msgstr ""
+"newInstance=true\n"
+"url=http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/package/org.acme.insurance/fmeyer\n"
+"localCacheDir=/Users/fernandomeyer/projects/jbossrules/drools-examples/drools-examples-brms/cache\n"
+"poll=30\n"
+"name=insuranceconfig"
#. Tag: para
#: Drools.xml:55
#, no-c-format
msgid "It is also possible to configure the options on the component directly, bypassing the configuration file."
-msgstr ""
+msgstr "E' anche possibile configurare le opzioni derettamente sul componente, bypassando il file di configurazione."
#. Tag: programlisting
#: Drools.xml:57
@@ -140,7 +145,7 @@
#: Drools.xml:59
#, no-c-format
msgid "Next, we need to make an instance of <literal>org.drools.WorkingMemory</literal> available to each conversation. (Each <literal>WorkingMemory</literal> accumulates facts relating to the current conversation.)"
-msgstr ""
+msgstr "Successivamente occorre rendere disponibile ad ogni conversazione un'istanza di <literal>org.drools.WorkingMemory</literal>. (Ogni <literal>WorkingMemory</literal> accumula fatti relativi alla conversazione corrente.)"
#. Tag: programlisting
#: Drools.xml:65
@@ -152,7 +157,7 @@
#: Drools.xml:67
#, no-c-format
msgid "Notice that we gave the <literal>policyPricingWorkingMemory</literal> a reference back to our rule base via the <literal>ruleBase</literal> configuration property."
-msgstr ""
+msgstr "Notare che abbiamo dato a <literal>policyPricingWorkingMemory</literal> un riferimento alla base di regole tramite la proprietà di configurazione <literal>ruleBase</literal>."
#. Tag: title
#: Drools.xml:76
@@ -164,7 +169,7 @@
#: Drools.xml:78
#, no-c-format
msgid "We can now inject our <literal>WorkingMemory</literal> into any Seam component, assert facts, and fire rules:"
-msgstr ""
+msgstr "Ora possiamo iniettare la <literal>WorkingMemory</literal> in un qualsiasi componente di Seam, asserire i fatti e lanciare le regole:"
#. Tag: programlisting
#: Drools.xml:83
@@ -204,7 +209,7 @@
#: Drools.xml:90
#, no-c-format
msgid "You can even allow a rule base to act as a jBPM action handler, decision handler, or assignment handler—in either a pageflow or business process definition."
-msgstr ""
+msgstr "Si può anche consentire alla base di regole di agire come action handler di jBPM, decision handler, o assignment handler— sia in una definizione di pageflow sia in un processo di business."
#. Tag: programlisting
#: Drools.xml:96
@@ -266,13 +271,13 @@
#: Drools.xml:98
#, no-c-format
msgid "The <literal><assertObjects></literal> element specifies EL expressions that return an object or collection of objects to be asserted as facts into the <literal>WorkingMemory</literal>."
-msgstr ""
+msgstr "L'elemento <literal><assertObjects></literal> specifica le espressioni EL che restituiscono un oggetto od una collezione di oggetti da asserire come fatti nella <literal>WorkingMemory</literal>."
#. Tag: para
#: Drools.xml:104
#, no-c-format
msgid "There is also support for using Drools for jBPM task assignments:"
-msgstr ""
+msgstr "Esiste anche il supporto per l'uso di Drools per le assegnazioni dei task in jBPM:"
#. Tag: programlisting
#: Drools.xml:108
@@ -310,11 +315,12 @@
" <transition name=\"approved\" to=\"approved\"/>\n"
"</task-node>]]>"
+# rivedere la frase.
#. Tag: para
#: Drools.xml:110
#, no-c-format
msgid "Certain objects are available to the rules as Drools globals, namely the jBPM <literal>Assignable</literal>, as <literal>assignable</literal> and a Seam <literal>Decision</literal> object, as <literal>decision</literal>. Rules which handle decisions should call <literal>decision.setOutcome(\"result\")</literal> to determine the result of the decision. Rules which perform assignments should set the actor id using the <literal>Assignable</literal>."
-msgstr ""
+msgstr "Alcuni oggetti sono consultabili dalle regole come Drools globals, chiamate <literal>Assignable</literal> in jBPM, come <literal>assignable</literal> ed oggetto <literal>Decision</literal> in Seam, come <literal>decision</literal>. Le regole che gestiscono le decisioni dovrebbero chiamare <literal>decision.setOutcome(\"result\")</literal> per determinare il risultato della decisione. Le regole che eseguono assegnazioni dovrebbero impostare l'actor id usando <literal>Assignable</literal>."
#. Tag: programlisting
#: Drools.xml:119
@@ -382,17 +388,17 @@
#: Drools.xml:124
#, no-c-format
msgid "You can find out more about Drools at <ulink url=\"http://www.drools.org\"></ulink>"
-msgstr ""
+msgstr "Puoi trovare altre informazioni su Drools all'indirizzo <ulink url=\"http://www.drools.org\"></ulink>"
#. Tag: para
#: Drools.xml:131
#, no-c-format
msgid "Seam comes with enough of Drools' dependencies to implement some simple rules. If you want to add extra capabilities to Drools you should download the full distribution and add in extra dependencies as needed."
-msgstr ""
+msgstr "Seam viene fornito con dipendenze Drools sufficienti per implementare alcune regole semplici. Per aggiungere ulteriori funzionalità a Drools occorre scaricare la distribuzione completa ed aggiungere le dipendenze necessarie."
#. Tag: para
#: Drools.xml:140
#, no-c-format
msgid "Drools comes with MVEL compiled for Java 1.4, which is compatible with Java 1.4, Java 5 and Java 6. You may want to change your MVEL jar with one compiled for the version of Java you are using"
-msgstr ""
+msgstr "Drools viene rilasciato con MVEL compilato per Java 1.4, che è compatibile con Java 1.4, Java 5 e Java 6. Puoi cambiare il jar MVEL con quello compilato per la tua versione di Java."
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,7 +6,7 @@
"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-15 23:17+0100\n"
+"PO-Revision-Date: 2008-12-16 11:18+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -415,7 +415,7 @@
#: Jbpm.xml:253
#, no-c-format
msgid "Of course, we still need to define what happens if a request originates from a page rendered during a pageflow, and the conversation with the pageflow no longer exists. In this case, the <literal>no-conversation-view-id</literal> declaration goes into the pageflow definition:"
-msgstr ""
+msgstr "Occorre ancora definire cosa succede se una richiesta ha origine da una pagina generata durante un pageflow mentre la conversazione con il pageflow non esiste più. In questo caso la dichiarazione <literal>no-conversation-view-id</literal> va dentro la definizione del pageflow:"
#. Tag: programlisting
#: Jbpm.xml:261
@@ -461,7 +461,7 @@
#: Jbpm.xml:278
#, no-c-format
msgid "We need to install the Seam jBPM-related components, and place the pageflow definitions (using the standard <literal>.jpdl.xml</literal> extension) inside a Seam archive (an archive which contains a <literal>seam.properties</literal> file):"
-msgstr ""
+msgstr "Vanno installati i componenti di Seam relativi a jBPM e vanno collocate le definizione dei pageflow (usando l'estensione standard <literal>.jpdl.xml</literal>) dentro l'archivio Seam (un archivio che contiene un file <literal>seam.properties</literal>):"
#. Tag: programlisting
#: Jbpm.xml:285
@@ -473,7 +473,7 @@
#: Jbpm.xml:287
#, no-c-format
msgid "We can also explicitly tell Seam where to find our pageflow definition. We specify this in <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Possiamo anche comunicare esplicitamente a Seam dove trovare le definizioni dei pageflow. Questo viene specificato dentro <literal>components.xml</literal>:"
#. Tag: programlisting
#: Jbpm.xml:292
@@ -597,7 +597,7 @@
#: Jbpm.xml:335
#, no-c-format
msgid "Each <literal><page></literal> node represents a state where the system is waiting for user input:"
-msgstr ""
+msgstr "Ogni nodo <literal><page></literal> rappresenta uno stato in cui il sistema aspetta input da parte dell'utente:"
#. Tag: programlisting
#: Jbpm.xml:340
@@ -627,7 +627,7 @@
#: Jbpm.xml:351
#, no-c-format
msgid "The transition name is the name of a JSF outcome triggered by clicking a command button or command link in <literal>numberGuess.jsp</literal>."
-msgstr ""
+msgstr "Il nome della transizione è il nome dell'esito JSF lanciato cliccando un command button od un command link in <literal>numberGuess.jsp</literal>."
#. Tag: programlisting
#: Jbpm.xml:356
@@ -682,7 +682,7 @@
#: Jbpm.xml:384
#, no-c-format
msgid "It is even possible to have the button call an action method, in which case the action outcome will determine the transition to be taken:"
-msgstr ""
+msgstr "E' anche possibile che il pulsante chiami un action method, nel qual caso l'esito dell'azione determinerà la transizione da prendere:"
#. Tag: programlisting
#: Jbpm.xml:389
@@ -740,7 +740,7 @@
#: Jbpm.xml:411
#, no-c-format
msgid "A decision is made by evaluating a JSF EL expression in the Seam contexts."
-msgstr ""
+msgstr "Una decisione viene presa valutando un'espressione EL JSF nei contesti di Seam."
#. Tag: title
#: Jbpm.xml:418
@@ -772,7 +772,7 @@
#: Jbpm.xml:428
#, no-c-format
msgid "Optionally, we can end a task, specify a jBPM <literal>transition</literal> name. In this case, Seam will signal the end of the current task in the overarching business process."
-msgstr ""
+msgstr "Opzionalmente possiamo terminare un task specificando un nome alla <literal>transition</literal> jBPM. In questo modo Seam segnalerà la fine del task corrente al processo di business sottostante."
#. Tag: programlisting
#: Jbpm.xml:434
@@ -932,7 +932,7 @@
#: Jbpm.xml:534
#, no-c-format
msgid "We always need to know what user is currently logged in. jBPM \"knows\" users by their <emphasis>actor id</emphasis> and <emphasis>group actor ids</emphasis>. We specify the current actor ids using the built in Seam component named <literal>actor</literal>:"
-msgstr ""
+msgstr "Bisogna sempre sapere quale utente è attualmente loggato. jBPM \"riconosce\" gli utenti dal loro <emphasis>actor id</emphasis> e dai <emphasis>group actor id</emphasis>. Specificheremo gli attuali actor id usando il componente interno di Seam chiamato <literal>actor</literal>:"
#. Tag: programlisting
#: Jbpm.xml:542
More information about the seam-commits
mailing list