[seam-commits] Seam SVN: r9784 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Mon Dec 15 12:36:41 EST 2008
Author: nico.ben
Date: 2008-12-15 12:36:40 -0500 (Mon, 15 Dec 2008)
New Revision: 9784
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Events.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
trunk/doc/Seam_Reference_Guide/it-IT/Jms.po
trunk/doc/Seam_Reference_Guide/it-IT/Mail.po
trunk/doc/Seam_Reference_Guide/it-IT/Performance.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Events.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Events.po 2008-12-15 15:50:47 UTC (rev 9783)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Events.po 2008-12-15 17:36:40 UTC (rev 9784)
@@ -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-15 18:36+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,13 +22,7 @@
#. Tag: para
#: Events.xml:7
#, no-c-format
-msgid ""
-"Complementing the contextual component model, there are two further basic "
-"concepts that facilitate the extreme loose-coupling that is the distinctive "
-"feature of Seam applications. The first is a strong event model where events "
-"may be mapped to event listeners via JSF-like method binding expressions. "
-"The second is the pervasive use of annotations and interceptors to apply "
-"cross-cutting concerns to components which implement business logic."
+msgid "Complementing the contextual component model, there are two further basic concepts that facilitate the extreme loose-coupling that is the distinctive feature of Seam applications. The first is a strong event model where events may be mapped to event listeners via JSF-like method binding expressions. The second is the pervasive use of annotations and interceptors to apply cross-cutting concerns to components which implement business logic."
msgstr ""
#. Tag: title
@@ -40,11 +34,7 @@
#. Tag: para
#: Events.xml:18
#, no-c-format
-msgid ""
-"The Seam component model was developed for use with <emphasis>event-driven "
-"applications</emphasis>, specifically to enable the development of fine-"
-"grained, loosely-coupled components in a fine-grained eventing model. Events "
-"in Seam come in several types, most of which we have already seen:"
+msgid "The Seam component model was developed for use with <emphasis>event-driven applications</emphasis>, specifically to enable the development of fine-grained, loosely-coupled components in a fine-grained eventing model. Events in Seam come in several types, most of which we have already seen:"
msgstr ""
#. Tag: para
@@ -80,26 +70,19 @@
#. Tag: para
#: Events.xml:43
#, no-c-format
-msgid ""
-"All of these various kinds of events are mapped to Seam components via JSF "
-"EL method binding expressions. For a JSF event, this is defined in the JSF "
-"template:"
+msgid "All of these various kinds of events are mapped to Seam components via JSF EL method binding expressions. For a JSF event, this is defined in the JSF template:"
msgstr ""
#. Tag: programlisting
#: Events.xml:48
#, no-c-format
-msgid ""
-"<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}"
-"\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}\"/>]]>"
+msgstr "<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}\"/>]]>"
#. Tag: para
#: Events.xml:52
#, no-c-format
-msgid ""
-"For a jBPM transition event, it is specified in the jBPM process definition "
-"or pageflow definition:"
+msgid "For a jBPM transition event, it is specified in the jBPM process definition or pageflow definition:"
msgstr ""
#. Tag: programlisting
@@ -112,14 +95,16 @@
" </transition>\n"
"</start-page>]]>"
msgstr ""
+"<![CDATA[<start-page name=\"hello\" view-id=\"/hello.jsp\">\n"
+" <transition to=\"hello\">\n"
+" <action expression=\"#{helloWorld.sayHello}\"/>\n"
+" </transition>\n"
+"</start-page>]]>"
#. Tag: para
#: Events.xml:59
#, no-c-format
-msgid ""
-"You can find out more information about JSF events and jBPM events "
-"elsewhere. Let's concentrate for now upon the two additional kinds of events "
-"defined by Seam."
+msgid "You can find out more information about JSF events and jBPM events elsewhere. Let's concentrate for now upon the two additional kinds of events defined by Seam."
msgstr ""
#. Tag: title
@@ -131,10 +116,7 @@
#. Tag: para
#: Events.xml:68
#, no-c-format
-msgid ""
-"A Seam page action is an event that occurs just before we render a page. We "
-"declare page actions in <literal>WEB-INF/pages.xml</literal>. We can define "
-"a page action for either a particular JSF view id:"
+msgid "A Seam page action is an event that occurs just before we render a page. We declare page actions in <literal>WEB-INF/pages.xml</literal>. We can define a page action for either a particular JSF view id:"
msgstr ""
#. Tag: programlisting
@@ -145,14 +127,14 @@
" <page view-id=\"/hello.jsp\" action=\"#{helloWorld.sayHello}\"/>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/hello.jsp\" action=\"#{helloWorld.sayHello}\"/>\n"
+"</pages>]]>"
#. Tag: para
#: Events.xml:76
#, no-c-format
-msgid ""
-"Or we can use a <literal>*</literal> wildcard as a suffix to the "
-"<literal>view-id</literal> to specify an action that applies to all view ids "
-"that match the pattern:"
+msgid "Or we can use a <literal>*</literal> wildcard as a suffix to the <literal>view-id</literal> to specify an action that applies to all view ids that match the pattern:"
msgstr ""
#. Tag: programlisting
@@ -163,53 +145,44 @@
" <page view-id=\"/hello/*\" action=\"#{helloWorld.sayHello}\"/>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/hello/*\" action=\"#{helloWorld.sayHello}\"/>\n"
+"</pages>]]>"
#. Tag: para
#: Events.xml:84
#, no-c-format
-msgid ""
-"If multiple wildcarded page actions match the current view-id, Seam will "
-"call all the actions, in order of least-specific to most-specific."
+msgid "If multiple wildcarded page actions match the current view-id, Seam will call all the actions, in order of least-specific to most-specific."
msgstr ""
#. Tag: para
#: Events.xml:89
#, no-c-format
-msgid ""
-"The page action method can return a JSF outcome. If the outcome is non-null, "
-"Seam will use the defined navigation rules to navigate to a view."
+msgid "The page action method can return a JSF outcome. If the outcome is non-null, Seam will use the defined navigation rules to navigate to a view."
msgstr ""
#. Tag: para
#: Events.xml:94
#, no-c-format
-msgid ""
-"Furthermore, the view id mentioned in the <literal><page></literal> "
-"element need not correspond to a real JSP or Facelets page! So, we can "
-"reproduce the functionality of a traditional action-oriented framework like "
-"Struts or WebWork using page actions. For example:"
+msgid "Furthermore, the view id mentioned in the <literal><page></literal> element need not correspond to a real JSP or Facelets page! So, we can reproduce the functionality of a traditional action-oriented framework like Struts or WebWork using page actions. For example:"
msgstr ""
#. Tag: programlisting
#: Events.xml:101
#, no-c-format
msgid "<![CDATA[TODO: translate struts action into page action]]>"
-msgstr ""
+msgstr "<![CDATA[TODO: translate struts action into page action]]>"
#. Tag: para
#: Events.xml:104
#, no-c-format
-msgid ""
-"This is quite useful if you want to do complex things in response to non-"
-"faces requests (for example, HTTP GET requests)."
+msgid "This is quite useful if you want to do complex things in response to non-faces requests (for example, HTTP GET requests)."
msgstr ""
#. Tag: para
#: Events.xml:109
#, no-c-format
-msgid ""
-"Multiple or conditional page actions my be specified using the <literal><"
-"action></literal> tag:"
+msgid "Multiple or conditional page actions my be specified using the <literal><action></literal> tag:"
msgstr ""
#. Tag: programlisting
@@ -218,12 +191,17 @@
msgid ""
"<![CDATA[<pages>\n"
" <page view-id=\"/hello.jsp\">\n"
-" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation."
-"failed}\"/>\n"
+" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation.failed}\"/>\n"
" <action execute=\"#{hitCount.increment}\"/>\n"
" </page>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/hello.jsp\">\n"
+" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation.failed}\"/>\n"
+" <action execute=\"#{hitCount.increment}\"/>\n"
+" </page>\n"
+"</pages>]]>"
#. Tag: title
#: Events.xml:120
@@ -234,19 +212,13 @@
#. Tag: para
#: Events.xml:122
#, no-c-format
-msgid ""
-"A JSF faces request (a form submission) encapsulates both an \"action\" (a "
-"method binding) and \"parameters\" (input value bindings). A page action "
-"might also needs parameters!"
+msgid "A JSF faces request (a form submission) encapsulates both an \"action\" (a method binding) and \"parameters\" (input value bindings). A page action might also needs parameters!"
msgstr ""
#. Tag: para
#: Events.xml:128
#, no-c-format
-msgid ""
-"Since GET requests are bookmarkable, page parameters are passed as human-"
-"readable request parameters. (Unlike JSF form inputs, which are anything "
-"but!)"
+msgid "Since GET requests are bookmarkable, page parameters are passed as human-readable request parameters. (Unlike JSF form inputs, which are anything but!)"
msgstr ""
#. Tag: para
@@ -264,9 +236,7 @@
#. Tag: para
#: Events.xml:141
#, no-c-format
-msgid ""
-"Seam lets us provide a value binding that maps a named request parameter to "
-"an attribute of a model object."
+msgid "Seam lets us provide a value binding that maps a named request parameter to an attribute of a model object."
msgstr ""
#. Tag: programlisting
@@ -280,62 +250,47 @@
" </page>\n"
" </pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/hello.jsp\" action=\"#{helloWorld.sayHello}\">\n"
+" <param name=\"firstName\" value=\"#{person.firstName}\"/>\n"
+" <param name=\"lastName\" value=\"#{person.lastName}\"/>\n"
+" </page>\n"
+" </pages>]]>"
#. Tag: para
#: Events.xml:148
#, no-c-format
-msgid ""
-"The <literal><param></literal> declaration is bidirectional, just like "
-"a value binding for a JSF input:"
+msgid "The <literal><param></literal> declaration is bidirectional, just like a value binding for a JSF input:"
msgstr ""
#. Tag: para
#: Events.xml:155
#, no-c-format
-msgid ""
-"When a non-faces (GET) request for the view id occurs, Seam sets the value "
-"of the named request parameter onto the model object, after performing "
-"appropriate type conversions."
+msgid "When a non-faces (GET) request for the view id occurs, Seam sets the value of the named request parameter onto the model object, after performing appropriate type conversions."
msgstr ""
#. Tag: para
#: Events.xml:162
#, no-c-format
-msgid ""
-"Any <literal><s:link></literal> or <literal><s:button></literal> "
-"transparently includes the request parameter. The value of the parameter is "
-"determined by evaluating the value binding during the render phase (when the "
-"<literal><s:link></literal> is rendered)."
+msgid "Any <literal><s:link></literal> or <literal><s:button></literal> transparently includes the request parameter. The value of the parameter is determined by evaluating the value binding during the render phase (when the <literal><s:link></literal> is rendered)."
msgstr ""
#. Tag: para
#: Events.xml:170
#, no-c-format
-msgid ""
-"Any navigation rule with a <literal><redirect/></literal> to the view "
-"id transparently includes the request parameter. The value of the parameter "
-"is determined by evaluating the value binding at the end of the invoke "
-"application phase."
+msgid "Any navigation rule with a <literal><redirect/></literal> to the view id transparently includes the request parameter. The value of the parameter is determined by evaluating the value binding at the end of the invoke application phase."
msgstr ""
#. Tag: para
#: Events.xml:178
#, no-c-format
-msgid ""
-"The value is transparently propagated with any JSF form submission for the "
-"page with the given view id. This means that view parameters behave like "
-"<literal>PAGE</literal>-scoped context variables for faces requests."
+msgid "The value is transparently propagated with any JSF form submission for the page with the given view id. This means that view parameters behave like <literal>PAGE</literal>-scoped context variables for faces requests."
msgstr ""
#. Tag: para
#: Events.xml:187
#, no-c-format
-msgid ""
-"The essential idea behind all this is that <emphasis>however</emphasis> we "
-"get from any other page to <literal>/hello.jsp</literal> (or from <literal>/"
-"hello.jsp</literal> back to <literal>/hello.jsp</literal>), the value of the "
-"model attribute referred to in the value binding is \"remembered\", without "
-"the need for a conversation (or other server-side state)."
+msgid "The essential idea behind all this is that <emphasis>however</emphasis> we get from any other page to <literal>/hello.jsp</literal> (or from <literal>/hello.jsp</literal> back to <literal>/hello.jsp</literal>), the value of the model attribute referred to in the value binding is \"remembered\", without the need for a conversation (or other server-side state)."
msgstr ""
#. Tag: title
@@ -347,10 +302,7 @@
#. Tag: para
#: Events.xml:202
#, no-c-format
-msgid ""
-"If just the <literal>name</literal> attribute is specified then the request "
-"parameter is propagated using the <literal>PAGE</literal> context (it isn't "
-"mapped to model property)."
+msgid "If just the <literal>name</literal> attribute is specified then the request parameter is propagated using the <literal>PAGE</literal> context (it isn't mapped to model property)."
msgstr ""
#. Tag: programlisting
@@ -364,48 +316,35 @@
" </page>\n"
" </pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/hello.jsp\" action=\"#{helloWorld.sayHello}\">\n"
+" <param name=\"firstName\" />\n"
+" <param name=\"lastName\" />\n"
+" </page>\n"
+" </pages>]]>"
#. Tag: para
#: Events.xml:211
#, no-c-format
-msgid ""
-"Propagation of page parameters is especially useful if you want to build "
-"multi-layer master-detail CRUD pages. You can use it to \"remember\" which "
-"view you were previously on (e.g. when pressing the Save button), and which "
-"entity you were editing."
+msgid "Propagation of page parameters is especially useful if you want to build multi-layer master-detail CRUD pages. You can use it to \"remember\" which view you were previously on (e.g. when pressing the Save button), and which entity you were editing."
msgstr ""
#. Tag: para
#: Events.xml:218
#, no-c-format
-msgid ""
-"Any <literal><s:link></literal> or <literal><s:button></literal> "
-"transparently propagates the request parameter if that parameter is listed "
-"as a page parameter for the view."
+msgid "Any <literal><s:link></literal> or <literal><s:button></literal> transparently propagates the request parameter if that parameter is listed as a page parameter for the view."
msgstr ""
#. Tag: para
#: Events.xml:225
#, no-c-format
-msgid ""
-"The value is transparently propagated with any JSF form submission for the "
-"page with the given view id. (This means that view parameters behave like "
-"<literal>PAGE</literal>-scoped context variables for faces requests."
+msgid "The value is transparently propagated with any JSF form submission for the page with the given view id. (This means that view parameters behave like <literal>PAGE</literal>-scoped context variables for faces requests."
msgstr ""
#. Tag: para
#: Events.xml:234
#, no-c-format
-msgid ""
-"This all sounds pretty complex, and you're probably wondering if such an "
-"exotic construct is really worth the effort. Actually, the idea is very "
-"natural once you \"get it\". It is definitely worth taking the time to "
-"understand this stuff. Page parameters are the most elegant way to propagate "
-"state across a non-faces request. They are especially cool for problems like "
-"search screens with bookmarkable results pages, where we would like to be "
-"able to write our application code to handle both POST and GET requests with "
-"the same code. Page parameters eliminate repetitive listing of request "
-"parameters in the view definition and make redirects much easier to code."
+msgid "This all sounds pretty complex, and you're probably wondering if such an exotic construct is really worth the effort. Actually, the idea is very natural once you \"get it\". It is definitely worth taking the time to understand this stuff. Page parameters are the most elegant way to propagate state across a non-faces request. They are especially cool for problems like search screens with bookmarkable results pages, where we would like to be able to write our application code to handle both POST and GET requests with the same code. Page parameters eliminate repetitive listing of request parameters in the view definition and make redirects much easier to code."
msgstr ""
#. Tag: title
@@ -417,10 +356,7 @@
#. Tag: para
#: Events.xml:251
#, no-c-format
-msgid ""
-"Rewriting occurs based on rewrite patterns found for views in <literal>pages."
-"xml</literal>. Seam URL rewriting does both incoming and outgoing URL "
-"rewriting based on the same pattern. Here's a simple pattern:"
+msgid "Rewriting occurs based on rewrite patterns found for views in <literal>pages.xml</literal>. Seam URL rewriting does both incoming and outgoing URL rewriting based on the same pattern. Here's a simple pattern:"
msgstr ""
#. Tag: programlisting
@@ -433,26 +369,22 @@
"</page>\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+"<page view-id=\"/home.xhtml\">\n"
+" <rewrite pattern=\"/home\" />\n"
+"</page>\n"
+"]]>"
#. Tag: para
#: Events.xml:260
#, no-c-format
-msgid ""
-"In this case, any incoming request for <literal>/home</literal> will be sent "
-"to <literal>/home.xhtml</literal>. More interestingly, any link generated "
-"that would normally point to <literal>/home.seam</literal> will instead be "
-"rewritten as <literal>/home</literal>. Rewrite patterns only match the "
-"portion of the URL before the query parameters. So, <literal>/home.seam?"
-"conversationId=13</literal> and <literal>/home.seam?color=red</literal> will "
-"both be matched by this rewrite rule."
+msgid "In this case, any incoming request for <literal>/home</literal> will be sent to <literal>/home.xhtml</literal>. More interestingly, any link generated that would normally point to <literal>/home.seam</literal> will instead be rewritten as <literal>/home</literal>. Rewrite patterns only match the portion of the URL before the query parameters. So, <literal>/home.seam?conversationId=13</literal> and <literal>/home.seam?color=red</literal> will both be matched by this rewrite rule."
msgstr ""
#. Tag: para
#: Events.xml:270
#, no-c-format
-msgid ""
-"Rewrite rules can take these query paramters into consideration, as shown "
-"with the following rules."
+msgid "Rewrite rules can take these query paramters into consideration, as shown with the following rules."
msgstr ""
#. Tag: programlisting
@@ -466,27 +398,23 @@
"</page>\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+"<page view-id=\"/home.xhtml\">\n"
+" <rewrite pattern=\"/home/{color}\" />\n"
+" <rewrite pattern=\"/home\" />\n"
+"</page>\n"
+"]]>"
#. Tag: para
#: Events.xml:275
#, no-c-format
-msgid ""
-"In this case, an incoming request for <literal>/home/red</literal> will be "
-"served as if it were a request for <literal>/home.seam?color=red</literal>. "
-"Similarly, if color is a page parameter an outgoing URL that would normally "
-"show as <literal>/home.seam?color=blue</literal> would instead be output as "
-"<literal>/home/blue</literal>. Rules are processed in order, so it is "
-"important to list more specific rules before more general rules."
+msgid "In this case, an incoming request for <literal>/home/red</literal> will be served as if it were a request for <literal>/home.seam?color=red</literal>. Similarly, if color is a page parameter an outgoing URL that would normally show as <literal>/home.seam?color=blue</literal> would instead be output as <literal>/home/blue</literal>. Rules are processed in order, so it is important to list more specific rules before more general rules."
msgstr ""
#. Tag: para
#: Events.xml:285
#, no-c-format
-msgid ""
-"Default Seam query parameters can also be mapped using URL rewriting, "
-"allowing for another option for hiding Seam's fingerprints. In the following "
-"example, <literal>/search.seam?conversationId=13</literal> would be written "
-"as <literal>/search-13</literal>."
+msgid "Default Seam query parameters can also be mapped using URL rewriting, allowing for another option for hiding Seam's fingerprints. In the following example, <literal>/search.seam?conversationId=13</literal> would be written as <literal>/search-13</literal>."
msgstr ""
#. Tag: programlisting
@@ -500,24 +428,23 @@
"</page>\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+"<page view-id=\"/search.xhtml\">\n"
+" <rewrite pattern=\"/search-{conversationId}\" />\n"
+" <rewrite pattern=\"/search\" />\n"
+"</page>\n"
+"]]>"
#. Tag: para
#: Events.xml:292
#, no-c-format
-msgid ""
-"Seam URL rewriting provides simple, bidirectional rewriting on a per-view "
-"basis. For more complex rewriting rules that cover non-seam components, Seam "
-"applications can continue to use the <literal>org.tuckey URLRewriteFilter </"
-"literal>or apply rewriting rules at the web server."
+msgid "Seam URL rewriting provides simple, bidirectional rewriting on a per-view basis. For more complex rewriting rules that cover non-seam components, Seam applications can continue to use the <literal>org.tuckey URLRewriteFilter </literal>or apply rewriting rules at the web server."
msgstr ""
#. Tag: para
#: Events.xml:298
#, no-c-format
-msgid ""
-"URL rewriting requires the Seam rewrite filter to be enable. Rewrite filter "
-"configuration is discussed in <xref linkend=\"configuration.filters.rewrite"
-"\"/>."
+msgid "URL rewriting requires the Seam rewrite filter to be enable. Rewrite filter configuration is discussed in <xref linkend=\"configuration.filters.rewrite\"/>."
msgstr ""
#. Tag: title
@@ -540,14 +467,21 @@
" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" "
-"value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" value=\"#{calculator.op}\"/>\n"
" </page>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
+" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
+" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
+" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" value=\"#{calculator.op}\"/>\n"
+" </page>\n"
+"</pages>]]>"
#. Tag: para
-#: Events.xml:314 Events.xml:327
+#: Events.xml:314
+#: Events.xml:327
#, no-c-format
msgid "Alternatively:"
msgstr ""
@@ -560,17 +494,22 @@
" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#"
-"{calculator.op}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
" </page>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
+" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
+" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
+" </page>\n"
+"</pages>]]>"
#. Tag: para
#: Events.xml:321
#, no-c-format
-msgid ""
-"JSF validators, and <literal>required=\"true\"</literal> may also be used:"
+msgid "JSF validators, and <literal>required=\"true\"</literal> may also be used:"
msgstr ""
#. Tag: programlisting
@@ -586,6 +525,14 @@
" </page>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/blog.xhtml\">\n"
+" <param name=\"date\" \n"
+" value=\"#{blog.date}\" \n"
+" validatorId=\"com.my.blog.PastDate\" \n"
+" required=\"true\"/>\n"
+" </page>\n"
+"</pages>]]>"
#. Tag: programlisting
#: Events.xml:331
@@ -600,21 +547,25 @@
" </page>\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/blog.xhtml\">\n"
+" <param name=\"date\" \n"
+" value=\"#{blog.date}\" \n"
+" validator=\"#{pastDateValidator}\" \n"
+" required=\"true\"/>\n"
+" </page>\n"
+"</pages>]]>"
#. Tag: para
#: Events.xml:333
#, no-c-format
-msgid ""
-"Even better, model-based Hibernate validator annotations are automatically "
-"recognized and validated."
+msgid "Even better, model-based Hibernate validator annotations are automatically recognized and validated."
msgstr ""
#. Tag: para
#: Events.xml:338
#, no-c-format
-msgid ""
-"When type conversion or validation fails, a global <literal>FacesMessage</"
-"literal> is added to the <literal>FacesContext</literal>."
+msgid "When type conversion or validation fails, a global <literal>FacesMessage</literal> is added to the <literal>FacesContext</literal>."
msgstr ""
#. Tag: title
@@ -626,17 +577,13 @@
#. Tag: para
#: Events.xml:348
#, no-c-format
-msgid ""
-"You can use standard JSF navigation rules defined in <literal>faces-config."
-"xml</literal> in a Seam application. However, JSF navigation rules have a "
-"number of annoying limitations:"
+msgid "You can use standard JSF navigation rules defined in <literal>faces-config.xml</literal> in a Seam application. However, JSF navigation rules have a number of annoying limitations:"
msgstr ""
#. Tag: para
#: Events.xml:356
#, no-c-format
-msgid ""
-"It is not possible to specify request parameters to be used when redirecting."
+msgid "It is not possible to specify request parameters to be used when redirecting."
msgstr ""
#. Tag: para
@@ -648,18 +595,13 @@
#. Tag: para
#: Events.xml:366
#, no-c-format
-msgid ""
-"Rules work by evaluating the return value of the action method; it is not "
-"possible to evaluate an arbitrary EL expression."
+msgid "Rules work by evaluating the return value of the action method; it is not possible to evaluate an arbitrary EL expression."
msgstr ""
#. Tag: para
#: Events.xml:373
#, no-c-format
-msgid ""
-"A further problem is that \"orchestration\" logic gets scattered between "
-"<literal>pages.xml</literal> and <literal>faces-config.xml</literal>. It's "
-"better to unify this logic into <literal>pages.xml</literal>."
+msgid "A further problem is that \"orchestration\" logic gets scattered between <literal>pages.xml</literal> and <literal>faces-config.xml</literal>. It's better to unify this logic into <literal>pages.xml</literal>."
msgstr ""
#. Tag: para
@@ -684,6 +626,17 @@
" \n"
"</navigation-rule>]]>"
msgstr ""
+"<![CDATA[<navigation-rule>\n"
+" <from-view-id>/editDocument.xhtml</from-view-id>\n"
+" \n"
+" <navigation-case>\n"
+" <from-action>#{documentEditor.update}</from-action>\n"
+" <from-outcome>success</from-outcome>\n"
+" <to-view-id>/viewDocument.xhtml</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+" \n"
+"</navigation-rule>]]>"
#. Tag: para
#: Events.xml:384
@@ -705,14 +658,20 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\">\n"
+" <rule if-outcome=\"success\">\n"
+" <redirect view-id=\"/viewDocument.xhtml\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:390
#, no-c-format
-msgid ""
-"But it would be even nicer if we didn't have to pollute our "
-"<literal>DocumentEditor</literal> component with string-valued return values "
-"(the JSF outcomes). So Seam lets us write:"
+msgid "But it would be even nicer if we didn't have to pollute our <literal>DocumentEditor</literal> component with string-valued return values (the JSF outcomes). So Seam lets us write:"
msgstr ""
#. Tag: programlisting
@@ -730,6 +689,16 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\" \n"
+" evaluate=\"#{documentEditor.errors.size}\">\n"
+" <rule if-outcome=\"0\">\n"
+" <redirect view-id=\"/viewDocument.xhtml\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:397
@@ -751,22 +720,26 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\">\n"
+" <rule if=\"#{documentEditor.errors.empty}\">\n"
+" <redirect view-id=\"/viewDocument.xhtml\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:403
#, no-c-format
-msgid ""
-"The first form evaluates a value binding to determine the outcome value to "
-"be used by the subsequent rules. The second approach ignores the outcome and "
-"evaluates a value binding for each possible rule."
+msgid "The first form evaluates a value binding to determine the outcome value to be used by the subsequent rules. The second approach ignores the outcome and evaluates a value binding for each possible rule."
msgstr ""
#. Tag: para
#: Events.xml:410
#, no-c-format
-msgid ""
-"Of course, when an update succeeds, we probably want to end the current "
-"conversation. We can do that like this:"
+msgid "Of course, when an update succeeds, we probably want to end the current conversation. We can do that like this:"
msgstr ""
#. Tag: programlisting
@@ -784,14 +757,21 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\">\n"
+" <rule if=\"#{documentEditor.errors.empty}\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/viewDocument.xhtml\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:417
#, no-c-format
-msgid ""
-"As we've ended conversation any subsequent requests won't know which "
-"document we are interested in. We can pass the document id as a request "
-"parameter which also makes the view bookmarkable:"
+msgid "As we've ended conversation any subsequent requests won't know which document we are interested in. We can pass the document id as a request parameter which also makes the view bookmarkable:"
msgstr ""
#. Tag: programlisting
@@ -804,22 +784,30 @@
" <rule if=\"#{documentEditor.errors.empty}\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/viewDocument.xhtml\">\n"
-" <param name=\"documentId\" value=\"#{documentEditor."
-"documentId}\"/>\n"
+" <param name=\"documentId\" value=\"#{documentEditor.documentId}\"/>\n"
" </redirect>\n"
" </rule>\n"
" </navigation>\n"
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\">\n"
+" <rule if=\"#{documentEditor.errors.empty}\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/viewDocument.xhtml\">\n"
+" <param name=\"documentId\" value=\"#{documentEditor.documentId}\"/>\n"
+" </redirect>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:425
#, no-c-format
-msgid ""
-"Null outcomes are a special case in JSF. The null outcome is interpreted to "
-"mean \"redisplay the page\". The following navigation rule matches any non-"
-"null outcome, but <emphasis>not</emphasis> the null outcome:"
+msgid "Null outcomes are a special case in JSF. The null outcome is interpreted to mean \"redisplay the page\". The following navigation rule matches any non-null outcome, but <emphasis>not</emphasis> the null outcome:"
msgstr ""
#. Tag: programlisting
@@ -836,13 +824,20 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\">\n"
+" <rule>\n"
+" <render view-id=\"/viewDocument.xhtml\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:433
#, no-c-format
-msgid ""
-"If you want to perform navigation when a null outcome occurs, use the "
-"following form instead:"
+msgid "If you want to perform navigation when a null outcome occurs, use the following form instead:"
msgstr ""
#. Tag: programlisting
@@ -857,6 +852,13 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+" \n"
+" <navigation from-action=\"#{documentEditor.update}\">\n"
+" <render view-id=\"/viewDocument.xhtml\"/>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: para
#: Events.xml:440
@@ -878,25 +880,26 @@
" \n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/editDocument.xhtml\">\n"
+"\n"
+" <navigation>\n"
+" <rule if-outcome=\"success\">\n"
+" <redirect view-id=\"/#{userAgent}/displayDocument.xhtml\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+" \n"
+"</page>]]>"
#. Tag: title
#: Events.xml:449
#, no-c-format
-msgid ""
-"Fine-grained files for definition of navigation, page actions and parameters"
+msgid "Fine-grained files for definition of navigation, page actions and parameters"
msgstr ""
#. Tag: para
#: Events.xml:451
#, no-c-format
-msgid ""
-"If you have a lot of different page actions and page parameters, or even "
-"just a lot of navigation rules, you will almost certainly want to split the "
-"declarations up over multiple files. You can define actions and parameters "
-"for a page with the view id <literal>/calc/calculator.jsp</literal> in a "
-"resource named <literal>calc/calculator.page.xml</literal>. The root element "
-"in this case is the <literal><page></literal> element, and the view id "
-"is implied:"
+msgid "If you have a lot of different page actions and page parameters, or even just a lot of navigation rules, you will almost certainly want to split the declarations up over multiple files. You can define actions and parameters for a page with the view id <literal>/calc/calculator.jsp</literal> in a resource named <literal>calc/calculator.page.xml</literal>. The root element in this case is the <literal><page></literal> element, and the view id is implied:"
msgstr ""
#. Tag: programlisting
@@ -906,10 +909,14 @@
"<![CDATA[<page action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#"
-"{calculator.op}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page action=\"#{calculator.calculate}\">\n"
+" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
+" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
+"</page>]]>"
#. Tag: title
#: Events.xml:469
@@ -920,19 +927,13 @@
#. Tag: para
#: Events.xml:471
#, no-c-format
-msgid ""
-"Seam components can interact by simply calling each others methods. Stateful "
-"components may even implement the observer/observable pattern. But to enable "
-"components to interact in a more loosely-coupled fashion than is possible "
-"when the components call each others methods directly, Seam provides "
-"<emphasis>component-driven events</emphasis>."
+msgid "Seam components can interact by simply calling each others methods. Stateful components may even implement the observer/observable pattern. But to enable components to interact in a more loosely-coupled fashion than is possible when the components call each others methods directly, Seam provides <emphasis>component-driven events</emphasis>."
msgstr ""
#. Tag: para
#: Events.xml:479
#, no-c-format
-msgid ""
-"We specify event listeners (observers) in <literal>components.xml</literal>."
+msgid "We specify event listeners (observers) in <literal>components.xml</literal>."
msgstr ""
#. Tag: programlisting
@@ -946,6 +947,12 @@
" </event>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <event type=\"hello\">\n"
+" <action execute=\"#{helloListener.sayHelloBack}\"/>\n"
+" <action execute=\"#{logger.logHello}\"/>\n"
+" </event>\n"
+"</components>]]>"
#. Tag: para
#: Events.xml:485
@@ -956,10 +963,7 @@
#. Tag: para
#: Events.xml:489
#, no-c-format
-msgid ""
-"When an event occurs, the actions registered for that event will be called "
-"in the order they appear in <literal>components.xml</literal>. How does a "
-"component raise an event? Seam provides a built-in component for this."
+msgid "When an event occurs, the actions registered for that event will be called in the order they appear in <literal>components.xml</literal>. How does a component raise an event? Seam provides a built-in component for this."
msgstr ""
#. Tag: programlisting
@@ -974,6 +978,13 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"helloWorld\")\n"
+"public class HelloWorld {\n"
+" public void sayHello() {\n"
+" FacesMessages.instance().add(\"Hello World!\");\n"
+" Events.instance().raiseEvent(\"hello\");\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Events.xml:497
@@ -993,14 +1004,18 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"helloWorld\")\n"
+"public class HelloWorld {\n"
+" @RaiseEvent(\"hello\")\n"
+" public void sayHello() {\n"
+" FacesMessages.instance().add(\"Hello World!\");\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Events.xml:503
#, no-c-format
-msgid ""
-"Notice that this event producer has no dependency upon event consumers. The "
-"event listener may now be implemented with absolutely no dependency upon the "
-"producer:"
+msgid "Notice that this event producer has no dependency upon event consumers. The event listener may now be implemented with absolutely no dependency upon the producer:"
msgstr ""
#. Tag: programlisting
@@ -1014,15 +1029,17 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"helloListener\")\n"
+"public class HelloListener {\n"
+" public void sayHelloBack() {\n"
+" FacesMessages.instance().add(\"Hello to you too!\");\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Events.xml:511
#, no-c-format
-msgid ""
-"The method binding defined in <literal>components.xml</literal> above takes "
-"care of mapping the event to the consumer. If you don't like futzing about "
-"in the <literal>components.xml</literal> file, you can use an annotation "
-"instead:"
+msgid "The method binding defined in <literal>components.xml</literal> above takes care of mapping the event to the consumer. If you don't like futzing about in the <literal>components.xml</literal> file, you can use an annotation instead:"
msgstr ""
#. Tag: programlisting
@@ -1037,16 +1054,18 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"helloListener\")\n"
+"public class HelloListener {\n"
+" @Observer(\"hello\")\n"
+" public void sayHelloBack() {\n"
+" FacesMessages.instance().add(\"Hello to you too!\");\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Events.xml:520
#, no-c-format
-msgid ""
-"You might wonder why I've not mentioned anything about event objects in this "
-"discussion. In Seam, there is no need for an event object to propagate state "
-"between event producer and listener. State is held in the Seam contexts, and "
-"is shared between components. However, if you really want to pass an event "
-"object, you can:"
+msgid "You might wonder why I've not mentioned anything about event objects in this discussion. In Seam, there is no need for an event object to propagate state between event producer and listener. State is held in the Seam contexts, and is shared between components. However, if you really want to pass an event object, you can:"
msgstr ""
#. Tag: programlisting
@@ -1057,12 +1076,19 @@
"public class HelloWorld {\n"
" private String name;\n"
" public void sayHello() {\n"
-" FacesMessages.instance().add(\"Hello World, my name is #0.\", "
-"name);\n"
+" FacesMessages.instance().add(\"Hello World, my name is #0.\", name);\n"
" Events.instance().raiseEvent(\"hello\", name);\n"
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"helloWorld\")\n"
+"public class HelloWorld {\n"
+" private String name;\n"
+" public void sayHello() {\n"
+" FacesMessages.instance().add(\"Hello World, my name is #0.\", name);\n"
+" Events.instance().raiseEvent(\"hello\", name);\n"
+" }\n"
+"}]]>"
#. Tag: programlisting
#: Events.xml:530
@@ -1076,6 +1102,13 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"helloListener\")\n"
+"public class HelloListener {\n"
+" @Observer(\"hello\")\n"
+" public void sayHelloBack(String name) {\n"
+" FacesMessages.instance().add(\"Hello #0!\", name);\n"
+" }\n"
+"}]]>"
#. Tag: title
#: Events.xml:535
@@ -1086,306 +1119,229 @@
#. Tag: para
#: Events.xml:536
#, no-c-format
-msgid ""
-"Seam defines a number of built-in events that the application can use to "
-"perform special kinds of framework integration. The events are:"
+msgid "Seam defines a number of built-in events that the application can use to perform special kinds of framework integration. The events are:"
msgstr ""
#. Tag: para
#: Events.xml:542
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.validationFailed</literal> — called when JSF "
-"validation fails"
+msgid "<literal>org.jboss.seam.validationFailed</literal> — called when JSF validation fails"
msgstr ""
#. Tag: para
#: Events.xml:543
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.noConversation</literal> — called when there "
-"is no long running conversation and a long running conversation is required"
+msgid "<literal>org.jboss.seam.noConversation</literal> — called when there is no long running conversation and a long running conversation is required"
msgstr ""
#. Tag: para
#: Events.xml:544
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.preSetVariable.<name></literal> — called "
-"when the context variable <name> is set"
+msgid "<literal>org.jboss.seam.preSetVariable.<name></literal> — called when the context variable <name> is set"
msgstr ""
#. Tag: para
#: Events.xml:545
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postSetVariable.<name></literal> — "
-"called when the context variable <name> is set"
+msgid "<literal>org.jboss.seam.postSetVariable.<name></literal> — called when the context variable <name> is set"
msgstr ""
#. Tag: para
#: Events.xml:546
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.preRemoveVariable.<name></literal> — "
-"called when the context variable <name> is unset"
+msgid "<literal>org.jboss.seam.preRemoveVariable.<name></literal> — called when the context variable <name> is unset"
msgstr ""
#. Tag: para
#: Events.xml:547
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postRemoveVariable.<name></literal> — "
-"called when the context variable <name> is unset"
+msgid "<literal>org.jboss.seam.postRemoveVariable.<name></literal> — called when the context variable <name> is unset"
msgstr ""
#. Tag: para
#: Events.xml:548
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.preDestroyContext.<SCOPE></literal> — "
-"called before the <SCOPE> context is destroyed"
+msgid "<literal>org.jboss.seam.preDestroyContext.<SCOPE></literal> — called before the <SCOPE> context is destroyed"
msgstr ""
#. Tag: para
#: Events.xml:549
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postDestroyContext.<SCOPE></literal> — "
-"called after the <SCOPE> context is destroyed"
+msgid "<literal>org.jboss.seam.postDestroyContext.<SCOPE></literal> — called after the <SCOPE> context is destroyed"
msgstr ""
#. Tag: para
#: Events.xml:550
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.beginConversation </literal>— called whenever "
-"a long-running conversation begins"
+msgid "<literal>org.jboss.seam.beginConversation </literal>— called whenever a long-running conversation begins"
msgstr ""
#. Tag: para
#: Events.xml:551
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.endConversation </literal>— called whenever a "
-"long-running conversation ends"
+msgid "<literal>org.jboss.seam.endConversation </literal>— called whenever a long-running conversation ends"
msgstr ""
#. Tag: para
#: Events.xml:552
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.conversationTimeout</literal>— called when a "
-"conversation timeout occurs. The conversation id is passed as a parameter."
+msgid "<literal>org.jboss.seam.conversationTimeout</literal>— called when a conversation timeout occurs. The conversation id is passed as a parameter."
msgstr ""
#. Tag: para
#: Events.xml:553
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.beginPageflow </literal>— called when a "
-"pageflow begins"
+msgid "<literal>org.jboss.seam.beginPageflow </literal>— called when a pageflow begins"
msgstr ""
#. Tag: para
#: Events.xml:554
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.beginPageflow.<name> </literal>— called "
-"when the pageflow <name> begins"
+msgid "<literal>org.jboss.seam.beginPageflow.<name> </literal>— called when the pageflow <name> begins"
msgstr ""
#. Tag: para
#: Events.xml:555
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.endPageflow </literal>— called when a pageflow "
-"ends"
+msgid "<literal>org.jboss.seam.endPageflow </literal>— called when a pageflow ends"
msgstr ""
#. Tag: para
#: Events.xml:556
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.endPageflow.<name> </literal>— called "
-"when the pageflow <name> ends"
+msgid "<literal>org.jboss.seam.endPageflow.<name> </literal>— called when the pageflow <name> ends"
msgstr ""
#. Tag: para
#: Events.xml:557
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.createProcess.<name> </literal>— called "
-"when the process <name> is created"
+msgid "<literal>org.jboss.seam.createProcess.<name> </literal>— called when the process <name> is created"
msgstr ""
#. Tag: para
#: Events.xml:558
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.endProcess.<name> </literal>— called "
-"when the process <name> ends"
+msgid "<literal>org.jboss.seam.endProcess.<name> </literal>— called when the process <name> ends"
msgstr ""
#. Tag: para
#: Events.xml:559
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.initProcess.<name> </literal>— called "
-"when the process <name> is associated with the conversation"
+msgid "<literal>org.jboss.seam.initProcess.<name> </literal>— called when the process <name> is associated with the conversation"
msgstr ""
#. Tag: para
#: Events.xml:560
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.initTask.<name> </literal>— called when "
-"the task <name> is associated with the conversation"
+msgid "<literal>org.jboss.seam.initTask.<name> </literal>— called when the task <name> is associated with the conversation"
msgstr ""
#. Tag: para
#: Events.xml:561
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.startTask.<name> </literal>— called when "
-"the task <name> is started"
+msgid "<literal>org.jboss.seam.startTask.<name> </literal>— called when the task <name> is started"
msgstr ""
#. Tag: para
#: Events.xml:562
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.endTask.<name> </literal>— called when "
-"the task <name> is ended"
+msgid "<literal>org.jboss.seam.endTask.<name> </literal>— called when the task <name> is ended"
msgstr ""
#. Tag: para
#: Events.xml:563
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postCreate.<name> </literal>— called "
-"when the component <name> is created"
+msgid "<literal>org.jboss.seam.postCreate.<name> </literal>— called when the component <name> is created"
msgstr ""
#. Tag: para
#: Events.xml:564
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.preDestroy.<name> </literal>— called "
-"when the component <name> is destroyed"
+msgid "<literal>org.jboss.seam.preDestroy.<name> </literal>— called when the component <name> is destroyed"
msgstr ""
#. Tag: para
#: Events.xml:565
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.beforePhase </literal>— called before the "
-"start of a JSF phase"
+msgid "<literal>org.jboss.seam.beforePhase </literal>— called before the start of a JSF phase"
msgstr ""
#. Tag: para
#: Events.xml:566
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.afterPhase </literal>— called after the end of "
-"a JSF phase"
+msgid "<literal>org.jboss.seam.afterPhase </literal>— called after the end of a JSF phase"
msgstr ""
#. Tag: para
#: Events.xml:567
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postInitialization </literal>— called when "
-"Seam has initialized and started up all components"
+msgid "<literal>org.jboss.seam.postInitialization </literal>— called when Seam has initialized and started up all components"
msgstr ""
#. Tag: para
#: Events.xml:568
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postReInitialization </literal>— called when "
-"Seam has re-initialized and started up all components after a redeploy"
+msgid "<literal>org.jboss.seam.postReInitialization </literal>— called when Seam has re-initialized and started up all components after a redeploy"
msgstr ""
#. Tag: para
#: Events.xml:569
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.postAuthenticate.<name> </literal>— "
-"called after a user is authenticated"
+msgid "<literal>org.jboss.seam.postAuthenticate.<name> </literal>— called after a user is authenticated"
msgstr ""
#. Tag: para
#: Events.xml:570
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.preAuthenticate.<name> </literal>— "
-"called before attempting to authenticate a user"
+msgid "<literal>org.jboss.seam.preAuthenticate.<name> </literal>— called before attempting to authenticate a user"
msgstr ""
#. Tag: para
#: Events.xml:571
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.notLoggedIn</literal> — called there is no "
-"authenticated user and authentication is required"
+msgid "<literal>org.jboss.seam.notLoggedIn</literal> — called there is no authenticated user and authentication is required"
msgstr ""
#. Tag: para
#: Events.xml:572
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.rememberMe</literal> — occurs when Seam "
-"security detects the username in a cookie"
+msgid "<literal>org.jboss.seam.rememberMe</literal> — occurs when Seam security detects the username in a cookie"
msgstr ""
#. Tag: para
#: Events.xml:573
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.exceptionHandled.<type></literal> — "
-"called when an uncaught exception is handled by Seam"
+msgid "<literal>org.jboss.seam.exceptionHandled.<type></literal> — called when an uncaught exception is handled by Seam"
msgstr ""
#. Tag: para
#: Events.xml:574
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.exceptionHandled</literal> — called when an "
-"uncaught exception is handled by Seam"
+msgid "<literal>org.jboss.seam.exceptionHandled</literal> — called when an uncaught exception is handled by Seam"
msgstr ""
#. Tag: para
#: Events.xml:575
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.exceptionNotHandled</literal> — called when "
-"there was no handler for an uncaught exception"
+msgid "<literal>org.jboss.seam.exceptionNotHandled</literal> — called when there was no handler for an uncaught exception"
msgstr ""
#. Tag: para
#: Events.xml:576
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.afterTransactionSuccess</literal> — called "
-"when a transaction succeeds in the Seam Application Framework"
+msgid "<literal>org.jboss.seam.afterTransactionSuccess</literal> — called when a transaction succeeds in the Seam Application Framework"
msgstr ""
#. Tag: para
#: Events.xml:577
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.afterTransactionSuccess.<name></literal> "
-"— called when a transaction succeeds in the Seam Application Framework "
-"which manages an entity called <literal><name></literal>"
+msgid "<literal>org.jboss.seam.afterTransactionSuccess.<name></literal> — called when a transaction succeeds in the Seam Application Framework which manages an entity called <literal><name></literal>"
msgstr ""
#. Tag: para
#: Events.xml:580
#, no-c-format
-msgid ""
-"Seam components may observe any of these events in just the same way they "
-"observe any other component-driven events."
+msgid "Seam components may observe any of these events in just the same way they observe any other component-driven events."
msgstr ""
#. Tag: title
@@ -1397,13 +1353,7 @@
#. Tag: para
#: Events.xml:591
#, no-c-format
-msgid ""
-"EJB 3.0 introduced a standard interceptor model for session bean components. "
-"To add an interceptor to a bean, you need to write a class with a method "
-"annotated <literal>@AroundInvoke</literal> and annotate the bean with an "
-"<literal>@Interceptors</literal> annotation that specifies the name of the "
-"interceptor class. For example, the following interceptor checks that the "
-"user is logged in before allowing invoking an action listener method:"
+msgid "EJB 3.0 introduced a standard interceptor model for session bean components. To add an interceptor to a bean, you need to write a class with a method annotated <literal>@AroundInvoke</literal> and annotate the bean with an <literal>@Interceptors</literal> annotation that specifies the name of the interceptor class. For example, the following interceptor checks that the user is logged in before allowing invoking an action listener method:"
msgstr ""
#. Tag: programlisting
@@ -1413,11 +1363,9 @@
"<![CDATA[public class LoggedInInterceptor {\n"
"\n"
" @AroundInvoke\n"
-" public Object checkLoggedIn(InvocationContext invocation) throws "
-"Exception {\n"
+" public Object checkLoggedIn(InvocationContext invocation) throws Exception {\n"
" \n"
-" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!"
-"=null;\n"
+" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!=null;\n"
" if (isLoggedIn) {\n"
" //the user is already logged in\n"
" return invocation.proceed();\n"
@@ -1430,19 +1378,28 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[public class LoggedInInterceptor {\n"
+"\n"
+" @AroundInvoke\n"
+" public Object checkLoggedIn(InvocationContext invocation) throws Exception {\n"
+" \n"
+" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!=null;\n"
+" if (isLoggedIn) {\n"
+" //the user is already logged in\n"
+" return invocation.proceed();\n"
+" }\n"
+" else {\n"
+" //the user is not logged in, fwd to login page\n"
+" return \"login\";\n"
+" }\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: para
#: Events.xml:602
#, no-c-format
-msgid ""
-"To apply this interceptor to a session bean which acts as an action "
-"listener, we must annotate the session bean <literal>@Interceptors"
-"(LoggedInInterceptor.class)</literal>. This is a somewhat ugly annotation. "
-"Seam builds upon the interceptor framework in EJB3 by allowing you to use "
-"<literal>@Interceptors</literal> as a meta-annotation for class level "
-"interceptors (those annotated <literal>@Target(TYPE)</literal>). In our "
-"example, we would create an <literal>@LoggedIn</literal> annotation, as "
-"follows:"
+msgid "To apply this interceptor to a session bean which acts as an action listener, we must annotate the session bean <literal>@Interceptors(LoggedInInterceptor.class)</literal>. This is a somewhat ugly annotation. Seam builds upon the interceptor framework in EJB3 by allowing you to use <literal>@Interceptors</literal> as a meta-annotation for class level interceptors (those annotated <literal>@Target(TYPE)</literal>). In our example, we would create an <literal>@LoggedIn</literal> annotation, as follows:"
msgstr ""
#. Tag: programlisting
@@ -1454,13 +1411,15 @@
"@Interceptors(LoggedInInterceptor.class)\n"
"public @interface LoggedIn {}]]>"
msgstr ""
+"<![CDATA[@Target(TYPE)\n"
+"@Retention(RUNTIME)\n"
+"@Interceptors(LoggedInInterceptor.class)\n"
+"public @interface LoggedIn {}]]>"
#. Tag: para
#: Events.xml:613
#, no-c-format
-msgid ""
-"We can now simply annotate our action listener bean with <literal>@LoggedIn</"
-"literal> to apply the interceptor."
+msgid "We can now simply annotate our action listener bean with <literal>@LoggedIn</literal> to apply the interceptor."
msgstr ""
#. Tag: programlisting
@@ -1479,14 +1438,22 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateless\n"
+"@Name(\"changePasswordAction\")\n"
+"@LoggedIn\n"
+"@Interceptors(SeamInterceptor.class)\n"
+"public class ChangePasswordAction implements ChangePassword { \n"
+" \n"
+" ...\n"
+" \n"
+" public String changePassword() { ... }\n"
+" \n"
+"}]]>"
#. Tag: para
#: Events.xml:620
#, no-c-format
-msgid ""
-"If interceptor ordering is important (it usually is), you can add "
-"<literal>@Interceptor</literal> annotations to your interceptor classes to "
-"specify a partial order of interceptors."
+msgid "If interceptor ordering is important (it usually is), you can add <literal>@Interceptor</literal> annotations to your interceptor classes to specify a partial order of interceptors."
msgstr ""
#. Tag: programlisting
@@ -1502,13 +1469,19 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@Interceptor(around={BijectionInterceptor.class,\n"
+" ValidationInterceptor.class,\n"
+" ConversationInterceptor.class},\n"
+" within=RemoveInterceptor.class)\n"
+"public class LoggedInInterceptor\n"
+"{\n"
+" ...\n"
+"}]]>"
#. Tag: para
#: Events.xml:628
#, no-c-format
-msgid ""
-"You can even have a \"client-side\" interceptor, that runs around any of the "
-"built-in functionality of EJB3:"
+msgid "You can even have a \"client-side\" interceptor, that runs around any of the built-in functionality of EJB3:"
msgstr ""
#. Tag: programlisting
@@ -1521,47 +1494,34 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@Interceptor(type=CLIENT)\n"
+"public class LoggedInInterceptor\n"
+"{\n"
+" ...\n"
+"}]]>"
#. Tag: para
#: Events.xml:635
#, no-c-format
-msgid ""
-"EJB interceptors are stateful, with a lifecycle that is the same as the "
-"component they intercept. For interceptors which do not need to maintain "
-"state, Seam lets you get a performance optimization by specifying "
-"<literal>@Interceptor(stateless=true)</literal>."
+msgid "EJB interceptors are stateful, with a lifecycle that is the same as the component they intercept. For interceptors which do not need to maintain state, Seam lets you get a performance optimization by specifying <literal>@Interceptor(stateless=true)</literal>."
msgstr ""
#. Tag: para
#: Events.xml:642
#, no-c-format
-msgid ""
-"Much of the functionality of Seam is implemented as a set of built-in Seam "
-"interceptors, including the interceptors named in the previous example. You "
-"don't have to explicitly specify these interceptors by annotating your "
-"components; they exist for all interceptable Seam components."
+msgid "Much of the functionality of Seam is implemented as a set of built-in Seam interceptors, including the interceptors named in the previous example. You don't have to explicitly specify these interceptors by annotating your components; they exist for all interceptable Seam components."
msgstr ""
#. Tag: para
#: Events.xml:649
#, no-c-format
-msgid ""
-"You can even use Seam interceptors with JavaBean components, not just EJB3 "
-"beans!"
+msgid "You can even use Seam interceptors with JavaBean components, not just EJB3 beans!"
msgstr ""
#. Tag: para
#: Events.xml:653
#, no-c-format
-msgid ""
-"EJB defines interception not only for business methods (using "
-"<literal>@AroundInvoke</literal>), but also for the lifecycle methods "
-"<literal>@PostConstruct</literal>, <literal>@PreDestroy</literal>, "
-"<literal>@PrePassivate</literal> and <literal>@PostActive</literal>. Seam "
-"supports all these lifecycle methods on both component and interceptor not "
-"only for EJB3 beans, but also for JavaBean components (except "
-"<literal>@PreDestroy</literal> which is not meaningful for JavaBean "
-"components)."
+msgid "EJB defines interception not only for business methods (using <literal>@AroundInvoke</literal>), but also for the lifecycle methods <literal>@PostConstruct</literal>, <literal>@PreDestroy</literal>, <literal>@PrePassivate</literal> and <literal>@PostActive</literal>. Seam supports all these lifecycle methods on both component and interceptor not only for EJB3 beans, but also for JavaBean components (except <literal>@PreDestroy</literal> which is not meaningful for JavaBean components)."
msgstr ""
#. Tag: title
@@ -1573,14 +1533,7 @@
#. Tag: para
#: Events.xml:667
#, no-c-format
-msgid ""
-"JSF is surprisingly limited when it comes to exception handling. As a "
-"partial workaround for this problem, Seam lets you define how a particular "
-"class of exception is to be treated by annotating the exception class, or "
-"declaring the exception class in an XML file. This facility is meant to be "
-"combined with the EJB 3.0-standard <literal>@ApplicationException</literal> "
-"annotation which specifies whether the exception should cause a transaction "
-"rollback."
+msgid "JSF is surprisingly limited when it comes to exception handling. As a partial workaround for this problem, Seam lets you define how a particular class of exception is to be treated by annotating the exception class, or declaring the exception class in an XML file. This facility is meant to be combined with the EJB 3.0-standard <literal>@ApplicationException</literal> annotation which specifies whether the exception should cause a transaction rollback."
msgstr ""
#. Tag: title
@@ -1592,46 +1545,25 @@
#. Tag: para
#: Events.xml:679
#, no-c-format
-msgid ""
-"EJB specifies well-defined rules that let us control whether an exception "
-"immediately marks the current transaction for rollback when it is thrown by "
-"a business method of the bean: <emphasis>system exceptions</emphasis> always "
-"cause a transaction rollback, <emphasis>application exceptions</emphasis> do "
-"not cause a rollback by default, but they do if "
-"<literal>@ApplicationException(rollback=true)</literal> is specified. (An "
-"application exception is any checked exception, or any unchecked exception "
-"annotated <literal>@ApplicationException</literal>. A system exception is "
-"any unchecked exception without an <literal>@ApplicationException</literal> "
-"annotation.)"
+msgid "EJB specifies well-defined rules that let us control whether an exception immediately marks the current transaction for rollback when it is thrown by a business method of the bean: <emphasis>system exceptions</emphasis> always cause a transaction rollback, <emphasis>application exceptions</emphasis> do not cause a rollback by default, but they do if <literal>@ApplicationException(rollback=true)</literal> is specified. (An application exception is any checked exception, or any unchecked exception annotated <literal>@ApplicationException</literal>. A system exception is any unchecked exception without an <literal>@ApplicationException</literal> annotation.)"
msgstr ""
#. Tag: para
#: Events.xml:692
#, no-c-format
-msgid ""
-"Note that there is a difference between marking a transaction for rollback, "
-"and actually rolling it back. The exception rules say that the transaction "
-"should be marked rollback only, but it may still be active after the "
-"exception is thrown."
+msgid "Note that there is a difference between marking a transaction for rollback, and actually rolling it back. The exception rules say that the transaction should be marked rollback only, but it may still be active after the exception is thrown."
msgstr ""
#. Tag: para
#: Events.xml:699
#, no-c-format
-msgid ""
-"Seam applies the EJB 3.0 exception rollback rules also to Seam JavaBean "
-"components."
+msgid "Seam applies the EJB 3.0 exception rollback rules also to Seam JavaBean components."
msgstr ""
#. Tag: para
#: Events.xml:704
#, no-c-format
-msgid ""
-"But these rules only apply in the Seam component layer. What about an "
-"exception that is uncaught and propagates out of the Seam component layer, "
-"and out of the JSF layer? Well, it is always wrong to leave a dangling "
-"transaction open, so Seam rolls back any active transaction when an "
-"exception occurs and is uncaught in the Seam component layer."
+msgid "But these rules only apply in the Seam component layer. What about an exception that is uncaught and propagates out of the Seam component layer, and out of the JSF layer? Well, it is always wrong to leave a dangling transaction open, so Seam rolls back any active transaction when an exception occurs and is uncaught in the Seam component layer."
msgstr ""
#. Tag: title
@@ -1643,9 +1575,7 @@
#. Tag: para
#: Events.xml:716
#, no-c-format
-msgid ""
-"To enable Seam's exception handling, we need to make sure we have the master "
-"servlet filter declared in <literal>web.xml</literal>:"
+msgid "To enable Seam's exception handling, we need to make sure we have the master servlet filter declared in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1662,14 +1592,20 @@
" <url-pattern>*.seam</url-pattern>\n"
"</filter-mapping>]]>"
msgstr ""
+"<![CDATA[<filter>\n"
+" <filter-name>Seam Filter</filter-name>\n"
+" <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>\n"
+"</filter>\n"
+"\n"
+"<filter-mapping>\n"
+" <filter-name>Seam Filter</filter-name>\n"
+" <url-pattern>*.seam</url-pattern>\n"
+"</filter-mapping>]]>"
#. Tag: para
#: Events.xml:723
#, no-c-format
-msgid ""
-"You need to disable Facelets development mode in <literal>web.xml</literal> "
-"and Seam debug mode in <literal>components.xml</literal> if you want your "
-"exception handlers to fire."
+msgid "You need to disable Facelets development mode in <literal>web.xml</literal> and Seam debug mode in <literal>components.xml</literal> if you want your exception handlers to fire."
msgstr ""
#. Tag: title
@@ -1681,11 +1617,7 @@
#. Tag: para
#: Events.xml:734
#, no-c-format
-msgid ""
-"The following exception results in a HTTP 404 error whenever it propagates "
-"out of the Seam component layer. It does not roll back the current "
-"transaction immediately when thrown, but the transaction will be rolled back "
-"if it the exception is not caught by another Seam component."
+msgid "The following exception results in a HTTP 404 error whenever it propagates out of the Seam component layer. It does not roll back the current transaction immediately when thrown, but the transaction will be rolled back if it the exception is not caught by another Seam component."
msgstr ""
#. Tag: programlisting
@@ -1695,14 +1627,13 @@
"<![CDATA[@HttpError(errorCode=404)\n"
"public class ApplicationException extends Exception { ... }]]>"
msgstr ""
+"<![CDATA[@HttpError(errorCode=404)\n"
+"public class ApplicationException extends Exception { ... }]]>"
#. Tag: para
#: Events.xml:743
#, no-c-format
-msgid ""
-"This exception results in a browser redirect whenever it propagates out of "
-"the Seam component layer. It also ends the current conversation. It causes "
-"an immediate rollback of the current transaction."
+msgid "This exception results in a browser redirect whenever it propagates out of the Seam component layer. It also ends the current conversation. It causes an immediate rollback of the current transaction."
msgstr ""
#. Tag: programlisting
@@ -1711,33 +1642,28 @@
msgid ""
"<![CDATA[@Redirect(viewId=\"/failure.xhtml\", end=true)\n"
"@ApplicationException(rollback=true)\n"
-"public class UnrecoverableApplicationException extends RuntimeException "
-"{ ... }]]>"
+"public class UnrecoverableApplicationException extends RuntimeException { ... }]]>"
msgstr ""
+"<![CDATA[@Redirect(viewId=\"/failure.xhtml\", end=true)\n"
+"@ApplicationException(rollback=true)\n"
+"public class UnrecoverableApplicationException extends RuntimeException { ... }]]>"
#. Tag: note
#: Events.xml:751
#, no-c-format
-msgid ""
-"It is important to note that Seam cannot handle exceptions that occur during "
-"JSF's RENDER_RESPONSE phase, as it is not possible to perform a redirect "
-"once the response has started being written to."
+msgid "It is important to note that Seam cannot handle exceptions that occur during JSF's RENDER_RESPONSE phase, as it is not possible to perform a redirect once the response has started being written to."
msgstr ""
#. Tag: para
#: Events.xml:757
#, no-c-format
-msgid ""
-"You can also use EL to specify the <literal>viewId</literal> to redirect to."
+msgid "You can also use EL to specify the <literal>viewId</literal> to redirect to."
msgstr ""
#. Tag: para
#: Events.xml:761
#, no-c-format
-msgid ""
-"This exception results in a redirect, along with a message to the user, when "
-"it propagates out of the Seam component layer. It also immediately rolls "
-"back the current transaction."
+msgid "This exception results in a redirect, along with a message to the user, when it propagates out of the Seam component layer. It also immediately rolls back the current transaction."
msgstr ""
#. Tag: programlisting
@@ -1747,6 +1673,8 @@
"<![CDATA[@Redirect(viewId=\"/error.xhtml\", message=\"Unexpected error\")\n"
"public class SystemException extends RuntimeException { ... }]]>"
msgstr ""
+"<![CDATA[@Redirect(viewId=\"/error.xhtml\", message=\"Unexpected error\")\n"
+"public class SystemException extends RuntimeException { ... }]]>"
#. Tag: title
#: Events.xml:772
@@ -1757,10 +1685,7 @@
#. Tag: para
#: Events.xml:774
#, no-c-format
-msgid ""
-"Since we can't add annotations to all the exception classes we are "
-"interested in, Seam also lets us specify this functionality in "
-"<literal>pages.xml</literal>."
+msgid "Since we can't add annotations to all the exception classes we are interested in, Seam also lets us specify this functionality in <literal>pages.xml</literal>."
msgstr ""
#. Tag: programlisting
@@ -1789,29 +1714,44 @@
" \n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" \n"
+" <exception class=\"javax.persistence.EntityNotFoundException\">\n"
+" <http-error error-code=\"404\"/>\n"
+" </exception>\n"
+" \n"
+" <exception class=\"javax.persistence.PersistenceException\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>Database access failed</message>\n"
+" </redirect>\n"
+" </exception>\n"
+" \n"
+" <exception>\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>Unexpected failure</message>\n"
+" </redirect>\n"
+" </exception>\n"
+" \n"
+"</pages>]]>"
#. Tag: para
#: Events.xml:781
#, no-c-format
-msgid ""
-"The last <literal><exception></literal> declaration does not specify a "
-"class, and is a catch-all for any exception for which handling is not "
-"otherwise specified via annotations or in <literal>pages.xml</literal>."
+msgid "The last <literal><exception></literal> declaration does not specify a class, and is a catch-all for any exception for which handling is not otherwise specified via annotations or in <literal>pages.xml</literal>."
msgstr ""
#. Tag: para
#: Events.xml:787
#, no-c-format
-msgid ""
-"You can also use EL to specify the <literal>view-id</literal> to redirect to."
+msgid "You can also use EL to specify the <literal>view-id</literal> to redirect to."
msgstr ""
#. Tag: para
#: Events.xml:791
#, no-c-format
-msgid ""
-"You can also access the handled exception instance through EL, Seam places "
-"it in the conversation context, e.g. to access the message of the exception:"
+msgid "You can also access the handled exception instance through EL, Seam places it in the conversation context, e.g. to access the message of the exception:"
msgstr ""
#. Tag: programlisting
@@ -1826,22 +1766,30 @@
" <exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message severity=\"WARN\">#{org.jboss.seam.handledException."
-"message}</message>\n"
+" <message severity=\"WARN\">#{org.jboss.seam.handledException.message}</message>\n"
" </redirect>\n"
" </exception>\n"
"\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[...\n"
+"throw new AuthorizationException(\"You are not allowed to do this!\");\n"
+"\n"
+"<pages>\n"
+"\n"
+" <exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message severity=\"WARN\">#{org.jboss.seam.handledException.message}</message>\n"
+" </redirect>\n"
+" </exception>\n"
+"\n"
+"</pages>]]>"
#. Tag: para
#: Events.xml:798
#, no-c-format
-msgid ""
-"<literal>org.jboss.seam.handledException</literal> holds the nested "
-"exception that was actually handled by an exception handler. The outermost "
-"(wrapper) exception is also available, as <literal>org.jboss.seam."
-"caughtException</literal>."
+msgid "<literal>org.jboss.seam.handledException</literal> holds the nested exception that was actually handled by an exception handler. The outermost (wrapper) exception is also available, as <literal>org.jboss.seam.caughtException</literal>."
msgstr ""
#. Tag: title
@@ -1853,60 +1801,51 @@
#. Tag: para
#: Events.xml:807
#, no-c-format
-msgid ""
-"For the exception handlers defined in <literal>pages.xml</literal>, it is "
-"possible to declare the logging level at which the exception will be logged, "
-"or to even suppress the exception being logged altogether. The attributes "
-"<literal>log</literal> and <literal>logLevel</literal> can be used to "
-"control exception logging. By setting <literal>log=\"false\"</literal> as "
-"per the following example, then no log message will be generated when the "
-"specified exception occurs:"
+msgid "For the exception handlers defined in <literal>pages.xml</literal>, it is possible to declare the logging level at which the exception will be logged, or to even suppress the exception being logged altogether. The attributes <literal>log</literal> and <literal>logLevel</literal> can be used to control exception logging. By setting <literal>log=\"false\"</literal> as per the following example, then no log message will be generated when the specified exception occurs:"
msgstr ""
#. Tag: programlisting
#: Events.xml:816
#, no-c-format
msgid ""
-"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException"
-"\" log=\"false\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" log=\"false\">\n"
" <redirect view-id=\"/register.xhtml\">\n"
-" <message severity=\"warn\">You must be a member to use this "
-"feature</message>\n"
+" <message severity=\"warn\">You must be a member to use this feature</message>\n"
" </redirect>\n"
" </exception>]]>"
msgstr ""
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" log=\"false\">\n"
+" <redirect view-id=\"/register.xhtml\">\n"
+" <message severity=\"warn\">You must be a member to use this feature</message>\n"
+" </redirect>\n"
+" </exception>]]>"
#. Tag: para
#: Events.xml:818
#, no-c-format
-msgid ""
-"If the <literal>log</literal> attribute is not specified, then it defaults "
-"to <literal>true</literal> (i.e. the exception will be logged). "
-"Alternatively, you can specify the <literal>logLevel</literal> to control at "
-"which log level the exception will be logged:"
+msgid "If the <literal>log</literal> attribute is not specified, then it defaults to <literal>true</literal> (i.e. the exception will be logged). Alternatively, you can specify the <literal>logLevel</literal> to control at which log level the exception will be logged:"
msgstr ""
#. Tag: programlisting
#: Events.xml:824
#, no-c-format
msgid ""
-"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException"
-"\" logLevel=\"info\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" logLevel=\"info\">\n"
" <redirect view-id=\"/register.xhtml\">\n"
-" <message severity=\"warn\">You must be a member to use this "
-"feature</message>\n"
+" <message severity=\"warn\">You must be a member to use this feature</message>\n"
" </redirect>\n"
" </exception>]]>"
msgstr ""
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" logLevel=\"info\">\n"
+" <redirect view-id=\"/register.xhtml\">\n"
+" <message severity=\"warn\">You must be a member to use this feature</message>\n"
+" </redirect>\n"
+" </exception>]]>"
#. Tag: para
#: Events.xml:826
#, no-c-format
-msgid ""
-"The acceptable values for <literal>logLevel</literal> are: <literal>fatal, "
-"error, warn, info, debug</literal> or <literal>trace</literal>. If the "
-"<literal>logLevel</literal> is not specified, or if an invalid value is "
-"configured, then it will default to <literal>error</literal>."
+msgid "The acceptable values for <literal>logLevel</literal> are: <literal>fatal, error, warn, info, debug</literal> or <literal>trace</literal>. If the <literal>logLevel</literal> is not specified, or if an invalid value is configured, then it will default to <literal>error</literal>."
msgstr ""
#. Tag: title
@@ -1934,11 +1873,22 @@
"<exception class=\"javax.persistence.OptimisticLockException\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message>Another user changed the same data, please try again</"
-"message>\n"
+" <message>Another user changed the same data, please try again</message>\n"
" </redirect>\n"
"</exception>]]>"
msgstr ""
+"<![CDATA[<exception class=\"javax.persistence.EntityNotFoundException\">\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>Not found</message>\n"
+" </redirect>\n"
+"</exception>\n"
+"\n"
+"<exception class=\"javax.persistence.OptimisticLockException\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>Another user changed the same data, please try again</message>\n"
+" </redirect>\n"
+"</exception>]]>"
#. Tag: para
#: Events.xml:845
@@ -1950,13 +1900,17 @@
#: Events.xml:849
#, no-c-format
msgid ""
-"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException"
-"\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException\">\n"
" <redirect view-id=\"/error.xhtml\">\n"
" <message>Not found</message>\n"
" </redirect>\n"
"</exception>]]>"
msgstr ""
+"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException\">\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>Not found</message>\n"
+" </redirect>\n"
+"</exception>]]>"
#. Tag: para
#: Events.xml:851
@@ -1968,8 +1922,7 @@
#: Events.xml:855
#, no-c-format
msgid ""
-"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException"
-"\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
" <redirect>\n"
" <message>You don't have permission to do this</message>\n"
" </redirect>\n"
@@ -1981,6 +1934,17 @@
" </redirect>\n"
"</exception>]]>"
msgstr ""
+"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
+" <redirect>\n"
+" <message>You don't have permission to do this</message>\n"
+" </redirect>\n"
+"</exception>\n"
+" \n"
+"<exception class=\"org.jboss.seam.security.NotLoggedInException\">\n"
+" <redirect view-id=\"/login.xhtml\">\n"
+" <message>Please log in first</message>\n"
+" </redirect>\n"
+"</exception>]]>"
#. Tag: para
#: Events.xml:857
@@ -1998,15 +1962,16 @@
" </redirect>\n"
"</exception>]]>"
msgstr ""
+"<![CDATA[<exception class=\"javax.faces.application.ViewExpiredException\">\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>Your session has timed out, please try again</message>\n"
+" </redirect>\n"
+"</exception>]]>"
#. Tag: para
#: Events.xml:863
#, no-c-format
-msgid ""
-"A <literal>ViewExpiredException</literal> occurs if the user posts back to a "
-"page once their session has expired. <literal>no-conversation-view-id</"
-"literal> and <literal>conversation-required</literal> give you finer grained "
-"control over session expiration if you are inside a conversation."
+msgid "A <literal>ViewExpiredException</literal> occurs if the user posts back to a page once their session has expired. <literal>no-conversation-view-id</literal> and <literal>conversation-required</literal> give you finer grained control over session expiration if you are inside a conversation."
msgstr ""
#. Tag: title
@@ -2018,19 +1983,12 @@
#. Tag: para
#: Events.xml:875
#, no-c-format
-msgid ""
-"When specified as the attribute of a <literal>page</literal> element in "
-"<literal>pages.xml</literal>, this setting controls whether a page requires "
-"an active long-running or nested conversation before being rendered. If "
-"there is not an active long-running or nested conversation when trying to "
-"access the page, you will be redirected to the <literal>no-conversation-view-"
-"id</literal> view (which is specified in the root <literal>pages</literal> "
-"element) instead."
+msgid "When specified as the attribute of a <literal>page</literal> element in <literal>pages.xml</literal>, this setting controls whether a page requires an active long-running or nested conversation before being rendered. If there is not an active long-running or nested conversation when trying to access the page, you will be redirected to the <literal>no-conversation-view-id</literal> view (which is specified in the root <literal>pages</literal> element) instead."
msgstr ""
#. Tag: programlisting
#: Events.xml:883
#, no-c-format
-msgid ""
-"<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
-msgstr ""
+msgid "<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
+msgstr "<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 15:50:47 UTC (rev 9783)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 17:36:40 UTC (rev 9784)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-15 06:47+0100\n"
+"PO-Revision-Date: 2008-12-15 18:16+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -343,7 +343,7 @@
#: Jbpm.xml:178
#, no-c-format
msgid "The stateful/stateless navigation distinction is quite similar to the traditional view of modal/modeless interaction. Now, Seam applications are not usually modal in the simple sense of the word - indeed, avoiding application modal behavior is one of the main reasons for having conversations! However, Seam applications can be, and often are, modal at the level of a particular conversation. It is well-known that modal behavior is something to avoid as much as possible; it is very difficult to predict the order in which your users are going to want to do things! However, there is no doubt that the stateful model has its place."
-msgstr ""
+msgstr "La distinzione di navigazione stateful/stateless è abbastanza simile alla tradizionale vista di interazione modale/senza modello. Ora le applicazioni Seam non sono solitamente modali nel semplice senso della parola - infatti, evitare il comportamento modale dell'applicazione è uno delle principali ragioni per usare le conversazioni! Comunque le applicazioni Seam possono essere, e spesso lo sono, modali a livello di una particolare conversazione. E' noto che il comportamento modale è qualcosa da evitare il più possibile; è molto difficile predire l'ordine in cui gli utenti vogliono fare le cose! Comunque non c'è dubbio che il modello stateful ha un suo utilizzo."
#. Tag: para
#: Jbpm.xml:191
@@ -361,7 +361,7 @@
#: Jbpm.xml:201
#, no-c-format
msgid "When JSF or Seam navigation rules are used, Seam lets the user freely navigate via the back, forward and refresh buttons. It is the responsibility of the application to ensure that conversational state remains internally consistent when this occurs. Experience with the combination of web application frameworks like Struts or WebWork - that do not support a conversational model - and stateless component models like EJB stateless session beans or the Spring framework has taught many developers that this is close to impossible to do! However, our experience is that in the context of Seam, where there is a well-defined conversational model, backed by stateful session beans, it is actually quite straightforward. Usually it is as simple as combining the use of <literal>no-conversation-view-id</literal> with null checks at the beginning of action listener methods. We consider support for freeform navigation to be almost always desirable."
-msgstr ""
+msgstr "Quando le regole di navigazione di JSF o Seam vendono impiegate, Seam consente all'utente di navigare liberamente avanti ed indietro e di usare il pulsante aggiorna. E' responsabilità dell'applicazione assicurare che lo stato conversazionale rimanga internamente consistente quando questo avviene. L'esperienza con la combinazione di framework web come Struts o WebWork - che non supportano un modello conversazionale - e modelli a componenti stateless come session bean EJB stateless o il framework Spring ha insegnato a molti sviluppatori che questo è quasi praticamente impossibile da realizzare! Comunqur la nostra esperienza è che il contesto di Seam, dove c'è un modello conversazionale ben definito, agganciato a session bean stateful, è in verità abbastanza semplice. E' tanto semplice quanto combinare l'uso di <literal>no-conversation-view-id</literal> con controlli nulli all'inizio di metodi action listener. Riteniamo che il supporto alla navigazione libera sia!
quasi sempre desiderabile."
#. Tag: para
#: Jbpm.xml:219
@@ -517,7 +517,7 @@
#: Jbpm.xml:308
#, no-c-format
msgid "Alternatively we can start a pageflow using pages.xml:"
-msgstr ""
+msgstr "In alternativa possiamo iniziare un pageflow usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:310
@@ -966,7 +966,7 @@
#: Jbpm.xml:549
#, no-c-format
msgid "To initiate a business process instance, we use the <literal>@CreateProcess</literal> annotation:"
-msgstr ""
+msgstr "Per iniziare un'istanza di processo di business, usiamo l'annotazione <literal>@CreateProcess</literal>:"
#. Tag: programlisting
#: Jbpm.xml:554
@@ -982,7 +982,7 @@
#: Jbpm.xml:556
#, no-c-format
msgid "Alternatively we can initiate a business process using pages.xml:"
-msgstr ""
+msgstr "In alternativa possiamo iniziare un processo di business usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:558
@@ -1154,7 +1154,7 @@
#: Jbpm.xml:624
#, no-c-format
msgid "Alternatively we can begin work on a task using pages.xml:"
-msgstr ""
+msgstr "In alternativa possiamo iniziare a lavorare su un task usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:626
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jms.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jms.po 2008-12-15 15:50:47 UTC (rev 9783)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jms.po 2008-12-15 17:36:40 UTC (rev 9784)
@@ -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:38+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-15 18:19+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,114 +17,78 @@
#: Jms.xml:2
#, no-c-format
msgid "Asynchronicity and messaging"
-msgstr ""
+msgstr "Asincronicità e messaggistica"
#. Tag: para
#: Jms.xml:3
#, no-c-format
-msgid ""
-"Seam makes it very easy to perform work asynchronously from a web request. "
-"When most people think of asynchronicity in Java EE, they think of using "
-"JMS. This is certainly one way to approach the problem in Seam, and is the "
-"right way when you have strict and well-defined quality of service "
-"requirements. Seam makes it easy to send and recieve JMS messages using Seam "
-"components."
+msgid "Seam makes it very easy to perform work asynchronously from a web request. When most people think of asynchronicity in Java EE, they think of using JMS. This is certainly one way to approach the problem in Seam, and is the right way when you have strict and well-defined quality of service requirements. Seam makes it easy to send and recieve JMS messages using Seam components."
msgstr ""
#. Tag: para
#: Jms.xml:11
#, no-c-format
-msgid ""
-"But for many usecases, JMS is overkill. Seam layers a simple asynchronous "
-"method and event facility over your choice of <emphasis>dispatchers</"
-"emphasis>:"
+msgid "But for many usecases, JMS is overkill. Seam layers a simple asynchronous method and event facility over your choice of <emphasis>dispatchers</emphasis>:"
msgstr ""
#. Tag: para
#: Jms.xml:18
#, no-c-format
-msgid ""
-"<literal>java.util.concurrent.ScheduledThreadPoolExecutor</literal> (by "
-"default)"
+msgid "<literal>java.util.concurrent.ScheduledThreadPoolExecutor</literal> (by default)"
msgstr ""
#. Tag: para
#: Jms.xml:23
#, no-c-format
msgid "the EJB timer service (for EJB 3.0 environments)"
-msgstr ""
+msgstr "Il servizio EJB timer (per ambienti EJB 3.0)"
#. Tag: para
#: Jms.xml:28
#, no-c-format
msgid "Quartz"
-msgstr ""
+msgstr "Quartz"
#. Tag: title
#: Jms.xml:35
#, no-c-format
msgid "Asynchronicity"
-msgstr ""
+msgstr "Asincronicità"
#. Tag: para
#: Jms.xml:37
#, no-c-format
-msgid ""
-"Asynchronous events and method calls have the same quality of service "
-"expectations as the underlying dispatcher mechanism. The default dispatcher, "
-"based upon a <literal>ScheduledThreadPoolExecutor</literal> performs "
-"efficiently but provides no support for persistent asynchronous tasks, and "
-"hence no guarantee that a task will ever actually be executed. If you're "
-"working in an environment that supports EJB 3.0, and add the following line "
-"to <literal>components.xml</literal>:"
+msgid "Asynchronous events and method calls have the same quality of service expectations as the underlying dispatcher mechanism. The default dispatcher, based upon a <literal>ScheduledThreadPoolExecutor</literal> performs efficiently but provides no support for persistent asynchronous tasks, and hence no guarantee that a task will ever actually be executed. If you're working in an environment that supports EJB 3.0, and add the following line to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
#: Jms.xml:46
#, no-c-format
msgid "<![CDATA[<async:timer-service-dispatcher/>]]>"
-msgstr ""
+msgstr "<![CDATA[<async:timer-service-dispatcher/>]]>"
#. Tag: para
#: Jms.xml:48
#, no-c-format
-msgid ""
-"then your asynchronous tasks will be processed by the container's EJB timer "
-"service. If you're not familiar with the Timer service, don't worry, you "
-"don't need to interact with it directly if you want to use asynchronous "
-"methods in Seam. The important thing to know is that any good EJB 3.0 "
-"implementation will have the option of using persistent timers, which gives "
-"some guarantee that the tasks will eventually be processed."
+msgid "then your asynchronous tasks will be processed by the container's EJB timer service. If you're not familiar with the Timer service, don't worry, you don't need to interact with it directly if you want to use asynchronous methods in Seam. The important thing to know is that any good EJB 3.0 implementation will have the option of using persistent timers, which gives some guarantee that the tasks will eventually be processed."
msgstr ""
#. Tag: para
#: Jms.xml:56
#, no-c-format
-msgid ""
-"Another alternative is to use the open source Quartz library to manage "
-"asynchronous method. You need to bundle the Quartz library JAR (found in the "
-"<literal>lib</literal> directory) in your EAR and declare it as a Java "
-"module in <literal>application.xml</literal>. The Quartz dispatcher may be "
-"configured by adding a Quartz property file to the classpath. It must be "
-"named <literal>seam.quartz.properties</literal>. In addition, you need to "
-"add the following line to <literal>components.xml</literal> to install the "
-"Quartz dispatcher."
+msgid "Another alternative is to use the open source Quartz library to manage asynchronous method. You need to bundle the Quartz library JAR (found in the <literal>lib</literal> directory) in your EAR and declare it as a Java module in <literal>application.xml</literal>. The Quartz dispatcher may be configured by adding a Quartz property file to the classpath. It must be named <literal>seam.quartz.properties</literal>. In addition, you need to add the following line to <literal>components.xml</literal> to install the Quartz dispatcher."
msgstr ""
#. Tag: programlisting
#: Jms.xml:66
#, no-c-format
msgid "<![CDATA[<async:quartz-dispatcher/>]]>"
-msgstr ""
+msgstr "<![CDATA[<async:quartz-dispatcher/>]]>"
#. Tag: para
#: Jms.xml:68
#, no-c-format
-msgid ""
-"The Seam API for the default <literal>ScheduledThreadPoolExecutor</literal>, "
-"the EJB3 <literal>Timer</literal>, and the Quartz <literal>Scheduler</"
-"literal> are largely the same. They can just \"plug and play\" by adding a "
-"line to <literal>components.xml</literal>."
+msgid "The Seam API for the default <literal>ScheduledThreadPoolExecutor</literal>, the EJB3 <literal>Timer</literal>, and the Quartz <literal>Scheduler</literal> are largely the same. They can just \"plug and play\" by adding a line to <literal>components.xml</literal>."
msgstr ""
#. Tag: title
@@ -136,21 +100,13 @@
#. Tag: para
#: Jms.xml:77
#, no-c-format
-msgid ""
-"In simplest form, an asynchronous call just lets a method call be processed "
-"asynchronously (in a different thread) from the caller. We usually use an "
-"asynchronous call when we want to return an immediate response to the "
-"client, and let some expensive work be processed in the background. This "
-"pattern works very well in applications which use AJAX, where the client can "
-"automatically poll the server for the result of the work."
+msgid "In simplest form, an asynchronous call just lets a method call be processed asynchronously (in a different thread) from the caller. We usually use an asynchronous call when we want to return an immediate response to the client, and let some expensive work be processed in the background. This pattern works very well in applications which use AJAX, where the client can automatically poll the server for the result of the work."
msgstr ""
#. Tag: para
#: Jms.xml:85
#, no-c-format
-msgid ""
-"For EJB components, we annotate the local interface to specify that a method "
-"is processed asynchronously."
+msgid "For EJB components, we annotate the local interface to specify that a method is processed asynchronously."
msgstr ""
#. Tag: programlisting
@@ -164,13 +120,17 @@
" public void processPayment(Payment payment);\n"
"}]]>"
msgstr ""
+"<![CDATA[@Local\n"
+"public interface PaymentHandler\n"
+"{\n"
+" @Asynchronous\n"
+" public void processPayment(Payment payment);\n"
+"}]]>"
#. Tag: para
#: Jms.xml:92
#, no-c-format
-msgid ""
-"(For JavaBean components we can annotate the component implementation class "
-"if we like.)"
+msgid "(For JavaBean components we can annotate the component implementation class if we like.)"
msgstr ""
#. Tag: para
@@ -193,6 +153,15 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateless\n"
+"@Name(\"paymentHandler\")\n"
+"public class PaymentHandlerBean implements PaymentHandler\n"
+"{\n"
+" public void processPayment(Payment payment)\n"
+" {\n"
+" //do some work!\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Jms.xml:102
@@ -218,24 +187,30 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"paymentAction\")\n"
+"public class CreatePaymentAction\n"
+"{\n"
+" @In(create=true) PaymentHandler paymentHandler;\n"
+" @In Bill bill;\n"
+" \n"
+" public String pay()\n"
+" {\n"
+" paymentHandler.processPayment( new Payment(bill) );\n"
+" return \"success\";\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Jms.xml:108
#, no-c-format
-msgid ""
-"The asynchronous method is processed in a completely new event context and "
-"does not have access to the session or conversation context state of the "
-"caller. However, the business process context <emphasis>is</emphasis> "
-"propagated."
+msgid "The asynchronous method is processed in a completely new event context and does not have access to the session or conversation context state of the caller. However, the business process context <emphasis>is</emphasis> propagated."
msgstr ""
#. Tag: para
#: Jms.xml:114
#, no-c-format
-msgid ""
-"Asynchronous method calls may be scheduled for later execution using the "
-"<literal>@Duration</literal>, <literal>@Expiration</literal> and "
-"<literal>@IntervalDuration</literal> annotations."
+msgid "Asynchronous method calls may be scheduled for later execution using the <literal>@Duration</literal>, <literal>@Expiration</literal> and <literal>@IntervalDuration</literal> annotations."
msgstr ""
#. Tag: programlisting
@@ -246,8 +221,7 @@
"public interface PaymentHandler\n"
"{\n"
" @Asynchronous\n"
-" public void processScheduledPayment(Payment payment, @Expiration Date "
-"date);\n"
+" public void processScheduledPayment(Payment payment, @Expiration Date date);\n"
"\n"
" @Asynchronous\n"
" public void processRecurringPayment(Payment payment, \n"
@@ -255,6 +229,17 @@
" @IntervalDuration Long interval)'\n"
"}]]>"
msgstr ""
+"<![CDATA[@Local\n"
+"public interface PaymentHandler\n"
+"{\n"
+" @Asynchronous\n"
+" public void processScheduledPayment(Payment payment, @Expiration Date date);\n"
+"\n"
+" @Asynchronous\n"
+" public void processRecurringPayment(Payment payment, \n"
+" @Expiration Date date, \n"
+" @IntervalDuration Long interval)'\n"
+"}]]>"
#. Tag: programlisting
#: Jms.xml:122
@@ -269,32 +254,43 @@
" \n"
" public String schedulePayment()\n"
" {\n"
-" paymentHandler.processScheduledPayment( new Payment(bill), bill."
-"getDueDate() );\n"
+" paymentHandler.processScheduledPayment( new Payment(bill), bill.getDueDate() );\n"
" return \"success\";\n"
" }\n"
"\n"
" public String scheduleRecurringPayment()\n"
" {\n"
-" paymentHandler.processRecurringPayment( new Payment(bill), bill."
-"getDueDate(), \n"
+" paymentHandler.processRecurringPayment( new Payment(bill), bill.getDueDate(), \n"
" ONE_MONTH );\n"
" return \"success\";\n"
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"paymentAction\")\n"
+"public class CreatePaymentAction\n"
+"{\n"
+" @In(create=true) PaymentHandler paymentHandler;\n"
+" @In Bill bill;\n"
+" \n"
+" public String schedulePayment()\n"
+" {\n"
+" paymentHandler.processScheduledPayment( new Payment(bill), bill.getDueDate() );\n"
+" return \"success\";\n"
+" }\n"
+"\n"
+" public String scheduleRecurringPayment()\n"
+" {\n"
+" paymentHandler.processRecurringPayment( new Payment(bill), bill.getDueDate(), \n"
+" ONE_MONTH );\n"
+" return \"success\";\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Jms.xml:124
#, no-c-format
-msgid ""
-"Both client and server may access the <literal>Timer</literal> object "
-"associated with the invocation. The <literal>Timer</literal> object shown "
-"below is the EJB3 timer when you use the EJB3 dispatcher. For the default "
-"<literal>ScheduledThreadPoolExecutor</literal>, the returned object is "
-"<literal>Future</literal> from the JDK. For the Quartz dispatcher, it "
-"returns <literal>QuartzTriggerHandle</literal>, which we will discuss in the "
-"next section."
+msgid "Both client and server may access the <literal>Timer</literal> object associated with the invocation. The <literal>Timer</literal> object shown below is the EJB3 timer when you use the EJB3 dispatcher. For the default <literal>ScheduledThreadPoolExecutor</literal>, the returned object is <literal>Future</literal> from the JDK. For the Quartz dispatcher, it returns <literal>QuartzTriggerHandle</literal>, which we will discuss in the next section."
msgstr ""
#. Tag: programlisting
@@ -305,10 +301,15 @@
"public interface PaymentHandler\n"
"{\n"
" @Asynchronous\n"
-" public Timer processScheduledPayment(Payment payment, @Expiration Date "
-"date);\n"
+" public Timer processScheduledPayment(Payment payment, @Expiration Date date);\n"
"}]]>"
msgstr ""
+"<![CDATA[@Local\n"
+"public interface PaymentHandler\n"
+"{\n"
+" @Asynchronous\n"
+" public Timer processScheduledPayment(Payment payment, @Expiration Date date);\n"
+"}]]>"
#. Tag: programlisting
#: Jms.xml:131
@@ -320,8 +321,7 @@
"{\n"
" @In Timer timer;\n"
" \n"
-" public Timer processScheduledPayment(Payment payment, @Expiration Date "
-"date)\n"
+" public Timer processScheduledPayment(Payment payment, @Expiration Date date)\n"
" {\n"
" //do some work!\n"
" \n"
@@ -330,6 +330,20 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateless\n"
+"@Name(\"paymentHandler\")\n"
+"public class PaymentHandlerBean implements PaymentHandler\n"
+"{\n"
+" @In Timer timer;\n"
+" \n"
+" public Timer processScheduledPayment(Payment payment, @Expiration Date date)\n"
+" {\n"
+" //do some work!\n"
+" \n"
+" return timer; //note that return value is completely ignored\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: programlisting
#: Jms.xml:133
@@ -344,14 +358,26 @@
" \n"
" public String schedulePayment()\n"
" {\n"
-" Timer timer = paymentHandler.processScheduledPayment( new Payment"
-"(bill), \n"
-" bill.getDueDate"
-"() );\n"
+" Timer timer = paymentHandler.processScheduledPayment( new Payment(bill), \n"
+" bill.getDueDate() );\n"
" return \"success\";\n"
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"paymentAction\")\n"
+"public class CreatePaymentAction\n"
+"{\n"
+" @In(create=true) PaymentHandler paymentHandler;\n"
+" @In Bill bill;\n"
+" \n"
+" public String schedulePayment()\n"
+" {\n"
+" Timer timer = paymentHandler.processScheduledPayment( new Payment(bill), \n"
+" bill.getDueDate() );\n"
+" return \"success\";\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Jms.xml:135
@@ -368,21 +394,13 @@
#. Tag: para
#: Jms.xml:144
#, no-c-format
-msgid ""
-"The Quartz dispatcher (see earlier on how to install it) allows you to use "
-"the <literal>@Asynchronous</literal>, <literal>@Duration</literal>, "
-"<literal>@Expiration</literal>, and <literal>@IntervalDuration</literal> "
-"annotations as above. But it has some powerful additional features. The "
-"Quartz dispatcher supports three new annotations."
+msgid "The Quartz dispatcher (see earlier on how to install it) allows you to use the <literal>@Asynchronous</literal>, <literal>@Duration</literal>, <literal>@Expiration</literal>, and <literal>@IntervalDuration</literal> annotations as above. But it has some powerful additional features. The Quartz dispatcher supports three new annotations."
msgstr ""
#. Tag: para
#: Jms.xml:148
#, no-c-format
-msgid ""
-"The <literal>@FinalExpiration</literal> annotation specifies an end date for "
-"the recurring task. Note that you can inject the <code>QuartzTriggerHandle</"
-"code>."
+msgid "The <literal>@FinalExpiration</literal> annotation specifies an end date for the recurring task. Note that you can inject the <code>QuartzTriggerHandle</code>."
msgstr ""
#. Tag: programlisting
@@ -408,20 +426,35 @@
" // Starts now, repeats every hour, and ends on May 10th, 2010\n"
" Calendar cal = Calendar.getInstance ();\n"
" cal.set (2010, Calendar.MAY, 10);\n"
-" processor.schedulePayment(new Date(), 60*60*1000, cal.getTime(), "
-"payment);\n"
+" processor.schedulePayment(new Date(), 60*60*1000, cal.getTime(), payment);\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+" @In QuartzTriggerHandle timer;\n"
+" \n"
+" // Defines the method in the \"processor\" component\n"
+" @Asynchronous\n"
+" public QuartzTriggerHandle schedulePayment(@Expiration Date when, \n"
+" @IntervalDuration Long interval,\n"
+" @FinalExpiration Date endDate, \n"
+" Payment payment) \n"
+" { \n"
+" // do the repeating or long running task until endDate\n"
+" }\n"
+" \n"
+" ... ...\n"
+" \n"
+" // Schedule the task in the business logic processing code\n"
+" // Starts now, repeats every hour, and ends on May 10th, 2010\n"
+" Calendar cal = Calendar.getInstance ();\n"
+" cal.set (2010, Calendar.MAY, 10);\n"
+" processor.schedulePayment(new Date(), 60*60*1000, cal.getTime(), payment);\n"
+"]]>"
#. Tag: para
#: Jms.xml:152
#, no-c-format
-msgid ""
-"Note that the method returns the <literal>QuartzTriggerHandle</literal> "
-"object, which you can use later to stop, pause, and resume the scheduler. "
-"The <literal>QuartzTriggerHandle</literal> object is serializable, so you "
-"can save it into the database if you need to keep it around for extended "
-"period of time."
+msgid "Note that the method returns the <literal>QuartzTriggerHandle</literal> object, which you can use later to stop, pause, and resume the scheduler. The <literal>QuartzTriggerHandle</literal> object is serializable, so you can save it into the database if you need to keep it around for extended period of time."
msgstr ""
#. Tag: programlisting
@@ -442,14 +475,24 @@
" payment.getQuartzTriggerHandle().cancel();\n"
"]]>"
msgstr ""
+"<![CDATA[QuartzTriggerHandle handle =\n"
+" processor.schedulePayment(payment.getPaymentDate(), \n"
+" payment.getPaymentCron(), \n"
+" payment);\n"
+" payment.setQuartzTriggerHandle( handle );\n"
+" // Save payment to DB\n"
+" \n"
+" // later ...\n"
+" \n"
+" // Retrieve payment from DB\n"
+" // Cancel the remaining scheduled tasks\n"
+" payment.getQuartzTriggerHandle().cancel();\n"
+"]]>"
#. Tag: para
#: Jms.xml:156
#, no-c-format
-msgid ""
-"The <literal>@IntervalCron</literal> annotation supports Unix cron job "
-"syntax for task scheduling. For instance, the following asynchronous method "
-"runs at 2:10pm and at 2:44pm every Wednesday in the month of March."
+msgid "The <literal>@IntervalCron</literal> annotation supports Unix cron job syntax for task scheduling. For instance, the following asynchronous method runs at 2:10pm and at 2:44pm every Wednesday in the month of March."
msgstr ""
#. Tag: programlisting
@@ -470,20 +513,30 @@
" \n"
" // Schedule the task in the business logic processing code\n"
" QuartzTriggerHandle handle = \n"
-" processor.schedulePayment(new Date(), \"0 10,44 14 ? 3 WED\", "
-"payment);\n"
+" processor.schedulePayment(new Date(), \"0 10,44 14 ? 3 WED\", payment);\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+" // Define the method\n"
+" @Asynchronous\n"
+" public QuartzTriggerHandle schedulePayment(@Expiration Date when, \n"
+" @IntervalCron String cron, \n"
+" Payment payment) \n"
+" { \n"
+" // do the repeating or long running task\n"
+" }\n"
+" \n"
+" ... ...\n"
+" \n"
+" // Schedule the task in the business logic processing code\n"
+" QuartzTriggerHandle handle = \n"
+" processor.schedulePayment(new Date(), \"0 10,44 14 ? 3 WED\", payment);\n"
+"]]>"
#. Tag: para
#: Jms.xml:161
#, no-c-format
-msgid ""
-"The <literal>@IntervalBusinessDay</literal> annotation supports invocation "
-"on the \"nth Business Day\" scenario. For instance, the following "
-"asynchronous method runs at 14:00 on the 2nd business day of each month. By "
-"default, it excludes all weekends and US federal holidays until 2010 from "
-"the business days."
+msgid "The <literal>@IntervalBusinessDay</literal> annotation supports invocation on the \"nth Business Day\" scenario. For instance, the following asynchronous method runs at 14:00 on the 2nd business day of each month. By default, it excludes all weekends and US federal holidays until 2010 from the business days."
msgstr ""
#. Tag: programlisting
@@ -508,15 +561,28 @@
" new NthBusinessDay(2, \"14:00\", WEEKLY), payment);\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+" // Define the method\n"
+" @Asynchronous\n"
+" public QuartzTriggerHandle schedulePayment(@Expiration Date when, \n"
+" @IntervalBusinessDay NthBusinessDay nth, \n"
+" Payment payment) \n"
+" { \n"
+" // do the repeating or long running task\n"
+" }\n"
+" \n"
+" ... ...\n"
+" \n"
+" // Schedule the task in the business logic processing code\n"
+" QuartzTriggerHandle handle = \n"
+" processor.schedulePayment(new Date(), \n"
+" new NthBusinessDay(2, \"14:00\", WEEKLY), payment);\n"
+"]]>"
#. Tag: para
#: Jms.xml:166
#, no-c-format
-msgid ""
-"The <literal>NthBusinessDay</literal> object contains the configuration of "
-"the invocation trigger. You can specify more holidays (e.g., company "
-"holidays, non-US holidays etc.) via the <literal>additionalHolidays</"
-"literal> property."
+msgid "The <literal>NthBusinessDay</literal> object contains the configuration of the invocation trigger. You can specify more holidays (e.g., company holidays, non-US holidays etc.) via the <literal>additionalHolidays</literal> property."
msgstr ""
#. Tag: programlisting
@@ -548,35 +614,47 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[\n"
+"public class NthBusinessDay implements Serializable\n"
+"{\n"
+" int n;\n"
+" String fireAtTime;\n"
+" List <Date> additionalHolidays;\n"
+" BusinessDayIntervalType interval;\n"
+" boolean excludeWeekends;\n"
+" boolean excludeUsFederalHolidays;\n"
+"\n"
+" public enum BusinessDayIntervalType { WEEKLY, MONTHLY, YEARLY }\n"
+"\n"
+" public NthBusinessDay ()\n"
+" {\n"
+" n = 1;\n"
+" fireAtTime = \"12:00\";\n"
+" additionalHolidays = new ArrayList <Date> ();\n"
+" interval = BusinessDayIntervalType.WEEKLY;\n"
+" excludeWeekends = true;\n"
+" excludeUsFederalHolidays = true;\n"
+" } \n"
+" ... ...\n"
+"}\n"
+"]]>"
#. Tag: para
#: Jms.xml:170
#, no-c-format
-msgid ""
-"The <literal>@IntervalDuration</literal>, <literal>@IntervalCron</literal>, "
-"and <literal>@IntervalNthBusinessDay</literal> annotations are mutually "
-"exclusive. If they are used in the same method, a <literal>RuntimeException</"
-"literal> will be thrown."
+msgid "The <literal>@IntervalDuration</literal>, <literal>@IntervalCron</literal>, and <literal>@IntervalNthBusinessDay</literal> annotations are mutually exclusive. If they are used in the same method, a <literal>RuntimeException</literal> will be thrown."
msgstr ""
#. Tag: title
#: Jms.xml:175
#, no-c-format
msgid "Asynchronous events"
-msgstr ""
+msgstr "Eventi asincroni"
#. Tag: para
#: Jms.xml:176
#, no-c-format
-msgid ""
-"Component-driven events may also be asynchronous. To raise an event for "
-"asynchronous processing, simply call the <literal>raiseAsynchronousEvent()</"
-"literal> method of the <literal>Events</literal> class. To schedule a timed "
-"event, call the <literal>raiseTimedEvent()</literal> method, passing a "
-"<emphasis>schedule</emphasis> object (for the default dispatcher or timer "
-"service dispatcher, use <literal>TimerSchedule</literal>). Components may "
-"observe asynchronous events in the usual way, but remember that only the "
-"business process context is propagated to the asynchronous thread."
+msgid "Component-driven events may also be asynchronous. To raise an event for asynchronous processing, simply call the <literal>raiseAsynchronousEvent()</literal> method of the <literal>Events</literal> class. To schedule a timed event, call the <literal>raiseTimedEvent()</literal> method, passing a <emphasis>schedule</emphasis> object (for the default dispatcher or timer service dispatcher, use <literal>TimerSchedule</literal>). Components may observe asynchronous events in the usual way, but remember that only the business process context is propagated to the asynchronous thread."
msgstr ""
#. Tag: title
@@ -588,23 +666,13 @@
#. Tag: para
#: Jms.xml:190
#, no-c-format
-msgid ""
-"Each asynchronous dispatcher behaves differently when an exception "
-"propagates through it. For example, the <literal>java.util.concurrent</"
-"literal> dispatcher will suspend further executions of a call which repeats, "
-"and the EJB3 timer service will swallow the exception. Seam therefore "
-"catches any exception which propagates out of the asynchronous call before "
-"it reaches the dispatcher."
+msgid "Each asynchronous dispatcher behaves differently when an exception propagates through it. For example, the <literal>java.util.concurrent</literal> dispatcher will suspend further executions of a call which repeats, and the EJB3 timer service will swallow the exception. Seam therefore catches any exception which propagates out of the asynchronous call before it reaches the dispatcher."
msgstr ""
#. Tag: para
#: Jms.xml:200
#, no-c-format
-msgid ""
-"By default, any exception which propagates out from an asynchronous "
-"execution will be caught and logged at error level. You can customize this "
-"behavior globally by overriding the <literal>org.jboss.seam.async."
-"asynchronousExceptionHandler</literal> component:"
+msgid "By default, any exception which propagates out from an asynchronous execution will be caught and logged at error level. You can customize this behavior globally by overriding the <literal>org.jboss.seam.async.asynchronousExceptionHandler</literal> component:"
msgstr ""
#. Tag: programlisting
@@ -613,8 +681,7 @@
msgid ""
"<![CDATA[@Scope(ScopeType.STATELESS)\n"
"@Name(\"org.jboss.seam.async.asynchronousExceptionHandler\")\n"
-"public class MyAsynchronousExceptionHandler extends "
-"AsynchronousExceptionHandler { \n"
+"public class MyAsynchronousExceptionHandler extends AsynchronousExceptionHandler { \n"
"\n"
" @Logger Log log;\n"
" \n"
@@ -628,23 +695,32 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@Scope(ScopeType.STATELESS)\n"
+"@Name(\"org.jboss.seam.async.asynchronousExceptionHandler\")\n"
+"public class MyAsynchronousExceptionHandler extends AsynchronousExceptionHandler { \n"
+"\n"
+" @Logger Log log;\n"
+" \n"
+" @In Future timer;\n"
+" \n"
+" @Override\n"
+" public void handleException(Exception exception) {\n"
+" log.debug(exception);\n"
+" timer.cancel(false);\n"
+" }\n"
+" \n"
+"}]]>"
#. Tag: para
#: Jms.xml:210
#, no-c-format
-msgid ""
-"Here, for example, using <literal>java.util.concurrent</literal> dispatcher, "
-"we inject it's control object and cancel all future invocations when an "
-"exception is encountered"
+msgid "Here, for example, using <literal>java.util.concurrent</literal> dispatcher, we inject it's control object and cancel all future invocations when an exception is encountered"
msgstr ""
#. Tag: para
#: Jms.xml:216
#, no-c-format
-msgid ""
-"You can also alter this behavior for an individual component by implementing "
-"the method <literal>public void handleAsynchronousException(Exception "
-"exception);</literal> on the component. For example:"
+msgid "You can also alter this behavior for an individual component by implementing the method <literal>public void handleAsynchronousException(Exception exception);</literal> on the component. For example:"
msgstr ""
#. Tag: programlisting
@@ -655,56 +731,44 @@
" log.fatal(exception);\n"
" }]]>"
msgstr ""
+"<![CDATA[ public void handleAsynchronousException(Exception exception) {\n"
+" log.fatal(exception);\n"
+" }]]>"
#. Tag: title
#: Jms.xml:230
#, no-c-format
msgid "Messaging in Seam"
-msgstr ""
+msgstr "Messaggistica in Seam"
#. Tag: para
#: Jms.xml:232
#, no-c-format
-msgid ""
-"Seam makes it easy to send and receive JMS messages to and from Seam "
-"components."
+msgid "Seam makes it easy to send and receive JMS messages to and from Seam components."
msgstr ""
#. Tag: title
#: Jms.xml:238
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "Configurazione"
#. Tag: para
#: Jms.xml:239
#, no-c-format
-msgid ""
-"To configure Seam's infrastructure for sending JMS messages, you need to "
-"tell Seam about any topics and queues you want to send messages to, and also "
-"tell Seam where to find the <literal>QueueConnectionFactory</literal> and/or "
-"<literal>TopicConnectionFactory</literal>."
+msgid "To configure Seam's infrastructure for sending JMS messages, you need to tell Seam about any topics and queues you want to send messages to, and also tell Seam where to find the <literal>QueueConnectionFactory</literal> and/or <literal>TopicConnectionFactory</literal>."
msgstr ""
#. Tag: para
#: Jms.xml:247
#, no-c-format
-msgid ""
-"Seam defaults to using <literal>UIL2ConnectionFactory</literal> which is the "
-"usual connection factory for use with JBossMQ. If you are using some other "
-"JMS provider, you need to set one or both of <literal>queueConnection."
-"queueConnectionFactoryJndiName</literal> and <literal>topicConnection."
-"topicConnectionFactoryJndiName</literal> in <literal>seam.properties</"
-"literal>, <literal>web.xml</literal> or <literal>components.xml</literal>."
+msgid "Seam defaults to using <literal>UIL2ConnectionFactory</literal> which is the usual connection factory for use with JBossMQ. If you are using some other JMS provider, you need to set one or both of <literal>queueConnection.queueConnectionFactoryJndiName</literal> and <literal>topicConnection.topicConnectionFactoryJndiName</literal> in <literal>seam.properties</literal>, <literal>web.xml</literal> or <literal>components.xml</literal>."
msgstr ""
#. Tag: para
#: Jms.xml:257
#, no-c-format
-msgid ""
-"You also need to list topics and queues in <literal>components.xml</literal> "
-"to install Seam managed <literal>TopicPublisher</literal>s and "
-"<literal>QueueSender</literal>s:"
+msgid "You also need to list topics and queues in <literal>components.xml</literal> to install Seam managed <literal>TopicPublisher</literal>s and <literal>QueueSender</literal>s:"
msgstr ""
#. Tag: programlisting
@@ -719,19 +783,24 @@
" auto-create=\"true\" \n"
" queue-jndi-name=\"queue/paymentQueue\"/>]]>"
msgstr ""
+"<![CDATA[<jms:managed-topic-publisher name=\"stockTickerPublisher\" \n"
+" auto-create=\"true\" \n"
+" topic-jndi-name=\"topic/stockTickerTopic\"/>\n"
+"\n"
+"<jms:managed-queue-sender name=\"paymentQueueSender\" \n"
+" auto-create=\"true\" \n"
+" queue-jndi-name=\"queue/paymentQueue\"/>]]>"
#. Tag: title
#: Jms.xml:268
#, no-c-format
msgid "Sending messages"
-msgstr ""
+msgstr "Spedire messaggi"
#. Tag: para
#: Jms.xml:269
#, no-c-format
-msgid ""
-"Now, you can inject a JMS <literal>TopicPublisher</literal> and "
-"<literal>TopicSession</literal> into any component:"
+msgid "Now, you can inject a JMS <literal>TopicPublisher</literal> and <literal>TopicSession</literal> into any component:"
msgstr ""
#. Tag: programlisting
@@ -746,8 +815,7 @@
"public void publish(StockPrice price) {\n"
" try\n"
" {\n"
-" stockTickerPublisher.publish( topicSession.createObjectMessage"
-"(price) );\n"
+" stockTickerPublisher.publish( topicSession.createObjectMessage(price) );\n"
" } \n"
" catch (Exception ex)\n"
" {\n"
@@ -755,6 +823,21 @@
" } \n"
"}]]>"
msgstr ""
+"<![CDATA[@In \n"
+"private TopicPublisher stockTickerPublisher; \n"
+"@In \n"
+"private TopicSession topicSession;\n"
+"\n"
+"public void publish(StockPrice price) {\n"
+" try\n"
+" {\n"
+" stockTickerPublisher.publish( topicSession.createObjectMessage(price) );\n"
+" } \n"
+" catch (Exception ex)\n"
+" {\n"
+" throw new RuntimeException(ex);\n"
+" } \n"
+"}]]>"
#. Tag: para
#: Jms.xml:276
@@ -774,8 +857,7 @@
"public void publish(Payment payment) {\n"
" try\n"
" {\n"
-" paymentQueueSender.send( queueSession.createObjectMessage"
-"(payment) );\n"
+" paymentQueueSender.send( queueSession.createObjectMessage(payment) );\n"
" } \n"
" catch (Exception ex)\n"
" {\n"
@@ -783,6 +865,21 @@
" } \n"
"}]]>"
msgstr ""
+"<![CDATA[@In\n"
+"private QueueSender paymentQueueSender; \n"
+"@In\n"
+"private QueueSession queueSession;\n"
+"\n"
+"public void publish(Payment payment) {\n"
+" try\n"
+" {\n"
+" paymentQueueSender.send( queueSession.createObjectMessage(payment) );\n"
+" } \n"
+" catch (Exception ex)\n"
+" {\n"
+" throw new RuntimeException(ex);\n"
+" } \n"
+"}]]>"
#. Tag: title
#: Jms.xml:283
@@ -793,10 +890,7 @@
#. Tag: para
#: Jms.xml:284
#, no-c-format
-msgid ""
-"You can process messages using any EJB3 message driven bean. Message-driven "
-"beans may even be Seam components, in which case it is possible to inject "
-"other event and application scoped Seam components."
+msgid "You can process messages using any EJB3 message driven bean. Message-driven beans may even be Seam components, in which case it is possible to inject other event and application scoped Seam components."
msgstr ""
#. Tag: title
@@ -808,7 +902,6 @@
#. Tag: para
#: Jms.xml:293
#, no-c-format
-msgid ""
-"Seam Remoting lets you subscribe to a JMS topic from client-side JavaScript. "
-"This is described in <xref linkend=\"remoting\"/>."
+msgid "Seam Remoting lets you subscribe to a JMS topic from client-side JavaScript. This is described in <xref linkend=\"remoting\"/>."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Mail.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Mail.po 2008-12-15 15:50:47 UTC (rev 9783)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Mail.po 2008-12-15 17:36:40 UTC (rev 9784)
@@ -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:38+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-15 18:23+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,39 +17,30 @@
#: Mail.xml:2
#, no-c-format
msgid "Email"
-msgstr ""
+msgstr "Email"
#. Tag: para
#: Mail.xml:3
#, no-c-format
-msgid ""
-"Seam now includes an optional components for templating and sending emails."
+msgid "Seam now includes an optional components for templating and sending emails."
msgstr ""
#. Tag: para
#: Mail.xml:7
#, no-c-format
-msgid ""
-"Email support is provided by <literal>jboss-seam-mail.jar</literal>. This "
-"JAR contains the mail JSF controls, which are used to construct emails, and "
-"the <literal>mailSession</literal> manager component."
+msgid "Email support is provided by <literal>jboss-seam-mail.jar</literal>. This JAR contains the mail JSF controls, which are used to construct emails, and the <literal>mailSession</literal> manager component."
msgstr ""
#. Tag: para
#: Mail.xml:13
#, no-c-format
-msgid ""
-"The examples/mail project contains an example of the email support in "
-"action. It demonstrates proper packaging, and it contains a number of "
-"example that demonstrate the key features currently supported."
+msgid "The examples/mail project contains an example of the email support in action. It demonstrates proper packaging, and it contains a number of example that demonstrate the key features currently supported."
msgstr ""
#. Tag: para
#: Mail.xml:19
#, no-c-format
-msgid ""
-"You can also test your mail's using Seam's integration testing environment. "
-"See <xref linkend=\"testing.mail\"/>."
+msgid "You can also test your mail's using Seam's integration testing environment. See <xref linkend=\"testing.mail\"/>."
msgstr ""
#. Tag: title
@@ -61,9 +52,7 @@
#. Tag: para
#: Mail.xml:27
#, no-c-format
-msgid ""
-"You don't need to learn a whole new templating language to use Seam Mail "
-"— an email is just facelet!"
+msgid "You don't need to learn a whole new templating language to use Seam Mail — an email is just facelet!"
msgstr ""
#. Tag: programlisting
@@ -75,50 +64,53 @@
" xmlns:h=\"http://java.sun.com/jsf/html\">\n"
" \n"
" <m:from name=\"Peter\" address=\"peter at example.com\" />\n"
-" <m:to name=\"#{person.firstname} #{person.lastname}\">#{person.address}</"
-"m:to>\n"
+" <m:to name=\"#{person.firstname} #{person.lastname}\">#{person.address}</m:to>\n"
" <m:subject>Try out Seam!</m:subject>\n"
" \n"
" <m:body>\n"
" <p><h:outputText value=\"Dear #{person.firstname}\" />,</p>\n"
" <p>You can try out Seam by visiting \n"
-" <a href=\"http://labs.jboss.com/jbossseam\">http://labs.jboss.com/"
-"jbossseam</a>.</p>\n"
+" <a href=\"http://labs.jboss.com/jbossseam\">http://labs.jboss.com/jbossseam</a>.</p>\n"
" <p>Regards,</p>\n"
" <p>Pete</p>\n"
" </m:body>\n"
" \n"
"</m:message>]]>"
msgstr ""
+"<![CDATA[<m:message xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:m=\"http://jboss.com/products/seam/mail\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\">\n"
+" \n"
+" <m:from name=\"Peter\" address=\"peter at example.com\" />\n"
+" <m:to name=\"#{person.firstname} #{person.lastname}\">#{person.address}</m:to>\n"
+" <m:subject>Try out Seam!</m:subject>\n"
+" \n"
+" <m:body>\n"
+" <p><h:outputText value=\"Dear #{person.firstname}\" />,</p>\n"
+" <p>You can try out Seam by visiting \n"
+" <a href=\"http://labs.jboss.com/jbossseam\">http://labs.jboss.com/jbossseam</a>.</p>\n"
+" <p>Regards,</p>\n"
+" <p>Pete</p>\n"
+" </m:body>\n"
+" \n"
+"</m:message>]]>"
#. Tag: para
#: Mail.xml:34
#, no-c-format
-msgid ""
-"The <literal><m:message></literal> tag wraps the whole message, and "
-"tells Seam to start rendering an email. Inside the <literal><m:message>"
-"</literal> tag we use an <literal><m:from></literal> tag to set who "
-"the message is from, a <literal><m:to></literal> tag to specify a "
-"sender (notice how we use EL as we would in a normal facelet), and a "
-"<literal><m:subject></literal> tag."
+msgid "The <literal><m:message></literal> tag wraps the whole message, and tells Seam to start rendering an email. Inside the <literal><m:message></literal> tag we use an <literal><m:from></literal> tag to set who the message is from, a <literal><m:to></literal> tag to specify a sender (notice how we use EL as we would in a normal facelet), and a <literal><m:subject></literal> tag."
msgstr ""
#. Tag: para
#: Mail.xml:43
#, no-c-format
-msgid ""
-"The <literal><m:body></literal> tag wraps the body of the email. You "
-"can use regular HTML tags inside the body as well as JSF components."
+msgid "The <literal><m:body></literal> tag wraps the body of the email. You can use regular HTML tags inside the body as well as JSF components."
msgstr ""
#. Tag: para
#: Mail.xml:48
#, no-c-format
-msgid ""
-"So, now you have your email template, how do you go about sending it? Well, "
-"at the end of rendering the <literal>m:message</literal> the "
-"<literal>mailSession</literal> is called to send the email, so all you have "
-"to do is ask Seam to render the view:"
+msgid "So, now you have your email template, how do you go about sending it? Well, at the end of rendering the <literal>m:message</literal> the <literal>mailSession</literal> is called to send the email, so all you have to do is ask Seam to render the view:"
msgstr ""
#. Tag: programlisting
@@ -138,27 +130,35 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@In(create=true)\n"
+"private Renderer renderer;\n"
+" \n"
+"public void send() {\n"
+" try {\n"
+" renderer.render(\"/simple.xhtml\");\n"
+" facesMessages.add(\"Email sent successfully\");\n"
+" } \n"
+" catch (Exception e) {\n"
+" facesMessages.add(\"Email sending failed: \" + e.getMessage());\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Mail.xml:57
#, no-c-format
-msgid ""
-"If, for example, you entered an invalid email address, then an exception "
-"would be thrown, which is caught and then displayed to the user."
+msgid "If, for example, you entered an invalid email address, then an exception would be thrown, which is caught and then displayed to the user."
msgstr ""
#. Tag: title
#: Mail.xml:63
#, no-c-format
msgid "Attachments"
-msgstr ""
+msgstr "Allegati"
#. Tag: para
#: Mail.xml:64
#, no-c-format
-msgid ""
-"Seam makes it easy to attach files to an email. It supports most of the "
-"standard java types used when working with files."
+msgid "Seam makes it easy to attach files to an email. It supports most of the standard java types used when working with files."
msgstr ""
#. Tag: para
@@ -171,71 +171,54 @@
#: Mail.xml:73
#, no-c-format
msgid "<![CDATA[<m:attachment value=\"/WEB-INF/lib/jboss-seam-mail.jar\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<m:attachment value=\"/WEB-INF/lib/jboss-seam-mail.jar\"/>]]>"
#. Tag: para
#: Mail.xml:75
#, no-c-format
-msgid ""
-"Seam will load the file from the classpath, and attach it to the email. By "
-"default it would be attached as <literal>jboss-seam-mail.jar</literal>; if "
-"you wanted it to have another name you would just add the <literal>fileName</"
-"literal> attribute:"
+msgid "Seam will load the file from the classpath, and attach it to the email. By default it would be attached as <literal>jboss-seam-mail.jar</literal>; if you wanted it to have another name you would just add the <literal>fileName</literal> attribute:"
msgstr ""
#. Tag: programlisting
#: Mail.xml:81
#, no-c-format
-msgid ""
-"<![CDATA[<m:attachment value=\"/WEB-INF/lib/jboss-seam-mail.jar\" fileName="
-"\"this-is-so-cool.jar\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<m:attachment value=\"/WEB-INF/lib/jboss-seam-mail.jar\" fileName=\"this-is-so-cool.jar\"/>]]>"
+msgstr "<![CDATA[<m:attachment value=\"/WEB-INF/lib/jboss-seam-mail.jar\" fileName=\"this-is-so-cool.jar\"/>]]>"
#. Tag: para
#: Mail.xml:83
#, no-c-format
-msgid ""
-"You could also attach a <literal>java.io.File</literal>, a <literal>java.net."
-"URL</literal>:"
+msgid "You could also attach a <literal>java.io.File</literal>, a <literal>java.net.URL</literal>:"
msgstr ""
#. Tag: programlisting
#: Mail.xml:87
#, no-c-format
msgid "<![CDATA[<m:attachment value=\"#{numbers}\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<m:attachment value=\"#{numbers}\"/>]]>"
#. Tag: para
#: Mail.xml:89
#, no-c-format
-msgid ""
-"Or a <literal>byte[]</literal> or a <literal>java.io.InputStream</literal>:"
+msgid "Or a <literal>byte[]</literal> or a <literal>java.io.InputStream</literal>:"
msgstr ""
#. Tag: programlisting
#: Mail.xml:93
#, no-c-format
-msgid ""
-"<![CDATA[<m:attachment value=\"#{person.photo}\" contentType=\"image/png\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<m:attachment value=\"#{person.photo}\" contentType=\"image/png\"/>]]>"
+msgstr "<![CDATA[<m:attachment value=\"#{person.photo}\" contentType=\"image/png\"/>]]>"
#. Tag: para
#: Mail.xml:95
#, no-c-format
-msgid ""
-"You'll notice that for a <literal>byte[]</literal> and a <literal>java.io."
-"InputStream</literal> you need to specify the MIME type of the attachment "
-"(as that information is not carried as part of the file)."
+msgid "You'll notice that for a <literal>byte[]</literal> and a <literal>java.io.InputStream</literal> you need to specify the MIME type of the attachment (as that information is not carried as part of the file)."
msgstr ""
#. Tag: para
#: Mail.xml:101
#, no-c-format
-msgid ""
-"And it gets even better, you can attach a Seam generated PDF, or any "
-"standard JSF view, just by wrapping a <literal><m:attachment></"
-"literal> around the normal tags you would use:"
+msgid "And it gets even better, you can attach a Seam generated PDF, or any standard JSF view, just by wrapping a <literal><m:attachment></literal> around the normal tags you would use:"
msgstr ""
#. Tag: programlisting
@@ -244,19 +227,20 @@
msgid ""
"<![CDATA[<m:attachment fileName=\"tiny.pdf\">\n"
" <p:document> \n"
-" A very tiny "
-"PDF \n"
+" A very tiny PDF \n"
" </p:document>\n"
"</m:attachment>]]>"
msgstr ""
+"<![CDATA[<m:attachment fileName=\"tiny.pdf\">\n"
+" <p:document> \n"
+" A very tiny PDF \n"
+" </p:document>\n"
+"</m:attachment>]]>"
#. Tag: para
#: Mail.xml:109
#, no-c-format
-msgid ""
-"If you had a set of files you wanted to attach (for example a set of "
-"pictures loaded from a database) you can just use a <literal><ui:"
-"repeat></literal>:"
+msgid "If you had a set of files you wanted to attach (for example a set of pictures loaded from a database) you can just use a <literal><ui:repeat></literal>:"
msgstr ""
#. Tag: programlisting
@@ -264,10 +248,12 @@
#, no-c-format
msgid ""
"<![CDATA[<ui:repeat value=\"#{people}\" var=\"person\">\n"
-" <m:attachment value=\"#{person.photo}\" contentType=\"image/jpeg\" "
-"fileName=\"#{person.firstname}_#{person.lastname}.jpg\"/>\n"
+" <m:attachment value=\"#{person.photo}\" contentType=\"image/jpeg\" fileName=\"#{person.firstname}_#{person.lastname}.jpg\"/>\n"
"</ui:repeat>]]>"
msgstr ""
+"<![CDATA[<ui:repeat value=\"#{people}\" var=\"person\">\n"
+" <m:attachment value=\"#{person.photo}\" contentType=\"image/jpeg\" fileName=\"#{person.firstname}_#{person.lastname}.jpg\"/>\n"
+"</ui:repeat>]]>"
#. Tag: para
#: Mail.xml:116
@@ -287,22 +273,24 @@
" disposition=\"inline\" />\n"
"<img src=\"cid:#{personPhoto.contentId}\" />]]>"
msgstr ""
+"<![CDATA[<m:attachment \n"
+" value=\"#{person.photo}\" \n"
+" contentType=\"image/jpeg\" \n"
+" fileName=\"#{person.firstname}_#{person.lastname}.jpg\" \n"
+" status=\"personPhoto\" \n"
+" disposition=\"inline\" />\n"
+"<img src=\"cid:#{personPhoto.contentId}\" />]]>"
#. Tag: para
#: Mail.xml:122
#, no-c-format
-msgid ""
-"You may be wondering what <literal>cid:#{...}</literal> does. Well, the IETF "
-"specified that by putting this as the src for your image, the attachments "
-"will be looked at when trying to locate the image (the <literal>Content-ID</"
-"literal>'s must match) — magic!"
+msgid "You may be wondering what <literal>cid:#{...}</literal> does. Well, the IETF specified that by putting this as the src for your image, the attachments will be looked at when trying to locate the image (the <literal>Content-ID</literal>'s must match) — magic!"
msgstr ""
#. Tag: para
#: Mail.xml:129
#, no-c-format
-msgid ""
-"You must declare the attachment before trying to access the status object."
+msgid "You must declare the attachment before trying to access the status object."
msgstr ""
#. Tag: title
@@ -314,9 +302,7 @@
#. Tag: para
#: Mail.xml:138
#, no-c-format
-msgid ""
-"Whilst most mail readers nowadays support HTML, some don't, so you can add a "
-"plain text alternative to your email body:"
+msgid "Whilst most mail readers nowadays support HTML, some don't, so you can add a plain text alternative to your email body:"
msgstr ""
#. Tag: programlisting
@@ -324,25 +310,25 @@
#, no-c-format
msgid ""
"<![CDATA[<m:body>\n"
-" <f:facet name=\"alternative\">Sorry, your email reader can't show our "
-"fancy email, \n"
+" <f:facet name=\"alternative\">Sorry, your email reader can't show our fancy email, \n"
"please go to http://labs.jboss.com/jbossseam to explore Seam.</f:facet>\n"
"</m:body>]]>"
msgstr ""
+"<![CDATA[<m:body>\n"
+" <f:facet name=\"alternative\">Sorry, your email reader can't show our fancy email, \n"
+"please go to http://labs.jboss.com/jbossseam to explore Seam.</f:facet>\n"
+"</m:body>]]>"
#. Tag: title
#: Mail.xml:148
#, no-c-format
msgid "Multiple recipients"
-msgstr ""
+msgstr "Destinatari multipli"
#. Tag: para
#: Mail.xml:150
#, no-c-format
-msgid ""
-"Often you'll want to send an email to a group of recipients (for example "
-"your users). All of the recipient mail tags can be placed inside a "
-"<literal><ui:repeat></literal>:"
+msgid "Often you'll want to send an email to a group of recipients (for example your users). All of the recipient mail tags can be placed inside a <literal><ui:repeat></literal>:"
msgstr ""
#. Tag: programlisting
@@ -350,24 +336,23 @@
#, no-c-format
msgid ""
"<![CDATA[<ui:repeat value=\"#{allUsers} var=\"user\">\n"
-" <m:to name=\"#{user.firstname} #{user.lastname}\" address=\"#{user."
-"emailAddress}\" />\n"
+" <m:to name=\"#{user.firstname} #{user.lastname}\" address=\"#{user.emailAddress}\" />\n"
"</ui:repeat>]]>"
msgstr ""
+"<![CDATA[<ui:repeat value=\"#{allUsers} var=\"user\">\n"
+" <m:to name=\"#{user.firstname} #{user.lastname}\" address=\"#{user.emailAddress}\" />\n"
+"</ui:repeat>]]>"
#. Tag: title
#: Mail.xml:161
#, no-c-format
msgid "Multiple messages"
-msgstr ""
+msgstr "Messaggi multipli"
#. Tag: para
#: Mail.xml:163
#, no-c-format
-msgid ""
-"Sometimes, however, you need to send a slightly different message to each "
-"recipient (e.g. a password reset). The best way to do this is to place the "
-"whole message inside a <literal><ui:repeat></literal>:"
+msgid "Sometimes, however, you need to send a slightly different message to each recipient (e.g. a password reset). The best way to do this is to place the whole message inside a <literal><ui:repeat></literal>:"
msgstr ""
#. Tag: programlisting
@@ -376,13 +361,19 @@
msgid ""
"<![CDATA[<ui:repeat value=\"#{people}\" var=\"p\">\n"
" <m:message>\n"
-" <m:from name=\"#{person.firstname} #{person.lastname}\">#{person."
-"address}</m:from>\n"
+" <m:from name=\"#{person.firstname} #{person.lastname}\">#{person.address}</m:from>\n"
" <m:to name=\"#{p.firstname}\">#{p.address}</m:to>\n"
" ...\n"
" </m:message>\n"
"</ui:repeat>]]>"
msgstr ""
+"<![CDATA[<ui:repeat value=\"#{people}\" var=\"p\">\n"
+" <m:message>\n"
+" <m:from name=\"#{person.firstname} #{person.lastname}\">#{person.address}</m:from>\n"
+" <m:to name=\"#{p.firstname}\">#{p.address}</m:to>\n"
+" ...\n"
+" </m:message>\n"
+"</ui:repeat>]]>"
#. Tag: title
#: Mail.xml:174
@@ -393,9 +384,7 @@
#. Tag: para
#: Mail.xml:176
#, no-c-format
-msgid ""
-"The mail templating example shows that facelets templating Just Works with "
-"the Seam mail tags."
+msgid "The mail templating example shows that facelets templating Just Works with the Seam mail tags."
msgstr ""
#. Tag: para
@@ -410,19 +399,29 @@
msgid ""
"<![CDATA[<m:message>\n"
" <m:from name=\"Seam\" address=\"do-not-reply at jboss.com\" />\n"
-" <m:to name=\"#{person.firstname} #{person.lastname}\">#{person.address}</"
-"m:to>\n"
+" <m:to name=\"#{person.firstname} #{person.lastname}\">#{person.address}</m:to>\n"
" <m:subject>#{subject}</m:subject>\n"
" <m:body>\n"
" <html>\n"
" <body>\n"
-" <ui:insert name=\"body\">This is the default body, specified "
-"by the template.</ui:insert>\n"
+" <ui:insert name=\"body\">This is the default body, specified by the template.</ui:insert>\n"
" </body>\n"
" </html>\n"
" </m:body>\n"
"</m:message>]]>"
msgstr ""
+"<![CDATA[<m:message>\n"
+" <m:from name=\"Seam\" address=\"do-not-reply at jboss.com\" />\n"
+" <m:to name=\"#{person.firstname} #{person.lastname}\">#{person.address}</m:to>\n"
+" <m:subject>#{subject}</m:subject>\n"
+" <m:body>\n"
+" <html>\n"
+" <body>\n"
+" <ui:insert name=\"body\">This is the default body, specified by the template.</ui:insert>\n"
+" </body>\n"
+" </html>\n"
+" </m:body>\n"
+"</m:message>]]>"
#. Tag: para
#: Mail.xml:187
@@ -436,44 +435,36 @@
msgid ""
"<![CDATA[<ui:param name=\"subject\" value=\"Templating with Seam Mail\"/>\n"
"<ui:define name=\"body\">\n"
-" <p>This example demonstrates that you can easily use <i>facelets "
-"templating</i> in email!</p>\n"
+" <p>This example demonstrates that you can easily use <i>facelets templating</i> in email!</p>\n"
"</ui:define>]]>"
msgstr ""
+"<![CDATA[<ui:param name=\"subject\" value=\"Templating with Seam Mail\"/>\n"
+"<ui:define name=\"body\">\n"
+" <p>This example demonstrates that you can easily use <i>facelets templating</i> in email!</p>\n"
+"</ui:define>]]>"
#. Tag: para
#: Mail.xml:193
#, no-c-format
-msgid ""
-"You can also use facelets source tags in your email, but you must place them "
-"in a jar in <literal>WEB-INF/lib</literal> - referencing the <literal>."
-"taglib.xml</literal> from <literal>web.xml</literal> isn't reliable when "
-"using Seam Mail (if you send your mail asynchrounously Seam Mail doesn't "
-"have access to the full JSF or Servlet context, and so doesn't know about "
-"<literal>web.xml</literal> configuration parameters)."
+msgid "You can also use facelets source tags in your email, but you must place them in a jar in <literal>WEB-INF/lib</literal> - referencing the <literal>.taglib.xml</literal> from <literal>web.xml</literal> isn't reliable when using Seam Mail (if you send your mail asynchrounously Seam Mail doesn't have access to the full JSF or Servlet context, and so doesn't know about <literal>web.xml</literal> configuration parameters)."
msgstr ""
#. Tag: para
#: Mail.xml:203
#, no-c-format
-msgid ""
-"If you do need more configure Facelets or JSF when sending mail, you'll need "
-"to override the Renderer component and do the configuration programmatically "
-"- only for advanced users!"
+msgid "If you do need more configure Facelets or JSF when sending mail, you'll need to override the Renderer component and do the configuration programmatically - only for advanced users!"
msgstr ""
#. Tag: title
#: Mail.xml:213
#, no-c-format
msgid "Internationalisation"
-msgstr ""
+msgstr "Internazionalizzazione"
#. Tag: para
#: Mail.xml:215
#, no-c-format
-msgid ""
-"Seam supports sending internationalised messages. By default, the encoding "
-"provided by JSF is used, but this can be overridden on the template:"
+msgid "Seam supports sending internationalised messages. By default, the encoding provided by JSF is used, but this can be overridden on the template:"
msgstr ""
#. Tag: programlisting
@@ -484,35 +475,32 @@
" ...\n"
"</m:message>]]>"
msgstr ""
+"<![CDATA[<m:message charset=\"UTF-8\">\n"
+" ...\n"
+"</m:message>]]>"
#. Tag: para
#: Mail.xml:223
#, no-c-format
-msgid ""
-"The body, subject and recipient (and from) name will be encoded. You'll need "
-"to make sure facelets uses the correct charset for parsing your pages by "
-"setting encoding of the template:"
+msgid "The body, subject and recipient (and from) name will be encoded. You'll need to make sure facelets uses the correct charset for parsing your pages by setting encoding of the template:"
msgstr ""
#. Tag: programlisting
#: Mail.xml:229
#, no-c-format
msgid "<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>]]>"
-msgstr ""
+msgstr "<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>]]>"
#. Tag: title
#: Mail.xml:233
#, no-c-format
msgid "Other Headers"
-msgstr ""
+msgstr "Altre intestazioni"
#. Tag: para
#: Mail.xml:235
#, no-c-format
-msgid ""
-"Sometimes you'll want to add other headers to your email. Seam provides "
-"support for some (see <xref linkend=\"mail.tags\"/>). For example, we can "
-"set the importance of the email, and ask for a read receipt:"
+msgid "Sometimes you'll want to add other headers to your email. Seam provides support for some (see <xref linkend=\"mail.tags\"/>). For example, we can set the importance of the email, and ask for a read receipt:"
msgstr ""
#. Tag: programlisting
@@ -523,40 +511,32 @@
" importance=\"low\"\n"
" requestReadReceipt=\"true\"/>]]>"
msgstr ""
+"<![CDATA[<m:message xmlns:m=\"http://jboss.com/products/seam/mail\"\n"
+" importance=\"low\"\n"
+" requestReadReceipt=\"true\"/>]]>"
#. Tag: para
#: Mail.xml:244
#, no-c-format
-msgid ""
-"Otherise you can add any header to the message using the <literal><m:"
-"header></literal> tag:"
+msgid "Otherise you can add any header to the message using the <literal><m:header></literal> tag:"
msgstr ""
#. Tag: programlisting
#: Mail.xml:249
#, no-c-format
msgid "<![CDATA[<m:header name=\"X-Sent-From\" value=\"JBoss Seam\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<m:header name=\"X-Sent-From\" value=\"JBoss Seam\"/>]]>"
#. Tag: title
#: Mail.xml:255
#, no-c-format
msgid "Receiving emails"
-msgstr ""
+msgstr "Ricevere email"
#. Tag: para
#: Mail.xml:257
#, no-c-format
-msgid ""
-"If you are using EJB then you can use a MDB (Message Driven Bean) to receive "
-"email. JBoss provides a JCA adaptor — <literal>mail-ra.rar</literal> "
-"— but the version distributed with JBoss AS has a number of "
-"limitations (and isn't bundled in some versions) therefore we recommend "
-"using the <literal>mail-ra.rar</literal> distributed with Seam is "
-"recommended (it's in the <literal>extras/</literal> directory in the Seam "
-"bundle). <literal>mail-ra.rar</literal> should be placed in <literal>"
-"$JBOSS_HOME/server/default/deploy</literal>; if the version of JBoss AS you "
-"use already has this file, replace it."
+msgid "If you are using EJB then you can use a MDB (Message Driven Bean) to receive email. JBoss provides a JCA adaptor — <literal>mail-ra.rar</literal> — but the version distributed with JBoss AS has a number of limitations (and isn't bundled in some versions) therefore we recommend using the <literal>mail-ra.rar</literal> distributed with Seam is recommended (it's in the <literal>extras/</literal> directory in the Seam bundle). <literal>mail-ra.rar</literal> should be placed in <literal>$JBOSS_HOME/server/default/deploy</literal>; if the version of JBoss AS you use already has this file, replace it."
msgstr ""
#. Tag: para
@@ -570,16 +550,11 @@
#, no-c-format
msgid ""
"<![CDATA[@MessageDriven(activationConfig={\n"
-" @ActivationConfigProperty(propertyName=\"mailServer\", propertyValue="
-"\"localhost\"),\n"
-" @ActivationConfigProperty(propertyName=\"mailFolder\", propertyValue="
-"\"INBOX\"),\n"
-" @ActivationConfigProperty(propertyName=\"storeProtocol\", propertyValue="
-"\"pop3\"),\n"
-" @ActivationConfigProperty(propertyName=\"userName\", propertyValue=\"seam"
-"\"),\n"
-" @ActivationConfigProperty(propertyName=\"password\", propertyValue=\"seam"
-"\")\n"
+" @ActivationConfigProperty(propertyName=\"mailServer\", propertyValue=\"localhost\"),\n"
+" @ActivationConfigProperty(propertyName=\"mailFolder\", propertyValue=\"INBOX\"),\n"
+" @ActivationConfigProperty(propertyName=\"storeProtocol\", propertyValue=\"pop3\"),\n"
+" @ActivationConfigProperty(propertyName=\"userName\", propertyValue=\"seam\"),\n"
+" @ActivationConfigProperty(propertyName=\"password\", propertyValue=\"seam\")\n"
"})\n"
"@ResourceAdapter(\"mail-ra.rar\")\n"
"@Name(\"mailListener\")\n"
@@ -595,107 +570,97 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@MessageDriven(activationConfig={\n"
+" @ActivationConfigProperty(propertyName=\"mailServer\", propertyValue=\"localhost\"),\n"
+" @ActivationConfigProperty(propertyName=\"mailFolder\", propertyValue=\"INBOX\"),\n"
+" @ActivationConfigProperty(propertyName=\"storeProtocol\", propertyValue=\"pop3\"),\n"
+" @ActivationConfigProperty(propertyName=\"userName\", propertyValue=\"seam\"),\n"
+" @ActivationConfigProperty(propertyName=\"password\", propertyValue=\"seam\")\n"
+"})\n"
+"@ResourceAdapter(\"mail-ra.rar\")\n"
+"@Name(\"mailListener\")\n"
+"public class MailListenerMDB implements MailListener {\n"
+"\n"
+" @In(create=true)\n"
+" private OrderProcessor orderProcessor;\n"
+"\n"
+" public void onMessage(Message message) {\n"
+" // Process the message\n"
+" orderProcessor.process(message.getSubject());\n"
+" }\n"
+" \n"
+"}]]>"
#. Tag: para
#: Mail.xml:275
#, no-c-format
-msgid ""
-"Each message received will cause <literal>onMessage(Message message)</"
-"literal> to be called. Most Seam annotations will work inside a MDB but you "
-"musn't access the persistence context."
+msgid "Each message received will cause <literal>onMessage(Message message)</literal> to be called. Most Seam annotations will work inside a MDB but you musn't access the persistence context."
msgstr ""
#. Tag: para
#: Mail.xml:281
#, no-c-format
-msgid ""
-"You can find more information on<literal>mail-ra.rar</literal> at <ulink url="
-"\"http://wiki.jboss.org/wiki/Wiki.jsp?page=InboundJavaMail\">http://wiki."
-"jboss.org/wiki/Wiki.jsp?page=InboundJavaMail</ulink>."
+msgid "You can find more information on<literal>mail-ra.rar</literal> at <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=InboundJavaMail\">http://wiki.jboss.org/wiki/Wiki.jsp?page=InboundJavaMail</ulink>."
msgstr ""
#. Tag: para
#: Mail.xml:286
#, no-c-format
-msgid ""
-"If you aren't using JBoss AS you can still use <literal>mail-ra.rar</"
-"literal> or you may find your application server includes a similar adapter."
+msgid "If you aren't using JBoss AS you can still use <literal>mail-ra.rar</literal> or you may find your application server includes a similar adapter."
msgstr ""
#. Tag: title
#: Mail.xml:294
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "Configurazione"
#. Tag: para
#: Mail.xml:296
#, no-c-format
-msgid ""
-"To include Email support in your application, include <literal>jboss-seam-"
-"mail.jar</literal> in your <literal>WEB-INF/lib</literal> directory. If you "
-"are using JBoss AS there is no further configuration needed to use Seam's "
-"email support. Otherwise you need to make sure you have the JavaMail API, an "
-"implementation of the JavaMail API present (the API and impl used in JBoss "
-"AS are distributed with seam as <literal>lib/mail.jar</literal>), and a copy "
-"of the Java Activation Framework (distributed with Seam as <literal>lib/"
-"activation.jar</literal>."
+msgid "To include Email support in your application, include <literal>jboss-seam-mail.jar</literal> in your <literal>WEB-INF/lib</literal> directory. If you are using JBoss AS there is no further configuration needed to use Seam's email support. Otherwise you need to make sure you have the JavaMail API, an implementation of the JavaMail API present (the API and impl used in JBoss AS are distributed with seam as <literal>lib/mail.jar</literal>), and a copy of the Java Activation Framework (distributed with Seam as <literal>lib/activation.jar</literal>."
msgstr ""
#. Tag: para
#: Mail.xml:308
#, no-c-format
-msgid ""
-"The Seam Email module requires the use of Facelets as the view technology. "
-"Future versions of the library may also support the use of JSP. "
-"Additionally, it requires the use of the seam-ui package."
+msgid "The Seam Email module requires the use of Facelets as the view technology. Future versions of the library may also support the use of JSP. Additionally, it requires the use of the seam-ui package."
msgstr ""
#. Tag: para
#: Mail.xml:315
#, no-c-format
-msgid ""
-"The <literal>mailSession</literal> component uses JavaMail to talk to a "
-"'real' SMTP server."
+msgid "The <literal>mailSession</literal> component uses JavaMail to talk to a 'real' SMTP server."
msgstr ""
#. Tag: literal
#: Mail.xml:321
#, no-c-format
msgid "mailSession"
-msgstr ""
+msgstr "mailSession"
#. Tag: para
#: Mail.xml:323
#, no-c-format
-msgid ""
-"A JavaMail Session may be available via a JNDI lookup if you are working in "
-"an JEE environment or you can use a Seam configured Session."
+msgid "A JavaMail Session may be available via a JNDI lookup if you are working in an JEE environment or you can use a Seam configured Session."
msgstr ""
#. Tag: para
#: Mail.xml:328
#, no-c-format
-msgid ""
-"The mailSession component's properties are described in more detail in <xref "
-"linkend=\"components.mail\"/>."
+msgid "The mailSession component's properties are described in more detail in <xref linkend=\"components.mail\"/>."
msgstr ""
#. Tag: title
#: Mail.xml:334
#, no-c-format
msgid "JNDI lookup in JBoss AS"
-msgstr ""
+msgstr "JNDI lookup in JBoss AS"
#. Tag: para
#: Mail.xml:336
#, no-c-format
-msgid ""
-"The JBossAS <literal>deploy/mail-service.xml</literal> configures a JavaMail "
-"session binding into JNDI. The default service configuration will need "
-"altering for your network. <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=JavaMail\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail</ulink> "
-"describes the service in more detail."
+msgid "The JBossAS <literal>deploy/mail-service.xml</literal> configures a JavaMail session binding into JNDI. The default service configuration will need altering for your network. <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail\">http://wiki.jboss.org/wiki/Wiki.jsp?page=JavaMail</ulink> describes the service in more detail."
msgstr ""
#. Tag: programlisting
@@ -710,13 +675,18 @@
" \n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
+" xmlns:mail=\"http://jboss.com/products/seam/mail\">\n"
+" \n"
+" <mail:mail-session session-jndi-name=\"java:/Mail\"/>\n"
+" \n"
+"</components>]]>"
#. Tag: para
#: Mail.xml:346
#, no-c-format
-msgid ""
-"Here we tell Seam to get the mail session bound to <literal>java:/Mail</"
-"literal> from JNDI."
+msgid "Here we tell Seam to get the mail session bound to <literal>java:/Mail</literal> from JNDI."
msgstr ""
#. Tag: title
@@ -728,9 +698,7 @@
#. Tag: para
#: Mail.xml:356
#, no-c-format
-msgid ""
-"A mail session can be configured via <literal>components.xml</literal>. Here "
-"we tell Seam to use <literal>smtp.example.com</literal> as the smtp server:"
+msgid "A mail session can be configured via <literal>components.xml</literal>. Here we tell Seam to use <literal>smtp.example.com</literal> as the smtp server:"
msgstr ""
#. Tag: programlisting
@@ -745,66 +713,55 @@
" \n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
+" xmlns:mail=\"http://jboss.com/products/seam/mail\">\n"
+" \n"
+" <mail:mail-session host=\"smtp.example.com\"/>\n"
+" \n"
+"</components>]]>"
#. Tag: title
#: Mail.xml:369
#, no-c-format
msgid "Meldware"
-msgstr ""
+msgstr "Meldware"
#. Tag: para
#: Mail.xml:371
#, no-c-format
-msgid ""
-"Seam's mail examples use Meldware (from <ulink url=\"http://buni.org\">buni."
-"org</ulink>) as a mail server. Meldware is a groupware package that provides "
-"<literal>SMTP</literal>, <literal>POP3</literal>, <literal>IMAP</literal>, "
-"webmail, a shared calendar and an graphical admin tool; it's written as a "
-"JEE application so can be deployed onto JBoss AS alongside your Seam "
-"application."
+msgid "Seam's mail examples use Meldware (from <ulink url=\"http://buni.org\">buni.org</ulink>) as a mail server. Meldware is a groupware package that provides <literal>SMTP</literal>, <literal>POP3</literal>, <literal>IMAP</literal>, webmail, a shared calendar and an graphical admin tool; it's written as a JEE application so can be deployed onto JBoss AS alongside your Seam application."
msgstr ""
#. Tag: para
#: Mail.xml:381
#, no-c-format
-msgid ""
-"The version of Meldware distributed with Seam (downloaded on demand) is "
-"specially tailored for development - mailboxes, users and aliases (email "
-"addresses) are created every time the application deploys. If you want to "
-"use Meldware in production you should install the latest release from <ulink "
-"url=\"http://buni.org\">buni.org</ulink>."
+msgid "The version of Meldware distributed with Seam (downloaded on demand) is specially tailored for development - mailboxes, users and aliases (email addresses) are created every time the application deploys. If you want to use Meldware in production you should install the latest release from <ulink url=\"http://buni.org\">buni.org</ulink>."
msgstr ""
#. Tag: title
#: Mail.xml:393
#, no-c-format
msgid "Tags"
-msgstr ""
+msgstr "Tag"
#. Tag: para
#: Mail.xml:395
#, no-c-format
-msgid ""
-"Emails are generated using tags in the <literal>http://jboss.com/products/"
-"seam/mail</literal> namespace. Documents should always have the "
-"<literal>message</literal> tag at the root of the message. The message tag "
-"prepares Seam to generate an email."
+msgid "Emails are generated using tags in the <literal>http://jboss.com/products/seam/mail</literal> namespace. Documents should always have the <literal>message</literal> tag at the root of the message. The message tag prepares Seam to generate an email."
msgstr ""
#. Tag: para
#: Mail.xml:402
#, no-c-format
-msgid ""
-"The standard templating tags of facelets can be used as normal. Inside the "
-"body you can use any JSF tag; if it requires access to external resources "
-"(stylesheets, javascript) then be sure to set the <literal>urlBase</literal>."
+msgid "The standard templating tags of facelets can be used as normal. Inside the body you can use any JSF tag; if it requires access to external resources (stylesheets, javascript) then be sure to set the <literal>urlBase</literal>."
msgstr ""
#. Tag: term
#: Mail.xml:411
#, no-c-format
msgid "<m:message>"
-msgstr ""
+msgstr "<m:message>"
#. Tag: para
#: Mail.xml:413
@@ -815,35 +772,25 @@
#. Tag: para
#: Mail.xml:418
#, no-c-format
-msgid ""
-"<literal>importance</literal> — low, normal or high. By default "
-"normal, this sets the importance of the mail message."
+msgid "<literal>importance</literal> — low, normal or high. By default normal, this sets the importance of the mail message."
msgstr ""
#. Tag: para
#: Mail.xml:424
#, no-c-format
-msgid ""
-"<literal>precedence</literal> — sets the precedence of the message (e."
-"g. bulk)."
+msgid "<literal>precedence</literal> — sets the precedence of the message (e.g. bulk)."
msgstr ""
#. Tag: para
#: Mail.xml:430
#, no-c-format
-msgid ""
-"<literal>requestReadReceipt</literal> — by default false, if set, a "
-"read receipt request will be will be added, with the read receipt being sent "
-"to the <literal>From:</literal> address."
+msgid "<literal>requestReadReceipt</literal> — by default false, if set, a read receipt request will be will be added, with the read receipt being sent to the <literal>From:</literal> address."
msgstr ""
#. Tag: para
#: Mail.xml:438
#, no-c-format
-msgid ""
-"<literal>urlBase</literal> — If set, the value is prepended to the "
-"<literal>requestContextPath</literal> allowing you to use components such as "
-"<literal><h:graphicImage></literal> in your emails."
+msgid "<literal>urlBase</literal> — If set, the value is prepended to the <literal>requestContextPath</literal> allowing you to use components such as <literal><h:graphicImage></literal> in your emails."
msgstr ""
#. Tag: para
@@ -856,14 +803,12 @@
#: Mail.xml:454
#, no-c-format
msgid "<m:from>"
-msgstr ""
+msgstr "<m:from>"
#. Tag: para
#: Mail.xml:456
#, no-c-format
-msgid ""
-"Set's the From: address for the email. You can only have one of these per "
-"email."
+msgid "Set's the From: address for the email. You can only have one of these per email."
msgstr ""
#. Tag: para
@@ -873,50 +818,48 @@
msgstr ""
#. Tag: para
-#: Mail.xml:468 Mail.xml:485
+#: Mail.xml:468
+#: Mail.xml:485
#, no-c-format
-msgid ""
-"<literal>address</literal> — the email address the email should come "
-"from."
+msgid "<literal>address</literal> — the email address the email should come from."
msgstr ""
#. Tag: term
#: Mail.xml:477
#, no-c-format
msgid "<m:replyTo>"
-msgstr ""
+msgstr "<m:replyTo>"
#. Tag: para
#: Mail.xml:479
#, no-c-format
-msgid ""
-"Set's the Reply-to: address for the email. You can only have one of these "
-"per email."
+msgid "Set's the Reply-to: address for the email. You can only have one of these per email."
msgstr ""
#. Tag: term
#: Mail.xml:494
#, no-c-format
msgid "<m:to>"
-msgstr ""
+msgstr "<m:to>"
#. Tag: para
#: Mail.xml:496
#, no-c-format
-msgid ""
-"Add a recipient to the email. Use multiple <m:to> tags for multiple "
-"recipients. This tag can be safely placed inside a repeat tag such as <ui:"
-"repeat>."
+msgid "Add a recipient to the email. Use multiple <m:to> tags for multiple recipients. This tag can be safely placed inside a repeat tag such as <ui:repeat>."
msgstr ""
#. Tag: para
-#: Mail.xml:503 Mail.xml:525 Mail.xml:548
+#: Mail.xml:503
+#: Mail.xml:525
+#: Mail.xml:548
#, no-c-format
msgid "<literal>name</literal> — the name of the recipient."
msgstr ""
#. Tag: para
-#: Mail.xml:508 Mail.xml:530 Mail.xml:553
+#: Mail.xml:508
+#: Mail.xml:530
+#: Mail.xml:553
#, no-c-format
msgid "<literal>address</literal> — the email address of the recipient."
msgstr ""
@@ -925,66 +868,55 @@
#: Mail.xml:516
#, no-c-format
msgid "<m:cc>"
-msgstr ""
+msgstr "<m:cc>"
#. Tag: para
#: Mail.xml:518
#, no-c-format
-msgid ""
-"Add a cc recipient to the email. Use multiple <m:cc> tags for multiple "
-"ccs. This tag can be safely placed inside a iterator tag such as <ui:"
-"repeat>."
+msgid "Add a cc recipient to the email. Use multiple <m:cc> tags for multiple ccs. This tag can be safely placed inside a iterator tag such as <ui:repeat>."
msgstr ""
#. Tag: term
#: Mail.xml:539
#, no-c-format
msgid "<m:bcc>"
-msgstr ""
+msgstr "<m:bcc>"
#. Tag: para
#: Mail.xml:541
#, no-c-format
-msgid ""
-"Add a bcc recipient to the email. Use multiple <m:bcc> tags for "
-"multiple bccs. This tag can be safely placed inside a repeat tag such as <"
-"ui:repeat>."
+msgid "Add a bcc recipient to the email. Use multiple <m:bcc> tags for multiple bccs. This tag can be safely placed inside a repeat tag such as <ui:repeat>."
msgstr ""
#. Tag: term
#: Mail.xml:562
#, no-c-format
msgid "<m:header>"
-msgstr ""
+msgstr "<m:header>"
#. Tag: para
#: Mail.xml:564
#, no-c-format
-msgid ""
-"Add a header to the email (e.g. <literal>X-Sent-From: JBoss Seam</literal>)"
+msgid "Add a header to the email (e.g. <literal>X-Sent-From: JBoss Seam</literal>)"
msgstr ""
#. Tag: para
#: Mail.xml:569
#, no-c-format
-msgid ""
-"<literal>name</literal> — The name of the header to add (e.g. "
-"<literal>X-Sent-From</literal>)."
+msgid "<literal>name</literal> — The name of the header to add (e.g. <literal>X-Sent-From</literal>)."
msgstr ""
#. Tag: para
#: Mail.xml:575
#, no-c-format
-msgid ""
-"<literal>value</literal> — The value of the header to add (e.g. "
-"<literal>JBoss Seam</literal>)."
+msgid "<literal>value</literal> — The value of the header to add (e.g. <literal>JBoss Seam</literal>)."
msgstr ""
#. Tag: term
#: Mail.xml:584
#, no-c-format
msgid "<m:attachment>"
-msgstr ""
+msgstr "<m:attachment>"
#. Tag: para
#: Mail.xml:586
@@ -1001,44 +933,31 @@
#. Tag: para
#: Mail.xml:596
#, no-c-format
-msgid ""
-"<literal>String</literal> — A <literal>String</literal> is interpreted "
-"as a path to file within the classpath"
+msgid "<literal>String</literal> — A <literal>String</literal> is interpreted as a path to file within the classpath"
msgstr ""
#. Tag: para
#: Mail.xml:602
#, no-c-format
-msgid ""
-"<literal>java.io.File</literal> — An EL expression can reference a "
-"<literal>File</literal> object"
+msgid "<literal>java.io.File</literal> — An EL expression can reference a <literal>File</literal> object"
msgstr ""
#. Tag: para
#: Mail.xml:608
#, no-c-format
-msgid ""
-"<literal>java.net.URL</literal> — An EL expression can reference a "
-"<literal>URL</literal> object"
+msgid "<literal>java.net.URL</literal> — An EL expression can reference a <literal>URL</literal> object"
msgstr ""
#. Tag: para
#: Mail.xml:614
#, no-c-format
-msgid ""
-"<literal>java.io.InputStream</literal> — An EL expression can "
-"reference an <literal>InputStream</literal>. In this case both a "
-"<literal>fileName</literal> and a <literal>contentType</literal> must be "
-"specified."
+msgid "<literal>java.io.InputStream</literal> — An EL expression can reference an <literal>InputStream</literal>. In this case both a <literal>fileName</literal> and a <literal>contentType</literal> must be specified."
msgstr ""
#. Tag: para
#: Mail.xml:622
#, no-c-format
-msgid ""
-"<literal>byte[]</literal> — An EL expression can reference an "
-"<literal>byte[]</literal>. In this case both a <literal>fileName</literal> "
-"and a <literal>contentType</literal> must be specified."
+msgid "<literal>byte[]</literal> — An EL expression can reference an <literal>byte[]</literal>. In this case both a <literal>fileName</literal> and a <literal>contentType</literal> must be specified."
msgstr ""
#. Tag: para
@@ -1050,42 +969,32 @@
#. Tag: para
#: Mail.xml:633
#, no-c-format
-msgid ""
-"If this tag contains a <literal><p:document></literal> tag, the "
-"document described will be generated and attached to the email. A "
-"<literal>fileName</literal> should be specfied."
+msgid "If this tag contains a <literal><p:document></literal> tag, the document described will be generated and attached to the email. A <literal>fileName</literal> should be specfied."
msgstr ""
#. Tag: para
#: Mail.xml:641
#, no-c-format
-msgid ""
-"If this tag contains other JSF tags a HTML document will be generated from "
-"them and attached to the email. A <literal>fileName</literal> should be "
-"specfied."
+msgid "If this tag contains other JSF tags a HTML document will be generated from them and attached to the email. A <literal>fileName</literal> should be specfied."
msgstr ""
#. Tag: para
#: Mail.xml:650
#, no-c-format
-msgid ""
-"<literal>fileName</literal> — Specify the file name to use for the "
-"attached file."
+msgid "<literal>fileName</literal> — Specify the file name to use for the attached file."
msgstr ""
#. Tag: para
#: Mail.xml:656
#, no-c-format
-msgid ""
-"<literal>contentType</literal> — Specify the MIME type of the attached "
-"file"
+msgid "<literal>contentType</literal> — Specify the MIME type of the attached file"
msgstr ""
#. Tag: term
#: Mail.xml:665
#, no-c-format
msgid "<m:subject>"
-msgstr ""
+msgstr "<m:subject>"
#. Tag: para
#: Mail.xml:667
@@ -1097,21 +1006,17 @@
#: Mail.xml:673
#, no-c-format
msgid "<m:body>"
-msgstr ""
+msgstr "<m:body>"
#. Tag: para
#: Mail.xml:675
#, no-c-format
-msgid ""
-"Set's the body for the email. Supports an <literal>alternative</literal> "
-"facet which, if an HTML email is generated can contain alternative text for "
-"a mail reader which doesn't support html."
+msgid "Set's the body for the email. Supports an <literal>alternative</literal> facet which, if an HTML email is generated can contain alternative text for a mail reader which doesn't support html."
msgstr ""
#. Tag: para
#: Mail.xml:682
#, no-c-format
-msgid ""
-"<literal>type</literal> — If set to <literal>plain</literal> then a "
-"plain text email will be generated otherwise an HTML email is generated."
+msgid "<literal>type</literal> — If set to <literal>plain</literal> then a plain text email will be generated otherwise an HTML email is generated."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Performance.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Performance.po 2008-12-15 15:50:47 UTC (rev 9783)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Performance.po 2008-12-15 17:36:40 UTC (rev 9784)
@@ -3,11 +3,11 @@
#
msgid ""
msgstr ""
-"Project-Id-Version: Seam_Reference_Guide \n"
+"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"
+"PO-Revision-Date: 2008-12-15 18:33+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,57 +17,37 @@
#: Performance.xml:5
#, no-c-format
msgid "Performance Tuning"
-msgstr ""
+msgstr "Tuning delle performance"
#. 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 ""
+msgid "This chapter is an attempt to document in one place all the tips for getting the best performance from your Seam application."
+msgstr "Questo capitolo è un tentativo di documentazione in un unico posto tutti i suggerimenti per ottenere le migliore performance da un'applicazione Seam."
#. Tag: title
#: Performance.xml:13
#, no-c-format
msgid "Bypassing Interceptors"
-msgstr ""
+msgstr "Bypassare gli interceptor"
#. 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 ""
+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 "Per binding di value repetitivi come quelli in dataTable JSF o altri controlli iterativi (come <literal>ui:repeat</literal>), l'intero stack di interceptor verrà invocato ad ogni invocazione di un componente Seam referenziato. L'effetto di questo può essere una sostanziale performance, specialmente se il componente viene chiamato molte volte. Un guadagno significante di performance può essere ottenuto disabilitando lo stack degli interceptor per in componente Seam da invocare. Per disabilitare gli interceptor di un componente occorre aggiungere l'annotazione <literal>@BypassInterceptors</literal> alla classe del componente."
#. 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 ""
+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 "E' molto importante essere consapevoli delle implicazioni che seguono la disabilitazioni degli interceptor per un componente Seam. Funzionalità quali la bijection, le restrizioni annotate sulla sicurezza, la sincronizzazione e altro vengono a mancare per un componente marcato con <literal>@BypassInterceptors</literal>. Mentre nella maggior parte dei casi è possibile compensare la perdita di queste funzionalità (es. invece di iniettare un componente usando <literal>@In</literal>, si può invece usare <literal>Component.getInstance()</literal>) è importante essere consci delle conseguenze."
#. Tag: para
#: Performance.xml:35
#, no-c-format
-msgid ""
-"The following code listing demonstrates a Seam component with its "
-"interceptors disabled:"
-msgstr ""
+msgid "The following code listing demonstrates a Seam component with its interceptors disabled:"
+msgstr "Il seguente listato di codice dimostra che un componente Seam viene disabilitato con i suoi interceptor:"
#. Tag: programlisting
#: Performance.xml:39
@@ -80,8 +60,7 @@
"{\n"
" public String getRowActions()\n"
" {\n"
-" // Role-based security check performed inline instead of using "
-"@Restrict or other security annotation\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"
@@ -93,3 +72,22 @@
" }\n"
"}]]>"
msgstr ""
+"<![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"
+"}]]>"
+
More information about the seam-commits
mailing list