Seam SVN: r9791 - trunk/examples/openid/src/org/jboss/seam/example/openid.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-16 14:26:27 -0500 (Tue, 16 Dec 2008)
New Revision: 9791
Added:
trunk/examples/openid/src/org/jboss/seam/example/openid/testng.xml
Log:
add testng stub
Added: trunk/examples/openid/src/org/jboss/seam/example/openid/testng.xml
===================================================================
--- trunk/examples/openid/src/org/jboss/seam/example/openid/testng.xml (rev 0)
+++ trunk/examples/openid/src/org/jboss/seam/example/openid/testng.xml 2008-12-16 19:26:27 UTC (rev 9791)
@@ -0,0 +1,5 @@
+<!DOCTYPE suite SYSTEM "http://beust.com/testng/testng-1.0.dtd" >
+
+<suite name="openid" verbose="2" parallel="false">
+
+</suite>
16 years
- 1
- 0
Seam SVN: r9790 - branches/community/Seam_2_0/src/main/org/jboss/seam/core.
by seam-commits＠lists.jboss.org
Author: youngm
Date: 2008-12-16 13:38:32 -0500 (Tue, 16 Dec 2008)
New Revision: 9790
Modified:
branches/community/Seam_2_0/src/main/org/jboss/seam/core/Interpolator.java
Log:
JBSEAM-2197
Modified: branches/community/Seam_2_0/src/main/org/jboss/seam/core/Interpolator.java
===================================================================
--- branches/community/Seam_2_0/src/main/org/jboss/seam/core/Interpolator.java 2008-12-16 16:11:06 UTC (rev 9789)
+++ branches/community/Seam_2_0/src/main/org/jboss/seam/core/Interpolator.java 2008-12-16 18:38:32 UTC (rev 9790)
@@ -122,8 +122,15 @@
} else if (nextTok.equals("}")) {
if (--level == 0) {
try {
- String value = new MessageFormat(expr.toString(), Locale.instance()).format(params);
- builder.append(value);
+ if (params.length == 0)
+ {
+ builder.append(expr.toString());
+ }
+ else
+ {
+ String value = new MessageFormat(expr.toString(), Locale.instance()).format(params);
+ builder.append(value);
+ }
} catch (Exception e) {
// if it is a bad message, use the expression itself
builder.append(expr);
16 years
- 1
- 0
Seam SVN: r9789 - trunk/doc/Seam_Reference_Guide/fr-FR.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-16 11:11:06 -0500 (Tue, 16 Dec 2008)
New Revision: 9789
Modified:
trunk/doc/Seam_Reference_Guide/fr-FR/Events.po
Log:
JBSEAM-3847
Modified: trunk/doc/Seam_Reference_Guide/fr-FR/Events.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/fr-FR/Events.po 2008-12-16 13:31:03 UTC (rev 9788)
+++ trunk/doc/Seam_Reference_Guide/fr-FR/Events.po 2008-12-16 16:11:06 UTC (rev 9789)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-04 00:58+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-16 16:59+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,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}"
-"\"/>]]>"
+msgid "<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}\"/>]]>"
msgstr ""
#. 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
@@ -116,10 +99,7 @@
#. 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 +111,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 +122,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
@@ -167,27 +144,19 @@
#. 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
@@ -199,17 +168,13 @@
#. 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,8 +183,7 @@
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>]]>"
@@ -234,19 +198,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 +222,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
@@ -284,58 +240,37 @@
#. 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 +282,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
@@ -368,44 +300,25 @@
#. 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 +330,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
@@ -437,22 +347,13 @@
#. 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
@@ -470,23 +371,13 @@
#. 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
@@ -504,20 +395,13 @@
#. 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 +424,14 @@
" <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 ""
#. Tag: para
-#: Events.xml:314 Events.xml:327
+#: Events.xml:314
+#: Events.xml:327
#, no-c-format
msgid "Alternatively:"
msgstr ""
@@ -560,8 +444,7 @@
" <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 ""
@@ -569,8 +452,7 @@
#. 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
@@ -604,17 +486,13 @@
#. 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 +504,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 +522,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
@@ -709,10 +578,7 @@
#. 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
@@ -755,18 +621,13 @@
#. 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
@@ -788,10 +649,7 @@
#. 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,8 +662,7 @@
" <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"
@@ -816,10 +673,7 @@
#. 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
@@ -840,9 +694,7 @@
#. 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
@@ -882,21 +734,13 @@
#. 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,8 +750,7 @@
"<![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 ""
@@ -920,19 +763,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
@@ -956,10 +793,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
@@ -997,10 +831,7 @@
#. 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
@@ -1018,11 +849,7 @@
#. 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
@@ -1041,12 +868,7 @@
#. 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,8 +879,7 @@
"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"
"}]]>"
@@ -1086,306 +907,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 +1141,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 +1151,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"
@@ -1434,15 +1170,7 @@
#. 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
@@ -1458,9 +1186,7 @@
#. 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
@@ -1483,10 +1209,7 @@
#. 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
@@ -1506,9 +1229,7 @@
#. 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
@@ -1525,43 +1246,25 @@
#. 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 +1276,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 +1288,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 +1318,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
@@ -1666,10 +1339,7 @@
#. 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 +1351,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
@@ -1699,10 +1365,7 @@
#. 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 +1374,25 @@
msgid ""
"<![CDATA[@Redirect(viewId=\"/failure.xhtml\", end=true)\n"
"@ApplicationException(rollback=true)\n"
-"public class UnrecoverableApplicationException extends RuntimeException "
-"{ ... }]]>"
+"public class UnrecoverableApplicationException extends RuntimeException { ... }]]>"
msgstr ""
#. 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
@@ -1757,10 +1412,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
@@ -1793,25 +1445,19 @@
#. 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,8 +1472,7 @@
" <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"
@@ -1837,11 +1482,7 @@
#. 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,25 +1494,16 @@
#. 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 ""
@@ -1879,22 +1511,16 @@
#. 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 ""
@@ -1902,11 +1528,7 @@
#. 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,8 +1556,7 @@
"<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 ""
@@ -1950,8 +1571,7 @@
#: 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"
@@ -1968,8 +1588,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"
@@ -2002,11 +1621,7 @@
#. 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 +1633,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\"/>]]>"
+msgid "<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
msgstr ""
+
16 years
- 1
- 0
Seam SVN: r9788 - branches/enterprise/JBPAPP_4_2_CP01/examples/icefaces/view.
by seam-commits＠lists.jboss.org
Author: manaRH
Date: 2008-12-16 08:31:03 -0500 (Tue, 16 Dec 2008)
New Revision: 9788
Modified:
branches/enterprise/JBPAPP_4_2_CP01/examples/icefaces/view/main.xhtml
Log:
JBPAPP-1353
Modified: branches/enterprise/JBPAPP_4_2_CP01/examples/icefaces/view/main.xhtml
===================================================================
--- branches/enterprise/JBPAPP_4_2_CP01/examples/icefaces/view/main.xhtml 2008-12-16 12:23:07 UTC (rev 9787)
+++ branches/enterprise/JBPAPP_4_2_CP01/examples/icefaces/view/main.xhtml 2008-12-16 13:31:03 UTC (rev 9788)
@@ -65,7 +65,7 @@
</h:column>
<h:column>
<f:facet name="header">Action</f:facet>
- <ice:commandLink id="viewHotel" value="View Hotel" action="#{hotelBooking.selectHotel(hot)}"/>
+ <s:link id="viewHotel" value="View Hotel" action="#{hotelBooking.selectHotel(hot)}"/>
</h:column>
</ice:dataTable>
<s:link value="More results" action="#{hotelSearch.nextPage}" rendered="#{hotelSearch.nextPageAvailable}"/>
16 years
- 1
- 0
Seam SVN: r9787 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-16 07:23:07 -0500 (Tue, 16 Dec 2008)
New Revision: 9787
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
trunk/doc/Seam_Reference_Guide/it-IT/Tools.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-16 11:19:03 UTC (rev 9786)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-16 12:23:07 UTC (rev 9787)
@@ -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-16 12:18+0100\n"
+"PO-Revision-Date: 2008-12-16 12:44+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,7 +23,7 @@
#: Drools.xml:7
#, no-c-format
msgid "Seam makes it easy to call JBoss Rules (Drools) rulebases from Seam components or jBPM process definitions."
-msgstr "Seam agevola le chiamate alle regole di JBoss Rules (Drools) dai componenti Seam o dalle definizioni di processo jBPM."
+msgstr "Seam facilita le chiamate alle regole di JBoss Rules (Drools) dai componenti Seam o dalle definizioni di processo jBPM."
#. Tag: title
#: Drools.xml:13
@@ -35,7 +35,7 @@
#: Drools.xml:15
#, no-c-format
msgid "The first step is to make an instance of <literal>org.drools.RuleBase</literal> available in a Seam context variable. For testing purposes, Seam provides a built-in component that compiles a static set of rules from the classpath. You can install this component via <literal>components.xml</literal>:"
-msgstr "Il primo passo è creare un'istanza di <literal>org.drools.RuleBase</literal> disponibile in una variabile del contesto di Seam. Per testare Seam fornisce un componente interno che compila un set statico di regole dal classpath. Puoi installare questo componente tramite <literal>components.xml</literal>:"
+msgstr "Il primo passo è creare un'istanza di <literal>org.drools.RuleBase</literal> disponibile in una variabile del contesto di Seam. Per i test Seam fornisce un componente interno che compila un set statico di regole dal classpath. Puoi installare questo componente tramite <literal>components.xml</literal>:"
#. Tag: programlisting
#: Drools.xml:22
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-16 11:19:03 UTC (rev 9786)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-16 12:23:07 UTC (rev 9787)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-14 21:05+0100\n"
+"PO-Revision-Date: 2008-12-16 13:21+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,7 +23,7 @@
#: Preface.xml:9
#, no-c-format
msgid "Seam is an application framework for Enterprise Java. It is inspired by the following principles:"
-msgstr "Seam è un'application framework per Java Enterprise. E' ispirato dai seguenti principi:"
+msgstr "Seam è un'application framework per Java Enterprise. Si ispira ai seguenti principi:"
#. Tag: emphasis
#: Preface.xml:16
@@ -114,7 +114,7 @@
#: Preface.xml:103
#, no-c-format
msgid "Optionally, Seam provides transparent business process management via jBPM. You won't believe how easy it is to implement complex workflows, collaboration and and task management using jBPM and Seam."
-msgstr "Opzionalmente Seam può fornire una gestione trasparente del processo di business tramite jBPM. Non ci crederai quanto è facile implementare dei workflow complessi, delle collaborazioni ed una gestione dei compiti utilizzando jBPM e Seam."
+msgstr "Opzionalmente Seam può fornire una gestione trasparente del processo di business tramite jBPM. Non ci crederai quanto è facile implementare workflow complessi, collaborazioni ed una gestione dei compiti utilizzando jBPM e Seam."
#. Tag: para
#: Preface.xml:108
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tools.po 2008-12-16 11:19:03 UTC (rev 9786)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tools.po 2008-12-16 12:23:07 UTC (rev 9787)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-12 00:16+0100\n"
+"PO-Revision-Date: 2008-12-16 12:55+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -29,7 +29,7 @@
#: Tools.xml:7
#, no-c-format
msgid "The jBPM designer and viewer will let you design and view in a nice way your business processes and your pageflows. This convenient tool is part of JBoss Eclipse IDE and more details can be found in the jBPM's documentation (http://docs.jboss.com/jbpm/v3/gpd/)"
-msgstr "Il designer ed il visualizzatore jBPM ti consente di progettare e vedere i tuoi processi di business ed i pageflow. Questo ottimo strumento è parte di JBoss Eclipse IDE ed ulteriori dettagli sono disponibili nella documentazione di jBPM (http://docs.jboss.com/jbpm/v3/gpd/)"
+msgstr "Il designer ed il visualizzatore jBPM ti consentono di progettare e vedere i processi di business ed i pageflow. Quest'ottimo strumento è parte di JBoss Eclipse IDE ed ulteriori dettagli sono disponibili nella documentazione di jBPM (http://docs.jboss.com/jbpm/v3/gpd/)"
#. Tag: title
#: Tools.xml:13
16 years
- 1
- 0
Seam SVN: r9786 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-16 06:19:03 -0500 (Tue, 16 Dec 2008)
New Revision: 9786
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po
trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:22+0000\n"
-"PO-Revision-Date: 2008-12-12 00:02+0100\n"
+"PO-Revision-Date: 2008-12-16 11:25+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -409,7 +409,7 @@
#: Annotations.xml:303
#, no-c-format
msgid "Annotations for bijection"
-msgstr ""
+msgstr "Annotazioni per la bijection"
#. Tag: para
#: Annotations.xml:304
@@ -632,7 +632,7 @@
#: Annotations.xml:478
#, no-c-format
msgid "<![CDATA[@Factory(\"processInstance\", scope=CONVERSATION) public ProcessInstance createProcessInstance() { ... }]]>"
-msgstr ""
+msgstr "<![CDATA[@Factory(\"processInstance\", scope=CONVERSATION) public ProcessInstance createProcessInstance() { ... }]]>"
#. Tag: para
#: Annotations.xml:479
@@ -722,7 +722,7 @@
#: Annotations.xml:579
#, no-c-format
msgid "Annotations for component lifecycle methods"
-msgstr ""
+msgstr "Annotazioni per i metodi del ciclo di vita dei componenti"
#. Tag: para
#: Annotations.xml:580
@@ -806,7 +806,7 @@
#: Annotations.xml:645
#, no-c-format
msgid "Annotations for context demarcation"
-msgstr ""
+msgstr "Annotazioni per la demarcazione del contesto"
#. Tag: para
#: Annotations.xml:646
@@ -916,13 +916,13 @@
#: Annotations.xml:739
#, no-c-format
msgid "@End"
-msgstr ""
+msgstr "@End"
#. Tag: programlisting
#: Annotations.xml:742
#, no-c-format
msgid "<![CDATA[@End]]>"
-msgstr ""
+msgstr "<![CDATA[@End]]>"
#. Tag: para
#: Annotations.xml:743
@@ -947,13 +947,13 @@
#: Annotations.xml:775
#, no-c-format
msgid "@StartTask"
-msgstr ""
+msgstr "@StartTask"
#. Tag: programlisting
#: Annotations.xml:778
#, no-c-format
msgid "<![CDATA[@StartTask]]>"
-msgstr ""
+msgstr "<![CDATA[@StartTask]]>"
#. Tag: para
#: Annotations.xml:779
@@ -978,13 +978,13 @@
#: Annotations.xml:824
#, no-c-format
msgid "@BeginTask"
-msgstr ""
+msgstr "@BeginTask"
#. Tag: programlisting
#: Annotations.xml:827
#, no-c-format
msgid "<![CDATA[@BeginTask]]>"
-msgstr ""
+msgstr "<![CDATA[@BeginTask]]>"
#. Tag: para
#: Annotations.xml:828
@@ -1002,13 +1002,13 @@
#: Annotations.xml:870
#, no-c-format
msgid "@EndTask"
-msgstr ""
+msgstr "@EndTask"
#. Tag: programlisting
#: Annotations.xml:873
#, no-c-format
msgid "<![CDATA[@EndTask]]>"
-msgstr ""
+msgstr "<![CDATA[@EndTask]]>"
#. Tag: para
#: Annotations.xml:874
@@ -1020,7 +1020,7 @@
#: Annotations.xml:883
#, no-c-format
msgid "<![CDATA[@EndTask(transition=\"transitionName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@EndTask(transition=\"transitionName\")]]>"
#. Tag: para
#: Annotations.xml:884
@@ -1038,13 +1038,13 @@
#: Annotations.xml:911
#, no-c-format
msgid "@CreateProcess"
-msgstr ""
+msgstr "@CreateProcess"
#. Tag: programlisting
#: Annotations.xml:914
#, no-c-format
msgid "<![CDATA[@CreateProcess(definition=\"process definition name\")]]>"
-msgstr ""
+msgstr "<![CDATA[@CreateProcess(definition=\"process definition name\")]]>"
#. Tag: para
#: Annotations.xml:915
@@ -1062,13 +1062,13 @@
#: Annotations.xml:935
#, no-c-format
msgid "@ResumeProcess"
-msgstr ""
+msgstr "@ResumeProcess"
#. Tag: programlisting
#: Annotations.xml:938
#, no-c-format
msgid "<![CDATA[@ResumeProcess(processIdParameter=\"processId\")]]>"
-msgstr ""
+msgstr "<![CDATA[@ResumeProcess(processIdParameter=\"processId\")]]>"
#. Tag: para
#: Annotations.xml:939
@@ -1086,13 +1086,13 @@
#: Annotations.xml:960
#, no-c-format
msgid "@Transition"
-msgstr ""
+msgstr "@Transition"
#. Tag: programlisting
#: Annotations.xml:963
#, no-c-format
msgid "<![CDATA[@Transition(\"cancel\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Transition(\"cancel\")]]>"
#. Tag: para
#: Annotations.xml:964
@@ -1116,13 +1116,13 @@
#: Annotations.xml:984
#, no-c-format
msgid "@Transactional"
-msgstr ""
+msgstr "@Transactional"
#. Tag: programlisting
#: Annotations.xml:987
#, no-c-format
msgid "<![CDATA[@Transactional]]>"
-msgstr ""
+msgstr "<![CDATA[@Transactional]]>"
#. Tag: para
#: Annotations.xml:988
@@ -1140,13 +1140,13 @@
#: Annotations.xml:1004
#, no-c-format
msgid "@ApplicationException"
-msgstr ""
+msgstr "@ApplicationException"
#. Tag: programlisting
#: Annotations.xml:1007
#, no-c-format
msgid "<![CDATA[@ApplicationException]]>"
-msgstr ""
+msgstr "<![CDATA[@ApplicationException]]>"
#. Tag: para
#: Annotations.xml:1008
@@ -1176,13 +1176,13 @@
#: Annotations.xml:1041
#, no-c-format
msgid "@Interceptors"
-msgstr ""
+msgstr "@Interceptors"
#. Tag: programlisting
#: Annotations.xml:1044
#, no-c-format
msgid "<![CDATA[@Interceptors({DVDInterceptor, CDInterceptor})]]>"
-msgstr ""
+msgstr "<![CDATA[@Interceptors({DVDInterceptor, CDInterceptor})]]>"
#. Tag: para
#: Annotations.xml:1045
@@ -1206,7 +1206,7 @@
#: Annotations.xml:1068
#, no-c-format
msgid "Annotations for exceptions"
-msgstr ""
+msgstr "Annotazioni per le eccezioni"
#. Tag: para
#: Annotations.xml:1070
@@ -1285,7 +1285,7 @@
#: Annotations.xml:1146
#, no-c-format
msgid "Annotations for Seam Remoting"
-msgstr ""
+msgstr "Annotazioni per Seam Remoting"
#. Tag: para
#: Annotations.xml:1147
@@ -1315,7 +1315,7 @@
#: Annotations.xml:1173
#, no-c-format
msgid "Annotations for Seam interceptors"
-msgstr ""
+msgstr "Annotazioni per gli interceptor di Seam"
#. Tag: para
#: Annotations.xml:1174
@@ -1333,7 +1333,7 @@
#: Annotations.xml:1185
#, no-c-format
msgid "@Interceptor"
-msgstr ""
+msgstr "@Interceptor"
#. Tag: programlisting
#: Annotations.xml:1188
@@ -1387,7 +1387,7 @@
#: Annotations.xml:1215
#, no-c-format
msgid "Annotations for asynchronicity"
-msgstr ""
+msgstr "Annotazioni per l'asincronicità"
#. Tag: para
#: Annotations.xml:1216
@@ -1489,7 +1489,7 @@
#: Annotations.xml:1278
#, no-c-format
msgid "Annotations for use with JSF"
-msgstr ""
+msgstr "Annotazioni per l'uso di JSF"
#. Tag: para
#: Annotations.xml:1279
@@ -1736,7 +1736,7 @@
#: Annotations.xml:1535
#, no-c-format
msgid "@Filter"
-msgstr ""
+msgstr "@Filter"
#. Tag: para
#: Annotations.xml:1538
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-04 00:58+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-16 11:34+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,27 +22,19 @@
#. Tag: para
#: Configuration.xml:6
#, no-c-format
-msgid ""
-"Configuration is a very boring topic and an extremely tedious pastime. "
-"Unfortunately, several lines of XML are required to integrate Seam into your "
-"JSF implementation and servlet container. There's no need to be too put off "
-"by the following sections; you'll never need to type any of this stuff "
-"yourself, since you can just use seam-gen to start your application or you "
-"can copy and paste from the example applications!"
+msgid "Configuration is a very boring topic and an extremely tedious pastime. Unfortunately, several lines of XML are required to integrate Seam into your JSF implementation and servlet container. There's no need to be too put off by the following sections; you'll never need to type any of this stuff yourself, since you can just use seam-gen to start your application or you can copy and paste from the example applications!"
msgstr ""
#. Tag: title
#: Configuration.xml:12
#, no-c-format
msgid "Basic Seam configuration"
-msgstr ""
+msgstr "Configurazione base di Seam"
#. Tag: para
#: Configuration.xml:14
#, no-c-format
-msgid ""
-"First, let's look at the basic configuration that is needed whenever we use "
-"Seam with JSF."
+msgid "First, let's look at the basic configuration that is needed whenever we use Seam with JSF."
msgstr ""
#. Tag: title
@@ -72,6 +64,16 @@
" <url-pattern>*.seam</url-pattern>\n"
"</servlet-mapping>]]>"
msgstr ""
+"<![CDATA[<servlet>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>\n"
+" <load-on-startup>1</load-on-startup>\n"
+"</servlet>\n"
+"\n"
+"<servlet-mapping>\n"
+" <servlet-name>Faces Servlet</servlet-name>\n"
+" <url-pattern>*.seam</url-pattern>\n"
+"</servlet-mapping>]]>"
#. Tag: para
#: Configuration.xml:23
@@ -82,9 +84,7 @@
#. Tag: para
#: Configuration.xml:25
#, no-c-format
-msgid ""
-"In addition, Seam requires the following entry in your <literal>web.xml</"
-"literal> file:"
+msgid "In addition, Seam requires the following entry in your <literal>web.xml</literal> file:"
msgstr ""
#. Tag: programlisting
@@ -95,24 +95,20 @@
" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
"</listener>]]>"
msgstr ""
+"<![CDATA[<listener>\n"
+" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
+"</listener>]]>"
#. Tag: para
#: Configuration.xml:29
#, no-c-format
-msgid ""
-"This listener is responsible for bootstrapping Seam, and for destroying "
-"session and application contexts."
+msgid "This listener is responsible for bootstrapping Seam, and for destroying session and application contexts."
msgstr ""
#. Tag: para
#: Configuration.xml:32
#, no-c-format
-msgid ""
-"Some JSF implementations have a broken implementation of server-side state "
-"saving that interferes with Seam's conversation propagation. If you have "
-"problems with conversation propagation during form submissions, try "
-"switching to client-side state saving. You'll need this in <literal>web.xml</"
-"literal>:"
+msgid "Some JSF implementations have a broken implementation of server-side state saving that interferes with Seam's conversation propagation. If you have problems with conversation propagation during form submissions, try switching to client-side state saving. You'll need this in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -124,22 +120,15 @@
" <param-value>client</param-value>\n"
"</context-param>]]>"
msgstr ""
+"<![CDATA[<context-param>\n"
+" <param-name>javax.faces.STATE_SAVING_METHOD</param-name>\n"
+" <param-value>client</param-value>\n"
+"</context-param>]]>"
#. Tag: para
#: Configuration.xml:38
#, no-c-format
-msgid ""
-"There is a minor gray area in the JSF specification regarding the mutability "
-"of view state values. Since Seam uses the JSF view state to back its PAGE "
-"scope this can become an issue in some cases. If you're using server side "
-"state saving with the JSF-RI and you want a PAGE scoped bean to keep its "
-"exact value for a given view of a page you will need to specify the "
-"following context-param. Otherwise if a user uses the \"back\" button a PAGE "
-"scoped component will have the latest value if it has changed not the value "
-"of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public."
-"dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This "
-"setting is not enabled by default because of the performance hit of "
-"serializing the JSF view with every request."
+msgid "There is a minor gray area in the JSF specification regarding the mutability of view state values. Since Seam uses the JSF view state to back its PAGE scope this can become an issue in some cases. If you're using server side state saving with the JSF-RI and you want a PAGE scoped bean to keep its exact value for a given view of a page you will need to specify the following context-param. Otherwise if a user uses the \"back\" button a PAGE scoped component will have the latest value if it has changed not the value of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This setting is not enabled by default because of the performance hit of serializing the JSF view with every request."
msgstr ""
#. Tag: programlisting
@@ -151,6 +140,10 @@
" <param-value>true</param-value>\n"
"</context-param>]]>"
msgstr ""
+"<![CDATA[<context-param>\n"
+" <param-name>com.sun.faces.serializeServerState</param-name>\n"
+" <param-value>true</param-value>\n"
+"</context-param>]]>"
#. Tag: title
#: Configuration.xml:56
@@ -161,9 +154,7 @@
#. Tag: para
#: Configuration.xml:58
#, no-c-format
-msgid ""
-"If you want follow our advice and use Facelets instead of JSP, add the "
-"following lines to <literal>faces-config.xml</literal>:"
+msgid "If you want follow our advice and use Facelets instead of JSP, add the following lines to <literal>faces-config.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -174,6 +165,9 @@
" <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>\n"
"</application>]]>"
msgstr ""
+"<![CDATA[<application>\n"
+" <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>\n"
+"</application>]]>"
#. Tag: para
#: Configuration.xml:63
@@ -190,20 +184,15 @@
" <param-value>.xhtml</param-value>\n"
"</context-param>]]>"
msgstr ""
+"<![CDATA[<context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+"</context-param>]]>"
#. Tag: para
#: Configuration.xml:67
#, no-c-format
-msgid ""
-"If you are using facelets in JBoss AS, you'll find that Facelets logging is "
-"broken (the log messages don't make it to the server log). Seam provides a "
-"bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</"
-"literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/"
-"jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in "
-"the <literal>WEB-INF/lib</literal> of your application. The Facelets logging "
-"catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/"
-"nonav/docs/dev/docbook.html#config-logging\">Facelets Developer "
-"Documentation</ulink>."
+msgid "If you are using facelets in JBoss AS, you'll find that Facelets logging is broken (the log messages don't make it to the server log). Seam provides a bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/lib</literal> of your application. The Facelets logging catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/nonav/docs/dev/docbook.html#config-logging\">Facelets Developer Documentation</ulink>."
msgstr ""
#. Tag: title
@@ -215,10 +204,7 @@
#. Tag: para
#: Configuration.xml:83
#, no-c-format
-msgid ""
-"The Seam Resource Servlet provides resources used by Seam Remoting, captchas "
-"(see the security chapter) and some JSF UI controls. Configuring the Seam "
-"Resource Servlet requires the following entry in <literal>web.xml</literal>:"
+msgid "The Seam Resource Servlet provides resources used by Seam Remoting, captchas (see the security chapter) and some JSF UI controls. Configuring the Seam Resource Servlet requires the following entry in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -235,6 +221,15 @@
" <url-pattern>/seam/resource/*</url-pattern>\n"
"</servlet-mapping>]]>"
msgstr ""
+"<![CDATA[<servlet>\n"
+" <servlet-name>Seam Resource Servlet</servlet-name>\n"
+" <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>\n"
+"</servlet>\n"
+" \n"
+"<servlet-mapping>\n"
+" <servlet-name>Seam Resource Servlet</servlet-name>\n"
+" <url-pattern>/seam/resource/*</url-pattern>\n"
+"</servlet-mapping>]]>"
#. Tag: title
#: Configuration.xml:91
@@ -245,12 +240,7 @@
#. Tag: para
#: Configuration.xml:93
#, no-c-format
-msgid ""
-"Seam doesn't need any servlet filters for basic operation. However, there "
-"are several features which depend upon the use of filters. To make things "
-"easier, Seam lets you add and configure servlet filters just like you would "
-"configure other built-in Seam components. To take advantage of this feature, "
-"we must first install a master filter in <literal>web.xml</literal>:"
+msgid "Seam doesn't need any servlet filters for basic operation. However, there are several features which depend upon the use of filters. To make things easier, Seam lets you add and configure servlet filters just like you would configure other built-in Seam components. To take advantage of this feature, we must first install a master filter in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -267,40 +257,38 @@
" <url-pattern>/*</url-pattern>\n"
"</filter-mapping>]]>"
msgstr ""
+"<![CDATA[<filter>\n"
+" <filter-name>Seam Filter</filter-name>\n"
+" <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>\n"
+"</filter>\n"
+"\n"
+"<filter-mapping>\n"
+" <filter-name>Seam Filter</filter-name>\n"
+" <url-pattern>/*</url-pattern>\n"
+"</filter-mapping>]]>"
#. Tag: para
#: Configuration.xml:100
#, no-c-format
-msgid ""
-"The Seam master filter <emphasis>must</emphasis> be the first filter "
-"specified in <literal>web.xml</literal>. This ensures it is run first."
+msgid "The Seam master filter <emphasis>must</emphasis> be the first filter specified in <literal>web.xml</literal>. This ensures it is run first."
msgstr ""
#. Tag: para
#: Configuration.xml:103
#, no-c-format
-msgid ""
-"The Seam filters share a number of common attributes, you can set these in "
-"<literal>components.xml</literal> in addition to any parameters discussed "
-"below:"
+msgid "The Seam filters share a number of common attributes, you can set these in <literal>components.xml</literal> in addition to any parameters discussed below:"
msgstr ""
#. Tag: para
#: Configuration.xml:111
#, no-c-format
-msgid ""
-"<literal>url-pattern</literal> — Used to specify which requests are "
-"filtered, the default is all requests. <literal>url-pattern</literal> is a "
-"Tomcat style pattern which allows a wildcard suffix."
+msgid "<literal>url-pattern</literal> — Used to specify which requests are filtered, the default is all requests. <literal>url-pattern</literal> is a Tomcat style pattern which allows a wildcard suffix."
msgstr ""
#. Tag: para
#: Configuration.xml:118
#, no-c-format
-msgid ""
-"<literal>regex-url-pattern</literal> — Used to specify which requests "
-"are filtered, the default is all requests. <literal>regex-url-pattern</"
-"literal> is a true regular expression match for request path."
+msgid "<literal>regex-url-pattern</literal> — Used to specify which requests are filtered, the default is all requests. <literal>regex-url-pattern</literal> is a true regular expression match for request path."
msgstr ""
#. Tag: para
@@ -312,10 +300,7 @@
#. Tag: para
#: Configuration.xml:131
#, no-c-format
-msgid ""
-"Note that the patterns are matched against the URI path of the request (see "
-"<literal>HttpServletRequest.getURIPath()</literal>) and that the name of the "
-"servlet context is removed before matching."
+msgid "Note that the patterns are matched against the URI path of the request (see <literal>HttpServletRequest.getURIPath()</literal>) and that the name of the servlet context is removed before matching."
msgstr ""
#. Tag: para
@@ -333,24 +318,13 @@
#. Tag: para
#: Configuration.xml:141
#, no-c-format
-msgid ""
-"This filter provides the exception mapping functionality in <literal>pages."
-"xml</literal> (almost all applications will need this). It also takes care "
-"of rolling back uncommitted transactions when uncaught exceptions occur. "
-"(According to the Java EE specification, the web container should do this "
-"automatically, but we've found that this behavior cannot be relied upon in "
-"all application servers. And it is certainly not required of plain servlet "
-"engines like Tomcat.)"
+msgid "This filter provides the exception mapping functionality in <literal>pages.xml</literal> (almost all applications will need this). It also takes care of rolling back uncommitted transactions when uncaught exceptions occur. (According to the Java EE specification, the web container should do this automatically, but we've found that this behavior cannot be relied upon in all application servers. And it is certainly not required of plain servlet engines like Tomcat.)"
msgstr ""
#. Tag: para
#: Configuration.xml:147
#, no-c-format
-msgid ""
-"By default, the exception handling filter will process all requests, however "
-"this behavior may be adjusted by adding a <literal><web:exception-"
-"filter></literal> entry to <literal>components.xml</literal>, as shown in "
-"this example:"
+msgid "By default, the exception handling filter will process all requests, however this behavior may be adjusted by adding a <literal><web:exception-filter></literal> entry to <literal>components.xml</literal>, as shown in this example:"
msgstr ""
#. Tag: programlisting
@@ -364,6 +338,12 @@
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:web=\"http://jboss.com/products/seam/web\">\n"
+"\n"
+" <web:exception-filter url-pattern=\"*.seam\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: title
#: Configuration.xml:157
@@ -374,55 +354,43 @@
#. Tag: para
#: Configuration.xml:158
#, no-c-format
-msgid ""
-"This filter allows Seam to propagate the conversation context across browser "
-"redirects. It intercepts any browser redirects and adds a request parameter "
-"that specifies the Seam conversation identifier."
+msgid "This filter allows Seam to propagate the conversation context across browser redirects. It intercepts any browser redirects and adds a request parameter that specifies the Seam conversation identifier."
msgstr ""
#. Tag: para
#: Configuration.xml:162
#, no-c-format
-msgid ""
-"The redirect filter will process all requests by default, but this behavior "
-"can also be adjusted in <literal>components.xml</literal>:"
+msgid "The redirect filter will process all requests by default, but this behavior can also be adjusted in <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:165
#, no-c-format
msgid "<![CDATA[<web:redirect-filter url-pattern=\"*.seam\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<web:redirect-filter url-pattern=\"*.seam\"/>]]>"
#. Tag: title
#: Configuration.xml:170
#, no-c-format
msgid "URL rewriting"
-msgstr ""
+msgstr "Riscrittura dell'URL"
#. Tag: para
#: Configuration.xml:171
#, no-c-format
-msgid ""
-"This filter allows Seam to apply URL rewriting for views based on "
-"configuration in the <literal>pages.xml</literal> file. This filter is not "
-"activate by default, but can be activated by adding the configuration to "
-"<literal>components.xml</literal>:"
+msgid "This filter allows Seam to apply URL rewriting for views based on configuration in the <literal>pages.xml</literal> file. This filter is not activate by default, but can be activated by adding the configuration to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:176
#, no-c-format
msgid "<![CDATA[<web:rewrite-filter view-mapping=\"*.seam\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<web:rewrite-filter view-mapping=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:179
#, no-c-format
-msgid ""
-"The <literal>view-mapping</literal> parameter must match the servlet mapping "
-"defined for the Faces Servlet in the <literal>web.xml</literal> file. If "
-"ommitted, the rewrite filter assumes the pattern <literal>*.seam</literal>."
+msgid "The <literal>view-mapping</literal> parameter must match the servlet mapping defined for the Faces Servlet in the <literal>web.xml</literal> file. If ommitted, the rewrite filter assumes the pattern <literal>*.seam</literal>."
msgstr ""
#. Tag: title
@@ -434,11 +402,7 @@
#. Tag: para
#: Configuration.xml:187
#, no-c-format
-msgid ""
-"This feature is necessary when using the Seam file upload JSF control. It "
-"detects multipart form requests and processes them according to the "
-"multipart/form-data specification (RFC-2388). To override the default "
-"settings, add the following entry to <literal>components.xml</literal>:"
+msgid "This feature is necessary when using the Seam file upload JSF control. It detects multipart form requests and processes them according to the multipart/form-data specification (RFC-2388). To override the default settings, add the following entry to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -449,25 +413,20 @@
" max-request-size=\"1000000\" \n"
" url-pattern=\"*.seam\"/>]]>"
msgstr ""
+"<![CDATA[<web:multipart-filter create-temp-files=\"true\" \n"
+" max-request-size=\"1000000\" \n"
+" url-pattern=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:195
#, no-c-format
-msgid ""
-"<literal>create-temp-files</literal> — If set to <literal>true</"
-"literal>, uploaded files are written to a temporary file (instead of held in "
-"memory). This may be an important consideration if large file uploads are "
-"expected. The default setting is <literal>false</literal>."
+msgid "<literal>create-temp-files</literal> — If set to <literal>true</literal>, uploaded files are written to a temporary file (instead of held in memory). This may be an important consideration if large file uploads are expected. The default setting is <literal>false</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:202
#, no-c-format
-msgid ""
-"<literal>max-request-size</literal> — If the size of a file upload "
-"request (determined by reading the <literal>Content-Length</literal> header "
-"in the request) exceeds this value, the request will be aborted. The default "
-"setting is 0 (no size limit)."
+msgid "<literal>max-request-size</literal> — If the size of a file upload request (determined by reading the <literal>Content-Length</literal> header in the request) exceeds this value, the request will be aborted. The default setting is 0 (no size limit)."
msgstr ""
#. Tag: title
@@ -483,11 +442,10 @@
msgstr ""
#. Tag: para
-#: Configuration.xml:214 Configuration.xml:309
+#: Configuration.xml:214
+#: Configuration.xml:309
#, no-c-format
-msgid ""
-"This filter is not installed by default and requires an entry in "
-"<literal>components.xml</literal> to enable it:"
+msgid "This filter is not installed by default and requires an entry in <literal>components.xml</literal> to enable it:"
msgstr ""
#. Tag: programlisting
@@ -498,6 +456,9 @@
" override-client=\"true\" \n"
" url-pattern=\"*.seam\"/>]]>"
msgstr ""
+"<![CDATA[<web:character-encoding-filter encoding=\"UTF-16\" \n"
+" override-client=\"true\" \n"
+" url-pattern=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:221
@@ -508,46 +469,31 @@
#. Tag: para
#: Configuration.xml:225
#, no-c-format
-msgid ""
-"<literal>override-client</literal> — If this is set to <literal>true</"
-"literal>, the request encoding will be set to whatever is specified by "
-"<literal>encoding</literal> no matter whether the request already specifies "
-"an encoding or not. If set to <literal>false</literal>, the request encoding "
-"will only be set if the request doesn't already specify an encoding. The "
-"default setting is <literal>false</literal>."
+msgid "<literal>override-client</literal> — If this is set to <literal>true</literal>, the request encoding will be set to whatever is specified by <literal>encoding</literal> no matter whether the request already specifies an encoding or not. If set to <literal>false</literal>, the request encoding will only be set if the request doesn't already specify an encoding. The default setting is <literal>false</literal>."
msgstr ""
#. Tag: title
#: Configuration.xml:236
#, no-c-format
msgid "RichFaces"
-msgstr ""
+msgstr "RichFaces"
#. Tag: para
#: Configuration.xml:238
#, no-c-format
-msgid ""
-"If RichFaces is used in your project, Seam will install the RichFaces Ajax "
-"filter for you, making sure to install it before all other built-in filters. "
-"You don't need to install the RichFaces Ajax filter in <literal>web.xml</"
-"literal> yourself."
+msgid "If RichFaces is used in your project, Seam will install the RichFaces Ajax filter for you, making sure to install it before all other built-in filters. You don't need to install the RichFaces Ajax filter in <literal>web.xml</literal> yourself."
msgstr ""
#. Tag: para
#: Configuration.xml:246
#, no-c-format
-msgid ""
-"The RichFaces Ajax filter is only installed if the RichFaces jars are "
-"present in your project."
+msgid "The RichFaces Ajax filter is only installed if the RichFaces jars are present in your project."
msgstr ""
#. Tag: para
#: Configuration.xml:251
#, no-c-format
-msgid ""
-"To override the default settings, add the following entry to "
-"<literal>components.xml</literal>. The options are the same as those "
-"specified in the RichFaces Developer Guide:"
+msgid "To override the default settings, add the following entry to <literal>components.xml</literal>. The options are the same as those specified in the RichFaces Developer Guide:"
msgstr ""
#. Tag: programlisting
@@ -559,35 +505,27 @@
" log4j-init-file=\"custom-log4j.xml\"\n"
" url-pattern=\"*.seam\"/>]]>"
msgstr ""
+"<![CDATA[<web:ajax4jsf-filter force-parser=\"true\" \n"
+" enable-cache=\"true\" \n"
+" log4j-init-file=\"custom-log4j.xml\"\n"
+" url-pattern=\"*.seam\"/>]]>"
#. Tag: para
#: Configuration.xml:257
#, no-c-format
-msgid ""
-"<literal>force-parser</literal> — forces all JSF pages to be validated "
-"by Richfaces's XML syntax checker. If <literal>false</literal>, only AJAX "
-"responses are validated and converted to well-formed XML. Setting "
-"<literal>force-parser</literal> to <literal>false</literal> improves "
-"performance, but can provide visual artifacts on AJAX updates."
+msgid "<literal>force-parser</literal> — forces all JSF pages to be validated by Richfaces's XML syntax checker. If <literal>false</literal>, only AJAX responses are validated and converted to well-formed XML. Setting <literal>force-parser</literal> to <literal>false</literal> improves performance, but can provide visual artifacts on AJAX updates."
msgstr ""
#. Tag: para
#: Configuration.xml:265
#, no-c-format
-msgid ""
-"<literal>enable-cache</literal> — enables caching of framework-"
-"generated resources (e.g. javascript, CSS, images, etc). When developing "
-"custom javascript or CSS, setting to true prevents the browser from caching "
-"the resource."
+msgid "<literal>enable-cache</literal> — enables caching of framework-generated resources (e.g. javascript, CSS, images, etc). When developing custom javascript or CSS, setting to true prevents the browser from caching the resource."
msgstr ""
#. Tag: para
#: Configuration.xml:271
#, no-c-format
-msgid ""
-"<literal>log4j-init-file</literal> — is used to setup per-application "
-"logging. A path, relative to web application context, to the log4j.xml "
-"configuration file should be provided."
+msgid "<literal>log4j-init-file</literal> — is used to setup per-application logging. A path, relative to web application context, to the log4j.xml configuration file should be provided."
msgstr ""
#. Tag: title
@@ -599,20 +537,13 @@
#. Tag: para
#: Configuration.xml:283
#, no-c-format
-msgid ""
-"This filter adds the authenticated user name to the log4j mapped diagnostic "
-"context so that it can be included in formatted log output if desired, by "
-"adding %X{username} to the pattern."
+msgid "This filter adds the authenticated user name to the log4j mapped diagnostic context so that it can be included in formatted log output if desired, by adding %X{username} to the pattern."
msgstr ""
#. Tag: para
#: Configuration.xml:289
#, no-c-format
-msgid ""
-"By default, the logging filter will process all requests, however this "
-"behavior may be adjusted by adding a <literal><web:logging-filter></"
-"literal> entry to <literal>components.xml</literal>, as shown in this "
-"example:"
+msgid "By default, the logging filter will process all requests, however this behavior may be adjusted by adding a <literal><web:logging-filter></literal> entry to <literal>components.xml</literal>, as shown in this example:"
msgstr ""
#. Tag: programlisting
@@ -624,6 +555,10 @@
" <web:logging-filter url-pattern=\"*.seam\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:web=\"http://jboss.com/products/seam/web\">\n"
+" <web:logging-filter url-pattern=\"*.seam\"/>\n"
+"</components>]]>"
#. Tag: title
#: Configuration.xml:298
@@ -634,46 +569,31 @@
#. Tag: para
#: Configuration.xml:299
#, no-c-format
-msgid ""
-"Requests sent direct to some servlet other than the JSF servlet are not "
-"processed through the JSF lifecycle, so Seam provides a servlet filter that "
-"can be applied to any other servlet that needs access to Seam components."
+msgid "Requests sent direct to some servlet other than the JSF servlet are not processed through the JSF lifecycle, so Seam provides a servlet filter that can be applied to any other servlet that needs access to Seam components."
msgstr ""
#. Tag: para
#: Configuration.xml:303
#, no-c-format
-msgid ""
-"This filter allows custom servlets to interact with the Seam contexts. It "
-"sets up the Seam contexts at the beginning of each request, and tears them "
-"down at the end of the request. You should make sure that this filter is "
-"<emphasis>never</emphasis> applied to the JSF <literal>FacesServlet</"
-"literal>. Seam uses the phase listener for context management in a JSF "
-"request."
+msgid "This filter allows custom servlets to interact with the Seam contexts. It sets up the Seam contexts at the beginning of each request, and tears them down at the end of the request. You should make sure that this filter is <emphasis>never</emphasis> applied to the JSF <literal>FacesServlet</literal>. Seam uses the phase listener for context management in a JSF request."
msgstr ""
#. Tag: programlisting
#: Configuration.xml:312
#, no-c-format
msgid "<![CDATA[<web:context-filter url-pattern=\"/media/*\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<web:context-filter url-pattern=\"/media/*\"/>]]>"
#. Tag: para
#: Configuration.xml:314
#, no-c-format
-msgid ""
-"The context filter expects to find the conversation id of any conversation "
-"context in a request parameter named <literal>conversationId</literal>. You "
-"are responsible for ensuring that it gets sent in the request."
+msgid "The context filter expects to find the conversation id of any conversation context in a request parameter named <literal>conversationId</literal>. You are responsible for ensuring that it gets sent in the request."
msgstr ""
#. Tag: para
#: Configuration.xml:318
#, no-c-format
-msgid ""
-"You are also responsible for ensuring propagation of any new conversation id "
-"back to the client. Seam exposes the conversation id as a property of the "
-"built in component <literal>conversation</literal>."
+msgid "You are also responsible for ensuring propagation of any new conversation id back to the client. Seam exposes the conversation id as a property of the built in component <literal>conversation</literal>."
msgstr ""
#. Tag: title
@@ -685,13 +605,7 @@
#. Tag: para
#: Configuration.xml:327
#, no-c-format
-msgid ""
-"Seam can install your filters for you, allowing you to specify "
-"<emphasis>where</emphasis> in the chain your filter is placed (the servlet "
-"specification doesn't provide a well defined order if you specify your "
-"filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</"
-"literal> annotation to your Seam component (which must implement "
-"<literal>javax.servlet.Filter</literal>):"
+msgid "Seam can install your filters for you, allowing you to specify <emphasis>where</emphasis> in the chain your filter is placed (the servlet specification doesn't provide a well defined order if you specify your filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</literal> annotation to your Seam component (which must implement <literal>javax.servlet.Filter</literal>):"
msgstr ""
#. Tag: programlisting
@@ -705,16 +619,17 @@
"@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")\n"
"public class MultipartFilter extends AbstractFilter {]]>"
msgstr ""
+"<![CDATA[@Startup\n"
+"@Scope(APPLICATION)\n"
+"@Name(\"org.jboss.seam.web.multipartFilter\")\n"
+"@BypassInterceptors\n"
+"@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")\n"
+"public class MultipartFilter extends AbstractFilter {]]>"
#. Tag: para
#: Configuration.xml:334
#, no-c-format
-msgid ""
-"Adding the <literal>@Startup</literal> annotation means thar the component "
-"is available during Seam startup; bijection isn't available here "
-"(<literal>@BypassInterceptors</literal>); and the filter should be further "
-"down the chain than the RichFaces filter (<literal>@Filter(within=\"org."
-"jboss.seam.web.ajax4jsfFilter\")</literal>)."
+msgid "Adding the <literal>@Startup</literal> annotation means thar the component is available during Seam startup; bijection isn't available here (<literal>@BypassInterceptors</literal>); and the filter should be further down the chain than the RichFaces filter (<literal>@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")</literal>)."
msgstr ""
#. Tag: title
@@ -726,24 +641,13 @@
#. Tag: para
#: Configuration.xml:345
#, no-c-format
-msgid ""
-"In a Seam application, EJB components have a certain duality, as they are "
-"managed by both the EJB container and Seam. Actually, it's more that Seam "
-"resolves EJB component references, manages the lifetime of stateful session "
-"bean components, and also participates in each method call via interceptors. "
-"Let's start with the configuration of the Seam interceptor chain."
+msgid "In a Seam application, EJB components have a certain duality, as they are managed by both the EJB container and Seam. Actually, it's more that Seam resolves EJB component references, manages the lifetime of stateful session bean components, and also participates in each method call via interceptors. Let's start with the configuration of the Seam interceptor chain."
msgstr ""
#. Tag: para
#: Configuration.xml:350
#, no-c-format
-msgid ""
-"We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB "
-"components. This interceptor delegates to a set of built-in server-side "
-"interceptors that handle such concerns as bijection, conversation "
-"demarcation, and business process signals. The simplest way to do this "
-"across an entire application is to add the following interceptor "
-"configuration in <literal>ejb-jar.xml</literal>:"
+msgid "We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB components. This interceptor delegates to a set of built-in server-side interceptors that handle such concerns as bijection, conversation demarcation, and business process signals. The simplest way to do this across an entire application is to add the following interceptor configuration in <literal>ejb-jar.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -752,33 +656,36 @@
msgid ""
"<![CDATA[<interceptors>\n"
" <interceptor>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
-"class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
" </interceptor>\n"
"</interceptors>\n"
" \n"
"<assembly-descriptor>\n"
" <interceptor-binding>\n"
" <ejb-name>*</ejb-name>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
-"class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
" </interceptor-binding>\n"
"</assembly-descriptor>\n"
"]]>"
msgstr ""
+"<![CDATA[<interceptors>\n"
+" <interceptor>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" </interceptor>\n"
+"</interceptors>\n"
+" \n"
+"<assembly-descriptor>\n"
+" <interceptor-binding>\n"
+" <ejb-name>*</ejb-name>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" </interceptor-binding>\n"
+"</assembly-descriptor>\n"
+"]]>"
#. Tag: para
#: Configuration.xml:357
#, no-c-format
-msgid ""
-"Seam needs to know where to go to find session beans in JNDI. One way to do "
-"this is specify the <literal>@JndiName</literal> annotation on every session "
-"bean Seam component. However, this is quite tedious. A better approach is to "
-"specify a pattern that Seam can use to calculate the JNDI name from the EJB "
-"name. Unfortunately, there is no standard mapping to global JNDI defined in "
-"the EJB3 specification, so this mapping is vendor-specific (and may depend "
-"on your own naming conventions as well). We usually specify this option in "
-"<literal>components.xml</literal>."
+msgid "Seam needs to know where to go to find session beans in JNDI. One way to do this is specify the <literal>@JndiName</literal> annotation on every session bean Seam component. However, this is quite tedious. A better approach is to specify a pattern that Seam can use to calculate the JNDI name from the EJB name. Unfortunately, there is no standard mapping to global JNDI defined in the EJB3 specification, so this mapping is vendor-specific (and may depend on your own naming conventions as well). We usually specify this option in <literal>components.xml</literal>."
msgstr ""
#. Tag: para
@@ -791,66 +698,48 @@
#: Configuration.xml:366
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"earName/#{ejbName}/local\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<core:init jndi-name=\"earName/#{ejbName}/local\" />]]>"
#. Tag: para
#: Configuration.xml:368
#, no-c-format
-msgid ""
-"In this case, <literal>earName</literal> is the name of the EAR in which the "
-"bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name "
-"of the EJB, and the final segment represents the type of interface (local or "
-"remote)."
+msgid "In this case, <literal>earName</literal> is the name of the EAR in which the bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name of the EJB, and the final segment represents the type of interface (local or remote)."
msgstr ""
#. Tag: para
#: Configuration.xml:372
#, no-c-format
-msgid ""
-"Outside the context of an EAR (when using the JBoss Embeddable EJB3 "
-"container), the first segment is dropped since there is no EAR, leaving us "
-"with the following pattern:"
+msgid "Outside the context of an EAR (when using the JBoss Embeddable EJB3 container), the first segment is dropped since there is no EAR, leaving us with the following pattern:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:375
#, no-c-format
msgid "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<core:init jndi-name=\"#{ejbName}/local\" />]]>"
#. Tag: para
#: Configuration.xml:377
#, no-c-format
-msgid ""
-"How these JNDI names are resolved and somehow locate an EJB component might "
-"appear a bit like black magic at this point, so let's dig into the details. "
-"First, let's talk about how the EJB components get into JNDI."
+msgid "How these JNDI names are resolved and somehow locate an EJB component might appear a bit like black magic at this point, so let's dig into the details. First, let's talk about how the EJB components get into JNDI."
msgstr ""
#. Tag: para
#: Configuration.xml:381
#, no-c-format
-msgid ""
-"The folks at JBoss don't care much for XML, if you can't tell. So when they "
-"designed JBoss AS, they decided that EJB components would get assigned a "
-"global JNDI name automatically, using the pattern just described (i.e., EAR "
-"name/EJB name/interface type). The EJB name is the first non-empty value "
-"from the following list:"
+msgid "The folks at JBoss don't care much for XML, if you can't tell. So when they designed JBoss AS, they decided that EJB components would get assigned a global JNDI name automatically, using the pattern just described (i.e., EAR name/EJB name/interface type). The EJB name is the first non-empty value from the following list:"
msgstr ""
#. Tag: para
#: Configuration.xml:387
#, no-c-format
-msgid ""
-"The value of the <literal><ejb-name></literal> element in ejb-jar.xml"
+msgid "The value of the <literal><ejb-name></literal> element in ejb-jar.xml"
msgstr ""
#. Tag: para
#: Configuration.xml:390
#, no-c-format
-msgid ""
-"The value of the <literal>name</literal> attribute in the @Stateless or "
-"@Stateful annotation"
+msgid "The value of the <literal>name</literal> attribute in the @Stateless or @Stateful annotation"
msgstr ""
#. Tag: para
@@ -862,9 +751,7 @@
#. Tag: para
#: Configuration.xml:397
#, no-c-format
-msgid ""
-"Let's look at an example. Assume that you have the following EJB bean and "
-"interface defined."
+msgid "Let's look at an example. Assume that you have the following EJB bean and interface defined."
msgstr ""
#. Tag: programlisting
@@ -893,40 +780,44 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[package com.example.myapp;\n"
+"\n"
+"import javax.ejb.Local;\n"
+"\n"
+"@Local\n"
+"public class Authenticator\n"
+"{\n"
+" boolean authenticate();\n"
+"}\n"
+"\n"
+"package com.example.myapp;\n"
+"\n"
+"import javax.ejb.Stateless;\n"
+"\n"
+"@Stateless\n"
+"@Name(\"authenticator\")\n"
+"public class AuthenticatorBean implements Authenticator\n"
+"{ \n"
+" public boolean authenticate() { ... }\n"
+"}\n"
+"]]>"
#. Tag: para
#: Configuration.xml:401
#, no-c-format
-msgid ""
-"Assuming your EJB bean class is deployed in an EAR named myapp, the global "
-"JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. "
-"As you learned, you can reference this EJB component as a Seam component "
-"with the name <literal>authenticator</literal> and Seam will take care of "
-"finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</"
-"literal> annotation)."
+msgid "Assuming your EJB bean class is deployed in an EAR named myapp, the global JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. As you learned, you can reference this EJB component as a Seam component with the name <literal>authenticator</literal> and Seam will take care of finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</literal> annotation)."
msgstr ""
#. Tag: para
#: Configuration.xml:407
#, no-c-format
-msgid ""
-"So what about the rest of the application servers? Well, according to the "
-"Java EE spec, which most vendors try to adhere to religiously, you have to "
-"declare an EJB reference for your EJB in order for it to be assigned a JNDI "
-"name. That requires some XML. It also means that it is up to you to "
-"establish a JNDI naming convention so that you can leverage the Seam JNDI "
-"pattern. You might find the JBoss convention a good one to follow."
+msgid "So what about the rest of the application servers? Well, according to the Java EE spec, which most vendors try to adhere to religiously, you have to declare an EJB reference for your EJB in order for it to be assigned a JNDI name. That requires some XML. It also means that it is up to you to establish a JNDI naming convention so that you can leverage the Seam JNDI pattern. You might find the JBoss convention a good one to follow."
msgstr ""
#. Tag: para
#: Configuration.xml:413
#, no-c-format
-msgid ""
-"There are two places you have to define the EJB reference when using Seam on "
-"non-JBoss application servers. If you are going to be looking up the Seam "
-"EJB component through JSF (in a JSF view or as a JSF action listener) or a "
-"Seam JavaBean component, then you must declare the EJB reference in web.xml. "
-"Here is the EJB reference for the example component just shown:"
+msgid "There are two places you have to define the EJB reference when using Seam on non-JBoss application servers. If you are going to be looking up the Seam EJB component through JSF (in a JSF view or as a JSF action listener) or a Seam JavaBean component, then you must declare the EJB reference in web.xml. Here is the EJB reference for the example component just shown:"
msgstr ""
#. Tag: programlisting
@@ -940,40 +831,29 @@
"</ejb-local-ref>\n"
"]]>"
msgstr ""
+"<![CDATA[<ejb-local-ref>\n"
+" <ejb-ref-name>myapp/AuthenticatorBean/local</ejb-ref-name>\n"
+" <ejb-ref-type>Session</ejb-ref-type>\n"
+" <local>org.example.vehicles.action.Authenticator</local>\n"
+"</ejb-local-ref>\n"
+"]]>"
#. Tag: para
#: Configuration.xml:420
#, no-c-format
-msgid ""
-"This reference will cover most uses of the component in a Seam application. "
-"However, if you want to be able to inject a Seam EJB component into another "
-"Seam EJB component using <literal>@In</literal>, you need to define this EJB "
-"reference in another location. This time, it must be defined in ejb-jar.xml, "
-"and it's a bit tricker."
+msgid "This reference will cover most uses of the component in a Seam application. However, if you want to be able to inject a Seam EJB component into another Seam EJB component using <literal>@In</literal>, you need to define this EJB reference in another location. This time, it must be defined in ejb-jar.xml, and it's a bit tricker."
msgstr ""
#. Tag: para
#: Configuration.xml:425
#, no-c-format
-msgid ""
-"Within the context of an EJB method call, you have to deal with a somewhat "
-"sheltered JNDI context. When Seam attempts to find another Seam EJB "
-"component to satisfy an injection point defined using <literal>@In</"
-"literal>, it isn't going to be successful looking up the component in JNDI. "
-"You cannot simply resolve JNDI names as you please. You have to define those "
-"references explicitly. Unlike with the web context, however, you cannot "
-"declare EJB references globally for all EJB components. Instead, you have to "
-"specify the JNDI resources for a given EJB component one-by-one (this "
-"applies to JBoss AS 5 in addition to non-JBoss application servers)."
+msgid "Within the context of an EJB method call, you have to deal with a somewhat sheltered JNDI context. When Seam attempts to find another Seam EJB component to satisfy an injection point defined using <literal>@In</literal>, it isn't going to be successful looking up the component in JNDI. You cannot simply resolve JNDI names as you please. You have to define those references explicitly. Unlike with the web context, however, you cannot declare EJB references globally for all EJB components. Instead, you have to specify the JNDI resources for a given EJB component one-by-one (this applies to JBoss AS 5 in addition to non-JBoss application servers)."
msgstr ""
#. Tag: para
#: Configuration.xml:433
#, no-c-format
-msgid ""
-"Let's assume that we have an EJB named RegisterAction (the name is resolved "
-"using the three steps mentioned previously). That EJB has the following Seam "
-"injection:"
+msgid "Let's assume that we have an EJB named RegisterAction (the name is resolved using the three steps mentioned previously). That EJB has the following Seam injection:"
msgstr ""
#. Tag: programlisting
@@ -984,13 +864,14 @@
"Authenticator authenticator;\n"
"]]>"
msgstr ""
+"<![CDATA[@In(create = true)\n"
+"Authenticator authenticator;\n"
+"]]>"
#. Tag: para
#: Configuration.xml:438
#, no-c-format
-msgid ""
-"In order for this injection to work, the link must be established in the ejb-"
-"jar.xml file as follows:"
+msgid "In order for this injection to work, the link must be established in the ejb-jar.xml file as follows:"
msgstr ""
#. Tag: programlisting
@@ -1002,8 +883,7 @@
" <session>\n"
" <ejb-name>RegisterAction</ejb-name>\n"
" <ejb-local-ref>\n"
-" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-"
-"name>\n"
+" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n"
" <ejb-ref-type>Session</ejb-ref-type>\n"
" <local>com.example.myapp.Authenticator</local>\n"
" </ejb-local-ref>\n"
@@ -1015,122 +895,87 @@
"</ejb-jar>\n"
"]]>"
msgstr ""
+"<![CDATA[<ejb-jar>\n"
+" <enterprise-beans>\n"
+" <session>\n"
+" <ejb-name>RegisterAction</ejb-name>\n"
+" <ejb-local-ref>\n"
+" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n"
+" <ejb-ref-type>Session</ejb-ref-type>\n"
+" <local>com.example.myapp.Authenticator</local>\n"
+" </ejb-local-ref>\n"
+" </session>\n"
+" </enterprise-beans>\n"
+"\n"
+" ...\n"
+" \n"
+"</ejb-jar>\n"
+"]]>"
#. Tag: para
#: Configuration.xml:442
#, no-c-format
-msgid ""
-"Notice that the contents of the <literal><ejb-local-ref></literal> are "
-"identical to what we defined in web.xml. What we are doing is bringing the "
-"reference into the EJB context where it can be used by the RegisterAction "
-"bean. You will need to add one of these references for any injection of a "
-"Seam EJB compoenent into another Seam EJB component using <literal>@In</"
-"literal>. (You can see an example of this setup in the jee5/booking example)."
+msgid "Notice that the contents of the <literal><ejb-local-ref></literal> are identical to what we defined in web.xml. What we are doing is bringing the reference into the EJB context where it can be used by the RegisterAction bean. You will need to add one of these references for any injection of a Seam EJB compoenent into another Seam EJB component using <literal>@In</literal>. (You can see an example of this setup in the jee5/booking example)."
msgstr ""
#. Tag: para
#: Configuration.xml:448
#, no-c-format
-msgid ""
-"But what about <literal>@EJB</literal>? It's true that you can inject one "
-"EJB into another using <literal>@EJB</literal>. However, by doing so, you "
-"are injecting the actual EJB reference rather than the Seam EJB component "
-"instance. In this case, some Seam features will work, while others won't. "
-"That's because Seam's interceptor is invoked on any method call to an EJB "
-"component. But that only invokes Seam's server-side interceptor chain. What "
-"you lose is Seam's state management and Seam's client-side interceptor "
-"chain. Client-side interceptors handle concerns such as security and "
-"concurrency. Also, when injecting a SFSB, there is no guarantee that you "
-"will get the SFSB bound to the active session or conversation, whatever the "
-"case may be. Thus, you definitely want to inject the Seam EJB component "
-"using <literal>@In</literal>."
+msgid "But what about <literal>@EJB</literal>? It's true that you can inject one EJB into another using <literal>@EJB</literal>. However, by doing so, you are injecting the actual EJB reference rather than the Seam EJB component instance. In this case, some Seam features will work, while others won't. That's because Seam's interceptor is invoked on any method call to an EJB component. But that only invokes Seam's server-side interceptor chain. What you lose is Seam's state management and Seam's client-side interceptor chain. Client-side interceptors handle concerns such as security and concurrency. Also, when injecting a SFSB, there is no guarantee that you will get the SFSB bound to the active session or conversation, whatever the case may be. Thus, you definitely want to inject the Seam EJB component using <literal>@In</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:458
#, no-c-format
-msgid ""
-"That covers how JNDI names are defined and used. The lesson is that with "
-"some application servers, such as GlassFish, you are going to have to "
-"specify JNDI names for all EJB components explicitly, and sometimes twice! "
-"And even if you are following the same naming convention as JBoss AS, the "
-"JNDI pattern in Seam may need to be altered. For instance, the global JNDI "
-"names are automatically prefixed with java:comp/env on GlassFish, so you "
-"need to define the JNDI pattern as follows:"
+msgid "That covers how JNDI names are defined and used. The lesson is that with some application servers, such as GlassFish, you are going to have to specify JNDI names for all EJB components explicitly, and sometimes twice! And even if you are following the same naming convention as JBoss AS, the JNDI pattern in Seam may need to be altered. For instance, the global JNDI names are automatically prefixed with java:comp/env on GlassFish, so you need to define the JNDI pattern as follows:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:464
#, no-c-format
-msgid ""
-"<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]"
-">"
-msgstr ""
+msgid "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>"
+msgstr "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>"
#. Tag: para
#: Configuration.xml:466
#, no-c-format
-msgid ""
-"Finally, let's talk about transactions. In an EJB3 environment, we recommend "
-"the use of a special built-in component for transaction management, that is "
-"fully aware of container transactions, and can correctly process transaction "
-"success events registered with the <literal>Events</literal> component. If "
-"you don't add this line to your <literal>components.xml</literal> file, Seam "
-"won't know when container-managed transactions end:"
+msgid "Finally, let's talk about transactions. In an EJB3 environment, we recommend the use of a special built-in component for transaction management, that is fully aware of container transactions, and can correctly process transaction success events registered with the <literal>Events</literal> component. If you don't add this line to your <literal>components.xml</literal> file, Seam won't know when container-managed transactions end:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:473
#, no-c-format
msgid "<![CDATA[<transaction:ejb-transaction/>]]>"
-msgstr ""
+msgstr "<![CDATA[<transaction:ejb-transaction/>]]>"
#. Tag: title
#: Configuration.xml:478
#, no-c-format
msgid "Don't forget!"
-msgstr ""
+msgstr "Non dimenticare!"
#. Tag: para
#: Configuration.xml:480
#, no-c-format
-msgid ""
-"There is one final item you need to know about. You must place a "
-"<literal>seam.properties</literal>, <literal>META-INF/seam.properties</"
-"literal> or <literal>META-INF/components.xml</literal> file in any archive "
-"in which your Seam components are deployed (even an empty properties file "
-"will do). At startup, Seam will scan any archives with <literal>seam."
-"properties</literal> files for seam components."
+msgid "There is one final item you need to know about. You must place a <literal>seam.properties</literal>, <literal>META-INF/seam.properties</literal> or <literal>META-INF/components.xml</literal> file in any archive in which your Seam components are deployed (even an empty properties file will do). At startup, Seam will scan any archives with <literal>seam.properties</literal> files for seam components."
msgstr ""
#. Tag: para
#: Configuration.xml:485
#, no-c-format
-msgid ""
-"In a web archive (WAR) file, you must place a <literal>seam.properties</"
-"literal> file in the <literal>WEB-INF/classes</literal> directory if you "
-"have any Seam components included here."
+msgid "In a web archive (WAR) file, you must place a <literal>seam.properties</literal> file in the <literal>WEB-INF/classes</literal> directory if you have any Seam components included here."
msgstr ""
#. Tag: para
#: Configuration.xml:488
#, no-c-format
-msgid ""
-"That's why all the Seam examples have an empty <literal>seam.properties</"
-"literal> file. You can't just delete this file and expect everything to "
-"still work!"
+msgid "That's why all the Seam examples have an empty <literal>seam.properties</literal> file. You can't just delete this file and expect everything to still work!"
msgstr ""
#. Tag: para
#: Configuration.xml:491
#, no-c-format
-msgid ""
-"You might think this is silly and what kind of idiot framework designers "
-"would make an empty file affect the behavior of their software?? Well, this "
-"is a workaround for a limitation of the JVM—if we didn't use this "
-"mechanism, our next best option would be to force you to list every "
-"component explicitly in <literal>components.xml</literal>, just like some "
-"other competing frameworks do! I think you'll like our way better."
+msgid "You might think this is silly and what kind of idiot framework designers would make an empty file affect the behavior of their software?? Well, this is a workaround for a limitation of the JVM—if we didn't use this mechanism, our next best option would be to force you to list every component explicitly in <literal>components.xml</literal>, just like some other competing frameworks do! I think you'll like our way better."
msgstr ""
#. Tag: title
@@ -1142,85 +987,69 @@
#. Tag: para
#: Configuration.xml:504
#, no-c-format
-msgid ""
-"Seam comes packaged and configured with Hibernate as the default JPA "
-"provider. If you require using a different JPA provider you must tell "
-"<literal>seam</literal> about it."
+msgid "Seam comes packaged and configured with Hibernate as the default JPA provider. If you require using a different JPA provider you must tell <literal>seam</literal> about it."
msgstr ""
#. Tag: title
#: Configuration.xml:510
#, no-c-format
msgid "This is a workaround"
-msgstr ""
+msgstr "Questo è un workaround"
#. Tag: para
#: Configuration.xml:511
#, no-c-format
-msgid ""
-"Configuration of the JPA provider will be easier in the future and will not "
-"require configuration changes, unless you are adding a custom persistence "
-"provider implementation."
+msgid "Configuration of the JPA provider will be easier in the future and will not require configuration changes, unless you are adding a custom persistence provider implementation."
msgstr ""
#. Tag: para
#: Configuration.xml:518
#, no-c-format
-msgid ""
-"Telling seam about a different JPA provider can be be done in one of two "
-"ways:"
+msgid "Telling seam about a different JPA provider can be be done in one of two ways:"
msgstr ""
#. Tag: para
#: Configuration.xml:519
#, no-c-format
-msgid ""
-"Update your application's <literal>components.xml</literal> so that the "
-"generic <literal>PersistenceProvider</literal> takes precedence over the "
-"hibernate version. Simply add the following to the file:"
+msgid "Update your application's <literal>components.xml</literal> so that the generic <literal>PersistenceProvider</literal> takes precedence over the hibernate version. Simply add the following to the file:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:524
#, no-c-format
msgid ""
-"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
-"\" \n"
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
" class=\"org.jboss.seam.persistence.PersistenceProvider\"\n"
" scope=\"stateless\">\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
+" class=\"org.jboss.seam.persistence.PersistenceProvider\"\n"
+" scope=\"stateless\">\n"
+"</component>]]>"
#. Tag: para
#: Configuration.xml:525
#, no-c-format
-msgid ""
-"If you want to take advantage of your JPA provider's non-standard features "
-"you will need to write you own implementation of the "
-"<literal>PersistenceProvider</literal>. Use "
-"<literal>HibernatePersistenceProvider</literal> as a starting point (don't "
-"forget to give back to the community :). Then you will need to tell "
-"<literal>seam</literal> to use it as before."
+msgid "If you want to take advantage of your JPA provider's non-standard features you will need to write you own implementation of the <literal>PersistenceProvider</literal>. Use <literal>HibernatePersistenceProvider</literal> as a starting point (don't forget to give back to the community :). Then you will need to tell <literal>seam</literal> to use it as before."
msgstr ""
#. Tag: programlisting
#: Configuration.xml:532
#, no-c-format
msgid ""
-"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
-"\" \n"
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
" class=\"org.your.package.YourPersistenceProvider\">\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
+" class=\"org.your.package.YourPersistenceProvider\">\n"
+"</component>]]>"
#. Tag: para
#: Configuration.xml:533
#, no-c-format
-msgid ""
-"All that is left is updating the <literal>persistence.xml</literal> file "
-"with the correct provider class, and what ever properties your provider "
-"needs. Don't forget to package your new provider's jar files in the "
-"application if they are needed."
+msgid "All that is left is updating the <literal>persistence.xml</literal> file with the correct provider class, and what ever properties your provider needs. Don't forget to package your new provider's jar files in the application if they are needed."
msgstr ""
#. Tag: title
@@ -1232,24 +1061,23 @@
#. Tag: para
#: Configuration.xml:552
#, no-c-format
-msgid ""
-"If you're running in a Java EE 5 environment, this is all the configuration "
-"required to start using Seam!"
+msgid "If you're running in a Java EE 5 environment, this is all the configuration required to start using Seam!"
msgstr ""
+# come tradurre?
#. Tag: title
-#: Configuration.xml:555 Configuration.xml:650 Configuration.xml:788
+#: Configuration.xml:555
+#: Configuration.xml:650
+#: Configuration.xml:788
#: Configuration.xml:821
#, no-c-format
msgid "Packaging"
-msgstr ""
+msgstr "Packaging"
#. Tag: para
#: Configuration.xml:557
#, no-c-format
-msgid ""
-"Once you've packaged all this stuff together into an EAR, the archive "
-"structure will look something like this:"
+msgid "Once you've packaged all this stuff together into an EAR, the archive structure will look something like this:"
msgstr ""
#. Tag: programlisting
@@ -1291,141 +1119,129 @@
" RegisterBean.class\n"
" ...]]>"
msgstr ""
+"<![CDATA[my-application.ear/\n"
+" jboss-seam.jar\n"
+" lib/\n"
+" jboss-el.jar\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" application.xml\n"
+" my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jsf-facelets.jar\n"
+" jboss-seam-ui.jar\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" persistence.xml\n"
+" seam.properties\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" LoginBean.class\n"
+" Register.class\n"
+" RegisterBean.class\n"
+" ...]]>"
#. Tag: para
#: Configuration.xml:562
#, no-c-format
-msgid ""
-"You should declare <literal>jboss-seam.jar</literal> as an ejb module in "
-"<literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> "
-"should be placed in the EAR's lib directory (putting it in the EAR classpath."
+msgid "You should declare <literal>jboss-seam.jar</literal> as an ejb module in <literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> should be placed in the EAR's lib directory (putting it in the EAR classpath."
msgstr ""
#. Tag: para
#: Configuration.xml:567
#, no-c-format
-msgid ""
-"If you want to use jBPM or Drools, you must include the needed jars in the "
-"EAR's lib directory."
+msgid "If you want to use jBPM or Drools, you must include the needed jars in the EAR's lib directory."
msgstr ""
#. Tag: para
#: Configuration.xml:569
#, no-c-format
-msgid ""
-"If you want to use facelets (our recommendation), you must include "
-"<literal>jsf-facelets.jar</literal> in the <literal>WEB-INF/lib</literal> "
-"directory of the WAR."
+msgid "If you want to use facelets (our recommendation), you must include <literal>jsf-facelets.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR."
msgstr ""
#. Tag: para
#: Configuration.xml:572
#, no-c-format
-msgid ""
-"If you want to use the Seam tag library (most Seam applications do), you "
-"must include <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/"
-"lib</literal> directory of the WAR. If you want to use the PDF or email tag "
-"libraries, you need to put <literal>jboss-seam-pdf.jar</literal> or "
-"<literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
+msgid "If you want to use the Seam tag library (most Seam applications do), you must include <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR. If you want to use the PDF or email tag libraries, you need to put <literal>jboss-seam-pdf.jar</literal> or <literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:577
#, no-c-format
-msgid ""
-"If you want to use the Seam debug page (only works for applications using "
-"facelets), you must include <literal>jboss-seam-debug.jar</literal> in the "
-"<literal>WEB-INF/lib</literal> directory of the WAR."
+msgid "If you want to use the Seam debug page (only works for applications using facelets), you must include <literal>jboss-seam-debug.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR."
msgstr ""
#. Tag: para
#: Configuration.xml:580
#, no-c-format
-msgid ""
-"Seam ships with several example applications that are deployable in any Java "
-"EE container that supports EJB 3.0."
+msgid "Seam ships with several example applications that are deployable in any Java EE container that supports EJB 3.0."
msgstr ""
#. Tag: para
#: Configuration.xml:583
#, no-c-format
-msgid ""
-"I really wish that was all there was to say on the topic of configuration "
-"but unfortunately we're only about a third of the way there. If you're too "
-"overwhelmed by all this tedious configuration stuff, feel free to skip over "
-"the rest of this section and come back to it later."
+msgid "I really wish that was all there was to say on the topic of configuration but unfortunately we're only about a third of the way there. If you're too overwhelmed by all this tedious configuration stuff, feel free to skip over the rest of this section and come back to it later."
msgstr ""
#. Tag: title
#: Configuration.xml:592
#, no-c-format
msgid "Configuring Seam in J2EE"
-msgstr ""
+msgstr "Configurare Seam in J2EE"
#. Tag: para
#: Configuration.xml:594
#, no-c-format
-msgid ""
-"Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. "
-"In this case you would use Hibernate3 or JPA instead of EJB 3.0 persistence, "
-"and plain JavaBeans instead of session beans. You'll miss out on some of the "
-"nice features of session beans but it will be very easy to migrate to EJB "
-"3.0 when you're ready and, in the meantime, you'll be able to take advantage "
-"of Seam's unique declarative state management architecture."
+msgid "Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. In this case you would use Hibernate3 or JPA instead of EJB 3.0 persistence, and plain JavaBeans instead of session beans. You'll miss out on some of the nice features of session beans but it will be very easy to migrate to EJB 3.0 when you're ready and, in the meantime, you'll be able to take advantage of Seam's unique declarative state management architecture."
msgstr ""
#. Tag: para
#: Configuration.xml:609
#, no-c-format
-msgid ""
-"Seam JavaBean components do not provide declarative transaction demarcation "
-"like session beans do. You <emphasis>could</emphasis> manage your "
-"transactions manually using the JTA <literal>UserTransaction</literal> or "
-"declaratively using Seam's <literal>@Transactional</literal> annotation. But "
-"most applications will just use Seam managed transactions when using "
-"Hibernate with JavaBeans."
+msgid "Seam JavaBean components do not provide declarative transaction demarcation like session beans do. You <emphasis>could</emphasis> manage your transactions manually using the JTA <literal>UserTransaction</literal> or declaratively using Seam's <literal>@Transactional</literal> annotation. But most applications will just use Seam managed transactions when using Hibernate with JavaBeans."
msgstr ""
#. Tag: para
#: Configuration.xml:615
#, no-c-format
-msgid ""
-"The Seam distribution includes a version of the booking example application "
-"that uses Hibernate3 and JavaBeans instead of EJB3, and another version that "
-"uses JPA and JavaBeans. These example applications are ready to deploy into "
-"any J2EE application server."
+msgid "The Seam distribution includes a version of the booking example application that uses Hibernate3 and JavaBeans instead of EJB3, and another version that uses JPA and JavaBeans. These example applications are ready to deploy into any J2EE application server."
msgstr ""
#. Tag: title
#: Configuration.xml:620
#, no-c-format
msgid "Boostrapping Hibernate in Seam"
-msgstr ""
+msgstr "Boostrapping di Hibernate in Seam"
#. Tag: para
#: Configuration.xml:622
#, no-c-format
-msgid ""
-"Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your "
-"<literal>hibernate.cfg.xml</literal> file if you install a built-in "
-"component:"
+msgid "Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your <literal>hibernate.cfg.xml</literal> file if you install a built-in component:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:625
#, no-c-format
-msgid ""
-"<![CDATA[<persistence:hibernate-session-factory name="
-"\"hibernateSessionFactory\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
+msgstr "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
#. Tag: para
#: Configuration.xml:627
#, no-c-format
-msgid ""
-"You will also need to configure a <emphasis>managed session</emphasis> if "
-"you want a Seam managed Hibernate <literal>Session</literal> to be available "
-"via injection."
+msgid "You will also need to configure a <emphasis>managed session</emphasis> if you want a Seam managed Hibernate <literal>Session</literal> to be available via injection."
msgstr ""
#. Tag: programlisting
@@ -1433,40 +1249,33 @@
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n"
-" session-factory=\"#{hibernateSessionFactory}\"/"
-">]]>"
+" session-factory=\"#{hibernateSessionFactory}\"/>]]>"
msgstr ""
+"<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n"
+" session-factory=\"#{hibernateSessionFactory}\"/>]]>"
#. Tag: title
#: Configuration.xml:635
#, no-c-format
msgid "Boostrapping JPA in Seam"
-msgstr ""
+msgstr "Boostrapping di JPA in Seam"
#. Tag: para
#: Configuration.xml:637
#, no-c-format
-msgid ""
-"Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your "
-"<literal>persistence.xml</literal> file if you install this built-in "
-"component:"
+msgid "Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your <literal>persistence.xml</literal> file if you install this built-in component:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:640
#, no-c-format
-msgid ""
-"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
+msgstr "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
#. Tag: para
#: Configuration.xml:642
#, no-c-format
-msgid ""
-"You will also need to configure a <emphasis>managed persistence context</"
-"emphasis> if you want a Seam managed JPA <literal>EntityManager</literal> to "
-"be available via injection."
+msgid "You will also need to configure a <emphasis>managed persistence context</emphasis> if you want a Seam managed JPA <literal>EntityManager</literal> to be available via injection."
msgstr ""
#. Tag: programlisting
@@ -1474,9 +1283,10 @@
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
-" entity-manager-factory=\"#{entityManagerFactory}"
-"\"/>]]>"
+" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
msgstr ""
+"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
+" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
#. Tag: para
#: Configuration.xml:652
@@ -1520,13 +1330,42 @@
" register.jsp\n"
" ...]]>"
msgstr ""
+"<![CDATA[my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jboss-seam.jar\n"
+" jboss-seam-ui.jar\n"
+" jboss-el.jar\n"
+" jsf-facelets.jar\n"
+" hibernate3.jar\n"
+" hibernate-annotations.jar\n"
+" hibernate-validator.jar\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" seam.properties\n"
+" hibernate.cfg.xml\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" Register.class\n"
+" ...\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...]]>"
#. Tag: para
#: Configuration.xml:656
#, no-c-format
-msgid ""
-"If we want to deploy Hibernate in a non-EE environment like Tomcat or "
-"TestNG, we need to do a little bit more work."
+msgid "If we want to deploy Hibernate in a non-EE environment like Tomcat or TestNG, we need to do a little bit more work."
msgstr ""
#. Tag: title
@@ -1538,34 +1377,26 @@
#. Tag: para
#: Configuration.xml:665
#, no-c-format
-msgid ""
-"It is possible to use Seam completely outside of an EE environment. In this "
-"case, you need to tell Seam how to manage transactions, since there will be "
-"no JTA available. If you're using JPA, you can tell Seam to use JPA resource-"
-"local transactions, ie. <literal>EntityTransaction</literal>, like so:"
+msgid "It is possible to use Seam completely outside of an EE environment. In this case, you need to tell Seam how to manage transactions, since there will be no JTA available. If you're using JPA, you can tell Seam to use JPA resource-local transactions, ie. <literal>EntityTransaction</literal>, like so:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:669
#, no-c-format
-msgid ""
-"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
+msgstr "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
#. Tag: para
#: Configuration.xml:671
#, no-c-format
-msgid ""
-"If you're using Hibernate, you can tell Seam to use the Hibernate "
-"transaction API like this:"
+msgid "If you're using Hibernate, you can tell Seam to use the Hibernate transaction API like this:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:673
#, no-c-format
msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
#. Tag: para
#: Configuration.xml:675
@@ -1576,8 +1407,7 @@
#. Tag: para
#: Configuration.xml:677
#, no-c-format
-msgid ""
-"A better alternative is to use JBoss Embedded to get access to the EE APIs."
+msgid "A better alternative is to use JBoss Embedded to get access to the EE APIs."
msgstr ""
#. Tag: title
@@ -1589,18 +1419,13 @@
#. Tag: para
#: Configuration.xml:684
#, no-c-format
-msgid ""
-"JBoss Embedded lets you run EJB3 components outside the context of the Java "
-"EE 5 application server. This is especially, but not only, useful for "
-"testing."
+msgid "JBoss Embedded lets you run EJB3 components outside the context of the Java EE 5 application server. This is especially, but not only, useful for testing."
msgstr ""
#. Tag: para
#: Configuration.xml:687
#, no-c-format
-msgid ""
-"The Seam booking example application includes a TestNG integration test "
-"suite that runs on JBoss Embedded via <literal>SeamTest</literal>."
+msgid "The Seam booking example application includes a TestNG integration test suite that runs on JBoss Embedded via <literal>SeamTest</literal>."
msgstr ""
#. Tag: para
@@ -1618,49 +1443,31 @@
#. Tag: para
#: Configuration.xml:714
#, no-c-format
-msgid ""
-"Embedded JBoss must by installed into Tomcat for Seam applications to run "
-"correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend="
-"\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be "
-"downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?"
-"group_id=22866&package_id=228977\">here</ulink>. The process for "
-"installing Embedded JBoss into Tomcat 6 is quite simple. First, you should "
-"copy the Embedded JBoss JARs and configuration files into Tomcat."
+msgid "Embedded JBoss must by installed into Tomcat for Seam applications to run correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend=\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=22866&package_i...">here</ulink>. The process for installing Embedded JBoss into Tomcat 6 is quite simple. First, you should copy the Embedded JBoss JARs and configuration files into Tomcat."
msgstr ""
#. Tag: para
#: Configuration.xml:728
#, no-c-format
-msgid ""
-"Copy all files and directories under the Embedded JBoss <literal>bootstrap</"
-"literal> and <literal>lib</literal> directories, except for the "
-"<literal>jndi.properties</literal> file, into the Tomcat <literal>lib</"
-"literal> directory."
+msgid "Copy all files and directories under the Embedded JBoss <literal>bootstrap</literal> and <literal>lib</literal> directories, except for the <literal>jndi.properties</literal> file, into the Tomcat <literal>lib</literal> directory."
msgstr ""
#. Tag: para
#: Configuration.xml:735
#, no-c-format
-msgid ""
-"Remove the <literal>annotations-api.jar</literal> file from the Tomcat "
-"<literal>lib</literal> directory."
+msgid "Remove the <literal>annotations-api.jar</literal> file from the Tomcat <literal>lib</literal> directory."
msgstr ""
#. Tag: para
#: Configuration.xml:741
#, no-c-format
-msgid ""
-"Next, two configuration files need to be updated to add Embedded JBoss-"
-"specific functionality."
+msgid "Next, two configuration files need to be updated to add Embedded JBoss-specific functionality."
msgstr ""
#. Tag: para
#: Configuration.xml:747
#, no-c-format
-msgid ""
-"Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</"
-"literal> to <literal>conf/server.xml</literal>. It must appear after all "
-"other listeners in the file:"
+msgid "Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</literal> to <literal>conf/server.xml</literal>. It must appear after all other listeners in the file:"
msgstr ""
#. Tag: programlisting
@@ -1669,33 +1476,36 @@
msgid ""
"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
"\n"
-" <!-- Comment these entries out to disable JMX MBeans support used for "
-"the \n"
+" <!-- Comment these entries out to disable JMX MBeans support used for the \n"
" administration web application -->\n"
" <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener"
-"\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans."
-"GlobalResourcesLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.storeconfig."
-"StoreConfigLifecycleListener\" />]]>"
+" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>"
msgstr ""
+"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
+"\n"
+" <!-- Comment these entries out to disable JMX MBeans support used for the \n"
+" administration web application -->\n"
+" <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>"
#. Tag: programlisting
#: Configuration.xml:751
#, no-c-format
msgid ""
"<![CDATA[ <!-- Add this listener -->\n"
-" <Listener className=\"org.jboss.embedded.tomcat."
-"EmbeddedJBossBootstrapListener\" />]]>"
+" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>"
msgstr ""
+"<![CDATA[ <!-- Add this listener -->\n"
+" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>"
#. Tag: para
#: Configuration.xml:755
#, no-c-format
-msgid ""
-"WAR file scanning should be enabled by adding the <literal>WebinfScanner</"
-"literal> listener to <literal>conf/context.xml</literal>:"
+msgid "WAR file scanning should be enabled by adding the <literal>WebinfScanner</literal> listener to <literal>conf/context.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1706,12 +1516,19 @@
" <!-- Default set of monitored resources -->\n"
" <WatchedResource>WEB-INF/web.xml</WatchedResource>\n"
" \n"
-" <!-- Uncomment this to disable session persistence across Tomcat "
-"restarts -->\n"
+" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n"
" <!--\n"
" <Manager pathname=\"\" />\n"
" -->]]>"
msgstr ""
+"<![CDATA[<Context>\n"
+" <!-- Default set of monitored resources -->\n"
+" <WatchedResource>WEB-INF/web.xml</WatchedResource>\n"
+" \n"
+" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n"
+" <!--\n"
+" <Manager pathname=\"\" />\n"
+" -->]]>"
#. Tag: programlisting
#: Configuration.xml:759
@@ -1720,40 +1537,32 @@
"<![CDATA[ <!-- Add this listener -->\n"
" <Listener className=\"org.jboss.embedded.tomcat.WebinfScanner\" />]]>"
msgstr ""
+"<![CDATA[ <!-- Add this listener -->\n"
+" <Listener className=\"org.jboss.embedded.tomcat.WebinfScanner\" />]]>"
#. Tag: programlisting
#: Configuration.xml:760
#, no-c-format
msgid "<![CDATA[</Context>]]>"
-msgstr ""
+msgstr "<![CDATA[</Context>]]>"
#. Tag: para
#: Configuration.xml:764
#, no-c-format
-msgid ""
-"If you are using Sun JDK 6, you need to set the Java option <literal>sun."
-"lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in "
-"the JAVA_OPTS environment variable used by the Catalina startup script "
-"(catalina.bat on Windows or catalina.sh on Unix)."
+msgid "If you are using Sun JDK 6, you need to set the Java option <literal>sun.lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in the JAVA_OPTS environment variable used by the Catalina startup script (catalina.bat on Windows or catalina.sh on Unix)."
msgstr ""
#. Tag: para
#: Configuration.xml:769
#, no-c-format
-msgid ""
-"Open the script appropriate for your operating system in a text editor. Add "
-"a new line immediately below the comments at the top of the file where you "
-"will define the JAVA_OPTS environment variable. On Windows, use the "
-"following syntax:"
+msgid "Open the script appropriate for your operating system in a text editor. Add a new line immediately below the comments at the top of the file where you will define the JAVA_OPTS environment variable. On Windows, use the following syntax:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:773
#, no-c-format
-msgid ""
-"<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader."
-"allowArraySyntax=true]]>"
-msgstr ""
+msgid "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>"
+msgstr "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>"
#. Tag: para
#: Configuration.xml:775
@@ -1764,26 +1573,19 @@
#. Tag: programlisting
#: Configuration.xml:777
#, no-c-format
-msgid ""
-"<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true"
-"\"]]>"
-msgstr ""
+msgid "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>"
+msgstr "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>"
#. Tag: para
#: Configuration.xml:782
#, no-c-format
-msgid ""
-"For more configuration options, please see the Embedded JBoss Tomcat "
-"integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
-"page=EmbeddedAndTomcat\">wiki entry</ulink>."
+msgid "For more configuration options, please see the Embedded JBoss Tomcat integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat\">wiki entry</ulink>."
msgstr ""
#. Tag: para
#: Configuration.xml:790
#, no-c-format
-msgid ""
-"The archive structure of a WAR-based deployment on an servlet engine like "
-"Tomcat will look something like this:"
+msgid "The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something like this:"
msgstr ""
#. Tag: programlisting
@@ -1823,29 +1625,55 @@
" register.jsp\n"
" ...]]>"
msgstr ""
+"<![CDATA[my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jboss-seam.jar\n"
+" jboss-seam-ui.jar\n"
+" jboss-el.jar\n"
+" jsf-facelets.jar\n"
+" jsf-api.jar\n"
+" jsf-impl.jar\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" persistence.xml\n"
+" seam.properties\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" LoginBean.class\n"
+" Register.class\n"
+" RegisterBean.class\n"
+" ...\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...]]>"
#. Tag: para
#: Configuration.xml:795
#, no-c-format
-msgid ""
-"Most of the Seam example applications may be deployed to Tomcat by running "
-"<literal>ant deploy.tomcat</literal>."
+msgid "Most of the Seam example applications may be deployed to Tomcat by running <literal>ant deploy.tomcat</literal>."
msgstr ""
#. Tag: title
#: Configuration.xml:803
#, no-c-format
msgid "Configuring jBPM in Seam"
-msgstr ""
+msgstr "Configurazione jBPM in Seam"
#. Tag: para
#: Configuration.xml:804
#, no-c-format
-msgid ""
-"Seam's jBPM integration is not installed by default, so you'll need to "
-"enable jBPM by installing a built-in component. You'll also need to "
-"explicitly list your process and pageflow definitions. In "
-"<literal>components.xml</literal>:"
+msgid "Seam's jBPM integration is not installed by default, so you'll need to enable jBPM by installing a built-in component. You'll also need to explicitly list your process and pageflow definitions. In <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1863,16 +1691,21 @@
" </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:pageflow-definitions>\n"
+" <value>createDocument.jpdl.xml</value>\n"
+" <value>editDocument.jpdl.xml</value>\n"
+" <value>approveDocument.jpdl.xml</value>\n"
+" </bpm:pageflow-definitions>\n"
+" <bpm:process-definitions>\n"
+" <value>documentLifecycle.jpdl.xml</value>\n"
+" </bpm:process-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: para
#: Configuration.xml:810
#, no-c-format
-msgid ""
-"No further special configuration is needed if you only have pageflows. If "
-"you do have business process definitions, you need to provide a jBPM "
-"configuration, and a Hibernate configuration for jBPM. The Seam DVD Store "
-"demo includes example <literal>jbpm.cfg.xml</literal> and <literal>hibernate."
-"cfg.xml</literal> files that will work with Seam:"
+msgid "No further special configuration is needed if you only have pageflows. If you do have business process definitions, you need to provide a jBPM configuration, and a Hibernate configuration for jBPM. The Seam DVD Store demo includes example <literal>jbpm.cfg.xml</literal> and <literal>hibernate.cfg.xml</literal> files that will work with Seam:"
msgstr ""
#. Tag: programlisting
@@ -1884,44 +1717,51 @@
" <jbpm-context>\n"
" <service name=\"persistence\">\n"
" <factory>\n"
-" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory"
-"\">\n"
+" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory\">\n"
" <field name=\"isTransactionEnabled\"><false/></field>\n"
" </bean>\n"
" </factory>\n"
" </service>\n"
" <service name=\"tx\" factory=\"org.jbpm.tx.TxServiceFactory\" />\n"
-" <service name=\"message\" factory=\"org.jbpm.msg.db."
-"DbMessageServiceFactory\" />\n"
-" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db."
-"DbSchedulerServiceFactory\" />\n"
-" <service name=\"logging\" factory=\"org.jbpm.logging.db."
-"DbLoggingServiceFactory\" />\n"
+" <service name=\"message\" factory=\"org.jbpm.msg.db.DbMessageServiceFactory\" />\n"
+" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db.DbSchedulerServiceFactory\" />\n"
+" <service name=\"logging\" factory=\"org.jbpm.logging.db.DbLoggingServiceFactory\" />\n"
" <service name=\"authentication\" \n"
-" factory=\"org.jbpm.security.authentication."
-"DefaultAuthenticationServiceFactory\" />\n"
+" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n"
" </jbpm-context>\n"
"\n"
"</jbpm-configuration>]]>"
msgstr ""
+"<![CDATA[<jbpm-configuration>\n"
+"\n"
+" <jbpm-context>\n"
+" <service name=\"persistence\">\n"
+" <factory>\n"
+" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory\">\n"
+" <field name=\"isTransactionEnabled\"><false/></field>\n"
+" </bean>\n"
+" </factory>\n"
+" </service>\n"
+" <service name=\"tx\" factory=\"org.jbpm.tx.TxServiceFactory\" />\n"
+" <service name=\"message\" factory=\"org.jbpm.msg.db.DbMessageServiceFactory\" />\n"
+" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db.DbSchedulerServiceFactory\" />\n"
+" <service name=\"logging\" factory=\"org.jbpm.logging.db.DbLoggingServiceFactory\" />\n"
+" <service name=\"authentication\" \n"
+" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n"
+" </jbpm-context>\n"
+"\n"
+"</jbpm-configuration>]]>"
#. Tag: para
#: Configuration.xml:817
#, no-c-format
-msgid ""
-"The most important thing to notice here is that jBPM transaction control is "
-"disabled. Seam or EJB3 should control the JTA transactions."
+msgid "The most important thing to notice here is that jBPM transaction control is disabled. Seam or EJB3 should control the JTA transactions."
msgstr ""
#. Tag: para
#: Configuration.xml:823
#, no-c-format
-msgid ""
-"There is not yet any well-defined packaging format for jBPM configuration "
-"and process/pageflow definition files. In the Seam examples we've decided to "
-"simply package all these files into the root of the EAR. In future, we will "
-"probably design some other standard packaging format. So the EAR looks "
-"something like this:"
+msgid "There is not yet any well-defined packaging format for jBPM configuration and process/pageflow definition files. In the Seam examples we've decided to simply package all these files into the root of the EAR. In future, we will probably design some other standard packaging format. So the EAR looks something like this:"
msgstr ""
#. Tag: programlisting
@@ -1970,6 +1810,47 @@
" approveDocument.jpdl.xml\n"
" documentLifecycle.jpdl.xml]]>"
msgstr ""
+"<![CDATA[my-application.ear/\n"
+" jboss-seam.jar\n"
+" lib/\n"
+" jboss-el.jar\n"
+" jbpm-3.1.jar\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" application.xml\n"
+" my-application.war/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" WEB-INF/\n"
+" web.xml\n"
+" components.xml\n"
+" faces-config.xml\n"
+" lib/\n"
+" jsf-facelets.jar\n"
+" jboss-seam-ui.jar\n"
+" login.jsp\n"
+" register.jsp\n"
+" ...\n"
+" my-application.jar/\n"
+" META-INF/\n"
+" MANIFEST.MF\n"
+" persistence.xml\n"
+" seam.properties\n"
+" org/\n"
+" jboss/\n"
+" myapplication/\n"
+" User.class\n"
+" Login.class\n"
+" LoginBean.class\n"
+" Register.class\n"
+" RegisterBean.class\n"
+" ...\n"
+" jbpm.cfg.xml\n"
+" hibernate.cfg.xml\n"
+" createDocument.jpdl.xml\n"
+" editDocument.jpdl.xml\n"
+" approveDocument.jpdl.xml\n"
+" documentLifecycle.jpdl.xml]]>"
#. Tag: title
#: Configuration.xml:835
@@ -1980,22 +1861,13 @@
#. Tag: para
#: Configuration.xml:837
#, no-c-format
-msgid ""
-"It is very important that the timeout for Stateful Session Beans is set "
-"higher than the timeout for HTTP Sessions, otherwise SFSB's may time out "
-"before the user's HTTP session has ended. JBoss Application Server has a "
-"default session bean timeout of 30 minutes, which is configured in "
-"<literal>server/default/conf/standardjboss.xml</literal> (replace "
-"<emphasis>default</emphasis> with your own configuration)."
+msgid "It is very important that the timeout for Stateful Session Beans is set higher than the timeout for HTTP Sessions, otherwise SFSB's may time out before the user's HTTP session has ended. JBoss Application Server has a default session bean timeout of 30 minutes, which is configured in <literal>server/default/conf/standardjboss.xml</literal> (replace <emphasis>default</emphasis> with your own configuration)."
msgstr ""
#. Tag: para
#: Configuration.xml:843
#, no-c-format
-msgid ""
-"The default SFSB timeout can be adjusted by modifying the value of "
-"<literal>max-bean-life</literal> in the "
-"<literal>LRUStatefulContextCachePolicy</literal> cache configuration:"
+msgid "The default SFSB timeout can be adjusted by modifying the value of <literal>max-bean-life</literal> in the <literal>LRUStatefulContextCachePolicy</literal> cache configuration:"
msgstr ""
#. Tag: programlisting
@@ -2003,8 +1875,7 @@
#, no-c-format
msgid ""
"<![CDATA[<container-cache-conf>\n"
-" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-"
-"policy>\n"
+" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>\n"
" <cache-policy-conf>\n"
" <min-capacity>50</min-capacity>\n"
" <max-capacity>1000000</max-capacity>\n"
@@ -2022,16 +1893,29 @@
" </cache-policy-conf>\n"
"</container-cache-conf>]]>"
msgstr ""
+"<![CDATA[<container-cache-conf>\n"
+" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>\n"
+" <cache-policy-conf>\n"
+" <min-capacity>50</min-capacity>\n"
+" <max-capacity>1000000</max-capacity>\n"
+" <remover-period>1800</remover-period>\n"
+"\n"
+" <!-- SFSB timeout in seconds; 1800 seconds == 30 minutes -->\n"
+" <max-bean-life>1800</max-bean-life> \n"
+"\n"
+" <overager-period>300</overager-period>\n"
+" <max-bean-age>600</max-bean-age>\n"
+" <resizer-period>400</resizer-period>\n"
+" <max-cache-miss-period>60</max-cache-miss-period>\n"
+" <min-cache-miss-period>1</min-cache-miss-period>\n"
+" <cache-load-factor>0.75</cache-load-factor>\n"
+" </cache-policy-conf>\n"
+"</container-cache-conf>]]>"
#. Tag: para
#: Configuration.xml:848
#, no-c-format
-msgid ""
-"The default HTTP session timeout can be modified in <literal>server/default/"
-"deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in "
-"<literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for "
-"JBoss 4.2.x. The following entry in this file controls the default session "
-"timeout for all web applications:"
+msgid "The default HTTP session timeout can be modified in <literal>server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in <literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for JBoss 4.2.x. The following entry in this file controls the default session timeout for all web applications:"
msgstr ""
#. Tag: programlisting
@@ -2043,13 +1927,15 @@
" <session-timeout>30</session-timeout>\n"
"</session-config>]]>"
msgstr ""
+"<![CDATA[<session-config>\n"
+" <!-- HTTP Session timeout, in minutes -->\n"
+" <session-timeout>30</session-timeout>\n"
+"</session-config>]]>"
#. Tag: para
#: Configuration.xml:855
#, no-c-format
-msgid ""
-"To override this value for your own application, simply include this entry "
-"in your application's own <literal>web.xml</literal>."
+msgid "To override this value for your own application, simply include this entry in your application's own <literal>web.xml</literal>."
msgstr ""
#. Tag: title
@@ -2061,12 +1947,7 @@
#. Tag: para
#: Configuration.xml:863
#, no-c-format
-msgid ""
-"If you want to run your Seam application in a portlet, take a look at the "
-"JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within "
-"a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://"
-"labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> "
-"for more."
+msgid "If you want to run your Seam application in a portlet, take a look at the JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> for more."
msgstr ""
#. Tag: title
@@ -2078,22 +1959,13 @@
#. Tag: para
#: Configuration.xml:876
#, no-c-format
-msgid ""
-"Seam scans all jars containing <literal>/seam.properties</literal>, "
-"<literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam."
-"properties</literal> on startup for resources. For example, all classes "
-"annotated with <literal>@Name</literal> are registered with Seam as Seam "
-"components."
+msgid "Seam scans all jars containing <literal>/seam.properties</literal>, <literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam.properties</literal> on startup for resources. For example, all classes annotated with <literal>@Name</literal> are registered with Seam as Seam components."
msgstr ""
#. Tag: para
#: Configuration.xml:883
#, no-c-format
-msgid ""
-"You may also want Seam to handle custom resources. A common use case is to "
-"handle a specific annotation and Seam provides specific support for this. "
-"First, tell Seam which annotations to handle in <literal>/META-INF/seam-"
-"deployment.properties</literal>:"
+msgid "You may also want Seam to handle custom resources. A common use case is to handle a specific annotation and Seam provides specific support for this. First, tell Seam which annotations to handle in <literal>/META-INF/seam-deployment.properties</literal>:"
msgstr ""
#. Tag: programlisting
@@ -2103,13 +1975,13 @@
"<![CDATA[# A colon-separated list of annotation types to handle\n"
"org.jboss.seam.deployment.annotationTypes=com.acme.Foo:com.acme.Bar]]>"
msgstr ""
+"<![CDATA[# A colon-separated list of annotation types to handle\n"
+"org.jboss.seam.deployment.annotationTypes=com.acme.Foo:com.acme.Bar]]>"
#. Tag: para
#: Configuration.xml:892
#, no-c-format
-msgid ""
-"Then, during application startup you can get hold of all classes annotated "
-"with <literal>@Foo</literal>:"
+msgid "Then, during application startup you can get hold of all classes annotated with <literal>@Foo</literal>:"
msgstr ""
#. Tag: programlisting
@@ -2139,14 +2011,33 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"fooStartup\")\n"
+"@Scope(APPLICATION)\n"
+"@Startup\n"
+"public class FooStartup {\n"
+"\n"
+" @In(\"#{deploymentStrategy.annotatedClasses['com.acme.Foo']}\")\n"
+" private Set<Class<Object>> fooClasses;\n"
+" \n"
+" @In(\"#{hotDeploymentStrategy.annotatedClasses['com.acme.Foo']}\")\n"
+" private Set<Class<Object>> hotFooClasses;\n"
+"\n"
+" @Create\n"
+" public void create() {\n"
+" for (Class clazz : fooClasses) {\n"
+" handleClass(clazz);\n"
+" }\n"
+" for (Class clazz : hotFooClasses) {\n"
+" handleClass(clazz);\n"
+" }\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: para
#: Configuration.xml:899
#, no-c-format
-msgid ""
-"You can also handle <emphasis>any</emphasis> resource. For example, you "
-"process any files with the extension <literal>.foo.xml</literal>. To do "
-"this, we need to write a custom deployment handler:"
+msgid "You can also handle <emphasis>any</emphasis> resource. For example, you process any files with the extension <literal>.foo.xml</literal>. To do this, we need to write a custom deployment handler:"
msgstr ""
#. Tag: programlisting
@@ -2172,21 +2063,35 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[public class FooDeploymentHandler implements DeploymentHandler {\n"
+" \n"
+" private Set<InputStream> files = new HashSet<InputStream>();\n"
+" \n"
+" public String getName() {\n"
+" return \"fooDeploymentHandler\";\n"
+" }\n"
+" \n"
+" public Set<InputStream> getFiles() {\n"
+" return files;\n"
+" }\n"
+" \n"
+" public void handle(String name, ClassLoader classLoader) {\n"
+" if (name.endsWith(\".foo.xml\")) {\n"
+" files.add(classLoader.getResourceAsStream(name));\n"
+" }\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Configuration.xml:907
#, no-c-format
-msgid ""
-"Here we are just building a list of any files with the suffix <literal>.foo."
-"xml</literal>."
+msgid "Here we are just building a list of any files with the suffix <literal>.foo.xml</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:912
#, no-c-format
-msgid ""
-"Then, we need to register the deployment handler with Seam. In <literal>/"
-"META-INF/seam-deployment.properties</literal>:"
+msgid "Then, we need to register the deployment handler with Seam. In <literal>/META-INF/seam-deployment.properties</literal>:"
msgstr ""
#. Tag: programlisting
@@ -2196,26 +2101,23 @@
"<![CDATA[# For standard deployment\n"
"org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n"
"# For hot deployment\n"
-"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme."
-"FooDeploymentHandler]]>"
+"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
msgstr ""
+"<![CDATA[# For standard deployment\n"
+"org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n"
+"# For hot deployment\n"
+"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
#. Tag: para
#: Configuration.xml:919
#, no-c-format
-msgid ""
-"You can register multiple deployment handler using a comma separated list."
+msgid "You can register multiple deployment handler using a comma separated list."
msgstr ""
#. Tag: para
#: Configuration.xml:924
#, no-c-format
-msgid ""
-"Seam uses deployment handlers internally to install components and "
-"namespaces, therefore the <literal>handle()</literal> is called too early in "
-"inside Seam bootstrap to normally be useful. However, you can easily access "
-"the deployment handler during an <literal>APPLICATION</literal> scoped "
-"component's startup:"
+msgid "Seam uses deployment handlers internally to install components and namespaces, therefore the <literal>handle()</literal> is called too early in inside Seam bootstrap to normally be useful. However, you can easily access the deployment handler during an <literal>APPLICATION</literal> scoped component's startup:"
msgstr ""
#. Tag: programlisting
@@ -2245,3 +2147,26 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"fooStartup\")\n"
+"@Scope(APPLICATION)\n"
+"@Startup\n"
+"public class FooStartup {\n"
+"\n"
+" @In(\"#{deploymentStrategy['fooDeploymentHandler']}\")\n"
+" private MyDeploymentHandler myDeploymentHandler;\n"
+" \n"
+" @In(\"#{hotDeploymentStrategy['fooDeploymentHandler']}\")\n"
+" private MyDeploymentHandler myHotDeploymentHandler;\n"
+"\n"
+" @Create\n"
+" public void create() {\n"
+" for (InputStream is : myDeploymentHandler.getFiles()) {\n"
+" handleFooXml(is);\n"
+" }\n"
+" for (InputStream is : myHotDeploymentHandler.getFiles()) {\n"
+" handleFooXml(is);\n"
+" }\n"
+" }\n"
+"\n"
+"}]]>"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:23+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-16 11:29+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -28,34 +28,19 @@
#. Tag: para
#: Conversations.xml:12
#, no-c-format
-msgid ""
-"Historically, the notion of a Seam \"conversation\" came about as a merger "
-"of three different ideas:"
+msgid "Historically, the notion of a Seam \"conversation\" came about as a merger of three different ideas:"
msgstr ""
#. Tag: para
#: Conversations.xml:19
#, no-c-format
-msgid ""
-"The idea of a <emphasis>workspace</emphasis>, which I encountered in a "
-"project for the Victorian government in 2002. In this project I was forced "
-"to implement workspace management on top of Struts, an experience I pray "
-"never to repeat."
+msgid "The idea of a <emphasis>workspace</emphasis>, which I encountered in a project for the Victorian government in 2002. In this project I was forced to implement workspace management on top of Struts, an experience I pray never to repeat."
msgstr ""
#. Tag: para
#: Conversations.xml:28
#, no-c-format
-msgid ""
-"The idea of an <emphasis>application transaction</emphasis> with optimistic "
-"semantics, and the realization that existing frameworks based around a "
-"stateless architecture could not provide effective management of extended "
-"persistence contexts. (The Hibernate team is truly fed up with copping the "
-"blame for <literal>LazyInitializationException</literal>s, which are not "
-"really Hibernate's fault, but rather the fault of the extremely limiting "
-"persistence context model supported by stateless architectures such as the "
-"Spring framework or the traditional <emphasis>stateless session facade</"
-"emphasis> (anti)pattern in J2EE.)"
+msgid "The idea of an <emphasis>application transaction</emphasis> with optimistic semantics, and the realization that existing frameworks based around a stateless architecture could not provide effective management of extended persistence contexts. (The Hibernate team is truly fed up with copping the blame for <literal>LazyInitializationException</literal>s, which are not really Hibernate's fault, but rather the fault of the extremely limiting persistence context model supported by stateless architectures such as the Spring framework or the traditional <emphasis>stateless session facade</emphasis> (anti)pattern in J2EE.)"
msgstr ""
#. Tag: para
@@ -67,116 +52,80 @@
#. Tag: para
#: Conversations.xml:49
#, no-c-format
-msgid ""
-"By unifying these ideas and providing deep support in the framework, we have "
-"a powerful construct that lets us build richer and more efficient "
-"applications with less code than before."
+msgid "By unifying these ideas and providing deep support in the framework, we have a powerful construct that lets us build richer and more efficient applications with less code than before."
msgstr ""
#. Tag: title
#: Conversations.xml:56
#, no-c-format
msgid "Seam's conversation model"
-msgstr ""
+msgstr "Il modello di conversazioni di Seam"
#. Tag: para
#: Conversations.xml:58
#, no-c-format
-msgid ""
-"The examples we have seen so far make use of a very simple conversation "
-"model that follows these rules:"
+msgid "The examples we have seen so far make use of a very simple conversation model that follows these rules:"
msgstr ""
#. Tag: para
#: Conversations.xml:65
#, no-c-format
-msgid ""
-"There is always a conversation context active during the apply request "
-"values, process validations, update model values, invoke application and "
-"render response phases of the JSF request lifecycle."
+msgid "There is always a conversation context active during the apply request values, process validations, update model values, invoke application and render response phases of the JSF request lifecycle."
msgstr ""
#. Tag: para
#: Conversations.xml:73
#, no-c-format
-msgid ""
-"At the end of the restore view phase of the JSF request lifecycle, Seam "
-"attempts to restore any previous long-running conversation context. If none "
-"exists, Seam creates a new temporary conversation context."
+msgid "At the end of the restore view phase of the JSF request lifecycle, Seam attempts to restore any previous long-running conversation context. If none exists, Seam creates a new temporary conversation context."
msgstr ""
#. Tag: para
#: Conversations.xml:81
#, no-c-format
-msgid ""
-"When an <literal>@Begin</literal> method is encountered, the temporary "
-"conversation context is promoted to a long running conversation."
+msgid "When an <literal>@Begin</literal> method is encountered, the temporary conversation context is promoted to a long running conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:88
#, no-c-format
-msgid ""
-"When an <literal>@End</literal> method is encountered, any long-running "
-"conversation context is demoted to a temporary conversation."
+msgid "When an <literal>@End</literal> method is encountered, any long-running conversation context is demoted to a temporary conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:95
#, no-c-format
-msgid ""
-"At the end of the render response phase of the JSF request lifecycle, Seam "
-"stores the contents of a long running conversation context or destroys the "
-"contents of a temporary conversation context."
+msgid "At the end of the render response phase of the JSF request lifecycle, Seam stores the contents of a long running conversation context or destroys the contents of a temporary conversation context."
msgstr ""
#. Tag: para
#: Conversations.xml:103
#, no-c-format
-msgid ""
-"Any faces request (a JSF postback) will propagate the conversation context. "
-"By default, non-faces requests (GET requests, for example) do not propagate "
-"the conversation context, but see below for more information on this."
+msgid "Any faces request (a JSF postback) will propagate the conversation context. By default, non-faces requests (GET requests, for example) do not propagate the conversation context, but see below for more information on this."
msgstr ""
#. Tag: para
#: Conversations.xml:111
#, no-c-format
-msgid ""
-"If the JSF request lifecycle is foreshortened by a redirect, Seam "
-"transparently stores and restores the current conversation context—"
-"unless the conversation was already ended via <literal>@End"
-"(beforeRedirect=true)</literal>."
+msgid "If the JSF request lifecycle is foreshortened by a redirect, Seam transparently stores and restores the current conversation context—unless the conversation was already ended via <literal>@End(beforeRedirect=true)</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:120
#, no-c-format
-msgid ""
-"Seam transparently propagates the conversation context (including the "
-"temporary conversation context) across JSF postbacks and redirects. If you "
-"don't do anything special, a <emphasis>non-faces request</emphasis> (a GET "
-"request for example) will not propagate the conversation context and will be "
-"processed in a new temporary conversation. This is usually - but not always "
-"- the desired behavior."
+msgid "Seam transparently propagates the conversation context (including the temporary conversation context) across JSF postbacks and redirects. If you don't do anything special, a <emphasis>non-faces request</emphasis> (a GET request for example) will not propagate the conversation context and will be processed in a new temporary conversation. This is usually - but not always - the desired behavior."
msgstr ""
#. Tag: para
#: Conversations.xml:129
#, no-c-format
-msgid ""
-"If you want to propagate a Seam conversation across a non-faces request, you "
-"need to explicitly code the Seam <emphasis>conversation id</emphasis> as a "
-"request parameter:"
+msgid "If you want to propagate a Seam conversation across a non-faces request, you need to explicitly code the Seam <emphasis>conversation id</emphasis> as a request parameter:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:135
#, no-c-format
-msgid ""
-"<![CDATA[<a href=\"main.jsf?#{manager.conversationIdParameter}=#"
-"{conversation.id}\">Continue</a>]]>"
-msgstr ""
+msgid "<![CDATA[<a href=\"main.jsf?#{manager.conversationIdParameter}=#{conversation.id}\">Continue</a>]]>"
+msgstr "<![CDATA[<a href=\"main.jsf?#{manager.conversationIdParameter}=#{conversation.id}\">Continue</a>]]>"
#. Tag: para
#: Conversations.xml:137
@@ -189,14 +138,18 @@
#, no-c-format
msgid ""
"<![CDATA[<h:outputLink value=\"main.jsf\">\n"
-" <f:param name=\"#{manager.conversationIdParameter}\" value=\"#"
-"{conversation.id}\"/>\n"
+" <f:param name=\"#{manager.conversationIdParameter}\" value=\"#{conversation.id}\"/>\n"
" <h:outputText value=\"Continue\"/>\n"
"</h:outputLink>]]>"
msgstr ""
+"<![CDATA[<h:outputLink value=\"main.jsf\">\n"
+" <f:param name=\"#{manager.conversationIdParameter}\" value=\"#{conversation.id}\"/>\n"
+" <h:outputText value=\"Continue\"/>\n"
+"</h:outputLink>]]>"
#. Tag: para
-#: Conversations.xml:143 Conversations.xml:156
+#: Conversations.xml:143
+#: Conversations.xml:156
#, no-c-format
msgid "If you use the Seam tag library, this is equivalent:"
msgstr ""
@@ -210,13 +163,15 @@
" <h:outputText value=\"Continue\"/>\n"
"</h:outputLink>]]>"
msgstr ""
+"<![CDATA[<h:outputLink value=\"main.jsf\">\n"
+" <s:conversationId/>\n"
+" <h:outputText value=\"Continue\"/>\n"
+"</h:outputLink>]]>"
#. Tag: para
#: Conversations.xml:149
#, no-c-format
-msgid ""
-"If you wish to disable propagation of the conversation context for a "
-"postback, a similar trick is used:"
+msgid "If you wish to disable propagation of the conversation context for a postback, a similar trick is used:"
msgstr ""
#. Tag: programlisting
@@ -227,6 +182,9 @@
" <f:param name=\"conversationPropagation\" value=\"none\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Exit\">\n"
+" <f:param name=\"conversationPropagation\" value=\"none\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:160
@@ -236,22 +194,20 @@
" <s:conversationPropagation type=\"none\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Exit\">\n"
+" <s:conversationPropagation type=\"none\"/>\n"
+"</h:commandLink>]]>"
#. Tag: para
#: Conversations.xml:162
#, no-c-format
-msgid ""
-"Note that disabling conversation context propagation is absolutely not the "
-"same thing as ending the conversation."
+msgid "Note that disabling conversation context propagation is absolutely not the same thing as ending the conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:167
#, no-c-format
-msgid ""
-"The <literal>conversationPropagation</literal> request parameter, or the "
-"<literal><s:conversationPropagation></literal> tag may even be used to "
-"begin and end conversation, or begin a nested conversation."
+msgid "The <literal>conversationPropagation</literal> request parameter, or the <literal><s:conversationPropagation></literal> tag may even be used to begin and end conversation, or begin a nested conversation."
msgstr ""
#. Tag: programlisting
@@ -262,6 +218,9 @@
" <s:conversationPropagation type=\"end\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Exit\">\n"
+" <s:conversationPropagation type=\"end\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:176
@@ -271,6 +230,9 @@
" <s:conversationPropagation type=\"nested\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Select Child\">\n"
+" <s:conversationPropagation type=\"nested\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:178
@@ -280,6 +242,9 @@
" <s:conversationPropagation type=\"begin\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Select Hotel\">\n"
+" <s:conversationPropagation type=\"begin\"/>\n"
+"</h:commandLink>]]>"
#. Tag: programlisting
#: Conversations.xml:180
@@ -289,34 +254,26 @@
" <s:conversationPropagation type=\"join\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"main\" value=\"Select Hotel\">\n"
+" <s:conversationPropagation type=\"join\"/>\n"
+"</h:commandLink>]]>"
#. Tag: para
#: Conversations.xml:182
#, no-c-format
-msgid ""
-"This conversation model makes it easy to build applications which behave "
-"correctly with respect to multi-window operation. For many applications, "
-"this is all that is needed. Some complex applications have either or both of "
-"the following additional requirements:"
+msgid "This conversation model makes it easy to build applications which behave correctly with respect to multi-window operation. For many applications, this is all that is needed. Some complex applications have either or both of the following additional requirements:"
msgstr ""
#. Tag: para
#: Conversations.xml:191
#, no-c-format
-msgid ""
-"A conversation spans many smaller units of user interaction, which execute "
-"serially or even concurrently. The smaller <emphasis>nested conversations</"
-"emphasis> have their own isolated set of conversation state, and also have "
-"access to the state of the outer conversation."
+msgid "A conversation spans many smaller units of user interaction, which execute serially or even concurrently. The smaller <emphasis>nested conversations</emphasis> have their own isolated set of conversation state, and also have access to the state of the outer conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:200
#, no-c-format
-msgid ""
-"The user is able to switch between many conversations within the same "
-"browser window. This feature is called <emphasis>workspace management</"
-"emphasis>."
+msgid "The user is able to switch between many conversations within the same browser window. This feature is called <emphasis>workspace management</emphasis>."
msgstr ""
#. Tag: title
@@ -328,97 +285,55 @@
#. Tag: para
#: Conversations.xml:213
#, no-c-format
-msgid ""
-"A nested conversation is created by invoking a method marked <literal>@Begin"
-"(nested=true)</literal> inside the scope of an existing conversation. A "
-"nested conversation has its own conversation context, but can read values "
-"from the outer conversation's context. The outer conversation's context is "
-"read-only within a nested conversation, but because objects are obtained by "
-"reference, changes to the objects themselves will be reflected in the outer "
-"context."
+msgid "A nested conversation is created by invoking a method marked <literal>@Begin(nested=true)</literal> inside the scope of an existing conversation. A nested conversation has its own conversation context, but can read values from the outer conversation's context. The outer conversation's context is read-only within a nested conversation, but because objects are obtained by reference, changes to the objects themselves will be reflected in the outer context."
msgstr ""
#. Tag: para
#: Conversations.xml:226
#, no-c-format
-msgid ""
-"Nesting a conversation through initializes a context that is stacked on the "
-"context of the original, or outer, conversation. The outer conversation is "
-"considered the parent."
+msgid "Nesting a conversation through initializes a context that is stacked on the context of the original, or outer, conversation. The outer conversation is considered the parent."
msgstr ""
#. Tag: para
#: Conversations.xml:233
#, no-c-format
-msgid ""
-"Any values outjected or directly set into the nested conversation’s context "
-"do not affect the objects accessible in the parent conversation’s context."
+msgid "Any values outjected or directly set into the nested conversation’s context do not affect the objects accessible in the parent conversation’s context."
msgstr ""
#. Tag: para
#: Conversations.xml:240
#, no-c-format
-msgid ""
-"Injection or a context lookup from the conversation context will first "
-"lookup the value in the current conversation context and, if no value is "
-"found, will proceed down the conversation stack if the conversation is "
-"nested. As you will see in moment, this behavior can be overriden."
+msgid "Injection or a context lookup from the conversation context will first lookup the value in the current conversation context and, if no value is found, will proceed down the conversation stack if the conversation is nested. As you will see in moment, this behavior can be overriden."
msgstr ""
#. Tag: para
#: Conversations.xml:250
#, no-c-format
-msgid ""
-"When an <literal>@End</literal> is subsequently encountered, the nested "
-"conversation will be destroyed, and the outer conversation will resume, by "
-"\"popping\" the conversation stack. Conversations may be nested to any "
-"arbitrary depth."
+msgid "When an <literal>@End</literal> is subsequently encountered, the nested conversation will be destroyed, and the outer conversation will resume, by \"popping\" the conversation stack. Conversations may be nested to any arbitrary depth."
msgstr ""
#. Tag: para
#: Conversations.xml:257
#, no-c-format
-msgid ""
-"Certain user activity (workspace management, or the back button) can cause "
-"the outer conversation to be resumed before the inner conversation is ended. "
-"In this case it is possible to have multiple concurrent nested conversations "
-"belonging to the same outer conversation. If the outer conversation ends "
-"before a nested conversation ends, Seam destroys all nested conversation "
-"contexts along with the outer context."
+msgid "Certain user activity (workspace management, or the back button) can cause the outer conversation to be resumed before the inner conversation is ended. In this case it is possible to have multiple concurrent nested conversations belonging to the same outer conversation. If the outer conversation ends before a nested conversation ends, Seam destroys all nested conversation contexts along with the outer context."
msgstr ""
#. Tag: para
#: Conversations.xml:267
#, no-c-format
-msgid ""
-"The conversation at the bottom of the conversation stack is the root "
-"conversation. Destroying this conversation always destroy all of its "
-"descendents. You can achieve this declaratively by specifying <literal>@End"
-"(root=true)</literal>."
+msgid "The conversation at the bottom of the conversation stack is the root conversation. Destroying this conversation always destroy all of its descendents. You can achieve this declaratively by specifying <literal>@End(root=true)</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:274
#, no-c-format
-msgid ""
-"A conversation may be thought of as a <emphasis>continuable state</"
-"emphasis>. Nested conversations allow the application to capture a "
-"consistent continuable state at various points in a user interaction, thus "
-"ensuring truly correct behavior in the face of backbuttoning and workspace "
-"management."
+msgid "A conversation may be thought of as a <emphasis>continuable state</emphasis>. Nested conversations allow the application to capture a consistent continuable state at various points in a user interaction, thus ensuring truly correct behavior in the face of backbuttoning and workspace management."
msgstr ""
#. Tag: para
#: Conversations.xml:282
#, no-c-format
-msgid ""
-"As mentioned previously, if a component exists in a parent conversation of "
-"the current nested conversation, the nested conversation will use the same "
-"instance. Occasionally, it is useful to have a different instance in each "
-"nested conversation, so that the component instance that exists in the "
-"parent conversation is invisible to its child conversations. You can achieve "
-"this behavior by annotating the component <literal>@PerNestedConversation</"
-"literal>."
+msgid "As mentioned previously, if a component exists in a parent conversation of the current nested conversation, the nested conversation will use the same instance. Occasionally, it is useful to have a different instance in each nested conversation, so that the component instance that exists in the parent conversation is invisible to its child conversations. You can achieve this behavior by annotating the component <literal>@PerNestedConversation</literal>."
msgstr ""
#. Tag: title
@@ -430,39 +345,25 @@
#. Tag: para
#: Conversations.xml:296
#, no-c-format
-msgid ""
-"JSF does not define any kind of action listener that is triggered when a "
-"page is accessed via a non-faces request (for example, a HTTP GET request). "
-"This can occur if the user bookmarks the page, or if we navigate to the page "
-"via an <literal><h:outputLink></literal>."
+msgid "JSF does not define any kind of action listener that is triggered when a page is accessed via a non-faces request (for example, a HTTP GET request). This can occur if the user bookmarks the page, or if we navigate to the page via an <literal><h:outputLink></literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:303
#, no-c-format
-msgid ""
-"Sometimes we want to begin a conversation immediately the page is accessed. "
-"Since there is no JSF action method, we can't solve the problem in the usual "
-"way, by annotating the action with <literal>@Begin</literal>."
+msgid "Sometimes we want to begin a conversation immediately the page is accessed. Since there is no JSF action method, we can't solve the problem in the usual way, by annotating the action with <literal>@Begin</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:309
#, no-c-format
-msgid ""
-"A further problem arises if the page needs some state to be fetched into a "
-"context variable. We've already seen two ways to solve this problem. If that "
-"state is held in a Seam component, we can fetch the state in a "
-"<literal>@Create</literal> method. If not, we can define a "
-"<literal>@Factory</literal> method for the context variable."
+msgid "A further problem arises if the page needs some state to be fetched into a context variable. We've already seen two ways to solve this problem. If that state is held in a Seam component, we can fetch the state in a <literal>@Create</literal> method. If not, we can define a <literal>@Factory</literal> method for the context variable."
msgstr ""
#. Tag: para
#: Conversations.xml:317
#, no-c-format
-msgid ""
-"If none of these options works for you, Seam lets you define a "
-"<emphasis>page action</emphasis> in the <literal>pages.xml</literal> file."
+msgid "If none of these options works for you, Seam lets you define a <emphasis>page action</emphasis> in the <literal>pages.xml</literal> file."
msgstr ""
#. Tag: programlisting
@@ -474,24 +375,21 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/messageList.jsp\" action=\"#{messageManager.list}\"/>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:325
#, no-c-format
-msgid ""
-"This action method is called at the beginning of the render response phase, "
-"any time the page is about to be rendered. If a page action returns a non-"
-"null outcome, Seam will process any appropriate JSF and Seam navigation "
-"rules, possibly resulting in a completely different page being rendered."
+msgid "This action method is called at the beginning of the render response phase, any time the page is about to be rendered. If a page action returns a non-null outcome, Seam will process any appropriate JSF and Seam navigation rules, possibly resulting in a completely different page being rendered."
msgstr ""
#. Tag: para
#: Conversations.xml:333
#, no-c-format
-msgid ""
-"If <emphasis>all</emphasis> you want to do before rendering the page is "
-"begin a conversation, you could use a built-in action method that does just "
-"that:"
+msgid "If <emphasis>all</emphasis> you want to do before rendering the page is begin a conversation, you could use a built-in action method that does just that:"
msgstr ""
#. Tag: programlisting
@@ -503,23 +401,21 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/messageList.jsp\" action=\"#{conversation.begin}\"/>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:341
#, no-c-format
-msgid ""
-"Note that you can also call this built-in action from a JSF control, and, "
-"similarly, you can use <literal>#{conversation.end}</literal> to end "
-"conversations."
+msgid "Note that you can also call this built-in action from a JSF control, and, similarly, you can use <literal>#{conversation.end}</literal> to end conversations."
msgstr ""
#. Tag: para
#: Conversations.xml:347
#, no-c-format
-msgid ""
-"If you want more control, to join existing conversations or begin a nested "
-"conversion, to begin a pageflow or an atomic conversation, you should use "
-"the <literal><begin-conversation></literal> element."
+msgid "If you want more control, to join existing conversations or begin a nested conversion, to begin a pageflow or an atomic conversation, you should use the <literal><begin-conversation></literal> element."
msgstr ""
#. Tag: programlisting
@@ -533,6 +429,12 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/messageList.jsp\">\n"
+" <begin-conversation nested=\"true\" pageflow=\"AddItem\"/>\n"
+" <page>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:356
@@ -551,6 +453,12 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/home.jsp\">\n"
+" <end-conversation/>\n"
+" <page>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Conversations.xml:363
@@ -561,16 +469,13 @@
#. Tag: para
#: Conversations.xml:369
#, no-c-format
-msgid ""
-"Annotate the <literal>@Create</literal> method with <literal>@Begin</literal>"
+msgid "Annotate the <literal>@Create</literal> method with <literal>@Begin</literal>"
msgstr ""
#. Tag: para
#: Conversations.xml:375
#, no-c-format
-msgid ""
-"Annotate the <literal>@Factory</literal> method with <literal>@Begin</"
-"literal>"
+msgid "Annotate the <literal>@Factory</literal> method with <literal>@Begin</literal>"
msgstr ""
#. Tag: para
@@ -582,76 +487,49 @@
#. Tag: para
#: Conversations.xml:387
#, no-c-format
-msgid ""
-"Use <literal><begin-conversation></literal> in <literal>pages.xml</"
-"literal>."
+msgid "Use <literal><begin-conversation></literal> in <literal>pages.xml</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:393
#, no-c-format
-msgid ""
-"Use <literal>#{conversation.begin}</literal> as the Seam page action method"
+msgid "Use <literal>#{conversation.begin}</literal> as the Seam page action method"
msgstr ""
#. Tag: title
#: Conversations.xml:403
#, no-c-format
-msgid ""
-"Using <literal><s:link></literal> and <literal><s:button></"
-"literal>"
+msgid "Using <literal><s:link></literal> and <literal><s:button></literal>"
msgstr ""
#. Tag: para
#: Conversations.xml:405
#, no-c-format
-msgid ""
-"JSF command links always perform a form submission via JavaScript, which "
-"breaks the web browser's \"open in new window\" or \"open in new tab\" "
-"feature. In plain JSF, you need to use an <literal><h:outputLink></"
-"literal> if you need this functionality. But there are two major limitations "
-"to <literal><h:outputLink></literal>."
+msgid "JSF command links always perform a form submission via JavaScript, which breaks the web browser's \"open in new window\" or \"open in new tab\" feature. In plain JSF, you need to use an <literal><h:outputLink></literal> if you need this functionality. But there are two major limitations to <literal><h:outputLink></literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:415
#, no-c-format
-msgid ""
-"JSF provides no way to attach an action listener to an <literal><h:"
-"outputLink></literal>."
+msgid "JSF provides no way to attach an action listener to an <literal><h:outputLink></literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:421
#, no-c-format
-msgid ""
-"JSF does not propagate the selected row of a <literal>DataModel</literal> "
-"since there is no actual form submission."
+msgid "JSF does not propagate the selected row of a <literal>DataModel</literal> since there is no actual form submission."
msgstr ""
#. Tag: para
#: Conversations.xml:428
#, no-c-format
-msgid ""
-"Seam provides the notion of a <emphasis>page action</emphasis> to help solve "
-"the first problem, but this does nothing to help us with the second problem. "
-"We <emphasis>could</emphasis> work around this by using the RESTful approach "
-"of passing a request parameter and requerying for the selected object on the "
-"server side. In some cases—such as the Seam blog example "
-"application—this is indeed the best approach. The RESTful style "
-"supports bookmarking, since it does not require server-side state. In other "
-"cases, where we don't care about bookmarks, the use of <literal>@DataModel</"
-"literal> and <literal>@DataModelSelection</literal> is just so convenient "
-"and transparent!"
+msgid "Seam provides the notion of a <emphasis>page action</emphasis> to help solve the first problem, but this does nothing to help us with the second problem. We <emphasis>could</emphasis> work around this by using the RESTful approach of passing a request parameter and requerying for the selected object on the server side. In some cases—such as the Seam blog example application—this is indeed the best approach. The RESTful style supports bookmarking, since it does not require server-side state. In other cases, where we don't care about bookmarks, the use of <literal>@DataModel</literal> and <literal>@DataModelSelection</literal> is just so convenient and transparent!"
msgstr ""
#. Tag: para
#: Conversations.xml:441
#, no-c-format
-msgid ""
-"To fill in this missing functionality, and to make conversation propagation "
-"even simpler to manage, Seam provides the <literal><s:link></literal> "
-"JSF tag."
+msgid "To fill in this missing functionality, and to make conversation propagation even simpler to manage, Seam provides the <literal><s:link></literal> JSF tag."
msgstr ""
#. Tag: para
@@ -664,54 +542,43 @@
#: Conversations.xml:451
#, no-c-format
msgid "<![CDATA[<s:link view=\"/login.xhtml\" value=\"Login\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:link view=\"/login.xhtml\" value=\"Login\"/>]]>"
#. Tag: para
#: Conversations.xml:453
#, no-c-format
-msgid ""
-"Or, it may specify an action method (in which case the action outcome "
-"determines the page that results):"
+msgid "Or, it may specify an action method (in which case the action outcome determines the page that results):"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:458
#, no-c-format
msgid "<![CDATA[<s:link action=\"#{login.logout}\" value=\"Logout\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:link action=\"#{login.logout}\" value=\"Logout\"/>]]>"
#. Tag: para
#: Conversations.xml:460
#, no-c-format
-msgid ""
-"If you specify <emphasis>both</emphasis> a JSF view id and an action method, "
-"the 'view' will be used <emphasis>unless</emphasis> the action method "
-"returns a non-null outcome:"
+msgid "If you specify <emphasis>both</emphasis> a JSF view id and an action method, the 'view' will be used <emphasis>unless</emphasis> the action method returns a non-null outcome:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:466
#, no-c-format
-msgid ""
-"<![CDATA[<s:link view=\"/loggedOut.xhtml\" action=\"#{login.logout}\" value="
-"\"Logout\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<s:link view=\"/loggedOut.xhtml\" action=\"#{login.logout}\" value=\"Logout\"/>]]>"
+msgstr "<![CDATA[<s:link view=\"/loggedOut.xhtml\" action=\"#{login.logout}\" value=\"Logout\"/>]]>"
#. Tag: para
#: Conversations.xml:468
#, no-c-format
-msgid ""
-"The link automatically propagates the selected row of a <literal>DataModel</"
-"literal> using inside <literal><h:dataTable></literal>:"
+msgid "The link automatically propagates the selected row of a <literal>DataModel</literal> using inside <literal><h:dataTable></literal>:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:473
#, no-c-format
-msgid ""
-"<![CDATA[<s:link view=\"/hotel.xhtml\" action=\"#{hotelSearch.selectHotel}\" "
-"value=\"#{hotel.name}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<s:link view=\"/hotel.xhtml\" action=\"#{hotelSearch.selectHotel}\" value=\"#{hotel.name}\"/>]]>"
+msgstr "<![CDATA[<s:link view=\"/hotel.xhtml\" action=\"#{hotelSearch.selectHotel}\" value=\"#{hotel.name}\"/>]]>"
#. Tag: para
#: Conversations.xml:475
@@ -723,7 +590,7 @@
#: Conversations.xml:479
#, no-c-format
msgid "<![CDATA[<s:link view=\"/main.xhtml\" propagation=\"none\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:link view=\"/main.xhtml\" propagation=\"none\"/>]]>"
#. Tag: para
#: Conversations.xml:481
@@ -734,42 +601,36 @@
#. Tag: programlisting
#: Conversations.xml:485
#, no-c-format
-msgid ""
-"<![CDATA[<s:link action=\"#{issueEditor.viewComment}\" propagation=\"nest\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<s:link action=\"#{issueEditor.viewComment}\" propagation=\"nest\"/>]]>"
+msgstr "<![CDATA[<s:link action=\"#{issueEditor.viewComment}\" propagation=\"nest\"/>]]>"
#. Tag: para
#: Conversations.xml:487
#, no-c-format
-msgid ""
-"If the link begins a conversation, you can even specify a pageflow to be "
-"used:"
+msgid "If the link begins a conversation, you can even specify a pageflow to be used:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:491
#, no-c-format
msgid ""
-"<![CDATA[<s:link action=\"#{documentEditor.getDocument}\" propagation=\"begin"
-"\"\n"
+"<![CDATA[<s:link action=\"#{documentEditor.getDocument}\" propagation=\"begin\"\n"
" pageflow=\"EditDocument\"/>]]>"
msgstr ""
+"<![CDATA[<s:link action=\"#{documentEditor.getDocument}\" propagation=\"begin\"\n"
+" pageflow=\"EditDocument\"/>]]>"
#. Tag: para
#: Conversations.xml:493
#, no-c-format
-msgid ""
-"The <literal>taskInstance</literal> attribute if for use in jBPM task lists:"
+msgid "The <literal>taskInstance</literal> attribute if for use in jBPM task lists:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:497
#, no-c-format
-msgid ""
-"<![CDATA[<s:link action=\"#{documentApproval.approveOrReject}\" taskInstance="
-"\"#{task}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<s:link action=\"#{documentApproval.approveOrReject}\" taskInstance=\"#{task}\"/>]]>"
+msgstr "<![CDATA[<s:link action=\"#{documentApproval.approveOrReject}\" taskInstance=\"#{task}\"/>]]>"
#. Tag: para
#: Conversations.xml:499
@@ -780,16 +641,14 @@
#. Tag: para
#: Conversations.xml:503
#, no-c-format
-msgid ""
-"Finally, if you need the \"link\" to be rendered as a button, use "
-"<literal><s:button></literal>:"
+msgid "Finally, if you need the \"link\" to be rendered as a button, use <literal><s:button></literal>:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:507
#, no-c-format
msgid "<![CDATA[<s:button action=\"#{login.logout}\" value=\"Logout\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<s:button action=\"#{login.logout}\" value=\"Logout\"/>]]>"
#. Tag: title
#: Conversations.xml:512
@@ -800,22 +659,13 @@
#. Tag: para
#: Conversations.xml:513
#, no-c-format
-msgid ""
-"It is quite common to display a message to the user indicating success or "
-"failure of an action. It is convenient to use a JSF <literal>FacesMessage</"
-"literal> for this. Unfortunately, a successful action often requires a "
-"browser redirect, and JSF does not propagate faces messages across "
-"redirects. This makes it quite difficult to display success messages in "
-"plain JSF."
+msgid "It is quite common to display a message to the user indicating success or failure of an action. It is convenient to use a JSF <literal>FacesMessage</literal> for this. Unfortunately, a successful action often requires a browser redirect, and JSF does not propagate faces messages across redirects. This makes it quite difficult to display success messages in plain JSF."
msgstr ""
#. Tag: para
#: Conversations.xml:522
#, no-c-format
-msgid ""
-"The built in conversation-scoped Seam component named "
-"<literal>facesMessages</literal> solves this problem. (You must have the "
-"Seam redirect filter installed.)"
+msgid "The built in conversation-scoped Seam component named <literal>facesMessages</literal> solves this problem. (You must have the Seam redirect filter installed.)"
msgstr ""
#. Tag: programlisting
@@ -835,15 +685,23 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"editDocumentAction\")\n"
+"@Stateless\n"
+"public class EditDocumentBean implements EditDocument {\n"
+" @In EntityManager em;\n"
+" @In Document document;\n"
+" @In FacesMessages facesMessages;\n"
+" \n"
+" public String update() {\n"
+" em.merge(document);\n"
+" facesMessages.add(\"Document updated\");\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Conversations.xml:530
#, no-c-format
-msgid ""
-"Any message added to <literal>facesMessages</literal> is used in the very "
-"next render response phase for the current conversation. This even works "
-"when there is no long-running conversation since Seam preserves even "
-"temporary conversation contexts across redirects."
+msgid "Any message added to <literal>facesMessages</literal> is used in the very next render response phase for the current conversation. This even works when there is no long-running conversation since Seam preserves even temporary conversation contexts across redirects."
msgstr ""
#. Tag: para
@@ -855,9 +713,8 @@
#. Tag: programlisting
#: Conversations.xml:542
#, no-c-format
-msgid ""
-"<![CDATA[facesMessages.add(\"Document #{document.title} was updated\");]]>"
-msgstr ""
+msgid "<![CDATA[facesMessages.add(\"Document #{document.title} was updated\");]]>"
+msgstr "<![CDATA[facesMessages.add(\"Document #{document.title} was updated\");]]>"
#. Tag: para
#: Conversations.xml:544
@@ -869,7 +726,7 @@
#: Conversations.xml:548
#, no-c-format
msgid "<![CDATA[<h:messages globalOnly=\"true\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<h:messages globalOnly=\"true\"/>]]>"
#. Tag: title
#: Conversations.xml:553
@@ -880,10 +737,7 @@
#. Tag: para
#: Conversations.xml:554
#, no-c-format
-msgid ""
-"When working with conversations that deal with persistent objects, it may be "
-"desirable to use the natural business key of the object instead of the "
-"standard, \"surrogate\" conversation id:"
+msgid "When working with conversations that deal with persistent objects, it may be desirable to use the natural business key of the object instead of the standard, \"surrogate\" conversation id:"
msgstr ""
#. Tag: emphasis
@@ -895,23 +749,13 @@
#. Tag: para
#: Conversations.xml:563
#, no-c-format
-msgid ""
-"It can be useful to redirect to an existing conversation if the user "
-"requests the same operation twice. Take this example: <quote> You are on "
-"ebay, half way through paying for an item you just won as a Christmas "
-"present for your parents. Lets say you're sending it straight to them - you "
-"enter your payment details but you can't remember their address. You "
-"accidentally reuse the same browser window finding out their address. Now "
-"you need to return to the payment for the item. </quote>"
+msgid "It can be useful to redirect to an existing conversation if the user requests the same operation twice. Take this example: <quote> You are on ebay, half way through paying for an item you just won as a Christmas present for your parents. Lets say you're sending it straight to them - you enter your payment details but you can't remember their address. You accidentally reuse the same browser window finding out their address. Now you need to return to the payment for the item. </quote>"
msgstr ""
#. Tag: para
#: Conversations.xml:576
#, no-c-format
-msgid ""
-"With a natural conversation its really easy to have the user rejoin the "
-"existing conversation, and pick up where they left off - just have them to "
-"rejoin the payForItem conversation with the itemId as the conversation id."
+msgid "With a natural conversation its really easy to have the user rejoin the existing conversation, and pick up where they left off - just have them to rejoin the payForItem conversation with the itemId as the conversation id."
msgstr ""
#. Tag: emphasis
@@ -923,30 +767,20 @@
#. Tag: para
#: Conversations.xml:587
#, no-c-format
-msgid ""
-"For me this consists of a navigable hierarchy (I can navigate by editing the "
-"url) and a meaningful URL (like this Wiki uses - so don't identify things by "
-"random ids). For some applications user friendly URLs are less important, of "
-"course."
+msgid "For me this consists of a navigable hierarchy (I can navigate by editing the url) and a meaningful URL (like this Wiki uses - so don't identify things by random ids). For some applications user friendly URLs are less important, of course."
msgstr ""
#. Tag: para
#: Conversations.xml:595
#, no-c-format
-msgid ""
-"With a natural conversations, when you are building your hotel booking "
-"system (or, of course, whatever your app is) you can generate a URL like "
-"<literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> "
-"(of course, whatever parameter <literal>hotel</literal> maps to on your "
-"domain model must be unique) and with URLRewrite easily transform this to "
-"http://seam-hotels/book/BestWesternAntwerpen."
+msgid "With a natural conversations, when you are building your hotel booking system (or, of course, whatever your app is) you can generate a URL like <literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> (of course, whatever parameter <literal>hotel</literal> maps to on your domain model must be unique) and with URLRewrite easily transform this to http://seam-hotels/book/BestWesternAntwerpen."
msgstr ""
#. Tag: para
#: Conversations.xml:606
#, no-c-format
msgid "Much better!"
-msgstr ""
+msgstr "Molto meglio!"
#. Tag: title
#: Conversations.xml:612
@@ -968,66 +802,57 @@
" parameter-name=\"auctionId\"\n"
" parameter-value=\"#{auction.auctionId}\"/>]]>"
msgstr ""
+"<![CDATA[ <conversation name=\"PlaceBid\"\n"
+" parameter-name=\"auctionId\"\n"
+" parameter-value=\"#{auction.auctionId}\"/>]]>"
#. Tag: para
#: Conversations.xml:619
#, no-c-format
-msgid ""
-"The first thing to note from the above definition is that the conversation "
-"has a name, in this case <literal>PlaceBid</literal>. This name uniquely "
-"identifies this particular named conversation, and is used by the "
-"<literal>page</literal> definition to identify a named conversation to "
-"participate in."
+msgid "The first thing to note from the above definition is that the conversation has a name, in this case <literal>PlaceBid</literal>. This name uniquely identifies this particular named conversation, and is used by the <literal>page</literal> definition to identify a named conversation to participate in."
msgstr ""
#. Tag: para
#: Conversations.xml:627
#, no-c-format
-msgid ""
-"The next attribute, <literal>parameter-name</literal> defines the request "
-"parameter that will contain the natural conversation id, in place of the "
-"default conversation id parameter. In this example, the <literal>parameter-"
-"name</literal> is <literal>auctionId</literal>. This means that instead of a "
-"conversation parameter like <literal>cid=123</literal> appearing in the URL "
-"for your page, it will contain <literal>auctionId=765432</literal> instead."
+msgid "The next attribute, <literal>parameter-name</literal> defines the request parameter that will contain the natural conversation id, in place of the default conversation id parameter. In this example, the <literal>parameter-name</literal> is <literal>auctionId</literal>. This means that instead of a conversation parameter like <literal>cid=123</literal> appearing in the URL for your page, it will contain <literal>auctionId=765432</literal> instead."
msgstr ""
#. Tag: para
#: Conversations.xml:636
#, no-c-format
-msgid ""
-"The last attribute in the above configuration, <literal>parameter-value</"
-"literal>, defines an EL expression used to evaluate the value of the natural "
-"business key to use as the conversation id. In this example, the "
-"conversation id will be the primary key value of the <literal>auction</"
-"literal> instance currently in scope."
+msgid "The last attribute in the above configuration, <literal>parameter-value</literal>, defines an EL expression used to evaluate the value of the natural business key to use as the conversation id. In this example, the conversation id will be the primary key value of the <literal>auction</literal> instance currently in scope."
msgstr ""
#. Tag: para
#: Conversations.xml:643
#, no-c-format
-msgid ""
-"Next, we define which pages will participate in the named conversation. This "
-"is done by specifying the <literal>conversation</literal> attribute for a "
-"<literal>page</literal> definition:"
+msgid "Next, we define which pages will participate in the named conversation. This is done by specifying the <literal>conversation</literal> attribute for a <literal>page</literal> definition:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:649
#, no-c-format
msgid ""
-"<![CDATA[ <page view-id=\"/bid.xhtml\" conversation=\"PlaceBid\" login-"
-"required=\"true\">\n"
+"<![CDATA[ <page view-id=\"/bid.xhtml\" conversation=\"PlaceBid\" login-required=\"true\">\n"
" <navigation from-action=\"#{bidAction.confirmBid}\"> \n"
" <rule if-outcome=\"success\">\n"
" <redirect view-id=\"/auction.xhtml\">\n"
-" <param name=\"id\" value=\"#{bidAction.bid.auction."
-"auctionId}\"/>\n"
+" <param name=\"id\" value=\"#{bidAction.bid.auction.auctionId}\"/>\n"
" </redirect>\n"
" </rule> \n"
" </navigation>\n"
" </page>]]>"
msgstr ""
+"<![CDATA[ <page view-id=\"/bid.xhtml\" conversation=\"PlaceBid\" login-required=\"true\">\n"
+" <navigation from-action=\"#{bidAction.confirmBid}\"> \n"
+" <rule if-outcome=\"success\">\n"
+" <redirect view-id=\"/auction.xhtml\">\n"
+" <param name=\"id\" value=\"#{bidAction.bid.auction.auctionId}\"/>\n"
+" </redirect>\n"
+" </rule> \n"
+" </navigation>\n"
+" </page>]]>"
#. Tag: title
#: Conversations.xml:654
@@ -1038,10 +863,7 @@
#. Tag: para
#: Conversations.xml:656
#, no-c-format
-msgid ""
-"When starting, or redirecting to, a natural conversation there are a number "
-"of options for specifying the natural conversation name. Let's start by "
-"looking at the following page definition:"
+msgid "When starting, or redirecting to, a natural conversation there are a number of options for specifying the natural conversation name. Let's start by looking at the following page definition:"
msgstr ""
#. Tag: programlisting
@@ -1056,17 +878,18 @@
" </navigation>\n"
" </page>]]>"
msgstr ""
+"<![CDATA[ <page view-id=\"/auction.xhtml\">\n"
+" <param name=\"id\" value=\"#{auctionDetail.selectedAuctionId}\"/>\n"
+" \n"
+" <navigation from-action=\"#{bidAction.placeBid}\">\n"
+" <redirect view-id=\"/bid.xhtml\"/>\n"
+" </navigation>\n"
+" </page>]]>"
#. Tag: para
#: Conversations.xml:664
#, no-c-format
-msgid ""
-"From here, we can see that invoking the action <literal>#{bidAction.placeBid}"
-"</literal> from our auction view (by the way, all these examples are taken "
-"from the seamBay example in Seam), that we will be redirected to <literal>/"
-"bid.xhtml</literal>, which, as we saw previously, is configured with the "
-"natural conversation <literal>PlaceBid</literal>. The declaration for our "
-"action method looks like this:"
+msgid "From here, we can see that invoking the action <literal>#{bidAction.placeBid}</literal> from our auction view (by the way, all these examples are taken from the seamBay example in Seam), that we will be redirected to <literal>/bid.xhtml</literal>, which, as we saw previously, is configured with the natural conversation <literal>PlaceBid</literal>. The declaration for our action method looks like this:"
msgstr ""
#. Tag: programlisting
@@ -1076,46 +899,38 @@
"<![CDATA[ @Begin(join = true)\n"
" public void placeBid()]]>"
msgstr ""
+"<![CDATA[ @Begin(join = true)\n"
+" public void placeBid()]]>"
#. Tag: para
#: Conversations.xml:674
#, no-c-format
-msgid ""
-"When named conversations are specified in the <literal><page/></"
-"literal> element, redirection to the named conversation occurs as part of "
-"navigation rules, after the action method has already been invoked. This is "
-"a problem when redirecting to an existing conversation, as redirection needs "
-"to be occur before the action method is invoked. Therefore it is necessary "
-"to specify the conversation name when the action is invoked. One way of "
-"doing this is by using the <literal>s:conversationName</literal> tag:"
+msgid "When named conversations are specified in the <literal><page/></literal> element, redirection to the named conversation occurs as part of navigation rules, after the action method has already been invoked. This is a problem when redirecting to an existing conversation, as redirection needs to be occur before the action method is invoked. Therefore it is necessary to specify the conversation name when the action is invoked. One way of doing this is by using the <literal>s:conversationName</literal> tag:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:684
#, no-c-format
msgid ""
-"<![CDATA[ <h:commandButton id=\"placeBidWithAmount\" styleClass=\"placeBid"
-"\" action=\"#{bidAction.placeBid}\">\n"
+"<![CDATA[ <h:commandButton id=\"placeBidWithAmount\" styleClass=\"placeBid\" action=\"#{bidAction.placeBid}\">\n"
" <s:conversationName value=\"PlaceBid\"/>\n"
" </h:commandButton>]]>"
msgstr ""
+"<![CDATA[ <h:commandButton id=\"placeBidWithAmount\" styleClass=\"placeBid\" action=\"#{bidAction.placeBid}\">\n"
+" <s:conversationName value=\"PlaceBid\"/>\n"
+" </h:commandButton>]]>"
#. Tag: para
#: Conversations.xml:686
#, no-c-format
-msgid ""
-"Another alternative is to specify the <literal>conversationName</literal> "
-"attribute when using either <literal>s:link</literal> or <literal>s:button</"
-"literal>:"
+msgid "Another alternative is to specify the <literal>conversationName</literal> attribute when using either <literal>s:link</literal> or <literal>s:button</literal>:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:691
#, no-c-format
-msgid ""
-"<![CDATA[ <s:link value=\"Place Bid\" action=\"#{bidAction.placeBid}\" "
-"conversationName=\"PlaceBid\"/>]]>"
-msgstr ""
+msgid "<![CDATA[ <s:link value=\"Place Bid\" action=\"#{bidAction.placeBid}\" conversationName=\"PlaceBid\"/>]]>"
+msgstr "<![CDATA[ <s:link value=\"Place Bid\" action=\"#{bidAction.placeBid}\" conversationName=\"PlaceBid\"/>]]>"
#. Tag: title
#: Conversations.xml:697
@@ -1126,28 +941,19 @@
#. Tag: para
#: Conversations.xml:699
#, no-c-format
-msgid ""
-"Workspace management is the ability to \"switch\" conversations in a single "
-"window. Seam makes workspace management completely transparent at the level "
-"of the Java code. To enable workspace management, all you need to do is:"
+msgid "Workspace management is the ability to \"switch\" conversations in a single window. Seam makes workspace management completely transparent at the level of the Java code. To enable workspace management, all you need to do is:"
msgstr ""
#. Tag: para
#: Conversations.xml:708
#, no-c-format
-msgid ""
-"Provide <emphasis>description</emphasis> text for each view id (when using "
-"JSF or Seam navigation rules) or page node (when using jPDL pageflows). This "
-"description text is displayed to the user by the workspace switchers."
+msgid "Provide <emphasis>description</emphasis> text for each view id (when using JSF or Seam navigation rules) or page node (when using jPDL pageflows). This description text is displayed to the user by the workspace switchers."
msgstr ""
#. Tag: para
#: Conversations.xml:716
#, no-c-format
-msgid ""
-"Include one or more of the standard workspace switcher JSP or facelets "
-"fragments in your pages. The standard fragments support workspace management "
-"via a drop down menu, a list of conversations, or breadcrumbs."
+msgid "Include one or more of the standard workspace switcher JSP or facelets fragments in your pages. The standard fragments support workspace management via a drop down menu, a list of conversations, or breadcrumbs."
msgstr ""
#. Tag: title
@@ -1159,12 +965,7 @@
#. Tag: para
#: Conversations.xml:727
#, no-c-format
-msgid ""
-"When you use JSF or Seam navigation rules, Seam switches to a conversation "
-"by restoring the current <literal>view-id</literal> for that conversation. "
-"The descriptive text for the workspace is defined in a file called "
-"<literal>pages.xml</literal> that Seam expects to find in the <literal>WEB-"
-"INF</literal> directory, right next to <literal>faces-config.xml</literal>:"
+msgid "When you use JSF or Seam navigation rules, Seam switches to a conversation by restoring the current <literal>view-id</literal> for that conversation. The descriptive text for the workspace is defined in a file called <literal>pages.xml</literal> that Seam expects to find in the <literal>WEB-INF</literal> directory, right next to <literal>faces-config.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1173,8 +974,7 @@
msgid ""
"<![CDATA[<pages>\n"
" <page view-id=\"/main.xhtml\">\n"
-" <description>Search hotels: #{hotelBooking.searchString}</"
-"description>\n"
+" <description>Search hotels: #{hotelBooking.searchString}</description>\n"
" </page>\n"
" <page view-id=\"/hotel.xhtml\">\n"
" <description>View hotel: #{hotel.name}</description>\n"
@@ -1187,14 +987,25 @@
" </page>\n"
" </pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/main.xhtml\">\n"
+" <description>Search hotels: #{hotelBooking.searchString}</description>\n"
+" </page>\n"
+" <page view-id=\"/hotel.xhtml\">\n"
+" <description>View hotel: #{hotel.name}</description>\n"
+" </page>\n"
+" <page view-id=\"/book.xhtml\">\n"
+" <description>Book hotel: #{hotel.name}</description>\n"
+" </page>\n"
+" <page view-id=\"/confirm.xhtml\">\n"
+" <description>Confirm: #{booking.description}</description>\n"
+" </page>\n"
+" </pages>]]>"
#. Tag: para
#: Conversations.xml:738
#, no-c-format
-msgid ""
-"Note that if this file is missing, the Seam application will continue to "
-"work perfectly! The only missing functionality will be the ability to switch "
-"workspaces."
+msgid "Note that if this file is missing, the Seam application will continue to work perfectly! The only missing functionality will be the ability to switch workspaces."
msgstr ""
#. Tag: title
@@ -1206,13 +1017,7 @@
#. Tag: para
#: Conversations.xml:748
#, no-c-format
-msgid ""
-"When you use a jPDL pageflow definition, Seam switches to a conversation by "
-"restoring the current jBPM process state. This is a more flexible model "
-"since it allows the same <literal>view-id</literal> to have different "
-"descriptions depending upon the current <literal><page></literal> "
-"node. The description text is defined by the <literal><page></literal> "
-"node:"
+msgid "When you use a jPDL pageflow definition, Seam switches to a conversation by restoring the current jBPM process state. This is a more flexible model since it allows the same <literal>view-id</literal> to have different descriptions depending upon the current <literal><page></literal> node. The description text is defined by the <literal><page></literal> node:"
msgstr ""
#. Tag: programlisting
@@ -1243,6 +1048,29 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<pageflow-definition name=\"shopping\">\n"
+"\n"
+" <start-state name=\"start\">\n"
+" <transition to=\"browse\"/>\n"
+" </start-state>\n"
+" \n"
+" <page name=\"browse\" view-id=\"/browse.xhtml\">\n"
+" <description>DVD Search: #{search.searchPattern}</description>\n"
+" <transition to=\"browse\"/>\n"
+" <transition name=\"checkout\" to=\"checkout\"/>\n"
+" </page>\n"
+" \n"
+" <page name=\"checkout\" view-id=\"/checkout.xhtml\">\n"
+" <description>Purchase: $#{cart.total}</description>\n"
+" <transition to=\"checkout\"/>\n"
+" <transition name=\"complete\" to=\"complete\"/>\n"
+" </page>\n"
+" \n"
+" <page name=\"complete\" view-id=\"/complete.xhtml\">\n"
+" <end-conversation />\n"
+" </page>\n"
+" \n"
+"</pageflow-definition>]]>"
#. Tag: title
#: Conversations.xml:764
@@ -1253,10 +1081,7 @@
#. Tag: para
#: Conversations.xml:766
#, no-c-format
-msgid ""
-"Include the following fragment in your JSP or facelets page to get a drop-"
-"down menu that lets you switch to any current conversation, or to any other "
-"page of the application:"
+msgid "Include the following fragment in your JSP or facelets page to get a drop-down menu that lets you switch to any current conversation, or to any other page of the application:"
msgstr ""
#. Tag: programlisting
@@ -1270,22 +1095,23 @@
"</h:selectOneMenu>\n"
"<h:commandButton action=\"#{switcher.select}\" value=\"Switch\"/>]]>"
msgstr ""
+"<![CDATA[<h:selectOneMenu value=\"#{switcher.conversationIdOrOutcome}\">\n"
+" <f:selectItem itemLabel=\"Find Issues\" itemValue=\"findIssue\"/>\n"
+" <f:selectItem itemLabel=\"Create Issue\" itemValue=\"editIssue\"/>\n"
+" <f:selectItems value=\"#{switcher.selectItems}\"/>\n"
+"</h:selectOneMenu>\n"
+"<h:commandButton action=\"#{switcher.select}\" value=\"Switch\"/>]]>"
#. Tag: para
#: Conversations.xml:774
#, no-c-format
-msgid ""
-"In this example, we have a menu that includes an item for each conversation, "
-"together with two additional items that let the user begin a new "
-"conversation."
+msgid "In this example, we have a menu that includes an item for each conversation, together with two additional items that let the user begin a new conversation."
msgstr ""
#. Tag: para
#: Conversations.xml:780
#, no-c-format
-msgid ""
-"Only conversations with a description (specified in <literal>pages.xml</"
-"literal>) will be included in the drop-down menu."
+msgid "Only conversations with a description (specified in <literal>pages.xml</literal>) will be included in the drop-down menu."
msgstr ""
#. Tag: title
@@ -1297,9 +1123,7 @@
#. Tag: para
#: Conversations.xml:800
#, no-c-format
-msgid ""
-"The conversation list is very similar to the conversation switcher, except "
-"that it is displayed as a table:"
+msgid "The conversation list is very similar to the conversation switcher, except that it is displayed as a table:"
msgstr ""
#. Tag: programlisting
@@ -1310,8 +1134,7 @@
" rendered=\"#{not empty conversationList}\">\n"
" <h:column>\n"
" <f:facet name=\"header\">Workspace</f:facet>\n"
-" <h:commandLink action=\"#{entry.select}\" value=\"#{entry."
-"description}\"/>\n"
+" <h:commandLink action=\"#{entry.select}\" value=\"#{entry.description}\"/>\n"
" <h:outputText value=\"[current]\" rendered=\"#{entry.current}\"/>\n"
" </h:column>\n"
" <h:column>\n"
@@ -1326,19 +1149,39 @@
" </h:column>\n"
" <h:column>\n"
" <f:facet name=\"header\">Action</f:facet>\n"
-" <h:commandButton action=\"#{entry.select}\" value=\"#{msg.Switch}\"/"
-">\n"
-" <h:commandButton action=\"#{entry.destroy}\" value=\"#{msg.Destroy}"
-"\"/>\n"
+" <h:commandButton action=\"#{entry.select}\" value=\"#{msg.Switch}\"/>\n"
+" <h:commandButton action=\"#{entry.destroy}\" value=\"#{msg.Destroy}\"/>\n"
" </h:column>\n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{conversationList}\" var=\"entry\"\n"
+" rendered=\"#{not empty conversationList}\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Workspace</f:facet>\n"
+" <h:commandLink action=\"#{entry.select}\" value=\"#{entry.description}\"/>\n"
+" <h:outputText value=\"[current]\" rendered=\"#{entry.current}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Activity</f:facet>\n"
+" <h:outputText value=\"#{entry.startDatetime}\">\n"
+" <f:convertDateTime type=\"time\" pattern=\"hh:mm a\"/>\n"
+" </h:outputText>\n"
+" <h:outputText value=\" - \"/>\n"
+" <h:outputText value=\"#{entry.lastDatetime}\">\n"
+" <f:convertDateTime type=\"time\" pattern=\"hh:mm a\"/>\n"
+" </h:outputText>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Action</f:facet>\n"
+" <h:commandButton action=\"#{entry.select}\" value=\"#{msg.Switch}\"/>\n"
+" <h:commandButton action=\"#{entry.destroy}\" value=\"#{msg.Destroy}\"/>\n"
+" </h:column>\n"
+"</h:dataTable>]]>"
#. Tag: para
#: Conversations.xml:807
#, no-c-format
-msgid ""
-"We imagine that you will want to customize this for your own application."
+msgid "We imagine that you will want to customize this for your own application."
msgstr ""
#. Tag: para
@@ -1362,10 +1205,7 @@
#. Tag: para
#: Conversations.xml:834
#, no-c-format
-msgid ""
-"Breadcrumbs are useful in applications which use a nested conversation "
-"model. The breadcrumbs are a list of links to conversations in the current "
-"conversation stack:"
+msgid "Breadcrumbs are useful in applications which use a nested conversation model. The breadcrumbs are a list of links to conversations in the current conversation stack:"
msgstr ""
#. Tag: programlisting
@@ -1374,10 +1214,13 @@
msgid ""
"<![CDATA[<ui:repeat value=\"#{conversationStack}\" var=\"entry\">\n"
" <h:outputText value=\" | \"/> \n"
-" <h:commandLink value=\"#{entry.description}\" action=\"#{entry.select}\"/"
-">\n"
+" <h:commandLink value=\"#{entry.description}\" action=\"#{entry.select}\"/>\n"
"</ui:repeat]]>"
msgstr ""
+"<![CDATA[<ui:repeat value=\"#{conversationStack}\" var=\"entry\">\n"
+" <h:outputText value=\" | \"/> \n"
+" <h:commandLink value=\"#{entry.description}\" action=\"#{entry.select}\"/>\n"
+"</ui:repeat]]>"
#. Tag: title
#: Conversations.xml:855
@@ -1388,22 +1231,13 @@
#. Tag: para
#: Conversations.xml:857
#, no-c-format
-msgid ""
-"Conversational components have one minor limitation: they cannot be used to "
-"hold bindings to JSF components. (We generally prefer not to use this "
-"feature of JSF unless absolutely necessary, since it creates a hard "
-"dependency from application logic to the view.) On a postback request, "
-"component bindings are updated during the Restore View phase, before the "
-"Seam conversation context has been restored."
+msgid "Conversational components have one minor limitation: they cannot be used to hold bindings to JSF components. (We generally prefer not to use this feature of JSF unless absolutely necessary, since it creates a hard dependency from application logic to the view.) On a postback request, component bindings are updated during the Restore View phase, before the Seam conversation context has been restored."
msgstr ""
#. Tag: para
#: Conversations.xml:865
#, no-c-format
-msgid ""
-"To work around this use an event scoped component to store the component "
-"bindings and inject it into the conversation scoped component that requires "
-"it."
+msgid "To work around this use an event scoped component to store the component bindings and inject it into the conversation scoped component that requires it."
msgstr ""
#. Tag: programlisting
@@ -1420,6 +1254,15 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"grid\")\n"
+"@Scope(ScopeType.EVENT)\n"
+"public class Grid\n"
+"{\n"
+" private HtmlPanelGrid htmlPanelGrid;\n"
+"\n"
+" // getters and setters\n"
+" ...\n"
+"}]]>"
#. Tag: programlisting
#: Conversations.xml:873
@@ -1435,25 +1278,26 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"gridEditor\")\n"
+"@Scope(ScopeType.CONVERSATION)\n"
+"public class GridEditor\n"
+"{\n"
+" @In(required=false)\n"
+" private Grid grid;\n"
+" \n"
+" ...\n"
+"}]]>"
#. Tag: para
#: Conversations.xml:875
#, no-c-format
-msgid ""
-"Also, you can't inject a conversation scoped component into an event scoped "
-"component which you bind a JSF control to. This includes Seam built in "
-"components like <literal>facesMessages</literal>."
+msgid "Also, you can't inject a conversation scoped component into an event scoped component which you bind a JSF control to. This includes Seam built in components like <literal>facesMessages</literal>."
msgstr ""
#. Tag: para
#: Conversations.xml:881
#, no-c-format
-msgid ""
-"Alternatively, you can access the JSF component tree through the implicit "
-"<literal>uiComponent</literal> handle. The following example accesses "
-"<literal>getRowIndex()</literal>of the <literal>UIData</literal> component "
-"which backs the data table during iteration, it prints the current row "
-"number:"
+msgid "Alternatively, you can access the JSF component tree through the implicit <literal>uiComponent</literal> handle. The following example accesses <literal>getRowIndex()</literal>of the <literal>UIData</literal> component which backs the data table during iteration, it prints the current row number:"
msgstr ""
#. Tag: programlisting
@@ -1461,20 +1305,25 @@
#, no-c-format
msgid ""
"<![CDATA[\n"
-"<h:dataTable id=\"lineItemTable\" var=\"lineItem\" value=\"#{orderHome."
-"lineItems}\">\n"
+"<h:dataTable id=\"lineItemTable\" var=\"lineItem\" value=\"#{orderHome.lineItems}\">\n"
" <h:column>\n"
" Row: #{uiComponent['lineItemTable'].rowIndex}\n"
" </h:column>\n"
" ...\n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[\n"
+"<h:dataTable id=\"lineItemTable\" var=\"lineItem\" value=\"#{orderHome.lineItems}\">\n"
+" <h:column>\n"
+" Row: #{uiComponent['lineItemTable'].rowIndex}\n"
+" </h:column>\n"
+" ...\n"
+"</h:dataTable>]]>"
#. Tag: para
#: Conversations.xml:890
#, no-c-format
-msgid ""
-"JSF UI components are available with their client identifier in this map."
+msgid "JSF UI components are available with their client identifier in this map."
msgstr ""
#. Tag: title
@@ -1486,61 +1335,37 @@
#. Tag: para
#: Conversations.xml:899
#, no-c-format
-msgid ""
-"A general discussion of concurrent calls to Seam components can be found in "
-"<xref linkend=\"concurrency\"/>. Here we will discuss the most common "
-"situation in which you will encounter concurrency — accessing "
-"conversational components from AJAX requests. We're going to discuss the "
-"options that a Ajax client library should provide to control events "
-"originating at the client — and we'll look at the options RichFaces "
-"gives you."
+msgid "A general discussion of concurrent calls to Seam components can be found in <xref linkend=\"concurrency\"/>. Here we will discuss the most common situation in which you will encounter concurrency — accessing conversational components from AJAX requests. We're going to discuss the options that a Ajax client library should provide to control events originating at the client — and we'll look at the options RichFaces gives you."
msgstr ""
#. Tag: para
#: Conversations.xml:909
#, no-c-format
-msgid ""
-"Conversational components don't allow real concurrent access therefore Seam "
-"queues each request to process them serially. This allows each request to be "
-"executed in a deterministic fashion. However, a simple queue isn't that "
-"great — firstly, if a method is, for some reason, taking a very long "
-"time to complete, running it over and over again whenever the client "
-"generates a request is bad idea (potential for Denial of Service attacks), "
-"and, secondly, AJAX is often to used to provide a quick status update to the "
-"user, so continuing to run the action after a long time isn't useful."
+msgid "Conversational components don't allow real concurrent access therefore Seam queues each request to process them serially. This allows each request to be executed in a deterministic fashion. However, a simple queue isn't that great — firstly, if a method is, for some reason, taking a very long time to complete, running it over and over again whenever the client generates a request is bad idea (potential for Denial of Service attacks), and, secondly, AJAX is often to used to provide a quick status update to the user, so continuing to run the action after a long time isn't useful."
msgstr ""
#. Tag: para
#: Conversations.xml:921
#, no-c-format
-msgid ""
-"Therefore, when you are working inside a long running conversation, Seam "
-"queues the action event for a period of time (the concurrent request "
-"timeout); if it can't process the event in time, it creates a temporary "
-"conversation and prints out a message to the user to let them know what's "
-"going on. It's therefore very important not to flood the server with AJAX "
-"events!"
+msgid "Therefore, when you are working inside a long running conversation, Seam queues the action event for a period of time (the concurrent request timeout); if it can't process the event in time, it creates a temporary conversation and prints out a message to the user to let them know what's going on. It's therefore very important not to flood the server with AJAX events!"
msgstr ""
#. Tag: para
#: Conversations.xml:930
#, no-c-format
-msgid ""
-"We can set a sensible default for the concurrent request timeout (in ms) in "
-"components.xml:"
+msgid "We can set a sensible default for the concurrent request timeout (in ms) in components.xml:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:935
#, no-c-format
msgid "<![CDATA[<core:manager concurrent-request-timeout=\"500\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<core:manager concurrent-request-timeout=\"500\" />]]>"
#. Tag: para
#: Conversations.xml:937
#, no-c-format
-msgid ""
-"We can also fine tune the concurrent request timeout on a page-by-page basis:"
+msgid "We can also fine tune the concurrent request timeout on a page-by-page basis:"
msgstr ""
#. Tag: programlisting
@@ -1552,29 +1377,21 @@
" login-required=\"true\"\n"
" concurrent-request-timeout=\"2000\" />]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/book.xhtml\" \n"
+" conversation-required=\"true\" \n"
+" login-required=\"true\"\n"
+" concurrent-request-timeout=\"2000\" />]]>"
#. Tag: para
#: Conversations.xml:944
#, no-c-format
-msgid ""
-"So far we've discussed AJAX requests which appear serial to the user - the "
-"client tells the server that an event has occur, and then rerenders part of "
-"the page based on the result. This approach is great when the AJAX request "
-"is lightweight (the methods called are simple e.g. calculating the sum of a "
-"column of numbers). But what if we need to do a complex computation thats "
-"going to take a minute?"
+msgid "So far we've discussed AJAX requests which appear serial to the user - the client tells the server that an event has occur, and then rerenders part of the page based on the result. This approach is great when the AJAX request is lightweight (the methods called are simple e.g. calculating the sum of a column of numbers). But what if we need to do a complex computation thats going to take a minute?"
msgstr ""
#. Tag: para
#: Conversations.xml:953
#, no-c-format
-msgid ""
-"For heavy computation we should use a poll based approach — the client "
-"sends an AJAX request to the server, which causes action to be executed "
-"asynchronously on the server (the response to the client is immediate) and "
-"the client then polls the server for updates. This is good approach when you "
-"have a long-running action for which it is important that every action "
-"executes (you don't want some to timeout)."
+msgid "For heavy computation we should use a poll based approach — the client sends an AJAX request to the server, which causes action to be executed asynchronously on the server (the response to the client is immediate) and the client then polls the server for updates. This is good approach when you have a long-running action for which it is important that every action executes (you don't want some to timeout)."
msgstr ""
#. Tag: title
@@ -1586,41 +1403,25 @@
#. Tag: para
#: Conversations.xml:965
#, no-c-format
-msgid ""
-"Well first, you need to decide whether you want to use the simpler \"serial"
-"\" request or whether you want to use a polling approach."
+msgid "Well first, you need to decide whether you want to use the simpler \"serial\" request or whether you want to use a polling approach."
msgstr ""
#. Tag: para
#: Conversations.xml:970
#, no-c-format
-msgid ""
-"If you go for a \"serial\" requests, then you need to estimate how long your "
-"request will take to complete - is it much shorter than the concurrent "
-"request timeout? If not, you probably want to alter the concurrent request "
-"timeout for this page (as discussed above). You probably want a queue on the "
-"client side to prevent flooding the server with requests. If the event "
-"occurs often (e.g. a keypress, onblur of input fields) and immediate update "
-"of the client is not a priority you should set a request delay on the client "
-"side. When working out your request delay, factor in that the event may also "
-"be queued on the server side."
+msgid "If you go for a \"serial\" requests, then you need to estimate how long your request will take to complete - is it much shorter than the concurrent request timeout? If not, you probably want to alter the concurrent request timeout for this page (as discussed above). You probably want a queue on the client side to prevent flooding the server with requests. If the event occurs often (e.g. a keypress, onblur of input fields) and immediate update of the client is not a priority you should set a request delay on the client side. When working out your request delay, factor in that the event may also be queued on the server side."
msgstr ""
#. Tag: para
#: Conversations.xml:983
#, no-c-format
-msgid ""
-"Finally, the client library may provide an option to abort unfinished "
-"duplicate requests in favor of the most recent."
+msgid "Finally, the client library may provide an option to abort unfinished duplicate requests in favor of the most recent."
msgstr ""
#. Tag: para
#: Conversations.xml:988
#, no-c-format
-msgid ""
-"Using a poll-style design requires less fine-tuning. You just mark your "
-"action method <literal>@Asynchronous</literal> and decide on a polling "
-"interval:"
+msgid "Using a poll-style design requires less fine-tuning. You just mark your action method <literal>@Asynchronous</literal> and decide on a polling interval:"
msgstr ""
#. Tag: programlisting
@@ -1642,6 +1443,20 @@
" return total;\n"
"}]]>"
msgstr ""
+"<![CDATA[int total;\n"
+"\n"
+"// This method is called when an event occurs on the client\n"
+"// It takes a really long time to execute\n"
+"@Asynchronous \n"
+"public void calculateTotal() {\n"
+" total = someReallyComplicatedCalculation();\n"
+"}\n"
+"\n"
+"// This method is called as the result of the poll\n"
+"// It's very quick to execute\n"
+"public int getTotal() {\n"
+" return total;\n"
+"}]]>"
#. Tag: title
#: Conversations.xml:998
@@ -1652,39 +1467,31 @@
#. Tag: para
#: Conversations.xml:1000
#, no-c-format
-msgid ""
-"However carefully you design your application to queue concurrent requests "
-"to your conversational component, there is a risk that the server will "
-"become overloaded and be unable to process all the requests before the "
-"request will have to wait longer than the <literal>concurrent-request-"
-"timeout</literal>. In this case Seam will throw a "
-"<literal>ConcurrentRequestTimeoutException</literal> which can be handled in "
-"<literal>pages.xml</literal>. We recommend sending an HTTP 503 error:"
+msgid "However carefully you design your application to queue concurrent requests to your conversational component, there is a risk that the server will become overloaded and be unable to process all the requests before the request will have to wait longer than the <literal>concurrent-request-timeout</literal>. In this case Seam will throw a <literal>ConcurrentRequestTimeoutException</literal> which can be handled in <literal>pages.xml</literal>. We recommend sending an HTTP 503 error:"
msgstr ""
#. Tag: programlisting
#: Conversations.xml:1011
#, no-c-format
msgid ""
-"<![CDATA[ <exception class=\"org.jboss.seam."
-"ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
" <http-error error-code=\"503\" />\n"
" </exception>]]>"
msgstr ""
+"<![CDATA[ <exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
+" <http-error error-code=\"503\" />\n"
+" </exception>]]>"
#. Tag: title
#: Conversations.xml:1014
#, no-c-format
msgid "503 Service Unavailable (HTTP/1.1 RFC)"
-msgstr ""
+msgstr "503 Service Unavailable (HTTP/1.1 RFC)"
#. Tag: para
#: Conversations.xml:1016
#, no-c-format
-msgid ""
-"The server is currently unable to handle the request due to a temporary "
-"overloading or maintenance of the server. The implication is that this is a "
-"temporary condition which will be alleviated after some delay."
+msgid "The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay."
msgstr ""
#. Tag: para
@@ -1697,25 +1504,24 @@
#: Conversations.xml:1028
#, no-c-format
msgid ""
-"<![CDATA[<exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException"
-"\" logLevel=\"trace\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message>The server is too busy to process your request, please try "
-"again later</message>\n"
+" <message>The server is too busy to process your request, please try again later</message>\n"
" </redirect>\n"
"</exception>]]>"
msgstr ""
+"<![CDATA[<exception class=\"org.jboss.seam.ConcurrentRequestTimeoutException\" logLevel=\"trace\">\n"
+" <end-conversation/>\n"
+" <redirect view-id=\"/error.xhtml\">\n"
+" <message>The server is too busy to process your request, please try again later</message>\n"
+" </redirect>\n"
+"</exception>]]>"
#. Tag: para
#: Conversations.xml:1030
#, no-c-format
-msgid ""
-"ICEfaces, RichFaces Ajax and Seam Remoting can all handle HTTP error codes. "
-"Seam Remoting will pop up a dialog box showing the HTTP error and ICEfaces "
-"will indicate the error in it's connection status component. RichFaces Ajax "
-"provides the most complete support for handling HTTP errors by providing a "
-"user definable callback. For example, to show the error message to the user:"
+msgid "ICEfaces, RichFaces Ajax and Seam Remoting can all handle HTTP error codes. Seam Remoting will pop up a dialog box showing the HTTP error and ICEfaces will indicate the error in it's connection status component. RichFaces Ajax provides the most complete support for handling HTTP errors by providing a user definable callback. For example, to show the error message to the user:"
msgstr ""
#. Tag: programlisting
@@ -1728,6 +1534,11 @@
" };\n"
"</script>]]>"
msgstr ""
+"<![CDATA[<script type=\"text/javascript\">\n"
+" A4J.AJAX.onError = function(req,status,message) { \n"
+" alert(\"message\"); \n"
+" };\n"
+"</script>]]>"
#. Tag: title
#: Conversations.xml:1044
@@ -1738,66 +1549,42 @@
#. Tag: para
#: Conversations.xml:1046
#, no-c-format
-msgid ""
-"RichFaces Ajax is the AJAX library most commonly used with Seam, and "
-"provides all the controls discussed above:"
+msgid "RichFaces Ajax is the AJAX library most commonly used with Seam, and provides all the controls discussed above:"
msgstr ""
#. Tag: para
#: Conversations.xml:1053
#, no-c-format
-msgid ""
-"<literal>eventsQueue</literal> — provide a queue in which events are "
-"placed. All events are queued and requests are sent to the server serially. "
-"This is useful if the request can to the server can take some time to "
-"execute (e.g. heavy computation, retrieving information from a slow source) "
-"as the server isn't flooded."
+msgid "<literal>eventsQueue</literal> — provide a queue in which events are placed. All events are queued and requests are sent to the server serially. This is useful if the request can to the server can take some time to execute (e.g. heavy computation, retrieving information from a slow source) as the server isn't flooded."
msgstr ""
#. Tag: para
#: Conversations.xml:1063
#, no-c-format
-msgid ""
-"<literal>ignoreDupResponses</literal> — ignore the response produced "
-"by the request if a more recent 'similar' request is already in the queue. "
-"ignoreDupResponses=\"true\" does <emphasis>not cancel</emphasis> the the "
-"processing of the request on the server side — just prevents "
-"unnecessary updates on the client side."
+msgid "<literal>ignoreDupResponses</literal> — ignore the response produced by the request if a more recent 'similar' request is already in the queue. ignoreDupResponses=\"true\" does <emphasis>not cancel</emphasis> the the processing of the request on the server side — just prevents unnecessary updates on the client side."
msgstr ""
#. Tag: para
#: Conversations.xml:1070
#, no-c-format
-msgid ""
-"This option should be used with care with Seam's conversations as it allows "
-"multiple concurrent requests to be made."
+msgid "This option should be used with care with Seam's conversations as it allows multiple concurrent requests to be made."
msgstr ""
#. Tag: para
#: Conversations.xml:1076
#, no-c-format
-msgid ""
-"<literal>requestDelay</literal> — defines the time (in ms.) that the "
-"request will be remain on the queue. If the request has not been processed "
-"by after this time the request will be sent (regardless of whether a "
-"response has been received) or discarded (if there is a more recent similar "
-"event on the queue)."
+msgid "<literal>requestDelay</literal> — defines the time (in ms.) that the request will be remain on the queue. If the request has not been processed by after this time the request will be sent (regardless of whether a response has been received) or discarded (if there is a more recent similar event on the queue)."
msgstr ""
#. Tag: para
#: Conversations.xml:1083
#, no-c-format
-msgid ""
-"This option should be used with care with Seam's conversations as it allows "
-"multiple concurrent requests to be made. You need to be sure that the delay "
-"you set (in combination with the concurrent request timeout) is longer than "
-"the action will take to execute."
+msgid "This option should be used with care with Seam's conversations as it allows multiple concurrent requests to be made. You need to be sure that the delay you set (in combination with the concurrent request timeout) is longer than the action will take to execute."
msgstr ""
#. Tag: para
#: Conversations.xml:1091
#, no-c-format
-msgid ""
-"<literal><a:poll reRender=\"total\" interval=\"1000\" /></literal> "
-"— Polls the server, and rerenders an area as needed"
+msgid "<literal><a:poll reRender=\"total\" interval=\"1000\" /></literal> — Polls the server, and rerenders an area as needed"
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-06 21:25+0100\n"
+"PO-Revision-Date: 2008-12-16 12:18+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -35,7 +35,7 @@
#: Drools.xml:15
#, no-c-format
msgid "The first step is to make an instance of <literal>org.drools.RuleBase</literal> available in a Seam context variable. For testing purposes, Seam provides a built-in component that compiles a static set of rules from the classpath. You can install this component via <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Il primo passo è creare un'istanza di <literal>org.drools.RuleBase</literal> disponibile in una variabile del contesto di Seam. Per testare Seam fornisce un componente interno che compila un set statico di regole dal classpath. Puoi installare questo componente tramite <literal>components.xml</literal>:"
#. Tag: programlisting
#: Drools.xml:22
@@ -57,7 +57,7 @@
#: Drools.xml:24
#, no-c-format
msgid "This component compiles rules from a set of <literal>.drl</literal> files and caches an instance of <literal>org.drools.RuleBase</literal> in the Seam <literal>APPLICATION</literal> context. Note that it is quite likely that you will need to install multiple rule bases in a rule-driven application."
-msgstr ""
+msgstr "Questo componente compila le regole da un set di file <literal>.drl</literal> e mette in cache un'istanza di <literal>org.drools.RuleBase</literal> nel contesto <literal>APPLICATION</literal> di Seam. Notare che è abbastanza probabile che in un'applicazione guidata dalle regole occorra installare altre basi di regole."
#. Tag: para
#: Drools.xml:32
@@ -85,7 +85,7 @@
#: Drools.xml:39
#, no-c-format
msgid "In most rules-driven applications, rules need to be dynamically deployable, so a production application will want to use a Drools RuleAgent to manage the RuleBase. The RuleAgent can connect to a Drools rule server (BRMS) or hot deploy rules packages from a local file repository. The RulesAgent-managed RuleBase is also configurable in <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Nella maggior parte delle applicazioni guidate dalle regole, le regole devono essere dinamicamente deployabili, e quindi un'applicazione in produzione dovrà usare un Drools RuleAgent per gestire la RuleBase. Il RuleAgent può connettersi al server di regole Drool (BRMS) od eseguire l'hot deploy dei pacchetti di regole dal repository locale. La RuleBase gestita dal RulesAgen è configurabile in <literal>components.xml</literal>:"
#. Tag: programlisting
#: Drools.xml:47
@@ -101,7 +101,7 @@
#: Drools.xml:49
#, no-c-format
msgid "The properties file contains properties specific to the RulesAgent. Here is an example configuration file from the Drools example distribution."
-msgstr ""
+msgstr "Il file delle proprietà contiene proprietà specifiche per RulesAgent. Ecco un file di configurazione d'esempio proveniente dalla distribuzione Drools."
#. Tag: programlisting
#: Drools.xml:52
@@ -113,12 +113,17 @@
"poll=30\n"
"name=insuranceconfig"
msgstr ""
+"newInstance=true\n"
+"url=http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/package/org.acme.insurance/fmeyer\n"
+"localCacheDir=/Users/fernandomeyer/projects/jbossrules/drools-examples/drools-examples-brms/cache\n"
+"poll=30\n"
+"name=insuranceconfig"
#. Tag: para
#: Drools.xml:55
#, no-c-format
msgid "It is also possible to configure the options on the component directly, bypassing the configuration file."
-msgstr ""
+msgstr "E' anche possibile configurare le opzioni derettamente sul componente, bypassando il file di configurazione."
#. Tag: programlisting
#: Drools.xml:57
@@ -140,7 +145,7 @@
#: Drools.xml:59
#, no-c-format
msgid "Next, we need to make an instance of <literal>org.drools.WorkingMemory</literal> available to each conversation. (Each <literal>WorkingMemory</literal> accumulates facts relating to the current conversation.)"
-msgstr ""
+msgstr "Successivamente occorre rendere disponibile ad ogni conversazione un'istanza di <literal>org.drools.WorkingMemory</literal>. (Ogni <literal>WorkingMemory</literal> accumula fatti relativi alla conversazione corrente.)"
#. Tag: programlisting
#: Drools.xml:65
@@ -152,7 +157,7 @@
#: Drools.xml:67
#, no-c-format
msgid "Notice that we gave the <literal>policyPricingWorkingMemory</literal> a reference back to our rule base via the <literal>ruleBase</literal> configuration property."
-msgstr ""
+msgstr "Notare che abbiamo dato a <literal>policyPricingWorkingMemory</literal> un riferimento alla base di regole tramite la proprietà di configurazione <literal>ruleBase</literal>."
#. Tag: title
#: Drools.xml:76
@@ -164,7 +169,7 @@
#: Drools.xml:78
#, no-c-format
msgid "We can now inject our <literal>WorkingMemory</literal> into any Seam component, assert facts, and fire rules:"
-msgstr ""
+msgstr "Ora possiamo iniettare la <literal>WorkingMemory</literal> in un qualsiasi componente di Seam, asserire i fatti e lanciare le regole:"
#. Tag: programlisting
#: Drools.xml:83
@@ -204,7 +209,7 @@
#: Drools.xml:90
#, no-c-format
msgid "You can even allow a rule base to act as a jBPM action handler, decision handler, or assignment handler—in either a pageflow or business process definition."
-msgstr ""
+msgstr "Si può anche consentire alla base di regole di agire come action handler di jBPM, decision handler, o assignment handler— sia in una definizione di pageflow sia in un processo di business."
#. Tag: programlisting
#: Drools.xml:96
@@ -266,13 +271,13 @@
#: Drools.xml:98
#, no-c-format
msgid "The <literal><assertObjects></literal> element specifies EL expressions that return an object or collection of objects to be asserted as facts into the <literal>WorkingMemory</literal>."
-msgstr ""
+msgstr "L'elemento <literal><assertObjects></literal> specifica le espressioni EL che restituiscono un oggetto od una collezione di oggetti da asserire come fatti nella <literal>WorkingMemory</literal>."
#. Tag: para
#: Drools.xml:104
#, no-c-format
msgid "There is also support for using Drools for jBPM task assignments:"
-msgstr ""
+msgstr "Esiste anche il supporto per l'uso di Drools per le assegnazioni dei task in jBPM:"
#. Tag: programlisting
#: Drools.xml:108
@@ -310,11 +315,12 @@
" <transition name=\"approved\" to=\"approved\"/>\n"
"</task-node>]]>"
+# rivedere la frase.
#. Tag: para
#: Drools.xml:110
#, no-c-format
msgid "Certain objects are available to the rules as Drools globals, namely the jBPM <literal>Assignable</literal>, as <literal>assignable</literal> and a Seam <literal>Decision</literal> object, as <literal>decision</literal>. Rules which handle decisions should call <literal>decision.setOutcome(\"result\")</literal> to determine the result of the decision. Rules which perform assignments should set the actor id using the <literal>Assignable</literal>."
-msgstr ""
+msgstr "Alcuni oggetti sono consultabili dalle regole come Drools globals, chiamate <literal>Assignable</literal> in jBPM, come <literal>assignable</literal> ed oggetto <literal>Decision</literal> in Seam, come <literal>decision</literal>. Le regole che gestiscono le decisioni dovrebbero chiamare <literal>decision.setOutcome(\"result\")</literal> per determinare il risultato della decisione. Le regole che eseguono assegnazioni dovrebbero impostare l'actor id usando <literal>Assignable</literal>."
#. Tag: programlisting
#: Drools.xml:119
@@ -382,17 +388,17 @@
#: Drools.xml:124
#, no-c-format
msgid "You can find out more about Drools at <ulink url=\"http://www.drools.org\"></ulink>"
-msgstr ""
+msgstr "Puoi trovare altre informazioni su Drools all'indirizzo <ulink url=\"http://www.drools.org\"></ulink>"
#. Tag: para
#: Drools.xml:131
#, no-c-format
msgid "Seam comes with enough of Drools' dependencies to implement some simple rules. If you want to add extra capabilities to Drools you should download the full distribution and add in extra dependencies as needed."
-msgstr ""
+msgstr "Seam viene fornito con dipendenze Drools sufficienti per implementare alcune regole semplici. Per aggiungere ulteriori funzionalità a Drools occorre scaricare la distribuzione completa ed aggiungere le dipendenze necessarie."
#. Tag: para
#: Drools.xml:140
#, no-c-format
msgid "Drools comes with MVEL compiled for Java 1.4, which is compatible with Java 1.4, Java 5 and Java 6. You may want to change your MVEL jar with one compiled for the version of Java you are using"
-msgstr ""
+msgstr "Drools viene rilasciato con MVEL compilato per Java 1.4, che è compatibile con Java 1.4, Java 5 e Java 6. Puoi cambiare il jar MVEL con quello compilato per la tua versione di Java."
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 22:28:44 UTC (rev 9785)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-16 11:19:03 UTC (rev 9786)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-15 23:17+0100\n"
+"PO-Revision-Date: 2008-12-16 11:18+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -415,7 +415,7 @@
#: Jbpm.xml:253
#, no-c-format
msgid "Of course, we still need to define what happens if a request originates from a page rendered during a pageflow, and the conversation with the pageflow no longer exists. In this case, the <literal>no-conversation-view-id</literal> declaration goes into the pageflow definition:"
-msgstr ""
+msgstr "Occorre ancora definire cosa succede se una richiesta ha origine da una pagina generata durante un pageflow mentre la conversazione con il pageflow non esiste più. In questo caso la dichiarazione <literal>no-conversation-view-id</literal> va dentro la definizione del pageflow:"
#. Tag: programlisting
#: Jbpm.xml:261
@@ -461,7 +461,7 @@
#: Jbpm.xml:278
#, no-c-format
msgid "We need to install the Seam jBPM-related components, and place the pageflow definitions (using the standard <literal>.jpdl.xml</literal> extension) inside a Seam archive (an archive which contains a <literal>seam.properties</literal> file):"
-msgstr ""
+msgstr "Vanno installati i componenti di Seam relativi a jBPM e vanno collocate le definizione dei pageflow (usando l'estensione standard <literal>.jpdl.xml</literal>) dentro l'archivio Seam (un archivio che contiene un file <literal>seam.properties</literal>):"
#. Tag: programlisting
#: Jbpm.xml:285
@@ -473,7 +473,7 @@
#: Jbpm.xml:287
#, no-c-format
msgid "We can also explicitly tell Seam where to find our pageflow definition. We specify this in <literal>components.xml</literal>:"
-msgstr ""
+msgstr "Possiamo anche comunicare esplicitamente a Seam dove trovare le definizioni dei pageflow. Questo viene specificato dentro <literal>components.xml</literal>:"
#. Tag: programlisting
#: Jbpm.xml:292
@@ -597,7 +597,7 @@
#: Jbpm.xml:335
#, no-c-format
msgid "Each <literal><page></literal> node represents a state where the system is waiting for user input:"
-msgstr ""
+msgstr "Ogni nodo <literal><page></literal> rappresenta uno stato in cui il sistema aspetta input da parte dell'utente:"
#. Tag: programlisting
#: Jbpm.xml:340
@@ -627,7 +627,7 @@
#: Jbpm.xml:351
#, no-c-format
msgid "The transition name is the name of a JSF outcome triggered by clicking a command button or command link in <literal>numberGuess.jsp</literal>."
-msgstr ""
+msgstr "Il nome della transizione è il nome dell'esito JSF lanciato cliccando un command button od un command link in <literal>numberGuess.jsp</literal>."
#. Tag: programlisting
#: Jbpm.xml:356
@@ -682,7 +682,7 @@
#: Jbpm.xml:384
#, no-c-format
msgid "It is even possible to have the button call an action method, in which case the action outcome will determine the transition to be taken:"
-msgstr ""
+msgstr "E' anche possibile che il pulsante chiami un action method, nel qual caso l'esito dell'azione determinerà la transizione da prendere:"
#. Tag: programlisting
#: Jbpm.xml:389
@@ -740,7 +740,7 @@
#: Jbpm.xml:411
#, no-c-format
msgid "A decision is made by evaluating a JSF EL expression in the Seam contexts."
-msgstr ""
+msgstr "Una decisione viene presa valutando un'espressione EL JSF nei contesti di Seam."
#. Tag: title
#: Jbpm.xml:418
@@ -772,7 +772,7 @@
#: Jbpm.xml:428
#, no-c-format
msgid "Optionally, we can end a task, specify a jBPM <literal>transition</literal> name. In this case, Seam will signal the end of the current task in the overarching business process."
-msgstr ""
+msgstr "Opzionalmente possiamo terminare un task specificando un nome alla <literal>transition</literal> jBPM. In questo modo Seam segnalerà la fine del task corrente al processo di business sottostante."
#. Tag: programlisting
#: Jbpm.xml:434
@@ -932,7 +932,7 @@
#: Jbpm.xml:534
#, no-c-format
msgid "We always need to know what user is currently logged in. jBPM \"knows\" users by their <emphasis>actor id</emphasis> and <emphasis>group actor ids</emphasis>. We specify the current actor ids using the built in Seam component named <literal>actor</literal>:"
-msgstr ""
+msgstr "Bisogna sempre sapere quale utente è attualmente loggato. jBPM \"riconosce\" gli utenti dal loro <emphasis>actor id</emphasis> e dai <emphasis>group actor id</emphasis>. Specificheremo gli attuali actor id usando il componente interno di Seam chiamato <literal>actor</literal>:"
#. Tag: programlisting
#: Jbpm.xml:542
16 years
- 1
- 0
Seam SVN: r9785 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-15 17:28:44 -0500 (Mon, 15 Dec 2008)
New Revision: 9785
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 17:36:40 UTC (rev 9784)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 22:28:44 UTC (rev 9785)
@@ -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 18:16+0100\n"
+"PO-Revision-Date: 2008-12-15 23:17+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -367,7 +367,7 @@
#: Jbpm.xml:219
#, no-c-format
msgid "In this case, the <literal>no-conversation-view-id</literal> declaration goes in <literal>pages.xml</literal>. It tells Seam to redirect to a different page if a request originates from a page rendered during a conversation, and that conversation no longer exists:"
-msgstr ""
+msgstr "In questo casola dichiarazione <literal>no-conversation-view-id</literal> va in <literal>pages.xml</literal>. Questa dice a Seam di reindirizzare ad una pagina differente se la richiesta proviene da una pagina generata durante una conversazione, e questa conversazione non esiste più:"
#. Tag: programlisting
#: Jbpm.xml:227
@@ -383,7 +383,7 @@
#: Jbpm.xml:229
#, no-c-format
msgid "On the other hand, in the stateful model, backbuttoning is interpreted as an undefined transition back to a previous state. Since the stateful model enforces a defined set of transitions from the current state, back buttoning is by default disallowed in the stateful model! Seam transparently detects the use of the back button, and blocks any attempt to perform an action from a previous, \"stale\" page, and simply redirects the user to the \"current\" page (and displays a faces message). Whether you consider this a feature or a limitation of the stateful model depends upon your point of view: as an application developer, it is a feature; as a user, it might be frustrating! You can enable backbutton navigation from a particular page node by setting <literal>back=\"enabled\"</literal>."
-msgstr ""
+msgstr "Dall'altro lato, nel modello stateful, il pulsante indietro viene interpretato come una transizione indietro ad un precedente stato. Poiché il modello stateful costringe ad un set di transizioni dallo stato corrente, il pulsante indietro viene di default disabilitato nel modello stateful! Seam rileva in modo trasparente l'uso del pulsante indietro e blocca qualsiasi tentativo di eseguire un'azione da una pagina precedente \"in stallo\", e reindirizza l'utente alla pagina \"corrente\" (mostrando un messagio faces). Se consideri questa una funzionalità oppure una limitazione del modello stateful dipende dal tuo punto di vista: come sviluppatore è una funzionalità; come utente può essere frustrante! Puoi abilitare da un particolare nodo di pagina la navigazione con il pulsante indietro impostando <literal>back=\"enabled\"</literal>."
#. Tag: programlisting
#: Jbpm.xml:245
@@ -409,7 +409,7 @@
#: Jbpm.xml:247
#, no-c-format
msgid "This allows backbuttoning <emphasis>from</emphasis> the <literal>checkout</literal> state to <emphasis>any previous state!</emphasis>"
-msgstr ""
+msgstr "Questo permette l'uso del pulsante indietro <emphasis>dallo</emphasis> stato <literal>checkout</literal> a <emphasis>qualsiasi altro stato!</emphasis>"
#. Tag: para
#: Jbpm.xml:253
@@ -1006,7 +1006,7 @@
#: Jbpm.xml:565
#, no-c-format
msgid "When a process reaches a task node, task instances are created. These must be assigned to users or user groups. We can either hardcode our actor ids, or delegate to a Seam component:"
-msgstr ""
+msgstr "Quando un processo raggiunge un task node, vengono create istante di compiti. Queste devono essere assegnate a utenti o gruppi di utenti. Possiamo codificare gli id degli attori (actor id) o delegare ad un componente Seam:"
#. Tag: programlisting
#: Jbpm.xml:571
@@ -1020,11 +1020,12 @@
" <assignment actor-id=\"#{actor.id}\"/>\n"
"</task>]]>"
+# va bene pool = gruppo ?
#. Tag: para
#: Jbpm.xml:573
#, no-c-format
msgid "In this case, we have simply assigned the task to the current user. We can also assign tasks to a pool:"
-msgstr ""
+msgstr "In questo caso abbiamo semplicemente assegnato il task all'utente corrente. Possiamo anche assegnare compiti ad un pool (gruppo):"
#. Tag: programlisting
#: Jbpm.xml:578
@@ -1044,11 +1045,12 @@
msgid "Task lists"
msgstr "Liste di task"
+# pooled task =?
#. Tag: para
#: Jbpm.xml:585
#, no-c-format
msgid "Several built-in Seam components make it easy to display task lists. The <literal>pooledTaskInstanceList</literal> is a list of pooled tasks that users may assign to themselves:"
-msgstr ""
+msgstr "Parecchi componenti incorporati in Seam consentono facilmente di visualizzare liste di compiti. <literal>pooledTaskInstanceList</literal> è una lista di compiti che gli utenti possono assegnare a se stessi:"
#. Tag: programlisting
#: Jbpm.xml:591
@@ -1078,7 +1080,7 @@
#: Jbpm.xml:593
#, no-c-format
msgid "Note that instead of <literal><s:link></literal> we could have used a plain JSF <literal><h:commandLink></literal>:"
-msgstr ""
+msgstr "Notare che invece di <literal><s:link></literal> avremmo potuto usare un semplice JSF<literal><h:commandLink></literal>:"
#. Tag: programlisting
#: Jbpm.xml:598
@@ -1096,13 +1098,13 @@
#: Jbpm.xml:600
#, no-c-format
msgid "The <literal>pooledTask</literal> component is a built-in component that simply assigns the task to the current user."
-msgstr ""
+msgstr "Il componente <literal>pooledTask</literal> è un componente incorporato che semplicemente assegna il task all'utente corrente."
#. Tag: para
#: Jbpm.xml:605
#, no-c-format
msgid "The <literal>taskInstanceListForType</literal> component includes tasks of a particular type that are assigned to the current user:"
-msgstr ""
+msgstr "Il componente <literal>taskInstanceListForType</literal> include i task di un particolare tipo che sono stati assegnati all'utente corrente:"
#. Tag: programlisting
#: Jbpm.xml:610
@@ -1138,7 +1140,7 @@
#: Jbpm.xml:617
#, no-c-format
msgid "To begin work on a task, we use either <literal>@StartTask</literal> or <literal>@BeginTask</literal> on the listener method:"
-msgstr ""
+msgstr "Per iniziare a lavorare ad un compito, si può usare o <literal>@StartTask</literal> o <literal>@BeginTask</literal> sul metodo listener."
#. Tag: programlisting
#: Jbpm.xml:622
16 years
- 1
- 0
Seam SVN: r9784 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
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(a)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[(a)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(a)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(a)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[(a)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[(a)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(a)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(a)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(a)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(a)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(a)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(a)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"
+"}]]>"
+
16 years
- 1
- 0
Seam SVN: r9783 - trunk.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-15 10:50:47 -0500 (Mon, 15 Dec 2008)
New Revision: 9783
Modified:
trunk/changelog.txt
Log:
update changelog
Modified: trunk/changelog.txt
===================================================================
--- trunk/changelog.txt 2008-12-15 15:48:55 UTC (rev 9782)
+++ trunk/changelog.txt 2008-12-15 15:50:47 UTC (rev 9783)
@@ -11,6 +11,7 @@
* [JBSEAM-3819] - grammar in http://docs.jboss.com/seam/latest/reference/en-US/html/tutorial.html
* [JBSEAM-3830] - e:cell doesn't support null values
* [JBSEAM-3834] - ClassCastException in Cell Column With Empty Date
+ * [JBSEAM-3843] - Seamspace example - pages.xml uses logLevel attribute
Release Notes - Seam - Version 2.1.1.CR2
16 years
- 1
- 0
Seam SVN: r9782 - tags/JBoss_Seam_2_1_1_GA.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-15 10:48:55 -0500 (Mon, 15 Dec 2008)
New Revision: 9782
Modified:
tags/JBoss_Seam_2_1_1_GA/changelog.txt
Log:
update changelog
Modified: tags/JBoss_Seam_2_1_1_GA/changelog.txt
===================================================================
--- tags/JBoss_Seam_2_1_1_GA/changelog.txt 2008-12-15 15:46:20 UTC (rev 9781)
+++ tags/JBoss_Seam_2_1_1_GA/changelog.txt 2008-12-15 15:48:55 UTC (rev 9782)
@@ -11,6 +11,7 @@
* [JBSEAM-3819] - grammar in http://docs.jboss.com/seam/latest/reference/en-US/html/tutorial.html
* [JBSEAM-3830] - e:cell doesn't support null values
* [JBSEAM-3834] - ClassCastException in Cell Column With Empty Date
+ * [JBSEAM-3843] - Seamspace example - pages.xml uses logLevel attribute
Release Notes - Seam - Version 2.1.1.CR2
16 years
- 1
- 0