seam-commits December 2008

seam-commits@lists.jboss.org

1 participants
172 discussions

by seam-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2008-12-13 13:59:46 -0500 (Sat, 13 Dec 2008) New Revision: 9771 Modified: trunk/build/ci.build.xml Log: Publish italian docs Modified: trunk/build/ci.build.xml =================================================================== --- trunk/build/ci.build.xml 2008-12-13 18:38:38 UTC (rev 9770) +++ trunk/build/ci.build.xml 2008-12-13 18:59:46 UTC (rev 9771) @@ -113,6 +113,7 @@ <remoteRepository refId="snapshots.jboss.org" /> <attach file="${doc.ref.dir}/target/docbook/publish/en-US/pdf/seam_reference.pdf" classifier="en-US" type="pdf" /> <attach file="${doc.ref.dir}/target/docbook/publish/fr-FR/pdf/seam_reference.pdf" classifier="fr-FR" type="pdf" /> + <attach file="${doc.ref.dir}/target/docbook/publish/it-IT/pdf/seam_reference.pdf" classifier="it-IT" type="pdf" /> </artifact:deploy> </target>

15 years, 9 months

1
0
0 / 0

Seam SVN: r9770 - in trunk: doc/Seam_Reference_Guide/as-IN and 24 other directories.

by seam-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2008-12-13 13:38:38 -0500 (Sat, 13 Dec 2008) New Revision: 9770 Added: trunk/doc/Seam_Reference_Guide/as-IN/Performance.po trunk/doc/Seam_Reference_Guide/bn-IN/Performance.po trunk/doc/Seam_Reference_Guide/de-DE/Performance.po trunk/doc/Seam_Reference_Guide/es-ES/Performance.po trunk/doc/Seam_Reference_Guide/es-MX/Performance.po trunk/doc/Seam_Reference_Guide/fr-FR/Performance.po trunk/doc/Seam_Reference_Guide/gu-IN/Performance.po trunk/doc/Seam_Reference_Guide/hi-IN/Performance.po trunk/doc/Seam_Reference_Guide/it-IT/Performance.po trunk/doc/Seam_Reference_Guide/ja-JP/Performance.po trunk/doc/Seam_Reference_Guide/kn-IN/Performance.po trunk/doc/Seam_Reference_Guide/ko-KR/Performance.po trunk/doc/Seam_Reference_Guide/ml-IN/Performance.po trunk/doc/Seam_Reference_Guide/mr-IN/Performance.po trunk/doc/Seam_Reference_Guide/or-IN/Performance.po trunk/doc/Seam_Reference_Guide/pa-IN/Performance.po trunk/doc/Seam_Reference_Guide/pot/Performance.pot trunk/doc/Seam_Reference_Guide/pt-BR/Performance.po trunk/doc/Seam_Reference_Guide/ru-RU/Performance.po trunk/doc/Seam_Reference_Guide/si-LK/Performance.po trunk/doc/Seam_Reference_Guide/sl-SL/Performance.po trunk/doc/Seam_Reference_Guide/ta-IN/Performance.po trunk/doc/Seam_Reference_Guide/te-IN/Performance.po trunk/doc/Seam_Reference_Guide/zh-CN/Performance.po trunk/doc/Seam_Reference_Guide/zh-TW/Performance.po Modified: trunk/build/docs.pom.xml trunk/doc/Seam_Reference_Guide/as-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/bn-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/de-DE/Tutorial.po trunk/doc/Seam_Reference_Guide/es-ES/Tutorial.po trunk/doc/Seam_Reference_Guide/es-MX/Tutorial.po trunk/doc/Seam_Reference_Guide/fr-FR/Tutorial.po trunk/doc/Seam_Reference_Guide/gu-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/hi-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po trunk/doc/Seam_Reference_Guide/it-IT/Tools.po trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po trunk/doc/Seam_Reference_Guide/ja-JP/Tutorial.po trunk/doc/Seam_Reference_Guide/kn-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/ko-KR/Tutorial.po trunk/doc/Seam_Reference_Guide/ml-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/mr-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/or-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/pa-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/pot/Annotations.pot trunk/doc/Seam_Reference_Guide/pot/Author_Group.pot trunk/doc/Seam_Reference_Guide/pot/Book_Info.pot trunk/doc/Seam_Reference_Guide/pot/Cache.pot trunk/doc/Seam_Reference_Guide/pot/Components.pot trunk/doc/Seam_Reference_Guide/pot/Concepts.pot trunk/doc/Seam_Reference_Guide/pot/Configuration.pot trunk/doc/Seam_Reference_Guide/pot/Controls.pot trunk/doc/Seam_Reference_Guide/pot/Conversations.pot trunk/doc/Seam_Reference_Guide/pot/Dependencies.pot trunk/doc/Seam_Reference_Guide/pot/Drools.pot trunk/doc/Seam_Reference_Guide/pot/Elenhancements.pot trunk/doc/Seam_Reference_Guide/pot/Events.pot trunk/doc/Seam_Reference_Guide/pot/Excel.pot trunk/doc/Seam_Reference_Guide/pot/Feedback.pot trunk/doc/Seam_Reference_Guide/pot/Framework.pot trunk/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot trunk/doc/Seam_Reference_Guide/pot/Gettingstarted.pot trunk/doc/Seam_Reference_Guide/pot/Glassfish.pot trunk/doc/Seam_Reference_Guide/pot/Groovy.pot trunk/doc/Seam_Reference_Guide/pot/Gwt.pot trunk/doc/Seam_Reference_Guide/pot/Hsearch.pot trunk/doc/Seam_Reference_Guide/pot/I18n.pot trunk/doc/Seam_Reference_Guide/pot/Itext.pot trunk/doc/Seam_Reference_Guide/pot/Jbpm.pot trunk/doc/Seam_Reference_Guide/pot/Jms.pot trunk/doc/Seam_Reference_Guide/pot/Mail.pot trunk/doc/Seam_Reference_Guide/pot/Persistence.pot trunk/doc/Seam_Reference_Guide/pot/Preface.pot trunk/doc/Seam_Reference_Guide/pot/Remoting.pot trunk/doc/Seam_Reference_Guide/pot/Revision_History.pot trunk/doc/Seam_Reference_Guide/pot/Rss.pot trunk/doc/Seam_Reference_Guide/pot/Security.pot trunk/doc/Seam_Reference_Guide/pot/Spring.pot trunk/doc/Seam_Reference_Guide/pot/Testing.pot trunk/doc/Seam_Reference_Guide/pot/Text.pot trunk/doc/Seam_Reference_Guide/pot/Tools.pot trunk/doc/Seam_Reference_Guide/pot/Tutorial.pot trunk/doc/Seam_Reference_Guide/pot/Validation.pot trunk/doc/Seam_Reference_Guide/pot/Weblogic.pot trunk/doc/Seam_Reference_Guide/pot/Webservices.pot trunk/doc/Seam_Reference_Guide/pot/Websphere.pot trunk/doc/Seam_Reference_Guide/pot/Wicket.pot trunk/doc/Seam_Reference_Guide/pot/Xml.pot trunk/doc/Seam_Reference_Guide/pot/messages.mo trunk/doc/Seam_Reference_Guide/pt-BR/Tutorial.po trunk/doc/Seam_Reference_Guide/ru-RU/Tutorial.po trunk/doc/Seam_Reference_Guide/si-LK/Tutorial.po trunk/doc/Seam_Reference_Guide/sl-SL/Tutorial.po trunk/doc/Seam_Reference_Guide/ta-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/te-IN/Tutorial.po trunk/doc/Seam_Reference_Guide/zh-CN/Tutorial.po trunk/doc/Seam_Reference_Guide/zh-TW/Tutorial.po Log: Updates to po, add italian to docs build Modified: trunk/build/docs.pom.xml =================================================================== --- trunk/build/docs.pom.xml 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/build/docs.pom.xml 2008-12-13 18:38:38 UTC (rev 9770) @@ -66,6 +66,7 @@ <masterTranslation>en-US</masterTranslation> <translations> <translation>fr-FR</translation> + <translation>it-IT</translation> </translations> <imageResource> <directory>${pom.basedir}/en-US</directory> Added: trunk/doc/Seam_Reference_Guide/as-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/as-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/as-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language as-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/as-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/as-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/as-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/bn-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/bn-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/bn-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language bn-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/bn-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/bn-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/bn-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/de-DE/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/de-DE/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/de-DE/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language de-DE translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/de-DE/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/de-DE/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/de-DE/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/es-ES/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/es-ES/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/es-ES/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language es-ES translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/es-ES/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/es-ES/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/es-ES/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/es-MX/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/es-MX/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/es-MX/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language es-MX translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/es-MX/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/es-MX/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/es-MX/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-11-06 00:10+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/fr-FR/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/fr-FR/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/fr-FR/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language fr-FR translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/fr-FR/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/fr-FR/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/fr-FR/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/gu-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/gu-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/gu-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language gu-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/gu-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/gu-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/gu-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/hi-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/hi-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/hi-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language hi-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/hi-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/hi-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/hi-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Modified: trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: seam 2_0\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-10-14 11:38+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-11-23 17:06+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" @@ -14,134 +14,131 @@ "Content-Transfer-Encoding: 8bit\n" #. Tag: author -#: Author_Group.xml:3 +#: Author_Group.xml:5 #, no-c-format msgid "<firstname>Gavin</firstname> <surname>King</surname>" msgstr "<firstname>Gavin</firstname> <surname>King</surname>" -#. Tag: shortaffil -#: Author_Group.xml:7 -#, no-c-format -msgid "Project Lead" -msgstr "Capo progetto" - #. Tag: author -#: Author_Group.xml:10 +#: Author_Group.xml:9 #, no-c-format msgid "<firstname>Pete</firstname> <surname>Muir</surname>" msgstr "<firstname>Pete</firstname> <surname>Muir</surname>" #. Tag: author -#: Author_Group.xml:14 +#: Author_Group.xml:13 #, no-c-format msgid "<firstname>Norman</firstname> <surname>Richards</surname>" msgstr "<firstname>Norman</firstname> <surname>Richards</surname>" #. Tag: author -#: Author_Group.xml:18 +#: Author_Group.xml:17 #, no-c-format msgid "<firstname>Shane</firstname> <surname>Bryzak</surname>" msgstr "<firstname>Shane</firstname> <surname>Bryzak</surname>" #. Tag: author -#: Author_Group.xml:22 +#: Author_Group.xml:21 #, no-c-format msgid "<firstname>Michael</firstname> <surname>Yuan</surname>" msgstr "<firstname>Michael</firstname> <surname>Yuan</surname>" #. Tag: author -#: Author_Group.xml:26 +#: Author_Group.xml:25 #, no-c-format msgid "<firstname>Mike</firstname> <surname>Youngstrom</surname>" msgstr "<firstname>Mike</firstname> <surname>Youngstrom</surname>" #. Tag: author -#: Author_Group.xml:30 +#: Author_Group.xml:29 #, no-c-format msgid "<firstname>Christian</firstname> <surname>Bauer</surname>" msgstr "<firstname>Michael</firstname> <surname>Yuan</surname>" #. Tag: author -#: Author_Group.xml:34 +#: Author_Group.xml:33 #, no-c-format msgid "<firstname>Jay</firstname> <surname>Balunas</surname>" msgstr "<firstname>Jay</firstname> <surname>Balunas</surname>" #. Tag: author -#: Author_Group.xml:38 +#: Author_Group.xml:37 #, no-c-format msgid "<firstname>Dan</firstname> <surname>Allen</surname>" msgstr "<firstname>Dan</firstname> <surname>Allen</surname>" #. Tag: author -#: Author_Group.xml:42 +#: Author_Group.xml:41 #, no-c-format -msgid "<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</surname>" -msgstr "<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</surname>" +msgid "" +"<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</" +"surname>" +msgstr "" +"<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</" +"surname>" #. Tag: author -#: Author_Group.xml:47 +#: Author_Group.xml:46 #, no-c-format msgid "<firstname>Emmanuel</firstname> <surname>Bernard</surname>" msgstr "<firstname>Emmanuel</firstname> <surname>Bernard</surname>" #. Tag: author -#: Author_Group.xml:51 +#: Author_Group.xml:50 #, no-c-format msgid "<firstname>Nicklas</firstname> <surname>Karlsson</surname>" msgstr "<firstname>Nicklas</firstname> <surname>Karlsson</surname>" #. Tag: author -#: Author_Group.xml:55 +#: Author_Group.xml:54 #, no-c-format msgid "<firstname>Daniel</firstname> <surname>Roth</surname>" msgstr "<firstname>Daniel</firstname> <surname>Roth</surname>" #. Tag: author -#: Author_Group.xml:59 +#: Author_Group.xml:58 #, no-c-format msgid "<firstname>Matt</firstname> <surname>Drees</surname>" msgstr "<firstname>Matt</firstname> <surname>Drees</surname>" #. Tag: author -#: Author_Group.xml:63 +#: Author_Group.xml:62 #, no-c-format msgid "<firstname>Jacob</firstname> <surname>Orshalick</surname>" msgstr "<firstname>Jacob</firstname> <surname>Orshalick</surname>" #. Tag: author -#: Author_Group.xml:67 +#: Author_Group.xml:66 #, no-c-format msgid "<firstname>Marek</firstname> <surname>Novotny</surname>" msgstr "<firstname>Marek</firstname> <surname>Novotny</surname>" #. Tag: othercredit -#: Author_Group.xml:71 +#: Author_Group.xml:70 #, no-c-format msgid "<firstname>James</firstname> <surname>Cobb</surname>" msgstr "<firstname>James</firstname> <surname>Cobb</surname>" #. Tag: shortaffil -#: Author_Group.xml:75 -#: Author_Group.xml:82 +#: Author_Group.xml:74 Author_Group.xml:81 #, no-c-format msgid "Graphic Design" msgstr "Design Grafico" #. Tag: othercredit -#: Author_Group.xml:78 +#: Author_Group.xml:77 #, no-c-format msgid "<firstname>Cheyenne</firstname> <surname>Weaver</surname>" msgstr "<firstname>Cheyenne</firstname> <surname>Weaver</surname>" #. Tag: othercredit -#: Author_Group.xml:85 +#: Author_Group.xml:84 #, no-c-format msgid "<firstname>Mark</firstname> <surname>Newton</surname>" msgstr "<firstname>Mark</firstname> <surname>Newton</surname>" #. Tag: othercredit -#: Author_Group.xml:89 +#: Author_Group.xml:88 #, no-c-format msgid "<firstname>Steve</firstname> <surname>Ebersole</surname>" msgstr "" @@ -159,8 +156,10 @@ msgstr "" #. Tag: editor -#: Author_Group.xml:93 +#: Author_Group.xml:99 #, no-c-format msgid "<firstname>Samson</firstname> <surname>Kittoli</surname>" msgstr "<firstname>Samson</firstname> <surname>Kittoli</surname>" +#~ msgid "Project Lead" +#~ msgstr "Capo progetto" Added: trunk/doc/Seam_Reference_Guide/it-IT/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/it-IT/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language it-IT translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tools.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Tools.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/it-IT/Tools.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -35,7 +35,7 @@ #: Tools.xml:13 #, no-c-format msgid "<title>Business process designer</title>" -msgstr "\"<title>Designer del processo di business</title>\"" +msgstr "<title>Designer del processo di business</title>" #. Tag: para #: Tools.xml:15 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-12-13 15:49+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" @@ -28,8 +28,21 @@ #. Tag: para #: Tutorial.xml:9 #, no-c-format -msgid "Seam provides a number of example applications demonstrating how to use the various features of Seam. This tutorial will guide you through a few of those examples to help you get started learning Seam. The Seam examples are located in the <filename>examples</filename> subdirectory of the Seam distribution. The registration example, which will be the first example we look at, is in the <filename>examples/registration</filename> directory." -msgstr "Seam fornisce un ampio numeri di applicazioni d'esempio che dimostrano l'uso delle varie funzionalità di Seam. Questo tutorial ti guiderà attraverso alcuni di questi esempi per aiutarti nell'apprendimento di Seam. Gli esempi di Seam sono posizionati nella sottodirectory <filename>examples</filename> della distribuzione Seam. L'esempio di registrazione, che è il primo esempio che vediamo, si trova nella directoyry <filename>examples/registration</filename>." +msgid "" +"Seam provides a number of example applications demonstrating how to use the " +"various features of Seam. This tutorial will guide you through a few of " +"those examples to help you get started learning Seam. The Seam examples are " +"located in the <filename>examples</filename> subdirectory of the Seam " +"distribution. The registration example, which will be the first example we " +"look at, is in the <filename>examples/registration</filename> directory." +msgstr "" +"Seam fornisce un ampio numeri di applicazioni d'esempio che dimostrano l'uso " +"delle varie funzionalità di Seam. Questo tutorial ti guiderà attraverso " +"alcuni di questi esempi per aiutarti nell'apprendimento di Seam. Gli esempi " +"di Seam sono posizionati nella sottodirectory <filename>examples</filename> " +"della distribuzione Seam. L'esempio di registrazione, che è il primo esempio " +"che vediamo, si trova nella directoyry <filename>examples/registration</" +"filename>." #. Tag: para #: Tutorial.xml:15 @@ -40,25 +53,41 @@ #. Tag: para #: Tutorial.xml:19 #, no-c-format -msgid "The <filename>view</filename> directory contains view-related files such as web page templates, images and stylesheets." -msgstr "La directory <filename>view</filename> contiene i file relativi alla vista come template di pagine web, immagini e fogli di stile." +msgid "" +"The <filename>view</filename> directory contains view-related files such as " +"web page templates, images and stylesheets." +msgstr "" +"La directory <filename>view</filename> contiene i file relativi alla vista " +"come template di pagine web, immagini e fogli di stile." #. Tag: para #: Tutorial.xml:25 #, no-c-format -msgid "The <filename>resources</filename> directory contains deployment descriptors and other configuration files." -msgstr "La directory <filename>resources</filename> contiene i descrittori per il deploy ed altri file di configurazione." +msgid "" +"The <filename>resources</filename> directory contains deployment descriptors " +"and other configuration files." +msgstr "" +"La directory <filename>resources</filename> contiene i descrittori per il " +"deploy ed altri file di configurazione." #. Tag: para #: Tutorial.xml:30 #, no-c-format -msgid "The <filename>src</filename> directory contains the application source code." -msgstr "La directory <filename>src</filename> contiene il codice sorgente dell'applicazione." +msgid "" +"The <filename>src</filename> directory contains the application source code." +msgstr "" +"La directory <filename>src</filename> contiene il codice sorgente " +"dell'applicazione." #. Tag: para #: Tutorial.xml:35 #, no-c-format -msgid "The example applications run both on JBoss AS and Tomcat with no additional configuration. The following sections will explain the procedure in both cases. Note that all the examples are built and run from the Ant <filename>build.xml</filename>, so you'll need a recent version of Ant installed before you get started." +msgid "" +"The example applications run both on JBoss AS and Tomcat with no additional " +"configuration. The following sections will explain the procedure in both " +"cases. Note that all the examples are built and run from the Ant " +"<filename>build.xml</filename>, so you'll need a recent version of Ant " +"installed before you get started." msgstr "" #. Tag: title @@ -70,19 +99,41 @@ #. Tag: para #: Tutorial.xml:47 #, no-c-format -msgid "The examples are configured for use on JBoss 4.2. You'll need to set <literal>jboss.home</literal>, in the shared <literal>build.properties</literal> file in the root folder of your Seam installation, to the location of your JBoss AS installation." +msgid "" +"The examples are configured for use on JBoss 4.2. You'll need to set " +"<literal>jboss.home</literal>, in the shared <literal>build.properties</" +"literal> file in the root folder of your Seam installation, to the location " +"of your JBoss AS installation." msgstr "" #. Tag: para #: Tutorial.xml:51 #, no-c-format -msgid "Once you've set the location of JBoss AS and started the application server, you can build and deploy any example by typing <literal>ant explode</literal> in the the directory for that example. Any example that is packaged as an EAR deploys to a URL like <literal>/seam-<replaceable>example</replaceable></literal>, where <replaceable>example</replaceable> is the name of the example folder, with one exception. If the example folder begins with seam, the prefix \"seam\" is ommitted. For instance, if JBoss AS is running on port 8080, the URL for the registration example is <ulink url=\"http://localhost:8080/seam-registration/\"> <literal>http://localhost:8080/seam-registration/</literal></ulink>, whereas the URL for the seamspace example is <ulink url=\"http://localhost:8080/seam-space/\"> <literal>http://localhost:8080/seam-space/</literal></ulink>." +msgid "" +"Once you've set the location of JBoss AS and started the application server, " +"you can build and deploy any example by typing <literal>ant explode</" +"literal> in the the directory for that example. Any example that is packaged " +"as an EAR deploys to a URL like <literal>/seam-<replaceable>example</" +"replaceable></literal>, where <replaceable>example</replaceable> is the name " +"of the example folder, with one exception. If the example folder begins with " +"seam, the prefix \"seam\" is ommitted. For instance, if JBoss AS is running " +"on port 8080, the URL for the registration example is <ulink url=\"http://" +"localhost:8080/seam-registration/\"> <literal>http://localhost:8080/seam-" +"registration/</literal></ulink>, whereas the URL for the seamspace example " +"is <ulink url=\"http://localhost:8080/seam-space/\"> <literal>http://" +"localhost:8080/seam-space/</literal></ulink>." msgstr "" #. Tag: para #: Tutorial.xml:62 #, no-c-format -msgid "If, on the other hand, the example gets packaged as a WAR, then it deploys to a URL like <literal>/jboss-seam-<replaceable>example</replaceable></literal>. Most of the examples can be deployed as a WAR to Tomcat with Embedded JBoss by typing <literal>ant tomcat.deploy</literal>. Several of the examples can only be deployed as a WAR. Those examples are groovybooking, hibernate, jpa, and spring." +msgid "" +"If, on the other hand, the example gets packaged as a WAR, then it deploys " +"to a URL like <literal>/jboss-seam-<replaceable>example</replaceable></" +"literal>. Most of the examples can be deployed as a WAR to Tomcat with " +"Embedded JBoss by typing <literal>ant tomcat.deploy</literal>. Several of " +"the examples can only be deployed as a WAR. Those examples are " +"groovybooking, hibernate, jpa, and spring." msgstr "" #. Tag: title @@ -94,25 +145,44 @@ #. Tag: para #: Tutorial.xml:73 #, no-c-format -msgid "The examples are also configured for use on Tomcat 6.0. You will need to follow the instructions in <xref linkend=\"config.install.embedded\"/> for installing JBoss Embedded on Tomcat 6.0. JBoss Embedded is only required to run the Seam demos that use EJB3 components on Tomcat. There are also examples of non-EJB3 applications that can be run on Tomcat without the use of JBoss Embedded." +msgid "" +"The examples are also configured for use on Tomcat 6.0. You will need to " +"follow the instructions in <xref linkend=\"config.install.embedded\"/> for " +"installing JBoss Embedded on Tomcat 6.0. JBoss Embedded is only required to " +"run the Seam demos that use EJB3 components on Tomcat. There are also " +"examples of non-EJB3 applications that can be run on Tomcat without the use " +"of JBoss Embedded." msgstr "" #. Tag: para #: Tutorial.xml:79 #, no-c-format -msgid "You'll need to set <literal>tomcat.home</literal>, in the shared <literal>build.properties</literal> file in the root folder of your Seam installation, to the location of your Tomcat installation. make sure you set the location of your Tomcat." +msgid "" +"You'll need to set <literal>tomcat.home</literal>, in the shared " +"<literal>build.properties</literal> file in the root folder of your Seam " +"installation, to the location of your Tomcat installation. make sure you set " +"the location of your Tomcat." msgstr "" #. Tag: para #: Tutorial.xml:85 #, no-c-format -msgid "You'll need to use a different Ant target when using Tomcat. Use <literal>ant tomcat.deploy</literal> in example subdirectory to build and deploy any example for Tomcat." +msgid "" +"You'll need to use a different Ant target when using Tomcat. Use " +"<literal>ant tomcat.deploy</literal> in example subdirectory to build and " +"deploy any example for Tomcat." msgstr "" #. Tag: para #: Tutorial.xml:90 #, no-c-format -msgid "On Tomcat, the examples deploy to URLs like <literal>/jboss-seam-<replaceable>example</replaceable></literal>, so for the registration example the URL would be <ulink url=\"http://localhost:8080/jboss-seam-registration/\"> <literal>http://localhost:8080/jboss-seam-registration/</literal></ulink>. The same is true for examples that deploy as a WAR, as mentioned in the previous section." +msgid "" +"On Tomcat, the examples deploy to URLs like <literal>/jboss-seam-" +"<replaceable>example</replaceable></literal>, so for the registration " +"example the URL would be <ulink url=\"http://localhost:8080/jboss-seam-" +"registration/\"> <literal>http://localhost:8080/jboss-seam-registration/</" +"literal></ulink>. The same is true for examples that deploy as a WAR, as " +"mentioned in the previous section." msgstr "" #. Tag: title @@ -124,7 +194,12 @@ #. Tag: para #: Tutorial.xml:101 #, no-c-format -msgid "Most of the examples come with a suite of TestNG integration tests. The easiest way to run the tests is to run <literal>ant test</literal>. It is also possible to run the tests inside your IDE using the TestNG plugin. Consult the readme.txt in the examples directory of the Seam distribution for more information." +msgid "" +"Most of the examples come with a suite of TestNG integration tests. The " +"easiest way to run the tests is to run <literal>ant test</literal>. It is " +"also possible to run the tests inside your IDE using the TestNG plugin. " +"Consult the readme.txt in the examples directory of the Seam distribution " +"for more information." msgstr "" #. Tag: title @@ -136,26 +211,32 @@ #. Tag: para #: Tutorial.xml:114 #, no-c-format -msgid "The registration example is a simple application that lets a new user store his username, real name and password in the database. The example isn't intended to show off all of the cool functionality of Seam. However, it demonstrates the use of an EJB3 session bean as a JSF action listener, and basic configuration of Seam." +msgid "" +"The registration example is a simple application that lets a new user store " +"his username, real name and password in the database. The example isn't " +"intended to show off all of the cool functionality of Seam. However, it " +"demonstrates the use of an EJB3 session bean as a JSF action listener, and " +"basic configuration of Seam." msgstr "" #. Tag: para #: Tutorial.xml:119 #, no-c-format -msgid "We'll go slowly, since we realize you might not yet be familiar with EJB 3.0." +msgid "" +"We'll go slowly, since we realize you might not yet be familiar with EJB 3.0." msgstr "" #. Tag: para #: Tutorial.xml:121 #, no-c-format -msgid "The start page displays a very basic form with three input fields. Try filling them in and then submitting the form. This will save a user object in the database." +msgid "" +"The start page displays a very basic form with three input fields. Try " +"filling them in and then submitting the form. This will save a user object " +"in the database." msgstr "" #. Tag: title -#: Tutorial.xml:134 -#: Tutorial.xml:533 -#: Tutorial.xml:722 -#: Tutorial.xml:955 +#: Tutorial.xml:134 Tutorial.xml:533 Tutorial.xml:722 Tutorial.xml:955 #, no-c-format msgid "Understanding the code" msgstr "Capire il codice" @@ -163,7 +244,10 @@ #. Tag: para #: Tutorial.xml:136 #, no-c-format -msgid "The example is implemented with two Facelets templates, one entity bean and one stateless session bean. Let's take a look at the code, starting from the \"bottom\"." +msgid "" +"The example is implemented with two Facelets templates, one entity bean and " +"one stateless session bean. Let's take a look at the code, starting from the " +"\"bottom\"." msgstr "" #. Tag: title @@ -175,7 +259,11 @@ #. Tag: para #: Tutorial.xml:143 #, no-c-format -msgid "We need an EJB entity bean for user data. This class defines <emphasis>persistence</emphasis> and <emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra annotations that define the class as a Seam component." +msgid "" +"We need an EJB entity bean for user data. This class defines " +"<emphasis>persistence</emphasis> and <emphasis>validation</emphasis> " +"declaratively, via annotations. It also needs some extra annotations that " +"define the class as a Seam component." msgstr "" #. Tag: title @@ -303,85 +391,135 @@ #. Tag: para #: Tutorial.xml:163 #, no-c-format -msgid "The EJB3 standard <literal>@Entity</literal> annotation indicates that the <literal>User</literal> class is an entity bean." +msgid "" +"The EJB3 standard <literal>@Entity</literal> annotation indicates that the " +"<literal>User</literal> class is an entity bean." msgstr "" #. Tag: para #: Tutorial.xml:167 #, no-c-format -msgid "A Seam component needs a <emphasis>component name</emphasis> specified by the <link linkend=\"name-annotation\"> <literal>@Name</literal> </link> annotation. This name must be unique within the Seam application. When JSF asks Seam to resolve a context variable with a name that is the same as a Seam component name, and the context variable is currently undefined (null), Seam will instantiate that component, and bind the new instance to the context variable. In this case, Seam will instantiate a <literal>User</literal> the first time JSF encounters a variable named <literal>user</literal>." +msgid "" +"A Seam component needs a <emphasis>component name</emphasis> specified by " +"the <link linkend=\"name-annotation\"> <literal>@Name</literal> </link> " +"annotation. This name must be unique within the Seam application. When JSF " +"asks Seam to resolve a context variable with a name that is the same as a " +"Seam component name, and the context variable is currently undefined (null), " +"Seam will instantiate that component, and bind the new instance to the " +"context variable. In this case, Seam will instantiate a <literal>User</" +"literal> the first time JSF encounters a variable named <literal>user</" +"literal>." msgstr "" #. Tag: para #: Tutorial.xml:178 #, no-c-format -msgid "Whenever Seam instantiates a component, it binds the new instance to a context variable in the component's <emphasis>default context</emphasis>. The default context is specified using the <link linkend=\"scope-annotation\"> <literal>@Scope</literal> </link> annotation. The <literal>User</literal> bean is a session scoped component." +msgid "" +"Whenever Seam instantiates a component, it binds the new instance to a " +"context variable in the component's <emphasis>default context</emphasis>. " +"The default context is specified using the <link linkend=\"scope-annotation" +"\"> <literal>@Scope</literal> </link> annotation. The <literal>User</" +"literal> bean is a session scoped component." msgstr "" #. Tag: para #: Tutorial.xml:186 #, no-c-format -msgid "The EJB standard <literal>@Table</literal> annotation indicates that the <literal>User</literal> class is mapped to the <literal>users</literal> table." +msgid "" +"The EJB standard <literal>@Table</literal> annotation indicates that the " +"<literal>User</literal> class is mapped to the <literal>users</literal> " +"table." msgstr "" #. Tag: para #: Tutorial.xml:191 #, no-c-format -msgid "<literal>name</literal>, <literal>password</literal> and <literal>username</literal> are the persistent attributes of the entity bean. All of our persistent attributes define accessor methods. These are needed when this component is used by JSF in the render response and update model values phases." +msgid "" +"<literal>name</literal>, <literal>password</literal> and <literal>username</" +"literal> are the persistent attributes of the entity bean. All of our " +"persistent attributes define accessor methods. These are needed when this " +"component is used by JSF in the render response and update model values " +"phases." msgstr "" #. Tag: para #: Tutorial.xml:198 #, no-c-format -msgid "An empty constructor is both required by both the EJB specification and by Seam." +msgid "" +"An empty constructor is both required by both the EJB specification and by " +"Seam." msgstr "Un costruttore vuoto è richiesto sia dalla specifica EJB sia da Seam." #. Tag: para #: Tutorial.xml:202 #, no-c-format -msgid "The <literal>@NotNull</literal> and <literal>@Length</literal> annotations are part of the Hibernate Validator framework. Seam integrates Hibernate Validator and lets you use it for data validation (even if you are not using Hibernate for persistence)." +msgid "" +"The <literal>@NotNull</literal> and <literal>@Length</literal> annotations " +"are part of the Hibernate Validator framework. Seam integrates Hibernate " +"Validator and lets you use it for data validation (even if you are not using " +"Hibernate for persistence)." msgstr "" #. Tag: para #: Tutorial.xml:208 #, no-c-format -msgid "The EJB standard <literal>@Id</literal> annotation indicates the primary key attribute of the entity bean." +msgid "" +"The EJB standard <literal>@Id</literal> annotation indicates the primary key " +"attribute of the entity bean." msgstr "" #. Tag: para #: Tutorial.xml:214 #, no-c-format -msgid "The most important things to notice in this example are the <literal>@Name</literal> and <literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component." +msgid "" +"The most important things to notice in this example are the <literal>@Name</" +"literal> and <literal>@Scope</literal> annotations. These annotations " +"establish that this class is a Seam component." msgstr "" #. Tag: para #: Tutorial.xml:216 #, no-c-format -msgid "We'll see below that the properties of our <literal>User</literal> class are bound directly to JSF components and are populated by JSF during the update model values phase. We don't need any tedious glue code to copy data back and forth between the JSP pages and the entity bean domain model." +msgid "" +"We'll see below that the properties of our <literal>User</literal> class are " +"bound directly to JSF components and are populated by JSF during the update " +"model values phase. We don't need any tedious glue code to copy data back " +"and forth between the JSP pages and the entity bean domain model." msgstr "" #. Tag: para #: Tutorial.xml:220 #, no-c-format -msgid "However, entity beans shouldn't do transaction management or database access. So we can't use this component as a JSF action listener. For that we need a session bean." +msgid "" +"However, entity beans shouldn't do transaction management or database " +"access. So we can't use this component as a JSF action listener. For that we " +"need a session bean." msgstr "" #. Tag: title #: Tutorial.xml:226 #, no-c-format -msgid "The stateless session bean class: <literal>RegisterAction.java</literal>" -msgstr "Classe del bean di sessione stateless: <literal>RegisterAction.java</literal>" +msgid "" +"The stateless session bean class: <literal>RegisterAction.java</literal>" +msgstr "" +"Classe del bean di sessione stateless: <literal>RegisterAction.java</literal>" #. Tag: para #: Tutorial.xml:228 #, no-c-format -msgid "Most Seam application use session beans as JSF action listeners (you can use JavaBeans instead if you like)." +msgid "" +"Most Seam application use session beans as JSF action listeners (you can use " +"JavaBeans instead if you like)." msgstr "" #. Tag: para #: Tutorial.xml:230 #, no-c-format -msgid "We have exactly one JSF action in our application, and one session bean method attached to it. In this case, we'll use a stateless session bean, since all the state associated with our action is held by the <literal>User</literal> bean." +msgid "" +"We have exactly one JSF action in our application, and one session bean " +"method attached to it. In this case, we'll use a stateless session bean, " +"since all the state associated with our action is held by the <literal>User</" +"literal> bean." msgstr "" #. Tag: para @@ -427,7 +565,8 @@ " }\n" " else\n" " {\n" -" FacesMessages.instance().add(\"User #{user.username} already exists\");\n" +" FacesMessages.instance().add(\"User #{user.username} already exists" +"\");\n" " return null;\n" " }\n" " }\n" @@ -461,7 +600,8 @@ " }\n" " else\n" " {\n" -" FacesMessages.instance().add(\"User #{user.username} already exists\");\n" +" FacesMessages.instance().add(\"User #{user.username} already exists" +"\");\n" " return null;\n" " }\n" " }\n" @@ -471,73 +611,123 @@ #. Tag: para #: Tutorial.xml:254 #, no-c-format -msgid "The EJB <literal>@Stateless</literal> annotation marks this class as a stateless session bean." +msgid "" +"The EJB <literal>@Stateless</literal> annotation marks this class as a " +"stateless session bean." msgstr "" #. Tag: para #: Tutorial.xml:258 #, no-c-format -msgid "The <link linkend=\"in-annotation\"> <literal>@In</literal> </link> annotation marks an attribute of the bean as injected by Seam. In this case, the attribute is injected from a context variable named <literal>user</literal> (the instance variable name)." +msgid "" +"The <link linkend=\"in-annotation\"> <literal>@In</literal> </link> " +"annotation marks an attribute of the bean as injected by Seam. In this case, " +"the attribute is injected from a context variable named <literal>user</" +"literal> (the instance variable name)." msgstr "" #. Tag: para #: Tutorial.xml:265 #, no-c-format -msgid "The EJB standard <literal>@PersistenceContext</literal> annotation is used to inject the EJB3 entity manager." +msgid "" +"The EJB standard <literal>@PersistenceContext</literal> annotation is used " +"to inject the EJB3 entity manager." msgstr "" #. Tag: para #: Tutorial.xml:269 #, no-c-format -msgid "The Seam <literal>@Logger</literal> annotation is used to inject the component's <literal>Log</literal> instance." +msgid "" +"The Seam <literal>@Logger</literal> annotation is used to inject the " +"component's <literal>Log</literal> instance." msgstr "" #. Tag: para #: Tutorial.xml:273 #, no-c-format -msgid "The action listener method uses the standard EJB3 <literal>EntityManager</literal> API to interact with the database, and returns the JSF outcome. Note that, since this is a session bean, a transaction is automatically begun when the <literal>register()</literal> method is called, and committed when it completes." +msgid "" +"The action listener method uses the standard EJB3 <literal>EntityManager</" +"literal> API to interact with the database, and returns the JSF outcome. " +"Note that, since this is a session bean, a transaction is automatically " +"begun when the <literal>register()</literal> method is called, and committed " +"when it completes." msgstr "" #. Tag: para #: Tutorial.xml:280 #, no-c-format -msgid "Notice that Seam lets you use a JSF EL expression inside EJB-QL. Under the covers, this results in an ordinary JPA <literal>setParameter()</literal> call on the standard JPA <literal>Query</literal> object. Nice, huh?" +msgid "" +"Notice that Seam lets you use a JSF EL expression inside EJB-QL. Under the " +"covers, this results in an ordinary JPA <literal>setParameter()</literal> " +"call on the standard JPA <literal>Query</literal> object. Nice, huh?" msgstr "" #. Tag: para #: Tutorial.xml:285 #, no-c-format -msgid "The <literal>Log</literal> API lets us easily display templated log messages which can also make use of JSF EL expressions." +msgid "" +"The <literal>Log</literal> API lets us easily display templated log messages " +"which can also make use of JSF EL expressions." msgstr "" #. Tag: para #: Tutorial.xml:290 #, no-c-format -msgid "JSF action listener methods return a string-valued outcome that determines what page will be displayed next. A null outcome (or a void action listener method) redisplays the previous page. In plain JSF, it is normal to always use a JSF <emphasis>navigation rule</emphasis> to determine the JSF view id from the outcome. For complex application this indirection is useful and a good practice. However, for very simple examples like this one, Seam lets you use the JSF view id as the outcome, eliminating the requirement for a navigation rule. <emphasis>Note that when you use a view id as an outcome, Seam always performs a browser redirect.</emphasis>" +msgid "" +"JSF action listener methods return a string-valued outcome that determines " +"what page will be displayed next. A null outcome (or a void action listener " +"method) redisplays the previous page. In plain JSF, it is normal to always " +"use a JSF <emphasis>navigation rule</emphasis> to determine the JSF view id " +"from the outcome. For complex application this indirection is useful and a " +"good practice. However, for very simple examples like this one, Seam lets " +"you use the JSF view id as the outcome, eliminating the requirement for a " +"navigation rule. <emphasis>Note that when you use a view id as an outcome, " +"Seam always performs a browser redirect.</emphasis>" msgstr "" #. Tag: para #: Tutorial.xml:302 #, no-c-format -msgid "Seam provides a number of <emphasis>built-in components</emphasis> to help solve common problems. The <literal>FacesMessages</literal> component makes it easy to display templated error or success messages. (As of Seam 2.1, you can use <literal>StatusMessages</literal> instead to remove the semantic dependency on JSF). Built-in Seam components may be obtained by injection, or by calling the <literal>instance()</literal> method on the class of the built-in component." +msgid "" +"Seam provides a number of <emphasis>built-in components</emphasis> to help " +"solve common problems. The <literal>FacesMessages</literal> component makes " +"it easy to display templated error or success messages. (As of Seam 2.1, you " +"can use <literal>StatusMessages</literal> instead to remove the semantic " +"dependency on JSF). Built-in Seam components may be obtained by injection, " +"or by calling the <literal>instance()</literal> method on the class of the " +"built-in component." msgstr "" #. Tag: para #: Tutorial.xml:314 #, no-c-format -msgid "Note that we did not explicitly specify a <literal>@Scope</literal> this time. Each Seam component type has a default scope if not explicitly specified. For stateless session beans, the default scope is the stateless context, which is the only sensible value." +msgid "" +"Note that we did not explicitly specify a <literal>@Scope</literal> this " +"time. Each Seam component type has a default scope if not explicitly " +"specified. For stateless session beans, the default scope is the stateless " +"context, which is the only sensible value." msgstr "" #. Tag: para #: Tutorial.xml:318 #, no-c-format -msgid "Our session bean action listener performs the business and persistence logic for our mini-application. In more complex applications, we might need require a separate service layer. This is easy to achieve with Seam, but it's overkill for most web applications. Seam does not force you into any particular strategy for application layering, allowing your application to be as simple, or as complex, as you want." +msgid "" +"Our session bean action listener performs the business and persistence logic " +"for our mini-application. In more complex applications, we might need " +"require a separate service layer. This is easy to achieve with Seam, but " +"it's overkill for most web applications. Seam does not force you into any " +"particular strategy for application layering, allowing your application to " +"be as simple, or as complex, as you want." msgstr "" #. Tag: para #: Tutorial.xml:324 #, no-c-format -msgid "Note that in this simple application, we've actually made it far more complex than it needs to be. If we had used the Seam application framework controllers, we would have eliminated all of our application code. However, then we wouldn't have had much of an application to explain." +msgid "" +"Note that in this simple application, we've actually made it far more " +"complex than it needs to be. If we had used the Seam application framework " +"controllers, we would have eliminated all of our application code. However, " +"then we wouldn't have had much of an application to explain." msgstr "" #. Tag: title @@ -583,13 +773,18 @@ #. Tag: title #: Tutorial.xml:346 #, no-c-format -msgid "The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</literal>" +msgid "" +"The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</" +"literal>" msgstr "" #. Tag: para #: Tutorial.xml:348 #, no-c-format -msgid "The view pages for a Seam application could be implemented using any technology that supports JSF. In this example we use Facelets, because we think it's better than JSP." +msgid "" +"The view pages for a Seam application could be implemented using any " +"technology that supports JSF. In this example we use Facelets, because we " +"think it's better than JSP." msgstr "" #. Tag: title @@ -618,13 +813,17 @@ " <h:form>\n" " <s:validateAll>\n" " <h:panelGrid columns=\"2\">\n" -" Username: <h:inputText value=\"#{user.username}\" required=\"true\"/>\n" -" Real Name: <h:inputText value=\"#{user.name}\" required=\"true\"/>\n" -" Password: <h:inputSecret value=\"#{user.password}\" required=\"true\"/>\n" +" Username: <h:inputText value=\"#{user.username}\" required=" +"\"true\"/>\n" +" Real Name: <h:inputText value=\"#{user.name}\" required=" +"\"true\"/>\n" +" Password: <h:inputSecret value=\"#{user.password}\" " +"required=\"true\"/>\n" " </h:panelGrid>\n" " </s:validateAll>\n" " <h:messages/>\n" -" <h:commandButton value=\"Register\" action=\"#{register.register}\"/>\n" +" <h:commandButton value=\"Register\" action=\"#{register.register}" +"\"/>\n" " </h:form>\n" " </f:view>\n" " </body>\n" @@ -647,13 +846,17 @@ " <h:form>\n" " <s:validateAll>\n" " <h:panelGrid columns=\"2\">\n" -" Username: <h:inputText value=\"#{user.username}\" required=\"true\"/>\n" -" Real Name: <h:inputText value=\"#{user.name}\" required=\"true\"/>\n" -" Password: <h:inputSecret value=\"#{user.password}\" required=\"true\"/>\n" +" Username: <h:inputText value=\"#{user.username}\" required=" +"\"true\"/>\n" +" Real Name: <h:inputText value=\"#{user.name}\" required=" +"\"true\"/>\n" +" Password: <h:inputSecret value=\"#{user.password}\" " +"required=\"true\"/>\n" " </h:panelGrid>\n" " </s:validateAll>\n" " <h:messages/>\n" -" <h:commandButton value=\"Register\" action=\"#{register.register}\"/>\n" +" <h:commandButton value=\"Register\" action=\"#{register.register}" +"\"/>\n" " </h:form>\n" " </f:view>\n" " </body>\n" @@ -663,7 +866,11 @@ #. Tag: para #: Tutorial.xml:356 #, no-c-format -msgid "The only thing here that is specific to Seam is the <literal><s:validateAll></literal> tag. This JSF component tells JSF to validate all the contained input fields against the Hibernate Validator annotations specified on the entity bean." +msgid "" +"The only thing here that is specific to Seam is the <literal><s:" +"validateAll></literal> tag. This JSF component tells JSF to validate all " +"the contained input fields against the Hibernate Validator annotations " +"specified on the entity bean." msgstr "" #. Tag: title @@ -687,7 +894,8 @@ " </head>\n" " <body>\n" " <f:view>\n" -" Welcome, #{user.name}, you are successfully registered as #{user.username}.\n" +" Welcome, #{user.name}, you are successfully registered as #{user." +"username}.\n" " </f:view>\n" " </body>\n" "\n" @@ -705,7 +913,8 @@ " </head>\n" " <body>\n" " <f:view>\n" -" Welcome, #{user.name}, you are successfully registered as #{user.username}.\n" +" Welcome, #{user.name}, you are successfully registered as #{user." +"username}.\n" " </f:view>\n" " </body>\n" "\n" @@ -715,31 +924,53 @@ #. Tag: para #: Tutorial.xml:366 #, no-c-format -msgid "This is a simple Facelets page using some inline EL. There's nothing specific to Seam here." +msgid "" +"This is a simple Facelets page using some inline EL. There's nothing " +"specific to Seam here." msgstr "" #. Tag: title #: Tutorial.xml:371 #, no-c-format -msgid "The Seam component deployment descriptor: <literal>components.xml</literal>" +msgid "" +"The Seam component deployment descriptor: <literal>components.xml</literal>" msgstr "" #. Tag: para #: Tutorial.xml:373 #, no-c-format -msgid "Since this is the first Seam app we've seen, we'll take a look at the deployment descriptors. Before we get into them, it is worth noting that Seam strongly values minimal configuration. These configuration files will be created for you when you create a Seam application. You'll never need to touch most of these files. We're presenting them now only to help you understand what all the pieces in the example are doing." +msgid "" +"Since this is the first Seam app we've seen, we'll take a look at the " +"deployment descriptors. Before we get into them, it is worth noting that " +"Seam strongly values minimal configuration. These configuration files will " +"be created for you when you create a Seam application. You'll never need to " +"touch most of these files. We're presenting them now only to help you " +"understand what all the pieces in the example are doing." msgstr "" #. Tag: para #: Tutorial.xml:380 #, no-c-format -msgid "If you've used many Java frameworks before, you'll be used to having to declare all your component classes in some kind of XML file that gradually grows more and more unmanageable as your project matures. You'll be relieved to know that Seam does not require that application components be accompanied by XML. Most Seam applications require a very small amount of XML that does not grow very much as the project gets bigger." +msgid "" +"If you've used many Java frameworks before, you'll be used to having to " +"declare all your component classes in some kind of XML file that gradually " +"grows more and more unmanageable as your project matures. You'll be relieved " +"to know that Seam does not require that application components be " +"accompanied by XML. Most Seam applications require a very small amount of " +"XML that does not grow very much as the project gets bigger." msgstr "" #. Tag: para #: Tutorial.xml:386 #, no-c-format -msgid "Nevertheless, it is often useful to be able to provide for <emphasis>some</emphasis> external configuration of <emphasis>some</emphasis> components (particularly the components built in to Seam). You have a couple of options here, but the most flexible option is to provide this configuration in a file called <literal>components.xml</literal>, located in the <literal>WEB-INF</literal> directory. We'll use the <literal>components.xml</literal> file to tell Seam how to find our EJB components in JNDI:" +msgid "" +"Nevertheless, it is often useful to be able to provide for <emphasis>some</" +"emphasis> external configuration of <emphasis>some</emphasis> components " +"(particularly the components built in to Seam). You have a couple of options " +"here, but the most flexible option is to provide this configuration in a " +"file called <literal>components.xml</literal>, located in the <literal>WEB-" +"INF</literal> directory. We'll use the <literal>components.xml</literal> " +"file to tell Seam how to find our EJB components in JNDI:" msgstr "" #. Tag: title @@ -783,7 +1014,13 @@ #. Tag: para #: Tutorial.xml:396 #, no-c-format -msgid "This code configures a property named <literal>jndiPattern</literal> of a built-in Seam component named <literal>org.jboss.seam.core.init</literal>. The funny <literal>@</literal> symbols are there because our Ant build script puts the correct JNDI pattern in when we deploy the application, which it reads from the components.properties file. You learn more about how this process works in <xref linkend=\"xml.descriptor\"/>." +msgid "" +"This code configures a property named <literal>jndiPattern</literal> of a " +"built-in Seam component named <literal>org.jboss.seam.core.init</literal>. " +"The funny <literal>@</literal> symbols are there because our Ant build " +"script puts the correct JNDI pattern in when we deploy the application, " +"which it reads from the components.properties file. You learn more about how " +"this process works in <xref linkend=\"xml.descriptor\"/>." msgstr "" #. Tag: title @@ -795,7 +1032,9 @@ #. Tag: para #: Tutorial.xml:407 #, no-c-format -msgid "The presentation layer for our mini-application will be deployed in a WAR. So we'll need a web deployment descriptor." +msgid "" +"The presentation layer for our mini-application will be deployed in a WAR. " +"So we'll need a web deployment descriptor." msgstr "" #. Tag: title @@ -817,7 +1056,8 @@ " version=\"2.5\">\n" "\n" " <listener>\n" -" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n" +" <listener-class>org.jboss.seam.servlet.SeamListener</listener-" +"class>\n" " </listener>\n" " \n" " <context-param>\n" @@ -851,7 +1091,8 @@ " version=\"2.5\">\n" "\n" " <listener>\n" -" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n" +" <listener-class>org.jboss.seam.servlet.SeamListener</listener-" +"class>\n" " </listener>\n" " \n" " <context-param>\n" @@ -879,7 +1120,9 @@ #. Tag: para #: Tutorial.xml:414 #, no-c-format -msgid "This <literal>web.xml</literal> file configures Seam and JSF. The configuration you see here is pretty much identical in all Seam applications." +msgid "" +"This <literal>web.xml</literal> file configures Seam and JSF. The " +"configuration you see here is pretty much identical in all Seam applications." msgstr "" #. Tag: title @@ -891,7 +1134,11 @@ #. Tag: para #: Tutorial.xml:422 #, no-c-format -msgid "Most Seam applications use JSF views as the presentation layer. So usually we'll need <literal>faces-config.xml</literal>. In our case, we are going to use Facelets for defining our views, so we need to tell JSF to use Facelets as its templating engine." +msgid "" +"Most Seam applications use JSF views as the presentation layer. So usually " +"we'll need <literal>faces-config.xml</literal>. In our case, we are going to " +"use Facelets for defining our views, so we need to tell JSF to use Facelets " +"as its templating engine." msgstr "" #. Tag: title @@ -935,19 +1182,31 @@ #. Tag: para #: Tutorial.xml:432 #, no-c-format -msgid "Note that we don't need any JSF managed bean declarations! Our managed beans are annotated Seam components. In Seam applications, the <literal>faces-config.xml</literal> is used much less often than in plain JSF. Here, we are simply using it to enable Facelets as the view handler instead of JSP." +msgid "" +"Note that we don't need any JSF managed bean declarations! Our managed beans " +"are annotated Seam components. In Seam applications, the <literal>faces-" +"config.xml</literal> is used much less often than in plain JSF. Here, we are " +"simply using it to enable Facelets as the view handler instead of JSP." msgstr "" #. Tag: para #: Tutorial.xml:437 #, no-c-format -msgid "In fact, once you have all the basic descriptors set up, the <emphasis>only</emphasis> XML you need to write as you add new functionality to a Seam application is orchestration: navigation rules or jBPM process definitions. Seam's stand is that <emphasis>process flow</emphasis> and <emphasis>configuration data</emphasis> are the only things that truly belong in XML." +msgid "" +"In fact, once you have all the basic descriptors set up, the <emphasis>only</" +"emphasis> XML you need to write as you add new functionality to a Seam " +"application is orchestration: navigation rules or jBPM process definitions. " +"Seam's stand is that <emphasis>process flow</emphasis> and " +"<emphasis>configuration data</emphasis> are the only things that truly " +"belong in XML." msgstr "" #. Tag: para #: Tutorial.xml:442 #, no-c-format -msgid "In this simple example, we don't even need a navigation rule, since we decided to embed the view id in our action code." +msgid "" +"In this simple example, we don't even need a navigation rule, since we " +"decided to embed the view id in our action code." msgstr "" #. Tag: title @@ -959,7 +1218,10 @@ #. Tag: para #: Tutorial.xml:450 #, no-c-format -msgid "The <literal>ejb-jar.xml</literal> file integrates Seam with EJB3, by attaching the <literal>SeamInterceptor</literal> to all session beans in the archive." +msgid "" +"The <literal>ejb-jar.xml</literal> file integrates Seam with EJB3, by " +"attaching the <literal>SeamInterceptor</literal> to all session beans in the " +"archive." msgstr "" #. Tag: programlisting @@ -976,14 +1238,16 @@ " \n" " <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" " \n" @@ -999,14 +1263,16 @@ " \n" " <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" " \n" @@ -1015,13 +1281,17 @@ #. Tag: title #: Tutorial.xml:458 #, no-c-format -msgid "The EJB persistence deployment descriptor: <literal>persistence.xml</literal>" +msgid "" +"The EJB persistence deployment descriptor: <literal>persistence.xml</literal>" msgstr "" #. Tag: para #: Tutorial.xml:460 #, no-c-format -msgid "The <literal>persistence.xml</literal> file tells the EJB persistence provider where to find the datasource, and contains some vendor-specific settings. In this case, enables automatic schema export at startup time." +msgid "" +"The <literal>persistence.xml</literal> file tells the EJB persistence " +"provider where to find the datasource, and contains some vendor-specific " +"settings. In this case, enables automatic schema export at startup time." msgstr "" #. Tag: programlisting @@ -1040,7 +1310,8 @@ " <provider>org.hibernate.ejb.HibernatePersistence</provider>\n" " <jta-data-source>java:/DefaultDS</jta-data-source>\n" " <properties>\n" -" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/>\n" +" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/" +">\n" " </properties>\n" " </persistence-unit>\n" " \n" @@ -1058,7 +1329,8 @@ " <provider>org.hibernate.ejb.HibernatePersistence</provider>\n" " <jta-data-source>java:/DefaultDS</jta-data-source>\n" " <properties>\n" -" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/>\n" +" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/" +">\n" " </properties>\n" " </persistence-unit>\n" " \n" @@ -1073,7 +1345,9 @@ #. Tag: para #: Tutorial.xml:471 #, no-c-format -msgid "Finally, since our application is deployed as an EAR, we need a deployment descriptor there, too." +msgid "" +"Finally, since our application is deployed as an EAR, we need a deployment " +"descriptor there, too." msgstr "" #. Tag: title @@ -1145,20 +1419,21 @@ #. Tag: para #: Tutorial.xml:477 #, no-c-format -msgid "This deployment descriptor links modules in the enterprise archive and binds the web application to the context root <literal>/seam-registration</literal>." +msgid "" +"This deployment descriptor links modules in the enterprise archive and binds " +"the web application to the context root <literal>/seam-registration</" +"literal>." msgstr "" #. Tag: para #: Tutorial.xml:480 #, no-c-format -msgid "We've now seen <emphasis>all</emphasis> the files in the entire application!" +msgid "" +"We've now seen <emphasis>all</emphasis> the files in the entire application!" msgstr "" #. Tag: title -#: Tutorial.xml:486 -#: Tutorial.xml:673 -#: Tutorial.xml:887 -#: Tutorial.xml:1070 +#: Tutorial.xml:486 Tutorial.xml:673 Tutorial.xml:887 Tutorial.xml:1070 #, no-c-format msgid "How it works" msgstr "Come funziona" @@ -1166,37 +1441,65 @@ #. Tag: para #: Tutorial.xml:488 #, no-c-format -msgid "When the form is submitted, JSF asks Seam to resolve the variable named <literal>user</literal>. Since there is no value already bound to that name (in any Seam context), Seam instantiates the <literal>user</literal> component, and returns the resulting <literal>User</literal> entity bean instance to JSF after storing it in the Seam session context." +msgid "" +"When the form is submitted, JSF asks Seam to resolve the variable named " +"<literal>user</literal>. Since there is no value already bound to that name " +"(in any Seam context), Seam instantiates the <literal>user</literal> " +"component, and returns the resulting <literal>User</literal> entity bean " +"instance to JSF after storing it in the Seam session context." msgstr "" #. Tag: para #: Tutorial.xml:492 #, no-c-format -msgid "The form input values are now validated against the Hibernate Validator constraints specified on the <literal>User</literal> entity. If the constraints are violated, JSF redisplays the page. Otherwise, JSF binds the form input values to properties of the <literal>User</literal> entity bean." +msgid "" +"The form input values are now validated against the Hibernate Validator " +"constraints specified on the <literal>User</literal> entity. If the " +"constraints are violated, JSF redisplays the page. Otherwise, JSF binds the " +"form input values to properties of the <literal>User</literal> entity bean." msgstr "" #. Tag: para #: Tutorial.xml:495 #, no-c-format -msgid "Next, JSF asks Seam to resolve the variable named <literal>register</literal>. Seam uses the JNDI pattern mentioned earlier to locate the stateless session bean, wraps it as a Seam component, and returns it. Seam then presents this component to JSF and JSF invokes the <literal>register()</literal> action listener method." +msgid "" +"Next, JSF asks Seam to resolve the variable named <literal>register</" +"literal>. Seam uses the JNDI pattern mentioned earlier to locate the " +"stateless session bean, wraps it as a Seam component, and returns it. Seam " +"then presents this component to JSF and JSF invokes the <literal>register()</" +"literal> action listener method." msgstr "" #. Tag: para #: Tutorial.xml:499 #, no-c-format -msgid "But Seam is not done yet. Seam intercepts the method call and injects the <literal>User</literal> entity from the Seam session context, before allowing the invocation to continue." +msgid "" +"But Seam is not done yet. Seam intercepts the method call and injects the " +"<literal>User</literal> entity from the Seam session context, before " +"allowing the invocation to continue." msgstr "" #. Tag: para #: Tutorial.xml:501 #, no-c-format -msgid "The <literal>register()</literal> method checks if a user with the entered username already exists. If so, an error message is queued with the <literal>FacesMessages</literal> component, and a null outcome is returned, causing a page redisplay. The <literal>FacesMessages</literal> component interpolates the JSF expression embedded in the message string and adds a JSF <literal>FacesMessage</literal> to the view." +msgid "" +"The <literal>register()</literal> method checks if a user with the entered " +"username already exists. If so, an error message is queued with the " +"<literal>FacesMessages</literal> component, and a null outcome is returned, " +"causing a page redisplay. The <literal>FacesMessages</literal> component " +"interpolates the JSF expression embedded in the message string and adds a " +"JSF <literal>FacesMessage</literal> to the view." msgstr "" #. Tag: para #: Tutorial.xml:506 #, no-c-format -msgid "If no user with that username exists, the <literal>\"/registered.xhtml\"</literal> outcome triggers a browser redirect to the <literal>registered.xhtml</literal> page. When JSF comes to render the page, it asks Seam to resolve the variable named <literal>user</literal> and uses property values of the returned <literal>User</literal> entity from Seam's session scope." +msgid "" +"If no user with that username exists, the <literal>\"/registered.xhtml\"</" +"literal> outcome triggers a browser redirect to the <literal>registered." +"xhtml</literal> page. When JSF comes to render the page, it asks Seam to " +"resolve the variable named <literal>user</literal> and uses property values " +"of the returned <literal>User</literal> entity from Seam's session scope." msgstr "" #. Tag: title @@ -1208,13 +1511,20 @@ #. Tag: para #: Tutorial.xml:518 #, no-c-format -msgid "Clickable lists of database search results are such an important part of any online application that Seam provides special functionality on top of JSF to make it easier to query data using EJB-QL or HQL and display it as a clickable list using a JSF <literal><h:dataTable></literal>. The messages example demonstrates this functionality." +msgid "" +"Clickable lists of database search results are such an important part of any " +"online application that Seam provides special functionality on top of JSF to " +"make it easier to query data using EJB-QL or HQL and display it as a " +"clickable list using a JSF <literal><h:dataTable></literal>. The " +"messages example demonstrates this functionality." msgstr "" #. Tag: para #: Tutorial.xml:534 #, no-c-format -msgid "The message list example has one entity bean, <literal>Message</literal>, one session bean, <literal>MessageListBean</literal> and one JSP." +msgid "" +"The message list example has one entity bean, <literal>Message</literal>, " +"one session bean, <literal>MessageListBean</literal> and one JSP." msgstr "" #. Tag: title @@ -1226,7 +1536,9 @@ #. Tag: para #: Tutorial.xml:540 #, no-c-format -msgid "The <literal>Message</literal> entity defines the title, text, date and time of a message, and a flag indicating whether the message has been read:" +msgid "" +"The <literal>Message</literal> entity defines the title, text, date and time " +"of a message, and a flag indicating whether the message has been read:" msgstr "" #. Tag: title @@ -1376,19 +1688,33 @@ #. Tag: para #: Tutorial.xml:553 #, no-c-format -msgid "Just like in the previous example, we have a session bean, <literal>MessageManagerBean</literal>, which defines the action listener methods for the two buttons on our form. One of the buttons selects a message from the list, and displays that message. The other button deletes a message. So far, this is not so different to the previous example." +msgid "" +"Just like in the previous example, we have a session bean, " +"<literal>MessageManagerBean</literal>, which defines the action listener " +"methods for the two buttons on our form. One of the buttons selects a " +"message from the list, and displays that message. The other button deletes a " +"message. So far, this is not so different to the previous example." msgstr "" #. Tag: para #: Tutorial.xml:558 #, no-c-format -msgid "But <literal>MessageManagerBean</literal> is also responsible for fetching the list of messages the first time we navigate to the message list page. There are various ways the user could navigate to the page, and not all of them are preceded by a JSF action—the user might have bookmarked the page, for example. So the job of fetching the message list takes place in a Seam <emphasis>factory method</emphasis>, instead of in an action listener method." +msgid "" +"But <literal>MessageManagerBean</literal> is also responsible for fetching " +"the list of messages the first time we navigate to the message list page. " +"There are various ways the user could navigate to the page, and not all of " +"them are preceded by a JSF action—the user might have bookmarked the " +"page, for example. So the job of fetching the message list takes place in a " +"Seam <emphasis>factory method</emphasis>, instead of in an action listener " +"method." msgstr "" #. Tag: para #: Tutorial.xml:564 #, no-c-format -msgid "We want to cache the list of messages in memory between server requests, so we will make this a stateful session bean." +msgid "" +"We want to cache the list of messages in memory between server requests, so " +"we will make this a stateful session bean." msgstr "" #. Tag: title @@ -1419,7 +1745,8 @@ " @Factory(\"messageList\")\n" " public void findMessages()\n" " {\n" -" messageList = em.createQuery(\"select msg from Message msg order by msg.datetime desc\")\n" +" messageList = em.createQuery(\"select msg from Message msg order by " +"msg.datetime desc\")\n" " .getResultList();\n" " }\n" " \n" @@ -1458,7 +1785,8 @@ " @Factory(\"messageList\")\n" " public void findMessages()\n" " {\n" -" messageList = em.createQuery(\"select msg from Message msg order by msg.datetime desc\")\n" +" messageList = em.createQuery(\"select msg from Message msg order by " +"msg.datetime desc\")\n" " .getResultList();\n" " }\n" " \n" @@ -1482,61 +1810,99 @@ #. Tag: para #: Tutorial.xml:583 #, no-c-format -msgid "The <literal>@DataModel</literal> annotation exposes an attibute of type <literal>java.util.List</literal> to the JSF page as an instance of <literal>javax.faces.model.DataModel</literal>. This allows us to use the list in a JSF <literal><h:dataTable></literal> with clickable links for each row. In this case, the <literal>DataModel</literal> is made available in a session context variable named <literal>messageList</literal>." +msgid "" +"The <literal>@DataModel</literal> annotation exposes an attibute of type " +"<literal>java.util.List</literal> to the JSF page as an instance of " +"<literal>javax.faces.model.DataModel</literal>. This allows us to use the " +"list in a JSF <literal><h:dataTable></literal> with clickable links " +"for each row. In this case, the <literal>DataModel</literal> is made " +"available in a session context variable named <literal>messageList</literal>." msgstr "" #. Tag: para #: Tutorial.xml:591 #, no-c-format -msgid "The <literal>@DataModelSelection</literal> annotation tells Seam to inject the <literal>List</literal> element that corresponded to the clicked link." +msgid "" +"The <literal>@DataModelSelection</literal> annotation tells Seam to inject " +"the <literal>List</literal> element that corresponded to the clicked link." msgstr "" #. Tag: para #: Tutorial.xml:595 #, no-c-format -msgid "The <literal>@Out</literal> annotation then exposes the selected value directly to the page. So ever time a row of the clickable list is selected, the <literal>Message</literal> is injected to the attribute of the stateful bean, and the subsequently <emphasis>outjected</emphasis> to the event context variable named <literal>message</literal>." +msgid "" +"The <literal>@Out</literal> annotation then exposes the selected value " +"directly to the page. So every time a row of the clickable list is selected, " +"the <literal>Message</literal> is injected to the attribute of the stateful " +"bean, and the subsequently <emphasis>outjected</emphasis> to the event " +"context variable named <literal>message</literal>." msgstr "" #. Tag: para #: Tutorial.xml:602 #, no-c-format -msgid "This stateful bean has an EJB3 <emphasis>extended persistence context</emphasis>. The messages retrieved in the query remain in the managed state as long as the bean exists, so any subsequent method calls to the stateful bean can update them without needing to make any explicit call to the <literal>EntityManager</literal>." +msgid "" +"This stateful bean has an EJB3 <emphasis>extended persistence context</" +"emphasis>. The messages retrieved in the query remain in the managed state " +"as long as the bean exists, so any subsequent method calls to the stateful " +"bean can update them without needing to make any explicit call to the " +"<literal>EntityManager</literal>." msgstr "" #. Tag: para #: Tutorial.xml:608 #, no-c-format -msgid "The first time we navigate to the JSP page, there will be no value in the <literal>messageList</literal> context variable. The <literal>@Factory</literal> annotation tells Seam to create an instance of <literal>MessageManagerBean</literal> and invoke the <literal>findMessages()</literal> method to initialize the value. We call <literal>findMessages()</literal> a <emphasis>factory method</emphasis> for <literal>messages</literal>." +msgid "" +"The first time we navigate to the JSP page, there will be no value in the " +"<literal>messageList</literal> context variable. The <literal>@Factory</" +"literal> annotation tells Seam to create an instance of " +"<literal>MessageManagerBean</literal> and invoke the <literal>findMessages()" +"</literal> method to initialize the value. We call <literal>findMessages()</" +"literal> a <emphasis>factory method</emphasis> for <literal>messages</" +"literal>." msgstr "" #. Tag: para #: Tutorial.xml:616 #, no-c-format -msgid "The <literal>select()</literal> action listener method marks the selected <literal>Message</literal> as read, and updates it in the database." +msgid "" +"The <literal>select()</literal> action listener method marks the selected " +"<literal>Message</literal> as read, and updates it in the database." msgstr "" #. Tag: para #: Tutorial.xml:620 #, no-c-format -msgid "The <literal>delete()</literal> action listener method removes the selected <literal>Message</literal> from the database." +msgid "" +"The <literal>delete()</literal> action listener method removes the selected " +"<literal>Message</literal> from the database." msgstr "" #. Tag: para #: Tutorial.xml:624 #, no-c-format -msgid "All stateful session bean Seam components <emphasis>must</emphasis> have a method with no parameters marked <literal>@Remove</literal> that Seam uses to remove the stateful bean when the Seam context ends, and clean up any server-side state." +msgid "" +"All stateful session bean Seam components <emphasis>must</emphasis> have a " +"method with no parameters marked <literal>@Remove</literal> that Seam uses " +"to remove the stateful bean when the Seam context ends, and clean up any " +"server-side state." msgstr "" #. Tag: para #: Tutorial.xml:633 #, no-c-format -msgid "Note that this is a session-scoped Seam component. It is associated with the user login session, and all requests from a login session share the same instance of the component. (In Seam applications, we usually use session-scoped components sparingly.)" +msgid "" +"Note that this is a session-scoped Seam component. It is associated with the " +"user login session, and all requests from a login session share the same " +"instance of the component. (In Seam applications, we usually use session-" +"scoped components sparingly.)" msgstr "" #. Tag: title #: Tutorial.xml:640 #, no-c-format -msgid "The session bean local interface: <literal>MessageManager.java</literal>" +msgid "" +"The session bean local interface: <literal>MessageManager.java</literal>" msgstr "" #. Tag: para @@ -1582,7 +1948,12 @@ #. Tag: para #: Tutorial.xml:650 #, no-c-format -msgid "Let's skip over <literal>components.xml</literal>, <literal>persistence.xml</literal>, <literal>web.xml</literal>, <literal>ejb-jar.xml</literal>, <literal>faces-config.xml</literal> and <literal>application.xml</literal> since they are much the same as the previous example, and go straight to the JSP." +msgid "" +"Let's skip over <literal>components.xml</literal>, <literal>persistence.xml</" +"literal>, <literal>web.xml</literal>, <literal>ejb-jar.xml</literal>, " +"<literal>faces-config.xml</literal> and <literal>application.xml</literal> " +"since they are much the same as the previous example, and go straight to the " +"JSP." msgstr "" #. Tag: title @@ -1594,7 +1965,9 @@ #. Tag: para #: Tutorial.xml:660 #, no-c-format -msgid "The JSP page is a straightforward use of the JSF <literal><h:dataTable></literal> component. Again, nothing specific to Seam." +msgid "" +"The JSP page is a straightforward use of the JSF <literal><h:dataTable>" +"</literal> component. Again, nothing specific to Seam." msgstr "" #. Tag: title @@ -1625,24 +1998,28 @@ " <f:facet name=\"header\">\n" " <h:outputText value=\"Read\"/>\n" " </f:facet>\n" -" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/>\n" +" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/" +">\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">\n" " <h:outputText value=\"Title\"/>\n" " </f:facet>\n" -" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager.select}\"/>\n" +" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager." +"select}\"/>\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">\n" " <h:outputText value=\"Date/Time\"/>\n" " </f:facet>\n" " <h:outputText value=\"#{msg.datetime}\">\n" -" <f:convertDateTime type=\"both\" dateStyle=\"medium\" timeStyle=\"short\"/>\n" +" <f:convertDateTime type=\"both\" dateStyle=\"medium\" " +"timeStyle=\"short\"/>\n" " </h:outputText>\n" " </h:column>\n" " <h:column>\n" -" <h:commandButton value=\"Delete\" action=\"#{messageManager.delete}\"/>\n" +" <h:commandButton value=\"Delete\" action=\"#{messageManager." +"delete}\"/>\n" " </h:column>\n" " </h:dataTable>\n" " <h3><h:outputText value=\"#{message.title}\"/></h3>\n" @@ -1670,24 +2047,28 @@ " <f:facet name=\"header\">\n" " <h:outputText value=\"Read\"/>\n" " </f:facet>\n" -" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/>\n" +" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/" +">\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">\n" " <h:outputText value=\"Title\"/>\n" " </f:facet>\n" -" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager.select}\"/>\n" +" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager." +"select}\"/>\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">\n" " <h:outputText value=\"Date/Time\"/>\n" " </f:facet>\n" " <h:outputText value=\"#{msg.datetime}\">\n" -" <f:convertDateTime type=\"both\" dateStyle=\"medium\" timeStyle=\"short\"/>\n" +" <f:convertDateTime type=\"both\" dateStyle=\"medium\" " +"timeStyle=\"short\"/>\n" " </h:outputText>\n" " </h:column>\n" " <h:column>\n" -" <h:commandButton value=\"Delete\" action=\"#{messageManager.delete}\"/>\n" +" <h:commandButton value=\"Delete\" action=\"#{messageManager." +"delete}\"/>\n" " </h:column>\n" " </h:dataTable>\n" " <h3><h:outputText value=\"#{message.title}\"/></h3>\n" @@ -1700,19 +2081,47 @@ #. Tag: para #: Tutorial.xml:675 #, no-c-format -msgid "The first time we navigate to the <literal>messages.jsp</literal> page, the page will try to resolve the <literal>messageList</literal> context variable. Since this context variable is not initialized, Seam will call the factory method <literal>findMessages()</literal>, which performs a query against the database and results in a <literal>DataModel</literal> being outjected. This <literal>DataModel</literal> provides the row data needed for rendering the <literal><h:dataTable></literal>." +msgid "" +"The first time we navigate to the <literal>messages.jsp</literal> page, the " +"page will try to resolve the <literal>messageList</literal> context " +"variable. Since this context variable is not initialized, Seam will call the " +"factory method <literal>findMessages()</literal>, which performs a query " +"against the database and results in a <literal>DataModel</literal> being " +"outjected. This <literal>DataModel</literal> provides the row data needed " +"for rendering the <literal><h:dataTable></literal>." msgstr "" #. Tag: para #: Tutorial.xml:682 #, no-c-format -msgid "When the user clicks the <literal><h:commandLink></literal>, JSF calls the <literal>select()</literal> action listener. Seam intercepts this call and injects the selected row data into the <literal>message</literal> attribute of the <literal>messageManager</literal> component. The action listener fires, marking the selected <literal>Message</literal> as read. At the end of the call, Seam outjects the selected <literal>Message</literal> to the context variable named <literal>message</literal>. Next, the EJB container commits the transaction, and the change to the <literal>Message</literal> is flushed to the database. Finally, the page is re-rendered, redisplaying the message list, and displaying the selected message below it." +msgid "" +"When the user clicks the <literal><h:commandLink></literal>, JSF calls " +"the <literal>select()</literal> action listener. Seam intercepts this call " +"and injects the selected row data into the <literal>message</literal> " +"attribute of the <literal>messageManager</literal> component. The action " +"listener fires, marking the selected <literal>Message</literal> as read. At " +"the end of the call, Seam outjects the selected <literal>Message</literal> " +"to the context variable named <literal>message</literal>. Next, the EJB " +"container commits the transaction, and the change to the <literal>Message</" +"literal> is flushed to the database. Finally, the page is re-rendered, " +"redisplaying the message list, and displaying the selected message below it." msgstr "" #. Tag: para #: Tutorial.xml:691 #, no-c-format -msgid "If the user clicks the <literal><h:commandButton></literal>, JSF calls the <literal>delete()</literal> action listener. Seam intercepts this call and injects the selected row data into the <literal>message</literal> attribute of the <literal>messageList</literal> component. The action listener fires, removing the selected <literal>Message</literal> from the list, and also calling <literal>remove()</literal> on the <literal>EntityManager</literal>. At the end of the call, Seam refreshes the <literal>messageList</literal> context variable and clears the context variable named <literal>message</literal>. The EJB container commits the transaction, and deletes the <literal>Message</literal> from the database. Finally, the page is re-rendered, redisplaying the message list." +msgid "" +"If the user clicks the <literal><h:commandButton></literal>, JSF calls " +"the <literal>delete()</literal> action listener. Seam intercepts this call " +"and injects the selected row data into the <literal>message</literal> " +"attribute of the <literal>messageList</literal> component. The action " +"listener fires, removing the selected <literal>Message</literal> from the " +"list, and also calling <literal>remove()</literal> on the " +"<literal>EntityManager</literal>. At the end of the call, Seam refreshes the " +"<literal>messageList</literal> context variable and clears the context " +"variable named <literal>message</literal>. The EJB container commits the " +"transaction, and deletes the <literal>Message</literal> from the database. " +"Finally, the page is re-rendered, redisplaying the message list." msgstr "" #. Tag: title @@ -1724,13 +2133,21 @@ #. Tag: para #: Tutorial.xml:708 #, no-c-format -msgid "jBPM provides sophisticated functionality for workflow and task management. To get a small taste of how jBPM integrates with Seam, we'll show you a simple \"todo list\" application. Since managing lists of tasks is such core functionality for jBPM, there is hardly any Java code at all in this example." +msgid "" +"jBPM provides sophisticated functionality for workflow and task management. " +"To get a small taste of how jBPM integrates with Seam, we'll show you a " +"simple \"todo list\" application. Since managing lists of tasks is such core " +"functionality for jBPM, there is hardly any Java code at all in this example." msgstr "" #. Tag: para #: Tutorial.xml:723 #, no-c-format -msgid "The center of this example is the jBPM process definition. There are also two JSPs and two trivial JavaBeans (There was no reason to use session beans, since they do not access the database, or have any other transactional behavior). Let's start with the process definition:" +msgid "" +"The center of this example is the jBPM process definition. There are also " +"two JSPs and two trivial JavaBeans (There was no reason to use session " +"beans, since they do not access the database, or have any other " +"transactional behavior). Let's start with the process definition:" msgstr "" #. Tag: title @@ -1780,49 +2197,77 @@ #. Tag: para #: Tutorial.xml:740 #, no-c-format -msgid "The <literal><start-state></literal> node represents the logical start of the process. When the process starts, it immediately transitions to the <literal>todo</literal> node." +msgid "" +"The <literal><start-state></literal> node represents the logical start " +"of the process. When the process starts, it immediately transitions to the " +"<literal>todo</literal> node." msgstr "" #. Tag: para #: Tutorial.xml:745 #, no-c-format -msgid "The <literal><task-node></literal> node represents a <emphasis>wait state</emphasis>, where business process execution pauses, waiting for one or more tasks to be performed." +msgid "" +"The <literal><task-node></literal> node represents a <emphasis>wait " +"state</emphasis>, where business process execution pauses, waiting for one " +"or more tasks to be performed." msgstr "" #. Tag: para #: Tutorial.xml:750 #, no-c-format -msgid "The <literal><task></literal> element defines a task to be performed by a user. Since there is only one task defined on this node, when it is complete, execution resumes, and we transition to the end state. The task gets its description from a Seam component named <literal>todoList</literal> (one of the JavaBeans)." +msgid "" +"The <literal><task></literal> element defines a task to be performed " +"by a user. Since there is only one task defined on this node, when it is " +"complete, execution resumes, and we transition to the end state. The task " +"gets its description from a Seam component named <literal>todoList</literal> " +"(one of the JavaBeans)." msgstr "" #. Tag: para #: Tutorial.xml:756 #, no-c-format -msgid "Tasks need to be assigned to a user or group of users when they are created. In this case, the task is assigned to the current user, which we get from a built-in Seam component named <literal>actor</literal>. Any Seam component may be used to perform task assignment." +msgid "" +"Tasks need to be assigned to a user or group of users when they are created. " +"In this case, the task is assigned to the current user, which we get from a " +"built-in Seam component named <literal>actor</literal>. Any Seam component " +"may be used to perform task assignment." msgstr "" #. Tag: para #: Tutorial.xml:762 #, no-c-format -msgid "The <literal><end-state></literal> node defines the logical end of the business process. When execution reaches this node, the process instance is destroyed." +msgid "" +"The <literal><end-state></literal> node defines the logical end of the " +"business process. When execution reaches this node, the process instance is " +"destroyed." msgstr "" #. Tag: para #: Tutorial.xml:771 #, no-c-format -msgid "If we view this process definition using the process definition editor provided by JBossIDE, this is what it looks like:" +msgid "" +"If we view this process definition using the process definition editor " +"provided by JBossIDE, this is what it looks like:" msgstr "" #. Tag: para #: Tutorial.xml:783 #, no-c-format -msgid "This document defines our <emphasis>business process</emphasis> as a graph of nodes. This is the most trivial possible business process: there is one <emphasis>task</emphasis> to be performed, and when that task is complete, the business process ends." +msgid "" +"This document defines our <emphasis>business process</emphasis> as a graph " +"of nodes. This is the most trivial possible business process: there is one " +"<emphasis>task</emphasis> to be performed, and when that task is complete, " +"the business process ends." msgstr "" #. Tag: para #: Tutorial.xml:787 #, no-c-format -msgid "The first JavaBean handles the login screen <literal>login.jsp</literal>. Its job is just to initialize the jBPM actor id using the <literal>actor</literal> component. In a real application, it would also need to authenticate the user." +msgid "" +"The first JavaBean handles the login screen <literal>login.jsp</literal>. " +"Its job is just to initialize the jBPM actor id using the <literal>actor</" +"literal> component. In a real application, it would also need to " +"authenticate the user." msgstr "" #. Tag: title @@ -1888,7 +2333,9 @@ #. Tag: para #: Tutorial.xml:796 #, no-c-format -msgid "Here we see the use of <literal>@In</literal> to inject the built-in <literal>Actor</literal> component." +msgid "" +"Here we see the use of <literal>@In</literal> to inject the built-in " +"<literal>Actor</literal> component." msgstr "" #. Tag: para @@ -1948,8 +2395,12 @@ #. Tag: para #: Tutorial.xml:807 #, no-c-format -msgid "The second JavaBean is responsible for starting business process instances, and ending tasks." -msgstr "Il secondo JavaBean è responsabile per l'avvio delle istanze del processo di business e della fine dei task." +msgid "" +"The second JavaBean is responsible for starting business process instances, " +"and ending tasks." +msgstr "" +"Il secondo JavaBean è responsabile per l'avvio delle istanze del processo di " +"business e della fine dei task." #. Tag: title #: Tutorial.xml:811 @@ -2010,25 +2461,36 @@ #. Tag: para #: Tutorial.xml:821 #, no-c-format -msgid "The description property accepts user input form the JSP page, and exposes it to the process definition, allowing the task description to be set." +msgid "" +"The description property accepts user input form the JSP page, and exposes " +"it to the process definition, allowing the task description to be set." msgstr "" #. Tag: para #: Tutorial.xml:825 #, no-c-format -msgid "The Seam <literal>@CreateProcess</literal> annotation creates a new jBPM process instance for the named process definition." +msgid "" +"The Seam <literal>@CreateProcess</literal> annotation creates a new jBPM " +"process instance for the named process definition." msgstr "" #. Tag: para #: Tutorial.xml:829 #, no-c-format -msgid "The Seam <literal>@StartTask</literal> annotation starts work on a task. The <literal>@EndTask</literal> ends the task, and allows the business process execution to resume." +msgid "" +"The Seam <literal>@StartTask</literal> annotation starts work on a task. The " +"<literal>@EndTask</literal> ends the task, and allows the business process " +"execution to resume." msgstr "" #. Tag: para #: Tutorial.xml:838 #, no-c-format -msgid "In a more realistic example, <literal>@StartTask</literal> and <literal>@EndTask</literal> would not appear on the same method, because there is usually work to be done using the application in order to complete the task." +msgid "" +"In a more realistic example, <literal>@StartTask</literal> and " +"<literal>@EndTask</literal> would not appear on the same method, because " +"there is usually work to be done using the application in order to complete " +"the task." msgstr "" #. Tag: para @@ -2038,8 +2500,7 @@ msgstr "" #. Tag: title -#: Tutorial.xml:844 -#: Tutorial.xml:854 +#: Tutorial.xml:844 Tutorial.xml:854 #, no-c-format msgid "todo.jsp" msgstr "todo.jsp" @@ -2074,7 +2535,8 @@ " <f:facet name=\"header\">\n" " <h:outputText value=\"Created\"/>\n" " </f:facet>\n" -" <h:outputText value=\"#{task.taskMgmtInstance.processInstance.start}\">\n" +" <h:outputText value=\"#{task.taskMgmtInstance." +"processInstance.start}\">\n" " <f:convertDateTime type=\"date\"/>\n" " </h:outputText>\n" " </h:column>\n" @@ -2082,18 +2544,21 @@ " <f:facet name=\"header\">\n" " <h:outputText value=\"Priority\"/>\n" " </f:facet>\n" -" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/>\n" +" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/" +">\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">\n" " <h:outputText value=\"Due Date\"/>\n" " </f:facet>\n" -" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100\">\n" +" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100" +"\">\n" " <f:convertDateTime type=\"date\" dateStyle=\"short\"/>\n" " </h:inputText>\n" " </h:column>\n" " <h:column>\n" -" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n" +" <s:button value=\"Done\" action=\"#{todoList.done}\" " +"taskInstance=\"#{task}\"/>\n" " </h:column>\n" " </h:dataTable>\n" " </div>\n" @@ -2107,7 +2572,8 @@ " <h:form id=\"new\">\n" " <div>\n" " <h:inputText value=\"#{todoList.description}\"/>\n" -" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n" +" <h:commandButton value=\"Create New Item\" action=\"#{todoList." +"createTodo}\"/>\n" " </div>\n" " </h:form>\n" "</f:view>\n" @@ -2140,7 +2606,8 @@ " <f:facet name=\"header\">\n" " <h:outputText value=\"Created\"/>\n" " </f:facet>\n" -" <h:outputText value=\"#{task.taskMgmtInstance.processInstance.start}\">\n" +" <h:outputText value=\"#{task.taskMgmtInstance." +"processInstance.start}\">\n" " <f:convertDateTime type=\"date\"/>\n" " </h:outputText>\n" " </h:column>\n" @@ -2148,18 +2615,21 @@ " <f:facet name=\"header\">\n" " <h:outputText value=\"Priority\"/>\n" " </f:facet>\n" -" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/>\n" +" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/" +">\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">\n" " <h:outputText value=\"Due Date\"/>\n" " </f:facet>\n" -" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100\">\n" +" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100" +"\">\n" " <f:convertDateTime type=\"date\" dateStyle=\"short\"/>\n" " </h:inputText>\n" " </h:column>\n" " <h:column>\n" -" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n" +" <s:button value=\"Done\" action=\"#{todoList.done}\" " +"taskInstance=\"#{task}\"/>\n" " </h:column>\n" " </h:dataTable>\n" " </div>\n" @@ -2173,7 +2643,8 @@ " <h:form id=\"new\">\n" " <div>\n" " <h:inputText value=\"#{todoList.description}\"/>\n" -" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n" +" <h:commandButton value=\"Create New Item\" action=\"#{todoList." +"createTodo}\"/>\n" " </div>\n" " </h:form>\n" "</f:view>\n" @@ -2189,7 +2660,10 @@ #. Tag: para #: Tutorial.xml:851 #, no-c-format -msgid "The page renders a list of tasks, which it gets from a built-in Seam component named <literal>taskInstanceList</literal>. The list is defined inside a JSF form." +msgid "" +"The page renders a list of tasks, which it gets from a built-in Seam " +"component named <literal>taskInstanceList</literal>. The list is defined " +"inside a JSF form." msgstr "" #. Tag: programlisting @@ -2198,7 +2672,8 @@ msgid "" "<![CDATA[<h:form id=\"list\">\n" " <div>\n" -" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty taskInstanceList}\"/>\n" +" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty " +"taskInstanceList}\"/>\n" " <h:dataTable value=\"#{taskInstanceList}\" var=\"task\" \n" " rendered=\"#{not empty taskInstanceList}\">\n" " ...\n" @@ -2208,7 +2683,8 @@ msgstr "" "<![CDATA[<h:form id=\"list\">\n" " <div>\n" -" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty taskInstanceList}\"/>\n" +" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty " +"taskInstanceList}\"/>\n" " <h:dataTable value=\"#{taskInstanceList}\" var=\"task\" \n" " rendered=\"#{not empty taskInstanceList}\">\n" " ...\n" @@ -2219,7 +2695,12 @@ #. Tag: para #: Tutorial.xml:858 #, no-c-format -msgid "Each element of the list is an instance of the jBPM class <literal>TaskInstance</literal>. The following code simply displays the interesting properties of each task in the list. For the description, priority and due date, we use input controls, to allow the user to update these values." +msgid "" +"Each element of the list is an instance of the jBPM class " +"<literal>TaskInstance</literal>. The following code simply displays the " +"interesting properties of each task in the list. For the description, " +"priority and due date, we use input controls, to allow the user to update " +"these values." msgstr "" #. Tag: programlisting @@ -2287,7 +2768,10 @@ #. Tag: para #: Tutorial.xml:865 #, no-c-format -msgid "This button ends the task by calling the action method annotated <literal>@StartTask @EndTask</literal>. It passes the task id to Seam as a request parameter:" +msgid "" +"This button ends the task by calling the action method annotated " +"<literal>@StartTask @EndTask</literal>. It passes the task id to Seam as a " +"request parameter:" msgstr "" #. Tag: programlisting @@ -2295,29 +2779,39 @@ #, no-c-format msgid "" "<![CDATA[<h:column>\n" -" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n" +" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#" +"{task}\"/>\n" "</h:column>]]>" msgstr "" "<![CDATA[<h:column>\n" -" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n" +" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#" +"{task}\"/>\n" "</h:column>]]>" #. Tag: para #: Tutorial.xml:870 #, no-c-format -msgid "Note that this is using a Seam <literal><s:button></literal> JSF control from the <literal>seam-ui.jar</literal> package. This button is used to update the properties of the tasks. When the form is submitted, Seam and jBPM will make any changes to the tasks persistent. There is no need for any action listener method:" +msgid "" +"Note that this is using a Seam <literal><s:button></literal> JSF " +"control from the <literal>seam-ui.jar</literal> package. This button is used " +"to update the properties of the tasks. When the form is submitted, Seam and " +"jBPM will make any changes to the tasks persistent. There is no need for any " +"action listener method:" msgstr "" #. Tag: programlisting #: Tutorial.xml:875 #, no-c-format msgid "<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>" -msgstr "<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>" +msgstr "" +"<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>" #. Tag: para #: Tutorial.xml:877 #, no-c-format -msgid "A second form on the page is used to create new items, by calling the action method annotated <literal>@CreateProcess</literal>." +msgid "" +"A second form on the page is used to create new items, by calling the action " +"method annotated <literal>@CreateProcess</literal>." msgstr "" #. Tag: programlisting @@ -2327,45 +2821,79 @@ "<![CDATA[<h:form id=\"new\">\n" " <div>\n" " <h:inputText value=\"#{todoList.description}\"/>\n" -" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n" +" <h:commandButton value=\"Create New Item\" action=\"#{todoList." +"createTodo}\"/>\n" " </div>\n" "</h:form>]]>" msgstr "" "<![CDATA[<h:form id=\"new\">\n" " <div>\n" " <h:inputText value=\"#{todoList.description}\"/>\n" -" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n" +" <h:commandButton value=\"Create New Item\" action=\"#{todoList." +"createTodo}\"/>\n" " </div>\n" "</h:form>]]>" #. Tag: para #: Tutorial.xml:888 #, no-c-format -msgid "After logging in, todo.jsp uses the <literal>taskInstanceList</literal> component to display a table of outstanding todo items for a the current user. Initially there are none. It also presents a form to enter a new entry. When the user types the todo item and hits the \"Create New Item\" button, <literal>#{todoList.createTodo}</literal> is called. This starts the todo process, as defined in <literal>todo.jpdl.xml</literal>." +msgid "" +"After logging in, todo.jsp uses the <literal>taskInstanceList</literal> " +"component to display a table of outstanding todo items for a the current " +"user. Initially there are none. It also presents a form to enter a new " +"entry. When the user types the todo item and hits the \"Create New Item\" " +"button, <literal>#{todoList.createTodo}</literal> is called. This starts the " +"todo process, as defined in <literal>todo.jpdl.xml</literal>." msgstr "" #. Tag: para #: Tutorial.xml:894 #, no-c-format -msgid "The process instance is created, starting in the start state and immediately transition to the <literal>todo</literal> state, where a new task is created. The task description is set based on the user's input, which was saved to <literal>#{todoList.description}</literal>. Then, the task is assigned to the current user, which was stored in the seam actor component. Note that in this example, the process has no extra process state. All the state in this example is stored in the task definition. The process and task information is stored in the database at the end of the request." +msgid "" +"The process instance is created, starting in the start state and immediately " +"transition to the <literal>todo</literal> state, where a new task is " +"created. The task description is set based on the user's input, which was " +"saved to <literal>#{todoList.description}</literal>. Then, the task is " +"assigned to the current user, which was stored in the seam actor component. " +"Note that in this example, the process has no extra process state. All the " +"state in this example is stored in the task definition. The process and task " +"information is stored in the database at the end of the request." msgstr "" #. Tag: para #: Tutorial.xml:905 #, no-c-format -msgid "When <literal>todo.jsp</literal> is redisplayed, <literal>taskInstanceList</literal> now finds the task that was just created. The task is shown in an <literal>h:dataTable</literal>. The internal state of the task is displayed in each column: <literal>#{task.description}</literal>, <literal>#{task.priority}</literal>, <literal>#{task.dueDate}</literal>, etc... These fields can all be edited and saved back to the database." +msgid "" +"When <literal>todo.jsp</literal> is redisplayed, <literal>taskInstanceList</" +"literal> now finds the task that was just created. The task is shown in an " +"<literal>h:dataTable</literal>. The internal state of the task is displayed " +"in each column: <literal>#{task.description}</literal>, <literal>#{task." +"priority}</literal>, <literal>#{task.dueDate}</literal>, etc... These fields " +"can all be edited and saved back to the database." msgstr "" #. Tag: para #: Tutorial.xml:915 #, no-c-format -msgid "Each todo item also has \"Done\" button, which calls <literal>#{todoList.done}</literal>. The <literal>todoList</literal> component knows which task the button is for because each s:button specificies <literal>taskInstance=\"#{task}\"</literal>, referring to the task for that particular line of of the table. The <literal>@StartTast</literal> and <literal>@EndTask</literal> annotations cause seam to make the task active and immediately complete the task. The original process then transitions into the <literal>done</literal> state, according to the process definition, where it ends. The state of the task and process are both updated in the database." +msgid "" +"Each todo item also has \"Done\" button, which calls <literal>#{todoList." +"done}</literal>. The <literal>todoList</literal> component knows which task " +"the button is for because each s:button specificies <literal>taskInstance=\"#" +"{task}\"</literal>, referring to the task for that particular line of of the " +"table. The <literal>@StartTast</literal> and <literal>@EndTask</literal> " +"annotations cause seam to make the task active and immediately complete the " +"task. The original process then transitions into the <literal>done</literal> " +"state, according to the process definition, where it ends. The state of the " +"task and process are both updated in the database." msgstr "" #. Tag: para #: Tutorial.xml:926 #, no-c-format -msgid "When <literal>todo.jsp</literal> is displayed again, the now-completed task is no longer displayed in the <literal>taskInstanceList</literal>, since that component only display active tasks for the user." +msgid "" +"When <literal>todo.jsp</literal> is displayed again, the now-completed task " +"is no longer displayed in the <literal>taskInstanceList</literal>, since " +"that component only display active tasks for the user." msgstr "" #. Tag: title @@ -2377,19 +2905,30 @@ #. Tag: para #: Tutorial.xml:936 #, no-c-format -msgid "For Seam applications with relatively freeform (ad hoc) navigation, JSF/Seam navigation rules are a perfectly good way to define the page flow. For applications with a more constrained style of navigation, especially for user interfaces which are more stateful, navigation rules make it difficult to really understand the flow of the system. To understand the flow, you need to piece it together from the view pages, the actions and the navigation rules." +msgid "" +"For Seam applications with relatively freeform (ad hoc) navigation, JSF/Seam " +"navigation rules are a perfectly good way to define the page flow. For " +"applications with a more constrained style of navigation, especially for " +"user interfaces which are more stateful, navigation rules make it difficult " +"to really understand the flow of the system. To understand the flow, you " +"need to piece it together from the view pages, the actions and the " +"navigation rules." msgstr "" #. Tag: para #: Tutorial.xml:942 #, no-c-format -msgid "Seam allows you to use a jPDL process definition to define pageflow. The simple number guessing example shows how this is done." +msgid "" +"Seam allows you to use a jPDL process definition to define pageflow. The " +"simple number guessing example shows how this is done." msgstr "" #. Tag: para #: Tutorial.xml:956 #, no-c-format -msgid "The example is implemented using one JavaBean, three JSP pages and a jPDL pageflow definition. Let's begin with the pageflow:" +msgid "" +"The example is implemented using one JavaBean, three JSP pages and a jPDL " +"pageflow definition. Let's begin with the pageflow:" msgstr "" #. Tag: title @@ -2406,7 +2945,8 @@ " xmlns=\"http://jboss.com/products/seam/pageflow\"\n" " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" " xsi:schemaLocation=\"http://jboss.com/products/seam/pageflow \n" -" http://jboss.com/products/seam/pageflow-2.1.xsd\"\n" +" http://jboss.com/products/seam/pageflow-2.1.xsd" +"\"\n" " name=\"numberGuess\">\n" " \n" " <start-page name=\"displayGuess\" view-id=\"/numberGuess.jspx\">\n" @@ -2418,12 +2958,14 @@ " <transition name=\"cheat\" to=\"cheat\"/>\n" " </start-page>\n" " \n" -" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n" +" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}" +"\">\n" " <transition name=\"true\" to=\"win\"/>\n" " <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n" " </decision>\n" " \n" -" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess.lastGuess}\">\n" +" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess." +"lastGuess}\">\n" " <transition name=\"true\" to=\"lose\"/>\n" " <transition name=\"false\" to=\"displayGuess\"/>\n" " </decision>\n" @@ -2460,13 +3002,15 @@ " version=\"2.0\">\n" " <jsp:output doctype-root-element=\"html\" \n" " doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n" -" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n" +" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-" +"transitional.dtd\"/>\n" " <jsp:directive.page contentType=\"text/html\"/>\n" " <html>\n" " <head>\n" " <title>Guess a number...</title>\n" " <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n" -" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms.js\" />\n" +" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms." +"js\" />\n" " </head>\n" " <body>\n" " <h1>Guess a number...</h1>\n" @@ -2476,9 +3020,11 @@ " <div>\n" " <h:messages globalOnly=\"true\"/>\n" " <h:outputText value=\"Higher!\" \n" -" rendered=\"#{numberGuess.randomNumber gt numberGuess.currentGuess}\"/>\n" +" rendered=\"#{numberGuess.randomNumber gt numberGuess." +"currentGuess}\"/>\n" " <h:outputText value=\"Lower!\" \n" -" rendered=\"#{numberGuess.randomNumber lt numberGuess.currentGuess}\"/>\n" +" rendered=\"#{numberGuess.randomNumber lt numberGuess." +"currentGuess}\"/>\n" " </div>\n" " \n" " <div>\n" @@ -2490,22 +3036,30 @@ " \n" " <div>\n" " Your guess: \n" -" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess\" \n" +" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess" +"\" \n" " required=\"true\" size=\"3\" \n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) gt 20}\">\n" +" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) " +"gt 20}\">\n" " <f:validateLongRange maximum=\"#{numberGuess.biggest}\" \n" " minimum=\"#{numberGuess.smallest}\"/>\n" " </h:inputText>\n" " <h:selectOneMenu value=\"#{numberGuess.currentGuess}\" \n" " id=\"selectGuessMenu\" required=\"true\"\n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 20 and \n" -" (numberGuess.biggest-numberGuess.smallest) gt 4}\">\n" -" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n" +" rendered=\"#{(numberGuess.biggest-numberGuess." +"smallest) le 20 and \n" +" (numberGuess.biggest-numberGuess." +"smallest) gt 4}\">\n" +" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" " +"label=\"#{i}\"/>\n" " </h:selectOneMenu>\n" -" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=\"selectGuessRadio\" \n" +" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=" +"\"selectGuessRadio\" \n" " required=\"true\"\n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 4}\">\n" -" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n" +" rendered=\"#{(numberGuess.biggest-numberGuess." +"smallest) le 4}\">\n" +" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" " +"label=\"#{i}\"/>\n" " </h:selectOneRadio>\n" " <h:commandButton value=\"Guess\" action=\"guess\"/>\n" " <s:button value=\"Cheat\" view=\"/confirm.jspx\"/>\n" @@ -2525,43 +3079,64 @@ #. Tag: para #: Tutorial.xml:971 #, no-c-format -msgid "The <literal><page></literal> element defines a wait state where the system displays a particular JSF view and waits for user input. The <literal>view-id</literal> is the same JSF view id used in plain JSF navigation rules. The <literal>redirect</literal> attribute tells Seam to use post-then-redirect when navigating to the page. (This results in friendly browser URLs.)" +msgid "" +"The <literal><page></literal> element defines a wait state where the " +"system displays a particular JSF view and waits for user input. The " +"<literal>view-id</literal> is the same JSF view id used in plain JSF " +"navigation rules. The <literal>redirect</literal> attribute tells Seam to " +"use post-then-redirect when navigating to the page. (This results in " +"friendly browser URLs.)" msgstr "" #. Tag: para #: Tutorial.xml:978 #, no-c-format -msgid "The <literal><transition></literal> element names a JSF outcome. The transition is triggered when a JSF action results in that outcome. Execution will then proceed to the next node of the pageflow graph, after invocation of any jBPM transition actions." +msgid "" +"The <literal><transition></literal> element names a JSF outcome. The " +"transition is triggered when a JSF action results in that outcome. Execution " +"will then proceed to the next node of the pageflow graph, after invocation " +"of any jBPM transition actions." msgstr "" #. Tag: para #: Tutorial.xml:984 #, no-c-format -msgid "A transition <literal><action></literal> is just like a JSF action, except that it occurs when a jBPM transition occurs. The transition action can invoke any Seam component." +msgid "" +"A transition <literal><action></literal> is just like a JSF action, " +"except that it occurs when a jBPM transition occurs. The transition action " +"can invoke any Seam component." msgstr "" #. Tag: para #: Tutorial.xml:989 #, no-c-format -msgid "A <literal><decision></literal> node branches the pageflow, and determines the next node to execute by evaluating a JSF EL expression." +msgid "" +"A <literal><decision></literal> node branches the pageflow, and " +"determines the next node to execute by evaluating a JSF EL expression." msgstr "" #. Tag: para #: Tutorial.xml:997 #, no-c-format -msgid "Here is what the pageflow looks like in the JBoss Developer Studio pageflow editor:" +msgid "" +"Here is what the pageflow looks like in the JBoss Developer Studio pageflow " +"editor:" msgstr "" #. Tag: para #: Tutorial.xml:1008 #, no-c-format -msgid "Now that we have seen the pageflow, it is very, very easy to understand the rest of the application!" +msgid "" +"Now that we have seen the pageflow, it is very, very easy to understand the " +"rest of the application!" msgstr "" #. Tag: para #: Tutorial.xml:1010 #, no-c-format -msgid "Here is the main page of the application, <literal>numberGuess.jspx</literal>:" +msgid "" +"Here is the main page of the application, <literal>numberGuess.jspx</" +"literal>:" msgstr "" #. Tag: title @@ -2583,13 +3158,15 @@ " version=\"2.0\">\n" " <jsp:output doctype-root-element=\"html\" \n" " doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n" -" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n" +" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-" +"transitional.dtd\"/>\n" " <jsp:directive.page contentType=\"text/html\"/>\n" " <html>\n" " <head>\n" " <title>Guess a number...</title>\n" " <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n" -" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms.js\" />\n" +" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms." +"js\" />\n" " </head>\n" " <body>\n" " <h1>Guess a number...</h1>\n" @@ -2599,9 +3176,11 @@ " <div>\n" " <h:messages globalOnly=\"true\"/>\n" " <h:outputText value=\"Higher!\" \n" -" rendered=\"#{numberGuess.randomNumber gt numberGuess.currentGuess}\"/>\n" +" rendered=\"#{numberGuess.randomNumber gt numberGuess." +"currentGuess}\"/>\n" " <h:outputText value=\"Lower!\" \n" -" rendered=\"#{numberGuess.randomNumber lt numberGuess.currentGuess}\"/>\n" +" rendered=\"#{numberGuess.randomNumber lt numberGuess." +"currentGuess}\"/>\n" " </div>\n" " \n" " <div>\n" @@ -2613,22 +3192,30 @@ " \n" " <div>\n" " Your guess: \n" -" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess\" \n" +" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess" +"\" \n" " required=\"true\" size=\"3\" \n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) gt 20}\">\n" +" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) " +"gt 20}\">\n" " <f:validateLongRange maximum=\"#{numberGuess.biggest}\" \n" " minimum=\"#{numberGuess.smallest}\"/>\n" " </h:inputText>\n" " <h:selectOneMenu value=\"#{numberGuess.currentGuess}\" \n" " id=\"selectGuessMenu\" required=\"true\"\n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 20 and \n" -" (numberGuess.biggest-numberGuess.smallest) gt 4}\">\n" -" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n" +" rendered=\"#{(numberGuess.biggest-numberGuess." +"smallest) le 20 and \n" +" (numberGuess.biggest-numberGuess." +"smallest) gt 4}\">\n" +" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" " +"label=\"#{i}\"/>\n" " </h:selectOneMenu>\n" -" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=\"selectGuessRadio\" \n" +" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=" +"\"selectGuessRadio\" \n" " required=\"true\"\n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 4}\">\n" -" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n" +" rendered=\"#{(numberGuess.biggest-numberGuess." +"smallest) le 4}\">\n" +" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" " +"label=\"#{i}\"/>\n" " </h:selectOneRadio>\n" " <h:commandButton value=\"Guess\" action=\"guess\"/>\n" " <s:button value=\"Cheat\" view=\"/confirm.jspx\"/>\n" @@ -2654,13 +3241,15 @@ " version=\"2.0\">\n" " <jsp:output doctype-root-element=\"html\" \n" " doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n" -" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n" +" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-" +"transitional.dtd\"/>\n" " <jsp:directive.page contentType=\"text/html\"/>\n" " <html>\n" " <head>\n" " <title>Guess a number...</title>\n" " <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n" -" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms.js\" />\n" +" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms." +"js\" />\n" " </head>\n" " <body>\n" " <h1>Guess a number...</h1>\n" @@ -2670,9 +3259,11 @@ " <div>\n" " <h:messages globalOnly=\"true\"/>\n" " <h:outputText value=\"Higher!\" \n" -" rendered=\"#{numberGuess.randomNumber gt numberGuess.currentGuess}\"/>\n" +" rendered=\"#{numberGuess.randomNumber gt numberGuess." +"currentGuess}\"/>\n" " <h:outputText value=\"Lower!\" \n" -" rendered=\"#{numberGuess.randomNumber lt numberGuess.currentGuess}\"/>\n" +" rendered=\"#{numberGuess.randomNumber lt numberGuess." +"currentGuess}\"/>\n" " </div>\n" " \n" " <div>\n" @@ -2684,22 +3275,30 @@ " \n" " <div>\n" " Your guess: \n" -" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess\" \n" +" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess" +"\" \n" " required=\"true\" size=\"3\" \n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) gt 20}\">\n" +" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) " +"gt 20}\">\n" " <f:validateLongRange maximum=\"#{numberGuess.biggest}\" \n" " minimum=\"#{numberGuess.smallest}\"/>\n" " </h:inputText>\n" " <h:selectOneMenu value=\"#{numberGuess.currentGuess}\" \n" " id=\"selectGuessMenu\" required=\"true\"\n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 20 and \n" -" (numberGuess.biggest-numberGuess.smallest) gt 4}\">\n" -" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n" +" rendered=\"#{(numberGuess.biggest-numberGuess." +"smallest) le 20 and \n" +" (numberGuess.biggest-numberGuess." +"smallest) gt 4}\">\n" +" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" " +"label=\"#{i}\"/>\n" " </h:selectOneMenu>\n" -" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=\"selectGuessRadio\" \n" +" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=" +"\"selectGuessRadio\" \n" " required=\"true\"\n" -" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 4}\">\n" -" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n" +" rendered=\"#{(numberGuess.biggest-numberGuess." +"smallest) le 4}\">\n" +" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" " +"label=\"#{i}\"/>\n" " </h:selectOneRadio>\n" " <h:commandButton value=\"Guess\" action=\"guess\"/>\n" " <s:button value=\"Cheat\" view=\"/confirm.jspx\"/>\n" @@ -2719,7 +3318,9 @@ #. Tag: para #: Tutorial.xml:1018 #, no-c-format -msgid "Notice how the command button names the <literal>guess</literal> transition instead of calling an action directly." +msgid "" +"Notice how the command button names the <literal>guess</literal> transition " +"instead of calling an action directly." msgstr "" #. Tag: para @@ -2745,7 +3346,8 @@ " version=\"2.0\">\n" " <jsp:output doctype-root-element=\"html\"\n" " doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n" -" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n" +" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-" +"transitional.dtd\"/>\n" " <jsp:directive.page contentType=\"text/html\"/>\n" " <html>\n" " <head>\n" @@ -2755,8 +3357,10 @@ " <body>\n" " <h1>You won!</h1>\n" " <f:view>\n" -" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}\" />.\n" -" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> guesses.\n" +" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}" +"\" />.\n" +" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> " +"guesses.\n" " <h:outputText value=\"But you cheated, so it doesn't count!\" \n" " rendered=\"#{numberGuess.cheat}\"/>\n" " Would you like to <a href=\"numberGuess.seam\">play again</a>?\n" @@ -2773,7 +3377,8 @@ " version=\"2.0\">\n" " <jsp:output doctype-root-element=\"html\"\n" " doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n" -" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n" +" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-" +"transitional.dtd\"/>\n" " <jsp:directive.page contentType=\"text/html\"/>\n" " <html>\n" " <head>\n" @@ -2783,8 +3388,10 @@ " <body>\n" " <h1>You won!</h1>\n" " <f:view>\n" -" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}\" />.\n" -" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> guesses.\n" +" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}" +"\" />.\n" +" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> " +"guesses.\n" " <h:outputText value=\"But you cheated, so it doesn't count!\" \n" " rendered=\"#{numberGuess.cheat}\"/>\n" " Would you like to <a href=\"numberGuess.seam\">play again</a>?\n" @@ -2797,7 +3404,9 @@ #. Tag: para #: Tutorial.xml:1028 #, no-c-format -msgid "The <literal>lose.jspx</literal> looks roughly the same, so we'll skip over it." +msgid "" +"The <literal>lose.jspx</literal> looks roughly the same, so we'll skip over " +"it." msgstr "" #. Tag: para @@ -3027,13 +3636,19 @@ #. Tag: para #: Tutorial.xml:1041 #, no-c-format -msgid "The first time a JSP page asks for a <literal>numberGuess</literal> component, Seam will create a new one for it, and the <literal>@Create</literal> method will be invoked, allowing the component to initialize itself." +msgid "" +"The first time a JSP page asks for a <literal>numberGuess</literal> " +"component, Seam will create a new one for it, and the <literal>@Create</" +"literal> method will be invoked, allowing the component to initialize itself." msgstr "" #. Tag: para #: Tutorial.xml:1051 #, no-c-format -msgid "The <literal>pages.xml</literal> file starts a Seam <emphasis>conversation</emphasis> (much more about that later), and specifies the pageflow definition to use for the conversation's page flow." +msgid "" +"The <literal>pages.xml</literal> file starts a Seam <emphasis>conversation</" +"emphasis> (much more about that later), and specifies the pageflow " +"definition to use for the conversation's page flow." msgstr "" #. Tag: title @@ -3049,7 +3664,8 @@ "<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" "<pages xmlns=\"http://jboss.com/products/seam/pages\"\n" " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" -" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.1.xsd\">\n" +" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://" +"jboss.com/products/seam/pages-2.1.xsd\">\n" "\n" " <page view-id=\"/numberGuess.jspx\">\n" " <begin-conversation join=\"true\" pageflow=\"numberGuess\"/>\n" @@ -3061,7 +3677,8 @@ "<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n" "<pages xmlns=\"http://jboss.com/products/seam/pages\"\n" " xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" -" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.1.xsd\">\n" +" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://" +"jboss.com/products/seam/pages-2.1.xsd\">\n" "\n" " <page view-id=\"/numberGuess.jspx\">\n" " <begin-conversation join=\"true\" pageflow=\"numberGuess\"/>\n" @@ -3073,43 +3690,89 @@ #. Tag: para #: Tutorial.xml:1064 #, no-c-format -msgid "As you can see, this Seam component is pure business logic! It doesn't need to know anything at all about the user interaction flow. This makes the component potentially more reuseable." +msgid "" +"As you can see, this Seam component is pure business logic! It doesn't need " +"to know anything at all about the user interaction flow. This makes the " +"component potentially more reuseable." msgstr "" #. Tag: para #: Tutorial.xml:1071 #, no-c-format -msgid "We'll step through basic flow of the application. The game starts with the <literal>numberGuess.jspx</literal> view. When the page is first displayed, the <literal>pages.xml</literal> configuration causes conversation to begin and associates the <literal>numberGuess</literal> pageflow with that conversation. The pageflow starts with a <literal>start-page</literal> tag, which is a wait state, so the <literal>numberGuess.xhtml</literal> is rendered." +msgid "" +"We'll step through basic flow of the application. The game starts with the " +"<literal>numberGuess.jspx</literal> view. When the page is first displayed, " +"the <literal>pages.xml</literal> configuration causes conversation to begin " +"and associates the <literal>numberGuess</literal> pageflow with that " +"conversation. The pageflow starts with a <literal>start-page</literal> tag, " +"which is a wait state, so the <literal>numberGuess.xhtml</literal> is " +"rendered." msgstr "" #. Tag: para #: Tutorial.xml:1079 #, no-c-format -msgid "The view references the <literal>numberGuess</literal> component, causing a new instance to be created and stored in the conversation. The <literal>@Create</literal> method is called, initializing the state of the game. The view displays an <literal>h:form</literal> that allows the user to edit <literal>#{numberGuess.currentGuess}</literal>." +msgid "" +"The view references the <literal>numberGuess</literal> component, causing a " +"new instance to be created and stored in the conversation. The " +"<literal>@Create</literal> method is called, initializing the state of the " +"game. The view displays an <literal>h:form</literal> that allows the user to " +"edit <literal>#{numberGuess.currentGuess}</literal>." msgstr "" #. Tag: para #: Tutorial.xml:1085 #, no-c-format -msgid "The \"Guess\" button triggers the <literal>guess</literal> action. Seam defers to the pageflow to handle the action, which says that the pageflow should transition to the <literal>evaluateGuess</literal> state, first invoking <literal>#{numberGuess.guess}</literal>, which updates the guess count and highest/lowest suggestions in the <literal>numberGuess</literal> component." +msgid "" +"The \"Guess\" button triggers the <literal>guess</literal> action. Seam " +"defers to the pageflow to handle the action, which says that the pageflow " +"should transition to the <literal>evaluateGuess</literal> state, first " +"invoking <literal>#{numberGuess.guess}</literal>, which updates the guess " +"count and highest/lowest suggestions in the <literal>numberGuess</literal> " +"component." msgstr "" #. Tag: para #: Tutorial.xml:1091 #, no-c-format -msgid "The <literal>evaluateGuess</literal> state checks the value of <literal>#{numberGuess.correctGuess}</literal> and transitions either to the <literal>win</literal> or <literal>evaluatingRemainingGuesses</literal> state. We'll assume the number was incorrect, in which case the pageflow transitions to <literal>evaluatingRemainingGuesses</literal>. That is also a decision state, which tests the <literal>#{numberGuess.lastGuess}</literal> state to determine whether or not the user has more guesses. If there are more guesses (<literal>lastGuess</literal> is <literal>false</literal>), we transition back to the original <literal>displayGuess</literal> state. Finally we've reached a page state, so the associated page <literal>/numberGuess.jspx</literal> is displayed. Since the page has a redirect element, Seam sends a redirect to the the user's browser, starting the process over." +msgid "" +"The <literal>evaluateGuess</literal> state checks the value of <literal>#" +"{numberGuess.correctGuess}</literal> and transitions either to the " +"<literal>win</literal> or <literal>evaluatingRemainingGuesses</literal> " +"state. We'll assume the number was incorrect, in which case the pageflow " +"transitions to <literal>evaluatingRemainingGuesses</literal>. That is also a " +"decision state, which tests the <literal>#{numberGuess.lastGuess}</literal> " +"state to determine whether or not the user has more guesses. If there are " +"more guesses (<literal>lastGuess</literal> is <literal>false</literal>), we " +"transition back to the original <literal>displayGuess</literal> state. " +"Finally we've reached a page state, so the associated page <literal>/" +"numberGuess.jspx</literal> is displayed. Since the page has a redirect " +"element, Seam sends a redirect to the the user's browser, starting the " +"process over." msgstr "" #. Tag: para #: Tutorial.xml:1103 #, no-c-format -msgid "We won't follow the state any more except to note that if on a future request either the <literal>win</literal> or the <literal>lose</literal> transition were taken, the user would be taken to either the <literal>/win.jspx</literal> or <literal>/lose.jspx</literal>. Both states specify that Seam should end the conversation, tossing away all the game state and pageflow state, before redirecting the user to the final page." +msgid "" +"We won't follow the state any more except to note that if on a future " +"request either the <literal>win</literal> or the <literal>lose</literal> " +"transition were taken, the user would be taken to either the <literal>/win." +"jspx</literal> or <literal>/lose.jspx</literal>. Both states specify that " +"Seam should end the conversation, tossing away all the game state and " +"pageflow state, before redirecting the user to the final page." msgstr "" #. Tag: para #: Tutorial.xml:1113 #, no-c-format -msgid "The numberguess example also contains Giveup and Cheat buttons. You should be able to trace the pageflow state for both actions relatively easily. Pay particular attention to the <literal>cheat</literal> transtition, which loads a sub-process to handle that flow. Although it's overkill for this application, it does demonstrate how complex pageflows can be broken down into smaller parts to make them easier to understand." +msgid "" +"The numberguess example also contains Giveup and Cheat buttons. You should " +"be able to trace the pageflow state for both actions relatively easily. Pay " +"particular attention to the <literal>cheat</literal> transtition, which " +"loads a sub-process to handle that flow. Although it's overkill for this " +"application, it does demonstrate how complex pageflows can be broken down " +"into smaller parts to make them easier to understand." msgstr "" #. Tag: title @@ -3119,8 +3782,7 @@ msgstr "" #. Tag: title -#: Tutorial.xml:1128 -#: Tutorial.xml:1506 +#: Tutorial.xml:1128 Tutorial.xml:1506 #, no-c-format msgid "Introduction" msgstr "Introduzione" @@ -3128,7 +3790,9 @@ #. Tag: para #: Tutorial.xml:1130 #, no-c-format -msgid "The booking application is a complete hotel room reservation system incorporating the following features:" +msgid "" +"The booking application is a complete hotel room reservation system " +"incorporating the following features:" msgstr "" #. Tag: para @@ -3194,19 +3858,34 @@ #. Tag: para #: Tutorial.xml:1175 #, no-c-format -msgid "The booking application uses JSF, EJB 3.0 and Seam, together with Facelets for the view. There is also a port of this application to JSF, Facelets, Seam, JavaBeans and Hibernate3." +msgid "" +"The booking application uses JSF, EJB 3.0 and Seam, together with Facelets " +"for the view. There is also a port of this application to JSF, Facelets, " +"Seam, JavaBeans and Hibernate3." msgstr "" #. Tag: para #: Tutorial.xml:1178 #, no-c-format -msgid "One of the things you'll notice if you play with this application for long enough is that it is extremely <emphasis>robust</emphasis>. You can play with back buttons and browser refresh and opening multiple windows and entering nonsensical data as much as you like and you will find it very difficult to make the application crash. You might think that we spent weeks testing and fixing bugs to achive this. Actually, this is not the case. Seam was designed to make it very straightforward to build robust web applications and a lot of robustness that you are probably used to having to code yourself comes naturally and automatically with Seam." +msgid "" +"One of the things you'll notice if you play with this application for long " +"enough is that it is extremely <emphasis>robust</emphasis>. You can play " +"with back buttons and browser refresh and opening multiple windows and " +"entering nonsensical data as much as you like and you will find it very " +"difficult to make the application crash. You might think that we spent weeks " +"testing and fixing bugs to achive this. Actually, this is not the case. Seam " +"was designed to make it very straightforward to build robust web " +"applications and a lot of robustness that you are probably used to having to " +"code yourself comes naturally and automatically with Seam." msgstr "" #. Tag: para #: Tutorial.xml:1185 #, no-c-format -msgid "As you browse the sourcecode of the example application, and learn how the application works, observe how the declarative state management and integrated validation has been used to achieve this robustness." +msgid "" +"As you browse the sourcecode of the example application, and learn how the " +"application works, observe how the declarative state management and " +"integrated validation has been used to achieve this robustness." msgstr "" #. Tag: title @@ -3218,43 +3897,62 @@ #. Tag: para #: Tutorial.xml:1193 #, no-c-format -msgid "The project structure is identical to the previous one, to install and deploy this application, please refer to <xref linkend=\"try-examples\"/>. Once you've successfully started the application, you can access it by pointing your browser to <ulink url=\"http://localhost:8080/seam-booking/\"> <literal>http://localhost:8080/seam-booking/</literal> </ulink>" +msgid "" +"The project structure is identical to the previous one, to install and " +"deploy this application, please refer to <xref linkend=\"try-examples\"/>. " +"Once you've successfully started the application, you can access it by " +"pointing your browser to <ulink url=\"http://localhost:8080/seam-booking/\"> " +"<literal>http://localhost:8080/seam-booking/</literal> </ulink>" msgstr "" #. Tag: para #: Tutorial.xml:1200 #, no-c-format -msgid "The application uses six session beans for to implement the business logic for the listed features." +msgid "" +"The application uses six session beans for to implement the business logic " +"for the listed features." msgstr "" #. Tag: para #: Tutorial.xml:1204 #, no-c-format -msgid "<literal>AuthenticatorAction</literal> provides the login authentication logic." +msgid "" +"<literal>AuthenticatorAction</literal> provides the login authentication " +"logic." msgstr "" #. Tag: para #: Tutorial.xml:1207 #, no-c-format -msgid "<literal>BookingListAction</literal> retrieves existing bookings for the currently logged in user." +msgid "" +"<literal>BookingListAction</literal> retrieves existing bookings for the " +"currently logged in user." msgstr "" #. Tag: para #: Tutorial.xml:1210 #, no-c-format -msgid "<literal>ChangePasswordAction</literal> updates the password of the currently logged in user." +msgid "" +"<literal>ChangePasswordAction</literal> updates the password of the " +"currently logged in user." msgstr "" #. Tag: para #: Tutorial.xml:1213 #, no-c-format -msgid "<literal>HotelBookingAction</literal> implements booking and confirmation functionality. This functionality is implemented as a <emphasis>conversation</emphasis>, so this is one of the most interesting classes in the application." +msgid "" +"<literal>HotelBookingAction</literal> implements booking and confirmation " +"functionality. This functionality is implemented as a " +"<emphasis>conversation</emphasis>, so this is one of the most interesting " +"classes in the application." msgstr "" #. Tag: para #: Tutorial.xml:1218 #, no-c-format -msgid "<literal>HotelSearchingAction</literal> implements the hotel search functionality." +msgid "" +"<literal>HotelSearchingAction</literal> implements the hotel search " +"functionality." msgstr "" #. Tag: para @@ -3278,13 +3976,17 @@ #. Tag: para #: Tutorial.xml:1231 #, no-c-format -msgid "<literal>Booking</literal> is an entity bean that represents an existing booking" +msgid "" +"<literal>Booking</literal> is an entity bean that represents an existing " +"booking" msgstr "" #. Tag: para #: Tutorial.xml:1233 #, no-c-format -msgid "<literal>User</literal> is an entity bean to represents a user who can make hotel bookings" +msgid "" +"<literal>User</literal> is an entity bean to represents a user who can make " +"hotel bookings" msgstr "" #. Tag: title @@ -3296,55 +3998,123 @@ #. Tag: para #: Tutorial.xml:1241 #, no-c-format -msgid "We encourage you browse the sourcecode at your pleasure. In this tutorial we'll concentrate upon one particular piece of functionality: hotel search, selection, booking and confirmation. From the point of view of the user, everything from selecting a hotel to confirming a booking is one continuous unit of work, a <emphasis>conversation</emphasis>. Searching, however, is <emphasis>not</emphasis> part of the conversation. The user can select multiple hotels from the same search results page, in different browser tabs." +msgid "" +"We encourage you browse the sourcecode at your pleasure. In this tutorial " +"we'll concentrate upon one particular piece of functionality: hotel search, " +"selection, booking and confirmation. From the point of view of the user, " +"everything from selecting a hotel to confirming a booking is one continuous " +"unit of work, a <emphasis>conversation</emphasis>. Searching, however, is " +"<emphasis>not</emphasis> part of the conversation. The user can select " +"multiple hotels from the same search results page, in different browser tabs." msgstr "" #. Tag: para #: Tutorial.xml:1247 #, no-c-format -msgid "Most web application architectures have no first class construct to represent a conversation. This causes enormous problems managing conversational state. Usually, Java web applications use a combination of several techniques. Some state can be transfered in the URL. What can't is either thrown into the <literal>HttpSession</literal> or flushed to the database after every request, and reconstructed from the database at the beginning of each new request." +msgid "" +"Most web application architectures have no first class construct to " +"represent a conversation. This causes enormous problems managing " +"conversational state. Usually, Java web applications use a combination of " +"several techniques. Some state can be transfered in the URL. What can't is " +"either thrown into the <literal>HttpSession</literal> or flushed to the " +"database after every request, and reconstructed from the database at the " +"beginning of each new request." msgstr "" #. Tag: para #: Tutorial.xml:1253 #, no-c-format -msgid "Since the database is the least scalable tier, this often results in an utterly unacceptable lack of scalability. Added latency is also a problem, due to the extra traffic to and from the database on every request. To reduce this redundant traffic, Java applications often introduce a data (second-level) cache that keeps commonly accessed data between requests. This cache is necessarily inefficient, because invalidation is based upon an LRU policy instead of being based upon when the user has finished working with the data. Furthermore, because the cache is shared between many concurrent transactions, we've introduced a whole raft of problem's associated with keeping the cached state consistent with the database." +msgid "" +"Since the database is the least scalable tier, this often results in an " +"utterly unacceptable lack of scalability. Added latency is also a problem, " +"due to the extra traffic to and from the database on every request. To " +"reduce this redundant traffic, Java applications often introduce a data " +"(second-level) cache that keeps commonly accessed data between requests. " +"This cache is necessarily inefficient, because invalidation is based upon an " +"LRU policy instead of being based upon when the user has finished working " +"with the data. Furthermore, because the cache is shared between many " +"concurrent transactions, we've introduced a whole raft of problem's " +"associated with keeping the cached state consistent with the database." msgstr "" #. Tag: para #: Tutorial.xml:1261 #, no-c-format -msgid "Now consider the state held in the <literal>HttpSession</literal>. The HttpSession is great place for true session data, data that is common to all requests that the user has with the application. However, it's a bad place to store data related to individual series of requests. Using the session of conversational quickly breaks down when dealing with the back button and multiple windows. On top of that, without careful programming, data in the HTTP Session can grow quite large, making the HTTP session difficult to cluster. Developing mechanisms to isolate session state associated with different concurrent conversations, and incorporating failsafes to ensure that conversation state is destroyed when the user aborts one of the conversations by closing a browser window or tab is not for the faint hearted. Fortunately, with Seam, you don't have to worry about that." +msgid "" +"Now consider the state held in the <literal>HttpSession</literal>. The " +"HttpSession is great place for true session data, data that is common to all " +"requests that the user has with the application. However, it's a bad place " +"to store data related to individual series of requests. Using the session of " +"conversational quickly breaks down when dealing with the back button and " +"multiple windows. On top of that, without careful programming, data in the " +"HTTP Session can grow quite large, making the HTTP session difficult to " +"cluster. Developing mechanisms to isolate session state associated with " +"different concurrent conversations, and incorporating failsafes to ensure " +"that conversation state is destroyed when the user aborts one of the " +"conversations by closing a browser window or tab is not for the faint " +"hearted. Fortunately, with Seam, you don't have to worry about that." msgstr "" #. Tag: para #: Tutorial.xml:1274 #, no-c-format -msgid "Seam introduces the <emphasis>conversation context</emphasis> as a first class construct. You can safely keep conversational state in this context, and be assured that it will have a well-defined lifecycle. Even better, you won't need to be continually pushing data back and forth between the application server and the database, since the conversation context is a natural cache of data that the user is currently working with." +msgid "" +"Seam introduces the <emphasis>conversation context</emphasis> as a first " +"class construct. You can safely keep conversational state in this context, " +"and be assured that it will have a well-defined lifecycle. Even better, you " +"won't need to be continually pushing data back and forth between the " +"application server and the database, since the conversation context is a " +"natural cache of data that the user is currently working with." msgstr "" #. Tag: para #: Tutorial.xml:1279 #, no-c-format -msgid "In this application, we'll use the conversation context to store stateful session beans. There is an ancient canard in the Java community that stateful session beans are a scalability killer. This may have been true in the early days of enterprise Java, but it is no longer true today. Modern application servers have extremely sophisticated mechanisms for stateful session bean state replication. JBoss AS, for example, performs fine-grained replication, replicating only those bean attribute values which actually changed. Note that all the traditional technical arguments for why stateful beans are inefficient apply equally to the <literal>HttpSession</literal>, so the practice of shifting state from business tier stateful session bean components to the web session to try and improve performance is unbelievably misguided. It is certainly possible to write unscalable applications using stateful session beans, by using stateful beans incorrectly, or by using them for the w! rong thing. But that doesn't mean you should <emphasis>never</emphasis> use them. If you remain unconvinced, Seam allows the use of POJOs instead of stateful session beans. With Seam, the choice is yours." +msgid "" +"In this application, we'll use the conversation context to store stateful " +"session beans. There is an ancient canard in the Java community that " +"stateful session beans are a scalability killer. This may have been true in " +"the early days of enterprise Java, but it is no longer true today. Modern " +"application servers have extremely sophisticated mechanisms for stateful " +"session bean state replication. JBoss AS, for example, performs fine-grained " +"replication, replicating only those bean attribute values which actually " +"changed. Note that all the traditional technical arguments for why stateful " +"beans are inefficient apply equally to the <literal>HttpSession</literal>, " +"so the practice of shifting state from business tier stateful session bean " +"components to the web session to try and improve performance is unbelievably " +"misguided. It is certainly possible to write unscalable applications using " +"stateful session beans, by using stateful beans incorrectly, or by using " +"them for the wrong thing. But that doesn't mean you should <emphasis>never</" +"emphasis> use them. If you remain unconvinced, Seam allows the use of POJOs " +"instead of stateful session beans. With Seam, the choice is yours." msgstr "" #. Tag: para #: Tutorial.xml:1297 #, no-c-format -msgid "The booking example application shows how stateful components with different scopes can collaborate together to achieve complex behaviors. The main page of the booking application allows the user to search for hotels. The search results are kept in the Seam session scope. When the user navigates to one of these hotels, a conversation begins, and a conversation scoped component calls back to the session scoped component to retrieve the selected hotel." +msgid "" +"The booking example application shows how stateful components with different " +"scopes can collaborate together to achieve complex behaviors. The main page " +"of the booking application allows the user to search for hotels. The search " +"results are kept in the Seam session scope. When the user navigates to one " +"of these hotels, a conversation begins, and a conversation scoped component " +"calls back to the session scoped component to retrieve the selected hotel." msgstr "" #. Tag: para #: Tutorial.xml:1303 #, no-c-format -msgid "The booking example also demonstrates the use of RichFaces Ajax to implement rich client behavior without the use of handwritten JavaScript." +msgid "" +"The booking example also demonstrates the use of RichFaces Ajax to implement " +"rich client behavior without the use of handwritten JavaScript." msgstr "" #. Tag: para #: Tutorial.xml:1306 #, no-c-format -msgid "The search functionality is implemented using a session-scope stateful session bean, similar to the one we saw in the message list example." +msgid "" +"The search functionality is implemented using a session-scope stateful " +"session bean, similar to the one we saw in the message list example." msgstr "" #. Tag: title @@ -3388,7 +4158,8 @@ " private void queryHotels()\n" " {\n" " hotels = \n" -" em.createQuery(\"select h from Hotel h where lower(h.name) like #{pattern} \" + \n" +" em.createQuery(\"select h from Hotel h where lower(h.name) like #" +"{pattern} \" + \n" " \"or lower(h.city) like #{pattern} \" + \n" " \"or lower(h.zip) like #{pattern} \" +\n" " \"or lower(h.address) like #{pattern}\")\n" @@ -3414,7 +4185,8 @@ " public String getSearchPattern()\n" " {\n" " return searchString==null ? \n" -" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + '%';\n" +" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + " +"'%';\n" " }\n" " \n" " public String getSearchString()\n" @@ -3462,7 +4234,8 @@ " private void queryHotels()\n" " {\n" " hotels = \n" -" em.createQuery(\"select h from Hotel h where lower(h.name) like #{pattern} \" + \n" +" em.createQuery(\"select h from Hotel h where lower(h.name) like #" +"{pattern} \" + \n" " \"or lower(h.city) like #{pattern} \" + \n" " \"or lower(h.zip) like #{pattern} \" +\n" " \"or lower(h.address) like #{pattern}\")\n" @@ -3488,7 +4261,8 @@ " public String getSearchPattern()\n" " {\n" " return searchString==null ? \n" -" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + '%';\n" +" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + " +"'%';\n" " }\n" " \n" " public String getSearchString()\n" @@ -3508,31 +4282,50 @@ #. Tag: para #: Tutorial.xml:1322 #, no-c-format -msgid "The EJB standard <literal>@Stateful</literal> annotation identifies this class as a stateful session bean. Stateful session beans are scoped to the conversation context by default." +msgid "" +"The EJB standard <literal>@Stateful</literal> annotation identifies this " +"class as a stateful session bean. Stateful session beans are scoped to the " +"conversation context by default." msgstr "" #. Tag: para #: Tutorial.xml:1327 #, no-c-format -msgid "The <literal>@Restrict</literal> annotation applies a security restriction to the component. It restricts access to the component allowing only logged-in users. The security chapter explains more about security in Seam." +msgid "" +"The <literal>@Restrict</literal> annotation applies a security restriction " +"to the component. It restricts access to the component allowing only logged-" +"in users. The security chapter explains more about security in Seam." msgstr "" #. Tag: para #: Tutorial.xml:1332 #, no-c-format -msgid "The <link linkend=\"datamodel-annotation\"> <literal>@DataModel</literal> </link> annotation exposes a <literal>List</literal> as a JSF <literal>ListDataModel</literal>. This makes it easy to implement clickable lists for search screens. In this case, the list of hotels is exposed to the page as a <literal>ListDataModel</literal> in the conversation variable named <literal>hotels</literal>." +msgid "" +"The <link linkend=\"datamodel-annotation\"> <literal>@DataModel</literal> </" +"link> annotation exposes a <literal>List</literal> as a JSF " +"<literal>ListDataModel</literal>. This makes it easy to implement clickable " +"lists for search screens. In this case, the list of hotels is exposed to the " +"page as a <literal>ListDataModel</literal> in the conversation variable " +"named <literal>hotels</literal>." msgstr "" #. Tag: para #: Tutorial.xml:1341 #, no-c-format -msgid "The EJB standard <literal>@Remove</literal> annotation specifies that a stateful session bean should be removed and its state destroyed after invocation of the annotated method. In Seam, all stateful session beans must define a method with no parameters marked <literal>@Remove</literal>. This method will be called when Seam destroys the session context." +msgid "" +"The EJB standard <literal>@Remove</literal> annotation specifies that a " +"stateful session bean should be removed and its state destroyed after " +"invocation of the annotated method. In Seam, all stateful session beans must " +"define a method with no parameters marked <literal>@Remove</literal>. This " +"method will be called when Seam destroys the session context." msgstr "" #. Tag: para #: Tutorial.xml:1352 #, no-c-format -msgid "The main page of the application is a Facelets page. Let's look at the fragment which relates to searching for hotels:" +msgid "" +"The main page of the application is a Facelets page. Let's look at the " +"fragment which relates to searching for hotels:" msgstr "" #. Tag: title @@ -3555,13 +4348,16 @@ "\n" " <h:form id=\"searchCriteria\">\n" " <fieldset> \n" -" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}\" \n" +" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}" +"\" \n" " style=\"width: 165px;\">\n" -" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}\" \n" +" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}" +"\" \n" " reRender=\"searchResults\" />\n" " </h:inputText>\n" "  \n" -" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#{hotelSearch.find}\" \n" +" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#" +"{hotelSearch.find}\" \n" " reRender=\"searchResults\"/>\n" "  \n" " <a:status>\n" @@ -3570,7 +4366,8 @@ " </f:facet>\n" " </a:status>\n" " <br/>\n" -" <h:outputLabel for=\"pageSize\">Maximum results:</h:outputLabel> \n" +" <h:outputLabel for=\"pageSize\">Maximum results:</h:" +"outputLabel> \n" " <h:selectOneMenu value=\"#{hotelSearch.pageSize}\" id=\"pageSize\">\n" " <f:selectItem itemLabel=\"5\" itemValue=\"5\"/>\n" " <f:selectItem itemLabel=\"10\" itemValue=\"10\"/>\n" @@ -3624,13 +4421,16 @@ "\n" " <h:form id=\"searchCriteria\">\n" " <fieldset> \n" -" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}\" \n" +" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}" +"\" \n" " style=\"width: 165px;\">\n" -" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}\" \n" +" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}" +"\" \n" " reRender=\"searchResults\" />\n" " </h:inputText>\n" "  \n" -" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#{hotelSearch.find}\" \n" +" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#" +"{hotelSearch.find}\" \n" " reRender=\"searchResults\"/>\n" "  \n" " <a:status>\n" @@ -3639,7 +4439,8 @@ " </f:facet>\n" " </a:status>\n" " <br/>\n" -" <h:outputLabel for=\"pageSize\">Maximum results:</h:outputLabel> \n" +" <h:outputLabel for=\"pageSize\">Maximum results:</h:" +"outputLabel> \n" " <h:selectOneMenu value=\"#{hotelSearch.pageSize}\" id=\"pageSize\">\n" " <f:selectItem itemLabel=\"5\" itemValue=\"5\"/>\n" " <f:selectItem itemLabel=\"10\" itemValue=\"10\"/>\n" @@ -3686,48 +4487,78 @@ #. Tag: para #: Tutorial.xml:1367 #, no-c-format -msgid "The RichFaces Ajax <literal><a:support></literal> tag allows a JSF action event listener to be called by asynchronous <literal>XMLHttpRequest</literal> when a JavaScript event like <literal>onkeyup</literal> occurs. Even better, the <literal>reRender</literal> attribute lets us render a fragment of the JSF page and perform a partial page update when the asynchronous response is received." +msgid "" +"The RichFaces Ajax <literal><a:support></literal> tag allows a JSF " +"action event listener to be called by asynchronous <literal>XMLHttpRequest</" +"literal> when a JavaScript event like <literal>onkeyup</literal> occurs. " +"Even better, the <literal>reRender</literal> attribute lets us render a " +"fragment of the JSF page and perform a partial page update when the " +"asynchronous response is received." msgstr "" #. Tag: para #: Tutorial.xml:1374 #, no-c-format -msgid "The RichFaces Ajax <literal><a:status></literal> tag lets us display an animated image while we wait for asynchronous requests to return." +msgid "" +"The RichFaces Ajax <literal><a:status></literal> tag lets us display " +"an animated image while we wait for asynchronous requests to return." msgstr "" #. Tag: para #: Tutorial.xml:1378 #, no-c-format -msgid "The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a region of the page which can be re-rendered by an asynchronous request." +msgid "" +"The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a " +"region of the page which can be re-rendered by an asynchronous request." msgstr "" #. Tag: para #: Tutorial.xml:1382 #, no-c-format -msgid "The Seam <literal><s:link></literal> tag lets us attach a JSF action listener to an ordinary (non-JavaScript) HTML link. The advantage of this over the standard JSF <literal><h:commandLink></literal> is that it preserves the operation of \"open in new window\" and \"open in new tab\". Also notice that we use a method binding with a parameter: <literal>#{hotelBooking.selectHotel(hot)}</literal>. This is not possible in the standard Unified EL, but Seam provides an extension to the EL that lets you use parameters on any method binding expression." +msgid "" +"The Seam <literal><s:link></literal> tag lets us attach a JSF action " +"listener to an ordinary (non-JavaScript) HTML link. The advantage of this " +"over the standard JSF <literal><h:commandLink></literal> is that it " +"preserves the operation of \"open in new window\" and \"open in new tab\". " +"Also notice that we use a method binding with a parameter: <literal>#" +"{hotelBooking.selectHotel(hot)}</literal>. This is not possible in the " +"standard Unified EL, but Seam provides an extension to the EL that lets you " +"use parameters on any method binding expression." msgstr "" #. Tag: para #: Tutorial.xml:1389 #, no-c-format -msgid "If you're wondering how navigation occurs, you can find all the rules in <literal>WEB-INF/pages.xml</literal>; this is discussed in <xref linkend=\"events.pageaction.navigation\"/>." +msgid "" +"If you're wondering how navigation occurs, you can find all the rules in " +"<literal>WEB-INF/pages.xml</literal>; this is discussed in <xref linkend=" +"\"events.pageaction.navigation\"/>." msgstr "" #. Tag: para #: Tutorial.xml:1398 #, no-c-format -msgid "This page displays the search results dynamically as we type, and lets us choose a hotel and pass it to the <literal>selectHotel()</literal> method of the <literal>HotelBookingAction</literal>, which is where the <emphasis>really</emphasis> interesting stuff is going to happen." +msgid "" +"This page displays the search results dynamically as we type, and lets us " +"choose a hotel and pass it to the <literal>selectHotel()</literal> method of " +"the <literal>HotelBookingAction</literal>, which is where the " +"<emphasis>really</emphasis> interesting stuff is going to happen." msgstr "" #. Tag: para #: Tutorial.xml:1403 #, no-c-format -msgid "Now let's see how the booking example application uses a conversation-scoped stateful session bean to achieve a natural cache of persistent data related to the conversation. The following code example is pretty long. But if you think of it as a list of scripted actions that implement the various steps of the conversation, it's understandable. Read the class from top to bottom, as if it were a story." +msgid "" +"Now let's see how the booking example application uses a conversation-scoped " +"stateful session bean to achieve a natural cache of persistent data related " +"to the conversation. The following code example is pretty long. But if you " +"think of it as a list of scripted actions that implement the various steps " +"of the conversation, it's understandable. Read the class from top to bottom, " +"as if it were a story." msgstr "" #. Tag: title -#: Tutorial.xml:1408 -#: Tutorial.xml:1633 +#: Tutorial.xml:1408 Tutorial.xml:1633 #, no-c-format msgid "HotelBookingAction.java" msgstr "HotelBookingAction.java" @@ -3787,13 +4618,16 @@ " calendar.add(Calendar.DAY_OF_MONTH, -1);\n" " if ( booking.getCheckinDate().before( calendar.getTime() ) )\n" " {\n" -" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n" +" facesMessages.addToControl(\"checkinDate\", \"Check in date must be " +"a future date\");\n" " bookingValid=false;\n" " }\n" -" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n" +" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate" +"() ) )\n" " {\n" " facesMessages.addToControl(\"checkoutDate\", \n" -" \"Check out date must be later than check in date\");\n" +" \"Check out date must be later than " +"check in date\");\n" " bookingValid=false;\n" " }\n" " else\n" @@ -3811,7 +4645,8 @@ " public void confirm()\n" " {\n" " em.persist(booking);\n" -" facesMessages.add(\"Thank you, #{user.name}, your confimation number \" + \n" +" facesMessages.add(\"Thank you, #{user.name}, your confimation number " +"\" + \n" " \" for #{hotel.name} is #{booki g.id}\");\n" " log.info(\"New booking: #{booking.id} for #{user.username}\");\n" " events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n" @@ -3875,13 +4710,16 @@ " calendar.add(Calendar.DAY_OF_MONTH, -1);\n" " if ( booking.getCheckinDate().before( calendar.getTime() ) )\n" " {\n" -" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n" +" facesMessages.addToControl(\"checkinDate\", \"Check in date must be " +"a future date\");\n" " bookingValid=false;\n" " }\n" -" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n" +" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate" +"() ) )\n" " {\n" " facesMessages.addToControl(\"checkoutDate\", \n" -" \"Check out date must be later than check in date\");\n" +" \"Check out date must be later than " +"check in date\");\n" " bookingValid=false;\n" " }\n" " else\n" @@ -3899,7 +4737,8 @@ " public void confirm()\n" " {\n" " em.persist(booking);\n" -" facesMessages.add(\"Thank you, #{user.name}, your confimation number \" + \n" +" facesMessages.add(\"Thank you, #{user.name}, your confimation number " +"\" + \n" " \" for #{hotel.name} is #{booki g.id}\");\n" " log.info(\"New booking: #{booking.id} for #{user.username}\");\n" " events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n" @@ -3915,43 +4754,78 @@ #. Tag: para #: Tutorial.xml:1421 #, no-c-format -msgid "This bean uses an EJB3 <emphasis>extended persistence context</emphasis>, so that any entity instances remain managed for the whole lifecycle of the stateful session bean." +msgid "" +"This bean uses an EJB3 <emphasis>extended persistence context</emphasis>, so " +"that any entity instances remain managed for the whole lifecycle of the " +"stateful session bean." msgstr "" #. Tag: para #: Tutorial.xml:1426 #, no-c-format -msgid "The <link linkend=\"out-annotation\"> <literal>@Out</literal> </link> annotation declares that an attribute value is <emphasis>outjected</emphasis> to a context variable after method invocations. In this case, the context variable named <literal>hotel</literal> will be set to the value of the <literal>hotel</literal> instance variable after every action listener invocation completes." +msgid "" +"The <link linkend=\"out-annotation\"> <literal>@Out</literal> </link> " +"annotation declares that an attribute value is <emphasis>outjected</" +"emphasis> to a context variable after method invocations. In this case, the " +"context variable named <literal>hotel</literal> will be set to the value of " +"the <literal>hotel</literal> instance variable after every action listener " +"invocation completes." msgstr "" #. Tag: para #: Tutorial.xml:1434 #, no-c-format -msgid "The <link linkend=\"begin-annotation\"> <literal>@Begin</literal> </link> annotation specifies that the annotated method begins a <emphasis>long-running conversation</emphasis>, so the current conversation context will not be destroyed at the end of the request. Instead, it will be reassociated with every request from the current window, and destroyed either by timeout due to conversation inactivity or invocation of a matching <literal>@End</literal> method." +msgid "" +"The <link linkend=\"begin-annotation\"> <literal>@Begin</literal> </link> " +"annotation specifies that the annotated method begins a <emphasis>long-" +"running conversation</emphasis>, so the current conversation context will " +"not be destroyed at the end of the request. Instead, it will be reassociated " +"with every request from the current window, and destroyed either by timeout " +"due to conversation inactivity or invocation of a matching <literal>@End</" +"literal> method." msgstr "" #. Tag: para #: Tutorial.xml:1443 #, no-c-format -msgid "The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> annotation specifies that the annotated method ends the current long-running conversation, so the current conversation context will be destroyed at the end of the request." +msgid "" +"The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> " +"annotation specifies that the annotated method ends the current long-running " +"conversation, so the current conversation context will be destroyed at the " +"end of the request." msgstr "" #. Tag: para #: Tutorial.xml:1450 #, no-c-format -msgid "This EJB remove method will be called when Seam destroys the conversation context. Don't forget to define this method!" +msgid "" +"This EJB remove method will be called when Seam destroys the conversation " +"context. Don't forget to define this method!" msgstr "" #. Tag: para #: Tutorial.xml:1458 #, no-c-format -msgid "<literal>HotelBookingAction</literal> contains all the action listener methods that implement selection, booking and booking confirmation, and holds state related to this work in its instance variables. We think you'll agree that this code is much cleaner and simpler than getting and setting <literal>HttpSession</literal> attributes." +msgid "" +"<literal>HotelBookingAction</literal> contains all the action listener " +"methods that implement selection, booking and booking confirmation, and " +"holds state related to this work in its instance variables. We think you'll " +"agree that this code is much cleaner and simpler than getting and setting " +"<literal>HttpSession</literal> attributes." msgstr "" #. Tag: para #: Tutorial.xml:1464 #, no-c-format -msgid "Even better, a user can have multiple isolated conversations per login session. Try it! Log in, run a search, and navigate to different hotel pages in multiple browser tabs. You'll be able to work on creating two different hotel reservations at the same time. If you leave any one conversation inactive for long enough, Seam will eventually time out that conversation and destroy its state. If, after ending a conversation, you backbutton to a page of that conversation and try to perform an action, Seam will detect that the conversation was already ended, and redirect you to the search page." +msgid "" +"Even better, a user can have multiple isolated conversations per login " +"session. Try it! Log in, run a search, and navigate to different hotel pages " +"in multiple browser tabs. You'll be able to work on creating two different " +"hotel reservations at the same time. If you leave any one conversation " +"inactive for long enough, Seam will eventually time out that conversation " +"and destroy its state. If, after ending a conversation, you backbutton to a " +"page of that conversation and try to perform an action, Seam will detect " +"that the conversation was already ended, and redirect you to the search page." msgstr "" #. Tag: title @@ -3963,7 +4837,11 @@ #. Tag: para #: Tutorial.xml:1476 #, no-c-format -msgid "The WAR also includes <literal>seam-debug.jar</literal>. The Seam debug page will be available if this jar is deployed in <literal>WEB-INF/lib</literal>, along with the Facelets, and if you set the debug property of the <literal>init</literal> component:" +msgid "" +"The WAR also includes <literal>seam-debug.jar</literal>. The Seam debug page " +"will be available if this jar is deployed in <literal>WEB-INF/lib</literal>, " +"along with the Facelets, and if you set the debug property of the " +"<literal>init</literal> component:" msgstr "" #. Tag: programlisting @@ -3975,7 +4853,11 @@ #. Tag: para #: Tutorial.xml:1483 #, no-c-format -msgid "This page lets you browse and inspect the Seam components in any of the Seam contexts associated with your current login session. Just point your browser at <ulink url=\"http://localhost:8080/seam-booking/debug.seam\"> <literal>http://localhost:8080/seam-booking/debug.seam</literal> </ulink>." +msgid "" +"This page lets you browse and inspect the Seam components in any of the Seam " +"contexts associated with your current login session. Just point your browser " +"at <ulink url=\"http://localhost:8080/seam-booking/debug.seam\"> " +"<literal>http://localhost:8080/seam-booking/debug.seam</literal> </ulink>." msgstr "" #. Tag: title @@ -3987,31 +4869,58 @@ #. Tag: para #: Tutorial.xml:1508 #, no-c-format -msgid "Long-running conversations make it simple to maintain consistency of state in an application even in the face of multi-window operation and back-buttoning. Unfortunately, simply beginning and ending a long-running conversation is not always enough. Depending on the requirements of the application, inconsistencies between what the user's expectations and the reality of the application’s state can still result." +msgid "" +"Long-running conversations make it simple to maintain consistency of state " +"in an application even in the face of multi-window operation and back-" +"buttoning. Unfortunately, simply beginning and ending a long-running " +"conversation is not always enough. Depending on the requirements of the " +"application, inconsistencies between what the user's expectations and the " +"reality of the application’s state can still result." msgstr "" #. Tag: para #: Tutorial.xml:1513 #, no-c-format -msgid "The nested booking application extends the features of the hotel booking application to incorporate the selection of rooms. Each hotel has available rooms with descriptions for a user to select from. This requires the addition of a room selection page in the hotel reservation flow." +msgid "" +"The nested booking application extends the features of the hotel booking " +"application to incorporate the selection of rooms. Each hotel has available " +"rooms with descriptions for a user to select from. This requires the " +"addition of a room selection page in the hotel reservation flow." msgstr "" #. Tag: para #: Tutorial.xml:1526 #, no-c-format -msgid "The user now has the option to select any available room to be included in the booking. As with the hotel booking application we saw previously, this can lead to issues with state consistency. As with storing state in the <varname>HTTPSession</varname>, if a conversation variable changes it affects all windows operating within the same conversation context." +msgid "" +"The user now has the option to select any available room to be included in " +"the booking. As with the hotel booking application we saw previously, this " +"can lead to issues with state consistency. As with storing state in the " +"<varname>HTTPSession</varname>, if a conversation variable changes it " +"affects all windows operating within the same conversation context." msgstr "" #. Tag: para #: Tutorial.xml:1531 #, no-c-format -msgid "To demonstrate this, let’s suppose the user clones the room selection screen in a new window. The user then selects the <emphasis>Wonderful Room</emphasis> and proceeds to the confirmation screen. To see just how much it would cost to live the high-life, the user returns to the original window, selects the <emphasis>Fantastic Suite</emphasis> for booking, and again proceeds to confirmation. After reviewing the total cost, the user decides that practicality wins out and returns to the window showing <emphasis>Wonderful Room</emphasis> to confirm." +msgid "" +"To demonstrate this, let’s suppose the user clones the room selection screen " +"in a new window. The user then selects the <emphasis>Wonderful Room</" +"emphasis> and proceeds to the confirmation screen. To see just how much it " +"would cost to live the high-life, the user returns to the original window, " +"selects the <emphasis>Fantastic Suite</emphasis> for booking, and again " +"proceeds to confirmation. After reviewing the total cost, the user decides " +"that practicality wins out and returns to the window showing " +"<emphasis>Wonderful Room</emphasis> to confirm." msgstr "" #. Tag: para #: Tutorial.xml:1537 #, no-c-format -msgid "In this scenario, if we simply store all state in the conversation, we are not protected from multi-window operation within the same conversation. Nested conversations allow us to achieve correct behavior even when context can vary within the same conversation." +msgid "" +"In this scenario, if we simply store all state in the conversation, we are " +"not protected from multi-window operation within the same conversation. " +"Nested conversations allow us to achieve correct behavior even when context " +"can vary within the same conversation." msgstr "" #. Tag: title @@ -4023,7 +4932,10 @@ #. Tag: para #: Tutorial.xml:1545 #, no-c-format -msgid "Now let's see how the nested booking example extends the behavior of the hotel booking application through use of nested conversations. Again, we can read the class from top to bottom, as if it were a story." +msgid "" +"Now let's see how the nested booking example extends the behavior of the " +"hotel booking application through use of nested conversations. Again, we can " +"read the class from top to bottom, as if it were a story." msgstr "" #. Tag: title @@ -4062,7 +4974,8 @@ " @Factory(\"availableRooms\")\n" " public void loadAvailableRooms()\n" " {\n" -" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), booking.getCheckoutDate());\n" +" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), " +"booking.getCheckoutDate());\n" " log.info(\"Retrieved #0 available rooms\", availableRooms.size());\n" " }\n" "\n" @@ -4085,7 +4998,8 @@ "\n" " public String requestConfirmation()\n" " {\n" -" // all validations are performed through the s:validateAll, so checks are already\n" +" // all validations are performed through the s:validateAll, so checks " +"are already\n" " // performed\n" " log.info(\"Request confirmation from user\");\n" " \n" @@ -4100,7 +5014,8 @@ " return \"cancel\";\n" " }\n" "\n" -" @Destroy @Remove \n" +" @Destroy " +"@Remove \n" " public void destroy() {} \n" "}\n" "]]>" @@ -4131,7 +5046,8 @@ " @Factory(\"availableRooms\")\n" " public void loadAvailableRooms()\n" " {\n" -" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), booking.getCheckoutDate());\n" +" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), " +"booking.getCheckoutDate());\n" " log.info(\"Retrieved #0 available rooms\", availableRooms.size());\n" " }\n" "\n" @@ -4154,7 +5070,8 @@ "\n" " public String requestConfirmation()\n" " {\n" -" // all validations are performed through the s:validateAll, so checks are already\n" +" // all validations are performed through the s:validateAll, so checks " +"are already\n" " // performed\n" " log.info(\"Request confirmation from user\");\n" " \n" @@ -4169,7 +5086,8 @@ " return \"cancel\";\n" " }\n" "\n" -" @Destroy @Remove \n" +" @Destroy " +"@Remove \n" " public void destroy() {} \n" "}\n" "]]>" @@ -4177,31 +5095,58 @@ #. Tag: para #: Tutorial.xml:1561 #, no-c-format -msgid "The <varname>hotel</varname> instance is injected from the conversation context. The hotel is loaded through an <emphasis>extended persistence context</emphasis> so that the entity remains managed throughout the conversation. This allows us to lazily load the <varname>availableRooms</varname> through an <varname>@Factory</varname> method by simply walking the assocation." +msgid "" +"The <varname>hotel</varname> instance is injected from the conversation " +"context. The hotel is loaded through an <emphasis>extended persistence " +"context</emphasis> so that the entity remains managed throughout the " +"conversation. This allows us to lazily load the <varname>availableRooms</" +"varname> through an <varname>@Factory</varname> method by simply walking the " +"assocation." msgstr "" #. Tag: para #: Tutorial.xml:1569 #, no-c-format -msgid "When <link linkend=\"begin-annotation\"> <literal>@Begin(nested=true)</literal> </link> is encountered, a nested conversation is pushed onto the conversation stack. When executing within a nested conversation, components still have access to all outer conversation state, but setting any values in the nested conversation’s state container does not affect the outer conversation. In addition, nested conversations can exist concurrently stacked on the same outer conversation, allowing independent state for each." +msgid "" +"When <link linkend=\"begin-annotation\"> <literal>@Begin(nested=true)</" +"literal> </link> is encountered, a nested conversation is pushed onto the " +"conversation stack. When executing within a nested conversation, components " +"still have access to all outer conversation state, but setting any values in " +"the nested conversation’s state container does not affect the outer " +"conversation. In addition, nested conversations can exist concurrently " +"stacked on the same outer conversation, allowing independent state for each." msgstr "" #. Tag: para #: Tutorial.xml:1578 #, no-c-format -msgid "The <varname>roomSelection</varname> is outjected to the conversation based on the <varname>@DataModelSelection</varname>. Note that because the nested conversation has an independent context, the <varname>roomSelection</varname> is only set into the new nested conversation. Should the user select a different preference in another window or tab a new nested conversation would be started." +msgid "" +"The <varname>roomSelection</varname> is outjected to the conversation based " +"on the <varname>@DataModelSelection</varname>. Note that because the nested " +"conversation has an independent context, the <varname>roomSelection</" +"varname> is only set into the new nested conversation. Should the user " +"select a different preference in another window or tab a new nested " +"conversation would be started." msgstr "" #. Tag: para #: Tutorial.xml:1585 #, no-c-format -msgid "The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> annotation pops the conversation stack and resumes the outer conversation. The <varname>roomSelection</varname> is destroyed along with the conversation context." +msgid "" +"The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> " +"annotation pops the conversation stack and resumes the outer conversation. " +"The <varname>roomSelection</varname> is destroyed along with the " +"conversation context." msgstr "" #. Tag: para #: Tutorial.xml:1594 #, no-c-format -msgid "When we being a nested conversation it is pushed onto the conversation stack. In the <varname>nestedbooking</varname> example, the conversation stack consists of the outer long-running conversation (the booking) and each of the nested conversations (room selections)." +msgid "" +"When we being a nested conversation it is pushed onto the conversation " +"stack. In the <varname>nestedbooking</varname> example, the conversation " +"stack consists of the outer long-running conversation (the booking) and each " +"of the nested conversations (room selections)." msgstr "" #. Tag: title @@ -4223,13 +5168,17 @@ " <div class=\"section\">\n" " <h:outputText styleClass=\"output\" \n" " value=\"No rooms available for the dates selected: \" \n" -" rendered=\"#{availableRooms != null and availableRooms.rowCount == 0}\"/>\n" +" rendered=\"#{availableRooms != null and availableRooms." +"rowCount == 0}\"/>\n" " <h:outputText styleClass=\"output\" \n" " value=\"Rooms available for the dates selected: \" \n" -" rendered=\"#{availableRooms != null and availableRooms.rowCount > 0}\"/>\n" +" rendered=\"#{availableRooms != null and availableRooms." +"rowCount > 0}\"/>\n" " \n" -" <h:outputText styleClass=\"output\" value=\"#{booking.checkinDate}\"/> -\n" -" <h:outputText styleClass=\"output\" value=\"#{booking.checkoutDate}\"/>\n" +" <h:outputText styleClass=\"output\" value=\"#{booking." +"checkinDate}\"/> -\n" +" <h:outputText styleClass=\"output\" value=\"#{booking." +"checkoutDate}\"/>\n" " \n" " <br/><br/>\n" " \n" @@ -4246,20 +5195,23 @@ " <h:column>\n" " <f:facet name=\"header\">Per Night</f:facet>\n" " <h:outputText value=\"#{room.price}\">\n" -" <f:convertNumber type=\"currency\" currencySymbol=\"$\"/>\n" +" <f:convertNumber type=\"currency\" currencySymbol=\"$" +"\"/>\n" " </h:outputText>\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">Action</f:facet>\n" " <h:commandLink id=\"selectRoomPreference\" \n" -" action=\"#{roomPreference.selectPreference}\">Select</h:commandLink>\n" +" action=\"#{roomPreference.selectPreference}" +"\">Select</h:commandLink>\n" " </h:column>\n" " </h:dataTable>\n" " </div>\n" " <div class=\"entry\">\n" " <div class=\"label\"> </div>\n" " <div class=\"input\">\n" -" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book.xhtml\"/>\n" +" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book." +"xhtml\"/>\n" " </div>\n" " </div> \n" " </h:form>\n" @@ -4275,13 +5227,17 @@ " <div class=\"section\">\n" " <h:outputText styleClass=\"output\" \n" " value=\"No rooms available for the dates selected: \" \n" -" rendered=\"#{availableRooms != null and availableRooms.rowCount == 0}\"/>\n" +" rendered=\"#{availableRooms != null and availableRooms." +"rowCount == 0}\"/>\n" " <h:outputText styleClass=\"output\" \n" " value=\"Rooms available for the dates selected: \" \n" -" rendered=\"#{availableRooms != null and availableRooms.rowCount > 0}\"/>\n" +" rendered=\"#{availableRooms != null and availableRooms." +"rowCount > 0}\"/>\n" " \n" -" <h:outputText styleClass=\"output\" value=\"#{booking.checkinDate}\"/> -\n" -" <h:outputText styleClass=\"output\" value=\"#{booking.checkoutDate}\"/>\n" +" <h:outputText styleClass=\"output\" value=\"#{booking." +"checkinDate}\"/> -\n" +" <h:outputText styleClass=\"output\" value=\"#{booking." +"checkoutDate}\"/>\n" " \n" " <br/><br/>\n" " \n" @@ -4298,20 +5254,23 @@ " <h:column>\n" " <f:facet name=\"header\">Per Night</f:facet>\n" " <h:outputText value=\"#{room.price}\">\n" -" <f:convertNumber type=\"currency\" currencySymbol=\"$\"/>\n" +" <f:convertNumber type=\"currency\" currencySymbol=\"$" +"\"/>\n" " </h:outputText>\n" " </h:column>\n" " <h:column>\n" " <f:facet name=\"header\">Action</f:facet>\n" " <h:commandLink id=\"selectRoomPreference\" \n" -" action=\"#{roomPreference.selectPreference}\">Select</h:commandLink>\n" +" action=\"#{roomPreference.selectPreference}" +"\">Select</h:commandLink>\n" " </h:column>\n" " </h:dataTable>\n" " </div>\n" " <div class=\"entry\">\n" " <div class=\"label\"> </div>\n" " <div class=\"input\">\n" -" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book.xhtml\"/>\n" +" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book." +"xhtml\"/>\n" " </div>\n" " </div> \n" " </h:form>\n" @@ -4321,25 +5280,43 @@ #. Tag: para #: Tutorial.xml:1610 #, no-c-format -msgid "When requested from EL, the <varname>#{availableRooms}</varname> are loaded by the <varname>@Factory</varname> method defined in <varname>RoomPreferenceAction</varname>. The <varname>@Factory</varname> method will only be executed once to load the values into the current context as a <link linkend=\"datamodel-annotation\"> <varname>@DataModel</varname> </link> instance." +msgid "" +"When requested from EL, the <varname>#{availableRooms}</varname> are loaded " +"by the <varname>@Factory</varname> method defined in " +"<varname>RoomPreferenceAction</varname>. The <varname>@Factory</varname> " +"method will only be executed once to load the values into the current " +"context as a <link linkend=\"datamodel-annotation\"> <varname>@DataModel</" +"varname> </link> instance." msgstr "" #. Tag: para #: Tutorial.xml:1617 #, no-c-format -msgid "Invoking the <varname>#{roomPreference.selectPreference}</varname> action results in the row being selected and set into the <varname>@DataModelSelection</varname>. This value is then outjected to the nested conversation context." +msgid "" +"Invoking the <varname>#{roomPreference.selectPreference}</varname> action " +"results in the row being selected and set into the " +"<varname>@DataModelSelection</varname>. This value is then outjected to the " +"nested conversation context." msgstr "" #. Tag: para #: Tutorial.xml:1621 #, no-c-format -msgid "Revising the dates simply returns to the <varname>/book.xhtml</varname>. Note that we have not yet nested a conversation (no room preference has been selected), so the current conversation can simply be resumed. The <varname><s:button></varname> component simply propagates the current conversation when displaying the <varname>/book.xhtml</varname> view." +msgid "" +"Revising the dates simply returns to the <varname>/book.xhtml</varname>. " +"Note that we have not yet nested a conversation (no room preference has been " +"selected), so the current conversation can simply be resumed. The " +"<varname><s:button></varname> component simply propagates the current " +"conversation when displaying the <varname>/book.xhtml</varname> view." msgstr "" #. Tag: para #: Tutorial.xml:1629 #, no-c-format -msgid "Now that we have seen how to nest a conversation, let's see how we can confirm the booking once a room has been selected. This can be achieved by simply extending the behavior of the <varname>HotelBookingAction</varname>." +msgid "" +"Now that we have seen how to nest a conversation, let's see how we can " +"confirm the booking once a room has been selected. This can be achieved by " +"simply extending the behavior of the <varname>HotelBookingAction</varname>." msgstr "" #. Tag: programlisting @@ -4386,9 +5363,12 @@ " \n" " public String setBookingDates()\n" " {\n" -" // the result will indicate whether or not to begin the nested conversation\n" -" // as well as the navigation. if a null result is returned, the nested\n" -" // conversation will not begin, and the user will be returned to the current\n" +" // the result will indicate whether or not to begin the nested " +"conversation\n" +" // as well as the navigation. if a null result is returned, the " +"nested\n" +" // conversation will not begin, and the user will be returned to the " +"current\n" " // page to fix validation issues\n" " String result = null;\n" "\n" @@ -4398,11 +5378,14 @@ " // validate what we have received from the user so far\n" " if ( booking.getCheckinDate().before( calendar.getTime() ) )\n" " {\n" -" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n" +" facesMessages.addToControl(\"checkinDate\", \"Check in date must be " +"a future date\");\n" " }\n" -" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n" +" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate" +"() ) )\n" " {\n" -" facesMessages.addToControl(\"checkoutDate\", \"Check out date must be later than check in date\");\n" +" facesMessages.addToControl(\"checkoutDate\", \"Check out date must " +"be later than check in date\");\n" " }\n" " else\n" " {\n" @@ -4424,12 +5407,14 @@ " @End(root=true)\n" " public void confirm()\n" " {\n" -" // on confirmation we set the room preference in the booking. the room preference\n" +" // on confirmation we set the room preference in the booking. the " +"room preference\n" " // will be injected based on the nested conversation we are in.\n" " booking.setRoomPreference(roomSelection);\n" "\n" " em.persist(booking);\n" -" facesMessages.add(\"Thank you, #{user.name}, your confimation number for #{hotel.name} is #{booking.id}\");\n" +" facesMessages.add(\"Thank you, #{user.name}, your confimation number " +"for #{hotel.name} is #{booking.id}\");\n" " log.info(\"New booking: #{booking.id} for #{user.username}\");\n" " events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n" " }\n" @@ -4482,9 +5467,12 @@ " \n" " public String setBookingDates()\n" " {\n" -" // the result will indicate whether or not to begin the nested conversation\n" -" // as well as the navigation. if a null result is returned, the nested\n" -" // conversation will not begin, and the user will be returned to the current\n" +" // the result will indicate whether or not to begin the nested " +"conversation\n" +" // as well as the navigation. if a null result is returned, the " +"nested\n" +" // conversation will not begin, and the user will be returned to the " +"current\n" " // page to fix validation issues\n" " String result = null;\n" "\n" @@ -4494,11 +5482,14 @@ " // validate what we have received from the user so far\n" " if ( booking.getCheckinDate().before( calendar.getTime() ) )\n" " {\n" -" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n" +" facesMessages.addToControl(\"checkinDate\", \"Check in date must be " +"a future date\");\n" " }\n" -" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n" +" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate" +"() ) )\n" " {\n" -" facesMessages.addToControl(\"checkoutDate\", \"Check out date must be later than check in date\");\n" +" facesMessages.addToControl(\"checkoutDate\", \"Check out date must " +"be later than check in date\");\n" " }\n" " else\n" " {\n" @@ -4520,12 +5511,14 @@ " @End(root=true)\n" " public void confirm()\n" " {\n" -" // on confirmation we set the room preference in the booking. the room preference\n" +" // on confirmation we set the room preference in the booking. the " +"room preference\n" " // will be injected based on the nested conversation we are in.\n" " booking.setRoomPreference(roomSelection);\n" "\n" " em.persist(booking);\n" -" facesMessages.add(\"Thank you, #{user.name}, your confimation number for #{hotel.name} is #{booking.id}\");\n" +" facesMessages.add(\"Thank you, #{user.name}, your confimation number " +"for #{hotel.name} is #{booking.id}\");\n" " log.info(\"New booking: #{booking.id} for #{user.username}\");\n" " events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n" " }\n" @@ -4541,25 +5534,45 @@ #. Tag: para #: Tutorial.xml:1644 #, no-c-format -msgid "Annotating an action with <link linkend=\"end-annotation\"> <varname>@End(root=true)</varname> </link> ends the root conversation which effectively destroys the entire conversation stack. When any conversation is ended, it's nested conversations are ended as well. As the root is the conversation that started it all, this is a simple way to destroy and release all state associated with a workspace once the booking is confirmed." +msgid "" +"Annotating an action with <link linkend=\"end-annotation\"> <varname>@End" +"(root=true)</varname> </link> ends the root conversation which effectively " +"destroys the entire conversation stack. When any conversation is ended, it's " +"nested conversations are ended as well. As the root is the conversation that " +"started it all, this is a simple way to destroy and release all state " +"associated with a workspace once the booking is confirmed." msgstr "" #. Tag: para #: Tutorial.xml:1652 #, no-c-format -msgid "The <varname>roomSelection</varname> is only associated with the <varname>booking</varname> on user confirmation. While outjecting values to the nested conversation context will not impact the outer conversation, any objects injected from the outer conversation are injected by reference. This means that any changing to these objects will be reflected in the parent conversation as well as other concurrent nested conversations." +msgid "" +"The <varname>roomSelection</varname> is only associated with the " +"<varname>booking</varname> on user confirmation. While outjecting values to " +"the nested conversation context will not impact the outer conversation, any " +"objects injected from the outer conversation are injected by reference. This " +"means that any changing to these objects will be reflected in the parent " +"conversation as well as other concurrent nested conversations." msgstr "" #. Tag: para #: Tutorial.xml:1659 #, no-c-format -msgid "By simply annotating the cancellation action with <link linkend=\"end-annotation\"> <varname>@End(root=true, beforeRedirect=true)</varname> </link> we can easily destroy and release all state associated with the workspace prior to redirecting the user back to the hotel selection view." +msgid "" +"By simply annotating the cancellation action with <link linkend=\"end-" +"annotation\"> <varname>@End(root=true, beforeRedirect=true)</varname> </" +"link> we can easily destroy and release all state associated with the " +"workspace prior to redirecting the user back to the hotel selection view." msgstr "" #. Tag: para #: Tutorial.xml:1669 #, no-c-format -msgid "Feel free to deploy the application, open many windows or tabs and attempt combinations of various hotels with various room preferences. Confirming a booking always results in the correct hotel and room preference thanks to the nested conversation model." +msgid "" +"Feel free to deploy the application, open many windows or tabs and attempt " +"combinations of various hotels with various room preferences. Confirming a " +"booking always results in the correct hotel and room preference thanks to " +"the nested conversation model." msgstr "" #. Tag: title @@ -4571,18 +5584,21 @@ #. Tag: para #: Tutorial.xml:1678 #, no-c-format -msgid "The DVD Store demo application shows the practical usage of jBPM for both task management and pageflow." +msgid "" +"The DVD Store demo application shows the practical usage of jBPM for both " +"task management and pageflow." msgstr "" #. Tag: para #: Tutorial.xml:1680 #, no-c-format -msgid "The user screens take advantage of a jPDL pageflow to implement searching and shopping cart functionality." +msgid "" +"The user screens take advantage of a jPDL pageflow to implement searching " +"and shopping cart functionality." msgstr "" #. Tag: screeninfo -#: Tutorial.xml:1684 -#: Tutorial.xml:1699 +#: Tutorial.xml:1684 Tutorial.xml:1699 #, no-c-format msgid "DVD Store example" msgstr "Esempio di Negozio DVD" @@ -4590,13 +5606,18 @@ #. Tag: para #: Tutorial.xml:1695 #, no-c-format -msgid "The administration screens take use jBPM to manage the approval and shipping cycle for orders. The business process may even be changed dynamically, by selecting a different process definition!" +msgid "" +"The administration screens take use jBPM to manage the approval and shipping " +"cycle for orders. The business process may even be changed dynamically, by " +"selecting a different process definition!" msgstr "" #. Tag: para #: Tutorial.xml:1711 #, no-c-format -msgid "The Seam DVD Store demo can be run from <literal>dvdstore</literal> directory, just like the other demo applications." +msgid "" +"The Seam DVD Store demo can be run from <literal>dvdstore</literal> " +"directory, just like the other demo applications." msgstr "" #. Tag: title @@ -4608,7 +5629,16 @@ #. Tag: para #: Tutorial.xml:1720 #, no-c-format -msgid "Seam makes it very easy to implement applications which keep state on the server-side. However, server-side state is not always appropriate, especially in for functionality that serves up <emphasis>content</emphasis>. For this kind of problem we often want to keep application state in the URL so that any page can be accessed at any time through a bookmark. The blog example shows how to a implement an application that supports bookmarking throughout, even on the search results page. This example demonstrates how Seam can manage application state in the URL as well as how Seam can rewrite those URLs to be even" +msgid "" +"Seam makes it very easy to implement applications which keep state on the " +"server-side. However, server-side state is not always appropriate, " +"especially in for functionality that serves up <emphasis>content</emphasis>. " +"For this kind of problem we often want to keep application state in the URL " +"so that any page can be accessed at any time through a bookmark. The blog " +"example shows how to a implement an application that supports bookmarking " +"throughout, even on the search results page. This example demonstrates how " +"Seam can manage application state in the URL as well as how Seam can rewrite " +"those URLs to be even" msgstr "" #. Tag: screeninfo @@ -4620,7 +5650,10 @@ #. Tag: para #: Tutorial.xml:1744 #, no-c-format -msgid "The Blog example demonstrates the use of \"pull\"-style MVC, where instead of using action listener methods to retrieve data and prepare the data for the view, the view pulls data from components as it is being rendered." +msgid "" +"The Blog example demonstrates the use of \"pull\"-style MVC, where instead " +"of using action listener methods to retrieve data and prepare the data for " +"the view, the view pulls data from components as it is being rendered." msgstr "" #. Tag: title @@ -4632,22 +5665,27 @@ #. Tag: para #: Tutorial.xml:1751 #, no-c-format -msgid "This snippet from the <literal>index.xhtml</literal> facelets page displays a list of recent blog entries:" +msgid "" +"This snippet from the <literal>index.xhtml</literal> facelets page displays " +"a list of recent blog entries:" msgstr "" #. Tag: programlisting #: Tutorial.xml:1755 #, no-c-format msgid "" -"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" rows=\"3\">\n" +"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" " +"rows=\"3\">\n" " <h:column>\n" " <div class=\"blogEntry\">\n" " <h3>#{blogEntry.title}</h3>\n" " <div>\n" -" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry.body : blogEntry.excerpt}\"/>\n" +" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry." +"body : blogEntry.excerpt}\"/>\n" " </div>\n" " <p>\n" -" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}\" propagation=\"none\"\n" +" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}" +"\" propagation=\"none\"\n" " value=\"Read more...\">\n" " <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n" " </s:link>\n" @@ -4655,10 +5693,12 @@ " <p>\n" " [Posted on \n" " <h:outputText value=\"#{blogEntry.date}\">\n" -" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n" +" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#" +"{blog.locale}\" type=\"both\"/>\n" " </h:outputText>]\n" "  \n" -" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]\">\n" +" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]" +"\">\n" " <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n" " </s:link>\n" " </p>\n" @@ -4666,15 +5706,18 @@ " </h:column>\n" "</h:dataTable>]]>" msgstr "" -"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" rows=\"3\">\n" +"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" " +"rows=\"3\">\n" " <h:column>\n" " <div class=\"blogEntry\">\n" " <h3>#{blogEntry.title}</h3>\n" " <div>\n" -" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry.body : blogEntry.excerpt}\"/>\n" +" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry." +"body : blogEntry.excerpt}\"/>\n" " </div>\n" " <p>\n" -" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}\" propagation=\"none\"\n" +" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}" +"\" propagation=\"none\"\n" " value=\"Read more...\">\n" " <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n" " </s:link>\n" @@ -4682,10 +5725,12 @@ " <p>\n" " [Posted on \n" " <h:outputText value=\"#{blogEntry.date}\">\n" -" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n" +" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#" +"{blog.locale}\" type=\"both\"/>\n" " </h:outputText>]\n" "  \n" -" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]\">\n" +" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]" +"\">\n" " <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n" " </s:link>\n" " </p>\n" @@ -4696,7 +5741,13 @@ #. Tag: para #: Tutorial.xml:1759 #, no-c-format -msgid "If we navigate to this page from a bookmark, how does the <literal>#{blog.recentBlogEntries}</literal> data used by the <literal><h:dataTable></literal> actually get initialized? The <literal>Blog</literal> is retrieved lazily—\"pulled\"—when needed, by a Seam component named <literal>blog</literal>. This is the opposite flow of control to what is used in traditional action-based web frameworks like Struts." +msgid "" +"If we navigate to this page from a bookmark, how does the <literal>#{blog." +"recentBlogEntries}</literal> data used by the <literal><h:dataTable></" +"literal> actually get initialized? The <literal>Blog</literal> is retrieved " +"lazily—\"pulled\"—when needed, by a Seam component named " +"<literal>blog</literal>. This is the opposite flow of control to what is " +"used in traditional action-based web frameworks like Struts." msgstr "" #. Tag: programlisting @@ -4714,7 +5765,8 @@ " @Unwrap\n" " public Blog getBlog()\n" " {\n" -" return (Blog) entityManager.createQuery(\"select distinct b from Blog b left join fetch b.blogEntries\")\n" +" return (Blog) entityManager.createQuery(\"select distinct b from Blog " +"b left join fetch b.blogEntries\")\n" " .setHint(\"org.hibernate.cacheable\", true)\n" " .getSingleResult();\n" " }\n" @@ -4732,7 +5784,8 @@ " @Unwrap\n" " public Blog getBlog()\n" " {\n" -" return (Blog) entityManager.createQuery(\"select distinct b from Blog b left join fetch b.blogEntries\")\n" +" return (Blog) entityManager.createQuery(\"select distinct b from Blog " +"b left join fetch b.blogEntries\")\n" " .setHint(\"org.hibernate.cacheable\", true)\n" " .getSingleResult();\n" " }\n" @@ -4742,19 +5795,30 @@ #. Tag: para #: Tutorial.xml:1775 #, no-c-format -msgid "This component uses a <emphasis>seam-managed persistence context</emphasis>. Unlike the other examples we've seen, this persistence context is managed by Seam, instead of by the EJB3 container. The persistence context spans the entire web request, allowing us to avoid any exceptions that occur when accessing unfetched associations in the view." +msgid "" +"This component uses a <emphasis>seam-managed persistence context</emphasis>. " +"Unlike the other examples we've seen, this persistence context is managed by " +"Seam, instead of by the EJB3 container. The persistence context spans the " +"entire web request, allowing us to avoid any exceptions that occur when " +"accessing unfetched associations in the view." msgstr "" #. Tag: para #: Tutorial.xml:1782 #, no-c-format -msgid "The <literal>@Unwrap</literal> annotation tells Seam to provide the return value of the method—the <literal>Blog</literal>—instead of the actual <literal>BlogService</literal> component to clients. This is the Seam <emphasis>manager component pattern</emphasis>." +msgid "" +"The <literal>@Unwrap</literal> annotation tells Seam to provide the return " +"value of the method—the <literal>Blog</literal>—instead of the " +"actual <literal>BlogService</literal> component to clients. This is the Seam " +"<emphasis>manager component pattern</emphasis>." msgstr "" #. Tag: para #: Tutorial.xml:1792 #, no-c-format -msgid "This is good so far, but what about bookmarking the result of form submissions, such as a search results page?" +msgid "" +"This is good so far, but what about bookmarking the result of form " +"submissions, such as a search results page?" msgstr "" #. Tag: title @@ -4766,7 +5830,11 @@ #. Tag: para #: Tutorial.xml:1800 #, no-c-format -msgid "The blog example has a tiny form in the top right of each page that allows the user to search for blog entries. This is defined in a file, <literal>menu.xhtml</literal>, included by the facelets template, <literal>template.xhtml</literal>:" +msgid "" +"The blog example has a tiny form in the top right of each page that allows " +"the user to search for blog entries. This is defined in a file, " +"<literal>menu.xhtml</literal>, included by the facelets template, " +"<literal>template.xhtml</literal>:" msgstr "" #. Tag: programlisting @@ -4790,7 +5858,12 @@ #. Tag: para #: Tutorial.xml:1808 #, no-c-format -msgid "To implement a bookmarkable search results page, we need to perform a browser redirect after processing the search form submission. Because we used the JSF view id as the action outcome, Seam automatically redirects to the view id when the form is submitted. Alternatively, we could have defined a navigation rule like this:" +msgid "" +"To implement a bookmarkable search results page, we need to perform a " +"browser redirect after processing the search form submission. Because we " +"used the JSF view id as the action outcome, Seam automatically redirects to " +"the view id when the form is submitted. Alternatively, we could have defined " +"a navigation rule like this:" msgstr "" #. Tag: programlisting @@ -4840,7 +5913,13 @@ #. Tag: para #: Tutorial.xml:1821 #, no-c-format -msgid "But when we redirect, we need to include the values submitted with the form in the URL get a bookmarkable URL like <literal>http://localhost:8080/seam-blog/search/</literal>. JSF does not provide an easy way to do this, but Seam does. We use two Seam features to accomplish this: <emphasis>page parameters</emphasis> and <emphasis>URL rewriting</emphasis>. Both are defined in <literal>WEB-INF/pages.xml</literal>:" +msgid "" +"But when we redirect, we need to include the values submitted with the form " +"in the URL get a bookmarkable URL like <literal>http://localhost:8080/seam-" +"blog/search/</literal>. JSF does not provide an easy way to do this, but " +"Seam does. We use two Seam features to accomplish this: <emphasis>page " +"parameters</emphasis> and <emphasis>URL rewriting</emphasis>. Both are " +"defined in <literal>WEB-INF/pages.xml</literal>:" msgstr "" #. Tag: programlisting @@ -4852,7 +5931,8 @@ " <rewrite pattern=\"/search/{searchPattern}\"/> \n" " <rewrite pattern=\"/search\"/>\n" " \n" -" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/>\n" +" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/" +">\n" "\n" " </page>\n" " ...\n" @@ -4863,7 +5943,8 @@ " <rewrite pattern=\"/search/{searchPattern}\"/> \n" " <rewrite pattern=\"/search\"/>\n" " \n" -" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/>\n" +" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/" +">\n" "\n" " </page>\n" " ...\n" @@ -4872,19 +5953,41 @@ #. Tag: para #: Tutorial.xml:1833 #, no-c-format -msgid "The page parameter instructs Seam to link the request parameter named <literal>searchPattern</literal> to the value of <literal>#{searchService.searchPattern}</literal>, both whenever a request for the Search page comes in and whenever a link to the search page is generated. Seam takes responsibility for maintaining the link between URL state and application state, and you, the developer, don't have to worry about it." +msgid "" +"The page parameter instructs Seam to link the request parameter named " +"<literal>searchPattern</literal> to the value of <literal>#{searchService." +"searchPattern}</literal>, both whenever a request for the Search page comes " +"in and whenever a link to the search page is generated. Seam takes " +"responsibility for maintaining the link between URL state and application " +"state, and you, the developer, don't have to worry about it." msgstr "" #. Tag: para #: Tutorial.xml:1840 #, no-c-format -msgid "Without URL rewriting, the URL for a search on the term <literal>book</literal> would be <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal>. This is nice, but Seam can make the URL even simpler using a rewrite rule. The first rewrite rule, for the pattern <literal>/search/{searchPattern}</literal>, says that any time we have have a URL for search.xhtml with a searchPattern request parameter, we can fold that URL into the simpler URL. So,the URL we saw earlier, <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal> can be written instead as <literal>http://localhost:8080/seam-blog/search/book</literal>." +msgid "" +"Without URL rewriting, the URL for a search on the term <literal>book</" +"literal> would be <literal>http://localhost:8080/seam-blog/seam/search.xhtml?" +"searchPattern=book</literal>. This is nice, but Seam can make the URL even " +"simpler using a rewrite rule. The first rewrite rule, for the pattern " +"<literal>/search/{searchPattern}</literal>, says that any time we have have " +"a URL for search.xhtml with a searchPattern request parameter, we can fold " +"that URL into the simpler URL. So,the URL we saw earlier, <literal>http://" +"localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal> can " +"be written instead as <literal>http://localhost:8080/seam-blog/search/book</" +"literal>." msgstr "" #. Tag: para #: Tutorial.xml:1850 #, no-c-format -msgid "Just like with page parameters, URL rewriting is bi-directional. That means that Seam forwards requests for the simpler URL to the the right view, and it also automatically generates the simpler view for you. You never need to worry about constructing URLs. It's all handled transparently behind the scenes. The only requirement is that to use URL rewriting, the rewrite filter needs to be enabled in <literal>components.xml</literal>." +msgid "" +"Just like with page parameters, URL rewriting is bi-directional. That means " +"that Seam forwards requests for the simpler URL to the the right view, and " +"it also automatically generates the simpler view for you. You never need to " +"worry about constructing URLs. It's all handled transparently behind the " +"scenes. The only requirement is that to use URL rewriting, the rewrite " +"filter needs to be enabled in <literal>components.xml</literal>." msgstr "" #. Tag: programlisting @@ -4906,12 +6009,14 @@ "<![CDATA[<h:dataTable value=\"#{searchResults}\" var=\"blogEntry\">\n" " <h:column>\n" " <div>\n" -" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#{blogEntry.title}\">\n" +" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#" +"{blogEntry.title}\">\n" " <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n" " </s:link>\n" " posted on \n" " <h:outputText value=\"#{blogEntry.date}\">\n" -" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n" +" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog." +"locale}\" type=\"both\"/>\n" " </h:outputText>\n" " </div>\n" " </h:column>\n" @@ -4920,12 +6025,14 @@ "<![CDATA[<h:dataTable value=\"#{searchResults}\" var=\"blogEntry\">\n" " <h:column>\n" " <div>\n" -" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#{blogEntry.title}\">\n" +" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#" +"{blogEntry.title}\">\n" " <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n" " </s:link>\n" " posted on \n" " <h:outputText value=\"#{blogEntry.date}\">\n" -" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n" +" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog." +"locale}\" type=\"both\"/>\n" " </h:outputText>\n" " </div>\n" " </h:column>\n" @@ -4934,7 +6041,9 @@ #. Tag: para #: Tutorial.xml:1865 #, no-c-format -msgid "Which again uses \"pull\"-style MVC to retrieve the actual search results using Hibernate Search." +msgid "" +"Which again uses \"pull\"-style MVC to retrieve the actual search results " +"using Hibernate Search." msgstr "" #. Tag: programlisting @@ -4955,7 +6064,8 @@ " {\n" " if (searchPattern==null || \"\".equals(searchPattern) ) {\n" " searchPattern = null;\n" -" return entityManager.createQuery(\"select be from BlogEntry be order by date desc\").getResultList();\n" +" return entityManager.createQuery(\"select be from BlogEntry be " +"order by date desc\").getResultList();\n" " }\n" " else\n" " {\n" @@ -4963,7 +6073,8 @@ " boostPerField.put( \"title\", 4f );\n" " boostPerField.put( \"body\", 1f );\n" " String[] productFields = {\"title\", \"body\"};\n" -" QueryParser parser = new MultiFieldQueryParser(productFields, new StandardAnalyzer(), boostPerField);\n" +" QueryParser parser = new MultiFieldQueryParser(productFields, new " +"StandardAnalyzer(), boostPerField);\n" " parser.setAllowLeadingWildcard(true);\n" " org.apache.lucene.search.Query luceneQuery;\n" " try\n" @@ -4975,7 +6086,8 @@ " return null;\n" " }\n" "\n" -" return entityManager.createFullTextQuery(luceneQuery, BlogEntry.class)\n" +" return entityManager.createFullTextQuery(luceneQuery, BlogEntry." +"class)\n" " .setMaxResults(100)\n" " .getResultList();\n" " }\n" @@ -5008,7 +6120,8 @@ " {\n" " if (searchPattern==null || \"\".equals(searchPattern) ) {\n" " searchPattern = null;\n" -" return entityManager.createQuery(\"select be from BlogEntry be order by date desc\").getResultList();\n" +" return entityManager.createQuery(\"select be from BlogEntry be " +"order by date desc\").getResultList();\n" " }\n" " else\n" " {\n" @@ -5016,7 +6129,8 @@ " boostPerField.put( \"title\", 4f );\n" " boostPerField.put( \"body\", 1f );\n" " String[] productFields = {\"title\", \"body\"};\n" -" QueryParser parser = new MultiFieldQueryParser(productFields, new StandardAnalyzer(), boostPerField);\n" +" QueryParser parser = new MultiFieldQueryParser(productFields, new " +"StandardAnalyzer(), boostPerField);\n" " parser.setAllowLeadingWildcard(true);\n" " org.apache.lucene.search.Query luceneQuery;\n" " try\n" @@ -5028,7 +6142,8 @@ " return null;\n" " }\n" "\n" -" return entityManager.createFullTextQuery(luceneQuery, BlogEntry.class)\n" +" return entityManager.createFullTextQuery(luceneQuery, BlogEntry." +"class)\n" " .setMaxResults(100)\n" " .getResultList();\n" " }\n" @@ -5056,13 +6171,20 @@ #. Tag: para #: Tutorial.xml:1876 #, no-c-format -msgid "Very occasionally, it makes more sense to use push-style MVC for processing RESTful pages, and so Seam provides the notion of a <emphasis>page action</emphasis>. The Blog example uses a page action for the blog entry page, <literal>entry.xhtml</literal>. Note that this is a little bit contrived, it would have been easier to use pull-style MVC here as well." +msgid "" +"Very occasionally, it makes more sense to use push-style MVC for processing " +"RESTful pages, and so Seam provides the notion of a <emphasis>page action</" +"emphasis>. The Blog example uses a page action for the blog entry page, " +"<literal>entry.xhtml</literal>. Note that this is a little bit contrived, it " +"would have been easier to use pull-style MVC here as well." msgstr "" #. Tag: para #: Tutorial.xml:1881 #, no-c-format -msgid "The <literal>entryAction</literal> component works much like an action class in a traditional push-MVC action-oriented framework like Struts:" +msgid "" +"The <literal>entryAction</literal> component works much like an action class " +"in a traditional push-MVC action-oriented framework like Struts:" msgstr "" #. Tag: programlisting @@ -5180,13 +6302,23 @@ #. Tag: para #: Tutorial.xml:1892 #, no-c-format -msgid "Notice that the example is using page actions for post validation and the pageview counter. Also notice the use of a parameter in the page action method binding. This is not a standard feature of JSF EL, but Seam lets you use it, not just for page actions but also in JSF method bindings." +msgid "" +"Notice that the example is using page actions for post validation and the " +"pageview counter. Also notice the use of a parameter in the page action " +"method binding. This is not a standard feature of JSF EL, but Seam lets you " +"use it, not just for page actions but also in JSF method bindings." msgstr "" #. Tag: para #: Tutorial.xml:1897 #, no-c-format -msgid "When the <literal>entry.xhtml</literal> page is requested, Seam first binds the page parameter <literal>blogEntryId</literal> to the model. Keep in mind that because of the URL rewriting, the blogEntryId parameter name won't show up in the URL. Seam then runs the page action, which retrieves the needed data—the <literal>blogEntry</literal>—and places it in the Seam event context. Finally, the following is rendered:" +msgid "" +"When the <literal>entry.xhtml</literal> page is requested, Seam first binds " +"the page parameter <literal>blogEntryId</literal> to the model. Keep in mind " +"that because of the URL rewriting, the blogEntryId parameter name won't show " +"up in the URL. Seam then runs the page action, which retrieves the needed " +"data—the <literal>blogEntry</literal>—and places it in the Seam " +"event context. Finally, the following is rendered:" msgstr "" #. Tag: programlisting @@ -5201,7 +6333,8 @@ " <p>\n" " [Posted on \n" " <h:outputText value=\"#{blogEntry.date}\">\n" -" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n" +" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog." +"locale}\" type=\"both\"/>\n" " </h:outputText>]\n" " </p>\n" "</div>]]>" @@ -5214,7 +6347,8 @@ " <p>\n" " [Posted on \n" " <h:outputText value=\"#{blogEntry.date}\">\n" -" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n" +" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog." +"locale}\" type=\"both\"/>\n" " </h:outputText>]\n" " </p>\n" "</div>]]>" @@ -5222,7 +6356,11 @@ #. Tag: para #: Tutorial.xml:1907 #, no-c-format -msgid "If the blog entry is not found in the database, the <literal>EntryNotFoundException</literal> exception is thrown. We want this exception to result in a 404 error, not a 505, so we annotate the exception class:" +msgid "" +"If the blog entry is not found in the database, the " +"<literal>EntryNotFoundException</literal> exception is thrown. We want this " +"exception to result in a 404 error, not a 505, so we annotate the exception " +"class:" msgstr "" #. Tag: programlisting @@ -5252,7 +6390,9 @@ #. Tag: para #: Tutorial.xml:1914 #, no-c-format -msgid "An alternative implementation of the example does not use the parameter in the method binding:" +msgid "" +"An alternative implementation of the example does not use the parameter in " +"the method binding:" msgstr "" #. Tag: programlisting @@ -5327,6 +6467,10 @@ #. Tag: para #: Tutorial.xml:1924 #, no-c-format -msgid "The blog demo also demonstrates very simple password authentication, posting to the blog, page fragment caching and atom feed generation." -msgstr "La demo del blog mostra anche una semplice autenticazione di password, un invio di un post al blog, un esempio di caching frammentato della pagina e la generazione di atom feed." - +msgid "" +"The blog demo also demonstrates very simple password authentication, posting " +"to the blog, page fragment caching and atom feed generation." +msgstr "" +"La demo del blog mostra anche una semplice autenticazione di password, un " +"invio di un post al blog, un esempio di caching frammentato della pagina e " +"la generazione di atom feed." Added: trunk/doc/Seam_Reference_Guide/ja-JP/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ja-JP/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/ja-JP/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language ja-JP translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/ja-JP/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ja-JP/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/ja-JP/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/kn-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/kn-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/kn-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language kn-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/kn-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/kn-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/kn-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/ko-KR/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ko-KR/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/ko-KR/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language ko-KR translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/ko-KR/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ko-KR/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/ko-KR/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/ml-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ml-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/ml-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language ml-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/ml-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ml-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/ml-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/mr-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/mr-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/mr-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language mr-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/mr-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/mr-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/mr-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/or-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/or-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/or-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language or-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/or-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/or-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/or-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/pa-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/pa-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/pa-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language pa-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/pa-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/pa-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pa-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Modified: trunk/doc/Seam_Reference_Guide/pot/Annotations.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Annotations.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Annotations.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Author_Group.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Author_Group.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Author_Group.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Book_Info.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Book_Info.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Book_Info.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Cache.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Cache.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Cache.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Components.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Components.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Components.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Concepts.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Concepts.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Concepts.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Configuration.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Configuration.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Configuration.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Controls.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Controls.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Controls.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Conversations.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Conversations.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Conversations.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Dependencies.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Dependencies.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Dependencies.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Drools.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Drools.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Drools.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Elenhancements.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Elenhancements.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Elenhancements.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Events.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Events.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Events.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Excel.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Excel.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Excel.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Feedback.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Feedback.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Feedback.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Framework.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Framework.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Framework.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Gettingstarted.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Gettingstarted.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Gettingstarted.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Glassfish.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Glassfish.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Glassfish.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Groovy.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Groovy.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Groovy.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Gwt.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Gwt.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Gwt.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Hsearch.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Hsearch.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Hsearch.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/I18n.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/I18n.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/I18n.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Itext.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Itext.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Itext.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Jbpm.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Jbpm.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Jbpm.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Jms.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Jms.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Jms.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Mail.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Mail.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Mail.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Added: trunk/doc/Seam_Reference_Guide/pot/Performance.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Performance.pot (rev 0) +++ trunk/doc/Seam_Reference_Guide/pot/Performance.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,96 @@ +# SOME DESCRIPTIVE TITLE. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: application/x-xml2pot; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/pot/Persistence.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Persistence.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Persistence.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Preface.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Preface.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Preface.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Remoting.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Remoting.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Remoting.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Revision_History.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Revision_History.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Revision_History.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Rss.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Rss.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Rss.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Security.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Security.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Security.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Spring.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Spring.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Spring.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Testing.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Testing.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Testing.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Text.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Text.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Text.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Tools.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Tools.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Tools.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Tutorial.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Tutorial.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Tutorial.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" @@ -1444,7 +1444,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Modified: trunk/doc/Seam_Reference_Guide/pot/Validation.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Validation.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Validation.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Weblogic.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Weblogic.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Weblogic.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Webservices.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Webservices.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Webservices.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Websphere.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Websphere.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Websphere.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Wicket.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Wicket.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Wicket.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/Xml.pot =================================================================== --- trunk/doc/Seam_Reference_Guide/pot/Xml.pot 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pot/Xml.pot 2008-12-13 18:38:38 UTC (rev 9770) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-05 00:07+0000\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: trunk/doc/Seam_Reference_Guide/pot/messages.mo =================================================================== (Binary files differ) Added: trunk/doc/Seam_Reference_Guide/pt-BR/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/pt-BR/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/pt-BR/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language pt-BR translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/pt-BR/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/pt-BR/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/pt-BR/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/ru-RU/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ru-RU/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/ru-RU/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language ru-RU translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/ru-RU/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ru-RU/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/ru-RU/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/si-LK/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/si-LK/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/si-LK/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language si-LK translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/si-LK/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/si-LK/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/si-LK/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/sl-SL/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/sl-SL/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/sl-SL/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language sl-SL translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/sl-SL/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/sl-SL/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/sl-SL/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-21 00:37+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/ta-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ta-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/ta-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language ta-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/ta-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/ta-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/ta-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/te-IN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/te-IN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/te-IN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language te-IN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/te-IN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/te-IN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/te-IN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/zh-CN/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/zh-CN/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/zh-CN/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language zh-CN translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/zh-CN/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/zh-CN/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/zh-CN/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>." Added: trunk/doc/Seam_Reference_Guide/zh-TW/Performance.po =================================================================== --- trunk/doc/Seam_Reference_Guide/zh-TW/Performance.po (rev 0) +++ trunk/doc/Seam_Reference_Guide/zh-TW/Performance.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -0,0 +1,95 @@ +# Language zh-TW translations for Seam_Reference_Guide package. +# Automatically generated, 2008. +# +msgid "" +msgstr "" +"Project-Id-Version: Seam_Reference_Guide \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2008-12-13 18:12+0000\n" +"PO-Revision-Date: 2008-12-13 17:58+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: Performance.xml:5 +#, no-c-format +msgid "Performance Tuning" +msgstr "" + +#. Tag: para +#: Performance.xml:7 +#, no-c-format +msgid "" +"This chapter is an attempt to document in one place all the tips for getting " +"the best performance from your Seam application." +msgstr "" + +#. Tag: title +#: Performance.xml:13 +#, no-c-format +msgid "Bypassing Interceptors" +msgstr "" + +#. Tag: para +#: Performance.xml:15 +#, no-c-format +msgid "" +"For repetitive value bindings such as those found in a JSF dataTable or " +"other iterative control (like <literal>ui:repeat</literal>), the full " +"interceptor stack will be invoked for every invocation of the referenced " +"Seam component. The effect of this can result in a substantial performance " +"hit, especially if the component is accessed many times. A significant " +"performance gain can be achieved by disabling the interceptor stack for the " +"Seam component being invoked. To disable interceptors for the component, add " +"the <literal>@BypassInterceptors</literal> annotation to the component class." +msgstr "" + +#. Tag: para +#: Performance.xml:25 +#, no-c-format +msgid "" +"It is very important to be aware of the implications of disabling " +"interceptors for a Seam component. Features such as bijection, annotated " +"security restrictions, synchronization and others are unavailable for a " +"component marked with <literal>@BypassInterceptors</literal>. While in most " +"cases it is possible to compensate for the loss of these features (e.g. " +"instead of injecting a component using <literal>@In</literal>, you can use " +"<literal>Component.getInstance()</literal> instead) it is important to be " +"aware of the consequences." +msgstr "" + +#. Tag: para +#: Performance.xml:35 +#, no-c-format +msgid "" +"The following code listing demonstrates a Seam component with its " +"interceptors disabled:" +msgstr "" + +#. Tag: programlisting +#: Performance.xml:39 +#, no-c-format +msgid "" +"<![CDATA[@Name(\"foo\")\n" +"@Scope(EVENT)\n" +"@BypassInterceptors\n" +"public class Foo\n" +"{\n" +" public String getRowActions()\n" +" {\n" +" // Role-based security check performed inline instead of using " +"@Restrict or other security annotation\n" +" Identity.instance().checkRole(\"user\");\n" +" \n" +" // Inline code to lookup component instead of using @In\n" +" Bar bar = (Bar) Component.getInstance(\"bar\");\n" +" \n" +" String actions; \n" +" // some code here that does something \n" +" return actions;\n" +" }\n" +"}]]>" +msgstr "" Modified: trunk/doc/Seam_Reference_Guide/zh-TW/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/zh-TW/Tutorial.po 2008-12-13 18:09:24 UTC (rev 9769) +++ trunk/doc/Seam_Reference_Guide/zh-TW/Tutorial.po 2008-12-13 18:38:38 UTC (rev 9770) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2008-12-04 00:59+0000\n" +"POT-Creation-Date: 2008-12-13 17:58+0000\n" "PO-Revision-Date: 2008-04-04 01:24+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -1443,7 +1443,7 @@ #, no-c-format msgid "" "The <literal>@Out</literal> annotation then exposes the selected value " -"directly to the page. So ever time a row of the clickable list is selected, " +"directly to the page. So every time a row of the clickable list is selected, " "the <literal>Message</literal> is injected to the attribute of the stateful " "bean, and the subsequently <emphasis>outjected</emphasis> to the event " "context variable named <literal>message</literal>."

15 years, 9 months

1
0
0 / 0

Seam SVN: r9769 - trunk/doc/Seam_Reference_Guide/en-US.

by seam-commits＠lists.jboss.org

Author: pete.muir(a)jboss.org Date: 2008-12-13 13:09:24 -0500 (Sat, 13 Dec 2008) New Revision: 9769 Modified: trunk/doc/Seam_Reference_Guide/en-US/Performance.xml Log: native eol style Modified: trunk/doc/Seam_Reference_Guide/en-US/Performance.xml =================================================================== --- trunk/doc/Seam_Reference_Guide/en-US/Performance.xml 2008-12-13 15:31:24 UTC (rev 9768) +++ trunk/doc/Seam_Reference_Guide/en-US/Performance.xml 2008-12-13 18:09:24 UTC (rev 9769) @@ -1,63 +1,63 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> - -<chapter id="performance"> - <title>Performance Tuning</title> - - <para> - This chapter is an attempt to document in one place all the tips for getting the best performance from - your Seam application. - </para> - - <section> - <title>Bypassing Interceptors</title> - - <para> - For repetitive value bindings such as those found in a JSF dataTable or other iterative control - (like <literal>ui:repeat</literal>), the full interceptor stack will be invoked for every invocation of - the referenced Seam component. The effect of this can result in a substantial performance hit, especially - if the component is accessed many times. A significant performance gain can be achieved by disabling the - interceptor stack for the Seam component being invoked. To disable interceptors for the component, add the - <literal>@BypassInterceptors</literal> annotation to the component class. - </para> - - <warning> - <para> - It is very important to be aware of the implications of disabling interceptors for a Seam component. - Features such as bijection, annotated security restrictions, synchronization and others are - unavailable for a component marked with <literal>@BypassInterceptors</literal>. While in most cases - it is possible to compensate for the loss of these features (e.g. instead of injecting a component - using <literal>@In</literal>, you can use <literal>Component.getInstance()</literal> instead) it is - important to be aware of the consequences. - </para> - </warning> - - <para> - The following code listing demonstrates a Seam component with its interceptors disabled: - </para> - - <programlisting><![CDATA[@Name("foo") -@Scope(EVENT) -@BypassInterceptors -public class Foo -{ - public String getRowActions() - { - // Role-based security check performed inline instead of using @Restrict or other security annotation - Identity.instance().checkRole("user"); - - // Inline code to lookup component instead of using @In - Bar bar = (Bar) Component.getInstance("bar"); - - String actions; - // some code here that does something - return actions; - } -}]]></programlisting> - - - - </section> - - +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd"> + +<chapter id="performance"> + <title>Performance Tuning</title> + + <para> + This chapter is an attempt to document in one place all the tips for getting the best performance from + your Seam application. + </para> + + <section> + <title>Bypassing Interceptors</title> + + <para> + For repetitive value bindings such as those found in a JSF dataTable or other iterative control + (like <literal>ui:repeat</literal>), the full interceptor stack will be invoked for every invocation of + the referenced Seam component. The effect of this can result in a substantial performance hit, especially + if the component is accessed many times. A significant performance gain can be achieved by disabling the + interceptor stack for the Seam component being invoked. To disable interceptors for the component, add the + <literal>@BypassInterceptors</literal> annotation to the component class. + </para> + + <warning> + <para> + It is very important to be aware of the implications of disabling interceptors for a Seam component. + Features such as bijection, annotated security restrictions, synchronization and others are + unavailable for a component marked with <literal>@BypassInterceptors</literal>. While in most cases + it is possible to compensate for the loss of these features (e.g. instead of injecting a component + using <literal>@In</literal>, you can use <literal>Component.getInstance()</literal> instead) it is + important to be aware of the consequences. + </para> + </warning> + + <para> + The following code listing demonstrates a Seam component with its interceptors disabled: + </para> + + <programlisting><![CDATA[@Name("foo") +@Scope(EVENT) +@BypassInterceptors +public class Foo +{ + public String getRowActions() + { + // Role-based security check performed inline instead of using @Restrict or other security annotation + Identity.instance().checkRole("user"); + + // Inline code to lookup component instead of using @In + Bar bar = (Bar) Component.getInstance("bar"); + + String actions; + // some code here that does something + return actions; + } +}]]></programlisting> + + + + </section> + + </chapter> \ No newline at end of file Property changes on: trunk/doc/Seam_Reference_Guide/en-US/Performance.xml ___________________________________________________________________ Name: svn:eol-style + native

15 years, 9 months

1
0
0 / 0

Seam SVN: r9768 - trunk/doc/Seam_Reference_Guide/it-IT.

by seam-commits＠lists.jboss.org

Author: nico.ben Date: 2008-12-13 10:31:24 -0500 (Sat, 13 Dec 2008) New Revision: 9768 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po trunk/doc/Seam_Reference_Guide/it-IT/Validation.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 13:28:03 UTC (rev 9767) +++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 15:31:24 UTC (rev 9768) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-12-04 00:59+0000\n" -"PO-Revision-Date: 2008-12-13 14:25+0100\n" +"PO-Revision-Date: 2008-12-13 15:49+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -35,7 +35,7 @@ #: Tutorial.xml:15 #, no-c-format msgid "Each example has the same directory structure:" -msgstr "Ciascun esempi ha la stessa struttura di directory:" +msgstr "Ciascun esempio ha la medesima struttura di directory:" #. Tag: para #: Tutorial.xml:19 @@ -334,7 +334,7 @@ #: Tutorial.xml:198 #, no-c-format msgid "An empty constructor is both required by both the EJB specification and by Seam." -msgstr "" +msgstr "Un costruttore vuoto è richiesto sia dalla specifica EJB sia da Seam." #. Tag: para #: Tutorial.xml:202 @@ -370,7 +370,7 @@ #: Tutorial.xml:226 #, no-c-format msgid "The stateless session bean class: <literal>RegisterAction.java</literal>" -msgstr "" +msgstr "Classe del bean di sessione stateless: <literal>RegisterAction.java</literal>" #. Tag: para #: Tutorial.xml:228 @@ -1895,7 +1895,7 @@ #: Tutorial.xml:799 #, no-c-format msgid "The JSP itself is trivial:" -msgstr "" +msgstr "Lo stesso JSP è banale:" #. Tag: title #: Tutorial.xml:802 @@ -1949,7 +1949,7 @@ #: Tutorial.xml:807 #, no-c-format msgid "The second JavaBean is responsible for starting business process instances, and ending tasks." -msgstr "" +msgstr "Il secondo JavaBean è responsabile per l'avvio delle istanze del processo di business e della fine dei task." #. Tag: title #: Tutorial.xml:811 @@ -2804,7 +2804,7 @@ #: Tutorial.xml:1030 #, no-c-format msgid "Finally, we'll look at the actual application code:" -msgstr "" +msgstr "Infine diamo un'occhiata al codice dell'applicazione:" #. Tag: title #: Tutorial.xml:1033 @@ -4817,7 +4817,7 @@ #: Tutorial.xml:1816 #, no-c-format msgid "Then the form would have looked like this:" -msgstr "" +msgstr "Quindi la form avrebbe dovuto essere così:" #. Tag: programlisting #: Tutorial.xml:1818 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Validation.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-13 13:28:03 UTC (rev 9767) +++ trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-13 15:31:24 UTC (rev 9768) @@ -6,8 +6,8 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-10-14 11:39+0000\n" -"PO-Revision-Date: 2008-04-04 01:24+0000\n" -"Last-Translator: Automatically generated\n" +"PO-Revision-Date: 2008-12-13 16:30+0100\n" +"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,13 +17,13 @@ #: Validation.xml:2 #, no-c-format msgid "JSF form validation in Seam" -msgstr "" +msgstr "Validazione delle form JSF in Seam" #. Tag: para #: Validation.xml:3 #, no-c-format msgid "In plain JSF, validation is defined in the view:" -msgstr "" +msgstr "Nel puro JSF la validazione è definita nella vista:" #. Tag: programlisting #: Validation.xml:7 @@ -49,24 +49,39 @@ " <h:commandButton/>\n" "</h:form>]]>" msgstr "" +"<![CDATA[<h:form>\n" +" <h:messages/>\n" +"\n" +" <div>\n" +" Country:\n" +" <h:inputText value=\"#{location.country}\" required=\"true\">\n" +" <my:validateCountry/>\n" +" </h:inputText>\n" +" </div>\n" +" \n" +" <div>\n" +" Zip code:\n" +" <h:inputText value=\"#{location.zip}\" required=\"true\">\n" +" <my:validateZip/>\n" +" </h:inputText>\n" +" </div>\n" +"\n" +" <h:commandButton/>\n" +"</h:form>]]>" +# DRY = Don't Repeat Yourself ??? Intende questo? +# Controllare "..and exist all the way down to the database schema definition." #. Tag: para #: Validation.xml:9 #, no-c-format -msgid "" -"In practice, this approach usually violates DRY, since most \"validation\" " -"actually enforces constraints that are part of the data model, and exist all " -"the way down to the database schema definition. Seam provides support for " -"model-based constraints defined using Hibernate Validator." -msgstr "" +msgid "In practice, this approach usually violates DRY, since most \"validation\" actually enforces constraints that are part of the data model, and exist all the way down to the database schema definition. Seam provides support for model-based constraints defined using Hibernate Validator." +msgstr "In pratica quest'approccio di norma viola il principio DRY (Don't Repeat Yourself = Non ripeterti), poiché la maggior parte della \"validazione\" forza i vincoli che sono parte del modello di dati, e che esistono lungo tutta la definizione dello schema di database. Seam fornisce supporto ai vincoli del modello definiti, utilizzando Hibernate Validator." #. Tag: para #: Validation.xml:17 #, no-c-format -msgid "" -"Let's start by defining our constraints, on our <literal>Location</literal> " -"class:" -msgstr "" +msgid "Let's start by defining our constraints, on our <literal>Location</literal> class:" +msgstr "Iniziamo definendo i vincoli sulla classe <literal>Location</literal>: " #. Tag: programlisting #: Validation.xml:22 @@ -88,13 +103,26 @@ " public void setZip(String z) { zip = z; }\n" "}]]>" msgstr "" +"<![CDATA[public class Location {\n" +" private String country;\n" +" private String zip;\n" +" \n" +" @NotNull\n" +" @Length(max=30)\n" +" public String getCountry() { return country; }\n" +" public void setCountry(String c) { country = c; }\n" +"\n" +" @NotNull\n" +" @Length(max=6)\n" +" @Pattern(\"^\\d*$\")\n" +" public String getZip() { return zip; }\n" +" public void setZip(String z) { zip = z; }\n" +"}]]>" #. Tag: para #: Validation.xml:24 #, no-c-format -msgid "" -"Well, that's a decent first cut, but in practice it might be more elegant to " -"use custom constraints instead of the ones built into Hibernate Validator:" +msgid "Well, that's a decent first cut, but in practice it might be more elegant to use custom constraints instead of the ones built into Hibernate Validator:" msgstr "" #. Tag: programlisting @@ -116,14 +144,25 @@ " public void setZip(String z) { zip = z; }\n" "}]]>" msgstr "" +"<![CDATA[public class Location {\n" +" private String country;\n" +" private String zip;\n" +" \n" +" @NotNull\n" +" @Country\n" +" public String getCountry() { return country; }\n" +" public void setCountry(String c) { country = c; }\n" +"\n" +" @NotNull\n" +" @ZipCode\n" +" public String getZip() { return zip; }\n" +" public void setZip(String z) { zip = z; }\n" +"}]]>" #. Tag: para #: Validation.xml:32 #, no-c-format -msgid "" -"Whichever route we take, we no longer need to specify the type of validation " -"to be used in the JSF page. Instead, we can use <literal><s:validate></" -"literal> to validate against the constraint defined on the model object." +msgid "Whichever route we take, we no longer need to specify the type of validation to be used in the JSF page. Instead, we can use <literal><s:validate></literal> to validate against the constraint defined on the model object." msgstr "" #. Tag: programlisting @@ -151,33 +190,44 @@ "\n" "</h:form>]]>" msgstr "" +"<![CDATA[<h:form>\n" +" <h:messages/>\n" +"\n" +" <div>\n" +" Country:\n" +" <h:inputText value=\"#{location.country}\" required=\"true\">\n" +" <s:validate/>\n" +" </h:inputText>\n" +" </div>\n" +" \n" +" <div>\n" +" Zip code:\n" +" <h:inputText value=\"#{location.zip}\" required=\"true\">\n" +" <s:validate/>\n" +" </h:inputText>\n" +" </div>\n" +" \n" +" <h:commandButton/>\n" +"\n" +"</h:form>]]>" #. Tag: para #: Validation.xml:41 #, no-c-format -msgid "" -"<emphasis>Note:</emphasis> specifying <literal>@NotNull</literal> on the " -"model does <emphasis>not</emphasis> eliminate the requirement for " -"<literal>required=\"true\"</literal> to appear on the control! This is due " -"to a limitation of the JSF validation architecture." +msgid "<emphasis>Note:</emphasis> specifying <literal>@NotNull</literal> on the model does <emphasis>not</emphasis> eliminate the requirement for <literal>required=\"true\"</literal> to appear on the control! This is due to a limitation of the JSF validation architecture." msgstr "" #. Tag: para #: Validation.xml:48 #, no-c-format -msgid "" -"This approach <emphasis>defines</emphasis> constraints on the model, and " -"<emphasis>presents</emphasis> constraint violations in the view—a " -"significantly better design." +msgid "This approach <emphasis>defines</emphasis> constraints on the model, and <emphasis>presents</emphasis> constraint violations in the view—a significantly better design." msgstr "" #. Tag: para #: Validation.xml:54 #, no-c-format -msgid "" -"However, it is not much less verbose than what we started with, so let's try " -"<literal><s:validateAll></literal>:" -msgstr "" +msgid "However, it is not much less verbose than what we started with, so let's try <literal><s:validateAll></literal>:" +msgstr "Comunque non è molto meno corto di quanto lo era all'inizio, quindi proviamo <literal><s:validateAll></literal>:" #. Tag: programlisting #: Validation.xml:59 @@ -205,72 +255,74 @@ "\n" "</h:form>]]>" msgstr "" +"<![CDATA[<h:form>\n" +" \n" +" <h:messages/>\n" +"\n" +" <s:validateAll>\n" +"\n" +" <div>\n" +" Country:\n" +" <h:inputText value=\"#{location.country}\" required=\"true\"/>\n" +" </div>\n" +"\n" +" <div>\n" +" Zip code:\n" +" <h:inputText value=\"#{location.zip}\" required=\"true\"/>\n" +" </div>\n" +"\n" +" <h:commandButton/>\n" +"\n" +" </s:validateAll>\n" +"\n" +"</h:form>]]>" #. Tag: para #: Validation.xml:61 #, no-c-format -msgid "" -"This tag simply adds an <literal><s:validate></literal> to every input " -"in the form. For a large form, it can save a lot of typing!" -msgstr "" +msgid "This tag simply adds an <literal><s:validate></literal> to every input in the form. For a large form, it can save a lot of typing!" +msgstr "Questo tag semplicemente aggiunge un <literal><s:validate></literal> ad ogni input nella form. Per form grandi questo fa risparmiare molto!" #. Tag: para #: Validation.xml:67 #, no-c-format -msgid "" -"Now we need to do something about displaying feedback to the user when " -"validation fails. Currently we are displaying all messages at the top of the " -"form. In order for the user to correlate the message with an input, you need " -"to define a label using the standard <literal>label</literal> attribute on " -"the input component." +msgid "Now we need to do something about displaying feedback to the user when validation fails. Currently we are displaying all messages at the top of the form. In order for the user to correlate the message with an input, you need to define a label using the standard <literal>label</literal> attribute on the input component." msgstr "" #. Tag: programlisting #: Validation.xml:73 #, no-c-format msgid "" -"<![CDATA[<h:inputText value=\"#{location.zip}\" required=\"true\" label=" -"\"Zip:\">\n" +"<![CDATA[<h:inputText value=\"#{location.zip}\" required=\"true\" label=\"Zip:\">\n" " <s:validate/>\n" "</h:inputText>]]>" msgstr "" +"<![CDATA[<h:inputText value=\"#{location.zip}\" required=\"true\" label=\"Zip:\">\n" +" <s:validate/>\n" +"</h:inputText>]]>" #. Tag: para #: Validation.xml:75 #, no-c-format -msgid "" -"You can then inject this value into the message string using the placeholder " -"{0} (the first and only parameter passed to a JSF message for a Hiberate " -"Validator restriction). See the internationalization section for more " -"information regarding where to define these messages." +msgid "You can then inject this value into the message string using the placeholder {0} (the first and only parameter passed to a JSF message for a Hiberate Validator restriction). See the internationalization section for more information regarding where to define these messages." msgstr "" #. Tag: programlisting #: Validation.xml:83 #, no-c-format msgid "validator.length={0} length must be between {min} and {max}" -msgstr "" +msgstr "validator.length={0} la lunghezza deve essere tra {min} e {max}" #. Tag: para #: Validation.xml:85 #, no-c-format -msgid "" -"What we would really like to do, though, is display the message next to the " -"field with the error (this is possible in plain JSF), highlight the field " -"and label (this is not possible) and, for good measure, display some image " -"next to the field (also not possible). We also want to display a little " -"colored asterisk next to the label for each required form field. Using this " -"approach, the identifying label is not necessary." +msgid "What we would really like to do, though, is display the message next to the field with the error (this is possible in plain JSF), highlight the field and label (this is not possible) and, for good measure, display some image next to the field (also not possible). We also want to display a little colored asterisk next to the label for each required form field. Using this approach, the identifying label is not necessary." msgstr "" #. Tag: para #: Validation.xml:95 #, no-c-format -msgid "" -"That's quite a lot of functionality we need for each field of our form. We " -"wouldn't want to have to specify higlighting and the layout of the image, " -"message and input field for every field on the form. So, instead, we'll " -"specify the common layout in a facelets template:" +msgid "That's quite a lot of functionality we need for each field of our form. We wouldn't want to have to specify higlighting and the layout of the image, message and input field for every field on the form. So, instead, we'll specify the common layout in a facelets template:" msgstr "" #. Tag: programlisting @@ -287,13 +339,11 @@ " \n" " <s:label styleClass=\"#{invalid?'error':''}\">\n" " <ui:insert name=\"label\"/>\n" -" <s:span styleClass=\"required\" rendered=\"#{required}\">*</s:" -"span>\n" +" <s:span styleClass=\"required\" rendered=\"#{required}\">*</s:span>\n" " </s:label>\n" " \n" " <span class=\"#{invalid?'error':''}\">\n" -" <h:graphicImage value=\"/img/error.gif\" rendered=\"#{invalid}\"/" -">\n" +" <h:graphicImage value=\"/img/error.gif\" rendered=\"#{invalid}\"/>\n" " <s:validateAll>\n" " <ui:insert/>\n" " </s:validateAll>\n" @@ -305,13 +355,36 @@ " \n" "</ui:composition>]]>" msgstr "" +"<![CDATA[<ui:composition xmlns=\"http://www.w3.org/1999/xhtml\"\n" +" xmlns:ui=\"http://java.sun.com/jsf/facelets\"\n" +" xmlns:h=\"http://java.sun.com/jsf/html\"\n" +" xmlns:f=\"http://java.sun.com/jsf/core\"\n" +" xmlns:s=\"http://jboss.com/products/seam/taglib\">\n" +" \n" +" <div>\n" +" \n" +" <s:label styleClass=\"#{invalid?'error':''}\">\n" +" <ui:insert name=\"label\"/>\n" +" <s:span styleClass=\"required\" rendered=\"#{required}\">*</s:span>\n" +" </s:label>\n" +" \n" +" <span class=\"#{invalid?'error':''}\">\n" +" <h:graphicImage value=\"/img/error.gif\" rendered=\"#{invalid}\"/>\n" +" <s:validateAll>\n" +" <ui:insert/>\n" +" </s:validateAll>\n" +" </span>\n" +" \n" +" <s:message styleClass=\"error\"/>\n" +" \n" +" </div>\n" +" \n" +"</ui:composition>]]>" #. Tag: para #: Validation.xml:105 #, no-c-format -msgid "" -"We can include this template for each of our form fields using <literal><" -"s:decorate></literal>." +msgid "We can include this template for each of our form fields using <literal><s:decorate></literal>." msgstr "" #. Tag: programlisting @@ -336,14 +409,29 @@ "\n" "</h:form>]]>" msgstr "" +"<![CDATA[<h:form>\n" +"\n" +" <h:messages globalOnly=\"true\"/>\n" +"\n" +" <s:decorate template=\"edit.xhtml\">\n" +" <ui:define name=\"label\">Country:</ui:define>\n" +" <h:inputText value=\"#{location.country}\" required=\"true\"/>\n" +" </s:decorate>\n" +" \n" +" <s:decorate template=\"edit.xhtml\">\n" +" <ui:define name=\"label\">Zip code:</ui:define>\n" +" <h:inputText value=\"#{location.zip}\" required=\"true\"/>\n" +" </s:decorate>\n" +"\n" +" <h:commandButton/>\n" +"\n" +"</h:form>]]>" #. Tag: para #: Validation.xml:112 #, no-c-format -msgid "" -"Finally, we can use RichFaces Ajax to display validation messages as the " -"user is navigating around the form:" -msgstr "" +msgid "Finally, we can use RichFaces Ajax to display validation messages as the user is navigating around the form:" +msgstr "Infine è possibile utilizzare RichFaces Ajax per mostrare i messaggi di validazione mentre l'utente naviga nella form:" #. Tag: programlisting #: Validation.xml:117 @@ -356,16 +444,14 @@ " <s:decorate id=\"countryDecoration\" template=\"edit.xhtml\">\n" " <ui:define name=\"label\">Country:</ui:define>\n" " <h:inputText value=\"#{location.country}\" required=\"true\">\n" -" <a:support event=\"onblur\" reRender=\"countryDecoration\" " -"bypassUpdates=\"true\"/>\n" +" <a:support event=\"onblur\" reRender=\"countryDecoration\" bypassUpdates=\"true\"/>\n" " </h:inputText>\n" " </s:decorate>\n" " \n" " <s:decorate id=\"zipDecoration\" template=\"edit.xhtml\">\n" " <ui:define name=\"label\">Zip code:</ui:define>\n" " <h:inputText value=\"#{location.zip}\" required=\"true\">\n" -" <a:support event=\"onblur\" reRender=\"zipDecoration\" " -"bypassUpdates=\"true\"/>\n" +" <a:support event=\"onblur\" reRender=\"zipDecoration\" bypassUpdates=\"true\"/>\n" " </h:inputText>\n" " </s:decorate>\n" "\n" @@ -373,16 +459,32 @@ "\n" "</h:form>]]>" msgstr "" +"<![CDATA[<h:form>\n" +"\n" +" <h:messages globalOnly=\"true\"/>\n" +"\n" +" <s:decorate id=\"countryDecoration\" template=\"edit.xhtml\">\n" +" <ui:define name=\"label\">Country:</ui:define>\n" +" <h:inputText value=\"#{location.country}\" required=\"true\">\n" +" <a:support event=\"onblur\" reRender=\"countryDecoration\" bypassUpdates=\"true\"/>\n" +" </h:inputText>\n" +" </s:decorate>\n" +" \n" +" <s:decorate id=\"zipDecoration\" template=\"edit.xhtml\">\n" +" <ui:define name=\"label\">Zip code:</ui:define>\n" +" <h:inputText value=\"#{location.zip}\" required=\"true\">\n" +" <a:support event=\"onblur\" reRender=\"zipDecoration\" bypassUpdates=\"true\"/>\n" +" </h:inputText>\n" +" </s:decorate>\n" +"\n" +" <h:commandButton/>\n" +"\n" +"</h:form>]]>" #. Tag: para #: Validation.xml:119 #, no-c-format -msgid "" -"It's better style to define explicit ids for important controls on the page, " -"especially if you want to do automated testing for the UI, using some " -"toolkit like Selenium. If you don't provide explicit ids, JSF will generate " -"them, but the generated values will change if you change anything on the " -"page." +msgid "It's better style to define explicit ids for important controls on the page, especially if you want to do automated testing for the UI, using some toolkit like Selenium. If you don't provide explicit ids, JSF will generate them, but the generated values will change if you change anything on the page." msgstr "" #. Tag: programlisting @@ -395,19 +497,15 @@ "\n" " <s:decorate id=\"countryDecoration\" template=\"edit.xhtml\">\n" " <ui:define name=\"label\">Country:</ui:define>\n" -" <h:inputText id=\"country\" value=\"#{location.country}\" required=" -"\"true\">\n" -" <a:support event=\"onblur\" reRender=\"countryDecoration\" " -"bypassUpdates=\"true\"/>\n" +" <h:inputText id=\"country\" value=\"#{location.country}\" required=\"true\">\n" +" <a:support event=\"onblur\" reRender=\"countryDecoration\" bypassUpdates=\"true\"/>\n" " </h:inputText>\n" " </s:decorate>\n" " \n" " <s:decorate id=\"zipDecoration\" template=\"edit.xhtml\">\n" " <ui:define name=\"label\">Zip code:</ui:define>\n" -" <h:inputText id=\"zip\" value=\"#{location.zip}\" required=\"true" -"\">\n" -" <a:support event=\"onblur\" reRender=\"zipDecoration\" " -"bypassUpdates=\"true\"/>\n" +" <h:inputText id=\"zip\" value=\"#{location.zip}\" required=\"true\">\n" +" <a:support event=\"onblur\" reRender=\"zipDecoration\" bypassUpdates=\"true\"/>\n" " </h:inputText>\n" " </s:decorate>\n" "\n" @@ -415,15 +513,32 @@ "\n" "</h:form>]]>" msgstr "" +"<![CDATA[<h:form id=\"form\">\n" +"\n" +" <h:messages globalOnly=\"true\"/>\n" +"\n" +" <s:decorate id=\"countryDecoration\" template=\"edit.xhtml\">\n" +" <ui:define name=\"label\">Country:</ui:define>\n" +" <h:inputText id=\"country\" value=\"#{location.country}\" required=\"true\">\n" +" <a:support event=\"onblur\" reRender=\"countryDecoration\" bypassUpdates=\"true\"/>\n" +" </h:inputText>\n" +" </s:decorate>\n" +" \n" +" <s:decorate id=\"zipDecoration\" template=\"edit.xhtml\">\n" +" <ui:define name=\"label\">Zip code:</ui:define>\n" +" <h:inputText id=\"zip\" value=\"#{location.zip}\" required=\"true\">\n" +" <a:support event=\"onblur\" reRender=\"zipDecoration\" bypassUpdates=\"true\"/>\n" +" </h:inputText>\n" +" </s:decorate>\n" +"\n" +" <h:commandButton/>\n" +"\n" +"</h:form>]]>" #. Tag: para #: Validation.xml:130 #, no-c-format -msgid "" -"And what if you want to specify a different message to be displayed when " -"validation fails? You can use the Seam message bundle (and all it's goodies " -"like el expressions inside the message, and per-view message bundles) with " -"the Hibernate Validator:" +msgid "And what if you want to specify a different message to be displayed when validation fails? You can use the Seam message bundle (and all it's goodies like el expressions inside the message, and per-view message bundles) with the Hibernate Validator:" msgstr "" #. Tag: programlisting @@ -443,10 +558,22 @@ " public void setZip(String z) { zip = z; }\n" "}]]>" msgstr "" +"<![CDATA[public class Location {\n" +" private String name;\n" +" private String zip;\n" +" \n" +" // Getters and setters for name\n" +"\n" +" @NotNull\n" +" @Length(max=6)\n" +" @ZipCode(message=\"#{messages['location.zipCode.invalid']}\")\n" +" public String getZip() { return zip; }\n" +" public void setZip(String z) { zip = z; }\n" +"}]]>" #. Tag: programlisting #: Validation.xml:139 #, no-c-format -msgid "" -"location.zipCode.invalid = The zip code is not valid for #{location.name}" -msgstr "" +msgid "location.zipCode.invalid = The zip code is not valid for #{location.name}" +msgstr "location.zipCode.invalid = Codice ZIP non valido per #{location.name}" +

15 years, 9 months

1
0
0 / 0

Seam SVN: r9767 - trunk/doc/Seam_Reference_Guide/it-IT.

by seam-commits＠lists.jboss.org

Author: nico.ben Date: 2008-12-13 08:28:03 -0500 (Sat, 13 Dec 2008) New Revision: 9767 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-12 19:17:06 UTC (rev 9766) +++ trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-13 13:28:03 UTC (rev 9767) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-04-04 01:24+0000\n" -"PO-Revision-Date: 2008-12-12 20:10+0100\n" +"PO-Revision-Date: 2008-12-13 14:10+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -79,7 +79,7 @@ #: Elenhancements.xml:33 #, no-c-format msgid "Just as in calls to method from Java, parameters are surrounded by parentheses, and separated by commas:" -msgstr "" +msgstr "Come nelle chiamate ai metodi in Java, i parametri sono racchiusi tra parentesi e separati da virgole:" #. Tag: programlisting #: Elenhancements.xml:38 @@ -91,7 +91,7 @@ #: Elenhancements.xml:40 #, no-c-format msgid "The parameters <literal>hotel</literal> and <literal>user</literal> will be evaluated as value expressions and passed to the <literal>bookHotel()</literal> method of the component." -msgstr "" +msgstr "I parametri <literal>hotel</literal> e <literal>user</literal> verranno valutati come espressioni di valore e passati al metodo <literal>bookHotel()</literal> del componente." #. Tag: para #: Elenhancements.xml:45 @@ -115,7 +115,7 @@ #: Elenhancements.xml:51 #, no-c-format msgid "It's important to fully understand how this extension to EL works. When the page is rendered, the parameter <emphasis>names</emphasis> are stored (for example, <literal>hotel.id</literal> and <literal>user.username</literal>), and evaluated (as value expressions) when the page is submitted. You can't pass objects as parameters!" -msgstr "" +msgstr "E' importante capire bene come funziona quest'estensione a EL. Quando la pagine viene generata, i <emphasis>nomi</emphasis> dei parametri vengono memorizzati (per esempio <literal>hotel.id</literal> e <literal>user.username</literal>) e valutati (come espressioni di valore) quando la pagina viene inviata. Non si possono passare oggetti come parametri!" #. Tag: para #: Elenhancements.xml:60 @@ -135,11 +135,12 @@ msgid "<![CDATA[<h:commandLink action=\"#{printer.println('Hello world!')}\" value=\"Hello\"/>]]>" msgstr "<![CDATA[<h:commandLink action=\"#{printer.println('Hello world!')}\" value=\"Hello\"/>]]>" +# backing bean = ? per ora metto BEAN e basta. #. Tag: para #: Elenhancements.xml:73 #, no-c-format msgid "Unified EL also supports value expressions, used to bind a field to a backing bean. Value expressions use JavaBean naming conventions and expect a getter/setter pair. Often JSF expects a value expression where only retrieval (get) is needed (e.g. the <literal>rendered</literal> attribute). Many objects, however, don't have appropriately named property accessors or require parameters." -msgstr "" +msgstr "EL unificato supporta anche le espressioni di valore, usate per associare un campo ad un bean. Le espressioni di valore utilizzano le convenzioni dei nomi di JavaBean e richiedono get e set. Spesso JSP si attende un'espressione di valore dove solo un recupero (get) è richiesto (es. l'attributo <literal>rendered</literal>). Molti oggetti, comunque, non hanno nominato in modo appropriato i metodi accessor alle proprietà o i parametri richiesti." #. Tag: para #: Elenhancements.xml:82 @@ -157,7 +158,7 @@ #: Elenhancements.xml:89 #, no-c-format msgid "You can access the size of a collection in a similar manner:" -msgstr "Puoi accedere alla dimensione di una collezioni in maniera analoga:" +msgstr "Puoi accedere alla dimensione di una collezione in maniera analoga:" #. Tag: programlisting #: Elenhancements.xml:93 @@ -199,13 +200,13 @@ #: Elenhancements.xml:118 #, no-c-format msgid "<emphasis>Incompatibility with JSP 2.1</emphasis> — JBoss EL can't currently be used with JSP 2.1 as the compiler rejects expressions with parameters in. So, if you want to use this extension with JSF 1.2, you will need to use Facelets. The extension works correctly with JSP 2.0." -msgstr "" +msgstr "<emphasis>Incompatibilità con JSP 2.1</emphasis> — JBoss EL non può attualmente essere utilizzato con JSP 2.1 poiché il compilatore rifiuta espressioni con paramentri al suo interno. Quindi per usare quest'estensione con JSF 1.2, si dovranno utilizzare Facelets. Quest'estensione funziona correttamente con JSP 2.0." #. Tag: para #: Elenhancements.xml:127 #, no-c-format msgid "<emphasis>Use inside iterative components</emphasis> — Components like <literal><c:forEach /></literal> and <literal><ui:repeat /></literal>iterate over a List or array, exposing each item in the list to nested components. This works great if you are selecting a row using a <literal><h:commandButton /></literal> or <literal><h:commandLink /></literal>:" -msgstr "" +msgstr "<emphasis>Utilizzo all'interno di componenti iterativi</emphasis> — Componenti quali <literal><c:forEach /></literal> e <literal><ui:repeat /></literal>iterano su una lista o un array, esponendo ogni item della lista ai componenti innestati. Questo funziona bene se si sta selezionando unriga con <literal><h:commandButton /></literal> o <literal><h:commandLink /></literal>:" #. Tag: programlisting #: Elenhancements.xml:136 @@ -241,13 +242,13 @@ #: Elenhancements.xml:138 #, no-c-format msgid "However if you want to use <literal><s:link /></literal> or <literal><s:button /></literal> you <emphasis>must</emphasis> expose the items as a <literal>DataModel</literal>, and use a <literal><dataTable /></literal> (or equivalent from a component set like <literal><rich:dataTable /></literal> ). Neither <literal><s:link /></literal> or <literal><s:button /></literal> submit the form (and therefore produce a bookmarkable link) so a \"magic\" parameter is needed to recreate the item when the action method is called. This magic parameter can only be added when a data table backed by a <literal>DataModel</literal> is used." -msgstr "" +msgstr "Comunque si voglia usare <literal><s:link /></literal> o <literal><s:button /></literal> si <emphasis>deve</emphasis> esporre gli item come <literal>DataModel</literal> e usare <literal><dataTable /></literal> (o equivalente da componente impostato come <literal><rich:dataTable /></literal> ). Né <literal><s:link /></literal> né <literal><s:button /></literal> eseguono il submit della form (e quindi producono un bookmarkable link) quindi un parametro \"magico\" serve per ricreare l'item quando l'action method viene chiamato. Questo parametro magico può essere aggiunto soltanto quando viene usata una data table con dietro un <literal>DataModel</literal>." #. Tag: para #: Elenhancements.xml:154 #, no-c-format msgid "<emphasis>Calling a <literal>MethodExpression</literal> from Java code</emphasis> — Normally, when a <literal>MethodExpression</literal> is created, the parameter types are passed in by JSF. In the case of a method binding, JSF assumes that there are no parameters to pass. With this extension, we can't know the parameter types until after the expression has been evaluated. This has two minor consequences:" -msgstr "" +msgstr "<emphasis>Chiamata di un <literal>MethodExpression</literal> da codice Java</emphasis> — normalmente quando una <literal>MethodExpression</literal> viene creata, i tipi di parametro sono passati tramite JSF. Nel caso di un binding di metodo, JSF presume che non ci siano parametri da passare. Con quest'estensione non è possibile sapere il tipo di parametro prima che l'espressione venga valutata. Ciò ha due conseguenze:" #. Tag: para #: Elenhancements.xml:167 @@ -259,13 +260,13 @@ #: Elenhancements.xml:175 #, no-c-format msgid "Ordinarily, it is safe to call <literal>methodExpression.getMethodInfo().getParamTypes()</literal> at any time. For an expression with parameters, you must first invoke the <literal>MethodExpression</literal> before calling <literal>getParamTypes()</literal>." -msgstr "" +msgstr "Solitamente è sicuro chiamare in ogni momento <literal>methodExpression.getMethodInfo().getParamTypes()</literal>. Per un'espressione con parametri occorre prima invocare il <literal>MethodExpression</literal> prima di chiamare <literal>getParamTypes()</literal>." #. Tag: para #: Elenhancements.xml:185 #, no-c-format msgid "Both of these cases are exceedingly rare and only apply when you want to invoke the <literal>MethodExpression</literal> by hand in Java code." -msgstr "" +msgstr "Entrambi questi casi sono estremamente rari e si applicano solo quando vuoi invocare <literal>MethodExpression</literal> manualmente nel codice Java." #. Tag: title #: Elenhancements.xml:196 @@ -301,13 +302,13 @@ #: Elenhancements.xml:214 #, no-c-format msgid "The subexpression is enclosed in braces. In this example, the expression <literal>d.name</literal> is evaluated for each department, using <literal>d</literal> as an alias to the department object. The result of this expression will be a list of String values." -msgstr "" +msgstr "La sotto-espressione è racchiusa da parentesi. In quest'esempio l'espressione <literal>d.name</literal> viene valutata per ogni dipartimento, usando <literal>d</literal> come alias per l'oggetto dipartimento. Il risultato di quest'espressione sarà una lista di valori Stringa." #. Tag: para #: Elenhancements.xml:221 #, no-c-format msgid "Any valid expression can be used in an expression, so it would be perfectly valid to write the following, assuming you had a use for the lengths of all the department names in a company:" -msgstr "" +msgstr "Qualsiasi espressione valida può essere usata in un'espressione, e quindi sarebbe perfettamente valido scrivere la seguente, assumendo che venga usata per le lunghezze di tutti i nomi di dipartimento in un'azienda:" #. Tag: programlisting #: Elenhancements.xml:227 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-12 19:17:06 UTC (rev 9766) +++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 13:28:03 UTC (rev 9767) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-12-04 00:59+0000\n" -"PO-Revision-Date: 2008-12-12 20:16+0100\n" +"PO-Revision-Date: 2008-12-13 14:25+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -35,25 +35,25 @@ #: Tutorial.xml:15 #, no-c-format msgid "Each example has the same directory structure:" -msgstr "" +msgstr "Ciascun esempi ha la stessa struttura di directory:" #. Tag: para #: Tutorial.xml:19 #, no-c-format msgid "The <filename>view</filename> directory contains view-related files such as web page templates, images and stylesheets." -msgstr "" +msgstr "La directory <filename>view</filename> contiene i file relativi alla vista come template di pagine web, immagini e fogli di stile." #. Tag: para #: Tutorial.xml:25 #, no-c-format msgid "The <filename>resources</filename> directory contains deployment descriptors and other configuration files." -msgstr "" +msgstr "La directory <filename>resources</filename> contiene i descrittori per il deploy ed altri file di configurazione." #. Tag: para #: Tutorial.xml:30 #, no-c-format msgid "The <filename>src</filename> directory contains the application source code." -msgstr "" +msgstr "La directory <filename>src</filename> contiene il codice sorgente dell'applicazione." #. Tag: para #: Tutorial.xml:35 @@ -65,7 +65,7 @@ #: Tutorial.xml:45 #, no-c-format msgid "Running the examples on JBoss AS" -msgstr "" +msgstr "Eseguire gli esempi in JBoss AS" #. Tag: para #: Tutorial.xml:47 @@ -89,7 +89,7 @@ #: Tutorial.xml:71 #, no-c-format msgid "Running the examples on Tomcat" -msgstr "" +msgstr "Eseguire gli esempi in Tomcat" #. Tag: para #: Tutorial.xml:73 @@ -119,7 +119,7 @@ #: Tutorial.xml:100 #, no-c-format msgid "Running the example tests" -msgstr "" +msgstr "Eseguire i test degli esempi" #. Tag: para #: Tutorial.xml:101 @@ -3171,25 +3171,25 @@ #: Tutorial.xml:1153 #, no-c-format msgid "Room reservation" -msgstr "" +msgstr "Prenotazione stanza" #. Tag: para #: Tutorial.xml:1156 #, no-c-format msgid "Reservation confirmation" -msgstr "" +msgstr "Conferma prenotazione" #. Tag: para #: Tutorial.xml:1159 #, no-c-format msgid "Existing reservation list" -msgstr "" +msgstr "Lista di prenotazioni esistenti" #. Tag: screeninfo #: Tutorial.xml:1164 #, no-c-format msgid "Booking example" -msgstr "" +msgstr "Esempio di prenotazione" #. Tag: para #: Tutorial.xml:1175 @@ -3213,7 +3213,7 @@ #: Tutorial.xml:1191 #, no-c-format msgid "Overview of the booking example" -msgstr "" +msgstr "Panoramica sull'esempio di prenotazione" #. Tag: para #: Tutorial.xml:1193 @@ -3261,7 +3261,7 @@ #: Tutorial.xml:1221 #, no-c-format msgid "<literal>RegisterAction</literal> registers a new system user." -msgstr "" +msgstr "<literal>RegisterAction</literal> registra un nuovo utente di sistema." #. Tag: para #: Tutorial.xml:1225 @@ -3273,7 +3273,7 @@ #: Tutorial.xml:1229 #, no-c-format msgid "<literal>Hotel</literal> is an entity bean that represent a hotel" -msgstr "" +msgstr "<literal>Hotel</literal> è un entity bean che rappresenta un hotel" #. Tag: para #: Tutorial.xml:1231 @@ -3291,7 +3291,7 @@ #: Tutorial.xml:1240 #, no-c-format msgid "Understanding Seam conversations" -msgstr "" +msgstr "Capire le conversazioni in Seam" #. Tag: para #: Tutorial.xml:1241 @@ -3958,7 +3958,7 @@ #: Tutorial.xml:1474 #, no-c-format msgid "The Seam Debug Page" -msgstr "" +msgstr "La pagina di debug di Seam" #. Tag: para #: Tutorial.xml:1476 @@ -3982,7 +3982,7 @@ #: Tutorial.xml:1503 #, no-c-format msgid "Nested conversations: extending the Hotel Booking example" -msgstr "" +msgstr "Conversazioni Annidate: estendere l'esempio di Prenotazione Hotel" #. Tag: para #: Tutorial.xml:1508 @@ -4018,7 +4018,7 @@ #: Tutorial.xml:1543 #, no-c-format msgid "Understanding Nested Conversations" -msgstr "" +msgstr "Capire le Conversazioni Annidate" #. Tag: para #: Tutorial.xml:1545 @@ -4627,7 +4627,7 @@ #: Tutorial.xml:1749 #, no-c-format msgid "Using \"pull\"-style MVC" -msgstr "" +msgstr "Utilizzo di MVC \"pull\"-style" #. Tag: para #: Tutorial.xml:1751 @@ -5323,9 +5323,10 @@ msgid "It is a matter of taste which implementation you prefer." msgstr "E' una questione di gusti su quale implementazione tu preferisca." +# fragment caching = ? #. Tag: para #: Tutorial.xml:1924 #, no-c-format msgid "The blog demo also demonstrates very simple password authentication, posting to the blog, page fragment caching and atom feed generation." -msgstr "" +msgstr "La demo del blog mostra anche una semplice autenticazione di password, un invio di un post al blog, un esempio di caching frammentato della pagina e la generazione di atom feed."

15 years, 9 months

1
0
0 / 0

Seam SVN: r9766 - trunk/doc/Seam_Reference_Guide/it-IT.

by seam-commits＠lists.jboss.org

Author: nico.ben Date: 2008-12-12 14:17:06 -0500 (Fri, 12 Dec 2008) New Revision: 9766 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po trunk/doc/Seam_Reference_Guide/it-IT/Preface.po trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-12 15:05:19 UTC (rev 9765) +++ trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-12 19:17:06 UTC (rev 9766) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-04-04 01:24+0000\n" -"PO-Revision-Date: 2008-12-12 15:38+0100\n" +"PO-Revision-Date: 2008-12-12 20:10+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -23,7 +23,7 @@ #: Elenhancements.xml:7 #, no-c-format msgid "Seam uses JBoss EL which provides an extension to the standard Unified Expression Language (EL). JBoss EL provides a number of enhancements that increase the expressiveness and power of EL expressions." -msgstr "" +msgstr "Seam utilizza JBoss EL, il quale fornisce un'estensione allo standard Unified Expression Language (EL). JBoss EL apporta un numero di miglioramenti che incrementa l'espressività e la potenza delle espressioni EL. " #. Tag: title #: Elenhancements.xml:14 @@ -35,7 +35,7 @@ #: Elenhancements.xml:16 #, no-c-format msgid "Standard EL does not allow you to use a method with user defined parameters — of course, JSF listener methods (e.g. a <literal>valueChangeListener</literal>) take parameters provided by JSF." -msgstr "" +msgstr "Lo standard EL non consente di utilizzare un metodo con parametri definiti dall'utente — sicuramente metodi JSF listener (es. <literal>valueChangeListener</literal>) prende i parametri forniti da JSF." #. Tag: para #: Elenhancements.xml:22 @@ -97,7 +97,7 @@ #: Elenhancements.xml:45 #, no-c-format msgid "Any value expression may be used as a parameter:" -msgstr "" +msgstr "Qualsiasi valore d'espressione può essere usato come parametro:" #. Tag: programlisting #: Elenhancements.xml:49 @@ -121,13 +121,13 @@ #: Elenhancements.xml:60 #, no-c-format msgid "You must ensure that the parameters are available not only when the page is rendered, but also when it is submittedIf the arguments can not be resolved when the page is submitted the action method will be called with <literal>null</literal> arguments!" -msgstr "" +msgstr "Devi assicurarti che i paramentri siano disponibili non solo quando la pagina viene generata, ma anche quando ne viene fatto il submit. Se gli argomenti non possono essere risolti quando la pagina viene inviata, il metodo d'azione verrà chiamato con argomenti <literal>null</literal>!" #. Tag: para #: Elenhancements.xml:67 #, no-c-format msgid "You can also pass literal strings using single quotes:" -msgstr "" +msgstr "Puoi anche passare stringe letterali usando virgolette singole:" #. Tag: programlisting #: Elenhancements.xml:71 @@ -145,7 +145,7 @@ #: Elenhancements.xml:82 #, no-c-format msgid "JBoss EL removes this restriction by allowing values to be retrieved using the method syntax. For example:" -msgstr "" +msgstr "JBoss EL rimuove questa restrizione permettendo che i valori vengano recuperati usando la sintassi del metodo. Per esempio:" #. Tag: programlisting #: Elenhancements.xml:87 @@ -157,7 +157,7 @@ #: Elenhancements.xml:89 #, no-c-format msgid "You can access the size of a collection in a similar manner:" -msgstr "" +msgstr "Puoi accedere alla dimensione di una collezioni in maniera analoga:" #. Tag: programlisting #: Elenhancements.xml:93 @@ -175,7 +175,7 @@ #: Elenhancements.xml:99 #, no-c-format msgid "Parameters are also allowed. The following example calls the <literal>productsByColorMethod</literal> with a literal string argument:" -msgstr "" +msgstr "Sono consentiti anche i parametri. Il seguente esempio chiama <literal>productsByColorMethod</literal> con un argomento stringa letterale:" #. Tag: programlisting #: Elenhancements.xml:105 @@ -193,7 +193,7 @@ #: Elenhancements.xml:112 #, no-c-format msgid "When using JBoss EL you should keep the following points in mind:" -msgstr "" +msgstr "Nell'uso di JBoss EL dovresti tenere presente i seguenti punti:" #. Tag: para #: Elenhancements.xml:118 @@ -253,7 +253,7 @@ #: Elenhancements.xml:167 #, no-c-format msgid "When you invoke a <literal>MethodExpression</literal> in Java code, parameters you pass may be ignored. Parameters defined in the expression will take precedence." -msgstr "" +msgstr "Quando viene invocato un <literal>MethodExpression</literal> nel codice Java, i parametri passati potrebbero essere ignorati. I parametri definiti nell'espressione avranno la precedenza." #. Tag: para #: Elenhancements.xml:175 @@ -277,7 +277,7 @@ #: Elenhancements.xml:198 #, no-c-format msgid "JBoss EL supports a limited projection syntax. A projection expression maps a sub-expression across a multi-valued (list, set, etc...) expression. For instance, the expression:" -msgstr "" +msgstr "JBoss EL supporta una limitata sintassi di proiezione. Un'espressione di proiezione mappa una sotto-espressione attraverso un'espressione a valori multipli (lista, set, ecc...). Per esempio, l'espressione:" #. Tag: programlisting #: Elenhancements.xml:204 @@ -289,7 +289,7 @@ #: Elenhancements.xml:206 #, no-c-format msgid "might return a list of departments. If you only need a list of department names, your only option is to iterate over the list to retrieve the values. JBoss EL allows this with a projection expression:" -msgstr "" +msgstr "potrebbe restituire una lista di dipartimenti. Se tu avessi bisogno di una lista di nommi di dipartimento, la tua unica opzione è quella di iterare sulla lista per recuperare i valori. JBoss EL permette questo con l'espressione di proiezione:" #. Tag: programlisting #: Elenhancements.xml:212 @@ -319,7 +319,7 @@ #: Elenhancements.xml:229 #, no-c-format msgid "Projections can be nested. The following expression returns the last names of every employee in every department:" -msgstr "" +msgstr "Le proiezioni possono essere annidate. La seguente espressione ritorna gli ultimi nomi di ciascun impiegato in ogni dipartimento:" #. Tag: programlisting #: Elenhancements.xml:234 @@ -331,7 +331,7 @@ #: Elenhancements.xml:236 #, no-c-format msgid "Nested projections can be slightly tricky, however. The following expression looks like it returns a list of all the employees in all the departments:" -msgstr "" +msgstr "Le proiezioni annidate possono comunque rivelarsi un pò difficoltose. La seguente espressione sembra ritornare una lista di tutti gli impiegati in tutti i dipartimenti:" #. Tag: programlisting #: Elenhancements.xml:242 @@ -343,7 +343,7 @@ #: Elenhancements.xml:244 #, no-c-format msgid "However, it actually returns a list containing a list of the employees for each individual department. To combine the values, it is necessary to use a slightly longer expression:" -msgstr "" +msgstr "Comunque, restituisce una lista contenente una lista di impiegati per ogni singolo dipartimento. Per combinare questi valori è necessario usare un'espressione leggermente più lunga:" #. Tag: programlisting #: Elenhancements.xml:250 @@ -355,5 +355,5 @@ #: Elenhancements.xml:252 #, no-c-format msgid "It is important to note that this syntax cannot be parsed by Facelets or JSP and thus cannot be used in xhtml or JSP files. We anticipate that the projection syntax will change in future versions of JBoss EL." -msgstr "" +msgstr "E' importante notare che questa sintassi non può essere analizzata da Facelet o JSP e quindi non può essere usata in file xhtml o jsp. Anticipiamo che la sintassi di proiezione cambierà nelle future versioni di JBoss EL." Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-12 15:05:19 UTC (rev 9765) +++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-12 19:17:06 UTC (rev 9766) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-04-04 01:24+0000\n" -"PO-Revision-Date: 2008-12-12 15:33+0100\n" +"PO-Revision-Date: 2008-12-12 19:46+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -134,12 +134,11 @@ msgid "Declarative state management" msgstr "Gestione dichiarativa dello stato" -# memory leaks ??? #. Tag: para #: Preface.xml:123 #, no-c-format msgid "We're all used to the concept of declarative transaction management and declarative security from the early days of EJB. EJB 3.0 even introduces declarative persistence context management. These are three examples of a broader problem of managing state that is associated with a particular <emphasis>context</emphasis>, while ensuring that all needed cleanup occurs when the context ends. Seam takes the concept of declarative state management much further and applies it to <emphasis>application state</emphasis>. Traditionally, J2EE applications implement state management manually, by getting and setting servlet session and request attributes. This approach to state management is the source of many bugs and memory leaks when applications fail to clean up session attributes, or when session data associated with different workflows collides in a multi-window application. Seam has the potential to almost entirely eliminate this class of bugs." -msgstr "Siamo tutti abituati al concetto di gestione dichiarativa delle transazioni e sicurezza dichiarativa fin dai primi giorni di EJB. EJB3 introduce anche la gestione dichiarativa del contesto di persistenza. Ci sono tre esempi di un ampio problema di gestione dello stato che è associato ad un particolare <emphasis>contesto</emphasis>, mentre tutte i dovuti cleanup avvengono quando il contesto termina. Seam porta oltre il concetto di gestione dichiarativa dello stato e lo applica allo <emphasis>stato dell'applicazione</emphasis>. Tradizionalmente le applicazioni J2EE implementano manualmente la gestione dello stato con il get e set della sessione servlet e degli attributi di richiesta. Questo approccio alla gestione dello stato è l'origine di molti bug e memory leak quando l'applicazione non riesce a pulire gli attributi di sessione, o quando i dati di sessione associati a diversi workflow collidono all'interno di un'applicazione multi-finestra. Seam ha il potenziale ! per eliminare quasi interamente questa classe di bug." +msgstr "Siamo tutti abituati al concetto di gestione dichiarativa delle transazioni e sicurezza dichiarativa fin dai primi giorni di EJB. EJB3 introduce anche la gestione dichiarativa del contesto di persistenza. Ci sono tre esempi di un ampio problema di gestione dello stato che è associato ad un particolare <emphasis>contesto</emphasis>, mentre tutte i dovuti cleanup avvengono quando il contesto termina. Seam porta oltre il concetto di gestione dichiarativa dello stato e lo applica allo <emphasis>stato dell'applicazione</emphasis>. Tradizionalmente le applicazioni J2EE implementano manualmente la gestione dello stato con il get e set della sessione servlet e degli attributi di richiesta. Questo approccio alla gestione dello stato è l'origine di molti bug e problemi di memoria (memory leak) quando l'applicazione non riesce a pulire gli attributi di sessione, o quando i dati di sessione associati a diversi workflow collidono all'interno di un'applicazione multi-finestra. ! Seam ha il potenziale per eliminare quasi interamente questa classe di bug." #. Tag: para #: Preface.xml:136 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-12 15:05:19 UTC (rev 9765) +++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-12 19:17:06 UTC (rev 9766) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-12-04 00:59+0000\n" -"PO-Revision-Date: 2008-12-09 21:08+0100\n" +"PO-Revision-Date: 2008-12-12 20:16+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -23,13 +23,13 @@ #: Tutorial.xml:7 #, no-c-format msgid "Using the Seam examples" -msgstr "" +msgstr "Utilizzo degli esempi di Seam" #. Tag: para #: Tutorial.xml:9 #, no-c-format msgid "Seam provides a number of example applications demonstrating how to use the various features of Seam. This tutorial will guide you through a few of those examples to help you get started learning Seam. The Seam examples are located in the <filename>examples</filename> subdirectory of the Seam distribution. The registration example, which will be the first example we look at, is in the <filename>examples/registration</filename> directory." -msgstr "" +msgstr "Seam fornisce un ampio numeri di applicazioni d'esempio che dimostrano l'uso delle varie funzionalità di Seam. Questo tutorial ti guiderà attraverso alcuni di questi esempi per aiutarti nell'apprendimento di Seam. Gli esempi di Seam sono posizionati nella sottodirectory <filename>examples</filename> della distribuzione Seam. L'esempio di registrazione, che è il primo esempio che vediamo, si trova nella directoyry <filename>examples/registration</filename>." #. Tag: para #: Tutorial.xml:15 @@ -158,7 +158,7 @@ #: Tutorial.xml:955 #, no-c-format msgid "Understanding the code" -msgstr "" +msgstr "Capire il codice" #. Tag: para #: Tutorial.xml:136 @@ -182,7 +182,7 @@ #: Tutorial.xml:148 #, no-c-format msgid "User.java" -msgstr "" +msgstr "User.java" #. Tag: programlisting #: Tutorial.xml:160 @@ -394,7 +394,7 @@ #: Tutorial.xml:237 #, no-c-format msgid "RegisterAction.java" -msgstr "" +msgstr "RegisterAction.java" #. Tag: programlisting #: Tutorial.xml:250 @@ -556,7 +556,7 @@ #: Tutorial.xml:337 #, no-c-format msgid "Register.java" -msgstr "" +msgstr "Register.java" #. Tag: programlisting #: Tutorial.xml:338 @@ -596,7 +596,7 @@ #: Tutorial.xml:352 #, no-c-format msgid "register.xhtml" -msgstr "" +msgstr "register.xhtml" #. Tag: programlisting #: Tutorial.xml:353 @@ -670,7 +670,7 @@ #: Tutorial.xml:361 #, no-c-format msgid "registered.xhtml" -msgstr "" +msgstr "registered.xhtml" #. Tag: programlisting #: Tutorial.xml:362 @@ -746,7 +746,7 @@ #: Tutorial.xml:393 #, no-c-format msgid "components.xml" -msgstr "" +msgstr "components.xml" #. Tag: programlisting #: Tutorial.xml:394 @@ -802,7 +802,7 @@ #: Tutorial.xml:410 #, no-c-format msgid "web.xml" -msgstr "" +msgstr "web.xml" #. Tag: programlisting #: Tutorial.xml:411 @@ -898,7 +898,7 @@ #: Tutorial.xml:427 #, no-c-format msgid "faces-config.xml" -msgstr "" +msgstr "faces-config.xml" #. Tag: programlisting #: Tutorial.xml:428 @@ -1161,7 +1161,7 @@ #: Tutorial.xml:1070 #, no-c-format msgid "How it works" -msgstr "" +msgstr "Come funziona" #. Tag: para #: Tutorial.xml:488 @@ -1233,7 +1233,7 @@ #: Tutorial.xml:544 #, no-c-format msgid "Message.java" -msgstr "" +msgstr "Message.java" #. Tag: programlisting #: Tutorial.xml:545 @@ -1395,7 +1395,7 @@ #: Tutorial.xml:568 #, no-c-format msgid "MessageManagerBean.java" -msgstr "" +msgstr "MessageManagerBean.java" #. Tag: programlisting #: Tutorial.xml:580 @@ -1549,7 +1549,7 @@ #: Tutorial.xml:644 #, no-c-format msgid "MessageManager.java" -msgstr "" +msgstr "MessageManager.java" #. Tag: programlisting #: Tutorial.xml:646 @@ -1601,7 +1601,7 @@ #: Tutorial.xml:663 #, no-c-format msgid "messages.jsp" -msgstr "" +msgstr "messages.jsp" #. Tag: programlisting #: Tutorial.xml:664 @@ -1737,7 +1737,7 @@ #: Tutorial.xml:728 #, no-c-format msgid "todo.jpdl.xml" -msgstr "" +msgstr "todo.jpdl.xml" #. Tag: programlisting #: Tutorial.xml:737 @@ -3351,7 +3351,7 @@ #: Tutorial.xml:1310 #, no-c-format msgid "HotelSearchingAction.java" -msgstr "" +msgstr "HotelSearchingAction.java" #. Tag: programlisting #: Tutorial.xml:1319 @@ -3431,6 +3431,79 @@ " public void destroy() {}\n" "}]]>" msgstr "" +"<![CDATA[@Stateful\n" +"@Name(\"hotelSearch\")\n" +"@Scope(ScopeType.SESSION)\n" +"@Restrict(\"#{identity.loggedIn}\")\n" +"public class HotelSearchingAction implements HotelSearching\n" +"{\n" +" \n" +" @PersistenceContext\n" +" private EntityManager em;\n" +" \n" +" private String searchString;\n" +" private int pageSize = 10;\n" +" private int page;\n" +" \n" +" @DataModel\n" +" private List<Hotel> hotels;\n" +" \n" +" public void find()\n" +" {\n" +" page = 0;\n" +" queryHotels();\n" +" }\n" +" public void nextPage()\n" +" {\n" +" page++;\n" +" queryHotels();\n" +" }\n" +" \n" +" private void queryHotels()\n" +" {\n" +" hotels = \n" +" em.createQuery(\"select h from Hotel h where lower(h.name) like #{pattern} \" + \n" +" \"or lower(h.city) like #{pattern} \" + \n" +" \"or lower(h.zip) like #{pattern} \" +\n" +" \"or lower(h.address) like #{pattern}\")\n" +" .setMaxResults(pageSize)\n" +" .setFirstResult( page * pageSize )\n" +" .getResultList();\n" +" }\n" +" \n" +" public boolean isNextPageAvailable()\n" +" {\n" +" return hotels!=null && hotels.size()==pageSize;\n" +" }\n" +" \n" +" public int getPageSize() {\n" +" return pageSize;\n" +" }\n" +" \n" +" public void setPageSize(int pageSize) {\n" +" this.pageSize = pageSize;\n" +" }\n" +" \n" +" @Factory(value=\"pattern\", scope=ScopeType.EVENT)\n" +" public String getSearchPattern()\n" +" {\n" +" return searchString==null ? \n" +" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + '%';\n" +" }\n" +" \n" +" public String getSearchString()\n" +" {\n" +" return searchString;\n" +" }\n" +" \n" +" public void setSearchString(String searchString)\n" +" {\n" +" this.searchString = searchString;\n" +" }\n" +" \n" +" @Remove\n" +" public void destroy() {}\n" +"}]]>" #. Tag: para #: Tutorial.xml:1322 @@ -3466,7 +3539,7 @@ #: Tutorial.xml:1355 #, no-c-format msgid "main.xhtml" -msgstr "" +msgstr "main.xhtml" #. Tag: programlisting #: Tutorial.xml:1364 @@ -3657,7 +3730,7 @@ #: Tutorial.xml:1633 #, no-c-format msgid "HotelBookingAction.java" -msgstr "" +msgstr "HotelBookingAction.java" #. Tag: programlisting #: Tutorial.xml:1418 @@ -3957,7 +4030,7 @@ #: Tutorial.xml:1549 #, no-c-format msgid "RoomPreferenceAction.java" -msgstr "" +msgstr "RoomPreferenceAction.java" #. Tag: programlisting #: Tutorial.xml:1558 @@ -4135,7 +4208,7 @@ #: Tutorial.xml:1599 #, no-c-format msgid "rooms.xhtml" -msgstr "" +msgstr "rooms.xhtml" #. Tag: programlisting #: Tutorial.xml:1607 @@ -4512,7 +4585,7 @@ #: Tutorial.xml:1699 #, no-c-format msgid "DVD Store example" -msgstr "" +msgstr "Esempio di Negozio DVD" #. Tag: para #: Tutorial.xml:1695 @@ -4542,7 +4615,7 @@ #: Tutorial.xml:1733 #, no-c-format msgid "Blog example" -msgstr "" +msgstr "Esempio di Blog" #. Tag: para #: Tutorial.xml:1744

15 years, 9 months

1
0
0 / 0

Seam SVN: r9765 - trunk.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-12-12 10:05:19 -0500 (Fri, 12 Dec 2008) New Revision: 9765 Modified: trunk/changelog.txt trunk/readme.txt Log: pre-release Modified: trunk/changelog.txt =================================================================== --- trunk/changelog.txt 2008-12-12 15:04:52 UTC (rev 9764) +++ trunk/changelog.txt 2008-12-12 15:05:19 UTC (rev 9765) @@ -1,6 +1,17 @@ JBoss Seam Changelog ==================== +Release Notes - Seam - Version 2.1.1.GA + +** Bug + * [JBSEAM-3682] - empty data for date type throws exception in JXLHelper.createCell + * [JBSEAM-3802] - Seamspace example - pages.xml is not a valid xml document + * [JBSEAM-3803] - Openid example - typo in faces-config.xml + * [JBSEAM-3817] - logLevel is not the correct name for the attribute, log-level is + * [JBSEAM-3819] - grammar in http://docs.jboss.com/seam/latest/reference/en-US/html/tutorial.html + * [JBSEAM-3830] - e:cell doesn't support null values + * [JBSEAM-3834] - ClassCastException in Cell Column With Empty Date + Release Notes - Seam - Version 2.1.1.CR2 ** Bug Modified: trunk/readme.txt =================================================================== --- trunk/readme.txt 2008-12-12 15:04:52 UTC (rev 9764) +++ trunk/readme.txt 2008-12-12 15:05:19 UTC (rev 9765) @@ -1,7 +1,7 @@ JBoss Seam - Contextual Component framework for Java EE 5 ========================================================= -version 2.1.1.CR2, December 2008 +version 2.1.1.GA, December 2008 This software is distributed under the terms of the FSF Lesser Gnu Public License (see lgpl.txt).

15 years, 9 months

1
0
0 / 0

Seam SVN: r9764 - in tags/JBoss_Seam_2_1_1_GA: build and 1 other directory.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-12-12 10:04:52 -0500 (Fri, 12 Dec 2008) New Revision: 9764 Modified: tags/JBoss_Seam_2_1_1_GA/build/default.build.properties tags/JBoss_Seam_2_1_1_GA/changelog.txt tags/JBoss_Seam_2_1_1_GA/readme.txt Log: pre-release Modified: tags/JBoss_Seam_2_1_1_GA/build/default.build.properties =================================================================== --- tags/JBoss_Seam_2_1_1_GA/build/default.build.properties 2008-12-12 14:45:51 UTC (rev 9763) +++ tags/JBoss_Seam_2_1_1_GA/build/default.build.properties 2008-12-12 15:04:52 UTC (rev 9764) @@ -8,7 +8,7 @@ major.version 2 minor.version .1 patchlevel .1 -qualifier -SNAPSHOT +qualifier .GA # # Other program locations # ----------------------- Modified: tags/JBoss_Seam_2_1_1_GA/changelog.txt =================================================================== --- tags/JBoss_Seam_2_1_1_GA/changelog.txt 2008-12-12 14:45:51 UTC (rev 9763) +++ tags/JBoss_Seam_2_1_1_GA/changelog.txt 2008-12-12 15:04:52 UTC (rev 9764) @@ -1,6 +1,17 @@ JBoss Seam Changelog ==================== +Release Notes - Seam - Version 2.1.1.GA + +** Bug + * [JBSEAM-3682] - empty data for date type throws exception in JXLHelper.createCell + * [JBSEAM-3802] - Seamspace example - pages.xml is not a valid xml document + * [JBSEAM-3803] - Openid example - typo in faces-config.xml + * [JBSEAM-3817] - logLevel is not the correct name for the attribute, log-level is + * [JBSEAM-3819] - grammar in http://docs.jboss.com/seam/latest/reference/en-US/html/tutorial.html + * [JBSEAM-3830] - e:cell doesn't support null values + * [JBSEAM-3834] - ClassCastException in Cell Column With Empty Date + Release Notes - Seam - Version 2.1.1.CR2 ** Bug Modified: tags/JBoss_Seam_2_1_1_GA/readme.txt =================================================================== --- tags/JBoss_Seam_2_1_1_GA/readme.txt 2008-12-12 14:45:51 UTC (rev 9763) +++ tags/JBoss_Seam_2_1_1_GA/readme.txt 2008-12-12 15:04:52 UTC (rev 9764) @@ -1,7 +1,7 @@ JBoss Seam - Contextual Component framework for Java EE 5 ========================================================= -version 2.1.1.CR2, December 2008 +version 2.1.1.GA, December 2008 This software is distributed under the terms of the FSF Lesser Gnu Public License (see lgpl.txt).

15 years, 9 months

1
0
0 / 0

Seam SVN: r9763 - trunk/doc/Seam_Reference_Guide/it-IT.

by seam-commits＠lists.jboss.org

Author: nico.ben Date: 2008-12-12 09:45:51 -0500 (Fri, 12 Dec 2008) New Revision: 9763 Modified: trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po trunk/doc/Seam_Reference_Guide/it-IT/Preface.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po 2008-12-12 14:44:37 UTC (rev 9762) +++ trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po 2008-12-12 14:45:51 UTC (rev 9763) @@ -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-12 15:45+0100\n" +"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -22,14 +22,7 @@ #. Tag: para #: Concepts.xml:6 #, no-c-format -msgid "" -"The two core concepts in Seam are the notion of a <emphasis>context</" -"emphasis> and the notion of a <emphasis>component</emphasis>. Components are " -"stateful objects, usually EJBs, and an instance of a component is associated " -"with a context, and given a name in that context. <emphasis>Bijection</" -"emphasis> provides a mechanism for aliasing internal component names " -"(instance variables) to contextual names, allowing component trees to be " -"dynamically assembled, and reassembled by Seam." +msgid "The two core concepts in Seam are the notion of a <emphasis>context</emphasis> and the notion of a <emphasis>component</emphasis>. Components are stateful objects, usually EJBs, and an instance of a component is associated with a context, and given a name in that context. <emphasis>Bijection</emphasis> provides a mechanism for aliasing internal component names (instance variables) to contextual names, allowing component trees to be dynamically assembled, and reassembled by Seam." msgstr "" #. Tag: para @@ -42,23 +35,19 @@ #: Concepts.xml:19 #, no-c-format msgid "Seam contexts" -msgstr "" +msgstr "Contesti di Seam" #. Tag: para #: Concepts.xml:20 #, no-c-format -msgid "" -"Seam contexts are created and destroyed by the framework. The application " -"does not control context demarcation via explicit Java API calls. Context " -"are usually implicit. In some cases, however, contexts are demarcated via " -"annotations." +msgid "Seam contexts are created and destroyed by the framework. The application does not control context demarcation via explicit Java API calls. Context are usually implicit. In some cases, however, contexts are demarcated via annotations." msgstr "" #. Tag: para #: Concepts.xml:23 #, no-c-format msgid "The basic Seam contexts are:" -msgstr "" +msgstr "I contesti base di Seam sono:" #. Tag: para #: Concepts.xml:27 @@ -73,31 +62,36 @@ msgstr "" #. Tag: para -#: Concepts.xml:33 Concepts.xml:225 +#: Concepts.xml:33 +#: Concepts.xml:225 #, no-c-format msgid "<para>Page context</para>" msgstr "" #. Tag: para -#: Concepts.xml:36 Concepts.xml:228 +#: Concepts.xml:36 +#: Concepts.xml:228 #, no-c-format msgid "<para>Conversation context</para>" msgstr "" #. Tag: para -#: Concepts.xml:39 Concepts.xml:231 +#: Concepts.xml:39 +#: Concepts.xml:231 #, no-c-format msgid "<para>Session context</para>" msgstr "" #. Tag: para -#: Concepts.xml:42 Concepts.xml:234 +#: Concepts.xml:42 +#: Concepts.xml:234 #, no-c-format msgid "<para>Business process context</para>" msgstr "" #. Tag: para -#: Concepts.xml:45 Concepts.xml:237 +#: Concepts.xml:45 +#: Concepts.xml:237 #, no-c-format msgid "<para>Application context</para>" msgstr "" @@ -105,18 +99,7 @@ #. Tag: para #: Concepts.xml:49 #, no-c-format -msgid "" -"You will recognize some of these contexts from servlet and related " -"specifications. However, two of them might be new to you: " -"<emphasis>conversation context</emphasis>, and <emphasis>business process " -"context</emphasis>. One reason state management in web applications is so " -"fragile and error-prone is that the three built-in contexts (request, " -"session and application) are not especially meaningful from the point of " -"view of the business logic. A user login session, for example, is a fairly " -"arbitrary construct in terms of the actual application work flow. Therefore, " -"most Seam components are scoped to the conversation or business process " -"contexts, since they are the contexts which are most meaningful in terms of " -"the application." +msgid "You will recognize some of these contexts from servlet and related specifications. However, two of them might be new to you: <emphasis>conversation context</emphasis>, and <emphasis>business process context</emphasis>. One reason state management in web applications is so fragile and error-prone is that the three built-in contexts (request, session and application) are not especially meaningful from the point of view of the business logic. A user login session, for example, is a fairly arbitrary construct in terms of the actual application work flow. Therefore, most Seam components are scoped to the conversation or business process contexts, since they are the contexts which are most meaningful in terms of the application." msgstr "" #. Tag: para @@ -129,182 +112,120 @@ #: Concepts.xml:65 #, no-c-format msgid "<title>Stateless context</title>" -msgstr "" +msgstr "<title>Contesto Stateless</title>" #. Tag: para #: Concepts.xml:66 #, no-c-format -msgid "" -"Components which are truly stateless (stateless session beans, primarily) " -"always live in the stateless context (which is basically the absense of a " -"context since the instance Seam resolves is not stored). Stateless " -"components are not very interesting, and are arguably not very object-" -"oriented. Nevertheless, they do get developed and used and are thus an " -"important part of any Seam application." +msgid "Components which are truly stateless (stateless session beans, primarily) always live in the stateless context (which is basically the absense of a context since the instance Seam resolves is not stored). Stateless components are not very interesting, and are arguably not very object-oriented. Nevertheless, they do get developed and used and are thus an important part of any Seam application." msgstr "" #. Tag: title #: Concepts.xml:75 #, no-c-format msgid "<title>Event context</title>" -msgstr "" +msgstr "<title>Contesto Evento</title>" #. Tag: para #: Concepts.xml:76 #, no-c-format -msgid "" -"The event context is the \"narrowest\" stateful context, and is a " -"generalization of the notion of the web request context to cover other kinds " -"of events. Nevertheless, the event context associated with the lifecycle of " -"a JSF request is the most important example of an event context, and the one " -"you will work with most often. Components associated with the event context " -"are destroyed at the end of the request, but their state is available and " -"well-defined for at least the lifecycle of the request." +msgid "The event context is the \"narrowest\" stateful context, and is a generalization of the notion of the web request context to cover other kinds of events. Nevertheless, the event context associated with the lifecycle of a JSF request is the most important example of an event context, and the one you will work with most often. Components associated with the event context are destroyed at the end of the request, but their state is available and well-defined for at least the lifecycle of the request." msgstr "" #. Tag: para #: Concepts.xml:83 #, no-c-format -msgid "" -"When you invoke a Seam component via RMI, or Seam Remoting, the event " -"context is created and destroyed just for the invocation." +msgid "When you invoke a Seam component via RMI, or Seam Remoting, the event context is created and destroyed just for the invocation." msgstr "" #. Tag: title #: Concepts.xml:90 #, no-c-format msgid "<title>Page context</title>" -msgstr "" +msgstr "<title>Contesto Pagina</title>" #. Tag: para #: Concepts.xml:91 #, no-c-format -msgid "" -"The page context allows you to associate state with a particular instance of " -"a rendered page. You can initialize state in your event listener, or while " -"actually rendering the page, and then have access to it from any event that " -"originates from that page. This is especially useful for functionality like " -"clickable lists, where the list is backed by changing data on the server " -"side. The state is actually serialized to the client, so this construct is " -"extremely robust with respect to multi-window operation and the back button." +msgid "The page context allows you to associate state with a particular instance of a rendered page. You can initialize state in your event listener, or while actually rendering the page, and then have access to it from any event that originates from that page. This is especially useful for functionality like clickable lists, where the list is backed by changing data on the server side. The state is actually serialized to the client, so this construct is extremely robust with respect to multi-window operation and the back button." msgstr "" #. Tag: title #: Concepts.xml:102 #, no-c-format msgid "<title>Conversation context</title>" -msgstr "" +msgstr "<title>Contesto Conversazione</title>" #. Tag: para #: Concepts.xml:103 #, no-c-format -msgid "" -"The conversation context is a truly central concept in Seam. A " -"<emphasis>conversation</emphasis> is a unit of work from the point of view " -"of the user. It might span several interactions with the user, several " -"requests, and several database transactions. But to the user, a conversation " -"solves a single problem. For example, \"book hotel\", \"approve contract\", " -"\"create order\" are all conversations. You might like to think of a " -"conversation implementing a single \"use case\" or \"user story\", but the " -"relationship is not necessarily quite exact." +msgid "The conversation context is a truly central concept in Seam. A <emphasis>conversation</emphasis> is a unit of work from the point of view of the user. It might span several interactions with the user, several requests, and several database transactions. But to the user, a conversation solves a single problem. For example, \"book hotel\", \"approve contract\", \"create order\" are all conversations. You might like to think of a conversation implementing a single \"use case\" or \"user story\", but the relationship is not necessarily quite exact." msgstr "" #. Tag: para #: Concepts.xml:111 #, no-c-format -msgid "" -"A conversation holds state associated with \"what the user is doing now, in " -"this window\". A single user may have multiple conversations in progress at " -"any point in time, usually in multiple windows. The conversation context " -"allows us to ensure that state from the different conversations does not " -"collide and cause bugs." +msgid "A conversation holds state associated with \"what the user is doing now, in this window\". A single user may have multiple conversations in progress at any point in time, usually in multiple windows. The conversation context allows us to ensure that state from the different conversations does not collide and cause bugs." msgstr "" #. Tag: para #: Concepts.xml:117 #, no-c-format -msgid "" -"It might take you some time to get used to thinking of applications in terms " -"of conversations. But once you get used to it, we think you'll love the " -"notion, and never be able to not think in terms of conversations again!" +msgid "It might take you some time to get used to thinking of applications in terms of conversations. But once you get used to it, we think you'll love the notion, and never be able to not think in terms of conversations again!" msgstr "" #. Tag: para #: Concepts.xml:122 #, no-c-format -msgid "" -"Some conversations last for just a single request. Conversations that span " -"multiple requests must be demarcated using annotations provided by Seam." +msgid "Some conversations last for just a single request. Conversations that span multiple requests must be demarcated using annotations provided by Seam." msgstr "" #. Tag: para #: Concepts.xml:126 #, no-c-format -msgid "" -"Some conversations are also <emphasis>tasks</emphasis>. A task is a " -"conversation that is significant in terms of a long-running business " -"process, and has the potential to trigger a business process state " -"transition when it is successfully completed. Seam provides a special set of " -"annotations for task demarcation." +msgid "Some conversations are also <emphasis>tasks</emphasis>. A task is a conversation that is significant in terms of a long-running business process, and has the potential to trigger a business process state transition when it is successfully completed. Seam provides a special set of annotations for task demarcation." msgstr "" #. Tag: para #: Concepts.xml:132 #, no-c-format -msgid "" -"Conversations may be <emphasis>nested</emphasis>, with one conversation " -"taking place \"inside\" a wider conversation. This is an advanced feature." +msgid "Conversations may be <emphasis>nested</emphasis>, with one conversation taking place \"inside\" a wider conversation. This is an advanced feature." msgstr "" #. Tag: para #: Concepts.xml:136 #, no-c-format -msgid "" -"Usually, conversation state is actually held by Seam in the servlet session " -"between requests. Seam implements configurable <emphasis>conversation " -"timeout</emphasis>, automatically destroying inactive conversations, and " -"thus ensuring that the state held by a single user login session does not " -"grow without bound if the user abandons conversations." +msgid "Usually, conversation state is actually held by Seam in the servlet session between requests. Seam implements configurable <emphasis>conversation timeout</emphasis>, automatically destroying inactive conversations, and thus ensuring that the state held by a single user login session does not grow without bound if the user abandons conversations." msgstr "" #. Tag: para #: Concepts.xml:142 #, no-c-format -msgid "" -"Seam serializes processing of concurrent requests that take place in the " -"same long-running conversation context, in the same process." +msgid "Seam serializes processing of concurrent requests that take place in the same long-running conversation context, in the same process." msgstr "" #. Tag: para #: Concepts.xml:146 #, no-c-format -msgid "" -"Alternatively, Seam may be configured to keep conversational state in the " -"client browser." +msgid "Alternatively, Seam may be configured to keep conversational state in the client browser." msgstr "" #. Tag: title #: Concepts.xml:152 #, no-c-format msgid "<title>Session context</title>" -msgstr "" +msgstr "<title>Contesto Sessione</title>" #. Tag: para #: Concepts.xml:153 #, no-c-format -msgid "" -"A session context holds state associated with the user login session. While " -"there are some cases where it is useful to share state between several " -"conversations, we generally frown on the use of session context for holding " -"components other than global information about the logged in user." +msgid "A session context holds state associated with the user login session. While there are some cases where it is useful to share state between several conversations, we generally frown on the use of session context for holding components other than global information about the logged in user." msgstr "" #. Tag: para #: Concepts.xml:158 #, no-c-format -msgid "" -"In a JSR-168 portal environment, the session context represents the portlet " -"session." +msgid "In a JSR-168 portal environment, the session context represents the portlet session." msgstr "" #. Tag: title @@ -316,15 +237,7 @@ #. Tag: para #: Concepts.xml:165 #, no-c-format -msgid "" -"The business process context holds state associated with the long running " -"business process. This state is managed and made persistent by the BPM " -"engine (JBoss jBPM). The business process spans multiple interactions with " -"multiple users, so this state is shared between multiple users, but in a " -"well-defined manner. The current task determines the current business " -"process instance, and the lifecycle of the business process is defined " -"externally using a <emphasis>process definition language</emphasis>, so " -"there are no special annotations for business process demarcation." +msgid "The business process context holds state associated with the long running business process. This state is managed and made persistent by the BPM engine (JBoss jBPM). The business process spans multiple interactions with multiple users, so this state is shared between multiple users, but in a well-defined manner. The current task determines the current business process instance, and the lifecycle of the business process is defined externally using a <emphasis>process definition language</emphasis>, so there are no special annotations for business process demarcation." msgstr "" #. Tag: title @@ -336,47 +249,32 @@ #. Tag: para #: Concepts.xml:177 #, no-c-format -msgid "" -"The application context is the familiar servlet context from the servlet " -"spec. Application context is mainly useful for holding static information " -"such as configuration data, reference data or metamodels. For example, Seam " -"stores its own configuration and metamodel in the application context." +msgid "The application context is the familiar servlet context from the servlet spec. Application context is mainly useful for holding static information such as configuration data, reference data or metamodels. For example, Seam stores its own configuration and metamodel in the application context." msgstr "" #. Tag: title #: Concepts.xml:185 #, no-c-format msgid "Context variables" -msgstr "" +msgstr "Variabili di contesto" #. Tag: para #: Concepts.xml:186 #, no-c-format -msgid "" -"A context defines a namespace, a set of <emphasis>context variables</" -"emphasis>. These work much the same as session or request attributes in the " -"servlet spec. You may bind any value you like to a context variable, but " -"usually we bind Seam component instances to context variables." +msgid "A context defines a namespace, a set of <emphasis>context variables</emphasis>. These work much the same as session or request attributes in the servlet spec. You may bind any value you like to a context variable, but usually we bind Seam component instances to context variables." msgstr "" #. Tag: para #: Concepts.xml:192 #, no-c-format -msgid "" -"So, within a context, a component instance is identified by the context " -"variable name (this is usually, but not always, the same as the component " -"name). You may programatically access a named component instance in a " -"particular scope via the <literal>Contexts</literal> class, which provides " -"access to several thread-bound instances of the <literal>Context</literal> " -"interface:" +msgid "So, within a context, a component instance is identified by the context variable name (this is usually, but not always, the same as the component name). You may programatically access a named component instance in a particular scope via the <literal>Contexts</literal> class, which provides access to several thread-bound instances of the <literal>Context</literal> interface:" msgstr "" #. Tag: programlisting #: Concepts.xml:199 #, no-c-format -msgid "" -"<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>" -msgstr "" +msgid "<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>" +msgstr "<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>" #. Tag: para #: Concepts.xml:201 @@ -388,14 +286,12 @@ #: Concepts.xml:205 #, no-c-format msgid "<![CDATA[Contexts.getSessionContext().set(\"user\", user);]]>" -msgstr "" +msgstr "<![CDATA[Contexts.getSessionContext().set(\"user\", user);]]>" #. Tag: para #: Concepts.xml:207 #, no-c-format -msgid "" -"Usually, however, we obtain components from a context via injection, and put " -"component instances into a context via outjection." +msgid "Usually, however, we obtain components from a context via injection, and put component instances into a context via outjection." msgstr "" #. Tag: title @@ -407,25 +303,19 @@ #. Tag: para #: Concepts.xml:215 #, no-c-format -msgid "" -"Sometimes, as above, component instances are obtained from a particular " -"known scope. Other times, all stateful scopes are searched, in " -"<emphasis>priority order</emphasis>. The order is as follows:" +msgid "Sometimes, as above, component instances are obtained from a particular known scope. Other times, all stateful scopes are searched, in <emphasis>priority order</emphasis>. The order is as follows:" msgstr "" #. Tag: para #: Concepts.xml:222 #, no-c-format msgid "<para>Event context</para>" -msgstr "" +msgstr "<para>Contesto Evento</para>" #. Tag: para #: Concepts.xml:241 #, no-c-format -msgid "" -"You can perform a priority search by calling <literal>Contexts." -"lookupInStatefulContexts()</literal>. Whenever you access a component by " -"name from a JSF page, a priority search occurs." +msgid "You can perform a priority search by calling <literal>Contexts.lookupInStatefulContexts()</literal>. Whenever you access a component by name from a JSF page, a priority search occurs." msgstr "" #. Tag: title @@ -437,83 +327,43 @@ #. Tag: para #: Concepts.xml:250 #, no-c-format -msgid "" -"Neither the servlet nor EJB specifications define any facilities for " -"managing concurrent requests originating from the same client. The servlet " -"container simply lets all threads run concurrently and leaves enforcing " -"threadsafeness to application code. The EJB container allows stateless " -"components to be accessed concurrently, and throws an exception if multiple " -"threads access a stateful session bean." +msgid "Neither the servlet nor EJB specifications define any facilities for managing concurrent requests originating from the same client. The servlet container simply lets all threads run concurrently and leaves enforcing threadsafeness to application code. The EJB container allows stateless components to be accessed concurrently, and throws an exception if multiple threads access a stateful session bean." msgstr "" #. Tag: para #: Concepts.xml:256 #, no-c-format -msgid "" -"This behavior might have been okay in old-style web applications which were " -"based around fine-grained, synchronous requests. But for modern applications " -"which make heavy use of many fine-grained, asynchronous (AJAX) requests, " -"concurrency is a fact of life, and must be supported by the programming " -"model. Seam weaves a concurrency management layer into its context model." +msgid "This behavior might have been okay in old-style web applications which were based around fine-grained, synchronous requests. But for modern applications which make heavy use of many fine-grained, asynchronous (AJAX) requests, concurrency is a fact of life, and must be supported by the programming model. Seam weaves a concurrency management layer into its context model." msgstr "" #. Tag: para #: Concepts.xml:262 #, no-c-format -msgid "" -"The Seam session and application contexts are multithreaded. Seam will allow " -"concurrent requests in a context to be processed concurrently. The event and " -"page contexts are by nature single threaded. The business process context is " -"strictly speaking multi-threaded, but in practice concurrency is " -"sufficiently rare that this fact may be disregarded most of the time. " -"Finally, Seam enforces a <emphasis>single thread per conversation per " -"process</emphasis> model for the conversation context by serializing " -"concurrent requests in the same long-running conversation context." +msgid "The Seam session and application contexts are multithreaded. Seam will allow concurrent requests in a context to be processed concurrently. The event and page contexts are by nature single threaded. The business process context is strictly speaking multi-threaded, but in practice concurrency is sufficiently rare that this fact may be disregarded most of the time. Finally, Seam enforces a <emphasis>single thread per conversation per process</emphasis> model for the conversation context by serializing concurrent requests in the same long-running conversation context." msgstr "" #. Tag: para #: Concepts.xml:270 #, no-c-format -msgid "" -"Since the session context is multithreaded, and often contains volatile " -"state, session scope components are always protected by Seam from concurrent " -"access so long as the Seam interceptors are not disabled for that component. " -"If interceptors are disabled, then any thread-safety that is required must " -"be implemented by the component itself. Seam serializes requests to session " -"scope session beans and JavaBeans by default (and detects and breaks any " -"deadlocks that occur). This is not the default behaviour for application " -"scoped components however, since application scoped components do not " -"usually hold volatile state and because synchronization at the global level " -"is <emphasis>extremely</emphasis> expensive. However, you can force a " -"serialized threading model on any session bean or JavaBean component by " -"adding the <literal>@Synchronized</literal> annotation." +msgid "Since the session context is multithreaded, and often contains volatile state, session scope components are always protected by Seam from concurrent access so long as the Seam interceptors are not disabled for that component. If interceptors are disabled, then any thread-safety that is required must be implemented by the component itself. Seam serializes requests to session scope session beans and JavaBeans by default (and detects and breaks any deadlocks that occur). This is not the default behaviour for application scoped components however, since application scoped components do not usually hold volatile state and because synchronization at the global level is <emphasis>extremely</emphasis> expensive. However, you can force a serialized threading model on any session bean or JavaBean component by adding the <literal>@Synchronized</literal> annotation." msgstr "" #. Tag: para #: Concepts.xml:281 #, no-c-format -msgid "" -"This concurrency model means that AJAX clients can safely use volatile " -"session and conversational state, without the need for any special work on " -"the part of the developer." +msgid "This concurrency model means that AJAX clients can safely use volatile session and conversational state, without the need for any special work on the part of the developer." msgstr "" #. Tag: title #: Concepts.xml:290 #, no-c-format msgid "Seam components" -msgstr "" +msgstr "Componenti di Seam" #. Tag: para #: Concepts.xml:291 #, no-c-format -msgid "" -"Seam components are POJOs (Plain Old Java Objects). In particular, they are " -"JavaBeans or EJB 3.0 enterprise beans. While Seam does not require that " -"components be EJBs and can even be used without an EJB 3.0 compliant " -"container, Seam was designed with EJB 3.0 in mind and includes deep " -"integration with EJB 3.0. Seam supports the following <emphasis>component " -"types</emphasis>." +msgid "Seam components are POJOs (Plain Old Java Objects). In particular, they are JavaBeans or EJB 3.0 enterprise beans. While Seam does not require that components be EJBs and can even be used without an EJB 3.0 compliant container, Seam was designed with EJB 3.0 in mind and includes deep integration with EJB 3.0. Seam supports the following <emphasis>component types</emphasis>." msgstr "" #. Tag: para @@ -538,13 +388,13 @@ #: Concepts.xml:309 #, no-c-format msgid "<para>JavaBeans</para>" -msgstr "" +msgstr "<para>JavaBeans</para>" #. Tag: para #: Concepts.xml:312 #, no-c-format msgid "EJB 3.0 message-driven beans" -msgstr "" +msgstr "EJB 3.0 message-driven beans" #. Tag: para #: Concepts.xml:315 @@ -561,12 +411,7 @@ #. Tag: para #: Concepts.xml:321 #, no-c-format -msgid "" -"Stateless session bean components are not able to hold state across multiple " -"invocations. Therefore, they usually work by operating upon the state of " -"other components in the various Seam contexts. They may be used as JSF " -"action listeners, but cannot provide properties to JSF components for " -"display." +msgid "Stateless session bean components are not able to hold state across multiple invocations. Therefore, they usually work by operating upon the state of other components in the various Seam contexts. They may be used as JSF action listeners, but cannot provide properties to JSF components for display." msgstr "" #. Tag: para @@ -578,29 +423,19 @@ #. Tag: para #: Concepts.xml:329 #, no-c-format -msgid "" -"Stateless session beans can be accessed concurrently as a new instance is " -"used for each request. Assigning the instance to the request is the " -"responsibility of the EJB3 container (normally instances will be allocated " -"from a reusable pool meaning that you may find any instance variables " -"contain data from previous uses of the bean)." +msgid "Stateless session beans can be accessed concurrently as a new instance is used for each request. Assigning the instance to the request is the responsibility of the EJB3 container (normally instances will be allocated from a reusable pool meaning that you may find any instance variables contain data from previous uses of the bean)." msgstr "" #. Tag: para #: Concepts.xml:335 #, no-c-format -msgid "" -"Stateless session beans are the least interesting kind of Seam component." +msgid "Stateless session beans are the least interesting kind of Seam component." msgstr "" #. Tag: para #: Concepts.xml:338 #, no-c-format -msgid "" -"Seam stateless session bean components may be instantiated using " -"<literal>Component.getInstance()</literal> or <literal>@In(create=true)</" -"literal>. They should not be directly instantiated via JNDI lookup or the " -"<literal>new</literal> operator." +msgid "Seam stateless session bean components may be instantiated using <literal>Component.getInstance()</literal> or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup or the <literal>new</literal> operator." msgstr "" #. Tag: title @@ -612,53 +447,31 @@ #. Tag: para #: Concepts.xml:347 #, no-c-format -msgid "" -"Stateful session bean components are able to hold state not only across " -"multiple invocations of the bean, but also across multiple requests. " -"Application state that does not belong in the database should usually be " -"held by stateful session beans. This is a major difference between Seam and " -"many other web application frameworks. Instead of sticking information about " -"the current conversation directly in the <literal>HttpSession</literal>, you " -"should keep it in instance variables of a stateful session bean that is " -"bound to the conversation context. This allows Seam to manage the lifecycle " -"of this state for you, and ensure that there are no collisions between state " -"relating to different concurrent conversations." +msgid "Stateful session bean components are able to hold state not only across multiple invocations of the bean, but also across multiple requests. Application state that does not belong in the database should usually be held by stateful session beans. This is a major difference between Seam and many other web application frameworks. Instead of sticking information about the current conversation directly in the <literal>HttpSession</literal>, you should keep it in instance variables of a stateful session bean that is bound to the conversation context. This allows Seam to manage the lifecycle of this state for you, and ensure that there are no collisions between state relating to different concurrent conversations." msgstr "" #. Tag: para #: Concepts.xml:357 #, no-c-format -msgid "" -"Stateful session beans are often used as JSF action listener, and as backing " -"beans that provide properties to JSF components for display or form " -"submission." +msgid "Stateful session beans are often used as JSF action listener, and as backing beans that provide properties to JSF components for display or form submission." msgstr "" #. Tag: para #: Concepts.xml:361 #, no-c-format -msgid "" -"By default, stateful session beans are bound to the conversation context. " -"They may never be bound to the page or stateless contexts." +msgid "By default, stateful session beans are bound to the conversation context. They may never be bound to the page or stateless contexts." msgstr "" #. Tag: para #: Concepts.xml:365 #, no-c-format -msgid "" -"Concurrent requests to session-scoped stateful session beans are always " -"serialized by Seam as long as the Seam interceptors are not disabled for the " -"bean." +msgid "Concurrent requests to session-scoped stateful session beans are always serialized by Seam as long as the Seam interceptors are not disabled for the bean." msgstr "" #. Tag: para #: Concepts.xml:370 #, no-c-format -msgid "" -"Seam stateful session bean components may be instantiated using " -"<literal>Component.getInstance()</literal> or <literal>@In(create=true)</" -"literal>. They should not be directly instantiated via JNDI lookup or the " -"<literal>new</literal> operator." +msgid "Seam stateful session bean components may be instantiated using <literal>Component.getInstance()</literal> or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup or the <literal>new</literal> operator." msgstr "" #. Tag: title @@ -670,85 +483,55 @@ #. Tag: para #: Concepts.xml:379 #, no-c-format -msgid "" -"Entity beans may be bound to a context variable and function as a seam " -"component. Because entities have a persistent identity in addition to their " -"contextual identity, entity instances are usually bound explicitly in Java " -"code, rather than being instantiated implicitly by Seam." +msgid "Entity beans may be bound to a context variable and function as a seam component. Because entities have a persistent identity in addition to their contextual identity, entity instances are usually bound explicitly in Java code, rather than being instantiated implicitly by Seam." msgstr "" #. Tag: para #: Concepts.xml:384 #, no-c-format -msgid "" -"Entity bean components do not support bijection or context demarcation. Nor " -"does invocation of an entity bean trigger validation." +msgid "Entity bean components do not support bijection or context demarcation. Nor does invocation of an entity bean trigger validation." msgstr "" #. Tag: para #: Concepts.xml:388 #, no-c-format -msgid "" -"Entity beans are not usually used as JSF action listeners, but do often " -"function as backing beans that provide properties to JSF components for " -"display or form submission. In particular, it is common to use an entity as " -"a backing bean, together with a stateless session bean action listener to " -"implement create/update/delete type functionality." +msgid "Entity beans are not usually used as JSF action listeners, but do often function as backing beans that provide properties to JSF components for display or form submission. In particular, it is common to use an entity as a backing bean, together with a stateless session bean action listener to implement create/update/delete type functionality." msgstr "" #. Tag: para #: Concepts.xml:394 #, no-c-format -msgid "" -"By default, entity beans are bound to the conversation context. They may " -"never be bound to the stateless context." +msgid "By default, entity beans are bound to the conversation context. They may never be bound to the stateless context." msgstr "" #. Tag: para #: Concepts.xml:398 #, no-c-format -msgid "" -"Note that it in a clustered environment is somewhat less efficient to bind " -"an entity bean directly to a conversation or session scoped Seam context " -"variable than it would be to hold a reference to the entity bean in a " -"stateful session bean. For this reason, not all Seam applications define " -"entity beans to be Seam components." +msgid "Note that it in a clustered environment is somewhat less efficient to bind an entity bean directly to a conversation or session scoped Seam context variable than it would be to hold a reference to the entity bean in a stateful session bean. For this reason, not all Seam applications define entity beans to be Seam components." msgstr "" #. Tag: para #: Concepts.xml:404 #, no-c-format -msgid "" -"Seam entity bean components may be instantiated using <literal>Component." -"getInstance()</literal>, <literal>@In(create=true)</literal> or directly " -"using the <literal>new</literal> operator." +msgid "Seam entity bean components may be instantiated using <literal>Component.getInstance()</literal>, <literal>@In(create=true)</literal> or directly using the <literal>new</literal> operator." msgstr "" #. Tag: title #: Concepts.xml:411 #, no-c-format msgid "<title>JavaBeans</title>" -msgstr "" +msgstr "<title>JavaBeans</title>" #. Tag: para #: Concepts.xml:412 #, no-c-format -msgid "" -"Javabeans may be used just like a stateless or stateful session bean. " -"However, they do not provide the functionality of a session bean " -"(declarative transaction demarcation, declarative security, efficient " -"clustered state replication, EJB 3.0 persistence, timeout methods, etc)." +msgid "Javabeans may be used just like a stateless or stateful session bean. However, they do not provide the functionality of a session bean (declarative transaction demarcation, declarative security, efficient clustered state replication, EJB 3.0 persistence, timeout methods, etc)." msgstr "" #. Tag: para #: Concepts.xml:417 #, no-c-format -msgid "" -"In a later chapter, we show you how to use Seam and Hibernate without an EJB " -"container. In this use case, components are JavaBeans instead of session " -"beans. Note, however, that in many application servers it is somewhat less " -"efficient to cluster conversation or session scoped Seam JavaBean components " -"than it is to cluster stateful session bean components." +msgid "In a later chapter, we show you how to use Seam and Hibernate without an EJB container. In this use case, components are JavaBeans instead of session beans. Note, however, that in many application servers it is somewhat less efficient to cluster conversation or session scoped Seam JavaBean components than it is to cluster stateful session bean components." msgstr "" #. Tag: para @@ -760,18 +543,13 @@ #. Tag: para #: Concepts.xml:426 #, no-c-format -msgid "" -"Concurrent requests to session-scoped JavaBeans are always serialized by " -"Seam." +msgid "Concurrent requests to session-scoped JavaBeans are always serialized by Seam." msgstr "" #. Tag: para #: Concepts.xml:429 #, no-c-format -msgid "" -"Seam JavaBean components may be instantiated using <literal>Component." -"getInstance()</literal> or <literal>@In(create=true)</literal>. They should " -"not be directly instantiated using the <literal>new</literal> operator." +msgid "Seam JavaBean components may be instantiated using <literal>Component.getInstance()</literal> or <literal>@In(create=true)</literal>. They should not be directly instantiated using the <literal>new</literal> operator." msgstr "" #. Tag: title @@ -783,47 +561,31 @@ #. Tag: para #: Concepts.xml:438 #, no-c-format -msgid "" -"Message-driven beans may function as a seam component. However, message-" -"driven beans are called quite differently to other Seam components - instead " -"of invoking them via the context variable, they listen for messages sent to " -"a JMS queue or topic." +msgid "Message-driven beans may function as a seam component. However, message-driven beans are called quite differently to other Seam components - instead of invoking them via the context variable, they listen for messages sent to a JMS queue or topic." msgstr "" #. Tag: para #: Concepts.xml:443 #, no-c-format -msgid "" -"Message-driven beans may not be bound to a Seam context. Nor do they have " -"access to the session or conversation state of their \"caller\". However, " -"they do support bijection and some other Seam functionality." +msgid "Message-driven beans may not be bound to a Seam context. Nor do they have access to the session or conversation state of their \"caller\". However, they do support bijection and some other Seam functionality." msgstr "" #. Tag: para #: Concepts.xml:448 #, no-c-format -msgid "" -"Message-driven beans are never instantiated by the application. They are " -"instantiated by the EJB container when a message is received." +msgid "Message-driven beans are never instantiated by the application. They are instantiated by the EJB container when a message is received." msgstr "" #. Tag: title #: Concepts.xml:455 #, no-c-format msgid "Interception" -msgstr "" +msgstr "Intercettazione" #. Tag: para #: Concepts.xml:456 #, no-c-format -msgid "" -"In order to perform its magic (bijection, context demarcation, validation, " -"etc), Seam must intercept component invocations. For JavaBeans, Seam is in " -"full control of instantiation of the component, and no special configuration " -"is needed. For entity beans, interception is not required since bijection " -"and context demarcation are not defined. For session beans, we must register " -"an EJB interceptor for the session bean component. We could use an " -"annotation, as follows:" +msgid "In order to perform its magic (bijection, context demarcation, validation, etc), Seam must intercept component invocations. For JavaBeans, Seam is in full control of instantiation of the component, and no special configuration is needed. For entity beans, interception is not required since bijection and context demarcation are not defined. For session beans, we must register an EJB interceptor for the session bean component. We could use an annotation, as follows:" msgstr "" #. Tag: programlisting @@ -836,13 +598,16 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Stateless\n" +"@Interceptors(SeamInterceptor.class)\n" +"public class LoginAction implements Login { \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:466 #, no-c-format -msgid "" -"But a much better way is to define the interceptor in <literal>ejb-jar.xml</" -"literal>." +msgid "But a much better way is to define the interceptor in <literal>ejb-jar.xml</literal>." msgstr "" #. Tag: programlisting @@ -851,19 +616,29 @@ 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>]]>" 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>]]>" #. Tag: title #: Concepts.xml:475 @@ -874,9 +649,7 @@ #. Tag: para #: Concepts.xml:476 #, no-c-format -msgid "" -"All seam components need a name. We can assign a name to a component using " -"the <literal>@Name</literal> annotation:" +msgid "All seam components need a name. We can assign a name to a component using the <literal>@Name</literal> annotation:" msgstr "" #. Tag: programlisting @@ -889,51 +662,34 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:483 #, no-c-format -msgid "" -"This name is the <emphasis>seam component name</emphasis> and is not related " -"to any other name defined by the EJB specification. However, seam component " -"names work just like JSF managed bean names and you can think of the two " -"concepts as identical." +msgid "This name is the <emphasis>seam component name</emphasis> and is not related to any other name defined by the EJB specification. However, seam component names work just like JSF managed bean names and you can think of the two concepts as identical." msgstr "" #. Tag: para #: Concepts.xml:489 #, no-c-format -msgid "" -"<literal>@Name</literal> is not the only way to define a component name, but " -"we always need to specify the name <emphasis>somewhere</emphasis>. If we " -"don't, then none of the other Seam annotations will function." +msgid "<literal>@Name</literal> is not the only way to define a component name, but we always need to specify the name <emphasis>somewhere</emphasis>. If we don't, then none of the other Seam annotations will function." msgstr "" #. Tag: para #: Concepts.xml:495 #, no-c-format -msgid "" -"Whenever Seam instantiates a component, it binds the new instance to a " -"variable in the scope configured for the component that matches the " -"component name. This behavior is identical to how JSF managed beans work, " -"except that Seam allows you to configure this mapping using annotations " -"rather than XML. You can also programmatically bind a component to a context " -"variable. This is useful if a particular component serves more than one role " -"in the system. For example, the currently logged in <literal>User</literal> " -"might be bound to the <literal>currentUser</literal> session context " -"variable, while a <literal>User</literal> that is the subject of some " -"administration functionality might be bound to the <literal>user</literal> " -"conversation context variable. Be careful, though, because through a " -"programmatic assignment, it's possible to overwrite a context variable that " -"has a reference to a Seam component, potentially confusing matters." +msgid "Whenever Seam instantiates a component, it binds the new instance to a variable in the scope configured for the component that matches the component name. This behavior is identical to how JSF managed beans work, except that Seam allows you to configure this mapping using annotations rather than XML. You can also programmatically bind a component to a context variable. This is useful if a particular component serves more than one role in the system. For example, the currently logged in <literal>User</literal> might be bound to the <literal>currentUser</literal> session context variable, while a <literal>User</literal> that is the subject of some administration functionality might be bound to the <literal>user</literal> conversation context variable. Be careful, though, because through a programmatic assignment, it's possible to overwrite a context variable that has a reference to a Seam component, potentially confusing matters." msgstr "" #. Tag: para #: Concepts.xml:506 #, no-c-format -msgid "" -"For very large applications, and for built-in seam components, qualified " -"component names are often used to avoid naming conflicts." +msgid "For very large applications, and for built-in seam components, qualified component names are often used to avoid naming conflicts." msgstr "" #. Tag: programlisting @@ -946,13 +702,16 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"com.jboss.myapp.loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:513 #, no-c-format -msgid "" -"We may use the qualified component name both in Java code and in JSF's " -"expression language:" +msgid "We may use the qualified component name both in Java code and in JSF's expression language:" msgstr "" #. Tag: programlisting @@ -962,40 +721,32 @@ "<![CDATA[<h:commandButton type=\"submit\" value=\"Login\"\n" " action=\"#{com.jboss.myapp.loginAction.login}\"/>]]>" msgstr "" +"<![CDATA[<h:commandButton type=\"submit\" value=\"Login\"\n" +" action=\"#{com.jboss.myapp.loginAction.login}\"/>]]>" #. Tag: para #: Concepts.xml:519 #, no-c-format -msgid "" -"Since this is noisy, Seam also provides a means of aliasing a qualified name " -"to a simple name. Add a line like this to the <literal>components.xml</" -"literal> file:" +msgid "Since this is noisy, Seam also provides a means of aliasing a qualified name to a simple name. Add a line like this to the <literal>components.xml</literal> file:" msgstr "" #. Tag: programlisting #: Concepts.xml:524 #, no-c-format -msgid "" -"<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com." -"jboss.myapp.loginAction}\"/>]]>" -msgstr "" +msgid "<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com.jboss.myapp.loginAction}\"/>]]>" +msgstr "<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com.jboss.myapp.loginAction}\"/>]]>" #. Tag: para #: Concepts.xml:526 #, no-c-format -msgid "" -"All of the built-in Seam components have qualified names but can be accessed " -"through their unqualified names due to the namespace import feature of Seam. " -"The <literal>components.xml</literal> file included in the Seam JAR defines " -"the following namespaces." +msgid "All of the built-in Seam components have qualified names but can be accessed through their unqualified names due to the namespace import feature of Seam. The <literal>components.xml</literal> file included in the Seam JAR defines the following namespaces." msgstr "" #. Tag: programlisting #: Concepts.xml:533 #, no-c-format msgid "" -"<components xmlns="http://jboss.com/products/seam/components"" -">\n" +"<components xmlns="http://jboss.com/products/seam/components">\n" " \n" " <import>org.jboss.seam.core</import>\n" " <import>org.jboss.seam.cache</import>\n" @@ -1021,11 +772,7 @@ #. Tag: para #: Concepts.xml:535 #, no-c-format -msgid "" -"When attempting to resolve an unqualified name, Seam will check each of " -"those namespaces, in order. You can include additional namespaces in your " -"application's <literal>components.xml</literal> file for application-" -"specific namespaces." +msgid "When attempting to resolve an unqualified name, Seam will check each of those namespaces, in order. You can include additional namespaces in your application's <literal>components.xml</literal> file for application-specific namespaces." msgstr "" #. Tag: title @@ -1037,10 +784,7 @@ #. Tag: para #: Concepts.xml:544 #, no-c-format -msgid "" -"We can override the default scope (context) of a component using the " -"<literal>@Scope</literal> annotation. This lets us define what context a " -"component instance is bound to, when it is instantiated by Seam." +msgid "We can override the default scope (context) of a component using the <literal>@Scope</literal> annotation. This lets us define what context a component instance is bound to, when it is instantiated by Seam." msgstr "" #. Tag: programlisting @@ -1054,13 +798,17 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"user\")\n" +"@Entity\n" +"@Scope(SESSION)\n" +"public class User { \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:552 #, no-c-format -msgid "" -"<literal>org.jboss.seam.ScopeType</literal> defines an enumeration of " -"possible scopes." +msgid "<literal>org.jboss.seam.ScopeType</literal> defines an enumeration of possible scopes." msgstr "" #. Tag: title @@ -1072,17 +820,7 @@ #. Tag: para #: Concepts.xml:560 #, no-c-format -msgid "" -"Some Seam component classes can fulfill more than one role in the system. " -"For example, we often have a <literal>User</literal> class which is usually " -"used as a session-scoped component representing the current user but is used " -"in user administration screens as a conversation-scoped component. The " -"<literal>@Role</literal> annotation lets us define an additional named role " -"for a component, with a different scope—it lets us bind the same " -"component class to different context variables. (Any Seam component " -"<emphasis>instance</emphasis> may be bound to multiple context variables, " -"but this lets us do it at the class level, and take advantage of auto-" -"instantiation.)" +msgid "Some Seam component classes can fulfill more than one role in the system. For example, we often have a <literal>User</literal> class which is usually used as a session-scoped component representing the current user but is used in user administration screens as a conversation-scoped component. The <literal>@Role</literal> annotation lets us define an additional named role for a component, with a different scope—it lets us bind the same component class to different context variables. (Any Seam component <emphasis>instance</emphasis> may be bound to multiple context variables, but this lets us do it at the class level, and take advantage of auto-instantiation.)" msgstr "" #. Tag: programlisting @@ -1097,13 +835,18 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"user\")\n" +"@Entity\n" +"@Scope(CONVERSATION)\n" +"@Role(name=\"currentUser\", scope=SESSION)\n" +"public class User { \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:572 #, no-c-format -msgid "" -"The <literal>@Roles</literal> annotation lets us specify as many additional " -"roles as we like." +msgid "The <literal>@Roles</literal> annotation lets us specify as many additional roles as we like." msgstr "" #. Tag: programlisting @@ -1119,6 +862,14 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"user\")\n" +"@Entity\n" +"@Scope(CONVERSATION)\n" +"@Roles({@Role(name=\"currentUser\", scope=SESSION),\n" +" @Role(name=\"tempUser\", scope=EVENT)})\n" +"public class User { \n" +" ... \n" +"}]]>" #. Tag: title #: Concepts.xml:581 @@ -1129,101 +880,61 @@ #. Tag: para #: Concepts.xml:582 #, no-c-format -msgid "" -"Like many good frameworks, Seam eats its own dogfood and is implemented " -"mostly as a set of built-in Seam interceptors (see later) and Seam " -"components. This makes it easy for applications to interact with built-in " -"components at runtime or even customize the basic functionality of Seam by " -"replacing the built-in components with custom implementations. The built-in " -"components are defined in the Seam namespace <literal>org.jboss.seam.core</" -"literal> and the Java package of the same name." +msgid "Like many good frameworks, Seam eats its own dogfood and is implemented mostly as a set of built-in Seam interceptors (see later) and Seam components. This makes it easy for applications to interact with built-in components at runtime or even customize the basic functionality of Seam by replacing the built-in components with custom implementations. The built-in components are defined in the Seam namespace <literal>org.jboss.seam.core</literal> and the Java package of the same name." msgstr "" #. Tag: para #: Concepts.xml:589 #, no-c-format -msgid "" -"The built-in components may be injected, just like any Seam components, but " -"they also provide convenient static <literal>instance()</literal> methods:" +msgid "The built-in components may be injected, just like any Seam components, but they also provide convenient static <literal>instance()</literal> methods:" msgstr "" #. Tag: programlisting #: Concepts.xml:593 #, no-c-format -msgid "" -"<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>" -msgstr "" +msgid "<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>" +msgstr "<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>" #. Tag: title #: Concepts.xml:599 #, no-c-format msgid "Bijection" -msgstr "" +msgstr "Bijection" #. Tag: para #: Concepts.xml:600 #, no-c-format -msgid "" -"<emphasis>Dependency injection</emphasis> or <emphasis>inversion of control</" -"emphasis> is by now a familiar concept to most Java developers. Dependency " -"injection allows a component to obtain a reference to another component by " -"having the container \"inject\" the other component to a setter method or " -"instance variable. In all dependency injection implementations that we have " -"seen, injection occurs when the component is constructed, and the reference " -"does not subsequently change for the lifetime of the component instance. For " -"stateless components, this is reasonable. From the point of view of a " -"client, all instances of a particular stateless component are " -"interchangeable. On the other hand, Seam emphasizes the use of stateful " -"components. So traditional dependency injection is no longer a very useful " -"construct. Seam introduces the notion of <emphasis>bijection</emphasis> as a " -"generalization of injection. In contrast to injection, bijection is:" +msgid "<emphasis>Dependency injection</emphasis> or <emphasis>inversion of control</emphasis> is by now a familiar concept to most Java developers. Dependency injection allows a component to obtain a reference to another component by having the container \"inject\" the other component to a setter method or instance variable. In all dependency injection implementations that we have seen, injection occurs when the component is constructed, and the reference does not subsequently change for the lifetime of the component instance. For stateless components, this is reasonable. From the point of view of a client, all instances of a particular stateless component are interchangeable. On the other hand, Seam emphasizes the use of stateful components. So traditional dependency injection is no longer a very useful construct. Seam introduces the notion of <emphasis>bijection</emphasis> as a generalization of injection. In contrast to injection, bijection is:" msgstr "" #. Tag: para #: Concepts.xml:614 #, no-c-format -msgid "" -"<emphasis>contextual</emphasis> - bijection is used to assemble stateful " -"components from various different contexts (a component from a \"wider\" " -"context may even have a reference to a component from a \"narrower\" context)" +msgid "<emphasis>contextual</emphasis> - bijection is used to assemble stateful components from various different contexts (a component from a \"wider\" context may even have a reference to a component from a \"narrower\" context)" msgstr "" #. Tag: para #: Concepts.xml:621 #, no-c-format -msgid "" -"<emphasis>bidirectional</emphasis> - values are injected from context " -"variables into attributes of the component being invoked, and also " -"<emphasis>outjected</emphasis> from the component attributes back out to the " -"context, allowing the component being invoked to manipulate the values of " -"contextual variables simply by setting its own instance variables" +msgid "<emphasis>bidirectional</emphasis> - values are injected from context variables into attributes of the component being invoked, and also <emphasis>outjected</emphasis> from the component attributes back out to the context, allowing the component being invoked to manipulate the values of contextual variables simply by setting its own instance variables" msgstr "" #. Tag: para #: Concepts.xml:629 #, no-c-format -msgid "" -"<emphasis>dynamic</emphasis> - since the value of contextual variables " -"changes over time, and since Seam components are stateful, bijection takes " -"place every time a component is invoked" +msgid "<emphasis>dynamic</emphasis> - since the value of contextual variables changes over time, and since Seam components are stateful, bijection takes place every time a component is invoked" msgstr "" #. Tag: para #: Concepts.xml:636 #, no-c-format -msgid "" -"In essence, bijection lets you alias a context variable to a component " -"instance variable, by specifying that the value of the instance variable is " -"injected, outjected, or both. Of course, we use annotations to enable " -"bijection." +msgid "In essence, bijection lets you alias a context variable to a component instance variable, by specifying that the value of the instance variable is injected, outjected, or both. Of course, we use annotations to enable bijection." msgstr "" #. Tag: para #: Concepts.xml:642 #, no-c-format -msgid "" -"The <literal>@In</literal> annotation specifies that a value should be " -"injected, either into an instance variable:" +msgid "The <literal>@In</literal> annotation specifies that a value should be injected, either into an instance variable:" msgstr "" #. Tag: programlisting @@ -1237,6 +948,12 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" @In User user;\n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:649 @@ -1261,36 +978,35 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" User user;\n" +" \n" +" @In\n" +" public void setUser(User user) {\n" +" this.user=user;\n" +" }\n" +" \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:656 #, no-c-format -msgid "" -"By default, Seam will do a priority search of all contexts, using the name " -"of the property or instance variable that is being injected. You may wish to " -"specify the context variable name explicitly, using, for example, " -"<literal>@In(\"currentUser\")</literal>." +msgid "By default, Seam will do a priority search of all contexts, using the name of the property or instance variable that is being injected. You may wish to specify the context variable name explicitly, using, for example, <literal>@In(\"currentUser\")</literal>." msgstr "" #. Tag: para #: Concepts.xml:662 #, no-c-format -msgid "" -"If you want Seam to create an instance of the component when there is no " -"existing component instance bound to the named context variable, you should " -"specify <literal>@In(create=true)</literal>. If the value is optional (it " -"can be null), specify <literal>@In(required=false)</literal>." +msgid "If you want Seam to create an instance of the component when there is no existing component instance bound to the named context variable, you should specify <literal>@In(create=true)</literal>. If the value is optional (it can be null), specify <literal>@In(required=false)</literal>." msgstr "" #. Tag: para #: Concepts.xml:668 #, no-c-format -msgid "" -"For some components, it can be repetitive to have to specify <literal>@In" -"(create=true)</literal> everywhere they are used. In such cases, you can " -"annotate the component <literal>@AutoCreate</literal>, and then it will " -"always be created, whenever needed, even without the explicit use of " -"<literal>create=true</literal>." +msgid "For some components, it can be repetitive to have to specify <literal>@In(create=true)</literal> everywhere they are used. In such cases, you can annotate the component <literal>@AutoCreate</literal>, and then it will always be created, whenever needed, even without the explicit use of <literal>create=true</literal>." msgstr "" #. Tag: para @@ -1310,29 +1026,29 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" @In(\"#{user.username}\") String username;\n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:680 #, no-c-format -msgid "" -"Injected values are disinjected (i.e., set to <literal>null</literal>) " -"immediately after method completion and outjection." +msgid "Injected values are disinjected (i.e., set to <literal>null</literal>) immediately after method completion and outjection." msgstr "" #. Tag: para #: Concepts.xml:685 #, no-c-format -msgid "" -"(There is much more information about component lifecycle and injection in " -"the next chapter.)" +msgid "(There is much more information about component lifecycle and injection in the next chapter.)" msgstr "" #. Tag: para #: Concepts.xml:689 #, no-c-format -msgid "" -"The <literal>@Out</literal> annotation specifies that an attribute should be " -"outjected, either from an instance variable:" +msgid "The <literal>@Out</literal> annotation specifies that an attribute should be outjected, either from an instance variable:" msgstr "" #. Tag: programlisting @@ -1346,6 +1062,12 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" @Out User user;\n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:696 @@ -1370,6 +1092,18 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" User user;\n" +" \n" +" @Out\n" +" public User getUser() {\n" +" return user;\n" +" }\n" +" \n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:702 @@ -1388,12 +1122,18 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" @In @Out User user;\n" +" ... \n" +"}]]>" #. Tag: para #: Concepts.xml:708 #, no-c-format msgid "<para>or:</para>" -msgstr "" +msgstr "<para>o:</para>" #. Tag: programlisting #: Concepts.xml:712 @@ -1417,6 +1157,23 @@ " ... \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"loginAction\")\n" +"@Stateless\n" +"public class LoginAction implements Login { \n" +" User user;\n" +" \n" +" @In\n" +" public void setUser(User user) {\n" +" this.user=user;\n" +" }\n" +" \n" +" @Out\n" +" public User getUser() {\n" +" return user;\n" +" }\n" +" \n" +" ... \n" +"}]]>" #. Tag: title #: Concepts.xml:717 @@ -1427,53 +1184,31 @@ #. Tag: para #: Concepts.xml:719 #, no-c-format -msgid "" -"Session bean and entity bean Seam components support all the usual EJB 3.0 " -"lifecycle callback (<literal>@PostConstruct</literal>, <literal>@PreDestroy</" -"literal>, etc). But Seam also supports the use of any of these callbacks " -"with JavaBean components. However, since these annotations are not available " -"in a J2EE environment, Seam defines two additional component lifecycle " -"callbacks, equivalent to <literal>@PostConstruct</literal> and " -"<literal>@PreDestroy</literal>." +msgid "Session bean and entity bean Seam components support all the usual EJB 3.0 lifecycle callback (<literal>@PostConstruct</literal>, <literal>@PreDestroy</literal>, etc). But Seam also supports the use of any of these callbacks with JavaBean components. However, since these annotations are not available in a J2EE environment, Seam defines two additional component lifecycle callbacks, equivalent to <literal>@PostConstruct</literal> and <literal>@PreDestroy</literal>." msgstr "" #. Tag: para #: Concepts.xml:727 #, no-c-format -msgid "" -"The <literal>@Create</literal> method is called after Seam instantiates a " -"component. Components may define only one <literal>@Create</literal> method." +msgid "The <literal>@Create</literal> method is called after Seam instantiates a component. Components may define only one <literal>@Create</literal> method." msgstr "" #. Tag: para #: Concepts.xml:732 #, no-c-format -msgid "" -"The <literal>@Destroy</literal> method is called when the context that the " -"Seam component is bound to ends. Components may define only one " -"<literal>@Destroy</literal> method." +msgid "The <literal>@Destroy</literal> method is called when the context that the Seam component is bound to ends. Components may define only one <literal>@Destroy</literal> method." msgstr "" #. Tag: para #: Concepts.xml:737 #, no-c-format -msgid "" -"In addition, stateful session bean components <emphasis>must</emphasis> " -"define a method with no parameters annotated <literal>@Remove</literal>. " -"This method is called by Seam when the context ends." +msgid "In addition, stateful session bean components <emphasis>must</emphasis> define a method with no parameters annotated <literal>@Remove</literal>. This method is called by Seam when the context ends." msgstr "" #. Tag: para #: Concepts.xml:742 #, no-c-format -msgid "" -"Finally, a related annotation is the <literal>@Startup</literal> annotation, " -"which may be applied to any application or session scoped component. The " -"<literal>@Startup</literal> annotation tells Seam to instantiate the " -"component immediately, when the context begins, instead of waiting until it " -"is first referenced by a client. It is possible to control the order of " -"instantiation of startup components by specifying <literal>@Startup(depends=" -"{....})</literal>." +msgid "Finally, a related annotation is the <literal>@Startup</literal> annotation, which may be applied to any application or session scoped component. The <literal>@Startup</literal> annotation tells Seam to instantiate the component immediately, when the context begins, instead of waiting until it is first referenced by a client. It is possible to control the order of instantiation of startup components by specifying <literal>@Startup(depends={....})</literal>." msgstr "" #. Tag: title @@ -1485,10 +1220,7 @@ #. Tag: para #: Concepts.xml:755 #, no-c-format -msgid "" -"The <literal>@Install</literal> annotation lets you control conditional " -"installation of components that are required in some deployment scenarios " -"and not in others. This is useful if:" +msgid "The <literal>@Install</literal> annotation lets you control conditional installation of components that are required in some deployment scenarios and not in others. This is useful if:" msgstr "" #. Tag: para @@ -1500,69 +1232,49 @@ #. Tag: para #: Concepts.xml:767 #, no-c-format -msgid "" -"You want change the implementation of a component in certain deployment " -"scenarios." +msgid "You want change the implementation of a component in certain deployment scenarios." msgstr "" #. Tag: para #: Concepts.xml:773 #, no-c-format -msgid "" -"You want to install some components only if their dependencies are available " -"(useful for framework authors)." +msgid "You want to install some components only if their dependencies are available (useful for framework authors)." msgstr "" #. Tag: para #: Concepts.xml:780 #, no-c-format -msgid "" -"<literal>@Install</literal> works by letting you specify " -"<emphasis>precedence</emphasis> and <emphasis>dependencies</emphasis>." +msgid "<literal>@Install</literal> works by letting you specify <emphasis>precedence</emphasis> and <emphasis>dependencies</emphasis>." msgstr "" #. Tag: para #: Concepts.xml:785 #, no-c-format -msgid "" -"The precedence of a component is a number that Seam uses to decide which " -"component to install when there are multiple classes with the same component " -"name in the classpath. Seam will choose the component with the higher " -"precendence. There are some predefined precedence values (in ascending " -"order):" +msgid "The precedence of a component is a number that Seam uses to decide which component to install when there are multiple classes with the same component name in the classpath. Seam will choose the component with the higher precendence. There are some predefined precedence values (in ascending order):" msgstr "" #. Tag: para #: Concepts.xml:794 #, no-c-format -msgid "" -"<literal>BUILT_IN</literal> — the lowest precedece components are the " -"components built in to Seam." +msgid "<literal>BUILT_IN</literal> — the lowest precedece components are the components built in to Seam." msgstr "" #. Tag: para #: Concepts.xml:800 #, no-c-format -msgid "" -"<literal>FRAMEWORK</literal> — components defined by third-party " -"frameworks may override built-in components, but are overridden by " -"application components." +msgid "<literal>FRAMEWORK</literal> — components defined by third-party frameworks may override built-in components, but are overridden by application components." msgstr "" #. Tag: para #: Concepts.xml:807 #, no-c-format -msgid "" -"<literal>APPLICATION</literal> — the default precedence. This is " -"appropriate for most application components." +msgid "<literal>APPLICATION</literal> — the default precedence. This is appropriate for most application components." msgstr "" #. Tag: para #: Concepts.xml:813 #, no-c-format -msgid "" -"<literal>DEPLOYMENT</literal> — for application components which are " -"deployment-specific." +msgid "<literal>DEPLOYMENT</literal> — for application components which are deployment-specific." msgstr "" #. Tag: para @@ -1574,9 +1286,7 @@ #. Tag: para #: Concepts.xml:825 #, no-c-format -msgid "" -"Suppose we have a component named <literal>messageSender</literal> that " -"talks to a JMS queue." +msgid "Suppose we have a component named <literal>messageSender</literal> that talks to a JMS queue." msgstr "" #. Tag: programlisting @@ -1590,15 +1300,17 @@ " }\n" "}]]>" msgstr "" +"<![CDATA[@Name(\"messageSender\") \n" +"public class MessageSender {\n" +" public void sendMessage() {\n" +" //do something with JMS\n" +" }\n" +"}]]>" #. Tag: para #: Concepts.xml:832 #, no-c-format -msgid "" -"In our unit tests, we don't have a JMS queue available, so we would like to " -"stub out this method. We'll create a <emphasis>mock</emphasis> component " -"that exists in the classpath when unit tests are running, but is never " -"deployed with the application:" +msgid "In our unit tests, we don't have a JMS queue available, so we would like to stub out this method. We'll create a <emphasis>mock</emphasis> component that exists in the classpath when unit tests are running, but is never deployed with the application:" msgstr "" #. Tag: programlisting @@ -1613,35 +1325,31 @@ " }\n" "}]]>" msgstr "" +"<![CDATA[@Name(\"messageSender\") \n" +"@Install(precedence=MOCK)\n" +"public class MockMessageSender extends MessageSender {\n" +" public void sendMessage() {\n" +" //do nothing!\n" +" }\n" +"}]]>" #. Tag: para #: Concepts.xml:841 #, no-c-format -msgid "" -"The <literal>precedence</literal> helps Seam decide which version to use " -"when it finds both components in the classpath." +msgid "The <literal>precedence</literal> helps Seam decide which version to use when it finds both components in the classpath." msgstr "" #. Tag: para #: Concepts.xml:846 #, no-c-format -msgid "" -"This is nice if we are able to control exactly which classes are in the " -"classpath. But if I'm writing a reusable framework with many dependecies, I " -"don't want to have to break that framework across many jars. I want to be " -"able to decide which components to install depending upon what other " -"components are installed, and upon what classes are available in the " -"classpath. The <literal>@Install</literal> annotation also controls this " -"functionality. Seam uses this mechanism internally to enable conditional " -"installation of many of the built-in components. However, you probably won't " -"need to use it in your application." +msgid "This is nice if we are able to control exactly which classes are in the classpath. But if I'm writing a reusable framework with many dependecies, I don't want to have to break that framework across many jars. I want to be able to decide which components to install depending upon what other components are installed, and upon what classes are available in the classpath. The <literal>@Install</literal> annotation also controls this functionality. Seam uses this mechanism internally to enable conditional installation of many of the built-in components. However, you probably won't need to use it in your application." msgstr "" #. Tag: title #: Concepts.xml:860 #, no-c-format msgid "Logging" -msgstr "" +msgstr "Logging" #. Tag: para #: Concepts.xml:862 @@ -1653,8 +1361,7 @@ #: Concepts.xml:866 #, no-c-format msgid "" -"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction." -"class);\n" +"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction.class);\n" " \n" "public Order createOrder(User user, Product product, int quantity) {\n" " if ( log.isDebugEnabled() ) {\n" @@ -1665,15 +1372,21 @@ " return new Order(user, product, quantity);\n" "}]]>" msgstr "" +"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction.class);\n" +" \n" +"public Order createOrder(User user, Product product, int quantity) {\n" +" if ( log.isDebugEnabled() ) {\n" +" log.debug(\"Creating new order for user: \" + user.username() + \n" +" \" product: \" + product.name() \n" +" + \" quantity: \" + quantity);\n" +" }\n" +" return new Order(user, product, quantity);\n" +"}]]>" #. Tag: para #: Concepts.xml:868 #, no-c-format -msgid "" -"It is difficult to imagine how the code for a simple log message could " -"possibly be more verbose. There is more lines of code tied up in logging " -"than in the actual business logic! I remain totally astonished that the Java " -"community has not come up with anything better in 10 years." +msgid "It is difficult to imagine how the code for a simple log message could possibly be more verbose. There is more lines of code tied up in logging than in the actual business logic! I remain totally astonished that the Java community has not come up with anything better in 10 years." msgstr "" #. Tag: para @@ -1689,38 +1402,33 @@ "<![CDATA[@Logger private Log log;\n" " \n" "public Order createOrder(User user, Product product, int quantity) {\n" -" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", " -"user.username(), product.name(), quantity);\n" +" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", user.username(), product.name(), quantity);\n" " return new Order(user, product, quantity);\n" "}]]>" msgstr "" +"<![CDATA[@Logger private Log log;\n" +" \n" +"public Order createOrder(User user, Product product, int quantity) {\n" +" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", user.username(), product.name(), quantity);\n" +" return new Order(user, product, quantity);\n" +"}]]>" #. Tag: para #: Concepts.xml:880 #, no-c-format -msgid "" -"It doesn't matter if you declare the <literal>log</literal> variable static " -"or not—it will work either way, except for entity bean components " -"which require the <literal>log</literal> variable to be static." +msgid "It doesn't matter if you declare the <literal>log</literal> variable static or not—it will work either way, except for entity bean components which require the <literal>log</literal> variable to be static." msgstr "" #. Tag: para #: Concepts.xml:886 #, no-c-format -msgid "" -"Note that we don't need the noisy <literal>if ( log.isDebugEnabled() )</" -"literal> guard, since string concatenation happens <emphasis>inside</" -"emphasis> the <literal>debug()</literal> method. Note also that we don't " -"usually need to specify the log category explicitly, since Seam knows what " -"component it is injecting the <literal>Log</literal> into." +msgid "Note that we don't need the noisy <literal>if ( log.isDebugEnabled() )</literal> guard, since string concatenation happens <emphasis>inside</emphasis> the <literal>debug()</literal> method. Note also that we don't usually need to specify the log category explicitly, since Seam knows what component it is injecting the <literal>Log</literal> into." msgstr "" #. Tag: para #: Concepts.xml:901 #, no-c-format -msgid "" -"If <literal>User</literal> and <literal>Product</literal> are Seam " -"components available in the current contexts, it gets even better:" +msgid "If <literal>User</literal> and <literal>Product</literal> are Seam components available in the current contexts, it gets even better:" msgstr "" #. Tag: programlisting @@ -1730,67 +1438,45 @@ "<![CDATA[@Logger private Log log;\n" " \n" "public Order createOrder(User user, Product product, int quantity) {\n" -" log.debug(\"Creating new order for user: #{user.username} product: #" -"{product.name} quantity: #0\", quantity);\n" +" log.debug(\"Creating new order for user: #{user.username} product: #{product.name} quantity: #0\", quantity);\n" " return new Order(user, product, quantity);\n" "}]]>" msgstr "" +"<![CDATA[@Logger private Log log;\n" +" \n" +"public Order createOrder(User user, Product product, int quantity) {\n" +" log.debug(\"Creating new order for user: #{user.username} product: #{product.name} quantity: #0\", quantity);\n" +" return new Order(user, product, quantity);\n" +"}]]>" #. Tag: para #: Concepts.xml:908 #, no-c-format -msgid "" -"Seam logging automagically chooses whether to send output to log4j or JDK " -"logging. If log4j is in the classpath, Seam with use it. If it is not, Seam " -"will use JDK logging." +msgid "Seam logging automagically chooses whether to send output to log4j or JDK logging. If log4j is in the classpath, Seam with use it. If it is not, Seam will use JDK logging." msgstr "" #. Tag: title #: Concepts.xml:916 #, no-c-format -msgid "" -"The <literal>Mutable</literal> interface and <literal>@ReadOnly</literal>" +msgid "The <literal>Mutable</literal> interface and <literal>@ReadOnly</literal>" msgstr "" #. Tag: para #: Concepts.xml:917 #, no-c-format -msgid "" -"Many application servers feature an amazingly broken implementation of " -"<literal>HttpSession</literal> clustering, where changes to the state of " -"mutable objects bound to the session are only replicated when the " -"application calls <literal>setAttribute()</literal> explicitly. This is a " -"source of bugs that can not effectively be tested for at development time, " -"since they will only manifest when failover occurs. Furthermore, the actual " -"replication message contains the entire serialized object graph bound to the " -"session attribute, which is inefficient." +msgid "Many application servers feature an amazingly broken implementation of <literal>HttpSession</literal> clustering, where changes to the state of mutable objects bound to the session are only replicated when the application calls <literal>setAttribute()</literal> explicitly. This is a source of bugs that can not effectively be tested for at development time, since they will only manifest when failover occurs. Furthermore, the actual replication message contains the entire serialized object graph bound to the session attribute, which is inefficient." msgstr "" #. Tag: para #: Concepts.xml:926 #, no-c-format -msgid "" -"Of course, EJB stateful session beans must perform automatic dirty checking " -"and replication of mutable state and a sophisticated EJB container can " -"introduce optimizations such as attribute-level replication. Unfortunately, " -"not all Seam users have the good fortune to be working in an environment " -"that supports EJB 3.0. So, for session and conversation scoped JavaBean and " -"entity bean components, Seam provides an extra layer of cluster-safe state " -"management over the top of the web container session clustering." +msgid "Of course, EJB stateful session beans must perform automatic dirty checking and replication of mutable state and a sophisticated EJB container can introduce optimizations such as attribute-level replication. Unfortunately, not all Seam users have the good fortune to be working in an environment that supports EJB 3.0. So, for session and conversation scoped JavaBean and entity bean components, Seam provides an extra layer of cluster-safe state management over the top of the web container session clustering." msgstr "" #. Tag: para #: Concepts.xml:934 #, no-c-format -msgid "" -"For session or conversation scoped JavaBean components, Seam automatically " -"forces replication to occur by calling <literal>setAttribute()</literal> " -"once in every request that the component was invoked by the application. Of " -"course, this strategy is inefficient for read-mostly components. You can " -"control this behavior by implementing the <literal>org.jboss.seam.core." -"Mutable</literal> interface, or by extending <literal>org.jboss.seam.core." -"AbstractMutable</literal>, and writing your own dirty-checking logic inside " -"the component. For example," +msgid "For session or conversation scoped JavaBean components, Seam automatically forces replication to occur by calling <literal>setAttribute()</literal> once in every request that the component was invoked by the application. Of course, this strategy is inefficient for read-mostly components. You can control this behavior by implementing the <literal>org.jboss.seam.core.Mutable</literal> interface, or by extending <literal>org.jboss.seam.core.AbstractMutable</literal>, and writing your own dirty-checking logic inside the component. For example," msgstr "" #. Tag: programlisting @@ -1817,13 +1503,30 @@ " \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"account\")\n" +"public class Account extends AbstractMutable\n" +"{\n" +" private BigDecimal balance;\n" +" \n" +" public void setBalance(BigDecimal balance)\n" +" {\n" +" setDirty(this.balance, balance);\n" +" this.balance = balance;\n" +" }\n" +" \n" +" public BigDecimal getBalance()\n" +" {\n" +" return balance;\n" +" }\n" +" \n" +" ...\n" +" \n" +"}]]>" #. Tag: para #: Concepts.xml:945 #, no-c-format -msgid "" -"Or, you can use the <literal>@ReadOnly</literal> annotation to achieve a " -"similar effect:" +msgid "Or, you can use the <literal>@ReadOnly</literal> annotation to achieve a similar effect:" msgstr "" #. Tag: programlisting @@ -1850,19 +1553,30 @@ " \n" "}]]>" msgstr "" +"<![CDATA[@Name(\"account\")\n" +"public class Account\n" +"{\n" +" private BigDecimal balance;\n" +" \n" +" public void setBalance(BigDecimal balance)\n" +" {\n" +" this.balance = balance;\n" +" }\n" +" \n" +" @ReadOnly\n" +" public BigDecimal getBalance()\n" +" {\n" +" return balance;\n" +" }\n" +" \n" +" ...\n" +" \n" +"}]]>" #. Tag: para #: Concepts.xml:951 #, no-c-format -msgid "" -"For session or conversation scoped entity bean components, Seam " -"automatically forces replication to occur by calling <literal>setAttribute()" -"</literal> once in every request, <emphasis>unless the (conversation-scoped) " -"entity is currently associated with a Seam-managed persistence context, in " -"which case no replication is needed</emphasis>. This strategy is not " -"necessarily efficient, so session or conversation scope entity beans should " -"be used with care. You can always write a stateful session bean or JavaBean " -"component to \"manage\" the entity bean instance. For example," +msgid "For session or conversation scoped entity bean components, Seam automatically forces replication to occur by calling <literal>setAttribute()</literal> once in every request, <emphasis>unless the (conversation-scoped) entity is currently associated with a Seam-managed persistence context, in which case no replication is needed</emphasis>. This strategy is not necessarily efficient, so session or conversation scope entity beans should be used with care. You can always write a stateful session bean or JavaBean component to \"manage\" the entity bean instance. For example," msgstr "" #. Tag: programlisting @@ -1885,14 +1599,26 @@ " \n" "}]]>" msgstr "" +"<![CDATA[@Stateful\n" +"@Name(\"account\")\n" +"public class AccountManager extends AbstractMutable\n" +"{\n" +" private Account account; // an entity bean\n" +" \n" +" @Unwrap\n" +" public Account getAccount()\n" +" {\n" +" return account;\n" +" }\n" +" \n" +" ...\n" +" \n" +"}]]>" #. Tag: para #: Concepts.xml:962 #, no-c-format -msgid "" -"Note that the <literal>EntityHome</literal> class in the Seam Application " -"Framework provides a great example of managing an entity bean instance using " -"a Seam component." +msgid "Note that the <literal>EntityHome</literal> class in the Seam Application Framework provides a great example of managing an entity bean instance using a Seam component." msgstr "" #. Tag: title @@ -1904,29 +1630,13 @@ #. Tag: para #: Concepts.xml:971 #, no-c-format -msgid "" -"We often need to work with objects that are not Seam components. But we " -"still want to be able to inject them into our components using <literal>@In</" -"literal> and use them in value and method binding expressions, etc. " -"Sometimes, we even need to tie them into the Seam context lifecycle " -"(<literal>@Destroy</literal>, for example). So the Seam contexts can contain " -"objects which are not Seam components, and Seam provides a couple of nice " -"features that make it easier to work with non-component objects bound to " -"contexts." +msgid "We often need to work with objects that are not Seam components. But we still want to be able to inject them into our components using <literal>@In</literal> and use them in value and method binding expressions, etc. Sometimes, we even need to tie them into the Seam context lifecycle (<literal>@Destroy</literal>, for example). So the Seam contexts can contain objects which are not Seam components, and Seam provides a couple of nice features that make it easier to work with non-component objects bound to contexts." msgstr "" #. Tag: para #: Concepts.xml:979 #, no-c-format -msgid "" -"The <emphasis>factory component pattern</emphasis> lets a Seam component act " -"as the instantiator for a non-component object. A <emphasis>factory method</" -"emphasis> will be called when a context variable is referenced but has no " -"value bound to it. We define factory methods using the <literal>@Factory</" -"literal> annotation. The factory method binds a value to the context " -"variable, and determines the scope of the bound value. There are two styles " -"of factory method. The first style returns a value, which is bound to the " -"context by Seam:" +msgid "The <emphasis>factory component pattern</emphasis> lets a Seam component act as the instantiator for a non-component object. A <emphasis>factory method</emphasis> will be called when a context variable is referenced but has no value bound to it. We define factory methods using the <literal>@Factory</literal> annotation. The factory method binds a value to the context variable, and determines the scope of the bound value. There are two styles of factory method. The first style returns a value, which is bound to the context by Seam:" msgstr "" #. Tag: programlisting @@ -1938,13 +1648,15 @@ " return ... ;\n" "} ]]>" msgstr "" +"<![CDATA[@Factory(scope=CONVERSATION)\n" +"public List<Customer> getCustomerList() { \n" +" return ... ;\n" +"} ]]>" #. Tag: para #: Concepts.xml:990 #, no-c-format -msgid "" -"The second style is a method of type <literal>void</literal> which binds the " -"value to the context variable itself:" +msgid "The second style is a method of type <literal>void</literal> which binds the value to the context variable itself:" msgstr "" #. Tag: programlisting @@ -1958,27 +1670,23 @@ " customerList = ... ;\n" "} ]]>" msgstr "" +"<![CDATA[@DataModel List<Customer> customerList;\n" +"\n" +"@Factory(\"customerList\")\n" +"public void initCustomerList() { \n" +" customerList = ... ;\n" +"} ]]>" #. Tag: para #: Concepts.xml:997 #, no-c-format -msgid "" -"In both cases, the factory method is called when we reference the " -"<literal>customerList</literal> context variable and its value is null, and " -"then has no further part to play in the lifecycle of the value. An even more " -"powerful pattern is the <emphasis>manager component pattern</emphasis>. In " -"this case, we have a Seam component that is bound to a context variable, " -"that manages the value of the context variable, while remaining invisible to " -"clients." +msgid "In both cases, the factory method is called when we reference the <literal>customerList</literal> context variable and its value is null, and then has no further part to play in the lifecycle of the value. An even more powerful pattern is the <emphasis>manager component pattern</emphasis>. In this case, we have a Seam component that is bound to a context variable, that manages the value of the context variable, while remaining invisible to clients." msgstr "" #. Tag: para #: Concepts.xml:1005 #, no-c-format -msgid "" -"A manager component is any component with an <literal>@Unwrap</literal> " -"method. This method returns the value that will be visable to clients, and " -"is called <emphasis>every time</emphasis> a context variable is referenced." +msgid "A manager component is any component with an <literal>@Unwrap</literal> method. This method returns the value that will be visable to clients, and is called <emphasis>every time</emphasis> a context variable is referenced." msgstr "" #. Tag: programlisting @@ -1997,17 +1705,22 @@ " }\n" "}]]>" msgstr "" +"<![CDATA[@Name(\"customerList\")\n" +"@Scope(CONVERSATION)\n" +"public class CustomerListManager\n" +"{\n" +" ...\n" +" \n" +" @Unwrap\n" +" public List<Customer> getCustomerList() { \n" +" return ... ;\n" +" }\n" +"}]]>" #. Tag: para #: Concepts.xml:1015 #, no-c-format -msgid "" -"The manager component pattern is especially useful if we have an object " -"where you need more control over the lifecycle of the component. For " -"example, if you have a heavyweight object that needs a cleanup operation " -"when the context ends you could <literal>@Unwrap</literal> the object, and " -"perform cleanup in the <literal>@Destroy</literal> method of the manager " -"component." +msgid "The manager component pattern is especially useful if we have an object where you need more control over the lifecycle of the component. For example, if you have a heavyweight object that needs a cleanup operation when the context ends you could <literal>@Unwrap</literal> the object, and perform cleanup in the <literal>@Destroy</literal> method of the manager component." msgstr "" #. Tag: programlisting @@ -2052,12 +1765,47 @@ " ...\n" "}]]>" msgstr "" +"<![CDATA[@Name(\"hens\")\n" +"@Scope(APPLICATION) \n" +"public class HenHouse\n" +"{\n" +" Set<Hen> hens;\n" +" \n" +" @In(required=false) Hen hen;\n" +" \n" +" @Unwrap\n" +" public List<Hen> getHens()\n" +" {\n" +" if (hens == null)\n" +" {\n" +" // Setup our hens\n" +" }\n" +" return hens;\n" +" }\n" +" \n" +" @Observer({\"chickBorn\", \"chickenBoughtAtMarket\"})\n" +" public addHen()\n" +" {\n" +" hens.add(hen);\n" +" }\n" +" \n" +" @Observer(\"chickenSoldAtMarket\")\n" +" public removeHen()\n" +" {\n" +" hens.remove(hen);\n" +" }\n" +" \n" +" @Observer(\"foxGetsIn\")\n" +" public removeAllHens()\n" +" {\n" +" hens.clear();\n" +" }\n" +" ...\n" +"}]]>" #. Tag: para #: Concepts.xml:1024 #, no-c-format -msgid "" -"Here the managed component observes many events which change the underlying " -"object. The component manages these actions itself, and because the object " -"is unwrapped on every access, a consistent view is provided." +msgid "Here the managed component observes many events which change the underlying object. The component manages these actions itself, and because the object is unwrapped on every access, a consistent view is provided." msgstr "" + Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-12 14:44:37 UTC (rev 9762) +++ trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-12 14:45:51 UTC (rev 9763) @@ -6,8 +6,8 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-04-04 01:24+0000\n" -"PO-Revision-Date: 2008-04-04 01:24+0000\n" -"Last-Translator: Automatically generated\n" +"PO-Revision-Date: 2008-12-12 15:38+0100\n" +"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,45 +17,37 @@ #: Elenhancements.xml:5 #, no-c-format msgid "JBoss EL" -msgstr "" +msgstr "JBoss EL" #. Tag: para #: Elenhancements.xml:7 #, no-c-format -msgid "" -"Seam uses JBoss EL which provides an extension to the standard Unified " -"Expression Language (EL). JBoss EL provides a number of enhancements that " -"increase the expressiveness and power of EL expressions." +msgid "Seam uses JBoss EL which provides an extension to the standard Unified Expression Language (EL). JBoss EL provides a number of enhancements that increase the expressiveness and power of EL expressions." msgstr "" #. Tag: title #: Elenhancements.xml:14 #, no-c-format msgid "Parameterized Expressions" -msgstr "" +msgstr "Espressioni parametrizzate" #. Tag: para #: Elenhancements.xml:16 #, no-c-format -msgid "" -"Standard EL does not allow you to use a method with user defined parameters " -"— of course, JSF listener methods (e.g. a " -"<literal>valueChangeListener</literal>) take parameters provided by JSF." +msgid "Standard EL does not allow you to use a method with user defined parameters — of course, JSF listener methods (e.g. a <literal>valueChangeListener</literal>) take parameters provided by JSF." msgstr "" #. Tag: para #: Elenhancements.xml:22 #, no-c-format msgid "JBoss EL removes this restriction. For example:" -msgstr "" +msgstr "JBoss EL rimuove questa restrizione. Per esempio:" #. Tag: programlisting #: Elenhancements.xml:26 #, no-c-format -msgid "" -"<![CDATA[<h:commandButton action=\"#{hotelBooking.bookHotel(hotel)}\" value=" -"\"Book Hotel\"/>]]>" -msgstr "" +msgid "<![CDATA[<h:commandButton action=\"#{hotelBooking.bookHotel(hotel)}\" value=\"Book Hotel\"/>]]>" +msgstr "<![CDATA[<h:commandButton action=\"#{hotelBooking.bookHotel(hotel)}\" value=\"Book Hotel\"/>]]>" #. Tag: programlisting #: Elenhancements.xml:28 @@ -69,36 +61,36 @@ " }\n" "}]]>" msgstr "" +"<![CDATA[@Name(\"hotelBooking\")\n" +"public class HotelBooking {\n" +" \n" +" public String bookHotel(Hotel hotel) {\n" +" // Book the hotel\n" +" }\n" +"}]]>" #. Tag: title #: Elenhancements.xml:31 #, no-c-format msgid "Usage" -msgstr "" +msgstr "Utilizzo" #. Tag: para #: Elenhancements.xml:33 #, no-c-format -msgid "" -"Just as in calls to method from Java, parameters are surrounded by " -"parentheses, and separated by commas:" +msgid "Just as in calls to method from Java, parameters are surrounded by parentheses, and separated by commas:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:38 #, no-c-format -msgid "" -"<![CDATA[<h:commandButton action=\"#{hotelBooking.bookHotel(hotel, user)}\" " -"value=\"Book Hotel\"/>]]>" -msgstr "" +msgid "<![CDATA[<h:commandButton action=\"#{hotelBooking.bookHotel(hotel, user)}\" value=\"Book Hotel\"/>]]>" +msgstr "<![CDATA[<h:commandButton action=\"#{hotelBooking.bookHotel(hotel, user)}\" value=\"Book Hotel\"/>]]>" #. Tag: para #: Elenhancements.xml:40 #, no-c-format -msgid "" -"The parameters <literal>hotel</literal> and <literal>user</literal> will be " -"evaluated as value expressions and passed to the <literal>bookHotel()</" -"literal> method of the component." +msgid "The parameters <literal>hotel</literal> and <literal>user</literal> will be evaluated as value expressions and passed to the <literal>bookHotel()</literal> method of the component." msgstr "" #. Tag: para @@ -115,26 +107,20 @@ " action=\"#{hotelBooking.bookHotel(hotel.id, user.username)}\" \n" " value=\"Book Hotel\"/>]]>" msgstr "" +"<![CDATA[<h:commandButton \n" +" action=\"#{hotelBooking.bookHotel(hotel.id, user.username)}\" \n" +" value=\"Book Hotel\"/>]]>" #. Tag: para #: Elenhancements.xml:51 #, no-c-format -msgid "" -"It's important to fully understand how this extension to EL works. When the " -"page is rendered, the parameter <emphasis>names</emphasis> are stored (for " -"example, <literal>hotel.id</literal> and <literal>user.username</literal>), " -"and evaluated (as value expressions) when the page is submitted. You can't " -"pass objects as parameters!" +msgid "It's important to fully understand how this extension to EL works. When the page is rendered, the parameter <emphasis>names</emphasis> are stored (for example, <literal>hotel.id</literal> and <literal>user.username</literal>), and evaluated (as value expressions) when the page is submitted. You can't pass objects as parameters!" msgstr "" #. Tag: para #: Elenhancements.xml:60 #, no-c-format -msgid "" -"You must ensure that the parameters are available not only when the page is " -"rendered, but also when it is submittedIf the arguments can not be resolved " -"when the page is submitted the action method will be called with " -"<literal>null</literal> arguments!" +msgid "You must ensure that the parameters are available not only when the page is rendered, but also when it is submittedIf the arguments can not be resolved when the page is submitted the action method will be called with <literal>null</literal> arguments!" msgstr "" #. Tag: para @@ -146,38 +132,26 @@ #. Tag: programlisting #: Elenhancements.xml:71 #, no-c-format -msgid "" -"<![CDATA[<h:commandLink action=\"#{printer.println('Hello world!')}\" value=" -"\"Hello\"/>]]>" -msgstr "" +msgid "<![CDATA[<h:commandLink action=\"#{printer.println('Hello world!')}\" value=\"Hello\"/>]]>" +msgstr "<![CDATA[<h:commandLink action=\"#{printer.println('Hello world!')}\" value=\"Hello\"/>]]>" #. Tag: para #: Elenhancements.xml:73 #, no-c-format -msgid "" -"Unified EL also supports value expressions, used to bind a field to a " -"backing bean. Value expressions use JavaBean naming conventions and expect a " -"getter/setter pair. Often JSF expects a value expression where only " -"retrieval (get) is needed (e.g. the <literal>rendered</literal> attribute). " -"Many objects, however, don't have appropriately named property accessors or " -"require parameters." +msgid "Unified EL also supports value expressions, used to bind a field to a backing bean. Value expressions use JavaBean naming conventions and expect a getter/setter pair. Often JSF expects a value expression where only retrieval (get) is needed (e.g. the <literal>rendered</literal> attribute). Many objects, however, don't have appropriately named property accessors or require parameters." msgstr "" #. Tag: para #: Elenhancements.xml:82 #, no-c-format -msgid "" -"JBoss EL removes this restriction by allowing values to be retrieved using " -"the method syntax. For example:" +msgid "JBoss EL removes this restriction by allowing values to be retrieved using the method syntax. For example:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:87 #, no-c-format -msgid "" -"<![CDATA[<h:outputText value=\"#{person.name}\" rendered=\"#{person.name." -"length() > 5}\" />]]>" -msgstr "" +msgid "<![CDATA[<h:outputText value=\"#{person.name}\" rendered=\"#{person.name.length() > 5}\" />]]>" +msgstr "<![CDATA[<h:outputText value=\"#{person.name}\" rendered=\"#{person.name.length() > 5}\" />]]>" #. Tag: para #: Elenhancements.xml:89 @@ -189,35 +163,31 @@ #: Elenhancements.xml:93 #, no-c-format msgid "#{searchResults.size()}" -msgstr "" +msgstr "<![CDATA[<h:outputText value=\"#{person.name}\" rendered=\"#{person.name.length() > 5}\" />]]>" #. Tag: para #: Elenhancements.xml:95 #, no-c-format -msgid "" -"In general any expression of the form #{obj.property} would be identical to " -"the expression #{obj.getProperty()}." -msgstr "" +msgid "In general any expression of the form #{obj.property} would be identical to the expression #{obj.getProperty()}." +msgstr "In generale qualsiasi espressione nella forma #{obj.property} è identica all'espressione #{obj.getProperty()}." #. Tag: para #: Elenhancements.xml:99 #, no-c-format -msgid "" -"Parameters are also allowed. The following example calls the " -"<literal>productsByColorMethod</literal> with a literal string argument:" +msgid "Parameters are also allowed. The following example calls the <literal>productsByColorMethod</literal> with a literal string argument:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:105 #, no-c-format msgid "#{controller.productsByColor('blue')}" -msgstr "" +msgstr "#{controller.productsByColor('blue')}" #. Tag: title #: Elenhancements.xml:110 #, no-c-format msgid "Limitations and Hints" -msgstr "" +msgstr "Limitazioni e suggerimenti" #. Tag: para #: Elenhancements.xml:112 @@ -228,23 +198,13 @@ #. Tag: para #: Elenhancements.xml:118 #, no-c-format -msgid "" -"<emphasis>Incompatibility with JSP 2.1</emphasis> — JBoss EL can't " -"currently be used with JSP 2.1 as the compiler rejects expressions with " -"parameters in. So, if you want to use this extension with JSF 1.2, you will " -"need to use Facelets. The extension works correctly with JSP 2.0." +msgid "<emphasis>Incompatibility with JSP 2.1</emphasis> — JBoss EL can't currently be used with JSP 2.1 as the compiler rejects expressions with parameters in. So, if you want to use this extension with JSF 1.2, you will need to use Facelets. The extension works correctly with JSP 2.0." msgstr "" #. Tag: para #: Elenhancements.xml:127 #, no-c-format -msgid "" -"<emphasis>Use inside iterative components</emphasis> — Components like " -"<literal><c:forEach /></literal> and <literal><ui:repeat /></" -"literal>iterate over a List or array, exposing each item in the list to " -"nested components. This works great if you are selecting a row using a " -"<literal><h:commandButton /></literal> or <literal><h:commandLink /" -"></literal>:" +msgid "<emphasis>Use inside iterative components</emphasis> — Components like <literal><c:forEach /></literal> and <literal><ui:repeat /></literal>iterate over a List or array, exposing each item in the list to nested components. This works great if you are selecting a row using a <literal><h:commandButton /></literal> or <literal><h:commandLink /></literal>:" msgstr "" #. Tag: programlisting @@ -256,6 +216,10 @@ " return entityManager.createQuery(\"select ...\").getResultList();\n" "}]]>" msgstr "" +"<![CDATA[@Factory(\"items\")\n" +"public List<Item> getItems() {\n" +" return entityManager.createQuery(\"select ...\").getResultList();\n" +"}]]>" #. Tag: programlisting #: Elenhancements.xml:137 @@ -263,176 +227,133 @@ msgid "" "<![CDATA[<h:dataTable value=\"#{items}\" var=\"item\">\n" " <h:column>\n" -" <h:commandLink value=\"Select #{item.name}\" action=\"#{itemSelector." -"select(item})\" />\n" +" <h:commandLink value=\"Select #{item.name}\" action=\"#{itemSelector.select(item})\" />\n" " </h:column>\n" "</h:dataTable>]]>" msgstr "" +"<![CDATA[<h:dataTable value=\"#{items}\" var=\"item\">\n" +" <h:column>\n" +" <h:commandLink value=\"Select #{item.name}\" action=\"#{itemSelector.select(item})\" />\n" +" </h:column>\n" +"</h:dataTable>]]>" #. Tag: para #: Elenhancements.xml:138 #, no-c-format -msgid "" -"However if you want to use <literal><s:link /></literal> or " -"<literal><s:button /></literal> you <emphasis>must</emphasis> expose " -"the items as a <literal>DataModel</literal>, and use a <literal><" -"dataTable /></literal> (or equivalent from a component set like " -"<literal><rich:dataTable /></literal> ). Neither <literal><s:link /" -"></literal> or <literal><s:button /></literal> submit the form (and " -"therefore produce a bookmarkable link) so a \"magic\" parameter is needed to " -"recreate the item when the action method is called. This magic parameter can " -"only be added when a data table backed by a <literal>DataModel</literal> is " -"used." +msgid "However if you want to use <literal><s:link /></literal> or <literal><s:button /></literal> you <emphasis>must</emphasis> expose the items as a <literal>DataModel</literal>, and use a <literal><dataTable /></literal> (or equivalent from a component set like <literal><rich:dataTable /></literal> ). Neither <literal><s:link /></literal> or <literal><s:button /></literal> submit the form (and therefore produce a bookmarkable link) so a \"magic\" parameter is needed to recreate the item when the action method is called. This magic parameter can only be added when a data table backed by a <literal>DataModel</literal> is used." msgstr "" #. Tag: para #: Elenhancements.xml:154 #, no-c-format -msgid "" -"<emphasis>Calling a <literal>MethodExpression</literal> from Java code</" -"emphasis> — Normally, when a <literal>MethodExpression</literal> is " -"created, the parameter types are passed in by JSF. In the case of a method " -"binding, JSF assumes that there are no parameters to pass. With this " -"extension, we can't know the parameter types until after the expression has " -"been evaluated. This has two minor consequences:" +msgid "<emphasis>Calling a <literal>MethodExpression</literal> from Java code</emphasis> — Normally, when a <literal>MethodExpression</literal> is created, the parameter types are passed in by JSF. In the case of a method binding, JSF assumes that there are no parameters to pass. With this extension, we can't know the parameter types until after the expression has been evaluated. This has two minor consequences:" msgstr "" #. Tag: para #: Elenhancements.xml:167 #, no-c-format -msgid "" -"When you invoke a <literal>MethodExpression</literal> in Java code, " -"parameters you pass may be ignored. Parameters defined in the expression " -"will take precedence." +msgid "When you invoke a <literal>MethodExpression</literal> in Java code, parameters you pass may be ignored. Parameters defined in the expression will take precedence." msgstr "" #. Tag: para #: Elenhancements.xml:175 #, no-c-format -msgid "" -"Ordinarily, it is safe to call <literal>methodExpression.getMethodInfo()." -"getParamTypes()</literal> at any time. For an expression with parameters, " -"you must first invoke the <literal>MethodExpression</literal> before calling " -"<literal>getParamTypes()</literal>." +msgid "Ordinarily, it is safe to call <literal>methodExpression.getMethodInfo().getParamTypes()</literal> at any time. For an expression with parameters, you must first invoke the <literal>MethodExpression</literal> before calling <literal>getParamTypes()</literal>." msgstr "" #. Tag: para #: Elenhancements.xml:185 #, no-c-format -msgid "" -"Both of these cases are exceedingly rare and only apply when you want to " -"invoke the <literal>MethodExpression</literal> by hand in Java code." +msgid "Both of these cases are exceedingly rare and only apply when you want to invoke the <literal>MethodExpression</literal> by hand in Java code." msgstr "" #. Tag: title #: Elenhancements.xml:196 #, no-c-format msgid "Projection" -msgstr "" +msgstr "Proiezione" #. Tag: para #: Elenhancements.xml:198 #, no-c-format -msgid "" -"JBoss EL supports a limited projection syntax. A projection expression maps " -"a sub-expression across a multi-valued (list, set, etc...) expression. For " -"instance, the expression:" +msgid "JBoss EL supports a limited projection syntax. A projection expression maps a sub-expression across a multi-valued (list, set, etc...) expression. For instance, the expression:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:204 #, no-c-format msgid "#{company.departments}" -msgstr "" +msgstr "#{company.departments}" #. Tag: para #: Elenhancements.xml:206 #, no-c-format -msgid "" -"might return a list of departments. If you only need a list of department " -"names, your only option is to iterate over the list to retrieve the values. " -"JBoss EL allows this with a projection expression:" +msgid "might return a list of departments. If you only need a list of department names, your only option is to iterate over the list to retrieve the values. JBoss EL allows this with a projection expression:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:212 #, no-c-format msgid "#{company.departments.{d|d.name}}" -msgstr "" +msgstr "#{company.departments.{d|d.name}}" #. Tag: para #: Elenhancements.xml:214 #, no-c-format -msgid "" -"The subexpression is enclosed in braces. In this example, the expression " -"<literal>d.name</literal> is evaluated for each department, using " -"<literal>d</literal> as an alias to the department object. The result of " -"this expression will be a list of String values." +msgid "The subexpression is enclosed in braces. In this example, the expression <literal>d.name</literal> is evaluated for each department, using <literal>d</literal> as an alias to the department object. The result of this expression will be a list of String values." msgstr "" #. Tag: para #: Elenhancements.xml:221 #, no-c-format -msgid "" -"Any valid expression can be used in an expression, so it would be perfectly " -"valid to write the following, assuming you had a use for the lengths of all " -"the department names in a company:" +msgid "Any valid expression can be used in an expression, so it would be perfectly valid to write the following, assuming you had a use for the lengths of all the department names in a company:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:227 #, no-c-format msgid "#{company.departments.{d|d.size()}}" -msgstr "" +msgstr "#{company.departments.{d|d.size()}}" #. Tag: para #: Elenhancements.xml:229 #, no-c-format -msgid "" -"Projections can be nested. The following expression returns the last names " -"of every employee in every department:" +msgid "Projections can be nested. The following expression returns the last names of every employee in every department:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:234 #, no-c-format msgid "#{company.departments.{d|d.employees.{emp|emp.lastName}}}" -msgstr "" +msgstr "#{company.departments.{d|d.employees.{emp|emp.lastName}}}" #. Tag: para #: Elenhancements.xml:236 #, no-c-format -msgid "" -"Nested projections can be slightly tricky, however. The following expression " -"looks like it returns a list of all the employees in all the departments:" +msgid "Nested projections can be slightly tricky, however. The following expression looks like it returns a list of all the employees in all the departments:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:242 #, no-c-format msgid "#{company.departments.{d|d.employees}}" -msgstr "" +msgstr "#{company.departments.{d|d.employees}}" #. Tag: para #: Elenhancements.xml:244 #, no-c-format -msgid "" -"However, it actually returns a list containing a list of the employees for " -"each individual department. To combine the values, it is necessary to use a " -"slightly longer expression:" +msgid "However, it actually returns a list containing a list of the employees for each individual department. To combine the values, it is necessary to use a slightly longer expression:" msgstr "" #. Tag: programlisting #: Elenhancements.xml:250 #, no-c-format msgid "#{company.departments.{d|d.employees.{e|e}}}" -msgstr "" +msgstr "#{company.departments.{d|d.employees.{e|e}}}" #. Tag: para #: Elenhancements.xml:252 #, no-c-format -msgid "" -"It is important to note that this syntax cannot be parsed by Facelets or JSP " -"and thus cannot be used in xhtml or JSP files. We anticipate that the " -"projection syntax will change in future versions of JBoss EL." +msgid "It is important to note that this syntax cannot be parsed by Facelets or JSP and thus cannot be used in xhtml or JSP files. We anticipate that the projection syntax will change in future versions of JBoss EL." msgstr "" + Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po =================================================================== --- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-12 14:44:37 UTC (rev 9762) +++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-12 14:45:51 UTC (rev 9763) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2008-04-04 01:24+0000\n" -"PO-Revision-Date: 2008-12-12 14:48+0100\n" +"PO-Revision-Date: 2008-12-12 15:33+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -212,7 +212,7 @@ #: Preface.xml:219 #, no-c-format msgid "Seam components, being plain Java classes, are by nature unit testable. But for complex applications, unit testing alone is insufficient. Integration testing has traditionally been a messy and difficult task for Java web applications. Therefore, Seam provides for testability of Seam applications as a core feature of the framework. You can easily write JUnit or TestNG tests that reproduce a whole interaction with a user, exercising all components of the system apart from the view (the JSP or Facelets page). You can run these tests directly inside your IDE, where Seam will automatically deploy EJB components using JBoss Embedded." -msgstr "I componenti Seam, essendo semplici classi Java, sono per natura unità testabili. Ma per le applicazioni complesse, il test dell'unità (testing unit) da solo è insufficiente. Il test d'integrazione (integration testing) è tradizionalmente stato complicato e difficile per le applicazioni web Java. Seam fornisce la testabilità delle applicazioni come caratteristica essenziale del framework. Potrai facilmente scrivere test JUnit o TestNG che riproducano tutta l'interazione con l'utente, provando tutti i componenti del sistema separati dalla vista (pagina JSP o Facelet). Potrai eseguire questi test direttamente dentro il tu IDE, dove Seam automaticamente eseguirà il deploy dei componenti EJB usando JBoss Embedded." +msgstr "I componenti Seam, essendo semplici classi Java, sono per natura unità testabili. Ma per le applicazioni complesse, il test dell'unità (testing unit) da solo è insufficiente. Il test d'integrazione (integration testing) è tradizionalmente stato complicato e difficile per le applicazioni web Java. Seam fornisce la testabilità delle applicazioni come caratteristica essenziale del framework. Potrai facilmente scrivere test JUnit o TestNG che riproducano tutta l'interazione con l'utente, provando tutti i componenti del sistema separati dalla vista (pagina JSP o Facelet). Potrai eseguire questi test direttamente dentro il tuo IDE, dove Seam automaticamente eseguirà il deploy dei componenti EJB usando JBoss Embedded." #. Tag: emphasis #: Preface.xml:232

15 years, 9 months

1
0
0 / 0

Seam SVN: r9762 - tags.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2008-12-12 09:44:37 -0500 (Fri, 12 Dec 2008) New Revision: 9762 Added: tags/JBoss_Seam_2_1_1_GA/ Log: 2.1.1.GA tag Copied: tags/JBoss_Seam_2_1_1_GA (from rev 9761, trunk)

15 years, 9 months

1
0
0 / 0

← Newer
1
...
6
7
8
9
10
11
12
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

seam-commits December 2008