[seam-commits] Seam SVN: r9757 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Thu Dec 11 17:36:46 EST 2008
Author: nico.ben
Date: 2008-12-11 17:36:45 -0500 (Thu, 11 Dec 2008)
New Revision: 9757
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Feedback.po
trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po
trunk/doc/Seam_Reference_Guide/it-IT/Itext.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -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:22+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-07 22:50+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,115 +17,90 @@
#: Annotations.xml:5
#, no-c-format
msgid "Seam annotations"
-msgstr ""
+msgstr "Annotazioni di Seam"
#. Tag: para
#: Annotations.xml:7
#, no-c-format
-msgid ""
-"When you write a Seam application, you'll use a lot of annotations. Seam "
-"lets you use annotations to achieve a declarative style of programming. Most "
-"of the annotations you'll use are defined by the EJB 3.0 specification. The "
-"annotations for data validation are defined by the Hibernate Validator "
-"package. Finally, Seam defines its own set of annotations, which we'll "
-"describe in this chapter."
+msgid "When you write a Seam application, you'll use a lot of annotations. Seam lets you use annotations to achieve a declarative style of programming. Most of the annotations you'll use are defined by the EJB 3.0 specification. The annotations for data validation are defined by the Hibernate Validator package. Finally, Seam defines its own set of annotations, which we'll describe in this chapter."
msgstr ""
#. Tag: para
#: Annotations.xml:16
#, no-c-format
-msgid ""
-"All of these annotations are defined in the package <literal>org.jboss.seam."
-"annotations</literal>."
+msgid "All of these annotations are defined in the package <literal>org.jboss.seam.annotations</literal>."
msgstr ""
#. Tag: title
#: Annotations.xml:22
#, no-c-format
msgid "Annotations for component definition"
-msgstr ""
+msgstr "Annotazioni per la definizione di un componente"
#. Tag: para
#: Annotations.xml:23
#, no-c-format
-msgid ""
-"The first group of annotations lets you define a Seam component. These "
-"annotations appear on the component class."
+msgid "The first group of annotations lets you define a Seam component. These annotations appear on the component class."
msgstr ""
#. Tag: literal
#: Annotations.xml:31
#, no-c-format
msgid "@Name"
-msgstr ""
+msgstr "@Name"
#. Tag: programlisting
#: Annotations.xml:34
#, no-c-format
msgid "<![CDATA[@Name(\"componentName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Name(\"componentName\")]]>"
#. Tag: para
#: Annotations.xml:35
#, no-c-format
-msgid ""
-"Defines the Seam component name for a class. This annotation is required for "
-"all Seam components."
+msgid "Defines the Seam component name for a class. This annotation is required for all Seam components."
msgstr ""
#. Tag: literal
#: Annotations.xml:43
#, no-c-format
msgid "@Scope"
-msgstr ""
+msgstr "@Scope"
#. Tag: programlisting
#: Annotations.xml:46
#, no-c-format
msgid "<![CDATA[@Scope(ScopeType.CONVERSATION)]]>"
-msgstr ""
+msgstr "<![CDATA[@Scope(ScopeType.CONVERSATION)]]>"
#. Tag: para
#: Annotations.xml:47
#, no-c-format
-msgid ""
-"Defines the default context of the component. The possible values are "
-"defined by the <literal>ScopeType</literal> enumeration: <literal>EVENT, "
-"PAGE, CONVERSATION, SESSION, BUSINESS_PROCESS, APPLICATION, STATELESS</"
-"literal>."
+msgid "Defines the default context of the component. The possible values are defined by the <literal>ScopeType</literal> enumeration: <literal>EVENT, PAGE, CONVERSATION, SESSION, BUSINESS_PROCESS, APPLICATION, STATELESS</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:52
#, no-c-format
-msgid ""
-"When no scope is explicitly specified, the default depends upon the "
-"component type. For stateless session beans, the default is "
-"<literal>STATELESS</literal>. For entity beans and stateful session beans, "
-"the default is <literal>CONVERSATION</literal>. For JavaBeans, the default "
-"is <literal>EVENT</literal>."
+msgid "When no scope is explicitly specified, the default depends upon the component type. For stateless session beans, the default is <literal>STATELESS</literal>. For entity beans and stateful session beans, the default is <literal>CONVERSATION</literal>. For JavaBeans, the default is <literal>EVENT</literal>."
msgstr ""
#. Tag: literal
#: Annotations.xml:64
#, no-c-format
msgid "@Role"
-msgstr ""
+msgstr "@Role"
#. Tag: programlisting
#: Annotations.xml:67
#, no-c-format
msgid "<![CDATA[@Role(name=\"roleName\", scope=ScopeType.SESSION)]]>"
-msgstr ""
+msgstr "<![CDATA[@Role(name=\"roleName\", scope=ScopeType.SESSION)]]>"
#. Tag: para
#: Annotations.xml:68
#, no-c-format
-msgid ""
-"Allows a Seam component to be bound to multiple contexts variables. The "
-"<literal>@Name</literal>/<literal>@Scope</literal> annotations define a "
-"\"default role\". Each <literal>@Role</literal> annotation defines an "
-"additional role."
+msgid "Allows a Seam component to be bound to multiple contexts variables. The <literal>@Name</literal>/<literal>@Scope</literal> annotations define a \"default role\". Each <literal>@Role</literal> annotation defines an additional role."
msgstr ""
#. Tag: para
@@ -137,17 +112,14 @@
#. Tag: para
#: Annotations.xml:82
#, no-c-format
-msgid ""
-"<literal>scope</literal> — the context variable scope. When no scope "
-"is explicitly specified, the default depends upon the component type, as "
-"above."
+msgid "<literal>scope</literal> — the context variable scope. When no scope is explicitly specified, the default depends upon the component type, as above."
msgstr ""
#. Tag: literal
#: Annotations.xml:93
#, no-c-format
msgid "@Roles"
-msgstr ""
+msgstr "@Roles"
#. Tag: programlisting
#: Annotations.xml:96
@@ -158,327 +130,279 @@
" @Role(name=\"currentUser\", scope=ScopeType.SESSION)\n"
" })]]>"
msgstr ""
+"<![CDATA[@Roles({\n"
+" @Role(name=\"user\", scope=ScopeType.CONVERSATION),\n"
+" @Role(name=\"currentUser\", scope=ScopeType.SESSION)\n"
+" })]]>"
#. Tag: para
#: Annotations.xml:97
#, no-c-format
msgid "Allows specification of multiple additional roles."
-msgstr ""
+msgstr "Consente la specificazione di ruoli multipli addizionali."
#. Tag: literal
#: Annotations.xml:104
#, no-c-format
msgid "@BypassInterceptors"
-msgstr ""
+msgstr "@BypassInterceptors"
#. Tag: programlisting
#: Annotations.xml:107
#, no-c-format
msgid "<![CDATA[@BypassInterceptors]]>"
-msgstr ""
+msgstr "<![CDATA[@BypassInterceptors]]>"
#. Tag: para
#: Annotations.xml:108
#, no-c-format
-msgid ""
-"Disables Seam all interceptors on a particular component or method of a "
-"component."
-msgstr ""
+msgid "Disables Seam all interceptors on a particular component or method of a component."
+msgstr "Disabilita tutti gli interceptor di Seam per un particolare componente o metodo di un componente."
#. Tag: literal
#: Annotations.xml:116
#, no-c-format
msgid "@JndiName"
-msgstr ""
+msgstr "@JndiName"
#. Tag: programlisting
#: Annotations.xml:119
#, no-c-format
msgid "<![CDATA[@JndiName(\"my/jndi/name\")]]>"
-msgstr ""
+msgstr "<![CDATA[@JndiName(\"my/jndi/name\")]]>"
#. Tag: para
#: Annotations.xml:120
#, no-c-format
-msgid ""
-"Specifies the JNDI name that Seam will use to look up the EJB component. If "
-"no JNDI name is explicitly specified, Seam will use the JNDI pattern "
-"specified by <literal>org.jboss.seam.core.init.jndiPattern</literal>."
+msgid "Specifies the JNDI name that Seam will use to look up the EJB component. If no JNDI name is explicitly specified, Seam will use the JNDI pattern specified by <literal>org.jboss.seam.core.init.jndiPattern</literal>."
msgstr ""
#. Tag: literal
#: Annotations.xml:130
#, no-c-format
msgid "@Conversational"
-msgstr ""
+msgstr "@Conversational"
#. Tag: programlisting
#: Annotations.xml:133
#, no-c-format
msgid "<![CDATA[@Conversational]]>"
-msgstr ""
+msgstr "<![CDATA[@Conversational]]>"
#. Tag: para
#: Annotations.xml:134
#, no-c-format
-msgid ""
-"Specifies that a conversation scope component is conversational, meaning "
-"that no method of the component may be called unless a long-running "
-"conversation is active."
+msgid "Specifies that a conversation scope component is conversational, meaning that no method of the component may be called unless a long-running conversation is active."
msgstr ""
#. Tag: literal
#: Annotations.xml:143
#, no-c-format
msgid "@PerNestedConversation"
-msgstr ""
+msgstr "@PerNestedConversation"
#. Tag: programlisting
#: Annotations.xml:146
#, no-c-format
msgid "<![CDATA[@PerNestedConversation]]>"
-msgstr ""
+msgstr "<![CDATA[@PerNestedConversation]]>"
#. Tag: para
#: Annotations.xml:147
#, no-c-format
-msgid ""
-"Limits the scope of a CONVERSATION-scoped component to just the parent "
-"conversation in which it was instantiated. The component instance will not "
-"be visible to nested child conversations, which will get their own instance."
+msgid "Limits the scope of a CONVERSATION-scoped component to just the parent conversation in which it was instantiated. The component instance will not be visible to nested child conversations, which will get their own instance."
msgstr ""
#. Tag: para
#: Annotations.xml:153
#, no-c-format
-msgid ""
-"Warning: this is ill-defined, since it implies that a component will be "
-"visible for some part of a request cycle, and invisible after that. It is "
-"not recommended that applications use this feature!"
+msgid "Warning: this is ill-defined, since it implies that a component will be visible for some part of a request cycle, and invisible after that. It is not recommended that applications use this feature!"
msgstr ""
#. Tag: literal
#: Annotations.xml:163
#, no-c-format
msgid "@Startup"
-msgstr ""
+msgstr "@Startup"
#. Tag: programlisting
#: Annotations.xml:166
#, no-c-format
-msgid ""
-"<![CDATA[@Scope(APPLICATION) @Startup(depends=\"org.jboss.seam.bpm.jbpm\")]]>"
-msgstr ""
+msgid "<![CDATA[@Scope(APPLICATION) @Startup(depends=\"org.jboss.seam.bpm.jbpm\")]]>"
+msgstr "<![CDATA[@Scope(APPLICATION) @Startup(depends=\"org.jboss.seam.bpm.jbpm\")]]>"
#. Tag: para
#: Annotations.xml:167
#, no-c-format
-msgid ""
-"Specifies that an application scope component is started immediately at "
-"initialization time. This is mainly used for certain built-in components "
-"that bootstrap critical infrastructure such as JNDI, datasources, etc."
+msgid "Specifies that an application scope component is started immediately at initialization time. This is mainly used for certain built-in components that bootstrap critical infrastructure such as JNDI, datasources, etc."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:173
#, no-c-format
msgid "<![CDATA[@Scope(SESSION) @Startup]]>"
-msgstr ""
+msgstr "<![CDATA[@Scope(SESSION) @Startup]]>"
#. Tag: para
#: Annotations.xml:174
#, no-c-format
-msgid ""
-"Specifies that a session scope component is started immediately at session "
-"creation time."
+msgid "Specifies that a session scope component is started immediately at session creation time."
msgstr ""
#. Tag: para
#: Annotations.xml:180
#, no-c-format
-msgid ""
-"<literal>depends</literal> — specifies that the named components must "
-"be started first, if they are installed."
+msgid "<literal>depends</literal> — specifies that the named components must be started first, if they are installed."
msgstr ""
#. Tag: literal
#: Annotations.xml:191
#, no-c-format
msgid "@Install"
-msgstr ""
+msgstr "@Install"
#. Tag: programlisting
#: Annotations.xml:194
#, no-c-format
msgid "<![CDATA[@Install(false)]]>"
-msgstr ""
+msgstr "<![CDATA[@Install(false)]]>"
#. Tag: para
#: Annotations.xml:195
#, no-c-format
-msgid ""
-"Specifies whether or not a component should be installed by default. The "
-"lack of an <literal>@Install</literal> annotation indicates a component "
-"should be installed."
+msgid "Specifies whether or not a component should be installed by default. The lack of an <literal>@Install</literal> annotation indicates a component should be installed."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:200
#, no-c-format
msgid "<![CDATA[@Install(dependencies=\"org.jboss.seam.bpm.jbpm\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Install(dependencies=\"org.jboss.seam.bpm.jbpm\")]]>"
#. Tag: para
#: Annotations.xml:201
#, no-c-format
-msgid ""
-"Specifies that a component should only be stalled if the components listed "
-"as dependencies are also installed."
+msgid "Specifies that a component should only be stalled if the components listed as dependencies are also installed."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:205
#, no-c-format
msgid "<![CDATA[@Install(genericDependencies=ManagedQueueSender.class)]]>"
-msgstr ""
+msgstr "<![CDATA[@Install(genericDependencies=ManagedQueueSender.class)]]>"
#. Tag: para
#: Annotations.xml:206
#, no-c-format
-msgid ""
-"Specifies that a component should only be installed if a component that is "
-"implemented by a certain class is installed. This is useful when the "
-"dependency doesn't have a single well-known name."
+msgid "Specifies that a component should only be installed if a component that is implemented by a certain class is installed. This is useful when the dependency doesn't have a single well-known name."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:212
#, no-c-format
msgid "<![CDATA[@Install(classDependencies=\"org.hibernate.Session\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Install(classDependencies=\"org.hibernate.Session\")]]>"
#. Tag: para
#: Annotations.xml:213
#, no-c-format
-msgid ""
-"Specifies that a component should only be installed if the named class is in "
-"the classpath."
+msgid "Specifies that a component should only be installed if the named class is in the classpath."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:217
#, no-c-format
msgid "<![CDATA[@Install(precedence=BUILT_IN)]]>"
-msgstr ""
+msgstr "<![CDATA[@Install(precedence=BUILT_IN)]]>"
#. Tag: para
#: Annotations.xml:218
#, no-c-format
-msgid ""
-"Specifies the precedence of the component. If multiple components with the "
-"same name exist, the one with the higher precedence will be installed. The "
-"defined precendence values are (in ascending order):"
+msgid "Specifies the precedence of the component. If multiple components with the same name exist, the one with the higher precedence will be installed. The defined precendence values are (in ascending order):"
msgstr ""
#. Tag: para
#: Annotations.xml:227
#, no-c-format
-msgid ""
-"<literal>BUILT_IN</literal> — Precedence of all built-in Seam "
-"components"
+msgid "<literal>BUILT_IN</literal> — Precedence of all built-in Seam components"
msgstr ""
#. Tag: para
#: Annotations.xml:233
#, no-c-format
-msgid ""
-"<literal>FRAMEWORK</literal> — Precedence to use for components of "
-"frameworks which extend Seam"
+msgid "<literal>FRAMEWORK</literal> — Precedence to use for components of frameworks which extend Seam"
msgstr ""
#. Tag: para
#: Annotations.xml:239
#, no-c-format
-msgid ""
-"<literal>APPLICATION</literal> — Predence of application components "
-"(the default precedence)"
+msgid "<literal>APPLICATION</literal> — Predence of application components (the default precedence)"
msgstr ""
#. Tag: para
#: Annotations.xml:245
#, no-c-format
-msgid ""
-"<literal>DEPLOYMENT</literal> — Precedence to use for components which "
-"override application components in a particular deployment"
+msgid "<literal>DEPLOYMENT</literal> — Precedence to use for components which override application components in a particular deployment"
msgstr ""
#. Tag: para
#: Annotations.xml:252
#, no-c-format
-msgid ""
-"<literal>MOCK</literal> — Precedence for mock objects used in testing"
+msgid "<literal>MOCK</literal> — Precedence for mock objects used in testing"
msgstr ""
#. Tag: literal
#: Annotations.xml:263
#, no-c-format
msgid "@Synchronized"
-msgstr ""
+msgstr "@Synchronized"
#. Tag: programlisting
#: Annotations.xml:266
#, no-c-format
msgid "<![CDATA[@Synchronized(timeout=1000)]]>"
-msgstr ""
+msgstr "<![CDATA[@Synchronized(timeout=1000)]]>"
#. Tag: para
#: Annotations.xml:267
#, no-c-format
-msgid ""
-"Specifies that a component is accessed concurrently by multiple clients, and "
-"that Seam should serialize requests. If a request is not able to obtain its "
-"lock on the component in the given timeout period, an exception will be "
-"raised."
+msgid "Specifies that a component is accessed concurrently by multiple clients, and that Seam should serialize requests. If a request is not able to obtain its lock on the component in the given timeout period, an exception will be raised."
msgstr ""
#. Tag: literal
#: Annotations.xml:277
#, no-c-format
msgid "@ReadOnly"
-msgstr ""
+msgstr "@ReadOnly"
#. Tag: programlisting
#: Annotations.xml:280
#, no-c-format
msgid "<![CDATA[@ReadOnly]]>"
-msgstr ""
+msgstr "<![CDATA[@ReadOnly]]>"
#. Tag: para
#: Annotations.xml:281
#, no-c-format
-msgid ""
-"Specifies that a JavaBean component or component method does not require "
-"state replication at the end of the invocation."
+msgid "Specifies that a JavaBean component or component method does not require state replication at the end of the invocation."
msgstr ""
#. Tag: literal
#: Annotations.xml:289
#, no-c-format
msgid "@AutoCreate"
-msgstr ""
+msgstr "@AutoCreate"
#. Tag: programlisting
#: Annotations.xml:292
#, no-c-format
msgid "<![CDATA[@AutoCreate]]>"
-msgstr ""
+msgstr "<![CDATA[@AutoCreate]]>"
#. Tag: para
#: Annotations.xml:293
#, no-c-format
-msgid ""
-"Specifies that a component will be automatically created, even if the client "
-"does not specify <literal>create=true</literal>."
+msgid "Specifies that a component will be automatically created, even if the client does not specify <literal>create=true</literal>."
msgstr ""
#. Tag: title
@@ -490,320 +414,248 @@
#. Tag: para
#: Annotations.xml:304
#, no-c-format
-msgid ""
-"The next two annotations control bijection. These attributes occur on "
-"component instance variables or property accessor methods."
+msgid "The next two annotations control bijection. These attributes occur on component instance variables or property accessor methods."
msgstr ""
#. Tag: literal
#: Annotations.xml:312
#, no-c-format
msgid "<literal>@In</literal>"
-msgstr ""
+msgstr "<literal>@In</literal>"
#. Tag: programlisting
#: Annotations.xml:315
#, no-c-format
msgid "<![CDATA[@In]]>"
-msgstr ""
+msgstr "<![CDATA[@In]]>"
#. Tag: para
#: Annotations.xml:316
#, no-c-format
-msgid ""
-"Specifies that a component attribute is to be injected from a context "
-"variable at the beginning of each component invocation. If the context "
-"variable is null, an exception will be thrown."
+msgid "Specifies that a component attribute is to be injected from a context variable at the beginning of each component invocation. If the context variable is null, an exception will be thrown."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:322
#, no-c-format
msgid "<![CDATA[@In(required=false)]]>"
-msgstr ""
+msgstr "<![CDATA[@In(required=false)]]>"
#. Tag: para
#: Annotations.xml:323
#, no-c-format
-msgid ""
-"Specifies that a component attribute is to be injected from a context "
-"variable at the beginning of each component invocation. The context variable "
-"may be null."
+msgid "Specifies that a component attribute is to be injected from a context variable at the beginning of each component invocation. The context variable may be null."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:328
#, no-c-format
msgid "<![CDATA[@In(create=true)]]>"
-msgstr ""
+msgstr "<![CDATA[@In(create=true)]]>"
#. Tag: para
#: Annotations.xml:329
#, no-c-format
-msgid ""
-"Specifies that a component attribute is to be injected from a context "
-"variable at the beginning of each component invocation. If the context "
-"variable is null, an instance of the component is instantiated by Seam."
+msgid "Specifies that a component attribute is to be injected from a context variable at the beginning of each component invocation. If the context variable is null, an instance of the component is instantiated by Seam."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:335
#, no-c-format
msgid "<![CDATA[@In(value=\"contextVariableName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@In(value=\"contextVariableName\")]]>"
#. Tag: para
-#: Annotations.xml:336 Annotations.xml:403
+#: Annotations.xml:336
+#: Annotations.xml:403
#, no-c-format
-msgid ""
-"Specifies the name of the context variable explicitly, instead of using the "
-"annotated instance variable name."
+msgid "Specifies the name of the context variable explicitly, instead of using the annotated instance variable name."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:340
#, no-c-format
msgid "<![CDATA[@In(value=\"#{customer.addresses['shipping']}\")]]>"
-msgstr ""
+msgstr "<![CDATA[@In(value=\"#{customer.addresses['shipping']}\")]]>"
#. Tag: para
#: Annotations.xml:341
#, no-c-format
-msgid ""
-"Specifies that a component attribute is to be injected by evaluating a JSF "
-"EL expression at the beginning of each component invocation."
+msgid "Specifies that a component attribute is to be injected by evaluating a JSF EL expression at the beginning of each component invocation."
msgstr ""
#. Tag: para
#: Annotations.xml:348
#, no-c-format
-msgid ""
-"<literal>value</literal> — specifies the name of the context variable. "
-"Default to the name of the component attribute. Alternatively, specifies a "
-"JSF EL expression, surrounded by <literal>#{...}</literal>."
+msgid "<literal>value</literal> — specifies the name of the context variable. Default to the name of the component attribute. Alternatively, specifies a JSF EL expression, surrounded by <literal>#{...}</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:356
#, no-c-format
-msgid ""
-"<literal>create</literal> — specifies that Seam should instantiate the "
-"component with the same name as the context variable if the context variable "
-"is undefined (null) in all contexts. Default to false."
+msgid "<literal>create</literal> — specifies that Seam should instantiate the component with the same name as the context variable if the context variable is undefined (null) in all contexts. Default to false."
msgstr ""
#. Tag: para
#: Annotations.xml:364
#, no-c-format
-msgid ""
-"<literal>required</literal> — specifies Seam should throw an exception "
-"if the context variable is undefined in all contexts."
+msgid "<literal>required</literal> — specifies Seam should throw an exception if the context variable is undefined in all contexts."
msgstr ""
#. Tag: literal
#: Annotations.xml:375
#, no-c-format
msgid "@Out"
-msgstr ""
+msgstr "@Out"
#. Tag: programlisting
#: Annotations.xml:378
#, no-c-format
msgid "<![CDATA[@Out]]>"
-msgstr ""
+msgstr "<![CDATA[@Out]]>"
#. Tag: para
#: Annotations.xml:379
#, no-c-format
-msgid ""
-"Specifies that a component attribute that is a Seam component is to be "
-"outjected to its context variable at the end of the invocation. If the "
-"attribute is null, an exception is thrown."
+msgid "Specifies that a component attribute that is a Seam component is to be outjected to its context variable at the end of the invocation. If the attribute is null, an exception is thrown."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:384
#, no-c-format
msgid "<![CDATA[@Out(required=false)]]>"
-msgstr ""
+msgstr "<![CDATA[@Out(required=false)]]>"
#. Tag: para
#: Annotations.xml:385
#, no-c-format
-msgid ""
-"Specifies that a component attribute that is a Seam component is to be "
-"outjected to its context variable at the end of the invocation. The "
-"attribute may be null."
+msgid "Specifies that a component attribute that is a Seam component is to be outjected to its context variable at the end of the invocation. The attribute may be null."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:390
#, no-c-format
msgid "<![CDATA[@Out(scope=ScopeType.SESSION)]]>"
-msgstr ""
+msgstr "<![CDATA[@Out(scope=ScopeType.SESSION)]]>"
#. Tag: para
#: Annotations.xml:391
#, no-c-format
-msgid ""
-"Specifies that a component attribute that is <emphasis>not</emphasis> a Seam "
-"component type is to be outjected to a specific scope at the end of the "
-"invocation."
+msgid "Specifies that a component attribute that is <emphasis>not</emphasis> a Seam component type is to be outjected to a specific scope at the end of the invocation."
msgstr ""
#. Tag: para
#: Annotations.xml:396
#, no-c-format
-msgid ""
-"Alternatively, if no scope is explicitly specified, the scope of the "
-"component with the <literal>@Out</literal> attribute is used (or the "
-"<literal>EVENT</literal> scope if the component is stateless)."
+msgid "Alternatively, if no scope is explicitly specified, the scope of the component with the <literal>@Out</literal> attribute is used (or the <literal>EVENT</literal> scope if the component is stateless)."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:402
#, no-c-format
msgid "<![CDATA[@Out(value=\"contextVariableName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Out(value=\"contextVariableName\")]]>"
#. Tag: para
#: Annotations.xml:409
#, no-c-format
-msgid ""
-"<literal>value</literal> — specifies the name of the context variable. "
-"Default to the name of the component attribute."
+msgid "<literal>value</literal> — specifies the name of the context variable. Default to the name of the component attribute."
msgstr ""
#. Tag: para
#: Annotations.xml:416
#, no-c-format
-msgid ""
-"<literal>required</literal> — specifies Seam should throw an exception "
-"if the component attribute is null during outjection."
+msgid "<literal>required</literal> — specifies Seam should throw an exception if the component attribute is null during outjection."
msgstr ""
#. Tag: para
#: Annotations.xml:427
#, no-c-format
-msgid ""
-"Note that it is quite common for these annotations to occur together, for "
-"example:"
+msgid "Note that it is quite common for these annotations to occur together, for example:"
msgstr ""
#. Tag: programlisting
#: Annotations.xml:432
#, no-c-format
msgid "<![CDATA[@In(create=true) @Out private User currentUser;]]>"
-msgstr ""
+msgstr "<![CDATA[@In(create=true) @Out private User currentUser;]]>"
#. Tag: para
#: Annotations.xml:434
#, no-c-format
-msgid ""
-"The next annotation supports the <emphasis>manager component</emphasis> "
-"pattern, where a Seam component that manages the lifecycle of an instance of "
-"some other class that is to be injected. It appears on a component getter "
-"method."
+msgid "The next annotation supports the <emphasis>manager component</emphasis> pattern, where a Seam component that manages the lifecycle of an instance of some other class that is to be injected. It appears on a component getter method."
msgstr ""
#. Tag: literal
#: Annotations.xml:444
#, no-c-format
msgid "@Unwrap"
-msgstr ""
+msgstr "@Unwrap"
#. Tag: programlisting
#: Annotations.xml:447
#, no-c-format
msgid "<![CDATA[@Unwrap]]>"
-msgstr ""
+msgstr "<![CDATA[@Unwrap]]>"
#. Tag: para
#: Annotations.xml:448
#, no-c-format
-msgid ""
-"Specifies that the object returned by the annotated getter method is the "
-"thing that is injected instead of the component instance itself."
+msgid "Specifies that the object returned by the annotated getter method is the thing that is injected instead of the component instance itself."
msgstr ""
#. Tag: para
#: Annotations.xml:457
#, no-c-format
-msgid ""
-"The next annotation supports the <emphasis>factory component</emphasis> "
-"pattern, where a Seam component is responsible for initializing the value of "
-"a context variable. This is especially useful for initializing any state "
-"needed for rendering the response to a non-faces request. It appears on a "
-"component method."
+msgid "The next annotation supports the <emphasis>factory component</emphasis> pattern, where a Seam component is responsible for initializing the value of a context variable. This is especially useful for initializing any state needed for rendering the response to a non-faces request. It appears on a component method."
msgstr ""
#. Tag: literal
#: Annotations.xml:468
#, no-c-format
msgid "@Factory"
-msgstr ""
+msgstr "@Factory"
#. Tag: programlisting
#: Annotations.xml:471
#, no-c-format
-msgid ""
-"<![CDATA[@Factory(\"processInstance\") public void createProcessInstance() "
-"{ ... }]]>"
-msgstr ""
+msgid "<![CDATA[@Factory(\"processInstance\") public void createProcessInstance() { ... }]]>"
+msgstr "<![CDATA[@Factory(\"processInstance\") public void createProcessInstance() { ... }]]>"
#. Tag: para
#: Annotations.xml:472
#, no-c-format
-msgid ""
-"Specifies that the method of the component is used to initialize the value "
-"of the named context variable, when the context variable has no value. This "
-"style is used with methods that return <literal>void</literal>."
+msgid "Specifies that the method of the component is used to initialize the value of the named context variable, when the context variable has no value. This style is used with methods that return <literal>void</literal>."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:478
#, no-c-format
-msgid ""
-"<![CDATA[@Factory(\"processInstance\", scope=CONVERSATION) public "
-"ProcessInstance createProcessInstance() { ... }]]>"
+msgid "<![CDATA[@Factory(\"processInstance\", scope=CONVERSATION) public ProcessInstance createProcessInstance() { ... }]]>"
msgstr ""
#. Tag: para
#: Annotations.xml:479
#, no-c-format
-msgid ""
-"Specifies that the method returns a value that Seam should use to initialize "
-"the value of the named context variable, when the context variable has no "
-"value. This style is used with methods that return a value. If no scope is "
-"explicitly specified, the scope of the component with the <literal>@Factory</"
-"literal> method is used (unless the component is stateless, in which case "
-"the <literal>EVENT</literal> context is used)."
+msgid "Specifies that the method returns a value that Seam should use to initialize the value of the named context variable, when the context variable has no value. This style is used with methods that return a value. If no scope is explicitly specified, the scope of the component with the <literal>@Factory</literal> method is used (unless the component is stateless, in which case the <literal>EVENT</literal> context is used)."
msgstr ""
#. Tag: para
#: Annotations.xml:491
#, no-c-format
-msgid ""
-"<literal>value</literal> — specifies the name of the context variable. "
-"If the method is a getter method, default to the JavaBeans property name."
+msgid "<literal>value</literal> — specifies the name of the context variable. If the method is a getter method, default to the JavaBeans property name."
msgstr ""
#. Tag: para
#: Annotations.xml:498
#, no-c-format
-msgid ""
-"<literal>scope</literal> — specifies the scope that Seam should bind "
-"the returned value to. Only meaningful for factory methods which return a "
-"value."
+msgid "<literal>scope</literal> — specifies the scope that Seam should bind the returned value to. Only meaningful for factory methods which return a value."
msgstr ""
#. Tag: para
#: Annotations.xml:505
#, no-c-format
-msgid ""
-"<literal>autoCreate</literal> — specifies that this factory method "
-"should be automatically called whenever the variable is asked for, even if "
-"<literal>@In</literal> does not specify <literal>create=true</literal>."
+msgid "<literal>autoCreate</literal> — specifies that this factory method should be automatically called whenever the variable is asked for, even if <literal>@In</literal> does not specify <literal>create=true</literal>."
msgstr ""
#. Tag: para
@@ -816,29 +668,24 @@
#: Annotations.xml:525
#, no-c-format
msgid "@Logger"
-msgstr ""
+msgstr "@Logger"
#. Tag: programlisting
#: Annotations.xml:528
#, no-c-format
msgid "<![CDATA[@Logger(\"categoryName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Logger(\"categoryName\")]]>"
#. Tag: para
#: Annotations.xml:529
#, no-c-format
-msgid ""
-"Specifies that a component field is to be injected with an instance of "
-"<literal>org.jboss.seam.log.Log</literal>. For entity beans, the field must "
-"be declared as static."
+msgid "Specifies that a component field is to be injected with an instance of <literal>org.jboss.seam.log.Log</literal>. For entity beans, the field must be declared as static."
msgstr ""
#. Tag: para
#: Annotations.xml:536
#, no-c-format
-msgid ""
-"<literal>value</literal> — specifies the name of the log category. "
-"Default to the name of the component class."
+msgid "<literal>value</literal> — specifies the name of the log category. Default to the name of the component class."
msgstr ""
#. Tag: para
@@ -851,28 +698,24 @@
#: Annotations.xml:554
#, no-c-format
msgid "@RequestParameter"
-msgstr ""
+msgstr "@RequestParameter"
#. Tag: programlisting
#: Annotations.xml:557
#, no-c-format
msgid "<![CDATA[@RequestParameter(\"parameterName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@RequestParameter(\"parameterName\")]]>"
#. Tag: para
#: Annotations.xml:558
#, no-c-format
-msgid ""
-"Specifies that a component attribute is to be injected with the value of a "
-"request parameter. Basic type conversions are performed automatically."
+msgid "Specifies that a component attribute is to be injected with the value of a request parameter. Basic type conversions are performed automatically."
msgstr ""
#. Tag: para
#: Annotations.xml:565
#, no-c-format
-msgid ""
-"<literal>value</literal> — specifies the name of the request "
-"parameter. Default to the name of the component attribute."
+msgid "<literal>value</literal> — specifies the name of the request parameter. Default to the name of the component attribute."
msgstr ""
#. Tag: title
@@ -884,97 +727,79 @@
#. Tag: para
#: Annotations.xml:580
#, no-c-format
-msgid ""
-"These annotations allow a component to react to its own lifecycle events. "
-"They occur on methods of the component. There may be only one of each per "
-"component class."
+msgid "These annotations allow a component to react to its own lifecycle events. They occur on methods of the component. There may be only one of each per component class."
msgstr ""
#. Tag: literal
#: Annotations.xml:589
#, no-c-format
msgid "@Create"
-msgstr ""
+msgstr "@Create"
#. Tag: programlisting
#: Annotations.xml:592
#, no-c-format
msgid "<![CDATA[@Create]]>"
-msgstr ""
+msgstr "<![CDATA[@Create]]>"
#. Tag: para
#: Annotations.xml:593
#, no-c-format
-msgid ""
-"Specifies that the method should be called when an instance of the component "
-"is instantiated by Seam. Note that create methods are only supported for "
-"JavaBeans and stateful session beans."
+msgid "Specifies that the method should be called when an instance of the component is instantiated by Seam. Note that create methods are only supported for JavaBeans and stateful session beans."
msgstr ""
#. Tag: literal
#: Annotations.xml:603
#, no-c-format
msgid "@Destroy"
-msgstr ""
+msgstr "@Destroy"
#. Tag: programlisting
#: Annotations.xml:606
#, no-c-format
msgid "<![CDATA[@Destroy]]>"
-msgstr ""
+msgstr "<![CDATA[@Destroy]]>"
#. Tag: para
#: Annotations.xml:607
#, no-c-format
-msgid ""
-"Specifies that the method should be called when the context ends and its "
-"context variables are destroyed. Note that destroy methods are only "
-"supported for JavaBeans and stateful session beans."
+msgid "Specifies that the method should be called when the context ends and its context variables are destroyed. Note that destroy methods are only supported for JavaBeans and stateful session beans."
msgstr ""
#. Tag: para
#: Annotations.xml:613
#, no-c-format
-msgid ""
-"Destroy methods should be used only for cleanup. <emphasis>Seam catches, "
-"logs and swallows any exception that propagates out of a destroy method.</"
-"emphasis>"
+msgid "Destroy methods should be used only for cleanup. <emphasis>Seam catches, logs and swallows any exception that propagates out of a destroy method.</emphasis>"
msgstr ""
#. Tag: literal
#: Annotations.xml:622
#, no-c-format
msgid "@Observer"
-msgstr ""
+msgstr "@Observer"
#. Tag: programlisting
#: Annotations.xml:625
#, no-c-format
msgid "<![CDATA[@Observer(\"somethingChanged\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Observer(\"somethingChanged\")]]>"
#. Tag: para
#: Annotations.xml:626
#, no-c-format
-msgid ""
-"Specifies that the method should be called when a component-driven event of "
-"the specified type occurs."
+msgid "Specifies that the method should be called when a component-driven event of the specified type occurs."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:630
#, no-c-format
msgid "<![CDATA[@Observer(value=\"somethingChanged\",create=false)]]>"
-msgstr ""
+msgstr "<![CDATA[@Observer(value=\"somethingChanged\",create=false)]]>"
#. Tag: para
#: Annotations.xml:631
#, no-c-format
-msgid ""
-"Specifies that the method should be called when an event of the specified "
-"type occurs but that an instance should not be created if one doesn't exist. "
-"If an instance does not exist and create is false, the event will not be "
-"observed. The default value for create is true."
+msgid "Specifies that the method should be called when an event of the specified type occurs but that an instance should not be created if one doesn't exist. If an instance does not exist and create is false, the event will not be observed. The default value for create is true."
msgstr ""
#. Tag: title
@@ -986,139 +811,105 @@
#. Tag: para
#: Annotations.xml:646
#, no-c-format
-msgid ""
-"These annotations provide declarative conversation demarcation. They appear "
-"on methods of Seam components, usually action listener methods."
+msgid "These annotations provide declarative conversation demarcation. They appear on methods of Seam components, usually action listener methods."
msgstr ""
#. Tag: para
#: Annotations.xml:651
#, no-c-format
-msgid ""
-"Every web request has a conversation context associated with it. Most of "
-"these conversations end at the end of the request. If you want a "
-"conversation that span multiple requests, you must \"promote\" the current "
-"conversation to a <emphasis>long-running conversation</emphasis> by calling "
-"a method marked with <literal>@Begin</literal>."
+msgid "Every web request has a conversation context associated with it. Most of these conversations end at the end of the request. If you want a conversation that span multiple requests, you must \"promote\" the current conversation to a <emphasis>long-running conversation</emphasis> by calling a method marked with <literal>@Begin</literal>."
msgstr ""
#. Tag: literal
#: Annotations.xml:662
#, no-c-format
msgid "@Begin"
-msgstr ""
+msgstr "@Begin"
#. Tag: programlisting
#: Annotations.xml:665
#, no-c-format
msgid "<![CDATA[@Begin]]>"
-msgstr ""
+msgstr "<![CDATA[@Begin]]>"
#. Tag: para
#: Annotations.xml:666
#, no-c-format
-msgid ""
-"Specifies that a long-running conversation begins when this method returns a "
-"non-null outcome without exception."
+msgid "Specifies that a long-running conversation begins when this method returns a non-null outcome without exception."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:670
#, no-c-format
msgid "<![CDATA[@Begin(join=true)]]>"
-msgstr ""
+msgstr "<![CDATA[@Begin(join=true)]]>"
#. Tag: para
#: Annotations.xml:671
#, no-c-format
-msgid ""
-"Specifies that if a long-running conversation is already in progress, the "
-"conversation context is simply propagated."
+msgid "Specifies that if a long-running conversation is already in progress, the conversation context is simply propagated."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:675
#, no-c-format
msgid "<![CDATA[@Begin(nested=true)]]>"
-msgstr ""
+msgstr "<![CDATA[@Begin(nested=true)]]>"
#. Tag: para
#: Annotations.xml:676
#, no-c-format
-msgid ""
-"Specifies that if a long-running conversation is already in progress, a new "
-"<emphasis>nested</emphasis> conversation context begins. The nested "
-"conversation will end when the next <literal>@End</literal> is encountered, "
-"and the outer conversation will resume. It is perfectly legal for multiple "
-"nested conversations to exist concurrently in the same outer conversation."
+msgid "Specifies that if a long-running conversation is already in progress, a new <emphasis>nested</emphasis> conversation context begins. The nested conversation will end when the next <literal>@End</literal> is encountered, and the outer conversation will resume. It is perfectly legal for multiple nested conversations to exist concurrently in the same outer conversation."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:685
#, no-c-format
msgid "<![CDATA[@Begin(pageflow=\"process definition name\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Begin(pageflow=\"process definition name\")]]>"
#. Tag: para
#: Annotations.xml:686
#, no-c-format
-msgid ""
-"Specifies a jBPM process definition name that defines the pageflow for this "
-"conversation."
+msgid "Specifies a jBPM process definition name that defines the pageflow for this conversation."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:690
#, no-c-format
msgid "<![CDATA[@Begin(flushMode=FlushModeType.MANUAL)]]>"
-msgstr ""
+msgstr "<![CDATA[@Begin(flushMode=FlushModeType.MANUAL)]]>"
#. Tag: para
#: Annotations.xml:691
#, no-c-format
-msgid ""
-"Specify the flush mode of any Seam-managed persistence contexts. "
-"<literal>flushMode=FlushModeType.MANUAL</literal> supports the use of "
-"<emphasis>atomic conversations</emphasis> where all write operations are "
-"queued in the conversation context until an explicit call to <literal>flush()"
-"</literal> (which usually occurs at the end of the conversation)."
+msgid "Specify the flush mode of any Seam-managed persistence contexts. <literal>flushMode=FlushModeType.MANUAL</literal> supports the use of <emphasis>atomic conversations</emphasis> where all write operations are queued in the conversation context until an explicit call to <literal>flush()</literal> (which usually occurs at the end of the conversation)."
msgstr ""
#. Tag: para
#: Annotations.xml:702
#, no-c-format
-msgid ""
-"<literal>join</literal> — determines the behavior when a long-running "
-"conversation is already in progress. If <literal>true</literal>, the context "
-"is propagated. If <literal>false</literal>, an exception is thrown. Default "
-"to <literal>false</literal>. This setting is ignored when "
-"<literal>nested=true</literal> is specified."
+msgid "<literal>join</literal> — determines the behavior when a long-running conversation is already in progress. If <literal>true</literal>, the context is propagated. If <literal>false</literal>, an exception is thrown. Default to <literal>false</literal>. This setting is ignored when <literal>nested=true</literal> is specified."
msgstr ""
#. Tag: para
#: Annotations.xml:713
#, no-c-format
-msgid ""
-"<literal>nested</literal> — specifies that a nested conversation "
-"should be started if a long-running conversation is already in progress."
+msgid "<literal>nested</literal> — specifies that a nested conversation should be started if a long-running conversation is already in progress."
msgstr ""
#. Tag: para
-#: Annotations.xml:720 Annotations.xml:811 Annotations.xml:858
+#: Annotations.xml:720
+#: Annotations.xml:811
+#: Annotations.xml:858
#, no-c-format
-msgid ""
-"<literal>flushMode</literal> — set the flush mode of any Seam-managed "
-"Hibernate sessions or JPA persistence contexts that are created during this "
-"conversation."
+msgid "<literal>flushMode</literal> — set the flush mode of any Seam-managed Hibernate sessions or JPA persistence contexts that are created during this conversation."
msgstr ""
#. Tag: para
#: Annotations.xml:728
#, no-c-format
-msgid ""
-"<literal>pageflow</literal> — a process definition name of a jBPM "
-"process definition deployed via <literal>org.jboss.seam.bpm.jbpm."
-"pageflowDefinitions.</literal>"
+msgid "<literal>pageflow</literal> — a process definition name of a jBPM process definition deployed via <literal>org.jboss.seam.bpm.jbpm.pageflowDefinitions.</literal>"
msgstr ""
#. Tag: literal
@@ -1136,32 +927,20 @@
#. Tag: para
#: Annotations.xml:743
#, no-c-format
-msgid ""
-"Specifies that a long-running conversation ends when this method returns a "
-"non-null outcome without exception."
+msgid "Specifies that a long-running conversation ends when this method returns a non-null outcome without exception."
msgstr ""
#. Tag: para
-#: Annotations.xml:749 Annotations.xml:896
+#: Annotations.xml:749
+#: Annotations.xml:896
#, no-c-format
-msgid ""
-"<literal>beforeRedirect</literal> — by default, the conversation will "
-"not actually be destroyed until after any redirect has occurred. Setting "
-"<literal>beforeRedirect=true</literal> specifies that the conversation "
-"should be destroyed at the end of the current request, and that the redirect "
-"will be processed in a new temporary conversation context."
+msgid "<literal>beforeRedirect</literal> — by default, the conversation will not actually be destroyed until after any redirect has occurred. Setting <literal>beforeRedirect=true</literal> specifies that the conversation should be destroyed at the end of the current request, and that the redirect will be processed in a new temporary conversation context."
msgstr ""
#. Tag: para
#: Annotations.xml:760
#, no-c-format
-msgid ""
-"<literal>root</literal> — by default, ending a nested conversation "
-"simply pops the conversation stack and resumes the outer conversation. "
-"Setting <literal>root=true</literal> specifies that the root conversation "
-"should be destroyed which effectively destroys the entire conversation "
-"stack. If the conversation is not nested, the current conversation is simply "
-"ended."
+msgid "<literal>root</literal> — by default, ending a nested conversation simply pops the conversation stack and resumes the outer conversation. Setting <literal>root=true</literal> specifies that the root conversation should be destroyed which effectively destroys the entire conversation stack. If the conversation is not nested, the current conversation is simply ended."
msgstr ""
#. Tag: literal
@@ -1179,34 +958,20 @@
#. Tag: para
#: Annotations.xml:779
#, no-c-format
-msgid ""
-"\"Starts\" a jBPM task. Specifies that a long-running conversation begins "
-"when this method returns a non-null outcome without exception. This "
-"conversation is associated with the jBPM task specified in the named request "
-"parameter. Within the context of this conversation, a business process "
-"context is also defined, for the business process instance of the task "
-"instance."
+msgid "\"Starts\" a jBPM task. Specifies that a long-running conversation begins when this method returns a non-null outcome without exception. This conversation is associated with the jBPM task specified in the named request parameter. Within the context of this conversation, a business process context is also defined, for the business process instance of the task instance."
msgstr ""
#. Tag: para
#: Annotations.xml:790
#, no-c-format
-msgid ""
-"The jBPM <literal>TaskInstance</literal> will be available in a request "
-"context variable named <literal>taskInstance</literal>. The jPBM "
-"<literal>ProcessInstance</literal> will be available in a request context "
-"variable named <literal>processInstance</literal>. (Of course, these objects "
-"are available for injection via <literal>@In</literal>.)"
+msgid "The jBPM <literal>TaskInstance</literal> will be available in a request context variable named <literal>taskInstance</literal>. The jPBM <literal>ProcessInstance</literal> will be available in a request context variable named <literal>processInstance</literal>. (Of course, these objects are available for injection via <literal>@In</literal>.)"
msgstr ""
#. Tag: para
-#: Annotations.xml:802 Annotations.xml:849
+#: Annotations.xml:802
+#: Annotations.xml:849
#, no-c-format
-msgid ""
-"<literal>taskIdParameter</literal> — the name of a request parameter "
-"which holds the id of the task. Default to <literal>\"taskId\"</literal>, "
-"which is also the default used by the Seam <literal>taskList</literal> JSF "
-"component."
+msgid "<literal>taskIdParameter</literal> — the name of a request parameter which holds the id of the task. Default to <literal>\"taskId\"</literal>, which is also the default used by the Seam <literal>taskList</literal> JSF component."
msgstr ""
#. Tag: literal
@@ -1224,24 +989,13 @@
#. Tag: para
#: Annotations.xml:828
#, no-c-format
-msgid ""
-"Resumes work on an incomplete jBPM task. Specifies that a long-running "
-"conversation begins when this method returns a non-null outcome without "
-"exception. This conversation is associated with the jBPM task specified in "
-"the named request parameter. Within the context of this conversation, a "
-"business process context is also defined, for the business process instance "
-"of the task instance."
+msgid "Resumes work on an incomplete jBPM task. Specifies that a long-running conversation begins when this method returns a non-null outcome without exception. This conversation is associated with the jBPM task specified in the named request parameter. Within the context of this conversation, a business process context is also defined, for the business process instance of the task instance."
msgstr ""
#. Tag: para
#: Annotations.xml:839
#, no-c-format
-msgid ""
-"The jBPM <literal>org.jbpm.taskmgmt.exe.TaskInstance</literal> will be "
-"available in a request context variable named <literal>taskInstance</"
-"literal>. The jPBM <literal>org.jbpm.graph.exe.ProcessInstance</literal> "
-"will be available in a request context variable named "
-"<literal>processInstance</literal>."
+msgid "The jBPM <literal>org.jbpm.taskmgmt.exe.TaskInstance</literal> will be available in a request context variable named <literal>taskInstance</literal>. The jPBM <literal>org.jbpm.graph.exe.ProcessInstance</literal> will be available in a request context variable named <literal>processInstance</literal>."
msgstr ""
#. Tag: literal
@@ -1259,13 +1013,7 @@
#. Tag: para
#: Annotations.xml:874
#, no-c-format
-msgid ""
-"\"Ends\" a jBPM task. Specifies that a long-running conversation ends when "
-"this method returns a non-null outcome, and that the current task is "
-"complete. Triggers a jBPM transition. The actual transition triggered will "
-"be the default transition unless the application has called "
-"<literal>Transition.setName()</literal> on the built-in component named "
-"<literal>transition</literal>."
+msgid "\"Ends\" a jBPM task. Specifies that a long-running conversation ends when this method returns a non-null outcome, and that the current task is complete. Triggers a jBPM transition. The actual transition triggered will be the default transition unless the application has called <literal>Transition.setName()</literal> on the built-in component named <literal>transition</literal>."
msgstr ""
#. Tag: programlisting
@@ -1283,9 +1031,7 @@
#. Tag: para
#: Annotations.xml:889
#, no-c-format
-msgid ""
-"<literal>transition</literal> — the name of the jBPM transition to be "
-"triggered when ending the task. Defaults to the default transition."
+msgid "<literal>transition</literal> — the name of the jBPM transition to be triggered when ending the task. Defaults to the default transition."
msgstr ""
#. Tag: literal
@@ -1303,20 +1049,13 @@
#. Tag: para
#: Annotations.xml:915
#, no-c-format
-msgid ""
-"Creates a new jBPM process instance when the method returns a non-null "
-"outcome without exception. The <literal>ProcessInstance</literal> object "
-"will be available in a context variable named <literal>processInstance</"
-"literal>."
+msgid "Creates a new jBPM process instance when the method returns a non-null outcome without exception. The <literal>ProcessInstance</literal> object will be available in a context variable named <literal>processInstance</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:924
#, no-c-format
-msgid ""
-"<literal>definition</literal> — the name of the jBPM process "
-"definition deployed via <literal>org.jboss.seam.bpm.jbpm.processDefinitions</"
-"literal>."
+msgid "<literal>definition</literal> — the name of the jBPM process definition deployed via <literal>org.jboss.seam.bpm.jbpm.processDefinitions</literal>."
msgstr ""
#. Tag: literal
@@ -1334,19 +1073,13 @@
#. Tag: para
#: Annotations.xml:939
#, no-c-format
-msgid ""
-"Re-enters the scope of an existing jBPM process instance when the method "
-"returns a non-null outcome without exception. The <literal>ProcessInstance</"
-"literal> object will be available in a context variable named "
-"<literal>processInstance</literal>."
+msgid "Re-enters the scope of an existing jBPM process instance when the method returns a non-null outcome without exception. The <literal>ProcessInstance</literal> object will be available in a context variable named <literal>processInstance</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:948
#, no-c-format
-msgid ""
-"<literal>processIdParameter</literal> — the name a request parameter "
-"holding the process id. Default to <literal>\"processId\"</literal>."
+msgid "<literal>processIdParameter</literal> — the name a request parameter holding the process id. Default to <literal>\"processId\"</literal>."
msgstr ""
#. Tag: literal
@@ -1364,9 +1097,7 @@
#. Tag: para
#: Annotations.xml:964
#, no-c-format
-msgid ""
-"Marks a method as signalling a transition in the current jBPM process "
-"instance whenever the method returns a non-null result."
+msgid "Marks a method as signalling a transition in the current jBPM process instance whenever the method returns a non-null result."
msgstr ""
#. Tag: title
@@ -1378,9 +1109,7 @@
#. Tag: para
#: Annotations.xml:976
#, no-c-format
-msgid ""
-"Seam provides an annotation that lets you force a rollback of the JTA "
-"transaction for certain action listener outcomes."
+msgid "Seam provides an annotation that lets you force a rollback of the JTA transaction for certain action listener outcomes."
msgstr ""
#. Tag: literal
@@ -1398,20 +1127,13 @@
#. Tag: para
#: Annotations.xml:988
#, no-c-format
-msgid ""
-"Specifies that a JavaBean component should have a similar transactional "
-"behavior to the default behavior of a session bean component. ie. method "
-"invocations should take place in a transaction, and if no transaction exists "
-"when the method is called, a transaction will be started just for that "
-"method. This annotation may be applied at either class or method level."
+msgid "Specifies that a JavaBean component should have a similar transactional behavior to the default behavior of a session bean component. ie. method invocations should take place in a transaction, and if no transaction exists when the method is called, a transaction will be started just for that method. This annotation may be applied at either class or method level."
msgstr ""
#. Tag: emphasis
#: Annotations.xml:997
#, no-c-format
-msgid ""
-"Do not use this annotation on EJB 3.0 components, use "
-"<literal>@TransactionAttribute</literal>!"
+msgid "Do not use this annotation on EJB 3.0 components, use <literal>@TransactionAttribute</literal>!"
msgstr ""
#. Tag: literal
@@ -1429,36 +1151,25 @@
#. Tag: para
#: Annotations.xml:1008
#, no-c-format
-msgid ""
-"Synonym for javax.ejb.ApplicationException, for use in a pre Java EE 5 "
-"environment. Applied to an exception to denote that it is an application "
-"exception and should be reported to the client directly(i.e., unwrapped)."
+msgid "Synonym for javax.ejb.ApplicationException, for use in a pre Java EE 5 environment. Applied to an exception to denote that it is an application exception and should be reported to the client directly(i.e., unwrapped)."
msgstr ""
#. Tag: para
#: Annotations.xml:1014
#, no-c-format
-msgid ""
-"<emphasis>Do not use this annotation on EJB 3.0 components, use "
-"<literal>@javax.ejb.ApplicationException</literal> instead</emphasis>."
+msgid "<emphasis>Do not use this annotation on EJB 3.0 components, use <literal>@javax.ejb.ApplicationException</literal> instead</emphasis>."
msgstr ""
#. Tag: para
#: Annotations.xml:1021
#, no-c-format
-msgid ""
-"<literal>rollback</literal> — by default <literal>false</literal>, if "
-"<literal>true</literal> this exception should set the transaction to "
-"rollback only"
+msgid "<literal>rollback</literal> — by default <literal>false</literal>, if <literal>true</literal> this exception should set the transaction to rollback only"
msgstr ""
#. Tag: para
#: Annotations.xml:1029
#, no-c-format
-msgid ""
-"<literal>end</literal> — by default <literal>false</literal>, if "
-"<literal>true</literal> this exception should end the current long-running "
-"conversation"
+msgid "<literal>end</literal> — by default <literal>false</literal>, if <literal>true</literal> this exception should end the current long-running conversation"
msgstr ""
#. Tag: literal
@@ -1476,26 +1187,19 @@
#. Tag: para
#: Annotations.xml:1045
#, no-c-format
-msgid ""
-"Synonym for javax.interceptors.Interceptors, for use in a pre Java EE 5 "
-"environment. Note that this may only be used as a meta-annotation. Declares "
-"an ordered list of interceptors for a class or method."
+msgid "Synonym for javax.interceptors.Interceptors, for use in a pre Java EE 5 environment. Note that this may only be used as a meta-annotation. Declares an ordered list of interceptors for a class or method."
msgstr ""
#. Tag: para
#: Annotations.xml:1051
#, no-c-format
-msgid ""
-"<emphasis>Do not use this annotations on EJB 3.0 components, use "
-"<literal>@javax.interceptor.Interceptors</literal> instead</emphasis>."
+msgid "<emphasis>Do not use this annotations on EJB 3.0 components, use <literal>@javax.interceptor.Interceptors</literal> instead</emphasis>."
msgstr ""
#. Tag: para
#: Annotations.xml:1060
#, no-c-format
-msgid ""
-"These annotations are mostly useful for JavaBean Seam components. If you use "
-"EJB 3.0 components, you should use the standard Java EE5 annotation."
+msgid "These annotations are mostly useful for JavaBean Seam components. If you use EJB 3.0 components, you should use the standard Java EE5 annotation."
msgstr ""
#. Tag: title
@@ -1507,66 +1211,57 @@
#. Tag: para
#: Annotations.xml:1070
#, no-c-format
-msgid ""
-"These annotations let you specify how Seam should handle an exception that "
-"propagates out of a Seam component."
+msgid "These annotations let you specify how Seam should handle an exception that propagates out of a Seam component."
msgstr ""
#. Tag: literal
#: Annotations.xml:1078
#, no-c-format
msgid "@Redirect"
-msgstr ""
+msgstr "@Redirect"
#. Tag: programlisting
#: Annotations.xml:1081
#, no-c-format
msgid "<![CDATA[@Redirect(viewId=\"error.jsp\")]]>"
-msgstr ""
+msgstr "<![CDATA[@Redirect(viewId=\"error.jsp\")]]>"
#. Tag: para
#: Annotations.xml:1082
#, no-c-format
-msgid ""
-"Specifies that the annotated exception causes a browser redirect to a "
-"specified view id."
+msgid "Specifies that the annotated exception causes a browser redirect to a specified view id."
msgstr ""
#. Tag: para
#: Annotations.xml:1088
#, no-c-format
-msgid ""
-"<literal>viewId</literal> — specifies the JSF view id to redirect to. "
-"You can use EL here."
+msgid "<literal>viewId</literal> — specifies the JSF view id to redirect to. You can use EL here."
msgstr ""
#. Tag: para
#: Annotations.xml:1094
#, no-c-format
-msgid ""
-"<literal>message</literal> — a message to be displayed, default to the "
-"exception message."
+msgid "<literal>message</literal> — a message to be displayed, default to the exception message."
msgstr ""
#. Tag: para
-#: Annotations.xml:1100 Annotations.xml:1133
+#: Annotations.xml:1100
+#: Annotations.xml:1133
#, no-c-format
-msgid ""
-"<literal>end</literal> — specifies that the long-running conversation "
-"should end, default to <literal>false</literal>."
+msgid "<literal>end</literal> — specifies that the long-running conversation should end, default to <literal>false</literal>."
msgstr ""
#. Tag: literal
#: Annotations.xml:1111
#, no-c-format
msgid "@HttpError"
-msgstr ""
+msgstr "@HttpError"
#. Tag: programlisting
#: Annotations.xml:1114
#, no-c-format
msgid "<![CDATA[@HttpError(errorCode=404)]]>"
-msgstr ""
+msgstr "<![CDATA[@HttpError(errorCode=404)]]>"
#. Tag: para
#: Annotations.xml:1115
@@ -1577,17 +1272,13 @@
#. Tag: para
#: Annotations.xml:1121
#, no-c-format
-msgid ""
-"<literal>errorCode</literal> — the HTTP error code, default to "
-"<literal>500</literal>."
+msgid "<literal>errorCode</literal> — the HTTP error code, default to <literal>500</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:1127
#, no-c-format
-msgid ""
-"<literal>message</literal> — a message to be sent with the HTTP error, "
-"default to the exception message."
+msgid "<literal>message</literal> — a message to be sent with the HTTP error, default to the exception message."
msgstr ""
#. Tag: title
@@ -1599,31 +1290,25 @@
#. Tag: para
#: Annotations.xml:1147
#, no-c-format
-msgid ""
-"Seam Remoting requires that the local interface of a session bean be "
-"annotated with the following annotation:"
+msgid "Seam Remoting requires that the local interface of a session bean be annotated with the following annotation:"
msgstr ""
#. Tag: literal
#: Annotations.xml:1155
#, no-c-format
msgid "@WebRemote"
-msgstr ""
+msgstr "@WebRemote"
#. Tag: programlisting
#: Annotations.xml:1158
#, no-c-format
msgid "<![CDATA[@WebRemote(exclude=\"path.to.exclude\")]]>"
-msgstr ""
+msgstr "<![CDATA[@WebRemote(exclude=\"path.to.exclude\")]]>"
#. Tag: para
#: Annotations.xml:1159
#, no-c-format
-msgid ""
-"Indicates that the annotated method may be called from client-side "
-"JavaScript. The <literal>exclude</literal> property is optional and allows "
-"objects to be excluded from the result's object graph (see the Remoting "
-"chapter for more details)."
+msgid "Indicates that the annotated method may be called from client-side JavaScript. The <literal>exclude</literal> property is optional and allows objects to be excluded from the result's object graph (see the Remoting chapter for more details)."
msgstr ""
#. Tag: title
@@ -1641,9 +1326,7 @@
#. Tag: para
#: Annotations.xml:1177
#, no-c-format
-msgid ""
-"Please refer to the documentation for the EJB 3.0 specification for "
-"information about the annotations required for EJB interceptor definition."
+msgid "Please refer to the documentation for the EJB 3.0 specification for information about the annotations required for EJB interceptor definition."
msgstr ""
#. Tag: literal
@@ -1656,60 +1339,48 @@
#: Annotations.xml:1188
#, no-c-format
msgid "<![CDATA[@Interceptor(stateless=true)]]>"
-msgstr ""
+msgstr "<![CDATA[@Interceptor(stateless=true)]]>"
#. Tag: para
#: Annotations.xml:1189
#, no-c-format
-msgid ""
-"Specifies that this interceptor is stateless and Seam may optimize "
-"replication."
+msgid "Specifies that this interceptor is stateless and Seam may optimize replication."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1193
#, no-c-format
msgid "<![CDATA[@Interceptor(type=CLIENT)]]>"
-msgstr ""
+msgstr "<![CDATA[@Interceptor(type=CLIENT)]]>"
#. Tag: para
#: Annotations.xml:1194
#, no-c-format
-msgid ""
-"Specifies that this interceptor is a \"client-side\" interceptor that is "
-"called before the EJB container."
+msgid "Specifies that this interceptor is a \"client-side\" interceptor that is called before the EJB container."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1198
#, no-c-format
-msgid ""
-"<![CDATA[@Interceptor(around={SomeInterceptor.class, OtherInterceptor."
-"class})]]>"
-msgstr ""
+msgid "<![CDATA[@Interceptor(around={SomeInterceptor.class, OtherInterceptor.class})]]>"
+msgstr "<![CDATA[@Interceptor(around={SomeInterceptor.class, OtherInterceptor.class})]]>"
#. Tag: para
#: Annotations.xml:1199
#, no-c-format
-msgid ""
-"Specifies that this interceptor is positioned higher in the stack than the "
-"given interceptors."
+msgid "Specifies that this interceptor is positioned higher in the stack than the given interceptors."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1203
#, no-c-format
-msgid ""
-"<![CDATA[@Interceptor(within={SomeInterceptor.class, OtherInterceptor."
-"class})]]>"
-msgstr ""
+msgid "<![CDATA[@Interceptor(within={SomeInterceptor.class, OtherInterceptor.class})]]>"
+msgstr "<![CDATA[@Interceptor(within={SomeInterceptor.class, OtherInterceptor.class})]]>"
#. Tag: para
#: Annotations.xml:1204
#, no-c-format
-msgid ""
-"Specifies that this interceptor is positioned deeper in the stack than the "
-"given interceptors."
+msgid "Specifies that this interceptor is positioned deeper in the stack than the given interceptors."
msgstr ""
#. Tag: title
@@ -1721,18 +1392,14 @@
#. Tag: para
#: Annotations.xml:1216
#, no-c-format
-msgid ""
-"The following annotations are used to declare an asynchronous method, for "
-"example:"
+msgid "The following annotations are used to declare an asynchronous method, for example:"
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1221
#, no-c-format
-msgid ""
-"<![CDATA[@Asynchronous public void scheduleAlert(Alert alert, @Expiration "
-"Date date) { ... }]]>"
-msgstr ""
+msgid "<![CDATA[@Asynchronous public void scheduleAlert(Alert alert, @Expiration Date date) { ... }]]>"
+msgstr "<![CDATA[@Asynchronous public void scheduleAlert(Alert alert, @Expiration Date date) { ... }]]>"
#. Tag: programlisting
#: Annotations.xml:1222
@@ -1742,18 +1409,21 @@
" @Expiration Date date, \n"
" @IntervalDuration long interval) { ... }]]>"
msgstr ""
+"<![CDATA[@Asynchronous public Timer scheduleAlerts(Alert alert, \n"
+" @Expiration Date date, \n"
+" @IntervalDuration long interval) { ... }]]>"
#. Tag: literal
#: Annotations.xml:1227
#, no-c-format
msgid "@Asynchronous"
-msgstr ""
+msgstr "@Asynchronous"
#. Tag: programlisting
#: Annotations.xml:1230
#, no-c-format
msgid "<![CDATA[@Asynchronous]]>"
-msgstr ""
+msgstr "<![CDATA[@Asynchronous]]>"
#. Tag: para
#: Annotations.xml:1231
@@ -1765,60 +1435,54 @@
#: Annotations.xml:1238
#, no-c-format
msgid "@Duration"
-msgstr ""
+msgstr "@Duration"
#. Tag: programlisting
#: Annotations.xml:1241
#, no-c-format
msgid "<![CDATA[@Duration]]>"
-msgstr ""
+msgstr "<![CDATA[@Duration]]>"
#. Tag: para
#: Annotations.xml:1242
#, no-c-format
-msgid ""
-"Specifies that a parameter of the asynchronous call is the duration before "
-"the call is processed (or first processed for recurring calls)."
+msgid "Specifies that a parameter of the asynchronous call is the duration before the call is processed (or first processed for recurring calls)."
msgstr ""
#. Tag: literal
#: Annotations.xml:1251
#, no-c-format
msgid "@Expiration"
-msgstr ""
+msgstr "@Expiration"
#. Tag: programlisting
#: Annotations.xml:1254
#, no-c-format
msgid "<![CDATA[@Expiration]]>"
-msgstr ""
+msgstr "<![CDATA[@Expiration]]>"
#. Tag: para
#: Annotations.xml:1255
#, no-c-format
-msgid ""
-"Specifies that a parameter of the asynchronous call is the datetime at which "
-"the call is processed (or first processed for recurring calls)."
+msgid "Specifies that a parameter of the asynchronous call is the datetime at which the call is processed (or first processed for recurring calls)."
msgstr ""
#. Tag: literal
#: Annotations.xml:1264
#, no-c-format
msgid "@IntervalDuration"
-msgstr ""
+msgstr "@IntervalDuration"
#. Tag: programlisting
#: Annotations.xml:1267
#, no-c-format
msgid "<![CDATA[@IntervalDuration]]>"
-msgstr ""
+msgstr "<![CDATA[@IntervalDuration]]>"
#. Tag: para
#: Annotations.xml:1268
#, no-c-format
-msgid ""
-"Specifies that an asynchronous method call recurs, and that the annotationed "
-"parameter is duration between recurrences."
+msgid "Specifies that an asynchronous method call recurs, and that the annotationed parameter is duration between recurrences."
msgstr ""
#. Tag: title
@@ -1837,54 +1501,42 @@
#: Annotations.xml:1286
#, no-c-format
msgid "@Converter"
-msgstr ""
+msgstr "@Converter"
#. Tag: para
#: Annotations.xml:1289
#, no-c-format
-msgid ""
-"Allows a Seam component to act as a JSF converter. The annotated class must "
-"be a Seam component, and must implement <literal>javax.faces.convert."
-"Converter</literal>."
+msgid "Allows a Seam component to act as a JSF converter. The annotated class must be a Seam component, and must implement <literal>javax.faces.convert.Converter</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:1296
#, no-c-format
-msgid ""
-"<literal>id</literal> — the JSF converter id. Defaults to the "
-"component name."
+msgid "<literal>id</literal> — the JSF converter id. Defaults to the component name."
msgstr ""
#. Tag: para
#: Annotations.xml:1302
#, no-c-format
-msgid ""
-"<literal>forClass</literal> — if specified, register this component as "
-"the default converter for a type."
+msgid "<literal>forClass</literal> — if specified, register this component as the default converter for a type."
msgstr ""
#. Tag: literal
#: Annotations.xml:1313
#, no-c-format
msgid "@Validator"
-msgstr ""
+msgstr "@Validator"
#. Tag: para
#: Annotations.xml:1316
#, no-c-format
-msgid ""
-"Allows a Seam component to act as a JSF validator. The annotated class must "
-"be a Seam component, and must implement <literal>javax.faces.validator."
-"Validator</literal>."
+msgid "Allows a Seam component to act as a JSF validator. The annotated class must be a Seam component, and must implement <literal>javax.faces.validator.Validator</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:1323
#, no-c-format
-msgid ""
-"<literal>id</literal> — the JSF validator id. Defaults to the "
-"component name."
+msgid "<literal>id</literal> — the JSF validator id. Defaults to the component name."
msgstr ""
#. Tag: title
@@ -1896,121 +1548,86 @@
#. Tag: para
#: Annotations.xml:1335
#, no-c-format
-msgid ""
-"The following annotations make it easy to implement clickable lists backed "
-"by a stateful session bean. They appear on attributes."
+msgid "The following annotations make it easy to implement clickable lists backed by a stateful session bean. They appear on attributes."
msgstr ""
#. Tag: literal
#: Annotations.xml:1344
#, no-c-format
msgid "@DataModel"
-msgstr ""
+msgstr "@DataModel"
#. Tag: programlisting
#: Annotations.xml:1347
#, no-c-format
msgid "<![CDATA[@DataModel(\"variableName\")]]>"
-msgstr ""
+msgstr "<![CDATA[@DataModel(\"variableName\")]]>"
#. Tag: para
#: Annotations.xml:1348
#, no-c-format
-msgid ""
-"Outjects a property of type <literal>List</literal>, <literal>Map</literal>, "
-"<literal>Set</literal> or <literal>Object[]</literal> as a JSF "
-"<literal>DataModel</literal> into the scope of the owning component (or the "
-"<literal>EVENT</literal> scope if the owning component is "
-"<literal>STATELESS</literal>). In the case of <literal>Map</literal>, each "
-"row of the <literal>DataModel</literal> is a <literal>Map.Entry</literal>."
+msgid "Outjects a property of type <literal>List</literal>, <literal>Map</literal>, <literal>Set</literal> or <literal>Object[]</literal> as a JSF <literal>DataModel</literal> into the scope of the owning component (or the <literal>EVENT</literal> scope if the owning component is <literal>STATELESS</literal>). In the case of <literal>Map</literal>, each row of the <literal>DataModel</literal> is a <literal>Map.Entry</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:1361
#, no-c-format
-msgid ""
-"<literal>value</literal> — name of the conversation context variable. "
-"Default to the attribute name."
+msgid "<literal>value</literal> — name of the conversation context variable. Default to the attribute name."
msgstr ""
#. Tag: para
#: Annotations.xml:1368
#, no-c-format
-msgid ""
-"<literal>scope</literal> — if <literal>scope=ScopeType.PAGE</literal> "
-"is explicitly specified, the <literal>DataModel</literal> will be kept in "
-"the <literal>PAGE</literal> context."
+msgid "<literal>scope</literal> — if <literal>scope=ScopeType.PAGE</literal> is explicitly specified, the <literal>DataModel</literal> will be kept in the <literal>PAGE</literal> context."
msgstr ""
#. Tag: literal
#: Annotations.xml:1380
#, no-c-format
msgid "@DataModelSelection"
-msgstr ""
+msgstr "@DataModelSelection"
#. Tag: programlisting
#: Annotations.xml:1383
#, no-c-format
msgid "<![CDATA[@DataModelSelection]]>"
-msgstr ""
+msgstr "<![CDATA[@DataModelSelection]]>"
#. Tag: para
#: Annotations.xml:1384
#, no-c-format
-msgid ""
-"Injects the selected value from the JSF <literal>DataModel</literal> (this "
-"is the element of the underlying collection, or the map value). If only one "
-"<literal>@DataModel</literal> attribute is defined for a component, the "
-"selected value from that <literal>DataModel</literal> will be injected. "
-"Otherwise, the component name of each <literal>@DataModel</literal> must be "
-"specified in the value attribute for each <literal>@DataModelSelection</"
-"literal>."
+msgid "Injects the selected value from the JSF <literal>DataModel</literal> (this is the element of the underlying collection, or the map value). If only one <literal>@DataModel</literal> attribute is defined for a component, the selected value from that <literal>DataModel</literal> will be injected. Otherwise, the component name of each <literal>@DataModel</literal> must be specified in the value attribute for each <literal>@DataModelSelection</literal>."
msgstr ""
#. Tag: para
#: Annotations.xml:1396
#, no-c-format
-msgid ""
-"If <literal>PAGE</literal> scope is specified on the associated "
-"<literal>@DataModel</literal>, then, in addition to the DataModel Selection "
-"being injected, the associated DataModel will also be injected. In this "
-"case, if the property annotated with <literal>@DataModel</literal> is a "
-"getter method, then a setter method for the property must also be part of "
-"the Business API of the containing Seam Component."
+msgid "If <literal>PAGE</literal> scope is specified on the associated <literal>@DataModel</literal>, then, in addition to the DataModel Selection being injected, the associated DataModel will also be injected. In this case, if the property annotated with <literal>@DataModel</literal> is a getter method, then a setter method for the property must also be part of the Business API of the containing Seam Component."
msgstr ""
#. Tag: para
-#: Annotations.xml:1408 Annotations.xml:1438
+#: Annotations.xml:1408
+#: Annotations.xml:1438
#, no-c-format
-msgid ""
-"<literal>value</literal> — name of the conversation context variable. "
-"Not needed if there is exactly one <literal>@DataModel</literal> in the "
-"component."
+msgid "<literal>value</literal> — name of the conversation context variable. Not needed if there is exactly one <literal>@DataModel</literal> in the component."
msgstr ""
#. Tag: literal
#: Annotations.xml:1420
#, no-c-format
msgid "@DataModelSelectionIndex"
-msgstr ""
+msgstr "@DataModelSelectionIndex"
#. Tag: programlisting
#: Annotations.xml:1423
#, no-c-format
msgid "<![CDATA[@DataModelSelectionIndex]]>"
-msgstr ""
+msgstr "<![CDATA[@DataModelSelectionIndex]]>"
#. Tag: para
#: Annotations.xml:1424
#, no-c-format
-msgid ""
-"Exposes the selection index of the JSF <literal>DataModel</literal> as an "
-"attribute of the component (this is the row number of the underlying "
-"collection, or the map key). If only one <literal>@DataModel</literal> "
-"attribute is defined for a component, the selected value from that "
-"<literal>DataModel</literal> will be injected. Otherwise, the component name "
-"of each <literal>@DataModel</literal> must be specified in the value "
-"attribute for each <literal>@DataModelSelectionIndex</literal>."
+msgid "Exposes the selection index of the JSF <literal>DataModel</literal> as an attribute of the component (this is the row number of the underlying collection, or the map key). If only one <literal>@DataModel</literal> attribute is defined for a component, the selected value from that <literal>DataModel</literal> will be injected. Otherwise, the component name of each <literal>@DataModel</literal> must be specified in the value attribute for each <literal>@DataModelSelectionIndex</literal>."
msgstr ""
#. Tag: title
@@ -2022,23 +1639,20 @@
#. Tag: para
#: Annotations.xml:1454
#, no-c-format
-msgid ""
-"These meta-annotations make it possible to implement similar functionality "
-"to <literal>@DataModel</literal> and <literal>@DataModelSelection</literal> "
-"for other datastructures apart from lists."
+msgid "These meta-annotations make it possible to implement similar functionality to <literal>@DataModel</literal> and <literal>@DataModelSelection</literal> for other datastructures apart from lists."
msgstr ""
#. Tag: literal
#: Annotations.xml:1464
#, no-c-format
msgid "@DataBinderClass"
-msgstr ""
+msgstr "@DataBinderClass"
#. Tag: programlisting
#: Annotations.xml:1467
#, no-c-format
msgid "<![CDATA[@DataBinderClass(DataModelBinder.class)]]>"
-msgstr ""
+msgstr "<![CDATA[@DataBinderClass(DataModelBinder.class)]]>"
#. Tag: para
#: Annotations.xml:1468
@@ -2050,13 +1664,13 @@
#: Annotations.xml:1475
#, no-c-format
msgid "@DataSelectorClass"
-msgstr ""
+msgstr "@DataSelectorClass"
#. Tag: programlisting
#: Annotations.xml:1478
#, no-c-format
msgid "<![CDATA[@DataSelectorClass(DataModelSelector.class)]]>"
-msgstr ""
+msgstr "<![CDATA[@DataSelectorClass(DataModelSelector.class)]]>"
#. Tag: para
#: Annotations.xml:1479
@@ -2073,52 +1687,37 @@
#. Tag: para
#: Annotations.xml:1489
#, no-c-format
-msgid ""
-"This annotation provides a mechanism for declaring information about a set "
-"of components that are packaged together. It can be applied to any Java "
-"package."
+msgid "This annotation provides a mechanism for declaring information about a set of components that are packaged together. It can be applied to any Java package."
msgstr ""
#. Tag: literal
#: Annotations.xml:1499
#, no-c-format
msgid "@Namespace"
-msgstr ""
+msgstr "@Namespace"
#. Tag: programlisting
#: Annotations.xml:1502
#, no-c-format
-msgid ""
-"<![CDATA[@Namespace(value=\"http://jboss.com/products/seam/example/seampay"
-"\")]]>"
-msgstr ""
+msgid "<![CDATA[@Namespace(value=\"http://jboss.com/products/seam/example/seampay\")]]>"
+msgstr "<![CDATA[@Namespace(value=\"http://jboss.com/products/seam/example/seampay\")]]>"
#. Tag: para
#: Annotations.xml:1503
#, no-c-format
-msgid ""
-"Specifies that components in the current package are associated with the "
-"given namespace. The declared namespace can be used as an XML namespace in a "
-"<literal>components.xml</literal> file to simplify application configuration."
+msgid "Specifies that components in the current package are associated with the given namespace. The declared namespace can be used as an XML namespace in a <literal>components.xml</literal> file to simplify application configuration."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1509
#, no-c-format
-msgid ""
-"<![CDATA[@Namespace(value=\"http://jboss.com/products/seam/core\", prefix="
-"\"org.jboss.seam.core\")]]>"
-msgstr ""
+msgid "<![CDATA[@Namespace(value=\"http://jboss.com/products/seam/core\", prefix=\"org.jboss.seam.core\")]]>"
+msgstr "<![CDATA[@Namespace(value=\"http://jboss.com/products/seam/core\", prefix=\"org.jboss.seam.core\")]]>"
#. Tag: para
#: Annotations.xml:1510
#, no-c-format
-msgid ""
-"Specifies a namespace to associate with a given package. Additionally, it "
-"specifies a component name prefix to be applied to component names specified "
-"in the XML file. For example, an XML element named <literal>init</literal> "
-"that is associated with this namespace would be understood to actually refer "
-"to a component named <literal>org.jboss.seam.core.init</literal>."
+msgid "Specifies a namespace to associate with a given package. Additionally, it specifies a component name prefix to be applied to component names specified in the XML file. For example, an XML element named <literal>init</literal> that is associated with this namespace would be understood to actually refer to a component named <literal>org.jboss.seam.core.init</literal>."
msgstr ""
#. Tag: title
@@ -2130,9 +1729,7 @@
#. Tag: para
#: Annotations.xml:1526
#, no-c-format
-msgid ""
-"These annotations allow you to integrate your Seam components with the "
-"servlet container."
+msgid "These annotations allow you to integrate your Seam components with the servlet container."
msgstr ""
#. Tag: literal
@@ -2144,36 +1741,30 @@
#. Tag: para
#: Annotations.xml:1538
#, no-c-format
-msgid ""
-"Use the Seam component (which implements <literal>javax.servlet.Filter</"
-"literal>) annotated with <literal>@Filter</literal> as a servlet filter. It "
-"will be executed by Seam's master filter."
+msgid "Use the Seam component (which implements <literal>javax.servlet.Filter</literal>) annotated with <literal>@Filter</literal> as a servlet filter. It will be executed by Seam's master filter."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1546
#, no-c-format
msgid "<![CDATA[@Filter(around={\"seamComponent\", \"otherSeamComponent\"})]]>"
-msgstr ""
+msgstr "<![CDATA[@Filter(around={\"seamComponent\", \"otherSeamComponent\"})]]>"
#. Tag: para
#: Annotations.xml:1547
#, no-c-format
-msgid ""
-"Specifies that this filter is positioned higher in the stack than the given "
-"filters."
+msgid "Specifies that this filter is positioned higher in the stack than the given filters."
msgstr ""
#. Tag: programlisting
#: Annotations.xml:1553
#, no-c-format
msgid "<![CDATA[@Filter(within={\"seamComponent\", \"otherSeamComponent\"})]]>"
-msgstr ""
+msgstr "<![CDATA[@Filter(within={\"seamComponent\", \"otherSeamComponent\"})]]>"
#. Tag: para
#: Annotations.xml:1554
#, no-c-format
-msgid ""
-"Specifies that this filter is positioned deeper in the stack than the given "
-"filters."
+msgid "Specifies that this filter is positioned deeper in the stack than the given filters."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -5,138 +5,143 @@
msgstr ""
"Project-Id-Version: seam 2_0\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-11-06 00:22+0000\n"
-"PO-Revision-Date: 2008-05-03 11:34+0000\n"
-"Last-Translator: Automatically generated\n"
+"POT-Creation-Date: 2008-10-14 11:38+0000\n"
+"PO-Revision-Date: 2008-11-23 17:06+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: author
-#: Author_Group.xml:5
+#: Author_Group.xml:3
#, no-c-format
msgid "<firstname>Gavin</firstname> <surname>King</surname>"
-msgstr ""
+msgstr "<firstname>Gavin</firstname> <surname>King</surname>"
+#. Tag: shortaffil
+#: Author_Group.xml:7
+#, no-c-format
+msgid "Project Lead"
+msgstr "Capo progetto"
+
#. Tag: author
-#: Author_Group.xml:9
+#: Author_Group.xml:10
#, no-c-format
msgid "<firstname>Pete</firstname> <surname>Muir</surname>"
-msgstr ""
+msgstr "<firstname>Pete</firstname> <surname>Muir</surname>"
#. Tag: author
-#: Author_Group.xml:13
+#: Author_Group.xml:14
#, no-c-format
msgid "<firstname>Norman</firstname> <surname>Richards</surname>"
-msgstr ""
+msgstr "<firstname>Norman</firstname> <surname>Richards</surname>"
#. Tag: author
-#: Author_Group.xml:17
+#: Author_Group.xml:18
#, no-c-format
msgid "<firstname>Shane</firstname> <surname>Bryzak</surname>"
-msgstr ""
+msgstr "<firstname>Shane</firstname> <surname>Bryzak</surname>"
#. Tag: author
-#: Author_Group.xml:21
+#: Author_Group.xml:22
#, no-c-format
msgid "<firstname>Michael</firstname> <surname>Yuan</surname>"
-msgstr ""
+msgstr "<firstname>Michael</firstname> <surname>Yuan</surname>"
#. Tag: author
-#: Author_Group.xml:25
+#: Author_Group.xml:26
#, no-c-format
msgid "<firstname>Mike</firstname> <surname>Youngstrom</surname>"
-msgstr ""
+msgstr "<firstname>Mike</firstname> <surname>Youngstrom</surname>"
#. Tag: author
-#: Author_Group.xml:29
+#: Author_Group.xml:30
#, no-c-format
msgid "<firstname>Christian</firstname> <surname>Bauer</surname>"
-msgstr ""
+msgstr "<firstname>Michael</firstname> <surname>Yuan</surname>"
#. Tag: author
-#: Author_Group.xml:33
+#: Author_Group.xml:34
#, no-c-format
msgid "<firstname>Jay</firstname> <surname>Balunas</surname>"
-msgstr ""
+msgstr "<firstname>Jay</firstname> <surname>Balunas</surname>"
#. Tag: author
-#: Author_Group.xml:37
+#: Author_Group.xml:38
#, no-c-format
msgid "<firstname>Dan</firstname> <surname>Allen</surname>"
-msgstr ""
+msgstr "<firstname>Dan</firstname> <surname>Allen</surname>"
#. Tag: author
-#: Author_Group.xml:41
+#: Author_Group.xml:42
#, no-c-format
-msgid ""
-"<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</"
-"surname>"
-msgstr ""
+msgid "<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</surname>"
+msgstr "<firstname>Max</firstname> <othername>Rydahl</othername> <surname>Andersen</surname>"
#. Tag: author
-#: Author_Group.xml:46
+#: Author_Group.xml:47
#, no-c-format
msgid "<firstname>Emmanuel</firstname> <surname>Bernard</surname>"
-msgstr ""
+msgstr "<firstname>Emmanuel</firstname> <surname>Bernard</surname>"
#. Tag: author
-#: Author_Group.xml:50
+#: Author_Group.xml:51
#, no-c-format
msgid "<firstname>Nicklas</firstname> <surname>Karlsson</surname>"
-msgstr ""
+msgstr "<firstname>Nicklas</firstname> <surname>Karlsson</surname>"
#. Tag: author
-#: Author_Group.xml:54
+#: Author_Group.xml:55
#, no-c-format
msgid "<firstname>Daniel</firstname> <surname>Roth</surname>"
-msgstr ""
+msgstr "<firstname>Daniel</firstname> <surname>Roth</surname>"
#. Tag: author
-#: Author_Group.xml:58
+#: Author_Group.xml:59
#, no-c-format
msgid "<firstname>Matt</firstname> <surname>Drees</surname>"
-msgstr ""
+msgstr "<firstname>Matt</firstname> <surname>Drees</surname>"
#. Tag: author
-#: Author_Group.xml:62
+#: Author_Group.xml:63
#, no-c-format
msgid "<firstname>Jacob</firstname> <surname>Orshalick</surname>"
-msgstr ""
+msgstr "<firstname>Jacob</firstname> <surname>Orshalick</surname>"
#. Tag: author
-#: Author_Group.xml:66
+#: Author_Group.xml:67
#, no-c-format
msgid "<firstname>Marek</firstname> <surname>Novotny</surname>"
-msgstr ""
+msgstr "<firstname>Marek</firstname> <surname>Novotny</surname>"
#. Tag: othercredit
-#: Author_Group.xml:70
+#: Author_Group.xml:71
#, no-c-format
msgid "<firstname>James</firstname> <surname>Cobb</surname>"
-msgstr ""
+msgstr "<firstname>James</firstname> <surname>Cobb</surname>"
#. Tag: shortaffil
-#: Author_Group.xml:74 Author_Group.xml:81
+#: Author_Group.xml:75
+#: Author_Group.xml:82
#, no-c-format
msgid "Graphic Design"
-msgstr ""
+msgstr "Design Grafico"
#. Tag: othercredit
-#: Author_Group.xml:77
+#: Author_Group.xml:78
#, no-c-format
msgid "<firstname>Cheyenne</firstname> <surname>Weaver</surname>"
-msgstr ""
+msgstr "<firstname>Cheyenne</firstname> <surname>Weaver</surname>"
#. Tag: othercredit
-#: Author_Group.xml:84
+#: Author_Group.xml:85
#, no-c-format
msgid "<firstname>Mark</firstname> <surname>Newton</surname>"
-msgstr ""
+msgstr "<firstname>Mark</firstname> <surname>Newton</surname>"
#. Tag: othercredit
-#: Author_Group.xml:88
+#: Author_Group.xml:89
#, no-c-format
msgid "<firstname>Steve</firstname> <surname>Ebersole</surname>"
msgstr ""
@@ -154,7 +159,8 @@
msgstr ""
#. Tag: editor
-#: Author_Group.xml:99
+#: Author_Group.xml:93
#, no-c-format
msgid "<firstname>Samson</firstname> <surname>Kittoli</surname>"
-msgstr ""
+msgstr "<firstname>Samson</firstname> <surname>Kittoli</surname>"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -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-06 21:25+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,31 +17,24 @@
#: Drools.xml:5
#, no-c-format
msgid "Seam and JBoss Rules"
-msgstr ""
+msgstr "Seam e JBoss Rules"
#. Tag: para
#: 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 ""
+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."
#. Tag: title
#: Drools.xml:13
#, no-c-format
msgid "Installing rules"
-msgstr ""
+msgstr "Installazione delle regole"
#. Tag: para
#: 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>:"
+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 ""
#. Tag: programlisting
@@ -54,45 +47,44 @@
" </drools:rule-files>\n"
"</drools:rule-base>]]>"
msgstr ""
+"<![CDATA[<drools:rule-base name=\"policyPricingRules\">\n"
+" <drools:rule-files>\n"
+" <value>policyPricingRules.drl</value>\n"
+" </drools:rule-files>\n"
+"</drools:rule-base>]]>"
#. Tag: para
#: 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."
+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 ""
#. Tag: para
#: Drools.xml:32
#, no-c-format
-msgid ""
-"If you want to use a Drools DSL, you alse need to specify the DSL definition:"
-msgstr ""
+msgid "If you want to use a Drools DSL, you alse need to specify the DSL definition:"
+msgstr "Se vuoi utilizzare una Drool DSL, devi specificare la definizione DSL:"
#. Tag: programlisting
#: Drools.xml:37
#, no-c-format
msgid ""
-"<![CDATA[<drools:rule-base name=\"policyPricingRules\" dsl-file="
-"\"policyPricing.dsl\">\n"
+"<![CDATA[<drools:rule-base name=\"policyPricingRules\" dsl-file=\"policyPricing.dsl\">\n"
" <drools:rule-files>\n"
" <value>policyPricingRules.drl</value>\n"
" </drools:rule-files>\n"
"</drools:rule-base>]]>"
msgstr ""
+"<![CDATA[<drools:rule-base name=\"policyPricingRules\" dsl-file=\"policyPricing.dsl\">\n"
+" <drools:rule-files>\n"
+" <value>policyPricingRules.drl</value>\n"
+" </drools:rule-files>\n"
+"</drools:rule-base>]]>"
#. Tag: para
#: 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>:"
+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 ""
#. Tag: programlisting
@@ -100,16 +92,15 @@
#, no-c-format
msgid ""
"<![CDATA[<drools:rule-agent name=\"insuranceRules\" \n"
-" configurationFile=\"/WEB-INF/deployedrules.properties\" /"
-">]]>"
+" configurationFile=\"/WEB-INF/deployedrules.properties\" />]]>"
msgstr ""
+"<![CDATA[<drools:rule-agent name=\"insuranceRules\" \n"
+" configurationFile=\"/WEB-INF/deployedrules.properties\" />]]>"
#. Tag: para
#: 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."
+msgid "The properties file contains properties specific to the RulesAgent. Here is an example configuration file from the Drools example distribution."
msgstr ""
#. Tag: programlisting
@@ -117,10 +108,8 @@
#, no-c-format
msgid ""
"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"
+"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"
msgstr ""
@@ -128,9 +117,7 @@
#. 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."
+msgid "It is also possible to configure the options on the component directly, bypassing the configuration file."
msgstr ""
#. Tag: programlisting
@@ -138,52 +125,45 @@
#, no-c-format
msgid ""
"<![CDATA[<drools:rule-agent name=\"insuranceRules\"\n"
-" url=\"http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/package/"
-"org.acme.insurance/fmeyer\"\n"
-" local-cache-dir=\"/Users/fernandomeyer/projects/jbossrules/drools-"
-"examples/drools-examples-brms/cache\"\n"
+" url=\"http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/package/org.acme.insurance/fmeyer\"\n"
+" local-cache-dir=\"/Users/fernandomeyer/projects/jbossrules/drools-examples/drools-examples-brms/cache\"\n"
" poll=\"30\"\n"
" configuration-name=\"insuranceconfig\" />]]>"
msgstr ""
+"<![CDATA[<drools:rule-agent name=\"insuranceRules\"\n"
+" url=\"http://localhost:8080/drools-jbrms/org.drools.brms.JBRMS/package/org.acme.insurance/fmeyer\"\n"
+" local-cache-dir=\"/Users/fernandomeyer/projects/jbossrules/drools-examples/drools-examples-brms/cache\"\n"
+" poll=\"30\"\n"
+" configuration-name=\"insuranceconfig\" />]]>"
#. Tag: para
#: 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.)"
+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 ""
#. Tag: programlisting
#: Drools.xml:65
#, no-c-format
-msgid ""
-"<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\" "
-"auto-create=\"true\" rule-base=\"#{policyPricingRules}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\" auto-create=\"true\" rule-base=\"#{policyPricingRules}\"/>]]>"
+msgstr "<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\" auto-create=\"true\" rule-base=\"#{policyPricingRules}\"/>]]>"
#. Tag: para
#: 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."
+msgid "Notice that we gave the <literal>policyPricingWorkingMemory</literal> a reference back to our rule base via the <literal>ruleBase</literal> configuration property."
msgstr ""
#. Tag: title
#: Drools.xml:76
#, no-c-format
msgid "Using rules from a Seam component"
-msgstr ""
+msgstr "Utilizzo delle regole da un componente SEAM"
#. Tag: para
#: Drools.xml:78
#, no-c-format
-msgid ""
-"We can now inject our <literal>WorkingMemory</literal> into any Seam "
-"component, assert facts, and fire rules:"
+msgid "We can now inject our <literal>WorkingMemory</literal> into any Seam component, assert facts, and fire rules:"
msgstr ""
#. Tag: programlisting
@@ -202,20 +182,28 @@
" policyPricingWorkingMemory.fireAllRules();\n"
"}]]>"
msgstr ""
+"<![CDATA[@In WorkingMemory policyPricingWorkingMemory;\n"
+"\n"
+"@In Policy policy;\n"
+"@In Customer customer;\n"
+"\n"
+"public void pricePolicy() throws FactException\n"
+"{\n"
+" policyPricingWorkingMemory.assertObject(policy);\n"
+" policyPricingWorkingMemory.assertObject(customer);\n"
+" policyPricingWorkingMemory.fireAllRules();\n"
+"}]]>"
#. Tag: title
#: Drools.xml:88
#, no-c-format
msgid "Using rules from a jBPM process definition"
-msgstr ""
+msgstr "Utilizzo delle regole da una definizione di processo jBPM"
#. Tag: para
#: 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."
+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 ""
#. Tag: programlisting
@@ -225,8 +213,7 @@
"<![CDATA[<decision name=\"approval\">\n"
" \n"
" <handler class=\"org.jboss.seam.drools.DroolsDecisionHandler\">\n"
-" <workingMemoryName>orderApprovalRulesWorkingMemory</"
-"workingMemoryName>\n"
+" <workingMemoryName>orderApprovalRulesWorkingMemory</workingMemoryName>\n"
" <assertObjects>\n"
" <element>#{customer}</element>\n"
" <element>#{order}</element>\n"
@@ -236,8 +223,7 @@
" \n"
" <transition name=\"approved\" to=\"ship\">\n"
" <action class=\"org.jboss.seam.drools.DroolsActionHandler\">\n"
-" <workingMemoryName>shippingRulesWorkingMemory</"
-"workingMemoryName>\n"
+" <workingMemoryName>shippingRulesWorkingMemory</workingMemoryName>\n"
" <assertObjects>\n"
" <element>#{customer}</element>\n"
" <element>#{order}</element>\n"
@@ -250,14 +236,36 @@
" \n"
"</decision>]]>"
msgstr ""
+"<![CDATA[<decision name=\"approval\">\n"
+" \n"
+" <handler class=\"org.jboss.seam.drools.DroolsDecisionHandler\">\n"
+" <workingMemoryName>orderApprovalRulesWorkingMemory</workingMemoryName>\n"
+" <assertObjects>\n"
+" <element>#{customer}</element>\n"
+" <element>#{order}</element>\n"
+" <element>#{order.lineItems}</element>\n"
+" </assertObjects>\n"
+" </handler>\n"
+" \n"
+" <transition name=\"approved\" to=\"ship\">\n"
+" <action class=\"org.jboss.seam.drools.DroolsActionHandler\">\n"
+" <workingMemoryName>shippingRulesWorkingMemory</workingMemoryName>\n"
+" <assertObjects>\n"
+" <element>#{customer}</element>\n"
+" <element>#{order}</element>\n"
+" <element>#{order.lineItems}</element>\n"
+" </assertObjects>\n"
+" </action>\n"
+" </transition>\n"
+" \n"
+" <transition name=\"rejected\" to=\"cancelled\"/>\n"
+" \n"
+"</decision>]]>"
#. Tag: para
#: 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>."
+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 ""
#. Tag: para
@@ -272,10 +280,8 @@
msgid ""
"<![CDATA[<task-node name=\"review\">\n"
" <task name=\"review\" description=\"Review Order\">\n"
-" <assignment handler=\"org.jboss.seam.drools.DroolsAssignmentHandler"
-"\">\n"
-" <workingMemoryName>orderApprovalRulesWorkingMemory</"
-"workingMemoryName>\n"
+" <assignment handler=\"org.jboss.seam.drools.DroolsAssignmentHandler\">\n"
+" <workingMemoryName>orderApprovalRulesWorkingMemory</workingMemoryName>\n"
" <assertObjects>\n"
" <element>#{actor}</element>\n"
" <element>#{customer}</element>\n"
@@ -288,18 +294,26 @@
" <transition name=\"approved\" to=\"approved\"/>\n"
"</task-node>]]>"
msgstr ""
+"<![CDATA[<task-node name=\"review\">\n"
+" <task name=\"review\" description=\"Review Order\">\n"
+" <assignment handler=\"org.jboss.seam.drools.DroolsAssignmentHandler\">\n"
+" <workingMemoryName>orderApprovalRulesWorkingMemory</workingMemoryName>\n"
+" <assertObjects>\n"
+" <element>#{actor}</element>\n"
+" <element>#{customer}</element>\n"
+" <element>#{order}</element>\n"
+" <element>#{order.lineItems}</element>\n"
+" </assertObjects>\n"
+" </assignment>\n"
+" </task>\n"
+" <transition name=\"rejected\" to=\"cancelled\"/>\n"
+" <transition name=\"approved\" to=\"approved\"/>\n"
+"</task-node>]]>"
#. 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>."
+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 ""
#. Tag: programlisting
@@ -320,6 +334,19 @@
" decision.setOutcome(\"approved\");\n"
"end]]>"
msgstr ""
+"<![CDATA[package org.jboss.seam.examples.shop\n"
+"\n"
+"import org.jboss.seam.drools.Decision\n"
+"\n"
+"global Decision decision\n"
+"\n"
+"rule \"Approve Order For Loyal Customer\"\n"
+" when\n"
+" Customer( loyaltyStatus == \"GOLD\" )\n"
+" Order( totalAmount <= 10000 )\n"
+" then\n"
+" decision.setOutcome(\"approved\");\n"
+"end]]>"
#. Tag: programlisting
#: Drools.xml:121
@@ -338,29 +365,34 @@
" assignable.setPooledActors( new String[] {\"reviewers\"} );\n"
"end]]>"
msgstr ""
+"<![CDATA[package org.jboss.seam.examples.shop\n"
+"\n"
+"import org.jbpm.taskmgmt.exe.Assignable\n"
+"\n"
+"global Assignable assignable\n"
+"\n"
+"rule \"Assign Review For Small Order\"\n"
+" when\n"
+" Order( totalAmount <= 100 )\n"
+" then\n"
+" assignable.setPooledActors( new String[] {\"reviewers\"} );\n"
+"end]]>"
#. Tag: para
#: Drools.xml:124
#, no-c-format
-msgid ""
-"You can find out more about Drools at <ulink url=\"http://www.drools.org\"></"
-"ulink>"
+msgid "You can find out more about Drools at <ulink url=\"http://www.drools.org\"></ulink>"
msgstr ""
#. 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."
+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 ""
#. 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"
+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 ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Feedback.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Feedback.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Feedback.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-08 14:24+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,12 +17,11 @@
#: Feedback.xml:6
#, no-c-format
msgid "Contribute to Seam"
-msgstr ""
+msgstr "Contribuire a Seam"
#. Tag: para
#: Feedback.xml:7
#, no-c-format
-msgid ""
-"Visit <ulink url=\"http://www.seamframework.org/Community/Contribute\"> "
-"SeamFramework.org </ulink> to find out how to contribute to Seam!"
-msgstr ""
+msgid "Visit <ulink url=\"http://www.seamframework.org/Community/Contribute\"> SeamFramework.org </ulink> to find out how to contribute to Seam!"
+msgstr "Visita <ulink url=\"http://www.seamframework.org/Community/Contribute\"> SeamFramework.org</ulink> per scoprire come contribuire a Seam!"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Hsearch.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -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-10 23:04+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,68 +17,48 @@
#: Hsearch.xml:5
#, no-c-format
msgid "Hibernate Search"
-msgstr ""
+msgstr "Hibernate Search"
#. Tag: title
#: Hsearch.xml:8
#, no-c-format
msgid "Introduction"
-msgstr ""
+msgstr "Introduzione"
#. Tag: para
#: Hsearch.xml:10
#, no-c-format
-msgid ""
-"Full text search engines like Apache Lucene™ are a very powerful technology "
-"that bring full text and efficient queries to applications. Hibernate "
-"Search, which uses Apache Lucene under the covers, indexes your domain model "
-"with the addition of a few annotations, takes care of the database / index "
-"synchronization and returns regular managed objects that are matched by full "
-"text queries. Keep in mind, thought, that there are mismatches that arise "
-"when dealing with an object domain model over a text index (keeping the "
-"index up to date, mismatch between the index structure and the domain model, "
-"and querying mismatch). But the benefits of speed and efficiency far "
-"outweigh these limitations."
+msgid "Full text search engines like Apache Lucene™ are a very powerful technology that bring full text and efficient queries to applications. Hibernate Search, which uses Apache Lucene under the covers, indexes your domain model with the addition of a few annotations, takes care of the database / index synchronization and returns regular managed objects that are matched by full text queries. Keep in mind, thought, that there are mismatches that arise when dealing with an object domain model over a text index (keeping the index up to date, mismatch between the index structure and the domain model, and querying mismatch). But the benefits of speed and efficiency far outweigh these limitations."
msgstr ""
#. Tag: para
#: Hsearch.xml:21
#, no-c-format
-msgid ""
-"Hibernate Search has been designed to integrates nicely and as naturally as "
-"possible with JPA and Hibernate. As a natural extension, JBoss Seam provides "
-"an Hibernate Search integration."
+msgid "Hibernate Search has been designed to integrates nicely and as naturally as possible with JPA and Hibernate. As a natural extension, JBoss Seam provides an Hibernate Search integration."
msgstr ""
#. Tag: para
#: Hsearch.xml:25
#, no-c-format
-msgid ""
-"Please refer to the <ulink url=\"http://www.hibernate.org/hib_docs/search/"
-"reference/en/html_single/\">Hibernate Search documentation</ulink> for "
-"information specific to the Hibernate Search project."
-msgstr ""
+msgid "Please refer to the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">Hibernate Search documentation</ulink> for information specific to the Hibernate Search project."
+msgstr "Si prega di riferirsi alla <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">documentazione Hibernate Search</ulink> per informazioni sul progetto Hibernate Search."
#. Tag: title
#: Hsearch.xml:33
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "Configurazione"
#. Tag: para
#: Hsearch.xml:35
#, no-c-format
-msgid ""
-"Hibernate Search is configured either in the <filename>META-INF/persistence."
-"xml</filename> or <filename>hibernate.cfg.xml</filename> file."
+msgid "Hibernate Search is configured either in the <filename>META-INF/persistence.xml</filename> or <filename>hibernate.cfg.xml</filename> file."
msgstr ""
#. Tag: para
#: Hsearch.xml:39
#, no-c-format
-msgid ""
-"Hibernate Search configuration has sensible defaults for most configuration "
-"parameters. Here is a minimal persistence unit configuration to get started."
+msgid "Hibernate Search configuration has sensible defaults for most configuration parameters. Here is a minimal persistence unit configuration to get started."
msgstr ""
#. Tag: programlisting
@@ -98,14 +78,23 @@
" </properties>\n"
"</persistence-unit>]]>"
msgstr ""
+"<![CDATA[<persistence-unit name=\"sample\">\n"
+" <jta-data-source>java:/DefaultDS</jta-data-source>\n"
+" <properties>\n"
+" [...]\n"
+" <!-- utilizza un file system basato su indice -->\n"
+" <property name=\"hibernate.search.default.directory_provider\" \n"
+" value=\"org.hibernate.search.store.FSDirectoryProvider\"/>\n"
+" <!-- directory dove gli indici verranno memorizzati -->\n"
+" <property name=\"hibernate.search.default.indexBase\" \n"
+" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n"
+" </properties>\n"
+"</persistence-unit>]]>"
#. Tag: para
#: Hsearch.xml:45
#, no-c-format
-msgid ""
-"If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded "
-"into JBoss AS 4.2.GA), you also need to configure the appropriate event "
-"listeners."
+msgid "If you plan to target Hibernate Annotations or EntityManager 3.2.x (embedded into JBoss AS 4.2.GA), you also need to configure the appropriate event listeners."
msgstr ""
#. Tag: programlisting
@@ -124,93 +113,94 @@
" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n"
"\n"
" <property name=\"hibernate.ejb.event.post-insert\" \n"
-" value=\"org.hibernate.search.event.FullTextIndexEventListener"
-"\"/>\n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
" <property name=\"hibernate.ejb.event.post-update\" \n"
-" value=\"org.hibernate.search.event.FullTextIndexEventListener"
-"\"/>\n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
" <property name=\"hibernate.ejb.event.post-delete\" \n"
-" value=\"org.hibernate.search.event.FullTextIndexEventListener"
-"\"/>\n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
"\n"
" </properties>\n"
"</persistence-unit>]]>"
msgstr ""
+"<![CDATA[<persistence-unit name=\"sample\">\n"
+" <jta-data-source>java:/DefaultDS</jta-data-source>\n"
+" <properties>\n"
+" [...]\n"
+" <!-- utilizza un file system basato su indice -->\n"
+" <property name=\"hibernate.search.default.directory_provider\" \n"
+" value=\"org.hibernate.search.store.FSDirectoryProvider\"/>\n"
+" <!-- directory dove gli indici verranno memorizzati -->\n"
+" <property name=\"hibernate.search.default.indexBase\" \n"
+" value=\"/Users/prod/apps/dvdstore/dvdindexes\"/>\n"
+"\n"
+" <property name=\"hibernate.ejb.event.post-insert\" \n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
+" <property name=\"hibernate.ejb.event.post-update\" \n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
+" <property name=\"hibernate.ejb.event.post-delete\" \n"
+" value=\"org.hibernate.search.event.FullTextIndexEventListener\"/>\n"
+"\n"
+" </properties>\n"
+"</persistence-unit>]]>"
#. Tag: para
#: Hsearch.xml:52
#, no-c-format
-msgid ""
-"This step is no longer necessary if Hibernate Annotation or EntityManager "
-"3.3.x are used."
-msgstr ""
+msgid "This step is no longer necessary if Hibernate Annotation or EntityManager 3.3.x are used."
+msgstr "Questo passo non è più necessario se vengono utilizzati Hibernate Annotation o EntityManager 3.3.x."
#. Tag: para
#: Hsearch.xml:56
#, no-c-format
-msgid ""
-"In addition to the configuration file, the following jars have to be "
-"deployed:"
+msgid "In addition to the configuration file, the following jars have to be deployed:"
msgstr ""
#. Tag: para
#: Hsearch.xml:61
#, no-c-format
msgid "hibernate-search.jar"
-msgstr ""
+msgstr "hibernate-search.jar"
#. Tag: para
#: Hsearch.xml:65
#, no-c-format
msgid "hibernate-commons-annotations.jar"
-msgstr ""
+msgstr "hibernate-commons-annotations.jar"
#. Tag: para
#: Hsearch.xml:69
#, no-c-format
msgid "lucene-core.jar"
-msgstr ""
+msgstr "lucene-core.jar"
#. Tag: para
#: Hsearch.xml:74
#, no-c-format
-msgid ""
-"If you deploy those in a EAR, don't forget to update <filename>application."
-"xml</filename>"
+msgid "If you deploy those in a EAR, don't forget to update <filename>application.xml</filename>"
msgstr ""
#. Tag: title
#: Hsearch.xml:80
#, no-c-format
msgid "Usage"
-msgstr ""
+msgstr "Utilizzo"
#. Tag: para
#: Hsearch.xml:82
#, no-c-format
-msgid ""
-"Hibernate Search uses annotations to map entities to a Lucene index, check "
-"the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/"
-"html_single/\">reference documentation</ulink> for more informations."
+msgid "Hibernate Search uses annotations to map entities to a Lucene index, check the <ulink url=\"http://www.hibernate.org/hib_docs/search/reference/en/html_single/\">reference documentation</ulink> for more informations."
msgstr ""
#. Tag: para
#: Hsearch.xml:87
#, no-c-format
-msgid ""
-"Hibernate Search is fully integrated with the API and semantic of JPA / "
-"Hibernate. Switching from a HQL or Criteria based query requires just a few "
-"lines of code. The main API the application interacts with is the "
-"<classname>FullTextSession</classname> API (subclass of Hibernate's "
-"<classname>Session</classname>)."
+msgid "Hibernate Search is fully integrated with the API and semantic of JPA / Hibernate. Switching from a HQL or Criteria based query requires just a few lines of code. The main API the application interacts with is the <classname>FullTextSession</classname> API (subclass of Hibernate's <classname>Session</classname>)."
msgstr ""
#. Tag: para
#: Hsearch.xml:93
#, no-c-format
-msgid ""
-"When Hibernate Search is present, JBoss Seam injects a "
-"<classname>FullTextSession</classname>."
+msgid "When Hibernate Search is present, JBoss Seam injects a <classname>FullTextSession</classname>."
msgstr ""
#. Tag: programlisting
@@ -225,8 +215,7 @@
"\n"
" public void search(String searchString) {\n"
" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
-" org.hibernate.Query query session.createFullTextQuery(luceneQuery, "
-"Product.class);\n"
+" org.hibernate.Query query session.createFullTextQuery(luceneQuery, Product.class);\n"
" searchResults = query\n"
" .setMaxResults(pageSize + 1)\n"
" .setFirstResult(pageSize * currentPage)\n"
@@ -235,20 +224,33 @@
" [...]\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"search\")\n"
+"public class FullTextSearchAction implements FullTextSearch, Serializable {\n"
+"\n"
+" @In FullTextSession session;\n"
+"\n"
+" public void search(String searchString) {\n"
+" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
+" org.hibernate.Query query session.createFullTextQuery(luceneQuery, Product.class);\n"
+" searchResults = query\n"
+" .setMaxResults(pageSize + 1)\n"
+" .setFirstResult(pageSize * currentPage)\n"
+" .list();\n"
+" }\n"
+" [...]\n"
+"}]]>"
#. Tag: para
#: Hsearch.xml:99
#, no-c-format
-msgid ""
-"<classname>FullTextSession</classname> extends <classname>org.hibernate."
-"Session</classname> so that it can be used as a regular Hibernate Session"
+msgid "<classname>FullTextSession</classname> extends <classname>org.hibernate.Session</classname> so that it can be used as a regular Hibernate Session"
msgstr ""
#. Tag: para
#: Hsearch.xml:104
#, no-c-format
-msgid ""
-"If the Java Persistence API is used, a smoother integration is proposed."
+msgid "If the Java Persistence API is used, a smoother integration is proposed."
msgstr ""
#. Tag: programlisting
@@ -263,8 +265,7 @@
"\n"
" public void search(String searchString) {\n"
" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
-" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, "
-"Product.class);\n"
+" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, Product.class);\n"
" searchResults = query\n"
" .setMaxResults(pageSize + 1)\n"
" .setFirstResult(pageSize * currentPage)\n"
@@ -273,29 +274,33 @@
" [...]\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"search\")\n"
+"public class FullTextSearchAction implements FullTextSearch, Serializable {\n"
+" \n"
+" @In FullTextEntityManager em;\n"
+"\n"
+" public void search(String searchString) {\n"
+" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
+" javax.persistence.Query query = em.createFullTextQuery(luceneQuery, Product.class);\n"
+" searchResults = query\n"
+" .setMaxResults(pageSize + 1)\n"
+" .setFirstResult(pageSize * currentPage)\n"
+" .getResultList();\n"
+" }\n"
+" [...]\n"
+"}]]>"
#. Tag: para
#: Hsearch.xml:109
#, no-c-format
-msgid ""
-"When Hibernate Search is present, a <classname>FulltextEntityManager</"
-"classname> is injected. <classname>FullTextEntityManager</classname> extends "
-"<classname>EntityManager</classname> with search specific methods, the same "
-"way <classname>FullTextSession</classname> extends <classname>Session</"
-"classname>."
+msgid "When Hibernate Search is present, a <classname>FulltextEntityManager</classname> is injected. <classname>FullTextEntityManager</classname> extends <classname>EntityManager</classname> with search specific methods, the same way <classname>FullTextSession</classname> extends <classname>Session</classname>."
msgstr ""
#. Tag: para
#: Hsearch.xml:116
#, no-c-format
-msgid ""
-"When an EJB 3.0 Session or Message Driven Bean injection is used (i.e. via "
-"the @PersistenceContext annotation), it is not possible to replace the "
-"<classname>EntityManager</classname> interface by the "
-"<classname>FullTextEntityManager</classname> interface in the declaration "
-"statement. However, the implementation injected will be a "
-"<classname>FullTextEntityManager</classname> implementation: downcasting is "
-"then possible."
+msgid "When an EJB 3.0 Session or Message Driven Bean injection is used (i.e. via the @PersistenceContext annotation), it is not possible to replace the <classname>EntityManager</classname> interface by the <classname>FullTextEntityManager</classname> interface in the declaration statement. However, the implementation injected will be a <classname>FullTextEntityManager</classname> implementation: downcasting is then possible."
msgstr ""
#. Tag: programlisting
@@ -311,8 +316,7 @@
" public void search(String searchString) {\n"
" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
" FullTextEntityManager ftEm = (FullTextEntityManager) em;\n"
-" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, "
-"Product.class);\n"
+" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, Product.class);\n"
" searchResults = query\n"
" .setMaxResults(pageSize + 1)\n"
" .setFirstResult(pageSize * currentPage)\n"
@@ -321,19 +325,33 @@
" [...]\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"search\")\n"
+"public class FullTextSearchAction implements FullTextSearch, Serializable {\n"
+" \n"
+" @PersistenceContext EntityManager em;\n"
+"\n"
+" public void search(String searchString) {\n"
+" org.apache.lucene.search.Query luceneQuery = getLuceneQuery();\n"
+" FullTextEntityManager ftEm = (FullTextEntityManager) em;\n"
+" javax.persistence.Query query = ftEm.createFullTextQuery(luceneQuery, Product.class);\n"
+" searchResults = query\n"
+" .setMaxResults(pageSize + 1)\n"
+" .setFirstResult(pageSize * currentPage)\n"
+" .getResultList();\n"
+" }\n"
+" [...]\n"
+"}]]>"
#. Tag: para
#: Hsearch.xml:129
#, no-c-format
-msgid ""
-"For people accustomed to Hibernate Search out of Seam, note that using "
-"<methodname>Search.createFullTextSession</methodname> is not necessary."
-msgstr ""
+msgid "For people accustomed to Hibernate Search out of Seam, note that using <methodname>Search.createFullTextSession</methodname> is not necessary."
+msgstr "Per persone abituate a Hibernate Seam fuori da Seam, notare che l'uso di <methodname>Search.createFullTextSession</methodname> non è necessario."
#. Tag: para
#: Hsearch.xml:134
#, no-c-format
-msgid ""
-"Check the DVDStore or the blog examples of the JBoss Seam distribution for a "
-"concrete use of Hibernate Search."
-msgstr ""
+msgid "Check the DVDStore or the blog examples of the JBoss Seam distribution for a concrete use of Hibernate Search."
+msgstr "Controlla gli esempi DVDStore o Blog della distribuzione di JBoss Seam per un uso pratico di Hibernate Search."
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Itext.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Itext.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Itext.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -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-10 23:07+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,10 +22,7 @@
#. Tag: para
#: Itext.xml:3
#, no-c-format
-msgid ""
-"Seam now includes a component set for generating documents using iText. The "
-"primary focus of Seam's iText document support is for the generation of PDF "
-"doucuments, but Seam also offers basic support for RTF document generation."
+msgid "Seam now includes a component set for generating documents using iText. The primary focus of Seam's iText document support is for the generation of PDF doucuments, but Seam also offers basic support for RTF document generation."
msgstr ""
#. Tag: title
@@ -37,33 +34,19 @@
#. Tag: para
#: Itext.xml:9
#, no-c-format
-msgid ""
-"iText support is provided by <literal>jboss-seam-pdf.jar</literal>. This JAR "
-"contains the iText JSF controls, which are used to construct views that can "
-"render to PDF, and the DocumentStore component, which serves the rendered "
-"documents to the user. To include PDF support in your application, included "
-"<literal>jboss-seam-pdf.jar</literal> in your <literal>WEB-INF/lib</literal> "
-"directory along with the iText JAR file. There is no further configuration "
-"needed to use Seam's iText supportfon."
+msgid "iText support is provided by <literal>jboss-seam-pdf.jar</literal>. This JAR contains the iText JSF controls, which are used to construct views that can render to PDF, and the DocumentStore component, which serves the rendered documents to the user. To include PDF support in your application, included <literal>jboss-seam-pdf.jar</literal> in your <literal>WEB-INF/lib</literal> directory along with the iText JAR file. There is no further configuration needed to use Seam's iText supportfon."
msgstr ""
#. Tag: para
#: Itext.xml:14
#, no-c-format
-msgid ""
-"The Seam iText 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 iText 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
#: Itext.xml:17
#, no-c-format
-msgid ""
-"The <literal>examples/itext</literal> project contains an example of the PDF "
-"support in action. It demonstrates proper deployment packaging, and it "
-"contains a number examples that demonstrate the key PDF generation features "
-"current supported."
+msgid "The <literal>examples/itext</literal> project contains an example of the PDF support in action. It demonstrates proper deployment packaging, and it contains a number examples that demonstrate the key PDF generation features current supported."
msgstr ""
#. Tag: title
@@ -79,11 +62,31 @@
msgstr ""
#. Tag: emphasis
-#: Itext.xml:42 Itext.xml:184 Itext.xml:256 Itext.xml:291 Itext.xml:324
-#: Itext.xml:374 Itext.xml:397 Itext.xml:528 Itext.xml:592 Itext.xml:654
-#: Itext.xml:694 Itext.xml:749 Itext.xml:852 Itext.xml:939 Itext.xml:1080
-#: Itext.xml:1308 Itext.xml:1504 Itext.xml:1700 Itext.xml:1843 Itext.xml:1914
-#: Itext.xml:1975 Itext.xml:2022 Itext.xml:2102 Itext.xml:2214 Itext.xml:2264
+#: Itext.xml:42
+#: Itext.xml:184
+#: Itext.xml:256
+#: Itext.xml:291
+#: Itext.xml:324
+#: Itext.xml:374
+#: Itext.xml:397
+#: Itext.xml:528
+#: Itext.xml:592
+#: Itext.xml:654
+#: Itext.xml:694
+#: Itext.xml:749
+#: Itext.xml:852
+#: Itext.xml:939
+#: Itext.xml:1080
+#: Itext.xml:1308
+#: Itext.xml:1504
+#: Itext.xml:1700
+#: Itext.xml:1843
+#: Itext.xml:1914
+#: Itext.xml:1975
+#: Itext.xml:2022
+#: Itext.xml:2102
+#: Itext.xml:2214
+#: Itext.xml:2264
#: Itext.xml:2324
#, no-c-format
msgid "Description"
@@ -92,21 +95,34 @@
#. Tag: para
#: Itext.xml:44
#, no-c-format
-msgid ""
-"Documents are generated by facelet XHTML files using tags in the "
-"<literal>http://jboss.com/products/seam/pdf</literal> namespace. Documents "
-"should always have the <literal>document</literal> tag at the root of the "
-"document. The <literal>document</literal> tag prepares Seam to generate a "
-"document into the DocumentStore and renders an HTML redirect to that stored "
-"content."
+msgid "Documents are generated by facelet XHTML files using tags in the <literal>http://jboss.com/products/seam/pdf</literal> namespace. Documents should always have the <literal>document</literal> tag at the root of the document. The <literal>document</literal> tag prepares Seam to generate a document into the DocumentStore and renders an HTML redirect to that stored content."
msgstr ""
#. Tag: emphasis
-#: Itext.xml:51 Itext.xml:190 Itext.xml:264 Itext.xml:298 Itext.xml:330
-#: Itext.xml:415 Itext.xml:535 Itext.xml:599 Itext.xml:704 Itext.xml:796
-#: Itext.xml:857 Itext.xml:944 Itext.xml:1085 Itext.xml:1312 Itext.xml:1508
-#: Itext.xml:1704 Itext.xml:1848 Itext.xml:1918 Itext.xml:1980 Itext.xml:2026
-#: Itext.xml:2107 Itext.xml:2219 Itext.xml:2269 Itext.xml:2329
+#: Itext.xml:51
+#: Itext.xml:190
+#: Itext.xml:264
+#: Itext.xml:298
+#: Itext.xml:330
+#: Itext.xml:415
+#: Itext.xml:535
+#: Itext.xml:599
+#: Itext.xml:704
+#: Itext.xml:796
+#: Itext.xml:857
+#: Itext.xml:944
+#: Itext.xml:1085
+#: Itext.xml:1312
+#: Itext.xml:1508
+#: Itext.xml:1704
+#: Itext.xml:1848
+#: Itext.xml:1918
+#: Itext.xml:1980
+#: Itext.xml:2026
+#: Itext.xml:2107
+#: Itext.xml:2219
+#: Itext.xml:2269
+#: Itext.xml:2329
#, no-c-format
msgid "Attributes"
msgstr ""
@@ -114,68 +130,43 @@
#. Tag: para
#: Itext.xml:56
#, no-c-format
-msgid ""
-"<literal>type</literal> — The type of the document to be produced. "
-"Valid values are <literal>PDF</literal>, <literal>RTF</literal> and "
-"<literal>HTML</literal> modes. Seam defaults to PDF generation, and many of "
-"the features only work correctly when generating PDF documents."
+msgid "<literal>type</literal> — The type of the document to be produced. Valid values are <literal>PDF</literal>, <literal>RTF</literal> and <literal>HTML</literal> modes. Seam defaults to PDF generation, and many of the features only work correctly when generating PDF documents."
msgstr ""
#. Tag: para
#: Itext.xml:65
#, no-c-format
-msgid ""
-"<literal>pageSize</literal> — The size of the page to be generate. The "
-"most commonly used values would be <literal>LETTER</literal> and "
-"<literal>A4</literal>. A full list of supported pages sizes can be found in "
-"<literal>com.lowagie.text.PageSize</literal> class. Alternatively, pageSize "
-"can provide the width and height of the page directly. The value \"612 792"
-"\", for example, is equivalent to the LETTER page size."
+msgid "<literal>pageSize</literal> — The size of the page to be generate. The most commonly used values would be <literal>LETTER</literal> and <literal>A4</literal>. A full list of supported pages sizes can be found in <literal>com.lowagie.text.PageSize</literal> class. Alternatively, pageSize can provide the width and height of the page directly. The value \"612 792\", for example, is equivalent to the LETTER page size."
msgstr ""
#. Tag: para
#: Itext.xml:74
#, no-c-format
-msgid ""
-"<literal>orientation</literal> — The orientation of the page. Valid "
-"values are <literal>portrait</literal> and <literal>landscape</literal>. In "
-"landscape mode, the height and width page size values are reversed."
+msgid "<literal>orientation</literal> — The orientation of the page. Valid values are <literal>portrait</literal> and <literal>landscape</literal>. In landscape mode, the height and width page size values are reversed."
msgstr ""
#. Tag: para
#: Itext.xml:83
#, no-c-format
-msgid ""
-"<literal>margins</literal> — The left, right, top and bottom margin "
-"values."
+msgid "<literal>margins</literal> — The left, right, top and bottom margin values."
msgstr ""
#. Tag: para
#: Itext.xml:88
#, no-c-format
-msgid ""
-"<literal>marginMirroring</literal> — Indicates that margin settings "
-"should be reversed an alternating pages."
+msgid "<literal>marginMirroring</literal> — Indicates that margin settings should be reversed an alternating pages."
msgstr ""
#. Tag: para
#: Itext.xml:94
#, no-c-format
-msgid ""
-"<literal>disposition</literal> — When generating PDFs in a web "
-"browser, this determines the HTTP <literal>Content-Disposition</literal> of "
-"the document. Valid values are <literal>inline</literal>, which indicates "
-"the document should be displayed in the browser window if possible, and "
-"<literal>attachment</literal>, which indicates that the document should be "
-"treated as a download. The default value is <literal>inline</literal>."
+msgid "<literal>disposition</literal> — When generating PDFs in a web browser, this determines the HTTP <literal>Content-Disposition</literal> of the document. Valid values are <literal>inline</literal>, which indicates the document should be displayed in the browser window if possible, and <literal>attachment</literal>, which indicates that the document should be treated as a download. The default value is <literal>inline</literal>."
msgstr ""
#. Tag: para
#: Itext.xml:102
#, no-c-format
-msgid ""
-"<literal>fileName</literal> — For attachments, this value overrides "
-"the downloaded file name."
+msgid "<literal>fileName</literal> — For attachments, this value overrides the downloaded file name."
msgstr ""
#. Tag: emphasis
@@ -215,11 +206,30 @@
msgstr ""
#. Tag: emphasis
-#: Itext.xml:143 Itext.xml:242 Itext.xml:276 Itext.xml:309 Itext.xml:359
-#: Itext.xml:382 Itext.xml:510 Itext.xml:558 Itext.xml:640 Itext.xml:660
-#: Itext.xml:733 Itext.xml:838 Itext.xml:899 Itext.xml:1065 Itext.xml:1241
-#: Itext.xml:1490 Itext.xml:1686 Itext.xml:1829 Itext.xml:1900 Itext.xml:1958
-#: Itext.xml:2008 Itext.xml:2068 Itext.xml:2182 Itext.xml:2349
+#: Itext.xml:143
+#: Itext.xml:242
+#: Itext.xml:276
+#: Itext.xml:309
+#: Itext.xml:359
+#: Itext.xml:382
+#: Itext.xml:510
+#: Itext.xml:558
+#: Itext.xml:640
+#: Itext.xml:660
+#: Itext.xml:733
+#: Itext.xml:838
+#: Itext.xml:899
+#: Itext.xml:1065
+#: Itext.xml:1241
+#: Itext.xml:1490
+#: Itext.xml:1686
+#: Itext.xml:1829
+#: Itext.xml:1900
+#: Itext.xml:1958
+#: Itext.xml:2008
+#: Itext.xml:2068
+#: Itext.xml:2182
+#: Itext.xml:2349
#, no-c-format
msgid "Usage"
msgstr ""
@@ -228,10 +238,8 @@
#: Itext.xml:145
#, no-c-format
msgid ""
-"<![CDATA[<p:document xmlns:p=\"http://jboss.com/products/seam/pdf"
-"\"> \n"
-" The document goes "
-"here. \n"
+"<![CDATA[<p:document xmlns:p=\"http://jboss.com/products/seam/pdf\"> \n"
+" The document goes here. \n"
"</p:document>]]>"
msgstr ""
@@ -244,14 +252,7 @@
#. Tag: para
#: Itext.xml:160
#, no-c-format
-msgid ""
-"Useful documents will need to contain more than just text; however, the "
-"standard UI components are geared towards HTML generation and are not useful "
-"for generating PDF content. Instead, Seam provides a special UI components "
-"for generating suitable PDF content. Tags like <literal><p:image></"
-"literal> and <literal><p:paragraph></literal> are the basic "
-"foundations of simple documents. Tags like <literal><p:font></literal> "
-"provide style information to all the content surrounging them."
+msgid "Useful documents will need to contain more than just text; however, the standard UI components are geared towards HTML generation and are not useful for generating PDF content. Instead, Seam provides a special UI components for generating suitable PDF content. Tags like <literal><p:image></literal> and <literal><p:paragraph></literal> are the basic foundations of simple documents. Tags like <literal><p:font></literal> provide style information to all the content surrounging them."
msgstr ""
#. Tag: literal
@@ -263,9 +264,7 @@
#. Tag: para
#: Itext.xml:186
#, no-c-format
-msgid ""
-"Most uses of text should be sectioned into paragraphs so that text fragments "
-"can be flowed, formatted and styled in logical groups."
+msgid "Most uses of text should be sectioned into paragraphs so that text fragments can be flowed, formatted and styled in logical groups."
msgstr ""
#. Tag: literal
@@ -275,53 +274,59 @@
msgstr ""
#. Tag: literal
-#: Itext.xml:201 Itext.xml:1160
+#: Itext.xml:201
+#: Itext.xml:1160
#, no-c-format
msgid "extraParagraphSpace"
msgstr ""
#. Tag: literal
-#: Itext.xml:206 Itext.xml:1132
+#: Itext.xml:206
+#: Itext.xml:1132
#, no-c-format
msgid "leading"
msgstr ""
#. Tag: literal
-#: Itext.xml:211 Itext.xml:1140
+#: Itext.xml:211
+#: Itext.xml:1140
#, no-c-format
msgid "multipliedLeading"
msgstr ""
#. Tag: para
-#: Itext.xml:215 Itext.xml:462 Itext.xml:1025
+#: Itext.xml:215
+#: Itext.xml:462
+#: Itext.xml:1025
#, no-c-format
-msgid ""
-"<literal>spacingBefore</literal> — The blank space to be inserted "
-"before the element."
+msgid "<literal>spacingBefore</literal> — The blank space to be inserted before the element."
msgstr ""
#. Tag: para
-#: Itext.xml:220 Itext.xml:467 Itext.xml:1031
+#: Itext.xml:220
+#: Itext.xml:467
+#: Itext.xml:1031
#, no-c-format
-msgid ""
-"<literal>spacingAfter</literal> — The blank space to be inserted after "
-"the element."
+msgid "<literal>spacingAfter</literal> — The blank space to be inserted after the element."
msgstr ""
#. Tag: literal
-#: Itext.xml:226 Itext.xml:453
+#: Itext.xml:226
+#: Itext.xml:453
#, no-c-format
msgid "indentationLeft"
msgstr ""
#. Tag: literal
-#: Itext.xml:231 Itext.xml:458
+#: Itext.xml:231
+#: Itext.xml:458
#, no-c-format
msgid "indentationRight"
msgstr ""
#. Tag: literal
-#: Itext.xml:236 Itext.xml:1059
+#: Itext.xml:236
+#: Itext.xml:1059
#, no-c-format
msgid "keepTogether"
msgstr ""
@@ -344,18 +349,13 @@
#. Tag: para
#: Itext.xml:259
#, no-c-format
-msgid ""
-"The <literal>text</literal> tag allows text fragments to be produced from "
-"application data using normal JSF converter mechanisms. It is very similar "
-"to the <literal>outputText</literal> tag used when rendering HTML documents."
+msgid "The <literal>text</literal> tag allows text fragments to be produced from application data using normal JSF converter mechanisms. It is very similar to the <literal>outputText</literal> tag used when rendering HTML documents."
msgstr ""
#. Tag: para
#: Itext.xml:270
#, no-c-format
-msgid ""
-"<literal>value</literal> — The value to be displayed. This will "
-"typically be a value binding expression."
+msgid "<literal>value</literal> — The value to be displayed. This will typically be a value binding expression."
msgstr ""
#. Tag: programlisting
@@ -403,8 +403,7 @@
"</p:html>\n"
"\n"
"<p:html>\n"
-" <s:formattedText value=\"*This* is |Seam Text| as HTML. It's very^cool^."
-"\" />\n"
+" <s:formattedText value=\"*This* is |Seam Text| as HTML. It's very^cool^.\" />\n"
"</p:html> \n"
"]]>"
msgstr ""
@@ -418,18 +417,13 @@
#. Tag: para
#: Itext.xml:327
#, no-c-format
-msgid ""
-"The font tag defines the default font to be used for all text inside of it."
+msgid "The font tag defines the default font to be used for all text inside of it."
msgstr ""
#. Tag: para
#: Itext.xml:336
#, no-c-format
-msgid ""
-"<literal>name</literal> — The font name, for example: "
-"<literal>COURIER</literal>, <literal>HELVETICA</literal>, <literal>TIMES-"
-"ROMAN</literal>, <literal>SYMBOL</literal> or <literal>ZAPFDINGBATS</"
-"literal>."
+msgid "<literal>name</literal> — The font name, for example: <literal>COURIER</literal>, <literal>HELVETICA</literal>, <literal>TIMES-ROMAN</literal>, <literal>SYMBOL</literal> or <literal>ZAPFDINGBATS</literal>."
msgstr ""
#. Tag: para
@@ -441,11 +435,7 @@
#. Tag: para
#: Itext.xml:347
#, no-c-format
-msgid ""
-"<literal>style</literal> — The font styles. Any combination of : "
-"<literal>NORMAL</literal>, <literal>BOLD</literal>, <literal>ITALIC</"
-"literal>, <literal>OBLIQUE</literal>, <literal>UNDERLINE</literal>, "
-"<literal>LINE-THROUGH</literal>"
+msgid "<literal>style</literal> — The font styles. Any combination of : <literal>NORMAL</literal>, <literal>BOLD</literal>, <literal>ITALIC</literal>, <literal>OBLIQUE</literal>, <literal>UNDERLINE</literal>, <literal>LINE-THROUGH</literal>"
msgstr ""
#. Tag: para
@@ -490,34 +480,25 @@
#. Tag: para
#: Itext.xml:401
#, no-c-format
-msgid ""
-"<literal>p:image</literal> inserts an image into the document. Images can be "
-"be loaded from the classpath or from the web application context using the "
-"<literal>value</literal> attribute."
+msgid "<literal>p:image</literal> inserts an image into the document. Images can be be loaded from the classpath or from the web application context using the <literal>value</literal> attribute."
msgstr ""
#. Tag: para
#: Itext.xml:407
#, no-c-format
-msgid ""
-"Resources can also be dynamically generated by application code. The "
-"<literal>imageData</literal> attribute can specify a value binding "
-"expression whose value is a <literal>java.awt.Image</literal> object."
+msgid "Resources can also be dynamically generated by application code. The <literal>imageData</literal> attribute can specify a value binding expression whose value is a <literal>java.awt.Image</literal> object."
msgstr ""
#. Tag: para
#: Itext.xml:420
#, no-c-format
-msgid ""
-"<literal>value</literal> — A resource name or a method expression "
-"binding to an application-generated image."
+msgid "<literal>value</literal> — A resource name or a method expression binding to an application-generated image."
msgstr ""
#. Tag: para
#: Itext.xml:426
#, no-c-format
-msgid ""
-"<literal>rotation</literal> — The rotation of the image in degrees."
+msgid "<literal>rotation</literal> — The rotation of the image in degrees."
msgstr ""
#. Tag: para
@@ -535,16 +516,13 @@
#. Tag: para
#: Itext.xml:440
#, no-c-format
-msgid ""
-"<literal>alignment</literal>— The alignment of the image. (see <xref "
-"linkend=\"itext.alignment\"/> for possible values)"
+msgid "<literal>alignment</literal>— The alignment of the image. (see <xref linkend=\"itext.alignment\"/> for possible values)"
msgstr ""
#. Tag: para
#: Itext.xml:447
#, no-c-format
-msgid ""
-"<literal>alt</literal> — Alternative text representation for the image."
+msgid "<literal>alt</literal> — Alternative text representation for the image."
msgstr ""
#. Tag: literal
@@ -568,10 +546,7 @@
#. Tag: para
#: Itext.xml:491
#, no-c-format
-msgid ""
-"<literal>scalePercent</literal> — The scaling factor (as a percentage) "
-"to use for the image. This can be expressed as a single percentage value or "
-"as two percentage values representing separate x and y scaling percentages."
+msgid "<literal>scalePercent</literal> — The scaling factor (as a percentage) to use for the image. This can be expressed as a single percentage value or as two percentage values representing separate x and y scaling percentages."
msgstr ""
#. Tag: literal
@@ -607,40 +582,29 @@
#. Tag: para
#: Itext.xml:530
#, no-c-format
-msgid ""
-"<literal>p:anchor</literal> defines clickable links from a document. It "
-"supports the following attributes:"
+msgid "<literal>p:anchor</literal> defines clickable links from a document. It supports the following attributes:"
msgstr ""
#. Tag: para
#: Itext.xml:541
#, no-c-format
-msgid ""
-"<literal>name</literal> — The name of an in-document anchor "
-"destination."
+msgid "<literal>name</literal> — The name of an in-document anchor destination."
msgstr ""
#. Tag: para
#: Itext.xml:548
#, no-c-format
-msgid ""
-"<literal>reference</literal> — The destination the link refers to. "
-"Links to other points in the document should begin with a \"#\". For "
-"example, \"#link1\" to refer to an anchor postion with a <literal>name</"
-"literal> of <literal>link1</literal>. Links may also be a full URL to point "
-"to a resource outside of the document."
+msgid "<literal>reference</literal> — The destination the link refers to. Links to other points in the document should begin with a \"#\". For example, \"#link1\" to refer to an anchor postion with a <literal>name</literal> of <literal>link1</literal>. Links may also be a full URL to point to a resource outside of the document."
msgstr ""
#. Tag: programlisting
#: Itext.xml:560
#, no-c-format
msgid ""
-"<![CDATA[<p:listItem><p:anchor reference=\"#reason1\">Reason 1</p:anchor></p:"
-"listItem> \n"
+"<![CDATA[<p:listItem><p:anchor reference=\"#reason1\">Reason 1</p:anchor></p:listItem> \n"
"...\n"
"<p:paragraph>\n"
-" <p:anchor name=\"reason1\">It's the quickest way to get \"rich\"</p:"
-"anchor> \n"
+" <p:anchor name=\"reason1\">It's the quickest way to get \"rich\"</p:anchor> \n"
" ... \n"
"</p:paragraph>]]>"
msgstr ""
@@ -652,7 +616,8 @@
msgstr ""
#. Tag: literal
-#: Itext.xml:584 Itext.xml:744
+#: Itext.xml:584
+#: Itext.xml:744
#, no-c-format
msgid "<p:header>"
msgstr ""
@@ -666,48 +631,33 @@
#. Tag: para
#: Itext.xml:594
#, no-c-format
-msgid ""
-"The <literal>p:header</literal> and <literal>p:footer</literal> components "
-"provide the ability to place header and footer text on each page of a "
-"generated document. Header and footer declarations should appear at the "
-"beginning of a document."
+msgid "The <literal>p:header</literal> and <literal>p:footer</literal> components provide the ability to place header and footer text on each page of a generated document. Header and footer declarations should appear at the beginning of a document."
msgstr ""
#. Tag: para
-#: Itext.xml:607 Itext.xml:712 Itext.xml:865
+#: Itext.xml:607
+#: Itext.xml:712
+#: Itext.xml:865
#, no-c-format
-msgid ""
-"<literal>alignment</literal> — The alignment of the header/footer box "
-"section. (see <xref linkend=\"itext.alignment\"/> for alignment values)"
+msgid "<literal>alignment</literal> — The alignment of the header/footer box section. (see <xref linkend=\"itext.alignment\"/> for alignment values)"
msgstr ""
#. Tag: para
#: Itext.xml:614
#, no-c-format
-msgid ""
-"<literal>backgroundColor</literal> — The background color of the "
-"header/footer box. (see <xref linkend=\"itext.colors\"/> for color values)"
+msgid "<literal>backgroundColor</literal> — The background color of the header/footer box. (see <xref linkend=\"itext.colors\"/> for color values)"
msgstr ""
#. Tag: para
#: Itext.xml:623
#, no-c-format
-msgid ""
-"<literal>borderColor</literal> — The border color of the header/footer "
-"box. Individual border sides can be set using <literal>borderColorLeft</"
-"literal>, <literal>borderColorRight</literal>, <literal>borderColorTop</"
-"literal> and <literal>borderColorBottom</literal>.(see <xref linkend=\"itext."
-"colors\"/> for color values)"
+msgid "<literal>borderColor</literal> — The border color of the header/footer box. Individual border sides can be set using <literal>borderColorLeft</literal>, <literal>borderColorRight</literal>, <literal>borderColorTop</literal> and <literal>borderColorBottom</literal>.(see <xref linkend=\"itext.colors\"/> for color values)"
msgstr ""
#. Tag: para
#: Itext.xml:631
#, no-c-format
-msgid ""
-"<literal>borderWidth</literal> — The width of the border. Inidvidual "
-"border sides can be specified using <literal>borderWidthLeft</literal>, "
-"<literal>borderWidthRight</literal>, <literal>borderWidthTop</literal> and "
-"<literal>borderWidthBottom</literal>."
+msgid "<literal>borderWidth</literal> — The width of the border. Inidvidual border sides can be specified using <literal>borderWidthLeft</literal>, <literal>borderWidthRight</literal>, <literal>borderWidthTop</literal> and <literal>borderWidthBottom</literal>."
msgstr ""
#. Tag: programlisting
@@ -733,10 +683,7 @@
#. Tag: para
#: Itext.xml:656
#, no-c-format
-msgid ""
-"The current page number can be placed inside of a header or footer using the "
-"<literal>p:pageNumber</literal> tag. The page number tag can only be used in "
-"the context of a header or footer and can only be used once."
+msgid "The current page number can be placed inside of a header or footer using the <literal>p:pageNumber</literal> tag. The page number tag can only be used in the context of a header or footer and can only be used once."
msgstr ""
#. Tag: programlisting
@@ -770,32 +717,19 @@
#. Tag: para
#: Itext.xml:697
#, no-c-format
-msgid ""
-"If the generated document follows a book/article structure, the <literal>p:"
-"chapter</literal> and <literal>p:section</literal> tags can be used to "
-"provide the necessary structure. Sections can only be used inside of "
-"chapters, but they may be nested arbitrarily deep. Most PDF viewers provide "
-"easy navigation between chapters and sections in a document."
+msgid "If the generated document follows a book/article structure, the <literal>p:chapter</literal> and <literal>p:section</literal> tags can be used to provide the necessary structure. Sections can only be used inside of chapters, but they may be nested arbitrarily deep. Most PDF viewers provide easy navigation between chapters and sections in a document."
msgstr ""
#. Tag: para
#: Itext.xml:719
#, no-c-format
-msgid ""
-"<literal>number</literal> — The chapter number. Every chapter should "
-"be assigned a chapter number."
+msgid "<literal>number</literal> — The chapter number. Every chapter should be assigned a chapter number."
msgstr ""
#. Tag: para
#: Itext.xml:724
#, no-c-format
-msgid ""
-"<literal>numberDepth</literal> — The depth of numbering for section. "
-"All sections are numbered relative to their surrounding chapter/sections. "
-"The fourth section of of the first section of chapter three would be section "
-"3.1.4, if displayed at the default number depth of three. To omit the "
-"chapter number, a number depth of 2 should be used. In that case, the "
-"section number would be displayed as 1.4."
+msgid "<literal>numberDepth</literal> — The depth of numbering for section. All sections are numbered relative to their surrounding chapter/sections. The fourth section of of the first section of chapter three would be section 3.1.4, if displayed at the default number depth of three. To omit the chapter number, a number depth of 2 should be used. In that case, the section number would be displayed as 1.4."
msgstr ""
#. Tag: programlisting
@@ -821,10 +755,7 @@
#. Tag: para
#: Itext.xml:752
#, no-c-format
-msgid ""
-"Any chapter or section can contain a <literal>p:title</literal>. The title "
-"will be displayed next to the chapter/section number. The body of the title "
-"may contain raw text or may be a <literal>p:paragraph</literal>."
+msgid "Any chapter or section can contain a <literal>p:title</literal>. The title will be displayed next to the chapter/section number. The body of the title may contain raw text or may be a <literal>p:paragraph</literal>."
msgstr ""
#. Tag: title
@@ -836,12 +767,7 @@
#. Tag: para
#: Itext.xml:767
#, no-c-format
-msgid ""
-"List structures can be displayed using the <literal>p:list</literal> and "
-"<literal>p:listItem</literal> tags. Lists may contain arbitrarily-nested "
-"sublists. List items may not be used outside of a list. he following "
-"document uses the <literal>ui:repeat</literal> tag to to display a list of "
-"values retrieved from a Seam component."
+msgid "List structures can be displayed using the <literal>p:list</literal> and <literal>p:listItem</literal> tags. Lists may contain arbitrarily-nested sublists. List items may not be used outside of a list. he following document uses the <literal>ui:repeat</literal> tag to to display a list of values retrieved from a Seam component."
msgstr ""
#. Tag: programlisting
@@ -868,20 +794,13 @@
#. Tag: para
#: Itext.xml:802
#, no-c-format
-msgid ""
-"<literal>style</literal> — The ordering/bulleting style of list. One "
-"of: <literal>NUMBERED</literal>, <literal>LETTERED</literal>, "
-"<literal>GREEK</literal>, <literal>ROMAN</literal>, <literal>ZAPFDINGBATS</"
-"literal>, <literal>ZAPFDINGBATS_NUMBER</literal>. If no style is given, the "
-"list items are bulleted."
+msgid "<literal>style</literal> — The ordering/bulleting style of list. One of: <literal>NUMBERED</literal>, <literal>LETTERED</literal>, <literal>GREEK</literal>, <literal>ROMAN</literal>, <literal>ZAPFDINGBATS</literal>, <literal>ZAPFDINGBATS_NUMBER</literal>. If no style is given, the list items are bulleted."
msgstr ""
#. Tag: para
#: Itext.xml:809
#, no-c-format
-msgid ""
-"<literal>listSymbol</literal> — For bulleted lists, specifies the "
-"bullet symbol."
+msgid "<literal>listSymbol</literal> — For bulleted lists, specifies the bullet symbol."
msgstr ""
#. Tag: para
@@ -893,25 +812,19 @@
#. Tag: para
#: Itext.xml:820
#, no-c-format
-msgid ""
-"<literal>lowerCase</literal> — For list styles using letters, "
-"indicates whether the letters should be lower case."
+msgid "<literal>lowerCase</literal> — For list styles using letters, indicates whether the letters should be lower case."
msgstr ""
#. Tag: para
#: Itext.xml:826
#, no-c-format
-msgid ""
-"<literal>charNumber</literal> — For ZAPFDINGBATS, indicates the "
-"character code of the bullet character."
+msgid "<literal>charNumber</literal> — For ZAPFDINGBATS, indicates the character code of the bullet character."
msgstr ""
#. Tag: para
#: Itext.xml:832
#, no-c-format
-msgid ""
-"<literal>numberType</literal> — For ZAPFDINGBATS_NUMBER, indicates the "
-"numbering style."
+msgid "<literal>numberType</literal> — For ZAPFDINGBATS_NUMBER, indicates the numbering style."
msgstr ""
#. Tag: programlisting
@@ -940,9 +853,7 @@
#. Tag: para
#: Itext.xml:872
#, no-c-format
-msgid ""
-"<literal>alignment</literal> — The alignment of the list item. (See "
-"<xref linkend=\"itext.alignment\"/> for possible values)"
+msgid "<literal>alignment</literal> — The alignment of the list item. (See <xref linkend=\"itext.alignment\"/> for possible values)"
msgstr ""
#. Tag: para
@@ -954,23 +865,20 @@
#. Tag: para
#: Itext.xml:885
#, no-c-format
-msgid ""
-"<literal>indentationRight</literal> — The right indentation amount."
+msgid "<literal>indentationRight</literal> — The right indentation amount."
msgstr ""
#. Tag: para
#: Itext.xml:892
#, no-c-format
-msgid ""
-"<literal>listSymbol</literal> — Overrides the default list symbol for "
-"this list item."
+msgid "<literal>listSymbol</literal> — Overrides the default list symbol for this list item."
msgstr ""
#. Tag: programlisting
#: Itext.xml:901
#, no-c-format
msgid "<programlisting>...</programlisting>"
-msgstr ""
+msgstr "<programlisting>...</programlisting>"
#. Tag: title
#: Itext.xml:915
@@ -981,20 +889,14 @@
#. Tag: para
#: Itext.xml:917
#, no-c-format
-msgid ""
-"Table structures can be created using the <literal>p:table</literal> and "
-"<literal>p:cell</literal> tags. Unlike many table structures, there is no "
-"explicit row declaration. If a table has 3 columns, then every 3 cells will "
-"automatically form a row. Header and footer rows can be declared, and the "
-"headers and footers will be repeated in the event a table structure spans "
-"multiple pages."
+msgid "Table structures can be created using the <literal>p:table</literal> and <literal>p:cell</literal> tags. Unlike many table structures, there is no explicit row declaration. If a table has 3 columns, then every 3 cells will automatically form a row. Header and footer rows can be declared, and the headers and footers will be repeated in the event a table structure spans multiple pages."
msgstr ""
#. Tag: literal
#: Itext.xml:934
#, no-c-format
msgid "<p:table>"
-msgstr ""
+msgstr "<p:table>"
#. Tag: para
#: Itext.xml:941
@@ -1005,98 +907,81 @@
#. Tag: para
#: Itext.xml:951
#, no-c-format
-msgid ""
-"<literal>columns</literal> — The number of columns (cells) that make "
-"up a table row."
+msgid "<literal>columns</literal> — The number of columns (cells) that make up a table row."
msgstr ""
#. Tag: para
#: Itext.xml:958
#, no-c-format
-msgid ""
-"<literal>widths</literal> — The relative widths of each column. There "
-"should be one value for each column. For example: widths=\"2 1 1\" would "
-"indicate that there are 3 columns and the first column should be twice the "
-"size of the second and third column."
+msgid "<literal>widths</literal> — The relative widths of each column. There should be one value for each column. For example: widths=\"2 1 1\" would indicate that there are 3 columns and the first column should be twice the size of the second and third column."
msgstr ""
#. Tag: para
#: Itext.xml:967
#, no-c-format
-msgid ""
-"<literal>headerRows</literal> — The initial number of rows which are "
-"considered to be headers or footer rows and should be repeated if the table "
-"spans multiple pages."
+msgid "<literal>headerRows</literal> — The initial number of rows which are considered to be headers or footer rows and should be repeated if the table spans multiple pages."
msgstr ""
#. Tag: para
#: Itext.xml:975
#, no-c-format
-msgid ""
-"<literal>footerRows</literal> — The number of rows that are considered "
-"to be footer rows. This value is subtracted from the <literal>headerRows</"
-"literal> value. If document has 2 rows which make up the header and one row "
-"that makes up the footer, <literal>headerRows</literal> should be set to 3 "
-"and <literal>footerRows</literal> should be set to 1"
+msgid "<literal>footerRows</literal> — The number of rows that are considered to be footer rows. This value is subtracted from the <literal>headerRows</literal> value. If document has 2 rows which make up the header and one row that makes up the footer, <literal>headerRows</literal> should be set to 3 and <literal>footerRows</literal> should be set to 1"
msgstr ""
#. Tag: para
#: Itext.xml:986
#, no-c-format
-msgid ""
-"<literal>widthPercentage</literal> — The percentage of the page width "
-"that the table spans."
+msgid "<literal>widthPercentage</literal> — The percentage of the page width that the table spans."
msgstr ""
#. Tag: para
#: Itext.xml:991
#, no-c-format
-msgid ""
-"<literal>horizontalAlignment</literal> — The horizontal alignment of "
-"the table. (See <xref linkend=\"itext.alignment\"/> for possible values)"
+msgid "<literal>horizontalAlignment</literal> — The horizontal alignment of the table. (See <xref linkend=\"itext.alignment\"/> for possible values)"
msgstr ""
#. Tag: literal
#: Itext.xml:998
#, no-c-format
msgid "skipFirstHeader"
-msgstr ""
+msgstr "skipFirstHeader"
#. Tag: literal
-#: Itext.xml:1004 Itext.xml:1208
+#: Itext.xml:1004
+#: Itext.xml:1208
#, no-c-format
msgid "runDirection"
-msgstr ""
+msgstr "runDirection"
#. Tag: literal
#: Itext.xml:1010
#, no-c-format
msgid "lockedWidth"
-msgstr ""
+msgstr "lockedWidth"
#. Tag: literal
#: Itext.xml:1018
#, no-c-format
msgid "splitRows"
-msgstr ""
+msgstr "splitRows"
#. Tag: literal
#: Itext.xml:1036
#, no-c-format
msgid "extendLastRow"
-msgstr ""
+msgstr "extendLastRow"
#. Tag: literal
#: Itext.xml:1044
#, no-c-format
msgid "headersInEvent"
-msgstr ""
+msgstr "headersInEvent"
#. Tag: literal
#: Itext.xml:1051
#, no-c-format
msgid "splitLate"
-msgstr ""
+msgstr "splitLate"
#. Tag: programlisting
#: Itext.xml:1067
@@ -1113,12 +998,22 @@
" </ui:repeat>\n"
"</p:table>]]>"
msgstr ""
+"<![CDATA[<p:table columns=\"3\" headerRows=\"1\">\n"
+" <p:cell>name</p:cell>\n"
+" <p:cell>owner</p:cell>\n"
+" <p:cell>size</p:cell>\n"
+" <ui:repeat value=\"#{documents}\" var=\"doc\">\n"
+" <p:cell>#{doc.name}</p:cell>\n"
+" <p:cell>#{doc.user.name}</p:cell>\n"
+" <p:cell>#{doc.size}</p:cell>\n"
+" </ui:repeat>\n"
+"</p:table>]]>"
#. Tag: literal
#: Itext.xml:1075
#, no-c-format
msgid "<p:cell>"
-msgstr ""
+msgstr "<p:cell>"
#. Tag: para
#: Itext.xml:1082
@@ -1129,120 +1024,110 @@
#. Tag: para
#: Itext.xml:1092
#, no-c-format
-msgid ""
-"<literal>colspan</literal> — Cells can span more than one column by "
-"declaring a <literal>colspan</literal> greater than 1. Tables do not have "
-"the ability to span across multiple rows."
+msgid "<literal>colspan</literal> — Cells can span more than one column by declaring a <literal>colspan</literal> greater than 1. Tables do not have the ability to span across multiple rows."
msgstr ""
#. Tag: para
#: Itext.xml:1101
#, no-c-format
-msgid ""
-"<literal>horizontalAlignment</literal> — The horizontal alignment of "
-"the cell. (see <xref linkend=\"itext.alignment\"/> for possible values)"
+msgid "<literal>horizontalAlignment</literal> — The horizontal alignment of the cell. (see <xref linkend=\"itext.alignment\"/> for possible values)"
msgstr ""
#. Tag: para
#: Itext.xml:1109
#, no-c-format
-msgid ""
-"<literal>verticalAlignment</literal> — The vertical alignment of the "
-"cell. (see <xref linkend=\"itext.alignment\"/> for possible values)"
+msgid "<literal>verticalAlignment</literal> — The vertical alignment of the cell. (see <xref linkend=\"itext.alignment\"/> for possible values)"
msgstr ""
#. Tag: para
#: Itext.xml:1116
#, no-c-format
-msgid ""
-"<literal>padding</literal> — Padding on a given side can also be "
-"specified using <literal>paddingLeft</literal>, <literal>paddingRight</"
-"literal>, <literal>paddingTop</literal> and <literal>paddingBottom</literal>."
+msgid "<literal>padding</literal> — Padding on a given side can also be specified using <literal>paddingLeft</literal>, <literal>paddingRight</literal>, <literal>paddingTop</literal> and <literal>paddingBottom</literal>."
msgstr ""
#. Tag: literal
#: Itext.xml:1126
#, no-c-format
msgid "useBorderPadding"
-msgstr ""
+msgstr "useBorderPadding"
#. Tag: literal
#: Itext.xml:1148
#, no-c-format
msgid "indent"
-msgstr ""
+msgstr "indent"
#. Tag: literal
#: Itext.xml:1154
#, no-c-format
msgid "verticalAlignment"
-msgstr ""
+msgstr "verticalAlignment"
#. Tag: literal
#: Itext.xml:1168
#, no-c-format
msgid "fixedHeight"
-msgstr ""
+msgstr "fixedHeight"
#. Tag: literal
#: Itext.xml:1175
#, no-c-format
msgid "noWrap"
-msgstr ""
+msgstr "noWrap"
#. Tag: literal
#: Itext.xml:1181
#, no-c-format
msgid "minimumHeight"
-msgstr ""
+msgstr "minimumHeight"
#. Tag: literal
#: Itext.xml:1188
#, no-c-format
msgid "followingIndent"
-msgstr ""
+msgstr "followingIndent"
#. Tag: literal
#: Itext.xml:1196
#, no-c-format
msgid "rightIndent"
-msgstr ""
+msgstr "rightIndent"
#. Tag: literal
#: Itext.xml:1202
#, no-c-format
msgid "spaceCharRatio"
-msgstr ""
+msgstr "spaceCharRatio"
#. Tag: literal
#: Itext.xml:1214
#, no-c-format
msgid "arabicOptions"
-msgstr ""
+msgstr "arabicOptions"
#. Tag: literal
#: Itext.xml:1221
#, no-c-format
msgid "useAscender"
-msgstr ""
+msgstr "useAscender"
#. Tag: literal
#: Itext.xml:1229
#, no-c-format
msgid "grayFill"
-msgstr ""
+msgstr "grayFill"
#. Tag: literal
#: Itext.xml:1235
#, no-c-format
msgid "rotation"
-msgstr ""
+msgstr "rotation"
#. Tag: programlisting
#: Itext.xml:1243
#, no-c-format
msgid "<![CDATA[<p:cell>...</p:cell>]]>"
-msgstr ""
+msgstr "<![CDATA[<p:cell>...</p:cell>]]>"
#. Tag: title
#: Itext.xml:1255
@@ -1253,9 +1138,7 @@
#. Tag: para
#: Itext.xml:1257
#, no-c-format
-msgid ""
-"This section documents some of the constants shared by attributes on "
-"multiple tags."
+msgid "This section documents some of the constants shared by attributes on multiple tags."
msgstr ""
#. Tag: title
@@ -1267,14 +1150,7 @@
#. Tag: para
#: Itext.xml:1261
#, no-c-format
-msgid ""
-"Seam documents do not yet support a full color specification. Currently, "
-"only named colors are supported. They are: <literal>white</literal>, "
-"<literal>gray</literal>, <literal>lightgray</literal>, <literal>darkgray</"
-"literal>, <literal>black</literal>, <literal>red</literal>, <literal>pink</"
-"literal>, <literal>yellow</literal>, <literal>green</literal>, "
-"<literal>magenta</literal>, <literal>cyan</literal> and <literal>blue</"
-"literal>."
+msgid "Seam documents do not yet support a full color specification. Currently, only named colors are supported. They are: <literal>white</literal>, <literal>gray</literal>, <literal>lightgray</literal>, <literal>darkgray</literal>, <literal>black</literal>, <literal>red</literal>, <literal>pink</literal>, <literal>yellow</literal>, <literal>green</literal>, <literal>magenta</literal>, <literal>cyan</literal> and <literal>blue</literal>."
msgstr ""
#. Tag: title
@@ -1286,13 +1162,7 @@
#. Tag: para
#: Itext.xml:1272
#, no-c-format
-msgid ""
-"Where alignment values are used, the Seam PDF supports the following "
-"horizontal alignment values: <literal>left</literal>, <literal>right</"
-"literal>, <literal>center</literal>, <literal>justify</literal> and "
-"<literal>justifyall</literal>. The vertical alignment values are "
-"<literal>top</literal>, <literal>middle</literal>, <literal>bottom</"
-"literal>, and <literal>baseline</literal>."
+msgid "Where alignment values are used, the Seam PDF supports the following horizontal alignment values: <literal>left</literal>, <literal>right</literal>, <literal>center</literal>, <literal>justify</literal> and <literal>justifyall</literal>. The vertical alignment values are <literal>top</literal>, <literal>middle</literal>, <literal>bottom</literal>, and <literal>baseline</literal>."
msgstr ""
#. Tag: title
@@ -1304,13 +1174,7 @@
#. Tag: para
#: Itext.xml:1288
#, no-c-format
-msgid ""
-"Charting support is also provided with <literal>jboss-seam-pdf.jar</"
-"literal>. Charts can be used in PDF documents or can be used as images in an "
-"HTML page. Charting requires the JFreeChart library (<literal>jfreechart."
-"jar</literal> and <literal>jcommon.jar</literal>) to be added to the "
-"<literal>WEB-INF/lib</literal> directory. Three types of charts are "
-"currently supported: pie charts, bar charts and line charts."
+msgid "Charting support is also provided with <literal>jboss-seam-pdf.jar</literal>. Charts can be used in PDF documents or can be used as images in an HTML page. Charting requires the JFreeChart library (<literal>jfreechart.jar</literal> and <literal>jcommon.jar</literal>) to be added to the <literal>WEB-INF/lib</literal> directory. Three types of charts are currently supported: pie charts, bar charts and line charts."
msgstr ""
#. Tag: literal
@@ -1326,232 +1190,215 @@
msgstr ""
#. Tag: para
-#: Itext.xml:1317 Itext.xml:1513
+#: Itext.xml:1317
+#: Itext.xml:1513
#, no-c-format
-msgid ""
-"<literal>borderVisible</literal> — Controls whether or not a border is "
-"displayed around the entire chart."
+msgid "<literal>borderVisible</literal> — Controls whether or not a border is displayed around the entire chart."
msgstr ""
#. Tag: para
-#: Itext.xml:1323 Itext.xml:1519
+#: Itext.xml:1323
+#: Itext.xml:1519
#, no-c-format
-msgid ""
-"<literal>borderPaint</literal> — The color of the border, if visible;"
+msgid "<literal>borderPaint</literal> — The color of the border, if visible;"
msgstr ""
#. Tag: para
-#: Itext.xml:1328 Itext.xml:1524
+#: Itext.xml:1328
+#: Itext.xml:1524
#, no-c-format
-msgid ""
-"<literal>borderBackgroundPaint</literal> — The default background "
-"color of the chart."
+msgid "<literal>borderBackgroundPaint</literal> — The default background color of the chart."
msgstr ""
#. Tag: para
-#: Itext.xml:1333 Itext.xml:1529
+#: Itext.xml:1333
+#: Itext.xml:1529
#, no-c-format
msgid "<literal>borderStroke</literal> —"
msgstr ""
#. Tag: para
-#: Itext.xml:1339 Itext.xml:1535
+#: Itext.xml:1339
+#: Itext.xml:1535
#, no-c-format
-msgid ""
-"<literal>domainAxisLabel</literal> — The text label for the domain "
-"axis."
+msgid "<literal>domainAxisLabel</literal> — The text label for the domain axis."
msgstr ""
#. Tag: para
-#: Itext.xml:1344 Itext.xml:1540
+#: Itext.xml:1344
+#: Itext.xml:1540
#, no-c-format
-msgid ""
-"<literal>domainAxisPaint</literal> — The color of the domain axis "
-"label."
+msgid "<literal>domainAxisPaint</literal> — The color of the domain axis label."
msgstr ""
#. Tag: para
-#: Itext.xml:1350 Itext.xml:1546
+#: Itext.xml:1350
+#: Itext.xml:1546
#, no-c-format
-msgid ""
-"<literal>domainGridlinesVisible</literal>— Controls whether or not "
-"gridlines for the domain axis are shown on the chart."
+msgid "<literal>domainGridlinesVisible</literal>— Controls whether or not gridlines for the domain axis are shown on the chart."
msgstr ""
#. Tag: para
-#: Itext.xml:1355 Itext.xml:1551
+#: Itext.xml:1355
+#: Itext.xml:1551
#, no-c-format
-msgid ""
-"<literal>domainGridlinePaint</literal>— The color of the domain "
-"gridlines, if visible."
+msgid "<literal>domainGridlinePaint</literal>— The color of the domain gridlines, if visible."
msgstr ""
#. Tag: para
-#: Itext.xml:1360 Itext.xml:1556
+#: Itext.xml:1360
+#: Itext.xml:1556
#, no-c-format
-msgid ""
-"<literal>domainGridlineStroke</literal> — The stroke style of the "
-"domain gridleines, if visible."
+msgid "<literal>domainGridlineStroke</literal> — The stroke style of the domain gridleines, if visible."
msgstr ""
#. Tag: para
-#: Itext.xml:1366 Itext.xml:1562
+#: Itext.xml:1366
+#: Itext.xml:1562
#, no-c-format
msgid "<literal>height</literal> — The height of the chart."
msgstr ""
#. Tag: para
-#: Itext.xml:1371 Itext.xml:1484 Itext.xml:1567 Itext.xml:1680
+#: Itext.xml:1371
+#: Itext.xml:1484
+#: Itext.xml:1567
+#: Itext.xml:1680
#, no-c-format
msgid "<literal>width</literal> — The width of the chart."
msgstr ""
#. Tag: para
-#: Itext.xml:1376 Itext.xml:1572
+#: Itext.xml:1376
+#: Itext.xml:1572
#, no-c-format
-msgid ""
-"<literal>is3D</literal> — A boolean value indicating that the chart "
-"should be rendered in 3D instead of 2D."
+msgid "<literal>is3D</literal> — A boolean value indicating that the chart should be rendered in 3D instead of 2D."
msgstr ""
#. Tag: para
-#: Itext.xml:1382 Itext.xml:1578
+#: Itext.xml:1382
+#: Itext.xml:1578
#, no-c-format
-msgid ""
-"<literal>legend</literal> — A boolean value indicating whether or not "
-"the chart should include a legend."
+msgid "<literal>legend</literal> — A boolean value indicating whether or not the chart should include a legend."
msgstr ""
#. Tag: para
-#: Itext.xml:1388 Itext.xml:1584
+#: Itext.xml:1388
+#: Itext.xml:1584
#, no-c-format
-msgid ""
-"<literal>legendItemPaint</literal>— The default color of the text "
-"labels in the legend."
+msgid "<literal>legendItemPaint</literal>— The default color of the text labels in the legend."
msgstr ""
#. Tag: para
-#: Itext.xml:1394 Itext.xml:1590
+#: Itext.xml:1394
+#: Itext.xml:1590
#, no-c-format
-msgid ""
-"<literal>legendItemBackgoundPaint</literal>— The background color for "
-"the legend, if different from the chart background color."
+msgid "<literal>legendItemBackgoundPaint</literal>— The background color for the legend, if different from the chart background color."
msgstr ""
#. Tag: para
-#: Itext.xml:1400 Itext.xml:1596
+#: Itext.xml:1400
+#: Itext.xml:1596
#, no-c-format
-msgid ""
-"<literal>legendOutlinePaint</literal>— The color of the border around "
-"the legend."
+msgid "<literal>legendOutlinePaint</literal>— The color of the border around the legend."
msgstr ""
#. Tag: para
-#: Itext.xml:1406 Itext.xml:1602
+#: Itext.xml:1406
+#: Itext.xml:1602
#, no-c-format
-msgid ""
-"<literal>orientation</literal> — The orientation of the plot, either "
-"<code>vertical</code> (the default) or <code>horizontal</code>."
+msgid "<literal>orientation</literal> — The orientation of the plot, either <code>vertical</code> (the default) or <code>horizontal</code>."
msgstr ""
#. Tag: para
-#: Itext.xml:1412 Itext.xml:1608
+#: Itext.xml:1412
+#: Itext.xml:1608
#, no-c-format
-msgid ""
-"<literal>plotBackgroundPaint</literal>— The color of the plot "
-"background."
+msgid "<literal>plotBackgroundPaint</literal>— The color of the plot background."
msgstr ""
#. Tag: para
-#: Itext.xml:1418 Itext.xml:1614
+#: Itext.xml:1418
+#: Itext.xml:1614
#, no-c-format
-msgid ""
-"<literal>plotBackgroundAlpha</literal>— The alpha (transparency) level "
-"of the plot background. It should be a number between 0 (completely "
-"transparent) and 1 (completely opaque)."
+msgid "<literal>plotBackgroundAlpha</literal>— The alpha (transparency) level of the plot background. It should be a number between 0 (completely transparent) and 1 (completely opaque)."
msgstr ""
#. Tag: para
-#: Itext.xml:1425 Itext.xml:1621
+#: Itext.xml:1425
+#: Itext.xml:1621
#, no-c-format
-msgid ""
-"<literal>plotForegroundAlpha</literal>— The alpha (transparency) level "
-"of the plot. It should be a number between 0 (completely transparent) and 1 "
-"(completely opaque)."
+msgid "<literal>plotForegroundAlpha</literal>— The alpha (transparency) level of the plot. It should be a number between 0 (completely transparent) and 1 (completely opaque)."
msgstr ""
#. Tag: para
-#: Itext.xml:1432 Itext.xml:1628
+#: Itext.xml:1432
+#: Itext.xml:1628
#, no-c-format
-msgid ""
-"<literal>plotOutlinePaint</literal>— The color of the range gridlines, "
-"if visible."
+msgid "<literal>plotOutlinePaint</literal>— The color of the range gridlines, if visible."
msgstr ""
#. Tag: para
-#: Itext.xml:1437 Itext.xml:1633
+#: Itext.xml:1437
+#: Itext.xml:1633
#, no-c-format
-msgid ""
-"<literal>plotOutlineStroke</literal> — The stroke style of the range "
-"gridleines, if visible."
+msgid "<literal>plotOutlineStroke</literal> — The stroke style of the range gridleines, if visible."
msgstr ""
#. Tag: para
-#: Itext.xml:1443 Itext.xml:1639
+#: Itext.xml:1443
+#: Itext.xml:1639
#, no-c-format
-msgid ""
-"<literal>rangeAxisLabel</literal> — The text label for the range axis."
+msgid "<literal>rangeAxisLabel</literal> — The text label for the range axis."
msgstr ""
#. Tag: para
-#: Itext.xml:1448 Itext.xml:1644
+#: Itext.xml:1448
+#: Itext.xml:1644
#, no-c-format
-msgid ""
-"<literal>rangeAxisPaint</literal> — The color of the range axis label."
+msgid "<literal>rangeAxisPaint</literal> — The color of the range axis label."
msgstr ""
#. Tag: para
-#: Itext.xml:1454 Itext.xml:1650
+#: Itext.xml:1454
+#: Itext.xml:1650
#, no-c-format
-msgid ""
-"<literal>rangeGridlinesVisible</literal>— Controls whether or not "
-"gridlines for the range axis are shown on the chart."
+msgid "<literal>rangeGridlinesVisible</literal>— Controls whether or not gridlines for the range axis are shown on the chart."
msgstr ""
#. Tag: para
-#: Itext.xml:1459 Itext.xml:1655
+#: Itext.xml:1459
+#: Itext.xml:1655
#, no-c-format
-msgid ""
-"<literal>rangeGridlinePaint</literal>— The color of the range "
-"gridlines, if visible."
+msgid "<literal>rangeGridlinePaint</literal>— The color of the range gridlines, if visible."
msgstr ""
#. Tag: para
-#: Itext.xml:1464 Itext.xml:1660
+#: Itext.xml:1464
+#: Itext.xml:1660
#, no-c-format
-msgid ""
-"<literal>rangeGridlineStroke</literal> — The stroke style of the range "
-"gridleines, if visible."
+msgid "<literal>rangeGridlineStroke</literal> — The stroke style of the range gridleines, if visible."
msgstr ""
#. Tag: para
-#: Itext.xml:1470 Itext.xml:1666
+#: Itext.xml:1470
+#: Itext.xml:1666
#, no-c-format
msgid "<literal>title</literal> — The chart title text."
msgstr ""
#. Tag: para
-#: Itext.xml:1474 Itext.xml:1670
+#: Itext.xml:1474
+#: Itext.xml:1670
#, no-c-format
msgid "<literal>titlePaint</literal>— The color of the chart title text."
msgstr ""
#. Tag: para
-#: Itext.xml:1479 Itext.xml:1675
+#: Itext.xml:1479
+#: Itext.xml:1675
#, no-c-format
-msgid ""
-"<literal>titleBackgroundPaint</literal>— The background color around "
-"the chart title."
+msgid "<literal>titleBackgroundPaint</literal>— The background color around the chart title."
msgstr ""
#. Tag: programlisting
@@ -1619,24 +1466,19 @@
#. Tag: para
#: Itext.xml:1714
#, no-c-format
-msgid ""
-"<literal>label</literal>— The default label text for pie sections."
+msgid "<literal>label</literal>— The default label text for pie sections."
msgstr ""
#. Tag: para
#: Itext.xml:1719
#, no-c-format
-msgid ""
-"<literal>legend</literal>— A boolean value indicating whether or not "
-"the chart should include a legend. Default value is true"
+msgid "<literal>legend</literal>— A boolean value indicating whether or not the chart should include a legend. Default value is true"
msgstr ""
#. Tag: para
#: Itext.xml:1724
#, no-c-format
-msgid ""
-"<literal>is3D</literal>—A boolean value indicating that the chart "
-"should be rendered in 3D instead of 2D."
+msgid "<literal>is3D</literal>—A boolean value indicating that the chart should be rendered in 3D instead of 2D."
msgstr ""
#. Tag: para
@@ -1648,131 +1490,97 @@
#. Tag: para
#: Itext.xml:1734
#, no-c-format
-msgid ""
-"<literal>labelLinkPaint</literal>— The paint used for the label "
-"linking lines."
+msgid "<literal>labelLinkPaint</literal>— The paint used for the label linking lines."
msgstr ""
#. Tag: para
#: Itext.xml:1739
#, no-c-format
-msgid ""
-"<literal>labelLinkStroke</literal>— he stroke used for the label "
-"linking lines."
+msgid "<literal>labelLinkStroke</literal>— he stroke used for the label linking lines."
msgstr ""
#. Tag: para
#: Itext.xml:1745
#, no-c-format
-msgid ""
-"<literal>labelLinksVisible</literal>— A flag that controls whether or "
-"not the label links are drawn."
+msgid "<literal>labelLinksVisible</literal>— A flag that controls whether or not the label links are drawn."
msgstr ""
#. Tag: para
#: Itext.xml:1750
#, no-c-format
-msgid ""
-"<literal>labelOutlinePaint</literal>— The paint used to draw the "
-"outline of the section labels."
+msgid "<literal>labelOutlinePaint</literal>— The paint used to draw the outline of the section labels."
msgstr ""
#. Tag: para
#: Itext.xml:1755
#, no-c-format
-msgid ""
-"<literal>labelOutlineStroke</literal>— The stroke used to draw the "
-"outline of the section labels."
+msgid "<literal>labelOutlineStroke</literal>— The stroke used to draw the outline of the section labels."
msgstr ""
#. Tag: para
#: Itext.xml:1760
#, no-c-format
-msgid ""
-"<literal>labelShadowPaint</literal>— The paint used to draw the shadow "
-"for the section labels."
+msgid "<literal>labelShadowPaint</literal>— The paint used to draw the shadow for the section labels."
msgstr ""
#. Tag: para
#: Itext.xml:1765
#, no-c-format
-msgid ""
-"<literal>labelPaint</literal>— The color used to draw the section "
-"labels"
+msgid "<literal>labelPaint</literal>— The color used to draw the section labels"
msgstr ""
#. Tag: para
#: Itext.xml:1770
#, no-c-format
-msgid ""
-"<literal>labelGap</literal>— The gap between the labels and the plot "
-"as a percentage of the plot width."
+msgid "<literal>labelGap</literal>— The gap between the labels and the plot as a percentage of the plot width."
msgstr ""
#. Tag: para
#: Itext.xml:1775
#, no-c-format
-msgid ""
-"<literal>labelBackgroundPaint</literal>— The color used to draw the "
-"background of the section labels. If this is null, the background is not "
-"filled."
+msgid "<literal>labelBackgroundPaint</literal>— The color used to draw the background of the section labels. If this is null, the background is not filled."
msgstr ""
#. Tag: para
#: Itext.xml:1782
#, no-c-format
-msgid ""
-"<literal>startAngle</literal>— The starting angle of the first section."
+msgid "<literal>startAngle</literal>— The starting angle of the first section."
msgstr ""
#. Tag: para
#: Itext.xml:1787
#, no-c-format
-msgid ""
-"<literal>circular</literal>— A boolean value indicating that the chart "
-"should be drawn as a circle. If false, the chart is drawn as an ellipse. The "
-"default is true."
+msgid "<literal>circular</literal>— A boolean value indicating that the chart should be drawn as a circle. If false, the chart is drawn as an ellipse. The default is true."
msgstr ""
#. Tag: para
#: Itext.xml:1793
#, no-c-format
-msgid ""
-"<literal>direction</literal>— The direction the pie section are drawn. "
-"One of: <literal>clockwise</literal> or <literal>anticlockwise</literal>. "
-"The default is <literal>clockwise</literal>."
+msgid "<literal>direction</literal>— The direction the pie section are drawn. One of: <literal>clockwise</literal> or <literal>anticlockwise</literal>. The default is <literal>clockwise</literal>."
msgstr ""
#. Tag: para
#: Itext.xml:1799
#, no-c-format
-msgid ""
-"<literal>sectionOutlinePaint</literal>— The outline paint for all "
-"sections."
+msgid "<literal>sectionOutlinePaint</literal>— The outline paint for all sections."
msgstr ""
#. Tag: para
#: Itext.xml:1804
#, no-c-format
-msgid ""
-"<literal>sectionOutlineStroke</literal>— The outline stroke for all "
-"sections"
+msgid "<literal>sectionOutlineStroke</literal>— The outline stroke for all sections"
msgstr ""
#. Tag: para
#: Itext.xml:1809
#, no-c-format
-msgid ""
-"<literal>sectionOutlinesVisible</literal>— Indicates whether an "
-"outline is drawn for each section in the plot."
+msgid "<literal>sectionOutlinesVisible</literal>— Indicates whether an outline is drawn for each section in the plot."
msgstr ""
#. Tag: para
#: Itext.xml:1814
#, no-c-format
-msgid ""
-"<literal>baseSectionOutlinePaint</literal>— The base section outline "
-"paint."
+msgid "<literal>baseSectionOutlinePaint</literal>— The base section outline paint."
msgstr ""
#. Tag: para
@@ -1784,17 +1592,14 @@
#. Tag: para
#: Itext.xml:1823
#, no-c-format
-msgid ""
-"<literal>baseSectionOutlineStroke</literal>— The base section outline "
-"stroke."
+msgid "<literal>baseSectionOutlineStroke</literal>— The base section outline stroke."
msgstr ""
#. Tag: programlisting
#: Itext.xml:1831
#, no-c-format
msgid ""
-"<![CDATA[<p:piechart title=\"Pie Chart\" circular=\"false\" direction="
-"\"anticlockwise\" \n"
+"<![CDATA[<p:piechart title=\"Pie Chart\" circular=\"false\" direction=\"anticlockwise\" \n"
" startAngle=\"30\" labelGap=\"0.1\" labelLinkPaint=\"red\"> \n"
" <p:series key=\"Prices\"> \n"
" <p:data key=\"2003\" columnKey=\"2003\" value=\"7.36\" /> \n"
@@ -1815,10 +1620,7 @@
#. Tag: para
#: Itext.xml:1845
#, no-c-format
-msgid ""
-"Category data can be broken down into series. The series tag is used to "
-"categorize a set of data with a series and apply styling to the entire "
-"series."
+msgid "Category data can be broken down into series. The series tag is used to categorize a set of data with a series and apply styling to the entire series."
msgstr ""
#. Tag: para
@@ -1830,40 +1632,31 @@
#. Tag: para
#: Itext.xml:1865
#, no-c-format
-msgid ""
-"<literal>seriesPaint</literal> — The color of each item in the series"
+msgid "<literal>seriesPaint</literal> — The color of each item in the series"
msgstr ""
#. Tag: para
#: Itext.xml:1871
#, no-c-format
-msgid ""
-"<literal>seriesOutlinePaint</literal> — The outline color for each "
-"item in the series."
+msgid "<literal>seriesOutlinePaint</literal> — The outline color for each item in the series."
msgstr ""
#. Tag: para
#: Itext.xml:1876
#, no-c-format
-msgid ""
-"<literal>seriesOutlineStroke</literal> — The stroke used to draw each "
-"item in the series."
+msgid "<literal>seriesOutlineStroke</literal> — The stroke used to draw each item in the series."
msgstr ""
#. Tag: para
#: Itext.xml:1888
#, no-c-format
-msgid ""
-"<literal>seriesVisible</literal> — A boolean indicating if the series "
-"should be displayed."
+msgid "<literal>seriesVisible</literal> — A boolean indicating if the series should be displayed."
msgstr ""
#. Tag: para
#: Itext.xml:1893
#, no-c-format
-msgid ""
-"<literal>seriesVisibleInLegend</literal> — A boolean indiciating if "
-"the series should be listed in the legend."
+msgid "<literal>seriesVisibleInLegend</literal> — A boolean indiciating if the series should be listed in the legend."
msgstr ""
#. Tag: programlisting
@@ -1898,9 +1691,7 @@
#. Tag: para
#: Itext.xml:1927
#, no-c-format
-msgid ""
-"<literal>series</literal> — The series name, when not embedded inside "
-"a <code><p:series></code>."
+msgid "<literal>series</literal> — The series name, when not embedded inside a <code><p:series></code>."
msgstr ""
#. Tag: para
@@ -1912,33 +1703,25 @@
#. Tag: para
#: Itext.xml:1936
#, no-c-format
-msgid ""
-"<literal>explodedPercent</literal> — For pie charts, indicates how "
-"exploded a from the pie a piece is."
+msgid "<literal>explodedPercent</literal> — For pie charts, indicates how exploded a from the pie a piece is."
msgstr ""
#. Tag: para
#: Itext.xml:1942
#, no-c-format
-msgid ""
-"<literal>sectionOutlinePaint</literal> — For bar charts, the color of "
-"the section outline."
+msgid "<literal>sectionOutlinePaint</literal> — For bar charts, the color of the section outline."
msgstr ""
#. Tag: para
#: Itext.xml:1947
#, no-c-format
-msgid ""
-"<literal>sectionOutlineStroke</literal> — For bar charts, the stroke "
-"type for the section outline."
+msgid "<literal>sectionOutlineStroke</literal> — For bar charts, the stroke type for the section outline."
msgstr ""
#. Tag: para
#: Itext.xml:1952
#, no-c-format
-msgid ""
-"<literal>sectionPaint</literal> — For bar charts, the color of the "
-"section."
+msgid "<literal>sectionPaint</literal> — For bar charts, the color of the section."
msgstr ""
#. Tag: programlisting
@@ -1961,41 +1744,31 @@
#. Tag: para
#: Itext.xml:1977
#, no-c-format
-msgid ""
-"The color component declares a color or gradient than can be referenced when "
-"drawing filled shapes."
+msgid "The color component declares a color or gradient than can be referenced when drawing filled shapes."
msgstr ""
#. Tag: para
#: Itext.xml:1986
#, no-c-format
-msgid ""
-"<literal>color</literal> — The color value. For gradient colors, this "
-"the starting color."
+msgid "<literal>color</literal> — The color value. For gradient colors, this the starting color."
msgstr ""
#. Tag: para
#: Itext.xml:1992
#, no-c-format
-msgid ""
-"<literal>color2</literal> — For gradient colors, this is the color "
-"that ends the gradient."
+msgid "<literal>color2</literal> — For gradient colors, this is the color that ends the gradient."
msgstr ""
#. Tag: para
#: Itext.xml:1997
#, no-c-format
-msgid ""
-"<literal>point</literal> — The co-ordinates where the gradient color "
-"begins."
+msgid "<literal>point</literal> — The co-ordinates where the gradient color begins."
msgstr ""
#. Tag: para
#: Itext.xml:2002
#, no-c-format
-msgid ""
-"<literal>point2</literal> — The co-ordinates where the gradient color "
-"ends."
+msgid "<literal>point2</literal> — The co-ordinates where the gradient color ends."
msgstr ""
#. Tag: programlisting
@@ -2028,52 +1801,37 @@
#. Tag: para
#: Itext.xml:2037
#, no-c-format
-msgid ""
-"<literal>cap</literal> — The line cap type. Valid values are "
-"<literal>butt</literal>, <literal>round</literal> and <literal>square</"
-"literal>"
+msgid "<literal>cap</literal> — The line cap type. Valid values are <literal>butt</literal>, <literal>round</literal> and <literal>square</literal>"
msgstr ""
#. Tag: para
#: Itext.xml:2043
#, no-c-format
-msgid ""
-"<literal>join</literal> — The line join type. Valid values are "
-"<literal>miter</literal>, <literal>round</literal> and <literal>bevel</"
-"literal>"
+msgid "<literal>join</literal> — The line join type. Valid values are <literal>miter</literal>, <literal>round</literal> and <literal>bevel</literal>"
msgstr ""
#. Tag: para
#: Itext.xml:2049
#, no-c-format
-msgid ""
-"<literal>miterLimit</literal> — For miter joins, this value is the "
-"limit of the size of the join."
+msgid "<literal>miterLimit</literal> — For miter joins, this value is the limit of the size of the join."
msgstr ""
#. Tag: para
#: Itext.xml:2055
#, no-c-format
-msgid ""
-"<literal>dash</literal> — The dash value sets the dash pattern to be "
-"used to draw the line. The space separated integers indicate the length of "
-"each alternating drawn and undrawn segments."
+msgid "<literal>dash</literal> — The dash value sets the dash pattern to be used to draw the line. The space separated integers indicate the length of each alternating drawn and undrawn segments."
msgstr ""
#. Tag: para
#: Itext.xml:2062
#, no-c-format
-msgid ""
-"<literal>dashPhase</literal> — The dash phase indicates the offset "
-"into the dash pattern that the the line should be drawn with."
+msgid "<literal>dashPhase</literal> — The dash phase indicates the offset into the dash pattern that the the line should be drawn with."
msgstr ""
#. Tag: programlisting
#: Itext.xml:2070
#, no-c-format
-msgid ""
-"<![CDATA[<p:stroke id=\"dot2\" width=\"2\" cap=\"round\" join=\"bevel\" dash="
-"\"2 3\" />]]>"
+msgid "<![CDATA[<p:stroke id=\"dot2\" width=\"2\" cap=\"round\" join=\"bevel\" dash=\"2 3\" />]]>"
msgstr ""
#. Tag: title
@@ -2085,11 +1843,7 @@
#. Tag: para
#: Itext.xml:2083
#, no-c-format
-msgid ""
-"Seam can use iText to generate barcodes in a wide variety of formats. These "
-"barcodes can be embedded in a PDF document or displayed as an image on a web "
-"page. Note that when used with HTML images, barcodes can not currently "
-"display barcode text in the barcode."
+msgid "Seam can use iText to generate barcodes in a wide variety of formats. These barcodes can be embedded in a PDF document or displayed as an image on a web page. Note that when used with HTML images, barcodes can not currently display barcode text in the barcode."
msgstr ""
#. Tag: literal
@@ -2107,13 +1861,7 @@
#. Tag: para
#: Itext.xml:2113
#, no-c-format
-msgid ""
-"<literal>type</literal> — A barcode type supported by iText. Valid "
-"values include: <literal>EAN13</literal>, <literal>EAN8</literal>, "
-"<literal>UPCA</literal>, <literal>UPCE</literal>, <literal>SUPP2</literal>, "
-"<literal>SUPP5</literal>, <literal>POSTNET</literal>, <literal>PLANET</"
-"literal>, <literal>CODE128</literal>, <literal>CODE128_UCC</literal>, "
-"<literal>CODE128_RAW</literal> and <literal>CODABAR</literal>."
+msgid "<literal>type</literal> — A barcode type supported by iText. Valid values include: <literal>EAN13</literal>, <literal>EAN8</literal>, <literal>UPCA</literal>, <literal>UPCE</literal>, <literal>SUPP2</literal>, <literal>SUPP5</literal>, <literal>POSTNET</literal>, <literal>PLANET</literal>, <literal>CODE128</literal>, <literal>CODE128_UCC</literal>, <literal>CODE128_RAW</literal> and <literal>CODABAR</literal>."
msgstr ""
#. Tag: para
@@ -2125,32 +1873,25 @@
#. Tag: para
#: Itext.xml:2128
#, no-c-format
-msgid ""
-"<literal>xpos</literal>— For PDFs, the absolute y position of the "
-"barcode on the page."
+msgid "<literal>xpos</literal>— For PDFs, the absolute y position of the barcode on the page."
msgstr ""
#. Tag: para
#: Itext.xml:2133
#, no-c-format
-msgid ""
-"<literal>ypos</literal>— For PDFs, the absolute y position of the "
-"barcode on the page."
+msgid "<literal>ypos</literal>— For PDFs, the absolute y position of the barcode on the page."
msgstr ""
#. Tag: para
#: Itext.xml:2138
#, no-c-format
-msgid ""
-"<literal>rotDegrees</literal> — For PDFs, the rotation factor of the "
-"barcode in degrees."
+msgid "<literal>rotDegrees</literal> — For PDFs, the rotation factor of the barcode in degrees."
msgstr ""
#. Tag: para
#: Itext.xml:2143
#, no-c-format
-msgid ""
-"<literal>barHeight</literal> — The height of the bars in the barCode"
+msgid "<literal>barHeight</literal> — The height of the bars in the barCode"
msgstr ""
#. Tag: para
@@ -2162,10 +1903,7 @@
#. Tag: para
#: Itext.xml:2153
#, no-c-format
-msgid ""
-"<literal>barMultiplier</literal> — The bar multiplier for wide bars or "
-"the distance between bars for <literal>POSTNET</literal> and "
-"<literal>PLANET</literal> code."
+msgid "<literal>barMultiplier</literal> — The bar multiplier for wide bars or the distance between bars for <literal>POSTNET</literal> and <literal>PLANET</literal> code."
msgstr ""
#. Tag: para
@@ -2177,23 +1915,19 @@
#. Tag: para
#: Itext.xml:2164
#, no-c-format
-msgid ""
-"<literal>textColor</literal> — The color of any text on the barcode."
+msgid "<literal>textColor</literal> — The color of any text on the barcode."
msgstr ""
#. Tag: para
#: Itext.xml:2169
#, no-c-format
-msgid ""
-"<literal>textSize</literal> — The size of the barcode text, if any."
+msgid "<literal>textSize</literal> — The size of the barcode text, if any."
msgstr ""
#. Tag: para
#: Itext.xml:2174
#, no-c-format
-msgid ""
-"<literal>altText</literal> — The <literal>alt</literal> text for HTML "
-"image links."
+msgid "<literal>altText</literal> — The <literal>alt</literal> text for HTML image links."
msgstr ""
#. Tag: programlisting
@@ -2217,9 +1951,7 @@
#. Tag: para
#: Itext.xml:2195
#, no-c-format
-msgid ""
-"If you have a complex, pre-generated PDF with named fields, you can easily "
-"fill in the values from you application and present it to the user."
+msgid "If you have a complex, pre-generated PDF with named fields, you can easily fill in the values from you application and present it to the user."
msgstr ""
#. Tag: literal
@@ -2237,26 +1969,19 @@
#. Tag: para
#: Itext.xml:2224
#, no-c-format
-msgid ""
-"<literal>URL</literal> — An URL pointing to the PDF file to use as a "
-"template. If the value has no protocol part (://), the file is read locally."
+msgid "<literal>URL</literal> — An URL pointing to the PDF file to use as a template. If the value has no protocol part (://), the file is read locally."
msgstr ""
#. Tag: para
#: Itext.xml:2231
#, no-c-format
-msgid ""
-"<literal>filename</literal> — The filename to use for the generated "
-"PDF file."
+msgid "<literal>filename</literal> — The filename to use for the generated PDF file."
msgstr ""
#. Tag: para
#: Itext.xml:2237
#, no-c-format
-msgid ""
-"<literal>exportKey</literal> — Place the generated PDF file in a "
-"DocumentData object under the specified key in the event context. If set, no "
-"redirect will occur."
+msgid "<literal>exportKey</literal> — Place the generated PDF file in a DocumentData object under the specified key in the event context. If set, no redirect will occur."
msgstr ""
#. Tag: literal
@@ -2286,9 +2011,7 @@
#. Tag: para
#: Itext.xml:2287
#, no-c-format
-msgid ""
-"<literal>readOnly</literal> — Should the field be read-only? Defaults "
-"to true."
+msgid "<literal>readOnly</literal> — Should the field be read-only? Defaults to true."
msgstr ""
#. Tag: programlisting
@@ -2297,12 +2020,9 @@
msgid ""
"<![CDATA[\n"
" <p:form\n"
-" xmlns:p=\"http://jboss.com/products/"
-"seam/pdf\"\n"
-" URL=\"http://localhost/Concept/form."
-"pdf\">\n"
-" <p:field name=\"person.name\" value="
-"\"Me, myself and I\"/>\n"
+" xmlns:p=\"http://jboss.com/products/seam/pdf\"\n"
+" URL=\"http://localhost/Concept/form.pdf\">\n"
+" <p:field name=\"person.name\" value=\"Me, myself and I\"/>\n"
" </p:form>\n"
" ]]>"
msgstr ""
@@ -2316,10 +2036,7 @@
#. Tag: para
#: Itext.xml:2305
#, no-c-format
-msgid ""
-"Seam now provides experimental support for rendering Swing components to "
-"into a PDF image. Some Swing look and feels supports, notably ones that use "
-"native widgets, will not render correctly."
+msgid "Seam now provides experimental support for rendering Swing components to into a PDF image. Some Swing look and feels supports, notably ones that use native widgets, will not render correctly."
msgstr ""
#. Tag: literal
@@ -2337,31 +2054,25 @@
#. Tag: para
#: Itext.xml:2335
#, no-c-format
-msgid ""
-"<literal>width</literal> — The width of the component to be rendered."
+msgid "<literal>width</literal> — The width of the component to be rendered."
msgstr ""
#. Tag: para
#: Itext.xml:2339
#, no-c-format
-msgid ""
-"<literal>height</literal> — ..The height of the component to be "
-"rendered."
+msgid "<literal>height</literal> — ..The height of the component to be rendered."
msgstr ""
#. Tag: para
#: Itext.xml:2343
#, no-c-format
-msgid ""
-"<literal>component</literal> — An expression whose value is a Swing or "
-"AWT component."
+msgid "<literal>component</literal> — An expression whose value is a Swing or AWT component."
msgstr ""
#. Tag: programlisting
#: Itext.xml:2351
#, no-c-format
-msgid ""
-"<![CDATA[<p:swing width=\"310\" height=\"120\" component=\"#{aButton}\" />]]>"
+msgid "<![CDATA[<p:swing width=\"310\" height=\"120\" component=\"#{aButton}\" />]]>"
msgstr ""
#. Tag: title
@@ -2373,22 +2084,13 @@
#. Tag: para
#: Itext.xml:2364
#, no-c-format
-msgid ""
-"Document generation works out of the box with no additional configuration "
-"needed. However, there are a few points of configuration that are needed for "
-"more serious applications."
+msgid "Document generation works out of the box with no additional configuration needed. However, there are a few points of configuration that are needed for more serious applications."
msgstr ""
#. Tag: para
#: Itext.xml:2367
#, no-c-format
-msgid ""
-"The default implementation serves PDF documents from a generic URL, "
-"<literal>/seam-doc.seam</literal>. Many browsers (and users) would prefer to "
-"see URLs that contain the actual PDF name like <literal>/myDocument.pdf</"
-"literal>. This capability requires some configuration. To serve PDF files, "
-"all <literal>*.pdf</literal> resources should be mapped to the "
-"DocumentStoreServlet:"
+msgid "The default implementation serves PDF documents from a generic URL, <literal>/seam-doc.seam</literal>. Many browsers (and users) would prefer to see URLs that contain the actual PDF name like <literal>/myDocument.pdf</literal>. This capability requires some configuration. To serve PDF files, all <literal>*.pdf</literal> resources should be mapped to the DocumentStoreServlet:"
msgstr ""
#. Tag: programlisting
@@ -2397,8 +2099,7 @@
msgid ""
"<![CDATA[<servlet>\n"
" <servlet-name>Document Store Servlet</servlet-name>\n"
-" <servlet-class>org.jboss.seam.document.DocumentStoreServlet</servlet-"
-"class>\n"
+" <servlet-class>org.jboss.seam.document.DocumentStoreServlet</servlet-class>\n"
"</servlet>\n"
"\n"
"<servlet-mapping>\n"
@@ -2410,11 +2111,7 @@
#. Tag: para
#: Itext.xml:2374
#, no-c-format
-msgid ""
-"The <literal>use-extensions</literal> option on the document store component "
-"completes the functionality by instructing the document store to generate "
-"URLs with the correct filename extension for the document type being "
-"generated."
+msgid "The <literal>use-extensions</literal> option on the document store component completes the functionality by instructing the document store to generate URLs with the correct filename extension for the document type being generated."
msgstr ""
#. Tag: programlisting
@@ -2425,10 +2122,8 @@
" xmlns:document=\"http://jboss.com/products/seam/document\"\n"
" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
" xsi:schemaLocation=\"\n"
-" http://jboss.com/products/seam/document http://jboss.com/products/"
-"seam/document-2.1.xsd\n"
-" http://jboss.com/products/seam/components http://jboss.com/products/"
-"seam/components-2.1.xsd\">\n"
+" http://jboss.com/products/seam/document http://jboss.com/products/seam/document-2.1.xsd\n"
+" http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
" <document:document-store use-extensions=\"true\"/>\n"
"</components>]]>"
msgstr ""
@@ -2436,20 +2131,13 @@
#. Tag: para
#: Itext.xml:2380
#, no-c-format
-msgid ""
-"The document store stores documents in conversation scope, and documents "
-"will expire when the conversation ends. At that point, references to the "
-"document will be invalid. You can specify a default view to be shown when a "
-"document does not exist using the <literal>error-page</literal> property of "
-"the <literal>documentStore</literal>."
+msgid "The document store stores documents in conversation scope, and documents will expire when the conversation ends. At that point, references to the document will be invalid. You can specify a default view to be shown when a document does not exist using the <literal>error-page</literal> property of the <literal>documentStore</literal>."
msgstr ""
#. Tag: programlisting
#: Itext.xml:2383
#, no-c-format
-msgid ""
-"<![CDATA[<document:document-store use-extensions=\"true\" error-page=\"/"
-"documentMissing.seam\" />]]>"
+msgid "<![CDATA[<document:document-store use-extensions=\"true\" error-page=\"/documentMissing.seam\" />]]>"
msgstr ""
#. Tag: title
@@ -2475,3 +2163,4 @@
#, no-c-format
msgid "iText in Action"
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -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-07 22:40+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,15 +22,7 @@
#. Tag: para
#: Jbpm.xml:4
#, no-c-format
-msgid ""
-"JBoss jBPM is a business process management engine for any Java SE or EE "
-"environment. jBPM lets you represent a business process or user interaction "
-"as a graph of nodes representing wait states, decisions, tasks, web pages, "
-"etc. The graph is defined using a simple, very readable, XML dialect called "
-"jPDL, and may be edited and visualised graphically using an eclipse plugin. "
-"jPDL is an extensible language, and is suitable for a range of problems, "
-"from defining web application page flow, to traditional workflow management, "
-"all the way up to orchestration of services in a SOA environment."
+msgid "JBoss jBPM is a business process management engine for any Java SE or EE environment. jBPM lets you represent a business process or user interaction as a graph of nodes representing wait states, decisions, tasks, web pages, etc. The graph is defined using a simple, very readable, XML dialect called jPDL, and may be edited and visualised graphically using an eclipse plugin. jPDL is an extensible language, and is suitable for a range of problems, from defining web application page flow, to traditional workflow management, all the way up to orchestration of services in a SOA environment."
msgstr ""
#. Tag: para
@@ -42,46 +34,25 @@
#. Tag: para
#: Jbpm.xml:22
#, no-c-format
-msgid ""
-"Defining the pageflow involved in complex user interactions. A jPDL process "
-"definition defines the page flow for a single conversation. A Seam "
-"conversation is considered to be a relatively short-running interaction with "
-"a single user."
+msgid "Defining the pageflow involved in complex user interactions. A jPDL process definition defines the page flow for a single conversation. A Seam conversation is considered to be a relatively short-running interaction with a single user."
msgstr ""
#. Tag: para
#: Jbpm.xml:30
#, no-c-format
-msgid ""
-"Defining the overarching business process. The business process may span "
-"multiple conversations with multiple users. Its state is persistent in the "
-"jBPM database, so it is considered long-running. Coordination of the "
-"activities of multiple users is a much more complex problem than scripting "
-"an interaction with a single user, so jBPM offers sophisticated facilities "
-"for task management and dealing with multiple concurrent paths of execution."
+msgid "Defining the overarching business process. The business process may span multiple conversations with multiple users. Its state is persistent in the jBPM database, so it is considered long-running. Coordination of the activities of multiple users is a much more complex problem than scripting an interaction with a single user, so jBPM offers sophisticated facilities for task management and dealing with multiple concurrent paths of execution."
msgstr ""
#. Tag: para
#: Jbpm.xml:42
#, no-c-format
-msgid ""
-"Don't get these two things confused! They operate at very different levels "
-"or granularity. <emphasis>Pageflow</emphasis>, <emphasis>conversation</"
-"emphasis> and <emphasis>task</emphasis> all refer to a single interaction "
-"with a single user. A business process spans many tasks. Futhermore, the two "
-"applications of jBPM are totally orthogonal. You can use them together or "
-"independently or not at all."
+msgid "Don't get these two things confused! They operate at very different levels or granularity. <emphasis>Pageflow</emphasis>, <emphasis>conversation</emphasis> and <emphasis>task</emphasis> all refer to a single interaction with a single user. A business process spans many tasks. Futhermore, the two applications of jBPM are totally orthogonal. You can use them together or independently or not at all."
msgstr ""
#. Tag: para
#: Jbpm.xml:51
#, no-c-format
-msgid ""
-"You don't have to know jDPL to use Seam. If you're perfectly happy defining "
-"pageflow using JSF or Seam navigation rules, and if your application is more "
-"data-driven that process-driven, you probably don't need jBPM. But we're "
-"finding that thinking of user interaction in terms of a well-defined "
-"graphical representation is helping us build more robust applications."
+msgid "You don't have to know jDPL to use Seam. If you're perfectly happy defining pageflow using JSF or Seam navigation rules, and if your application is more data-driven that process-driven, you probably don't need jBPM. But we're finding that thinking of user interaction in terms of a well-defined graphical representation is helping us build more robust applications."
msgstr ""
#. Tag: title
@@ -99,9 +70,7 @@
#. Tag: para
#: Jbpm.xml:67
#, no-c-format
-msgid ""
-"Using JSF or Seam navigation rules - the <emphasis>stateless navigation "
-"model</emphasis>"
+msgid "Using JSF or Seam navigation rules - the <emphasis>stateless navigation model</emphasis>"
msgstr ""
#. Tag: para
@@ -113,10 +82,7 @@
#. Tag: para
#: Jbpm.xml:79
#, no-c-format
-msgid ""
-"Very simple applications will only need the stateless navigation model. Very "
-"complex applications will use both models in different places. Each model "
-"has its strengths and weaknesses!"
+msgid "Very simple applications will only need the stateless navigation model. Very complex applications will use both models in different places. Each model has its strengths and weaknesses!"
msgstr ""
#. Tag: title
@@ -128,13 +94,7 @@
#. Tag: para
#: Jbpm.xml:88
#, no-c-format
-msgid ""
-"The stateless model defines a mapping from a set of named, logical outcomes "
-"of an event directly to the resulting page of the view. The navigation rules "
-"are entirely oblivious to any state held by the application other than what "
-"page was the source of the event. This means that your action listener "
-"methods must sometimes make decisions about the page flow, since only they "
-"have access to the current state of the application."
+msgid "The stateless model defines a mapping from a set of named, logical outcomes of an event directly to the resulting page of the view. The navigation rules are entirely oblivious to any state held by the application other than what page was the source of the event. This means that your action listener methods must sometimes make decisions about the page flow, since only they have access to the current state of the application."
msgstr ""
#. Tag: para
@@ -170,12 +130,33 @@
"\n"
"</navigation-rule>]]>"
msgstr ""
+"<![CDATA[<navigation-rule>\n"
+" <from-view-id>/numberGuess.jsp</from-view-id>\n"
+" \n"
+" <navigation-case>\n"
+" <from-outcome>guess</from-outcome>\n"
+" <to-view-id>/numberGuess.jsp</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+"\n"
+" <navigation-case>\n"
+" <from-outcome>win</from-outcome>\n"
+" <to-view-id>/win.jsp</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+" \n"
+" <navigation-case>\n"
+" <from-outcome>lose</from-outcome>\n"
+" <to-view-id>/lose.jsp</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+"\n"
+"</navigation-rule>]]>"
#. Tag: para
#: Jbpm.xml:105
#, no-c-format
-msgid ""
-"Here is the same example page flow definition using Seam navigation rules:"
+msgid "Here is the same example page flow definition using Seam navigation rules:"
msgstr ""
#. Tag: programlisting
@@ -198,13 +179,26 @@
"\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/numberGuess.jsp\">\n"
+" \n"
+" <navigation>\n"
+" <rule if-outcome=\"guess\">\n"
+" <redirect view-id=\"/numberGuess.jsp\"/>\n"
+" </rule>\n"
+" <rule if-outcome=\"win\">\n"
+" <redirect view-id=\"/win.jsp\"/>\n"
+" </rule>\n"
+" <rule if-outcome=\"lose\">\n"
+" <redirect view-id=\"/lose.jsp\"/>\n"
+" </rule>\n"
+" </navigation>\n"
+"\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:112
#, no-c-format
-msgid ""
-"If you find navigation rules overly verbose, you can return view ids "
-"directly from your action listener methods:"
+msgid "If you find navigation rules overly verbose, you can return view ids directly from your action listener methods:"
msgstr ""
#. Tag: programlisting
@@ -217,13 +211,16 @@
" return null;\n"
"}]]>"
msgstr ""
+"<![CDATA[public String guess() {\n"
+" if (guess==randomNumber) return \"/win.jsp\";\n"
+" if (++guessCount==maxGuesses) return \"/lose.jsp\";\n"
+" return null;\n"
+"}]]>"
#. Tag: para
#: Jbpm.xml:119
#, no-c-format
-msgid ""
-"Note that this results in a redirect. You can even specify parameters to be "
-"used in the redirect:"
+msgid "Note that this results in a redirect. You can even specify parameters to be used in the redirect:"
msgstr ""
#. Tag: programlisting
@@ -231,20 +228,17 @@
#, no-c-format
msgid ""
"<![CDATA[public String search() {\n"
-" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}"
-"\";\n"
+" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}\";\n"
"}]]>"
msgstr ""
+"<![CDATA[public String search() {\n"
+" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}\";\n"
+"}]]>"
#. Tag: para
#: Jbpm.xml:126
#, no-c-format
-msgid ""
-"The stateful model defines a set of transitions between a set of named, "
-"logical application states. In this model, it is possible to express the "
-"flow of any user interaction entirely in the jPDL pageflow definition, and "
-"write action listener methods that are completely unaware of the flow of the "
-"interaction."
+msgid "The stateful model defines a set of transitions between a set of named, logical application states. In this model, it is possible to express the flow of any user interaction entirely in the jPDL pageflow definition, and write action listener methods that are completely unaware of the flow of the interaction."
msgstr ""
#. Tag: para
@@ -266,14 +260,12 @@
" </transition>\n"
" </start-page>\n"
" \n"
-" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}"
-"\">\n"
+" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
" <transition name=\"true\" to=\"win\"/>\n"
" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
" </decision>\n"
" \n"
-" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess."
-"lastGuess}\">\n"
+" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess.lastGuess}\">\n"
" <transition name=\"true\" to=\"lose\"/>\n"
" <transition name=\"false\" to=\"displayGuess\"/>\n"
" </decision>\n"
@@ -290,6 +282,36 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<pageflow-definition name=\"numberGuess\">\n"
+" \n"
+" <start-page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <redirect/>\n"
+" <transition name=\"guess\" to=\"evaluateGuess\">\n"
+" <action expression=\"#{numberGuess.guess}\" />\n"
+" </transition>\n"
+" </start-page>\n"
+" \n"
+" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
+" <transition name=\"true\" to=\"win\"/>\n"
+" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
+" </decision>\n"
+" \n"
+" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess.lastGuess}\">\n"
+" <transition name=\"true\" to=\"lose\"/>\n"
+" <transition name=\"false\" to=\"displayGuess\"/>\n"
+" </decision>\n"
+" \n"
+" <page name=\"win\" view-id=\"/win.jsp\">\n"
+" <redirect/>\n"
+" <end-conversation />\n"
+" </page>\n"
+" \n"
+" <page name=\"lose\" view-id=\"/lose.jsp\">\n"
+" <redirect/>\n"
+" <end-conversation />\n"
+" </page>\n"
+" \n"
+"</pageflow-definition>]]>"
#. Tag: para
#: Jbpm.xml:149
@@ -300,52 +322,31 @@
#. Tag: para
#: Jbpm.xml:155
#, no-c-format
-msgid ""
-"The JSF/Seam navigation rules are <emphasis>much</emphasis> simpler. "
-"(However, this obscures the fact that the underlying Java code is more "
-"complex.)"
+msgid "The JSF/Seam navigation rules are <emphasis>much</emphasis> simpler. (However, this obscures the fact that the underlying Java code is more complex.)"
msgstr ""
#. Tag: para
#: Jbpm.xml:162
#, no-c-format
-msgid ""
-"The jPDL makes the user interaction immediately understandable, without us "
-"needing to even look at the JSP or Java code."
+msgid "The jPDL makes the user interaction immediately understandable, without us needing to even look at the JSP or Java code."
msgstr ""
#. Tag: para
#: Jbpm.xml:169
#, no-c-format
-msgid ""
-"In addition, the stateful model is more <emphasis>constrained</emphasis>. "
-"For each logical state (each step in the page flow), there are a constrained "
-"set of possible transitions to other states. The stateless model is an "
-"<emphasis>ad hoc</emphasis> model which is suitable to relatively "
-"unconstrained, freeform navigation where the user decides where he/she wants "
-"to go next, not the application."
+msgid "In addition, the stateful model is more <emphasis>constrained</emphasis>. For each logical state (each step in the page flow), there are a constrained set of possible transitions to other states. The stateless model is an <emphasis>ad hoc</emphasis> model which is suitable to relatively unconstrained, freeform navigation where the user decides where he/she wants to go next, not the application."
msgstr ""
#. Tag: para
#: 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."
+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 ""
#. Tag: para
#: Jbpm.xml:191
#, no-c-format
-msgid ""
-"The biggest contrast between the two models is the back-button behavior."
+msgid "The biggest contrast between the two models is the back-button behavior."
msgstr ""
#. Tag: title
@@ -357,30 +358,13 @@
#. Tag: para
#: 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."
+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 ""
#. Tag: para
#: 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:"
+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 ""
#. Tag: programlisting
@@ -390,22 +374,13 @@
"<![CDATA[<page view-id=\"/checkout.xhtml\" \n"
" no-conversation-view-id=\"/main.xhtml\"/>]]>"
msgstr ""
+"<![CDATA[<page view-id=\"/checkout.xhtml\" \n"
+" no-conversation-view-id=\"/main.xhtml\"/>]]>"
#. Tag: para
#: 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>."
+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 ""
#. Tag: programlisting
@@ -420,23 +395,24 @@
" <transition name=\"complete\" to=\"complete\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"checkout\" \n"
+" view-id=\"/checkout.xhtml\" \n"
+" back=\"enabled\">\n"
+" <redirect/>\n"
+" <transition to=\"checkout\"/>\n"
+" <transition name=\"complete\" to=\"complete\"/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:247
#, no-c-format
-msgid ""
-"This allows backbuttoning <emphasis>from</emphasis> the <literal>checkout</"
-"literal> state to <emphasis>any previous state!</emphasis>"
+msgid "This allows backbuttoning <emphasis>from</emphasis> the <literal>checkout</literal> state to <emphasis>any previous state!</emphasis>"
msgstr ""
#. Tag: para
#: 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:"
+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 ""
#. Tag: programlisting
@@ -452,13 +428,19 @@
" <transition name=\"complete\" to=\"complete\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"checkout\" \n"
+" view-id=\"/checkout.xhtml\" \n"
+" back=\"enabled\" \n"
+" no-conversation-view-id=\"/main.xhtml\">\n"
+" <redirect/>\n"
+" <transition to=\"checkout\"/>\n"
+" <transition name=\"complete\" to=\"complete\"/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:264
#, no-c-format
-msgid ""
-"In practice, both navigation models have their place, and you'll quickly "
-"learn to recognize when to prefer one model over the other."
+msgid "In practice, both navigation models have their place, and you'll quickly learn to recognize when to prefer one model over the other."
msgstr ""
#. Tag: title
@@ -476,25 +458,19 @@
#. Tag: para
#: 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):"
+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 ""
#. Tag: programlisting
#: Jbpm.xml:285
#, no-c-format
msgid "<![CDATA[<bpm:jbpm />]]>"
-msgstr ""
+msgstr "<![CDATA[<bpm:jbpm />]]>"
#. Tag: para
#: 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>:"
+msgid "We can also explicitly tell Seam where to find our pageflow definition. We specify this in <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -507,6 +483,11 @@
" </bpm:pageflow-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:pageflow-definitions>\n"
+" <value>pageflow.jpdl.xml</value>\n"
+" </bpm:pageflow-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: title
#: Jbpm.xml:297
@@ -517,10 +498,7 @@
#. Tag: para
#: Jbpm.xml:299
#, no-c-format
-msgid ""
-"We \"start\" a jPDL-based pageflow by specifying the name of the process "
-"definition using a <literal>@Begin</literal>, <literal>@BeginTask</literal> "
-"or <literal>@StartTask</literal> annotation:"
+msgid "We \"start\" a jPDL-based pageflow by specifying the name of the process definition using a <literal>@Begin</literal>, <literal>@BeginTask</literal> or <literal>@StartTask</literal> annotation:"
msgstr ""
#. Tag: programlisting
@@ -530,6 +508,8 @@
"<![CDATA[@Begin(pageflow=\"numberguess\")\n"
"public void begin() { ... }]]>"
msgstr ""
+"<![CDATA[@Begin(pageflow=\"numberguess\")\n"
+"public void begin() { ... }]]>"
#. Tag: para
#: Jbpm.xml:308
@@ -545,28 +525,20 @@
" <begin-conversation pageflow=\"numberguess\"/>\n"
" </page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <begin-conversation pageflow=\"numberguess\"/>\n"
+" </page>]]>"
#. Tag: para
#: Jbpm.xml:312
#, no-c-format
-msgid ""
-"If we are beginning the pageflow during the <literal>RENDER_RESPONSE</"
-"literal> phase—during a <literal>@Factory</literal> or "
-"<literal>@Create</literal> method, for example—we consider ourselves "
-"to be already at the page being rendered, and use a <literal><start-"
-"page></literal> node as the first node in the pageflow, as in the example "
-"above."
+msgid "If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal> phase—during a <literal>@Factory</literal> or <literal>@Create</literal> method, for example—we consider ourselves to be already at the page being rendered, and use a <literal><start-page></literal> node as the first node in the pageflow, as in the example above."
msgstr ""
#. Tag: para
#: Jbpm.xml:320
#, no-c-format
-msgid ""
-"But if the pageflow is begun as the result of an action listener invocation, "
-"the outcome of the action listener determines which is the first page to be "
-"rendered. In this case, we use a <literal><start-state></literal> as "
-"the first node in the pageflow, and declare a transition for each possible "
-"outcome:"
+msgid "But if the pageflow is begun as the result of an action listener invocation, the outcome of the action listener determines which is the first page to be rendered. In this case, we use a <literal><start-state></literal> as the first node in the pageflow, and declare a transition for each possible outcome:"
msgstr ""
#. Tag: programlisting
@@ -593,6 +565,25 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<pageflow-definition name=\"viewEditDocument\">\n"
+"\n"
+" <start-state name=\"start\">\n"
+" <transition name=\"documentFound\" to=\"displayDocument\"/>\n"
+" <transition name=\"documentNotFound\" to=\"notFound\"/>\n"
+" </start-state>\n"
+" \n"
+" <page name=\"displayDocument\" view-id=\"/document.jsp\">\n"
+" <transition name=\"edit\" to=\"editDocument\"/>\n"
+" <transition name=\"done\" to=\"main\"/>\n"
+" </page>\n"
+" \n"
+" ...\n"
+" \n"
+" <page name=\"notFound\" view-id=\"/404.jsp\">\n"
+" <end-conversation/>\n"
+" </page>\n"
+" \n"
+"</pageflow-definition>]]>"
#. Tag: title
#: Jbpm.xml:333
@@ -603,9 +594,7 @@
#. Tag: para
#: Jbpm.xml:335
#, no-c-format
-msgid ""
-"Each <literal><page></literal> node represents a state where the "
-"system is waiting for user input:"
+msgid "Each <literal><page></literal> node represents a state where the system is waiting for user input:"
msgstr ""
#. Tag: programlisting
@@ -619,65 +608,48 @@
" </transition>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <redirect/>\n"
+" <transition name=\"guess\" to=\"evaluateGuess\">\n"
+" <action expression=\"#{numberGuess.guess}\" />\n"
+" </transition>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:342
#, no-c-format
-msgid ""
-"The <literal>view-id</literal> is the JSF view id. The <literal><redirect/"
-"></literal> element has the same effect as <literal><redirect/></"
-"literal> in a JSF navigation rule: namely, a post-then-redirect behavior, to "
-"overcome problems with the browser's refresh button. (Note that Seam "
-"propagates conversation contexts over these browser redirects. So there is "
-"no need for a Ruby on Rails style \"flash\" construct in Seam!)"
+msgid "The <literal>view-id</literal> is the JSF view id. The <literal><redirect/></literal> element has the same effect as <literal><redirect/></literal> in a JSF navigation rule: namely, a post-then-redirect behavior, to overcome problems with the browser's refresh button. (Note that Seam propagates conversation contexts over these browser redirects. So there is no need for a Ruby on Rails style \"flash\" construct in Seam!)"
msgstr ""
#. Tag: para
#: 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>."
+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 ""
#. Tag: programlisting
#: Jbpm.xml:356
#, no-c-format
-msgid ""
-"<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"guess\"/"
-">]]>"
-msgstr ""
+msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"guess\"/>]]>"
+msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"guess\"/>]]>"
#. Tag: para
#: Jbpm.xml:358
#, no-c-format
-msgid ""
-"When the transition is triggered by clicking this button, jBPM will activate "
-"the transition action by calling the <literal>guess()</literal> method of "
-"the <literal>numberGuess</literal> component. Notice that the syntax used "
-"for specifying actions in the jPDL is just a familiar JSF EL expression, and "
-"that the transition action handler is just a method of a Seam component in "
-"the current Seam contexts. So we have exactly the same event model for jBPM "
-"events that we already have for JSF events! (The <emphasis>One Kind of "
-"Stuff</emphasis> principle.)"
+msgid "When the transition is triggered by clicking this button, jBPM will activate the transition action by calling the <literal>guess()</literal> method of the <literal>numberGuess</literal> component. Notice that the syntax used for specifying actions in the jPDL is just a familiar JSF EL expression, and that the transition action handler is just a method of a Seam component in the current Seam contexts. So we have exactly the same event model for jBPM events that we already have for JSF events! (The <emphasis>One Kind of Stuff</emphasis> principle.)"
msgstr ""
#. Tag: para
#: Jbpm.xml:369
#, no-c-format
-msgid ""
-"In the case of a null outcome (for example, a command button with no "
-"<literal>action</literal> defined), Seam will signal the transition with no "
-"name if one exists, or else simply redisplay the page if all transitions "
-"have names. So we could slightly simplify our example pageflow and this "
-"button:"
+msgid "In the case of a null outcome (for example, a command button with no <literal>action</literal> defined), Seam will signal the transition with no name if one exists, or else simply redisplay the page if all transitions have names. So we could slightly simplify our example pageflow and this button:"
msgstr ""
#. Tag: programlisting
#: Jbpm.xml:376
#, no-c-format
msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\"/>]]>"
#. Tag: para
#: Jbpm.xml:378
@@ -696,22 +668,24 @@
" </transition>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <redirect/>\n"
+" <transition to=\"evaluateGuess\">\n"
+" <action expression=\"#{numberGuess.guess}\" />\n"
+" </transition>\n"
+"</page>]]>"
#. Tag: para
#: 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:"
+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 ""
#. Tag: programlisting
#: Jbpm.xml:389
#, no-c-format
-msgid ""
-"<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"#"
-"{numberGuess.guess}\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"#{numberGuess.guess}\"/>]]>"
+msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\" action=\"#{numberGuess.guess}\"/>]]>"
#. Tag: programlisting
#: Jbpm.xml:391
@@ -722,15 +696,15 @@
" <transition name=\"incorrectGuess\" to=\"evaluateGuess\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"displayGuess\" view-id=\"/numberGuess.jsp\">\n"
+" <transition name=\"correctGuess\" to=\"win\"/>\n"
+" <transition name=\"incorrectGuess\" to=\"evaluateGuess\"/>\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:393
#, no-c-format
-msgid ""
-"However, this is considered an inferior style, since it moves responsibility "
-"for controlling the flow out of the pageflow definition and back into the "
-"other components. It is much better to centralize this concern in the "
-"pageflow itself."
+msgid "However, this is considered an inferior style, since it moves responsibility for controlling the flow out of the pageflow definition and back into the other components. It is much better to centralize this concern in the pageflow itself."
msgstr ""
#. Tag: title
@@ -742,27 +716,27 @@
#. Tag: para
#: Jbpm.xml:404
#, no-c-format
-msgid ""
-"Usually, we don't need the more powerful features of jPDL when defining "
-"pageflows. We do need the <literal><decision></literal> node, however:"
+msgid "Usually, we don't need the more powerful features of jPDL when defining pageflows. We do need the <literal><decision></literal> node, however:"
msgstr ""
#. Tag: programlisting
#: Jbpm.xml:409
#, no-c-format
msgid ""
-"<![CDATA[<decision name=\"evaluateGuess\" expression=\"#{numberGuess."
-"correctGuess}\">\n"
+"<![CDATA[<decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
" <transition name=\"true\" to=\"win\"/>\n"
" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
"</decision>]]>"
msgstr ""
+"<![CDATA[<decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
+" <transition name=\"true\" to=\"win\"/>\n"
+" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
+"</decision>]]>"
#. Tag: para
#: Jbpm.xml:411
#, no-c-format
-msgid ""
-"A decision is made by evaluating a JSF EL expression in the Seam contexts."
+msgid "A decision is made by evaluating a JSF EL expression in the Seam contexts."
msgstr ""
#. Tag: title
@@ -774,10 +748,7 @@
#. Tag: para
#: Jbpm.xml:420
#, no-c-format
-msgid ""
-"We end the conversation using <literal><end-conversation></literal> or "
-"<literal>@End</literal>. (In fact, for readability, use of <emphasis>both</"
-"emphasis> is encouraged.)"
+msgid "We end the conversation using <literal><end-conversation></literal> or <literal>@End</literal>. (In fact, for readability, use of <emphasis>both</emphasis> is encouraged.)"
msgstr ""
#. Tag: programlisting
@@ -789,14 +760,15 @@
" <end-conversation/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"win\" view-id=\"/win.jsp\">\n"
+" <redirect/>\n"
+" <end-conversation/>\n"
+"</page>]]>"
#. Tag: para
#: 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."
+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 ""
#. Tag: programlisting
@@ -808,6 +780,10 @@
" <end-task transition=\"success\"/>\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page name=\"win\" view-id=\"/win.jsp\">\n"
+" <redirect/>\n"
+" <end-task transition=\"success\"/>\n"
+"</page>]]>"
#. Tag: title
#: Jbpm.xml:439
@@ -818,10 +794,7 @@
#. Tag: para
#: Jbpm.xml:440
#, no-c-format
-msgid ""
-"It is possible to compose pageflows and have one pageflow pause pause while "
-"another pageflow executes. The <literal><process-state></literal> node "
-"pauses the outer pageflow, and begins execution of a named pageflow:"
+msgid "It is possible to compose pageflows and have one pageflow pause pause while another pageflow executes. The <literal><process-state></literal> node pauses the outer pageflow, and begins execution of a named pageflow:"
msgstr ""
#. Tag: programlisting
@@ -833,16 +806,15 @@
" <transition to=\"displayGuess\"/>\n"
"</process-state>]]>"
msgstr ""
+"<![CDATA[<process-state name=\"cheat\">\n"
+" <sub-process name=\"cheat\"/>\n"
+" <transition to=\"displayGuess\"/>\n"
+"</process-state>]]>"
#. Tag: para
#: Jbpm.xml:449
#, no-c-format
-msgid ""
-"The inner flow begins executing at a <literal><start-state></literal> "
-"node. When it reaches an <literal><end-state></literal> node, "
-"execution of the inner flow ends, and execution of the outer flow resumes "
-"with the transition defined by the <literal><process-state></literal> "
-"element."
+msgid "The inner flow begins executing at a <literal><start-state></literal> node. When it reaches an <literal><end-state></literal> node, execution of the inner flow ends, and execution of the outer flow resumes with the transition defined by the <literal><process-state></literal> element."
msgstr ""
#. Tag: title
@@ -854,26 +826,13 @@
#. Tag: para
#: Jbpm.xml:463
#, no-c-format
-msgid ""
-"A business process is a well-defined set of tasks that must be performed by "
-"users or software systems according to well-defined rules about "
-"<emphasis>who</emphasis> can perform a task, and <emphasis>when</emphasis> "
-"it should be performed. Seam's jBPM integration makes it easy to display "
-"lists of tasks to users and let them manage their tasks. Seam also lets the "
-"application store state associated with the business process in the "
-"<literal>BUSINESS_PROCESS</literal> context, and have that state made "
-"persistent via jBPM variables."
+msgid "A business process is a well-defined set of tasks that must be performed by users or software systems according to well-defined rules about <emphasis>who</emphasis> can perform a task, and <emphasis>when</emphasis> it should be performed. Seam's jBPM integration makes it easy to display lists of tasks to users and let them manage their tasks. Seam also lets the application store state associated with the business process in the <literal>BUSINESS_PROCESS</literal> context, and have that state made persistent via jBPM variables."
msgstr ""
#. Tag: para
#: Jbpm.xml:475
#, no-c-format
-msgid ""
-"A simple business process definition looks much the same as a page flow "
-"definition (<emphasis>One Kind of Stuff</emphasis>), except that instead of "
-"<literal><page></literal> nodes, we have <literal><task-node></"
-"literal> nodes. In a long-running business process, the wait states are "
-"where the system is waiting for some user to log in and perform a task."
+msgid "A simple business process definition looks much the same as a page flow definition (<emphasis>One Kind of Stuff</emphasis>), except that instead of <literal><page></literal> nodes, we have <literal><task-node></literal> nodes. In a long-running business process, the wait states are where the system is waiting for some user to log in and perform a task."
msgstr ""
#. Tag: programlisting
@@ -897,16 +856,27 @@
" \n"
"</process-definition>]]>"
msgstr ""
+"<![CDATA[<process-definition name=\"todo\">\n"
+" \n"
+" <start-state name=\"start\">\n"
+" <transition to=\"todo\"/>\n"
+" </start-state>\n"
+" \n"
+" <task-node name=\"todo\">\n"
+" <task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment actor-id=\"#{actor.id}\"/>\n"
+" </task>\n"
+" <transition to=\"done\"/>\n"
+" </task-node>\n"
+" \n"
+" <end-state name=\"done\"/>\n"
+" \n"
+"</process-definition>]]>"
#. Tag: para
#: Jbpm.xml:496
#, no-c-format
-msgid ""
-"It is perfectly possible that we might have both jPDL business process "
-"definitions and jPDL pageflow definitions in the same project. If so, the "
-"relationship between the two is that a single <literal><task></"
-"literal> in a business process corresponds to a whole pageflow <literal><"
-"pageflow-definition></literal>"
+msgid "It is perfectly possible that we might have both jPDL business process definitions and jPDL pageflow definitions in the same project. If so, the relationship between the two is that a single <literal><task></literal> in a business process corresponds to a whole pageflow <literal><pageflow-definition></literal>"
msgstr ""
#. Tag: title
@@ -919,14 +889,12 @@
#: Jbpm.xml:510
#, no-c-format
msgid "Installing process definitions"
-msgstr ""
+msgstr "Installazione delle definizioni di processo"
#. Tag: para
#: Jbpm.xml:512
#, no-c-format
-msgid ""
-"We need to install jBPM, and tell it where to find the business process "
-"definitions:"
+msgid "We need to install jBPM, and tell it where to find the business process definitions:"
msgstr ""
#. Tag: programlisting
@@ -939,17 +907,16 @@
" </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:process-definitions>\n"
+" <value>todo.jpdl.xml</value>\n"
+" </bpm:process-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: para
#: Jbpm.xml:519
#, no-c-format
-msgid ""
-"As jBPM processes are persistent across application restarts, when using "
-"Seam in a production environment you won't want to install the process "
-"definition every time the application starts. Therefore, in a production "
-"environment, you'll need to deploy the process to jBPM outside of Seam. In "
-"other words, only install process definitions from <literal>components.xml</"
-"literal> when developing your application."
+msgid "As jBPM processes are persistent across application restarts, when using Seam in a production environment you won't want to install the process definition every time the application starts. Therefore, in a production environment, you'll need to deploy the process to jBPM outside of Seam. In other words, only install process definitions from <literal>components.xml</literal> when developing your application."
msgstr ""
#. Tag: title
@@ -961,11 +928,7 @@
#. Tag: para
#: 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>:"
+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 ""
#. Tag: programlisting
@@ -981,6 +944,14 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[@In Actor actor;\n"
+"\n"
+"public String login() {\n"
+" ...\n"
+" actor.setId( user.getUserName() );\n"
+" actor.getGroupActorIds().addAll( user.getGroupNames() );\n"
+" ...\n"
+"}]]>"
#. Tag: title
#: Jbpm.xml:547
@@ -991,9 +962,7 @@
#. Tag: para
#: Jbpm.xml:549
#, no-c-format
-msgid ""
-"To initiate a business process instance, we use the <literal>@CreateProcess</"
-"literal> annotation:"
+msgid "To initiate a business process instance, we use the <literal>@CreateProcess</literal> annotation:"
msgstr ""
#. Tag: programlisting
@@ -1003,6 +972,8 @@
"<![CDATA[@CreateProcess(definition=\"todo\")\n"
"public void createTodo() { ... }]]>"
msgstr ""
+"<![CDATA[@CreateProcess(definition=\"todo\")\n"
+"public void createTodo() { ... }]]>"
#. Tag: para
#: Jbpm.xml:556
@@ -1018,20 +989,20 @@
" <create-process definition=\"todo\" />\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <create-process definition=\"todo\" />\n"
+"</page>]]>"
#. Tag: title
#: Jbpm.xml:563
#, no-c-format
msgid "Task assignment"
-msgstr ""
+msgstr "Assegnazione task"
#. Tag: para
#: 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:"
+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 ""
#. Tag: programlisting
@@ -1042,13 +1013,14 @@
" <assignment actor-id=\"#{actor.id}\"/>\n"
"</task>]]>"
msgstr ""
+"<![CDATA[<task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment actor-id=\"#{actor.id}\"/>\n"
+"</task>]]>"
#. 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:"
+msgid "In this case, we have simply assigned the task to the current user. We can also assign tasks to a pool:"
msgstr ""
#. Tag: programlisting
@@ -1059,20 +1031,20 @@
" <assignment pooled-actors=\"employees\"/>\n"
"</task>]]>"
msgstr ""
+"<![CDATA[<task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment pooled-actors=\"employees\"/>\n"
+"</task>]]>"
#. Tag: title
#: Jbpm.xml:583
#, no-c-format
msgid "Task lists"
-msgstr ""
+msgstr "Liste di 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:"
+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 ""
#. Tag: programlisting
@@ -1085,18 +1057,24 @@
" <h:outputText value=\"#{task.description}\"/>\n"
" </h:column>\n"
" <h:column>\n"
-" <s:link action=\"#{pooledTask.assignToCurrentActor}\" value=\"Assign"
-"\" taskInstance=\"#{task}\"/>\n"
+" <s:link action=\"#{pooledTask.assignToCurrentActor}\" value=\"Assign\" taskInstance=\"#{task}\"/>\n"
" </h:column> \n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{pooledTaskInstanceList}\" var=\"task\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Description</f:facet>\n"
+" <h:outputText value=\"#{task.description}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <s:link action=\"#{pooledTask.assignToCurrentActor}\" value=\"Assign\" taskInstance=\"#{task}\"/>\n"
+" </h:column> \n"
+"</h:dataTable>]]>"
#. Tag: para
#: 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>:"
+msgid "Note that instead of <literal><s:link></literal> we could have used a plain JSF <literal><h:commandLink></literal>:"
msgstr ""
#. Tag: programlisting
@@ -1107,52 +1085,56 @@
" <f:param name=\"taskId\" value=\"#{task.id}\"/>\n"
"</h:commandLink>]]>"
msgstr ""
+"<![CDATA[<h:commandLink action=\"#{pooledTask.assignToCurrentActor}\"> \n"
+" <f:param name=\"taskId\" value=\"#{task.id}\"/>\n"
+"</h:commandLink>]]>"
#. Tag: para
#: 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."
+msgid "The <literal>pooledTask</literal> component is a built-in component that simply assigns the task to the current user."
msgstr ""
#. 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:"
+msgid "The <literal>taskInstanceListForType</literal> component includes tasks of a particular type that are assigned to the current user:"
msgstr ""
#. Tag: programlisting
#: Jbpm.xml:610
#, no-c-format
msgid ""
-"<![CDATA[<h:dataTable value=\"#{taskInstanceListForType['todo']}\" var=\"task"
-"\">\n"
+"<![CDATA[<h:dataTable value=\"#{taskInstanceListForType['todo']}\" var=\"task\">\n"
" <h:column>\n"
" <f:facet name=\"header\">Description</f:facet>\n"
" <h:outputText value=\"#{task.description}\"/>\n"
" </h:column>\n"
" <h:column>\n"
-" <s:link action=\"#{todoList.start}\" value=\"Start Work\" "
-"taskInstance=\"#{task}\"/>\n"
+" <s:link action=\"#{todoList.start}\" value=\"Start Work\" taskInstance=\"#{task}\"/>\n"
" </h:column> \n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{taskInstanceListForType['todo']}\" var=\"task\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Description</f:facet>\n"
+" <h:outputText value=\"#{task.description}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <s:link action=\"#{todoList.start}\" value=\"Start Work\" taskInstance=\"#{task}\"/>\n"
+" </h:column> \n"
+"</h:dataTable>]]>"
#. Tag: title
#: Jbpm.xml:615
#, no-c-format
msgid "Performing a task"
-msgstr ""
+msgstr "Esecuzione di un task"
#. Tag: para
#: 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:"
+msgid "To begin work on a task, we use either <literal>@StartTask</literal> or <literal>@BeginTask</literal> on the listener method:"
msgstr ""
#. Tag: programlisting
@@ -1162,6 +1144,8 @@
"<![CDATA[@StartTask\n"
"public String start() { ... }]]>"
msgstr ""
+"<![CDATA[@StartTask\n"
+"public String start() { ... }]]>"
#. Tag: para
#: Jbpm.xml:624
@@ -1177,22 +1161,20 @@
" <start-task />\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <start-task />\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:628
#, no-c-format
-msgid ""
-"These annotations begin a special kind of conversation that has significance "
-"in terms of the overarching business process. Work done by this conversation "
-"has access to state held in the business process context."
+msgid "These annotations begin a special kind of conversation that has significance in terms of the overarching business process. Work done by this conversation has access to state held in the business process context."
msgstr ""
#. Tag: para
#: Jbpm.xml:635
#, no-c-format
-msgid ""
-"If we end the conversation using <literal>@EndTask</literal>, Seam will "
-"signal the completion of the task:"
+msgid "If we end the conversation using <literal>@EndTask</literal>, Seam will signal the completion of the task:"
msgstr ""
#. Tag: programlisting
@@ -1202,6 +1184,8 @@
"<![CDATA[@EndTask(transition=\"completed\")\n"
"public String completed() { ... }]]>"
msgstr ""
+"<![CDATA[@EndTask(transition=\"completed\")\n"
+"public String completed() { ... }]]>"
#. Tag: para
#: Jbpm.xml:642
@@ -1217,6 +1201,9 @@
" <end-task transition=\"completed\" />\n"
"</page>]]>"
msgstr ""
+"<![CDATA[<page>\n"
+" <end-task transition=\"completed\" />\n"
+"</page>]]>"
#. Tag: para
#: Jbpm.xml:646
@@ -1227,17 +1214,12 @@
#. Tag: para
#: Jbpm.xml:650
#, no-c-format
-msgid ""
-"At this point, jBPM takes over and continues executing the business process "
-"definition. (In more complex processes, several tasks might need to be "
-"completed before process execution can resume.)"
+msgid "At this point, jBPM takes over and continues executing the business process definition. (In more complex processes, several tasks might need to be completed before process execution can resume.)"
msgstr ""
#. Tag: para
#: Jbpm.xml:656
#, no-c-format
-msgid ""
-"Please refer to the jBPM documentation for a more thorough overview of the "
-"sophisticated features that jBPM provides for managing complex business "
-"processes."
+msgid "Please refer to the jBPM documentation for a more thorough overview of the sophisticated features that jBPM provides for managing complex business processes."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-09 21:00+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,414 +17,247 @@
#: Preface.xml:7
#, no-c-format
msgid "Introduction to JBoss Seam"
-msgstr ""
+msgstr "Introduzione a JBoss Seam"
#. Tag: para
#: Preface.xml:9
#, no-c-format
-msgid ""
-"Seam is an application framework for Enterprise Java. It is inspired by the "
-"following principles:"
-msgstr ""
+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:"
#. Tag: emphasis
#: Preface.xml:16
#, no-c-format
msgid "One kind of \"stuff\""
-msgstr ""
+msgstr "Unico tipo di \"cosa\""
#. Tag: para
#: Preface.xml:18
#, no-c-format
-msgid ""
-"Seam defines a uniform component model for all business logic in your "
-"application. A Seam component may be stateful, with the state associated "
-"with any one of several well-defined contexts, including the long-running, "
-"persistent, <emphasis>business process context</emphasis> and the "
-"<emphasis>conversation context</emphasis>, which is preserved across "
-"multiple web requests in a user interaction."
-msgstr ""
+msgid "Seam defines a uniform component model for all business logic in your application. A Seam component may be stateful, with the state associated with any one of several well-defined contexts, including the long-running, persistent, <emphasis>business process context</emphasis> and the <emphasis>conversation context</emphasis>, which is preserved across multiple web requests in a user interaction."
+msgstr "Seam definisce un modello uniforme a componenti per tutte le business logic nella tua applicazione. Un componente Seam può essere stateful, con uno stato associato ad uno dei tanti contesti ben-definiti, che includono long-running, persistenza, <emphasis>contesto processo di business</emphasis> e il <emphasis>contesto conversazionale</emphasis>, che viene preservato lungo le richieste web multiple nell'interazione con l'utente."
#. Tag: para
#: Preface.xml:25
#, no-c-format
-msgid ""
-"There is no distinction between presentation tier components and business "
-"logic components in Seam. You can layer your application according to "
-"whatever architecture you devise, rather than being forced to shoehorn your "
-"application logic into an unnatural layering scheme forced upon you by "
-"whatever combination of stovepipe frameworks you're using today."
-msgstr ""
+msgid "There is no distinction between presentation tier components and business logic components in Seam. You can layer your application according to whatever architecture you devise, rather than being forced to shoehorn your application logic into an unnatural layering scheme forced upon you by whatever combination of stovepipe frameworks you're using today."
+msgstr "Non c'è alcuna distinzione in Seam tra i componenti del livello presentazione ed i componenti di business logic. Puoi stratificare la tua applicazione secondo una qualsiasi architettura a tuo piacimento, piuttosto che essere forzato a modellare la logica dell'applicazione in uno schema innaturale con una qualsiasi combinazione di framework aggrovigliati che stai usando oggi."
#. Tag: para
#: Preface.xml:32
#, no-c-format
-msgid ""
-"Unlike plain Java EE or J2EE components, Seam components may "
-"<emphasis>simultaneously</emphasis> access state associated with the web "
-"request and state held in transactional resources (without the need to "
-"propagate web request state manually via method parameters). You might "
-"object that the application layering imposed upon you by the old J2EE "
-"platform was a Good Thing. Well, nothing stops you creating an equivalent "
-"layered architecture using Seam—the difference is that <emphasis>you</"
-"emphasis> get to architect your own application and decide what the layers "
-"are and how they work together."
+msgid "Unlike plain Java EE or J2EE components, Seam components may <emphasis>simultaneously</emphasis> access state associated with the web request and state held in transactional resources (without the need to propagate web request state manually via method parameters). You might object that the application layering imposed upon you by the old J2EE platform was a Good Thing. Well, nothing stops you creating an equivalent layered architecture using Seam—the difference is that <emphasis>you</emphasis> get to architect your own application and decide what the layers are and how they work together."
msgstr ""
#. Tag: emphasis
#: Preface.xml:45
#, no-c-format
msgid "Integrate JSF with EJB 3.0"
-msgstr ""
+msgstr "Integrazione di JSF con EJB 3.0"
#. Tag: para
#: Preface.xml:47
#, no-c-format
-msgid ""
-"JSF and EJB 3.0 are two of the best new features of Java EE 5. EJB3 is a "
-"brand new component model for server side business and persistence logic. "
-"Meanwhile, JSF is a great component model for the presentation tier. "
-"Unfortunately, neither component model is able to solve all problems in "
-"computing by itself. Indeed, JSF and EJB3 work best used together. But the "
-"Java EE 5 specification provides no standard way to integrate the two "
-"component models. Fortunately, the creators of both models foresaw this "
-"situation and provided standard extension points to allow extension and "
-"integration with other frameworks."
+msgid "JSF and EJB 3.0 are two of the best new features of Java EE 5. EJB3 is a brand new component model for server side business and persistence logic. Meanwhile, JSF is a great component model for the presentation tier. Unfortunately, neither component model is able to solve all problems in computing by itself. Indeed, JSF and EJB3 work best used together. But the Java EE 5 specification provides no standard way to integrate the two component models. Fortunately, the creators of both models foresaw this situation and provided standard extension points to allow extension and integration with other frameworks."
msgstr ""
#. Tag: para
#: Preface.xml:57
#, no-c-format
-msgid ""
-"Seam unifies the component models of JSF and EJB3, eliminating glue code, "
-"and letting the developer think about the business problem."
-msgstr ""
+msgid "Seam unifies the component models of JSF and EJB3, eliminating glue code, and letting the developer think about the business problem."
+msgstr "Seam unifica i modelli a componenti di JSF e EJB3, eliminando il codice colla, e consentendo allo sciluppatore di pensare al problema di business."
#. Tag: para
#: Preface.xml:61
#, no-c-format
-msgid ""
-"It is possible to write Seam applications where \"everything\" is an EJB. "
-"This may come as a surprise if you're used to thinking of EJBs as coarse-"
-"grained, so-called \"heavyweight\" objects. However, version 3.0 has "
-"completely changed the nature of EJB from the point of view of the "
-"developer. An EJB is a fine-grained object—nothing more complex than "
-"an annotated JavaBean. Seam even encourages you to use session beans as JSF "
-"action listeners!"
+msgid "It is possible to write Seam applications where \"everything\" is an EJB. This may come as a surprise if you're used to thinking of EJBs as coarse-grained, so-called \"heavyweight\" objects. However, version 3.0 has completely changed the nature of EJB from the point of view of the developer. An EJB is a fine-grained object—nothing more complex than an annotated JavaBean. Seam even encourages you to use session beans as JSF action listeners!"
msgstr ""
#. Tag: para
#: Preface.xml:69
#, no-c-format
-msgid ""
-"On the other hand, if you prefer not to adopt EJB 3.0 at this time, you "
-"don't have to. Virtually any Java class may be a Seam component, and Seam "
-"provides all the functionality that you expect from a \"lightweight\" "
-"container, and more, for any component, EJB or otherwise."
-msgstr ""
+msgid "On the other hand, if you prefer not to adopt EJB 3.0 at this time, you don't have to. Virtually any Java class may be a Seam component, and Seam provides all the functionality that you expect from a \"lightweight\" container, and more, for any component, EJB or otherwise."
+msgstr "Dall'altro lato, se preferisci non adottare EJB 3.0 adesso, puoi non farlo. Virtualmente ogni classe java può essere un componente Seam, e Seam fornisce tutte le funzionalità che ci si attende da un \"lightweight\" container, ed in più, per ogni componente, EJB o altro."
#. Tag: emphasis
#: Preface.xml:79
#, no-c-format
msgid "Integrated AJAX"
-msgstr ""
+msgstr "AJAX integrato"
#. Tag: para
#: Preface.xml:81
#, no-c-format
-msgid ""
-"Seam supports the best open source JSF-based AJAX solutions: JBoss RichFaces "
-"and ICEfaces. These solutions let you add AJAX capability to your user "
-"interface without the need to write any JavaScript code."
-msgstr ""
+msgid "Seam supports the best open source JSF-based AJAX solutions: JBoss RichFaces and ICEfaces. These solutions let you add AJAX capability to your user interface without the need to write any JavaScript code."
+msgstr "Seam supporta le migliori soluzioni open source AJAX basate su JSF: JBoss RichFaces a ICEFaces. Queste soluzioni ti permettono di aggiungere funzionalità AJAX alla tua interfaccia utente senza il bisogno di scrivere codice JavaScript."
#. Tag: para
#: Preface.xml:86
#, no-c-format
-msgid ""
-"Alternatively, Seam provides a built-in JavaScript remoting layer that lets "
-"you call components asynchronously from client-side JavaScript without the "
-"need for an intermediate action layer. You can even subscribe to server-side "
-"JMS topics and receive messages via AJAX push."
-msgstr ""
+msgid "Alternatively, Seam provides a built-in JavaScript remoting layer that lets you call components asynchronously from client-side JavaScript without the need for an intermediate action layer. You can even subscribe to server-side JMS topics and receive messages via AJAX push."
+msgstr "In alternativa Seam fornisce al suo interno uno strato remoto di JavaScript che ti consente di chiamare i componenti in modo asincrono da JavaScript lato client senza il bisogno di uno strato di azione intermedio. Puoi anche sottoscrivere topic JMS lato server e ricevere messaggi tramite push AJAX."
#. Tag: para
#: Preface.xml:92
#, no-c-format
-msgid ""
-"Neither of these approaches would work well, were it not for Seam's built-in "
-"concurrency and state management, which ensures that many concurrent fine-"
-"grained, asynchronous AJAX requests are handled safely and efficiently on "
-"the server side."
+msgid "Neither of these approaches would work well, were it not for Seam's built-in concurrency and state management, which ensures that many concurrent fine-grained, asynchronous AJAX requests are handled safely and efficiently on the server side."
msgstr ""
+# da rivedere FIRST CLASS CONSTRUCT
#. Tag: emphasis
#: Preface.xml:101
#, no-c-format
msgid "Business process as a first class construct"
-msgstr ""
+msgstr "Processo di business come primo costrutto di classe"
#. Tag: para
#: 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 ""
+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 di processo di business tramire jBPM. Non ci crederai quanto è facile implementare workflow complessi, collaborazioni e gestione dei compiti utilizzando jBPM e Seam."
#. Tag: para
#: Preface.xml:108
#, no-c-format
-msgid ""
-"Seam even allows you to define presentation tier pageflow using the same "
-"language (jPDL) that jBPM uses for business process definition."
-msgstr ""
+msgid "Seam even allows you to define presentation tier pageflow using the same language (jPDL) that jBPM uses for business process definition."
+msgstr "Seam consente pure di definire il pageflow del livello di presentazione utilizzando lo stesso linguaggio (jPDL) che jBPM utilizza per la definizione dei processi di business."
#. Tag: para
#: Preface.xml:112
#, no-c-format
-msgid ""
-"JSF provides an incredibly rich event model for the presentation tier. Seam "
-"enhances this model by exposing jBPM's business process related events via "
-"exactly the same event handling mechanism, providing a uniform event model "
-"for Seam's uniform component model."
+msgid "JSF provides an incredibly rich event model for the presentation tier. Seam enhances this model by exposing jBPM's business process related events via exactly the same event handling mechanism, providing a uniform event model for Seam's uniform component model."
msgstr ""
#. Tag: emphasis
#: Preface.xml:121
#, no-c-format
msgid "Declarative state management"
-msgstr ""
+msgstr "Gestione dichiarativa dello stato"
+# memory leaks ???
#. Tag: para
#: Preface.xml:123
#, no-c-format
-msgid ""
-"We're all used to the concept of declarative transaction management and "
-"declarative security from the early days of EJB. EJB 3.0 even introduces "
-"declarative persistence context management. These are three examples of a "
-"broader problem of managing state that is associated with a particular "
-"<emphasis>context</emphasis>, while ensuring that all needed cleanup occurs "
-"when the context ends. Seam takes the concept of declarative state "
-"management much further and applies it to <emphasis>application state</"
-"emphasis>. Traditionally, J2EE applications implement state management "
-"manually, by getting and setting servlet session and request attributes. "
-"This approach to state management is the source of many bugs and memory "
-"leaks when applications fail to clean up session attributes, or when session "
-"data associated with different workflows collides in a multi-window "
-"application. Seam has the potential to almost entirely eliminate this class "
-"of bugs."
-msgstr ""
+msgid "We're all used to the concept of declarative transaction management and declarative security from the early days of EJB. EJB 3.0 even introduces declarative persistence context management. These are three examples of a broader problem of managing state that is associated with a particular <emphasis>context</emphasis>, while ensuring that all needed cleanup occurs when the context ends. Seam takes the concept of declarative state management much further and applies it to <emphasis>application state</emphasis>. Traditionally, J2EE applications implement state management manually, by getting and setting servlet session and request attributes. This approach to state management is the source of many bugs and memory leaks when applications fail to clean up session attributes, or when session data associated with different workflows collides in a multi-window application. Seam has the potential to almost entirely eliminate this class of bugs."
+msgstr "Siamo tutti abituati al concetto di gestione dichiarativa delle transazioni e sicurezza dichiarativa fin dai primi giorni di EJB. EJB3 introduce anche la gestione dichiarativa del contesto di persistenza. Ci sono tre esempi di un ampio problema di gestione dello stato che è associato ad un particolare <emphasis>contesto</emphasis>, mentre tutte i dovuti cleanup avvengono quando il contesto termina. Seam porta oltre il concetto di gestione dichiarativa dello stato e lo applica allo <emphasis>stato dell'applicazione</emphasis>. Tradizionalmente le applicazioni J2EE implementano manualmente la gestione dello stato con il get e set della sessione servlet e degli attributi di richiesta. Questo approccio alla gestione dello stato è l'origine di molti bug e memory leak quando l'applicazione non riesce a pulire gli attributi di sessione, o quando i dati di sessione associati a diversi workflow collidono all'interno di un'applicazione multi-finestra. Seam ha il potenziale !
per eliminare quasi interamente questa classe di bug."
#. Tag: para
#: Preface.xml:136
#, no-c-format
-msgid ""
-"Declarative application state management is made possible by the richness of "
-"the <emphasis>context model</emphasis> defined by Seam. Seam extends the "
-"context model defined by the servlet spec—request, session, "
-"application—with two new contexts—conversation and business "
-"process—that are more meaningful from the point of view of the "
-"business logic."
+msgid "Declarative application state management is made possible by the richness of the <emphasis>context model</emphasis> defined by Seam. Seam extends the context model defined by the servlet spec—request, session, application—with two new contexts—conversation and business process—that are more meaningful from the point of view of the business logic."
msgstr ""
#. Tag: para
#: Preface.xml:143
#, no-c-format
-msgid ""
-"You'll be amazed at how many things become easier once you start using "
-"conversations. Have you ever suffered pain dealing with lazy association "
-"fetching in an ORM solution like Hibernate or JPA? Seam's conversation-"
-"scoped persistence contexts mean you'll rarely have to see a "
-"<literal>LazyInitializationException</literal>. Have you ever had problems "
-"with the refresh button? The back button? With duplicate form submission? "
-"With propagating messages across a post-then-redirect? Seam's conversation "
-"management solves these problems without you even needing to really think "
-"about them. They're all symptoms of the broken state management architecture "
-"that has been prevalent since the earliest days of the web."
-msgstr ""
+msgid "You'll be amazed at how many things become easier once you start using conversations. Have you ever suffered pain dealing with lazy association fetching in an ORM solution like Hibernate or JPA? Seam's conversation-scoped persistence contexts mean you'll rarely have to see a <literal>LazyInitializationException</literal>. Have you ever had problems with the refresh button? The back button? With duplicate form submission? With propagating messages across a post-then-redirect? Seam's conversation management solves these problems without you even needing to really think about them. They're all symptoms of the broken state management architecture that has been prevalent since the earliest days of the web."
+msgstr "Resterai stupito di come molte cose divengano più semplici non appena inizia ad usare le conversazioni. Hai mai sofferto nell'utilizzo dell'associazione lazy in una soluzione ORM come Hibernate o JPA? I contesti di Seam di persistenza basati sulle conversazioni ti consentiranno di vedere raramente una <literal>LazyInitializationException</literal>. Hai mai avuto problemi con il pulsante di aggiornamento? Con il pulsante indietro? Con una form inviata due volte? Con la propagazione di messaggi attraverso un post-then-redirect? La gestione delle conversazioni di Seam risolve questi problemi senza che tu debba pensarci. Questi sono tutti sintomi di un'architettura errata di gestione dello stato che è stata prevalente fin dai primi giorni della comparsa del web."
#. Tag: emphasis
#: Preface.xml:158
#, no-c-format
msgid "Bijection"
-msgstr ""
+msgstr "Bijection"
#. Tag: para
#: Preface.xml:160
#, no-c-format
-msgid ""
-"The notion of <emphasis>Inversion of Control</emphasis> or "
-"<emphasis>dependency injection</emphasis> exists in both JSF and EJB3, as "
-"well as in numerous so-called \"lightweight containers\". Most of these "
-"containers emphasize injection of components that implement "
-"<emphasis>stateless services</emphasis>. Even when injection of stateful "
-"components is supported (such as in JSF), it is virtually useless for "
-"handling application state because the scope of the stateful component "
-"cannot be defined with sufficient flexibility, and because components "
-"belonging to wider scopes may not be injected into components belonging to "
-"narrower scopes."
+msgid "The notion of <emphasis>Inversion of Control</emphasis> or <emphasis>dependency injection</emphasis> exists in both JSF and EJB3, as well as in numerous so-called \"lightweight containers\". Most of these containers emphasize injection of components that implement <emphasis>stateless services</emphasis>. Even when injection of stateful components is supported (such as in JSF), it is virtually useless for handling application state because the scope of the stateful component cannot be defined with sufficient flexibility, and because components belonging to wider scopes may not be injected into components belonging to narrower scopes."
msgstr ""
#. Tag: para
#: Preface.xml:169
#, no-c-format
-msgid ""
-"<emphasis>Bijection</emphasis> differs from IoC in that it is "
-"<emphasis>dynamic</emphasis>, <emphasis>contextual</emphasis>, and "
-"<emphasis>bidirectional</emphasis>. You can think of it as a mechanism for "
-"aliasing contextual variables (names in the various contexts bound to the "
-"current thread) to attributes of the component. Bijection allows auto-"
-"assembly of stateful components by the container. It even allows a component "
-"to safely and easily manipulate the value of a context variable, just by "
-"assigning it to an attribute of the component."
-msgstr ""
+msgid "<emphasis>Bijection</emphasis> differs from IoC in that it is <emphasis>dynamic</emphasis>, <emphasis>contextual</emphasis>, and <emphasis>bidirectional</emphasis>. You can think of it as a mechanism for aliasing contextual variables (names in the various contexts bound to the current thread) to attributes of the component. Bijection allows auto-assembly of stateful components by the container. It even allows a component to safely and easily manipulate the value of a context variable, just by assigning it to an attribute of the component."
+msgstr "La <emphasis>Bijection</emphasis> differisce da IoC poiché è <emphasis>dinamiac</emphasis>, <emphasis>contestuale</emphasis>, e <emphasis>bidirezionale</emphasis>. Puoi pensare ad essa come un meccanismo per la denominazione di variabili contestuali (nomi in vari contesti legati all thread attuale) in attributi dei componenti. La bijection consente l'autoassemblamento dei componenti da parte del container. Permette pure che un componente possa in tutta sicurezza e semplicità manipolare il valore di una variabile di contesto, solamente assegnandola ad un attributo del componente. "
#. Tag: emphasis
#: Preface.xml:181
#, no-c-format
msgid "Workspace management and multi-window browsing"
-msgstr ""
+msgstr "Gestione del workspace e navigazione multi-finestra"
#. Tag: para
#: Preface.xml:183
#, no-c-format
-msgid ""
-"Seam applications let the user freely switch between multiple browser tabs, "
-"each associated with a different, safely isolated, conversation. "
-"Applications may even take advantage of <emphasis>workspace management</"
-"emphasis>, allowing the user to switch between conversations (workspaces) in "
-"a single browser tab. Seam provides not only correct multi-window operation, "
-"but also multi-window-like operation in a single window!"
+msgid "Seam applications let the user freely switch between multiple browser tabs, each associated with a different, safely isolated, conversation. Applications may even take advantage of <emphasis>workspace management</emphasis>, allowing the user to switch between conversations (workspaces) in a single browser tab. Seam provides not only correct multi-window operation, but also multi-window-like operation in a single window!"
msgstr ""
#. Tag: emphasis
#: Preface.xml:194
#, no-c-format
msgid "Prefer annotations to XML"
-msgstr ""
+msgstr "Preferenza delle annotazioni all'XML"
#. Tag: para
#: Preface.xml:196
#, no-c-format
-msgid ""
-"Traditionally, the Java community has been in a state of deep confusion "
-"about precisely what kinds of meta-information counts as configuration. J2EE "
-"and popular \"lightweight\" containers have provided XML-based deployment "
-"descriptors both for things which are truly configurable between different "
-"deployments of the system, and for any other kinds or declaration which can "
-"not easily be expressed in Java. Java 5 annotations changed all this."
+msgid "Traditionally, the Java community has been in a state of deep confusion about precisely what kinds of meta-information counts as configuration. J2EE and popular \"lightweight\" containers have provided XML-based deployment descriptors both for things which are truly configurable between different deployments of the system, and for any other kinds or declaration which can not easily be expressed in Java. Java 5 annotations changed all this."
msgstr ""
#. Tag: para
#: Preface.xml:204
#, no-c-format
-msgid ""
-"EJB 3.0 embraces annotations and \"configuration by exception\" as the "
-"easiest way to provide information to the container in a declarative form. "
-"Unfortunately, JSF is still heavily dependent on verbose XML configuration "
-"files. Seam extends the annotations provided by EJB 3.0 with a set of "
-"annotations for declarative state management and declarative context "
-"demarcation. This lets you eliminate the noisy JSF managed bean declarations "
-"and reduce the required XML to just that information which truly belongs in "
-"XML (the JSF navigation rules)."
+msgid "EJB 3.0 embraces annotations and \"configuration by exception\" as the easiest way to provide information to the container in a declarative form. Unfortunately, JSF is still heavily dependent on verbose XML configuration files. Seam extends the annotations provided by EJB 3.0 with a set of annotations for declarative state management and declarative context demarcation. This lets you eliminate the noisy JSF managed bean declarations and reduce the required XML to just that information which truly belongs in XML (the JSF navigation rules)."
msgstr ""
#. Tag: emphasis
#: Preface.xml:217
#, no-c-format
msgid "Integration testing is easy"
-msgstr ""
+msgstr "I test d'integrazione sono facili"
#. Tag: para
#: Preface.xml:219
#, no-c-format
-msgid ""
-"Seam components, being plain Java classes, are by nature unit testable. But "
-"for complex applications, unit testing alone is insufficient. Integration "
-"testing has traditionally been a messy and difficult task for Java web "
-"applications. Therefore, Seam provides for testability of Seam applications "
-"as a core feature of the framework. You can easily write JUnit or TestNG "
-"tests that reproduce a whole interaction with a user, exercising all "
-"components of the system apart from the view (the JSP or Facelets page). You "
-"can run these tests directly inside your IDE, where Seam will automatically "
-"deploy EJB components using JBoss Embedded."
+msgid "Seam components, being plain Java classes, are by nature unit testable. But for complex applications, unit testing alone is insufficient. Integration testing has traditionally been a messy and difficult task for Java web applications. Therefore, Seam provides for testability of Seam applications as a core feature of the framework. You can easily write JUnit or TestNG tests that reproduce a whole interaction with a user, exercising all components of the system apart from the view (the JSP or Facelets page). You can run these tests directly inside your IDE, where Seam will automatically deploy EJB components using JBoss Embedded."
msgstr ""
#. Tag: emphasis
#: Preface.xml:232
#, no-c-format
msgid "The specs ain't perfect"
-msgstr ""
+msgstr "Le specifiche non sono perfette"
#. Tag: para
#: Preface.xml:234
#, no-c-format
-msgid ""
-"We think the latest incarnation of Java EE is great. But we know it's never "
-"going to be perfect. Where there are holes in the specifications (for "
-"example, limitations in the JSF lifecycle for GET requests), Seam fixes "
-"them. And the authors of Seam are working with the JCP expert groups to make "
-"sure those fixes make their way back into the next revision of the standards."
+msgid "We think the latest incarnation of Java EE is great. But we know it's never going to be perfect. Where there are holes in the specifications (for example, limitations in the JSF lifecycle for GET requests), Seam fixes them. And the authors of Seam are working with the JCP expert groups to make sure those fixes make their way back into the next revision of the standards."
msgstr ""
#. Tag: emphasis
#: Preface.xml:245
#, no-c-format
msgid "There's more to a web application than serving HTML pages"
-msgstr ""
+msgstr "Una web application non genera soltanto pagine html ma fa molto di più"
#. Tag: para
#: Preface.xml:247
#, no-c-format
-msgid ""
-"Today's web frameworks think too small. They let you get user input off a "
-"form and into your Java objects. And then they leave you hanging. A truly "
-"complete web application framework should address problems like persistence, "
-"concurrency, asynchronicity, state management, security, email, messaging, "
-"PDF and chart generation, workflow, wikitext rendering, webservices, caching "
-"and more. Once you scratch the surface of Seam, you'll be amazed at how many "
-"problems become simpler..."
-msgstr ""
+msgid "Today's web frameworks think too small. They let you get user input off a form and into your Java objects. And then they leave you hanging. A truly complete web application framework should address problems like persistence, concurrency, asynchronicity, state management, security, email, messaging, PDF and chart generation, workflow, wikitext rendering, webservices, caching and more. Once you scratch the surface of Seam, you'll be amazed at how many problems become simpler..."
+msgstr "I web framework di oggi pensano troppo poco. Ti consentono di estrarre gli input dell'utente da una form e di metterlo in un oggetto Java. E poi ti abbandonano. Un vero web framework dovrebbe indirizzarsi verso problemi come la persistenza, la concorrenza, l'asincronicità, la gestione dello stato, la sicurezza, le email, la messaggistica, la generazione di PDF e grafici, il workflow, il rendering di wikitext, i web service, il caching e altro ancora. Dopo aver provato Seam, sarai stupito di come questi problemi vengano semplificati..."
#. Tag: para
#: Preface.xml:255
#, no-c-format
-msgid ""
-"Seam integrates JPA and Hibernate3 for persistence, the EJB Timer Service "
-"and Quartz for lightweight asychronicity, jBPM for workflow, JBoss Rules for "
-"business rules, Meldware Mail for email, Hibernate Search and Lucene for "
-"full text search, JMS for messaging and JBoss Cache for page fragment "
-"caching. Seam layers an innovative rule-based security framework over JAAS "
-"and JBoss Rules. There's even JSF tag libraries for rendering PDF, outgoing "
-"email, charts and wikitext. Seam components may be called synchronously as a "
-"Web Service, asynchronously from client-side JavaScript or Google Web "
-"Toolkit or, of course, directly from JSF."
-msgstr ""
+msgid "Seam integrates JPA and Hibernate3 for persistence, the EJB Timer Service and Quartz for lightweight asychronicity, jBPM for workflow, JBoss Rules for business rules, Meldware Mail for email, Hibernate Search and Lucene for full text search, JMS for messaging and JBoss Cache for page fragment caching. Seam layers an innovative rule-based security framework over JAAS and JBoss Rules. There's even JSF tag libraries for rendering PDF, outgoing email, charts and wikitext. Seam components may be called synchronously as a Web Service, asynchronously from client-side JavaScript or Google Web Toolkit or, of course, directly from JSF."
+msgstr "Seam integra JPA e Hibernate3 per la persistenza, EJB Timer Service e Quartz per l'asincronicità, jBPM per i workflow, JBoss Rules per le regole di business, Meldware Mail per le email, Hibernate Search e Lucene per la ricerca full text, JMS per la messaggistica e JBoss Cache per il caching delle pagine. Seam pone un framework di sicurezza basato sulle regole sopra JAAS JBoss Rules. Ci sono anche le librerie JSP per la creazione dei PDF, le mail in uscita, i grafici ed il testo wiki. I componenti Seam possono essere chiamati in modo sincrono come un Web Service, oppure in modo asincrono da JavaScript lato client o da Google Web Toolkit o, sicuramente, direttamente da JSF."
#. Tag: emphasis
#: Preface.xml:268
#, no-c-format
msgid "Get started now!"
-msgstr ""
+msgstr "Inizia ora!"
#. Tag: para
#: Preface.xml:270
#, no-c-format
-msgid ""
-"Seam works in any Java EE application server, and even works in Tomcat. If "
-"your environment supports EJB 3.0, great! If it doesn't, no problem, you can "
-"use Seam's built-in transaction management with JPA or Hibernate3 for "
-"persistence. Or, you can deploy JBoss Embedded in Tomcat, and get full "
-"support for EJB 3.0."
-msgstr ""
+msgid "Seam works in any Java EE application server, and even works in Tomcat. If your environment supports EJB 3.0, great! If it doesn't, no problem, you can use Seam's built-in transaction management with JPA or Hibernate3 for persistence. Or, you can deploy JBoss Embedded in Tomcat, and get full support for EJB 3.0."
+msgstr "Seam funziona in qualsiasi application server Java EE, e perfino in Tomcat. Se il tuo ambiente supporta EJB 3.0, benissimo! Altrimenti, nessun problema, puoi utilizzare la gestione delle transazioni interna di Seam con JPA o Hibernate3 per la persistenza. Oppure puoi fare il deploy di JBoss Embedded in Tomcat, ed ottenere pieno supporto per EJB 3.0."
#. Tag: para
#: Preface.xml:286
#, no-c-format
-msgid ""
-"It turns out that the combination of Seam, JSF and EJB3 is <emphasis>the</"
-"emphasis> simplest way to write a complex web application in Java. You won't "
-"believe how little code is required!"
-msgstr ""
+msgid "It turns out that the combination of Seam, JSF and EJB3 is <emphasis>the</emphasis> simplest way to write a complex web application in Java. You won't believe how little code is required!"
+msgstr "Risulta che la combinazione di Seam, JSF e EJB3 è <emphasis>il</emphasis> modo più semplice per scrivere un'applicazione web complessa in Java. Non ci crederai quanto poco codice viene richiesto!"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-11 20:53:36 UTC (rev 9756)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-11 22:36:45 UTC (rev 9757)
@@ -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:59+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-09 21:08+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,7 +17,7 @@
#: Tutorial.xml:4
#, no-c-format
msgid "Seam Tutorial"
-msgstr ""
+msgstr "Tutorial di Seam"
#. Tag: title
#: Tutorial.xml:7
@@ -28,13 +28,7 @@
#. Tag: para
#: Tutorial.xml:9
#, no-c-format
-msgid ""
-"Seam provides a number of example applications demonstrating how to use the "
-"various features of Seam. This tutorial will guide you through a few of "
-"those examples to help you get started learning Seam. The Seam examples are "
-"located in the <filename>examples</filename> subdirectory of the Seam "
-"distribution. The registration example, which will be the first example we "
-"look at, is in the <filename>examples/registration</filename> directory."
+msgid "Seam provides a number of example applications demonstrating how to use the various features of Seam. This tutorial will guide you through a few of those examples to help you get started learning Seam. The Seam examples are located in the <filename>examples</filename> subdirectory of the Seam distribution. The registration example, which will be the first example we look at, is in the <filename>examples/registration</filename> directory."
msgstr ""
#. Tag: para
@@ -46,35 +40,25 @@
#. Tag: para
#: Tutorial.xml:19
#, no-c-format
-msgid ""
-"The <filename>view</filename> directory contains view-related files such as "
-"web page templates, images and stylesheets."
+msgid "The <filename>view</filename> directory contains view-related files such as web page templates, images and stylesheets."
msgstr ""
#. Tag: para
#: Tutorial.xml:25
#, no-c-format
-msgid ""
-"The <filename>resources</filename> directory contains deployment descriptors "
-"and other configuration files."
+msgid "The <filename>resources</filename> directory contains deployment descriptors and other configuration files."
msgstr ""
#. Tag: para
#: Tutorial.xml:30
#, no-c-format
-msgid ""
-"The <filename>src</filename> directory contains the application source code."
+msgid "The <filename>src</filename> directory contains the application source code."
msgstr ""
#. Tag: para
#: Tutorial.xml:35
#, no-c-format
-msgid ""
-"The example applications run both on JBoss AS and Tomcat with no additional "
-"configuration. The following sections will explain the procedure in both "
-"cases. Note that all the examples are built and run from the Ant "
-"<filename>build.xml</filename>, so you'll need a recent version of Ant "
-"installed before you get started."
+msgid "The example applications run both on JBoss AS and Tomcat with no additional configuration. The following sections will explain the procedure in both cases. Note that all the examples are built and run from the Ant <filename>build.xml</filename>, so you'll need a recent version of Ant installed before you get started."
msgstr ""
#. Tag: title
@@ -86,41 +70,19 @@
#. Tag: para
#: Tutorial.xml:47
#, no-c-format
-msgid ""
-"The examples are configured for use on JBoss 4.2. You'll need to set "
-"<literal>jboss.home</literal>, in the shared <literal>build.properties</"
-"literal> file in the root folder of your Seam installation, to the location "
-"of your JBoss AS installation."
+msgid "The examples are configured for use on JBoss 4.2. You'll need to set <literal>jboss.home</literal>, in the shared <literal>build.properties</literal> file in the root folder of your Seam installation, to the location of your JBoss AS installation."
msgstr ""
#. Tag: para
#: Tutorial.xml:51
#, no-c-format
-msgid ""
-"Once you've set the location of JBoss AS and started the application server, "
-"you can build and deploy any example by typing <literal>ant explode</"
-"literal> in the the directory for that example. Any example that is packaged "
-"as an EAR deploys to a URL like <literal>/seam-<replaceable>example</"
-"replaceable></literal>, where <replaceable>example</replaceable> is the name "
-"of the example folder, with one exception. If the example folder begins with "
-"seam, the prefix \"seam\" is ommitted. For instance, if JBoss AS is running "
-"on port 8080, the URL for the registration example is <ulink url=\"http://"
-"localhost:8080/seam-registration/\"> <literal>http://localhost:8080/seam-"
-"registration/</literal></ulink>, whereas the URL for the seamspace example "
-"is <ulink url=\"http://localhost:8080/seam-space/\"> <literal>http://"
-"localhost:8080/seam-space/</literal></ulink>."
+msgid "Once you've set the location of JBoss AS and started the application server, you can build and deploy any example by typing <literal>ant explode</literal> in the the directory for that example. Any example that is packaged as an EAR deploys to a URL like <literal>/seam-<replaceable>example</replaceable></literal>, where <replaceable>example</replaceable> is the name of the example folder, with one exception. If the example folder begins with seam, the prefix \"seam\" is ommitted. For instance, if JBoss AS is running on port 8080, the URL for the registration example is <ulink url=\"http://localhost:8080/seam-registration/\"> <literal>http://localhost:8080/seam-registration/</literal></ulink>, whereas the URL for the seamspace example is <ulink url=\"http://localhost:8080/seam-space/\"> <literal>http://localhost:8080/seam-space/</literal></ulink>."
msgstr ""
#. Tag: para
#: Tutorial.xml:62
#, no-c-format
-msgid ""
-"If, on the other hand, the example gets packaged as a WAR, then it deploys "
-"to a URL like <literal>/jboss-seam-<replaceable>example</replaceable></"
-"literal>. Most of the examples can be deployed as a WAR to Tomcat with "
-"Embedded JBoss by typing <literal>ant tomcat.deploy</literal>. Several of "
-"the examples can only be deployed as a WAR. Those examples are "
-"groovybooking, hibernate, jpa, and spring."
+msgid "If, on the other hand, the example gets packaged as a WAR, then it deploys to a URL like <literal>/jboss-seam-<replaceable>example</replaceable></literal>. Most of the examples can be deployed as a WAR to Tomcat with Embedded JBoss by typing <literal>ant tomcat.deploy</literal>. Several of the examples can only be deployed as a WAR. Those examples are groovybooking, hibernate, jpa, and spring."
msgstr ""
#. Tag: title
@@ -132,44 +94,25 @@
#. Tag: para
#: Tutorial.xml:73
#, no-c-format
-msgid ""
-"The examples are also configured for use on Tomcat 6.0. You will need to "
-"follow the instructions in <xref linkend=\"config.install.embedded\"/> for "
-"installing JBoss Embedded on Tomcat 6.0. JBoss Embedded is only required to "
-"run the Seam demos that use EJB3 components on Tomcat. There are also "
-"examples of non-EJB3 applications that can be run on Tomcat without the use "
-"of JBoss Embedded."
+msgid "The examples are also configured for use on Tomcat 6.0. You will need to follow the instructions in <xref linkend=\"config.install.embedded\"/> for installing JBoss Embedded on Tomcat 6.0. JBoss Embedded is only required to run the Seam demos that use EJB3 components on Tomcat. There are also examples of non-EJB3 applications that can be run on Tomcat without the use of JBoss Embedded."
msgstr ""
#. Tag: para
#: Tutorial.xml:79
#, no-c-format
-msgid ""
-"You'll need to set <literal>tomcat.home</literal>, in the shared "
-"<literal>build.properties</literal> file in the root folder of your Seam "
-"installation, to the location of your Tomcat installation. make sure you set "
-"the location of your Tomcat."
+msgid "You'll need to set <literal>tomcat.home</literal>, in the shared <literal>build.properties</literal> file in the root folder of your Seam installation, to the location of your Tomcat installation. make sure you set the location of your Tomcat."
msgstr ""
#. Tag: para
#: Tutorial.xml:85
#, no-c-format
-msgid ""
-"You'll need to use a different Ant target when using Tomcat. Use "
-"<literal>ant tomcat.deploy</literal> in example subdirectory to build and "
-"deploy any example for Tomcat."
+msgid "You'll need to use a different Ant target when using Tomcat. Use <literal>ant tomcat.deploy</literal> in example subdirectory to build and deploy any example for Tomcat."
msgstr ""
#. Tag: para
#: Tutorial.xml:90
#, no-c-format
-msgid ""
-"On Tomcat, the examples deploy to URLs like <literal>/jboss-seam-"
-"<replaceable>example</replaceable></literal>, so for the registration "
-"example the URL would be <ulink url=\"http://localhost:8080/jboss-seam-"
-"registration/\"> <literal>http://localhost:8080/jboss-seam-registration/</"
-"literal></ulink>. The same is true for examples that deploy as a WAR, as "
-"mentioned in the previous section."
+msgid "On Tomcat, the examples deploy to URLs like <literal>/jboss-seam-<replaceable>example</replaceable></literal>, so for the registration example the URL would be <ulink url=\"http://localhost:8080/jboss-seam-registration/\"> <literal>http://localhost:8080/jboss-seam-registration/</literal></ulink>. The same is true for examples that deploy as a WAR, as mentioned in the previous section."
msgstr ""
#. Tag: title
@@ -181,12 +124,7 @@
#. Tag: para
#: Tutorial.xml:101
#, no-c-format
-msgid ""
-"Most of the examples come with a suite of TestNG integration tests. The "
-"easiest way to run the tests is to run <literal>ant test</literal>. It is "
-"also possible to run the tests inside your IDE using the TestNG plugin. "
-"Consult the readme.txt in the examples directory of the Seam distribution "
-"for more information."
+msgid "Most of the examples come with a suite of TestNG integration tests. The easiest way to run the tests is to run <literal>ant test</literal>. It is also possible to run the tests inside your IDE using the TestNG plugin. Consult the readme.txt in the examples directory of the Seam distribution for more information."
msgstr ""
#. Tag: title
@@ -198,32 +136,26 @@
#. Tag: para
#: Tutorial.xml:114
#, no-c-format
-msgid ""
-"The registration example is a simple application that lets a new user store "
-"his username, real name and password in the database. The example isn't "
-"intended to show off all of the cool functionality of Seam. However, it "
-"demonstrates the use of an EJB3 session bean as a JSF action listener, and "
-"basic configuration of Seam."
+msgid "The registration example is a simple application that lets a new user store his username, real name and password in the database. The example isn't intended to show off all of the cool functionality of Seam. However, it demonstrates the use of an EJB3 session bean as a JSF action listener, and basic configuration of Seam."
msgstr ""
#. Tag: para
#: Tutorial.xml:119
#, no-c-format
-msgid ""
-"We'll go slowly, since we realize you might not yet be familiar with EJB 3.0."
+msgid "We'll go slowly, since we realize you might not yet be familiar with EJB 3.0."
msgstr ""
#. Tag: para
#: Tutorial.xml:121
#, no-c-format
-msgid ""
-"The start page displays a very basic form with three input fields. Try "
-"filling them in and then submitting the form. This will save a user object "
-"in the database."
+msgid "The start page displays a very basic form with three input fields. Try filling them in and then submitting the form. This will save a user object in the database."
msgstr ""
#. Tag: title
-#: Tutorial.xml:134 Tutorial.xml:533 Tutorial.xml:722 Tutorial.xml:955
+#: Tutorial.xml:134
+#: Tutorial.xml:533
+#: Tutorial.xml:722
+#: Tutorial.xml:955
#, no-c-format
msgid "Understanding the code"
msgstr ""
@@ -231,10 +163,7 @@
#. Tag: para
#: Tutorial.xml:136
#, no-c-format
-msgid ""
-"The example is implemented with two Facelets templates, one entity bean and "
-"one stateless session bean. Let's take a look at the code, starting from the "
-"\"bottom\"."
+msgid "The example is implemented with two Facelets templates, one entity bean and one stateless session bean. Let's take a look at the code, starting from the \"bottom\"."
msgstr ""
#. Tag: title
@@ -246,11 +175,7 @@
#. Tag: para
#: Tutorial.xml:143
#, no-c-format
-msgid ""
-"We need an EJB entity bean for user data. This class defines "
-"<emphasis>persistence</emphasis> and <emphasis>validation</emphasis> "
-"declaratively, via annotations. It also needs some extra annotations that "
-"define the class as a Seam component."
+msgid "We need an EJB entity bean for user data. This class defines <emphasis>persistence</emphasis> and <emphasis>validation</emphasis> declaratively, via annotations. It also needs some extra annotations that define the class as a Seam component."
msgstr ""
#. Tag: title
@@ -319,138 +244,144 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Entity\n"
+"@Name(\"user\")\n"
+"@Scope(SESSION)\n"
+"@Table(name=\"users\")\n"
+"public class User implements Serializable\n"
+"{\n"
+" private static final long serialVersionUID = 1881413500711441951L;\n"
+" \n"
+" private String username;\n"
+" private String password;\n"
+" private String name;\n"
+" \n"
+" public User(String name, String password, String username)\n"
+" {\n"
+" this.name = name;\n"
+" this.password = password;\n"
+" this.username = username;\n"
+" }\n"
+" \n"
+" public User() {}\n"
+" \n"
+" @NotNull @Length(min=5, max=15)\n"
+" public String getPassword()\n"
+" {\n"
+" return password;\n"
+" }\n"
+"\n"
+" public void setPassword(String password)\n"
+" {\n"
+" this.password = password;\n"
+" }\n"
+" \n"
+" @NotNull\n"
+" public String getName()\n"
+" {\n"
+" return name;\n"
+" }\n"
+"\n"
+" public void setName(String name)\n"
+" {\n"
+" this.name = name;\n"
+" }\n"
+" \n"
+" @Id @NotNull @Length(min=5, max=15)\n"
+" public String getUsername()\n"
+" {\n"
+" return username;\n"
+" }\n"
+"\n"
+" public void setUsername(String username)\n"
+" {\n"
+" this.username = username;\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:163
#, no-c-format
-msgid ""
-"The EJB3 standard <literal>@Entity</literal> annotation indicates that the "
-"<literal>User</literal> class is an entity bean."
+msgid "The EJB3 standard <literal>@Entity</literal> annotation indicates that the <literal>User</literal> class is an entity bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:167
#, no-c-format
-msgid ""
-"A Seam component needs a <emphasis>component name</emphasis> specified by "
-"the <link linkend=\"name-annotation\"> <literal>@Name</literal> </link> "
-"annotation. This name must be unique within the Seam application. When JSF "
-"asks Seam to resolve a context variable with a name that is the same as a "
-"Seam component name, and the context variable is currently undefined (null), "
-"Seam will instantiate that component, and bind the new instance to the "
-"context variable. In this case, Seam will instantiate a <literal>User</"
-"literal> the first time JSF encounters a variable named <literal>user</"
-"literal>."
+msgid "A Seam component needs a <emphasis>component name</emphasis> specified by the <link linkend=\"name-annotation\"> <literal>@Name</literal> </link> annotation. This name must be unique within the Seam application. When JSF asks Seam to resolve a context variable with a name that is the same as a Seam component name, and the context variable is currently undefined (null), Seam will instantiate that component, and bind the new instance to the context variable. In this case, Seam will instantiate a <literal>User</literal> the first time JSF encounters a variable named <literal>user</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:178
#, no-c-format
-msgid ""
-"Whenever Seam instantiates a component, it binds the new instance to a "
-"context variable in the component's <emphasis>default context</emphasis>. "
-"The default context is specified using the <link linkend=\"scope-annotation"
-"\"> <literal>@Scope</literal> </link> annotation. The <literal>User</"
-"literal> bean is a session scoped component."
+msgid "Whenever Seam instantiates a component, it binds the new instance to a context variable in the component's <emphasis>default context</emphasis>. The default context is specified using the <link linkend=\"scope-annotation\"> <literal>@Scope</literal> </link> annotation. The <literal>User</literal> bean is a session scoped component."
msgstr ""
#. Tag: para
#: Tutorial.xml:186
#, no-c-format
-msgid ""
-"The EJB standard <literal>@Table</literal> annotation indicates that the "
-"<literal>User</literal> class is mapped to the <literal>users</literal> "
-"table."
+msgid "The EJB standard <literal>@Table</literal> annotation indicates that the <literal>User</literal> class is mapped to the <literal>users</literal> table."
msgstr ""
#. Tag: para
#: Tutorial.xml:191
#, no-c-format
-msgid ""
-"<literal>name</literal>, <literal>password</literal> and <literal>username</"
-"literal> are the persistent attributes of the entity bean. All of our "
-"persistent attributes define accessor methods. These are needed when this "
-"component is used by JSF in the render response and update model values "
-"phases."
+msgid "<literal>name</literal>, <literal>password</literal> and <literal>username</literal> are the persistent attributes of the entity bean. All of our persistent attributes define accessor methods. These are needed when this component is used by JSF in the render response and update model values phases."
msgstr ""
#. Tag: para
#: Tutorial.xml:198
#, no-c-format
-msgid ""
-"An empty constructor is both required by both the EJB specification and by "
-"Seam."
+msgid "An empty constructor is both required by both the EJB specification and by Seam."
msgstr ""
#. Tag: para
#: Tutorial.xml:202
#, no-c-format
-msgid ""
-"The <literal>@NotNull</literal> and <literal>@Length</literal> annotations "
-"are part of the Hibernate Validator framework. Seam integrates Hibernate "
-"Validator and lets you use it for data validation (even if you are not using "
-"Hibernate for persistence)."
+msgid "The <literal>@NotNull</literal> and <literal>@Length</literal> annotations are part of the Hibernate Validator framework. Seam integrates Hibernate Validator and lets you use it for data validation (even if you are not using Hibernate for persistence)."
msgstr ""
#. Tag: para
#: Tutorial.xml:208
#, no-c-format
-msgid ""
-"The EJB standard <literal>@Id</literal> annotation indicates the primary key "
-"attribute of the entity bean."
+msgid "The EJB standard <literal>@Id</literal> annotation indicates the primary key attribute of the entity bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:214
#, no-c-format
-msgid ""
-"The most important things to notice in this example are the <literal>@Name</"
-"literal> and <literal>@Scope</literal> annotations. These annotations "
-"establish that this class is a Seam component."
+msgid "The most important things to notice in this example are the <literal>@Name</literal> and <literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component."
msgstr ""
#. Tag: para
#: Tutorial.xml:216
#, no-c-format
-msgid ""
-"We'll see below that the properties of our <literal>User</literal> class are "
-"bound directly to JSF components and are populated by JSF during the update "
-"model values phase. We don't need any tedious glue code to copy data back "
-"and forth between the JSP pages and the entity bean domain model."
+msgid "We'll see below that the properties of our <literal>User</literal> class are bound directly to JSF components and are populated by JSF during the update model values phase. We don't need any tedious glue code to copy data back and forth between the JSP pages and the entity bean domain model."
msgstr ""
#. Tag: para
#: Tutorial.xml:220
#, no-c-format
-msgid ""
-"However, entity beans shouldn't do transaction management or database "
-"access. So we can't use this component as a JSF action listener. For that we "
-"need a session bean."
+msgid "However, entity beans shouldn't do transaction management or database access. So we can't use this component as a JSF action listener. For that we need a session bean."
msgstr ""
#. Tag: title
#: Tutorial.xml:226
#, no-c-format
-msgid ""
-"The stateless session bean class: <literal>RegisterAction.java</literal>"
+msgid "The stateless session bean class: <literal>RegisterAction.java</literal>"
msgstr ""
#. Tag: para
#: Tutorial.xml:228
#, no-c-format
-msgid ""
-"Most Seam application use session beans as JSF action listeners (you can use "
-"JavaBeans instead if you like)."
+msgid "Most Seam application use session beans as JSF action listeners (you can use JavaBeans instead if you like)."
msgstr ""
#. Tag: para
#: Tutorial.xml:230
#, no-c-format
-msgid ""
-"We have exactly one JSF action in our application, and one session bean "
-"method attached to it. In this case, we'll use a stateless session bean, "
-"since all the state associated with our action is held by the <literal>User</"
-"literal> bean."
+msgid "We have exactly one JSF action in our application, and one session bean method attached to it. In this case, we'll use a stateless session bean, since all the state associated with our action is held by the <literal>User</literal> bean."
msgstr ""
#. Tag: para
@@ -496,135 +427,117 @@
" }\n"
" else\n"
" {\n"
-" FacesMessages.instance().add(\"User #{user.username} already exists"
-"\");\n"
+" FacesMessages.instance().add(\"User #{user.username} already exists\");\n"
" return null;\n"
" }\n"
" }\n"
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateless\n"
+"@Name(\"register\")\n"
+"public class RegisterAction implements Register\n"
+"{\n"
+" @In\n"
+" private User user;\n"
+" \n"
+" @PersistenceContext\n"
+" private EntityManager em;\n"
+" \n"
+" @Logger\n"
+" private Log log;\n"
+" \n"
+" public String register()\n"
+" {\n"
+" List existing = em.createQuery(\n"
+" \"select username from User where username = #{user.username}\")\n"
+" .getResultList();\n"
+" \n"
+" if (existing.size()==0)\n"
+" {\n"
+" em.persist(user);\n"
+" log.info(\"Registered new user #{user.username}\");\n"
+" return \"/registered.xhtml\";\n"
+" }\n"
+" else\n"
+" {\n"
+" FacesMessages.instance().add(\"User #{user.username} already exists\");\n"
+" return null;\n"
+" }\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:254
#, no-c-format
-msgid ""
-"The EJB <literal>@Stateless</literal> annotation marks this class as a "
-"stateless session bean."
+msgid "The EJB <literal>@Stateless</literal> annotation marks this class as a stateless session bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:258
#, no-c-format
-msgid ""
-"The <link linkend=\"in-annotation\"> <literal>@In</literal> </link> "
-"annotation marks an attribute of the bean as injected by Seam. In this case, "
-"the attribute is injected from a context variable named <literal>user</"
-"literal> (the instance variable name)."
+msgid "The <link linkend=\"in-annotation\"> <literal>@In</literal> </link> annotation marks an attribute of the bean as injected by Seam. In this case, the attribute is injected from a context variable named <literal>user</literal> (the instance variable name)."
msgstr ""
#. Tag: para
#: Tutorial.xml:265
#, no-c-format
-msgid ""
-"The EJB standard <literal>@PersistenceContext</literal> annotation is used "
-"to inject the EJB3 entity manager."
+msgid "The EJB standard <literal>@PersistenceContext</literal> annotation is used to inject the EJB3 entity manager."
msgstr ""
#. Tag: para
#: Tutorial.xml:269
#, no-c-format
-msgid ""
-"The Seam <literal>@Logger</literal> annotation is used to inject the "
-"component's <literal>Log</literal> instance."
+msgid "The Seam <literal>@Logger</literal> annotation is used to inject the component's <literal>Log</literal> instance."
msgstr ""
#. Tag: para
#: Tutorial.xml:273
#, no-c-format
-msgid ""
-"The action listener method uses the standard EJB3 <literal>EntityManager</"
-"literal> API to interact with the database, and returns the JSF outcome. "
-"Note that, since this is a session bean, a transaction is automatically "
-"begun when the <literal>register()</literal> method is called, and committed "
-"when it completes."
+msgid "The action listener method uses the standard EJB3 <literal>EntityManager</literal> API to interact with the database, and returns the JSF outcome. Note that, since this is a session bean, a transaction is automatically begun when the <literal>register()</literal> method is called, and committed when it completes."
msgstr ""
#. Tag: para
#: Tutorial.xml:280
#, no-c-format
-msgid ""
-"Notice that Seam lets you use a JSF EL expression inside EJB-QL. Under the "
-"covers, this results in an ordinary JPA <literal>setParameter()</literal> "
-"call on the standard JPA <literal>Query</literal> object. Nice, huh?"
+msgid "Notice that Seam lets you use a JSF EL expression inside EJB-QL. Under the covers, this results in an ordinary JPA <literal>setParameter()</literal> call on the standard JPA <literal>Query</literal> object. Nice, huh?"
msgstr ""
#. Tag: para
#: Tutorial.xml:285
#, no-c-format
-msgid ""
-"The <literal>Log</literal> API lets us easily display templated log messages "
-"which can also make use of JSF EL expressions."
+msgid "The <literal>Log</literal> API lets us easily display templated log messages which can also make use of JSF EL expressions."
msgstr ""
#. Tag: para
#: Tutorial.xml:290
#, no-c-format
-msgid ""
-"JSF action listener methods return a string-valued outcome that determines "
-"what page will be displayed next. A null outcome (or a void action listener "
-"method) redisplays the previous page. In plain JSF, it is normal to always "
-"use a JSF <emphasis>navigation rule</emphasis> to determine the JSF view id "
-"from the outcome. For complex application this indirection is useful and a "
-"good practice. However, for very simple examples like this one, Seam lets "
-"you use the JSF view id as the outcome, eliminating the requirement for a "
-"navigation rule. <emphasis>Note that when you use a view id as an outcome, "
-"Seam always performs a browser redirect.</emphasis>"
+msgid "JSF action listener methods return a string-valued outcome that determines what page will be displayed next. A null outcome (or a void action listener method) redisplays the previous page. In plain JSF, it is normal to always use a JSF <emphasis>navigation rule</emphasis> to determine the JSF view id from the outcome. For complex application this indirection is useful and a good practice. However, for very simple examples like this one, Seam lets you use the JSF view id as the outcome, eliminating the requirement for a navigation rule. <emphasis>Note that when you use a view id as an outcome, Seam always performs a browser redirect.</emphasis>"
msgstr ""
#. Tag: para
#: Tutorial.xml:302
#, no-c-format
-msgid ""
-"Seam provides a number of <emphasis>built-in components</emphasis> to help "
-"solve common problems. The <literal>FacesMessages</literal> component makes "
-"it easy to display templated error or success messages. (As of Seam 2.1, you "
-"can use <literal>StatusMessages</literal> instead to remove the semantic "
-"dependency on JSF). Built-in Seam components may be obtained by injection, "
-"or by calling the <literal>instance()</literal> method on the class of the "
-"built-in component."
+msgid "Seam provides a number of <emphasis>built-in components</emphasis> to help solve common problems. The <literal>FacesMessages</literal> component makes it easy to display templated error or success messages. (As of Seam 2.1, you can use <literal>StatusMessages</literal> instead to remove the semantic dependency on JSF). Built-in Seam components may be obtained by injection, or by calling the <literal>instance()</literal> method on the class of the built-in component."
msgstr ""
#. Tag: para
#: Tutorial.xml:314
#, no-c-format
-msgid ""
-"Note that we did not explicitly specify a <literal>@Scope</literal> this "
-"time. Each Seam component type has a default scope if not explicitly "
-"specified. For stateless session beans, the default scope is the stateless "
-"context, which is the only sensible value."
+msgid "Note that we did not explicitly specify a <literal>@Scope</literal> this time. Each Seam component type has a default scope if not explicitly specified. For stateless session beans, the default scope is the stateless context, which is the only sensible value."
msgstr ""
#. Tag: para
#: Tutorial.xml:318
#, no-c-format
-msgid ""
-"Our session bean action listener performs the business and persistence logic "
-"for our mini-application. In more complex applications, we might need "
-"require a separate service layer. This is easy to achieve with Seam, but "
-"it's overkill for most web applications. Seam does not force you into any "
-"particular strategy for application layering, allowing your application to "
-"be as simple, or as complex, as you want."
+msgid "Our session bean action listener performs the business and persistence logic for our mini-application. In more complex applications, we might need require a separate service layer. This is easy to achieve with Seam, but it's overkill for most web applications. Seam does not force you into any particular strategy for application layering, allowing your application to be as simple, or as complex, as you want."
msgstr ""
#. Tag: para
#: Tutorial.xml:324
#, no-c-format
-msgid ""
-"Note that in this simple application, we've actually made it far more "
-"complex than it needs to be. If we had used the Seam application framework "
-"controllers, we would have eliminated all of our application code. However, "
-"then we wouldn't have had much of an application to explain."
+msgid "Note that in this simple application, we've actually made it far more complex than it needs to be. If we had used the Seam application framework controllers, we would have eliminated all of our application code. However, then we wouldn't have had much of an application to explain."
msgstr ""
#. Tag: title
@@ -655,6 +568,11 @@
" public String register();\n"
"}]]>"
msgstr ""
+"<![CDATA[@Local\n"
+"public interface Register\n"
+"{\n"
+" public String register();\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:341
@@ -665,18 +583,13 @@
#. Tag: title
#: Tutorial.xml:346
#, no-c-format
-msgid ""
-"The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</"
-"literal>"
+msgid "The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</literal>"
msgstr ""
#. Tag: para
#: Tutorial.xml:348
#, no-c-format
-msgid ""
-"The view pages for a Seam application could be implemented using any "
-"technology that supports JSF. In this example we use Facelets, because we "
-"think it's better than JSP."
+msgid "The view pages for a Seam application could be implemented using any technology that supports JSF. In this example we use Facelets, because we think it's better than JSP."
msgstr ""
#. Tag: title
@@ -705,32 +618,52 @@
" <h:form>\n"
" <s:validateAll>\n"
" <h:panelGrid columns=\"2\">\n"
-" Username: <h:inputText value=\"#{user.username}\" required="
-"\"true\"/>\n"
-" Real Name: <h:inputText value=\"#{user.name}\" required="
-"\"true\"/>\n"
-" Password: <h:inputSecret value=\"#{user.password}\" "
-"required=\"true\"/>\n"
+" Username: <h:inputText value=\"#{user.username}\" required=\"true\"/>\n"
+" Real Name: <h:inputText value=\"#{user.name}\" required=\"true\"/>\n"
+" Password: <h:inputSecret value=\"#{user.password}\" required=\"true\"/>\n"
" </h:panelGrid>\n"
" </s:validateAll>\n"
" <h:messages/>\n"
-" <h:commandButton value=\"Register\" action=\"#{register.register}"
-"\"/>\n"
+" <h:commandButton value=\"Register\" action=\"#{register.register}\"/>\n"
" </h:form>\n"
" </f:view>\n"
" </body>\n"
"\n"
"</html>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"utf-8\"?>\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:s=\"http://jboss.com/products/seam/taglib\"\n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
+"\n"
+" <head>\n"
+" <title>Register New User</title>\n"
+" </head>\n"
+" <body>\n"
+" <f:view>\n"
+" <h:form>\n"
+" <s:validateAll>\n"
+" <h:panelGrid columns=\"2\">\n"
+" Username: <h:inputText value=\"#{user.username}\" required=\"true\"/>\n"
+" Real Name: <h:inputText value=\"#{user.name}\" required=\"true\"/>\n"
+" Password: <h:inputSecret value=\"#{user.password}\" required=\"true\"/>\n"
+" </h:panelGrid>\n"
+" </s:validateAll>\n"
+" <h:messages/>\n"
+" <h:commandButton value=\"Register\" action=\"#{register.register}\"/>\n"
+" </h:form>\n"
+" </f:view>\n"
+" </body>\n"
+"\n"
+"</html>]]>"
#. Tag: para
#: Tutorial.xml:356
#, no-c-format
-msgid ""
-"The only thing here that is specific to Seam is the <literal><s:"
-"validateAll></literal> tag. This JSF component tells JSF to validate all "
-"the contained input fields against the Hibernate Validator annotations "
-"specified on the entity bean."
+msgid "The only thing here that is specific to Seam is the <literal><s:validateAll></literal> tag. This JSF component tells JSF to validate all the contained input fields against the Hibernate Validator annotations specified on the entity bean."
msgstr ""
#. Tag: title
@@ -754,65 +687,59 @@
" </head>\n"
" <body>\n"
" <f:view>\n"
-" Welcome, #{user.name}, you are successfully registered as #{user."
-"username}.\n"
+" Welcome, #{user.name}, you are successfully registered as #{user.username}.\n"
" </f:view>\n"
" </body>\n"
"\n"
"</html>\n"
"]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"utf-8\"?>\n"
+"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\" \n"
+" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\">\n"
+"<html xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\">\n"
+"\n"
+" <head>\n"
+" <title>Successfully Registered New User</title>\n"
+" </head>\n"
+" <body>\n"
+" <f:view>\n"
+" Welcome, #{user.name}, you are successfully registered as #{user.username}.\n"
+" </f:view>\n"
+" </body>\n"
+"\n"
+"</html>\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:366
#, no-c-format
-msgid ""
-"This is a simple Facelets page using some inline EL. There's nothing "
-"specific to Seam here."
+msgid "This is a simple Facelets page using some inline EL. There's nothing specific to Seam here."
msgstr ""
#. Tag: title
#: Tutorial.xml:371
#, no-c-format
-msgid ""
-"The Seam component deployment descriptor: <literal>components.xml</literal>"
+msgid "The Seam component deployment descriptor: <literal>components.xml</literal>"
msgstr ""
#. Tag: para
#: Tutorial.xml:373
#, no-c-format
-msgid ""
-"Since this is the first Seam app we've seen, we'll take a look at the "
-"deployment descriptors. Before we get into them, it is worth noting that "
-"Seam strongly values minimal configuration. These configuration files will "
-"be created for you when you create a Seam application. You'll never need to "
-"touch most of these files. We're presenting them now only to help you "
-"understand what all the pieces in the example are doing."
+msgid "Since this is the first Seam app we've seen, we'll take a look at the deployment descriptors. Before we get into them, it is worth noting that Seam strongly values minimal configuration. These configuration files will be created for you when you create a Seam application. You'll never need to touch most of these files. We're presenting them now only to help you understand what all the pieces in the example are doing."
msgstr ""
#. Tag: para
#: Tutorial.xml:380
#, no-c-format
-msgid ""
-"If you've used many Java frameworks before, you'll be used to having to "
-"declare all your component classes in some kind of XML file that gradually "
-"grows more and more unmanageable as your project matures. You'll be relieved "
-"to know that Seam does not require that application components be "
-"accompanied by XML. Most Seam applications require a very small amount of "
-"XML that does not grow very much as the project gets bigger."
+msgid "If you've used many Java frameworks before, you'll be used to having to declare all your component classes in some kind of XML file that gradually grows more and more unmanageable as your project matures. You'll be relieved to know that Seam does not require that application components be accompanied by XML. Most Seam applications require a very small amount of XML that does not grow very much as the project gets bigger."
msgstr ""
#. Tag: para
#: Tutorial.xml:386
#, no-c-format
-msgid ""
-"Nevertheless, it is often useful to be able to provide for <emphasis>some</"
-"emphasis> external configuration of <emphasis>some</emphasis> components "
-"(particularly the components built in to Seam). You have a couple of options "
-"here, but the most flexible option is to provide this configuration in a "
-"file called <literal>components.xml</literal>, located in the <literal>WEB-"
-"INF</literal> directory. We'll use the <literal>components.xml</literal> "
-"file to tell Seam how to find our EJB components in JNDI:"
+msgid "Nevertheless, it is often useful to be able to provide for <emphasis>some</emphasis> external configuration of <emphasis>some</emphasis> components (particularly the components built in to Seam). You have a couple of options here, but the most flexible option is to provide this configuration in a file called <literal>components.xml</literal>, located in the <literal>WEB-INF</literal> directory. We'll use the <literal>components.xml</literal> file to tell Seam how to find our EJB components in JNDI:"
msgstr ""
#. Tag: title
@@ -839,17 +766,24 @@
" \n"
"</components>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
+" http://jboss.com/products/seam/core\n"
+" http://jboss.com/products/seam/core-2.1.xsd \n"
+" http://jboss.com/products/seam/components\n"
+" http://jboss.com/products/seam/components-2.1.xsd\">\n"
+" \n"
+" <core:init jndi-pattern=\"@jndiPattern@\"/>\n"
+" \n"
+"</components>]]>"
#. Tag: para
#: Tutorial.xml:396
#, no-c-format
-msgid ""
-"This code configures a property named <literal>jndiPattern</literal> of a "
-"built-in Seam component named <literal>org.jboss.seam.core.init</literal>. "
-"The funny <literal>@</literal> symbols are there because our Ant build "
-"script puts the correct JNDI pattern in when we deploy the application, "
-"which it reads from the components.properties file. You learn more about how "
-"this process works in <xref linkend=\"xml.descriptor\"/>."
+msgid "This code configures a property named <literal>jndiPattern</literal> of a built-in Seam component named <literal>org.jboss.seam.core.init</literal>. The funny <literal>@</literal> symbols are there because our Ant build script puts the correct JNDI pattern in when we deploy the application, which it reads from the components.properties file. You learn more about how this process works in <xref linkend=\"xml.descriptor\"/>."
msgstr ""
#. Tag: title
@@ -861,9 +795,7 @@
#. Tag: para
#: Tutorial.xml:407
#, no-c-format
-msgid ""
-"The presentation layer for our mini-application will be deployed in a WAR. "
-"So we'll need a web deployment descriptor."
+msgid "The presentation layer for our mini-application will be deployed in a WAR. So we'll need a web deployment descriptor."
msgstr ""
#. Tag: title
@@ -885,8 +817,7 @@
" version=\"2.5\">\n"
"\n"
" <listener>\n"
-" <listener-class>org.jboss.seam.servlet.SeamListener</listener-"
-"class>\n"
+" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
" </listener>\n"
" \n"
" <context-param>\n"
@@ -911,13 +842,44 @@
"\n"
"</web-app>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<web-app xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
+" http://java.sun.com/xml/ns/javaee\n"
+" http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd\"\n"
+" version=\"2.5\">\n"
+"\n"
+" <listener>\n"
+" <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>\n"
+" </listener>\n"
+" \n"
+" <context-param>\n"
+" <param-name>javax.faces.DEFAULT_SUFFIX</param-name>\n"
+" <param-value>.xhtml</param-value>\n"
+" </context-param>\n"
+" \n"
+" <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>\n"
+" \n"
+" <session-config>\n"
+" <session-timeout>10</session-timeout>\n"
+" </session-config>\n"
+"\n"
+"</web-app>]]>"
#. Tag: para
#: Tutorial.xml:414
#, no-c-format
-msgid ""
-"This <literal>web.xml</literal> file configures Seam and JSF. The "
-"configuration you see here is pretty much identical in all Seam applications."
+msgid "This <literal>web.xml</literal> file configures Seam and JSF. The configuration you see here is pretty much identical in all Seam applications."
msgstr ""
#. Tag: title
@@ -929,11 +891,7 @@
#. Tag: para
#: Tutorial.xml:422
#, no-c-format
-msgid ""
-"Most Seam applications use JSF views as the presentation layer. So usually "
-"we'll need <literal>faces-config.xml</literal>. In our case, we are going to "
-"use Facelets for defining our views, so we need to tell JSF to use Facelets "
-"as its templating engine."
+msgid "Most Seam applications use JSF views as the presentation layer. So usually we'll need <literal>faces-config.xml</literal>. In our case, we are going to use Facelets for defining our views, so we need to tell JSF to use Facelets as its templating engine."
msgstr ""
#. Tag: title
@@ -960,35 +918,36 @@
" \n"
"</faces-config>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<faces-config xmlns=\"http://java.sun.com/xml/ns/javaee\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
+" http://java.sun.com/xml/ns/javaee\n"
+" http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd\"\n"
+" version=\"1.2\">\n"
+"\n"
+" <application>\n"
+" <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>\n"
+" </application>\n"
+" \n"
+"</faces-config>]]>"
#. Tag: para
#: Tutorial.xml:432
#, no-c-format
-msgid ""
-"Note that we don't need any JSF managed bean declarations! Our managed beans "
-"are annotated Seam components. In Seam applications, the <literal>faces-"
-"config.xml</literal> is used much less often than in plain JSF. Here, we are "
-"simply using it to enable Facelets as the view handler instead of JSP."
+msgid "Note that we don't need any JSF managed bean declarations! Our managed beans are annotated Seam components. In Seam applications, the <literal>faces-config.xml</literal> is used much less often than in plain JSF. Here, we are simply using it to enable Facelets as the view handler instead of JSP."
msgstr ""
#. Tag: para
#: Tutorial.xml:437
#, no-c-format
-msgid ""
-"In fact, once you have all the basic descriptors set up, the <emphasis>only</"
-"emphasis> XML you need to write as you add new functionality to a Seam "
-"application is orchestration: navigation rules or jBPM process definitions. "
-"Seam's stand is that <emphasis>process flow</emphasis> and "
-"<emphasis>configuration data</emphasis> are the only things that truly "
-"belong in XML."
+msgid "In fact, once you have all the basic descriptors set up, the <emphasis>only</emphasis> XML you need to write as you add new functionality to a Seam application is orchestration: navigation rules or jBPM process definitions. Seam's stand is that <emphasis>process flow</emphasis> and <emphasis>configuration data</emphasis> are the only things that truly belong in XML."
msgstr ""
#. Tag: para
#: Tutorial.xml:442
#, no-c-format
-msgid ""
-"In this simple example, we don't even need a navigation rule, since we "
-"decided to embed the view id in our action code."
+msgid "In this simple example, we don't even need a navigation rule, since we decided to embed the view id in our action code."
msgstr ""
#. Tag: title
@@ -1000,10 +959,7 @@
#. Tag: para
#: Tutorial.xml:450
#, no-c-format
-msgid ""
-"The <literal>ejb-jar.xml</literal> file integrates Seam with EJB3, by "
-"attaching the <literal>SeamInterceptor</literal> to all session beans in the "
-"archive."
+msgid "The <literal>ejb-jar.xml</literal> file integrates Seam with EJB3, by attaching the <literal>SeamInterceptor</literal> to all session beans in the archive."
msgstr ""
#. Tag: programlisting
@@ -1020,36 +976,52 @@
" \n"
" <interceptors>\n"
" <interceptor>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</"
-"interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
" </interceptor>\n"
" </interceptors>\n"
" \n"
" <assembly-descriptor>\n"
" <interceptor-binding>\n"
" <ejb-name>*</ejb-name>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</"
-"interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
" </interceptor-binding>\n"
" </assembly-descriptor>\n"
" \n"
"</ejb-jar>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<ejb-jar xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \n"
+" xsi:schemaLocation=\"\n"
+" http://java.sun.com/xml/ns/javaee\n"
+" http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd\"\n"
+" version=\"3.0\">\n"
+" \n"
+" <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"
+" \n"
+"</ejb-jar>]]>"
#. Tag: title
#: Tutorial.xml:458
#, no-c-format
-msgid ""
-"The EJB persistence deployment descriptor: <literal>persistence.xml</literal>"
+msgid "The EJB persistence deployment descriptor: <literal>persistence.xml</literal>"
msgstr ""
#. Tag: para
#: Tutorial.xml:460
#, no-c-format
-msgid ""
-"The <literal>persistence.xml</literal> file tells the EJB persistence "
-"provider where to find the datasource, and contains some vendor-specific "
-"settings. In this case, enables automatic schema export at startup time."
+msgid "The <literal>persistence.xml</literal> file tells the EJB persistence provider where to find the datasource, and contains some vendor-specific settings. In this case, enables automatic schema export at startup time."
msgstr ""
#. Tag: programlisting
@@ -1068,13 +1040,29 @@
" <provider>org.hibernate.ejb.HibernatePersistence</provider>\n"
" <jta-data-source>java:/DefaultDS</jta-data-source>\n"
" <properties>\n"
-" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/"
-">\n"
+" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/>\n"
" </properties>\n"
" </persistence-unit>\n"
" \n"
"</persistence>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<persistence xmlns=\"http://java.sun.com/xml/ns/persistence\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
+" http://java.sun.com/xml/ns/persistence\n"
+" http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd\" \n"
+" version=\"1.0\">\n"
+"\n"
+" <persistence-unit name=\"userDatabase\">\n"
+" <provider>org.hibernate.ejb.HibernatePersistence</provider>\n"
+" <jta-data-source>java:/DefaultDS</jta-data-source>\n"
+" <properties>\n"
+" <property name=\"hibernate.hbm2ddl.auto\" value=\"create-drop\"/>\n"
+" </properties>\n"
+" </persistence-unit>\n"
+" \n"
+"</persistence>]]>"
#. Tag: title
#: Tutorial.xml:469
@@ -1085,9 +1073,7 @@
#. Tag: para
#: Tutorial.xml:471
#, no-c-format
-msgid ""
-"Finally, since our application is deployed as an EAR, we need a deployment "
-"descriptor there, too."
+msgid "Finally, since our application is deployed as an EAR, we need a deployment descriptor there, too."
msgstr ""
#. Tag: title
@@ -1128,25 +1114,51 @@
"\n"
"</application>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<application xmlns=\"http://java.sun.com/xml/ns/javaee\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"\n"
+" http://java.sun.com/xml/ns/javaee\n"
+" http://java.sun.com/xml/ns/javaee/application_5.xsd\"\n"
+" version=\"5\">\n"
+" \n"
+" <display-name>Seam Registration</display-name>\n"
+"\n"
+" <module>\n"
+" <web>\n"
+" <web-uri>jboss-seam-registration.war</web-uri>\n"
+" <context-root>/seam-registration</context-root>\n"
+" </web>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>jboss-seam-registration.jar</ejb>\n"
+" </module>\n"
+" <module>\n"
+" <ejb>jboss-seam.jar</ejb>\n"
+" </module>\n"
+" <module>\n"
+" <java>jboss-el.jar</java>\n"
+" </module>\n"
+"\n"
+"</application>]]>"
#. Tag: para
#: Tutorial.xml:477
#, no-c-format
-msgid ""
-"This deployment descriptor links modules in the enterprise archive and binds "
-"the web application to the context root <literal>/seam-registration</"
-"literal>."
+msgid "This deployment descriptor links modules in the enterprise archive and binds the web application to the context root <literal>/seam-registration</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:480
#, no-c-format
-msgid ""
-"We've now seen <emphasis>all</emphasis> the files in the entire application!"
+msgid "We've now seen <emphasis>all</emphasis> the files in the entire application!"
msgstr ""
#. Tag: title
-#: Tutorial.xml:486 Tutorial.xml:673 Tutorial.xml:887 Tutorial.xml:1070
+#: Tutorial.xml:486
+#: Tutorial.xml:673
+#: Tutorial.xml:887
+#: Tutorial.xml:1070
#, no-c-format
msgid "How it works"
msgstr ""
@@ -1154,65 +1166,37 @@
#. Tag: para
#: Tutorial.xml:488
#, no-c-format
-msgid ""
-"When the form is submitted, JSF asks Seam to resolve the variable named "
-"<literal>user</literal>. Since there is no value already bound to that name "
-"(in any Seam context), Seam instantiates the <literal>user</literal> "
-"component, and returns the resulting <literal>User</literal> entity bean "
-"instance to JSF after storing it in the Seam session context."
+msgid "When the form is submitted, JSF asks Seam to resolve the variable named <literal>user</literal>. Since there is no value already bound to that name (in any Seam context), Seam instantiates the <literal>user</literal> component, and returns the resulting <literal>User</literal> entity bean instance to JSF after storing it in the Seam session context."
msgstr ""
#. Tag: para
#: Tutorial.xml:492
#, no-c-format
-msgid ""
-"The form input values are now validated against the Hibernate Validator "
-"constraints specified on the <literal>User</literal> entity. If the "
-"constraints are violated, JSF redisplays the page. Otherwise, JSF binds the "
-"form input values to properties of the <literal>User</literal> entity bean."
+msgid "The form input values are now validated against the Hibernate Validator constraints specified on the <literal>User</literal> entity. If the constraints are violated, JSF redisplays the page. Otherwise, JSF binds the form input values to properties of the <literal>User</literal> entity bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:495
#, no-c-format
-msgid ""
-"Next, JSF asks Seam to resolve the variable named <literal>register</"
-"literal>. Seam uses the JNDI pattern mentioned earlier to locate the "
-"stateless session bean, wraps it as a Seam component, and returns it. Seam "
-"then presents this component to JSF and JSF invokes the <literal>register()</"
-"literal> action listener method."
+msgid "Next, JSF asks Seam to resolve the variable named <literal>register</literal>. Seam uses the JNDI pattern mentioned earlier to locate the stateless session bean, wraps it as a Seam component, and returns it. Seam then presents this component to JSF and JSF invokes the <literal>register()</literal> action listener method."
msgstr ""
#. Tag: para
#: Tutorial.xml:499
#, no-c-format
-msgid ""
-"But Seam is not done yet. Seam intercepts the method call and injects the "
-"<literal>User</literal> entity from the Seam session context, before "
-"allowing the invocation to continue."
+msgid "But Seam is not done yet. Seam intercepts the method call and injects the <literal>User</literal> entity from the Seam session context, before allowing the invocation to continue."
msgstr ""
#. Tag: para
#: Tutorial.xml:501
#, no-c-format
-msgid ""
-"The <literal>register()</literal> method checks if a user with the entered "
-"username already exists. If so, an error message is queued with the "
-"<literal>FacesMessages</literal> component, and a null outcome is returned, "
-"causing a page redisplay. The <literal>FacesMessages</literal> component "
-"interpolates the JSF expression embedded in the message string and adds a "
-"JSF <literal>FacesMessage</literal> to the view."
+msgid "The <literal>register()</literal> method checks if a user with the entered username already exists. If so, an error message is queued with the <literal>FacesMessages</literal> component, and a null outcome is returned, causing a page redisplay. The <literal>FacesMessages</literal> component interpolates the JSF expression embedded in the message string and adds a JSF <literal>FacesMessage</literal> to the view."
msgstr ""
#. Tag: para
#: Tutorial.xml:506
#, no-c-format
-msgid ""
-"If no user with that username exists, the <literal>\"/registered.xhtml\"</"
-"literal> outcome triggers a browser redirect to the <literal>registered."
-"xhtml</literal> page. When JSF comes to render the page, it asks Seam to "
-"resolve the variable named <literal>user</literal> and uses property values "
-"of the returned <literal>User</literal> entity from Seam's session scope."
+msgid "If no user with that username exists, the <literal>\"/registered.xhtml\"</literal> outcome triggers a browser redirect to the <literal>registered.xhtml</literal> page. When JSF comes to render the page, it asks Seam to resolve the variable named <literal>user</literal> and uses property values of the returned <literal>User</literal> entity from Seam's session scope."
msgstr ""
#. Tag: title
@@ -1224,20 +1208,13 @@
#. Tag: para
#: Tutorial.xml:518
#, no-c-format
-msgid ""
-"Clickable lists of database search results are such an important part of any "
-"online application that Seam provides special functionality on top of JSF to "
-"make it easier to query data using EJB-QL or HQL and display it as a "
-"clickable list using a JSF <literal><h:dataTable></literal>. The "
-"messages example demonstrates this functionality."
+msgid "Clickable lists of database search results are such an important part of any online application that Seam provides special functionality on top of JSF to make it easier to query data using EJB-QL or HQL and display it as a clickable list using a JSF <literal><h:dataTable></literal>. The messages example demonstrates this functionality."
msgstr ""
#. Tag: para
#: Tutorial.xml:534
#, no-c-format
-msgid ""
-"The message list example has one entity bean, <literal>Message</literal>, "
-"one session bean, <literal>MessageListBean</literal> and one JSP."
+msgid "The message list example has one entity bean, <literal>Message</literal>, one session bean, <literal>MessageListBean</literal> and one JSP."
msgstr ""
#. Tag: title
@@ -1249,9 +1226,7 @@
#. Tag: para
#: Tutorial.xml:540
#, no-c-format
-msgid ""
-"The <literal>Message</literal> entity defines the title, text, date and time "
-"of a message, and a flag indicating whether the message has been read:"
+msgid "The <literal>Message</literal> entity defines the title, text, date and time of a message, and a flag indicating whether the message has been read:"
msgstr ""
#. Tag: title
@@ -1328,6 +1303,69 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@Entity\n"
+"@Name(\"message\")\n"
+"@Scope(EVENT)\n"
+"public class Message implements Serializable\n"
+"{\n"
+" private Long id;\n"
+" private String title;\n"
+" private String text;\n"
+" private boolean read;\n"
+" private Date datetime;\n"
+" \n"
+" @Id @GeneratedValue\n"
+" public Long getId()\n"
+" {\n"
+" return id;\n"
+" }\n"
+" public void setId(Long id)\n"
+" {\n"
+" this.id = id;\n"
+" }\n"
+" \n"
+" @NotNull @Length(max=100)\n"
+" public String getTitle()\n"
+" {\n"
+" return title;\n"
+" }\n"
+" public void setTitle(String title)\n"
+" {\n"
+" this.title = title;\n"
+" }\n"
+" \n"
+" @NotNull @Lob\n"
+" public String getText()\n"
+" {\n"
+" return text;\n"
+" }\n"
+" public void setText(String text)\n"
+" {\n"
+" this.text = text;\n"
+" }\n"
+" \n"
+" @NotNull\n"
+" public boolean isRead()\n"
+" {\n"
+" return read;\n"
+" }\n"
+" public void setRead(boolean read)\n"
+" {\n"
+" this.read = read;\n"
+" }\n"
+" \n"
+" @NotNull \n"
+" @Basic @Temporal(TemporalType.TIMESTAMP)\n"
+" public Date getDatetime()\n"
+" {\n"
+" return datetime;\n"
+" }\n"
+" public void setDatetime(Date datetime)\n"
+" {\n"
+" this.datetime = datetime;\n"
+" }\n"
+" \n"
+"}]]>"
#. Tag: title
#: Tutorial.xml:551
@@ -1338,33 +1376,19 @@
#. Tag: para
#: Tutorial.xml:553
#, no-c-format
-msgid ""
-"Just like in the previous example, we have a session bean, "
-"<literal>MessageManagerBean</literal>, which defines the action listener "
-"methods for the two buttons on our form. One of the buttons selects a "
-"message from the list, and displays that message. The other button deletes a "
-"message. So far, this is not so different to the previous example."
+msgid "Just like in the previous example, we have a session bean, <literal>MessageManagerBean</literal>, which defines the action listener methods for the two buttons on our form. One of the buttons selects a message from the list, and displays that message. The other button deletes a message. So far, this is not so different to the previous example."
msgstr ""
#. Tag: para
#: Tutorial.xml:558
#, no-c-format
-msgid ""
-"But <literal>MessageManagerBean</literal> is also responsible for fetching "
-"the list of messages the first time we navigate to the message list page. "
-"There are various ways the user could navigate to the page, and not all of "
-"them are preceded by a JSF action—the user might have bookmarked the "
-"page, for example. So the job of fetching the message list takes place in a "
-"Seam <emphasis>factory method</emphasis>, instead of in an action listener "
-"method."
+msgid "But <literal>MessageManagerBean</literal> is also responsible for fetching the list of messages the first time we navigate to the message list page. There are various ways the user could navigate to the page, and not all of them are preceded by a JSF action—the user might have bookmarked the page, for example. So the job of fetching the message list takes place in a Seam <emphasis>factory method</emphasis>, instead of in an action listener method."
msgstr ""
#. Tag: para
#: Tutorial.xml:564
#, no-c-format
-msgid ""
-"We want to cache the list of messages in memory between server requests, so "
-"we will make this a stateful session bean."
+msgid "We want to cache the list of messages in memory between server requests, so we will make this a stateful session bean."
msgstr ""
#. Tag: title
@@ -1395,8 +1419,7 @@
" @Factory(\"messageList\")\n"
" public void findMessages()\n"
" {\n"
-" messageList = em.createQuery(\"select msg from Message msg order by "
-"msg.datetime desc\")\n"
+" messageList = em.createQuery(\"select msg from Message msg order by msg.datetime desc\")\n"
" .getResultList();\n"
" }\n"
" \n"
@@ -1417,103 +1440,103 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Scope(SESSION)\n"
+"@Name(\"messageManager\")\n"
+"public class MessageManagerBean implements Serializable, MessageManager\n"
+"{\n"
+" @DataModel\n"
+" private List<Message> messageList;\n"
+" \n"
+" @DataModelSelection\n"
+" @Out(required=false)\n"
+" private Message message;\n"
+" \n"
+" @PersistenceContext(type=EXTENDED)\n"
+" private EntityManager em;\n"
+" \n"
+" @Factory(\"messageList\")\n"
+" public void findMessages()\n"
+" {\n"
+" messageList = em.createQuery(\"select msg from Message msg order by msg.datetime desc\")\n"
+" .getResultList();\n"
+" }\n"
+" \n"
+" public void select()\n"
+" {\n"
+" message.setRead(true);\n"
+" }\n"
+" \n"
+" public void delete()\n"
+" {\n"
+" messageList.remove(message);\n"
+" em.remove(message);\n"
+" message=null;\n"
+" }\n"
+" \n"
+" @Remove\n"
+" public void destroy() {}\n"
+"\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:583
#, no-c-format
-msgid ""
-"The <literal>@DataModel</literal> annotation exposes an attibute of type "
-"<literal>java.util.List</literal> to the JSF page as an instance of "
-"<literal>javax.faces.model.DataModel</literal>. This allows us to use the "
-"list in a JSF <literal><h:dataTable></literal> with clickable links "
-"for each row. In this case, the <literal>DataModel</literal> is made "
-"available in a session context variable named <literal>messageList</literal>."
+msgid "The <literal>@DataModel</literal> annotation exposes an attibute of type <literal>java.util.List</literal> to the JSF page as an instance of <literal>javax.faces.model.DataModel</literal>. This allows us to use the list in a JSF <literal><h:dataTable></literal> with clickable links for each row. In this case, the <literal>DataModel</literal> is made available in a session context variable named <literal>messageList</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:591
#, no-c-format
-msgid ""
-"The <literal>@DataModelSelection</literal> annotation tells Seam to inject "
-"the <literal>List</literal> element that corresponded to the clicked link."
+msgid "The <literal>@DataModelSelection</literal> annotation tells Seam to inject the <literal>List</literal> element that corresponded to the clicked link."
msgstr ""
#. Tag: para
#: Tutorial.xml:595
#, no-c-format
-msgid ""
-"The <literal>@Out</literal> annotation then exposes the selected value "
-"directly to the page. So ever time a row of the clickable list is selected, "
-"the <literal>Message</literal> is injected to the attribute of the stateful "
-"bean, and the subsequently <emphasis>outjected</emphasis> to the event "
-"context variable named <literal>message</literal>."
+msgid "The <literal>@Out</literal> annotation then exposes the selected value directly to the page. So ever time a row of the clickable list is selected, the <literal>Message</literal> is injected to the attribute of the stateful bean, and the subsequently <emphasis>outjected</emphasis> to the event context variable named <literal>message</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:602
#, no-c-format
-msgid ""
-"This stateful bean has an EJB3 <emphasis>extended persistence context</"
-"emphasis>. The messages retrieved in the query remain in the managed state "
-"as long as the bean exists, so any subsequent method calls to the stateful "
-"bean can update them without needing to make any explicit call to the "
-"<literal>EntityManager</literal>."
+msgid "This stateful bean has an EJB3 <emphasis>extended persistence context</emphasis>. The messages retrieved in the query remain in the managed state as long as the bean exists, so any subsequent method calls to the stateful bean can update them without needing to make any explicit call to the <literal>EntityManager</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:608
#, no-c-format
-msgid ""
-"The first time we navigate to the JSP page, there will be no value in the "
-"<literal>messageList</literal> context variable. The <literal>@Factory</"
-"literal> annotation tells Seam to create an instance of "
-"<literal>MessageManagerBean</literal> and invoke the <literal>findMessages()"
-"</literal> method to initialize the value. We call <literal>findMessages()</"
-"literal> a <emphasis>factory method</emphasis> for <literal>messages</"
-"literal>."
+msgid "The first time we navigate to the JSP page, there will be no value in the <literal>messageList</literal> context variable. The <literal>@Factory</literal> annotation tells Seam to create an instance of <literal>MessageManagerBean</literal> and invoke the <literal>findMessages()</literal> method to initialize the value. We call <literal>findMessages()</literal> a <emphasis>factory method</emphasis> for <literal>messages</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:616
#, no-c-format
-msgid ""
-"The <literal>select()</literal> action listener method marks the selected "
-"<literal>Message</literal> as read, and updates it in the database."
+msgid "The <literal>select()</literal> action listener method marks the selected <literal>Message</literal> as read, and updates it in the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:620
#, no-c-format
-msgid ""
-"The <literal>delete()</literal> action listener method removes the selected "
-"<literal>Message</literal> from the database."
+msgid "The <literal>delete()</literal> action listener method removes the selected <literal>Message</literal> from the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:624
#, no-c-format
-msgid ""
-"All stateful session bean Seam components <emphasis>must</emphasis> have a "
-"method with no parameters marked <literal>@Remove</literal> that Seam uses "
-"to remove the stateful bean when the Seam context ends, and clean up any "
-"server-side state."
+msgid "All stateful session bean Seam components <emphasis>must</emphasis> have a method with no parameters marked <literal>@Remove</literal> that Seam uses to remove the stateful bean when the Seam context ends, and clean up any server-side state."
msgstr ""
#. Tag: para
#: Tutorial.xml:633
#, no-c-format
-msgid ""
-"Note that this is a session-scoped Seam component. It is associated with the "
-"user login session, and all requests from a login session share the same "
-"instance of the component. (In Seam applications, we usually use session-"
-"scoped components sparingly.)"
+msgid "Note that this is a session-scoped Seam component. It is associated with the user login session, and all requests from a login session share the same instance of the component. (In Seam applications, we usually use session-scoped components sparingly.)"
msgstr ""
#. Tag: title
#: Tutorial.xml:640
#, no-c-format
-msgid ""
-"The session bean local interface: <literal>MessageManager.java</literal>"
+msgid "The session bean local interface: <literal>MessageManager.java</literal>"
msgstr ""
#. Tag: para
@@ -1541,6 +1564,14 @@
" public void destroy();\n"
"}]]>"
msgstr ""
+"<![CDATA[@Local\n"
+"public interface MessageManager\n"
+"{\n"
+" public void findMessages();\n"
+" public void select();\n"
+" public void delete();\n"
+" public void destroy();\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:648
@@ -1551,12 +1582,7 @@
#. Tag: para
#: Tutorial.xml:650
#, no-c-format
-msgid ""
-"Let's skip over <literal>components.xml</literal>, <literal>persistence.xml</"
-"literal>, <literal>web.xml</literal>, <literal>ejb-jar.xml</literal>, "
-"<literal>faces-config.xml</literal> and <literal>application.xml</literal> "
-"since they are much the same as the previous example, and go straight to the "
-"JSP."
+msgid "Let's skip over <literal>components.xml</literal>, <literal>persistence.xml</literal>, <literal>web.xml</literal>, <literal>ejb-jar.xml</literal>, <literal>faces-config.xml</literal> and <literal>application.xml</literal> since they are much the same as the previous example, and go straight to the JSP."
msgstr ""
#. Tag: title
@@ -1568,9 +1594,7 @@
#. Tag: para
#: Tutorial.xml:660
#, no-c-format
-msgid ""
-"The JSP page is a straightforward use of the JSF <literal><h:dataTable>"
-"</literal> component. Again, nothing specific to Seam."
+msgid "The JSP page is a straightforward use of the JSF <literal><h:dataTable></literal> component. Again, nothing specific to Seam."
msgstr ""
#. Tag: title
@@ -1601,28 +1625,24 @@
" <f:facet name=\"header\">\n"
" <h:outputText value=\"Read\"/>\n"
" </f:facet>\n"
-" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/"
-">\n"
+" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/>\n"
" </h:column>\n"
" <h:column>\n"
" <f:facet name=\"header\">\n"
" <h:outputText value=\"Title\"/>\n"
" </f:facet>\n"
-" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager."
-"select}\"/>\n"
+" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager.select}\"/>\n"
" </h:column>\n"
" <h:column>\n"
" <f:facet name=\"header\">\n"
" <h:outputText value=\"Date/Time\"/>\n"
" </f:facet>\n"
" <h:outputText value=\"#{msg.datetime}\">\n"
-" <f:convertDateTime type=\"both\" dateStyle=\"medium\" "
-"timeStyle=\"short\"/>\n"
+" <f:convertDateTime type=\"both\" dateStyle=\"medium\" timeStyle=\"short\"/>\n"
" </h:outputText>\n"
" </h:column>\n"
" <h:column>\n"
-" <h:commandButton value=\"Delete\" action=\"#{messageManager."
-"delete}\"/>\n"
+" <h:commandButton value=\"Delete\" action=\"#{messageManager.delete}\"/>\n"
" </h:column>\n"
" </h:dataTable>\n"
" <h3><h:outputText value=\"#{message.title}\"/></h3>\n"
@@ -1632,51 +1652,67 @@
" </body>\n"
"</html>]]>"
msgstr ""
+"<![CDATA[<%@ taglib uri=\"http://java.sun.com/jsf/html\" prefix=\"h\" %>\n"
+"<%@ taglib uri=\"http://java.sun.com/jsf/core\" prefix=\"f\" %>\n"
+"<html>\n"
+" <head>\n"
+" <title>Messages</title>\n"
+" </head>\n"
+" <body>\n"
+" <f:view>\n"
+" <h:form>\n"
+" <h2>Message List</h2>\n"
+" <h:outputText value=\"No messages to display\" \n"
+" rendered=\"#{messageList.rowCount==0}\"/>\n"
+" <h:dataTable var=\"msg\" value=\"#{messageList}\" \n"
+" rendered=\"#{messageList.rowCount>0}\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Read\"/>\n"
+" </f:facet>\n"
+" <h:selectBooleanCheckbox value=\"#{msg.read}\" disabled=\"true\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Title\"/>\n"
+" </f:facet>\n"
+" <h:commandLink value=\"#{msg.title}\" action=\"#{messageManager.select}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Date/Time\"/>\n"
+" </f:facet>\n"
+" <h:outputText value=\"#{msg.datetime}\">\n"
+" <f:convertDateTime type=\"both\" dateStyle=\"medium\" timeStyle=\"short\"/>\n"
+" </h:outputText>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <h:commandButton value=\"Delete\" action=\"#{messageManager.delete}\"/>\n"
+" </h:column>\n"
+" </h:dataTable>\n"
+" <h3><h:outputText value=\"#{message.title}\"/></h3>\n"
+" <div><h:outputText value=\"#{message.text}\"/></div>\n"
+" </h:form>\n"
+" </f:view>\n"
+" </body>\n"
+"</html>]]>"
#. Tag: para
#: Tutorial.xml:675
#, no-c-format
-msgid ""
-"The first time we navigate to the <literal>messages.jsp</literal> page, the "
-"page will try to resolve the <literal>messageList</literal> context "
-"variable. Since this context variable is not initialized, Seam will call the "
-"factory method <literal>findMessages()</literal>, which performs a query "
-"against the database and results in a <literal>DataModel</literal> being "
-"outjected. This <literal>DataModel</literal> provides the row data needed "
-"for rendering the <literal><h:dataTable></literal>."
+msgid "The first time we navigate to the <literal>messages.jsp</literal> page, the page will try to resolve the <literal>messageList</literal> context variable. Since this context variable is not initialized, Seam will call the factory method <literal>findMessages()</literal>, which performs a query against the database and results in a <literal>DataModel</literal> being outjected. This <literal>DataModel</literal> provides the row data needed for rendering the <literal><h:dataTable></literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:682
#, no-c-format
-msgid ""
-"When the user clicks the <literal><h:commandLink></literal>, JSF calls "
-"the <literal>select()</literal> action listener. Seam intercepts this call "
-"and injects the selected row data into the <literal>message</literal> "
-"attribute of the <literal>messageManager</literal> component. The action "
-"listener fires, marking the selected <literal>Message</literal> as read. At "
-"the end of the call, Seam outjects the selected <literal>Message</literal> "
-"to the context variable named <literal>message</literal>. Next, the EJB "
-"container commits the transaction, and the change to the <literal>Message</"
-"literal> is flushed to the database. Finally, the page is re-rendered, "
-"redisplaying the message list, and displaying the selected message below it."
+msgid "When the user clicks the <literal><h:commandLink></literal>, JSF calls the <literal>select()</literal> action listener. Seam intercepts this call and injects the selected row data into the <literal>message</literal> attribute of the <literal>messageManager</literal> component. The action listener fires, marking the selected <literal>Message</literal> as read. At the end of the call, Seam outjects the selected <literal>Message</literal> to the context variable named <literal>message</literal>. Next, the EJB container commits the transaction, and the change to the <literal>Message</literal> is flushed to the database. Finally, the page is re-rendered, redisplaying the message list, and displaying the selected message below it."
msgstr ""
#. Tag: para
#: Tutorial.xml:691
#, no-c-format
-msgid ""
-"If the user clicks the <literal><h:commandButton></literal>, JSF calls "
-"the <literal>delete()</literal> action listener. Seam intercepts this call "
-"and injects the selected row data into the <literal>message</literal> "
-"attribute of the <literal>messageList</literal> component. The action "
-"listener fires, removing the selected <literal>Message</literal> from the "
-"list, and also calling <literal>remove()</literal> on the "
-"<literal>EntityManager</literal>. At the end of the call, Seam refreshes the "
-"<literal>messageList</literal> context variable and clears the context "
-"variable named <literal>message</literal>. The EJB container commits the "
-"transaction, and deletes the <literal>Message</literal> from the database. "
-"Finally, the page is re-rendered, redisplaying the message list."
+msgid "If the user clicks the <literal><h:commandButton></literal>, JSF calls the <literal>delete()</literal> action listener. Seam intercepts this call and injects the selected row data into the <literal>message</literal> attribute of the <literal>messageList</literal> component. The action listener fires, removing the selected <literal>Message</literal> from the list, and also calling <literal>remove()</literal> on the <literal>EntityManager</literal>. At the end of the call, Seam refreshes the <literal>messageList</literal> context variable and clears the context variable named <literal>message</literal>. The EJB container commits the transaction, and deletes the <literal>Message</literal> from the database. Finally, the page is re-rendered, redisplaying the message list."
msgstr ""
#. Tag: title
@@ -1688,21 +1724,13 @@
#. Tag: para
#: Tutorial.xml:708
#, no-c-format
-msgid ""
-"jBPM provides sophisticated functionality for workflow and task management. "
-"To get a small taste of how jBPM integrates with Seam, we'll show you a "
-"simple \"todo list\" application. Since managing lists of tasks is such core "
-"functionality for jBPM, there is hardly any Java code at all in this example."
+msgid "jBPM provides sophisticated functionality for workflow and task management. To get a small taste of how jBPM integrates with Seam, we'll show you a simple \"todo list\" application. Since managing lists of tasks is such core functionality for jBPM, there is hardly any Java code at all in this example."
msgstr ""
#. Tag: para
#: Tutorial.xml:723
#, no-c-format
-msgid ""
-"The center of this example is the jBPM process definition. There are also "
-"two JSPs and two trivial JavaBeans (There was no reason to use session "
-"beans, since they do not access the database, or have any other "
-"transactional behavior). Let's start with the process definition:"
+msgid "The center of this example is the jBPM process definition. There are also two JSPs and two trivial JavaBeans (There was no reason to use session beans, since they do not access the database, or have any other transactional behavior). Let's start with the process definition:"
msgstr ""
#. Tag: title
@@ -1732,88 +1760,76 @@
" \n"
"</process-definition>]]>"
msgstr ""
+"<![CDATA[<process-definition name=\"todo\">\n"
+" \n"
+" <start-state name=\"start\">\n"
+" <transition to=\"todo\"/>\n"
+" </start-state>\n"
+" \n"
+" <task-node name=\"todo\">\n"
+" <task name=\"todo\" description=\"#{todoList.description}\">\n"
+" <assignment actor-id=\"#{actor.id}\"/>\n"
+" </task>\n"
+" <transition to=\"done\"/>\n"
+" </task-node>\n"
+" \n"
+" <end-state name=\"done\"/>\n"
+" \n"
+"</process-definition>]]>"
#. Tag: para
#: Tutorial.xml:740
#, no-c-format
-msgid ""
-"The <literal><start-state></literal> node represents the logical start "
-"of the process. When the process starts, it immediately transitions to the "
-"<literal>todo</literal> node."
+msgid "The <literal><start-state></literal> node represents the logical start of the process. When the process starts, it immediately transitions to the <literal>todo</literal> node."
msgstr ""
#. Tag: para
#: Tutorial.xml:745
#, no-c-format
-msgid ""
-"The <literal><task-node></literal> node represents a <emphasis>wait "
-"state</emphasis>, where business process execution pauses, waiting for one "
-"or more tasks to be performed."
+msgid "The <literal><task-node></literal> node represents a <emphasis>wait state</emphasis>, where business process execution pauses, waiting for one or more tasks to be performed."
msgstr ""
#. Tag: para
#: Tutorial.xml:750
#, no-c-format
-msgid ""
-"The <literal><task></literal> element defines a task to be performed "
-"by a user. Since there is only one task defined on this node, when it is "
-"complete, execution resumes, and we transition to the end state. The task "
-"gets its description from a Seam component named <literal>todoList</literal> "
-"(one of the JavaBeans)."
+msgid "The <literal><task></literal> element defines a task to be performed by a user. Since there is only one task defined on this node, when it is complete, execution resumes, and we transition to the end state. The task gets its description from a Seam component named <literal>todoList</literal> (one of the JavaBeans)."
msgstr ""
#. Tag: para
#: Tutorial.xml:756
#, no-c-format
-msgid ""
-"Tasks need to be assigned to a user or group of users when they are created. "
-"In this case, the task is assigned to the current user, which we get from a "
-"built-in Seam component named <literal>actor</literal>. Any Seam component "
-"may be used to perform task assignment."
+msgid "Tasks need to be assigned to a user or group of users when they are created. In this case, the task is assigned to the current user, which we get from a built-in Seam component named <literal>actor</literal>. Any Seam component may be used to perform task assignment."
msgstr ""
#. Tag: para
#: Tutorial.xml:762
#, no-c-format
-msgid ""
-"The <literal><end-state></literal> node defines the logical end of the "
-"business process. When execution reaches this node, the process instance is "
-"destroyed."
+msgid "The <literal><end-state></literal> node defines the logical end of the business process. When execution reaches this node, the process instance is destroyed."
msgstr ""
#. Tag: para
#: Tutorial.xml:771
#, no-c-format
-msgid ""
-"If we view this process definition using the process definition editor "
-"provided by JBossIDE, this is what it looks like:"
+msgid "If we view this process definition using the process definition editor provided by JBossIDE, this is what it looks like:"
msgstr ""
#. Tag: para
#: Tutorial.xml:783
#, no-c-format
-msgid ""
-"This document defines our <emphasis>business process</emphasis> as a graph "
-"of nodes. This is the most trivial possible business process: there is one "
-"<emphasis>task</emphasis> to be performed, and when that task is complete, "
-"the business process ends."
+msgid "This document defines our <emphasis>business process</emphasis> as a graph of nodes. This is the most trivial possible business process: there is one <emphasis>task</emphasis> to be performed, and when that task is complete, the business process ends."
msgstr ""
#. Tag: para
#: Tutorial.xml:787
#, no-c-format
-msgid ""
-"The first JavaBean handles the login screen <literal>login.jsp</literal>. "
-"Its job is just to initialize the jBPM actor id using the <literal>actor</"
-"literal> component. In a real application, it would also need to "
-"authenticate the user."
+msgid "The first JavaBean handles the login screen <literal>login.jsp</literal>. Its job is just to initialize the jBPM actor id using the <literal>actor</literal> component. In a real application, it would also need to authenticate the user."
msgstr ""
#. Tag: title
#: Tutorial.xml:791
#, no-c-format
msgid "Login.java"
-msgstr ""
+msgstr "Login.java"
#. Tag: programlisting
#: Tutorial.xml:792
@@ -1844,13 +1860,35 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"login\")\n"
+"public class Login\n"
+"{\n"
+" @In\n"
+" private Actor actor;\n"
+" \n"
+" private String user;\n"
+"\n"
+" public String getUser()\n"
+" {\n"
+" return user;\n"
+" }\n"
+"\n"
+" public void setUser(String user)\n"
+" {\n"
+" this.user = user;\n"
+" }\n"
+" \n"
+" public String login()\n"
+" {\n"
+" actor.setId(user);\n"
+" return \"/todo.jsp\";\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:796
#, no-c-format
-msgid ""
-"Here we see the use of <literal>@In</literal> to inject the built-in "
-"<literal>Actor</literal> component."
+msgid "Here we see the use of <literal>@In</literal> to inject the built-in <literal>Actor</literal> component."
msgstr ""
#. Tag: para
@@ -1863,7 +1901,7 @@
#: Tutorial.xml:802
#, no-c-format
msgid "login.jsp"
-msgstr ""
+msgstr "login.jsp"
#. Tag: programlisting
#: Tutorial.xml:803
@@ -1888,20 +1926,36 @@
"</body>\n"
"</html>]]>"
msgstr ""
+"<![CDATA[<%@ taglib uri=\"http://java.sun.com/jsf/html\" prefix=\"h\"%>\n"
+"<%@ taglib uri=\"http://java.sun.com/jsf/core\" prefix=\"f\"%>\n"
+"<html>\n"
+"<head>\n"
+"<title>Login</title>\n"
+"</head>\n"
+"<body>\n"
+"<h1>Login</h1>\n"
+"<f:view>\n"
+" <h:form>\n"
+" <div>\n"
+" <h:inputText value=\"#{login.user}\"/>\n"
+" <h:commandButton value=\"Login\" action=\"#{login.login}\"/>\n"
+" </div>\n"
+" </h:form>\n"
+"</f:view>\n"
+"</body>\n"
+"</html>]]>"
#. Tag: para
#: Tutorial.xml:807
#, no-c-format
-msgid ""
-"The second JavaBean is responsible for starting business process instances, "
-"and ending tasks."
+msgid "The second JavaBean is responsible for starting business process instances, and ending tasks."
msgstr ""
#. Tag: title
#: Tutorial.xml:811
#, no-c-format
msgid "TodoList.java"
-msgstr ""
+msgstr "TodoList.java"
#. Tag: programlisting
#: Tutorial.xml:818
@@ -1930,40 +1984,51 @@
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"todoList\")\n"
+"public class TodoList\n"
+"{\n"
+" private String description;\n"
+" \n"
+" public String getDescription()\n"
+" {\n"
+" return description;\n"
+" }\n"
+"\n"
+" public void setDescription(String description)\n"
+" {\n"
+" this.description = description;\n"
+" }\n"
+" \n"
+" @CreateProcess(definition=\"todo\")\n"
+" public void createTodo() {}\n"
+" \n"
+" @StartTask @EndTask\n"
+" public void done() {}\n"
+"\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:821
#, no-c-format
-msgid ""
-"The description property accepts user input form the JSP page, and exposes "
-"it to the process definition, allowing the task description to be set."
+msgid "The description property accepts user input form the JSP page, and exposes it to the process definition, allowing the task description to be set."
msgstr ""
#. Tag: para
#: Tutorial.xml:825
#, no-c-format
-msgid ""
-"The Seam <literal>@CreateProcess</literal> annotation creates a new jBPM "
-"process instance for the named process definition."
+msgid "The Seam <literal>@CreateProcess</literal> annotation creates a new jBPM process instance for the named process definition."
msgstr ""
#. Tag: para
#: Tutorial.xml:829
#, no-c-format
-msgid ""
-"The Seam <literal>@StartTask</literal> annotation starts work on a task. The "
-"<literal>@EndTask</literal> ends the task, and allows the business process "
-"execution to resume."
+msgid "The Seam <literal>@StartTask</literal> annotation starts work on a task. The <literal>@EndTask</literal> ends the task, and allows the business process execution to resume."
msgstr ""
#. Tag: para
#: Tutorial.xml:838
#, no-c-format
-msgid ""
-"In a more realistic example, <literal>@StartTask</literal> and "
-"<literal>@EndTask</literal> would not appear on the same method, because "
-"there is usually work to be done using the application in order to complete "
-"the task."
+msgid "In a more realistic example, <literal>@StartTask</literal> and <literal>@EndTask</literal> would not appear on the same method, because there is usually work to be done using the application in order to complete the task."
msgstr ""
#. Tag: para
@@ -1973,10 +2038,11 @@
msgstr ""
#. Tag: title
-#: Tutorial.xml:844 Tutorial.xml:854
+#: Tutorial.xml:844
+#: Tutorial.xml:854
#, no-c-format
msgid "todo.jsp"
-msgstr ""
+msgstr "todo.jsp"
#. Tag: programlisting
#: Tutorial.xml:845
@@ -2008,8 +2074,7 @@
" <f:facet name=\"header\">\n"
" <h:outputText value=\"Created\"/>\n"
" </f:facet>\n"
-" <h:outputText value=\"#{task.taskMgmtInstance."
-"processInstance.start}\">\n"
+" <h:outputText value=\"#{task.taskMgmtInstance.processInstance.start}\">\n"
" <f:convertDateTime type=\"date\"/>\n"
" </h:outputText>\n"
" </h:column>\n"
@@ -2017,21 +2082,18 @@
" <f:facet name=\"header\">\n"
" <h:outputText value=\"Priority\"/>\n"
" </f:facet>\n"
-" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/"
-">\n"
+" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/>\n"
" </h:column>\n"
" <h:column>\n"
" <f:facet name=\"header\">\n"
" <h:outputText value=\"Due Date\"/>\n"
" </f:facet>\n"
-" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100"
-"\">\n"
+" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100\">\n"
" <f:convertDateTime type=\"date\" dateStyle=\"short\"/>\n"
" </h:inputText>\n"
" </h:column>\n"
" <h:column>\n"
-" <s:button value=\"Done\" action=\"#{todoList.done}\" "
-"taskInstance=\"#{task}\"/>\n"
+" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n"
" </h:column>\n"
" </h:dataTable>\n"
" </div>\n"
@@ -2045,14 +2107,78 @@
" <h:form id=\"new\">\n"
" <div>\n"
" <h:inputText value=\"#{todoList.description}\"/>\n"
-" <h:commandButton value=\"Create New Item\" action=\"#{todoList."
-"createTodo}\"/>\n"
+" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n"
" </div>\n"
" </h:form>\n"
"</f:view>\n"
"</body>\n"
"</html>]]>"
msgstr ""
+"<![CDATA[<%@ taglib uri=\"http://java.sun.com/jsf/html\" prefix=\"h\" %>\n"
+"<%@ taglib uri=\"http://java.sun.com/jsf/core\" prefix=\"f\" %>\n"
+"<%@ taglib uri=\"http://jboss.com/products/seam/taglib\" prefix=\"s\" %>\n"
+"<html>\n"
+"<head>\n"
+"<title>Todo List</title>\n"
+"</head>\n"
+"<body>\n"
+"<h1>Todo List</h1>\n"
+"<f:view>\n"
+" <h:form id=\"list\">\n"
+" <div>\n"
+" <h:outputText value=\"There are no todo items.\" \n"
+" rendered=\"#{empty taskInstanceList}\"/>\n"
+" <h:dataTable value=\"#{taskInstanceList}\" var=\"task\" \n"
+" rendered=\"#{not empty taskInstanceList}\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Description\"/>\n"
+" </f:facet>\n"
+" <h:inputText value=\"#{task.description}\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Created\"/>\n"
+" </f:facet>\n"
+" <h:outputText value=\"#{task.taskMgmtInstance.processInstance.start}\">\n"
+" <f:convertDateTime type=\"date\"/>\n"
+" </h:outputText>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Priority\"/>\n"
+" </f:facet>\n"
+" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Due Date\"/>\n"
+" </f:facet>\n"
+" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100\">\n"
+" <f:convertDateTime type=\"date\" dateStyle=\"short\"/>\n"
+" </h:inputText>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n"
+" </h:column>\n"
+" </h:dataTable>\n"
+" </div>\n"
+" <div>\n"
+" <h:messages/>\n"
+" </div>\n"
+" <div>\n"
+" <h:commandButton value=\"Update Items\" action=\"update\"/>\n"
+" </div>\n"
+" </h:form>\n"
+" <h:form id=\"new\">\n"
+" <div>\n"
+" <h:inputText value=\"#{todoList.description}\"/>\n"
+" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n"
+" </div>\n"
+" </h:form>\n"
+"</f:view>\n"
+"</body>\n"
+"</html>]]>"
#. Tag: para
#: Tutorial.xml:849
@@ -2063,10 +2189,7 @@
#. Tag: para
#: Tutorial.xml:851
#, no-c-format
-msgid ""
-"The page renders a list of tasks, which it gets from a built-in Seam "
-"component named <literal>taskInstanceList</literal>. The list is defined "
-"inside a JSF form."
+msgid "The page renders a list of tasks, which it gets from a built-in Seam component named <literal>taskInstanceList</literal>. The list is defined inside a JSF form."
msgstr ""
#. Tag: programlisting
@@ -2075,8 +2198,7 @@
msgid ""
"<![CDATA[<h:form id=\"list\">\n"
" <div>\n"
-" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty "
-"taskInstanceList}\"/>\n"
+" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty taskInstanceList}\"/>\n"
" <h:dataTable value=\"#{taskInstanceList}\" var=\"task\" \n"
" rendered=\"#{not empty taskInstanceList}\">\n"
" ...\n"
@@ -2084,16 +2206,20 @@
" </div>\n"
"</h:form>]]>"
msgstr ""
+"<![CDATA[<h:form id=\"list\">\n"
+" <div>\n"
+" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty taskInstanceList}\"/>\n"
+" <h:dataTable value=\"#{taskInstanceList}\" var=\"task\" \n"
+" rendered=\"#{not empty taskInstanceList}\">\n"
+" ...\n"
+" </h:dataTable>\n"
+" </div>\n"
+"</h:form>]]>"
#. Tag: para
#: Tutorial.xml:858
#, no-c-format
-msgid ""
-"Each element of the list is an instance of the jBPM class "
-"<literal>TaskInstance</literal>. The following code simply displays the "
-"interesting properties of each task in the list. For the description, "
-"priority and due date, we use input controls, to allow the user to update "
-"these values."
+msgid "Each element of the list is an instance of the jBPM class <literal>TaskInstance</literal>. The following code simply displays the interesting properties of each task in the list. For the description, priority and due date, we use input controls, to allow the user to update these values."
msgstr ""
#. Tag: programlisting
@@ -2129,14 +2255,39 @@
" </h:inputText>\n"
"</h:column>]]>"
msgstr ""
+"<![CDATA[<h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Description\"/>\n"
+" </f:facet>\n"
+" <h:inputText value=\"#{task.description}\"/>\n"
+"</h:column>\n"
+"<h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Created\"/>\n"
+" </f:facet>\n"
+" <h:outputText value=\"#{task.taskMgmtInstance.processInstance.start}\">\n"
+" <f:convertDateTime type=\"date\"/>\n"
+" </h:outputText>\n"
+"</h:column>\n"
+"<h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Priority\"/>\n"
+" </f:facet>\n"
+" <h:inputText value=\"#{task.priority}\" style=\"width: 30\"/>\n"
+"</h:column>\n"
+"<h:column>\n"
+" <f:facet name=\"header\">\n"
+" <h:outputText value=\"Due Date\"/>\n"
+" </f:facet>\n"
+" <h:inputText value=\"#{task.dueDate}\" style=\"width: 100\">\n"
+" <f:convertDateTime type=\"date\" dateStyle=\"short\"/>\n"
+" </h:inputText>\n"
+"</h:column>]]>"
#. Tag: para
#: Tutorial.xml:865
#, no-c-format
-msgid ""
-"This button ends the task by calling the action method annotated "
-"<literal>@StartTask @EndTask</literal>. It passes the task id to Seam as a "
-"request parameter:"
+msgid "This button ends the task by calling the action method annotated <literal>@StartTask @EndTask</literal>. It passes the task id to Seam as a request parameter:"
msgstr ""
#. Tag: programlisting
@@ -2144,34 +2295,29 @@
#, no-c-format
msgid ""
"<![CDATA[<h:column>\n"
-" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#"
-"{task}\"/>\n"
+" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n"
"</h:column>]]>"
msgstr ""
+"<![CDATA[<h:column>\n"
+" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n"
+"</h:column>]]>"
#. Tag: para
#: Tutorial.xml:870
#, no-c-format
-msgid ""
-"Note that this is using a Seam <literal><s:button></literal> JSF "
-"control from the <literal>seam-ui.jar</literal> package. This button is used "
-"to update the properties of the tasks. When the form is submitted, Seam and "
-"jBPM will make any changes to the tasks persistent. There is no need for any "
-"action listener method:"
+msgid "Note that this is using a Seam <literal><s:button></literal> JSF control from the <literal>seam-ui.jar</literal> package. This button is used to update the properties of the tasks. When the form is submitted, Seam and jBPM will make any changes to the tasks persistent. There is no need for any action listener method:"
msgstr ""
#. Tag: programlisting
#: Tutorial.xml:875
#, no-c-format
msgid "<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>"
#. Tag: para
#: Tutorial.xml:877
#, no-c-format
-msgid ""
-"A second form on the page is used to create new items, by calling the action "
-"method annotated <literal>@CreateProcess</literal>."
+msgid "A second form on the page is used to create new items, by calling the action method annotated <literal>@CreateProcess</literal>."
msgstr ""
#. Tag: programlisting
@@ -2181,72 +2327,45 @@
"<![CDATA[<h:form id=\"new\">\n"
" <div>\n"
" <h:inputText value=\"#{todoList.description}\"/>\n"
-" <h:commandButton value=\"Create New Item\" action=\"#{todoList."
-"createTodo}\"/>\n"
+" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n"
" </div>\n"
"</h:form>]]>"
msgstr ""
+"<![CDATA[<h:form id=\"new\">\n"
+" <div>\n"
+" <h:inputText value=\"#{todoList.description}\"/>\n"
+" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n"
+" </div>\n"
+"</h:form>]]>"
#. Tag: para
#: Tutorial.xml:888
#, no-c-format
-msgid ""
-"After logging in, todo.jsp uses the <literal>taskInstanceList</literal> "
-"component to display a table of outstanding todo items for a the current "
-"user. Initially there are none. It also presents a form to enter a new "
-"entry. When the user types the todo item and hits the \"Create New Item\" "
-"button, <literal>#{todoList.createTodo}</literal> is called. This starts the "
-"todo process, as defined in <literal>todo.jpdl.xml</literal>."
+msgid "After logging in, todo.jsp uses the <literal>taskInstanceList</literal> component to display a table of outstanding todo items for a the current user. Initially there are none. It also presents a form to enter a new entry. When the user types the todo item and hits the \"Create New Item\" button, <literal>#{todoList.createTodo}</literal> is called. This starts the todo process, as defined in <literal>todo.jpdl.xml</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:894
#, no-c-format
-msgid ""
-"The process instance is created, starting in the start state and immediately "
-"transition to the <literal>todo</literal> state, where a new task is "
-"created. The task description is set based on the user's input, which was "
-"saved to <literal>#{todoList.description}</literal>. Then, the task is "
-"assigned to the current user, which was stored in the seam actor component. "
-"Note that in this example, the process has no extra process state. All the "
-"state in this example is stored in the task definition. The process and task "
-"information is stored in the database at the end of the request."
+msgid "The process instance is created, starting in the start state and immediately transition to the <literal>todo</literal> state, where a new task is created. The task description is set based on the user's input, which was saved to <literal>#{todoList.description}</literal>. Then, the task is assigned to the current user, which was stored in the seam actor component. Note that in this example, the process has no extra process state. All the state in this example is stored in the task definition. The process and task information is stored in the database at the end of the request."
msgstr ""
#. Tag: para
#: Tutorial.xml:905
#, no-c-format
-msgid ""
-"When <literal>todo.jsp</literal> is redisplayed, <literal>taskInstanceList</"
-"literal> now finds the task that was just created. The task is shown in an "
-"<literal>h:dataTable</literal>. The internal state of the task is displayed "
-"in each column: <literal>#{task.description}</literal>, <literal>#{task."
-"priority}</literal>, <literal>#{task.dueDate}</literal>, etc... These fields "
-"can all be edited and saved back to the database."
+msgid "When <literal>todo.jsp</literal> is redisplayed, <literal>taskInstanceList</literal> now finds the task that was just created. The task is shown in an <literal>h:dataTable</literal>. The internal state of the task is displayed in each column: <literal>#{task.description}</literal>, <literal>#{task.priority}</literal>, <literal>#{task.dueDate}</literal>, etc... These fields can all be edited and saved back to the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:915
#, no-c-format
-msgid ""
-"Each todo item also has \"Done\" button, which calls <literal>#{todoList."
-"done}</literal>. The <literal>todoList</literal> component knows which task "
-"the button is for because each s:button specificies <literal>taskInstance=\"#"
-"{task}\"</literal>, referring to the task for that particular line of of the "
-"table. The <literal>@StartTast</literal> and <literal>@EndTask</literal> "
-"annotations cause seam to make the task active and immediately complete the "
-"task. The original process then transitions into the <literal>done</literal> "
-"state, according to the process definition, where it ends. The state of the "
-"task and process are both updated in the database."
+msgid "Each todo item also has \"Done\" button, which calls <literal>#{todoList.done}</literal>. The <literal>todoList</literal> component knows which task the button is for because each s:button specificies <literal>taskInstance=\"#{task}\"</literal>, referring to the task for that particular line of of the table. The <literal>@StartTast</literal> and <literal>@EndTask</literal> annotations cause seam to make the task active and immediately complete the task. The original process then transitions into the <literal>done</literal> state, according to the process definition, where it ends. The state of the task and process are both updated in the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:926
#, no-c-format
-msgid ""
-"When <literal>todo.jsp</literal> is displayed again, the now-completed task "
-"is no longer displayed in the <literal>taskInstanceList</literal>, since "
-"that component only display active tasks for the user."
+msgid "When <literal>todo.jsp</literal> is displayed again, the now-completed task is no longer displayed in the <literal>taskInstanceList</literal>, since that component only display active tasks for the user."
msgstr ""
#. Tag: title
@@ -2258,37 +2377,26 @@
#. Tag: para
#: Tutorial.xml:936
#, no-c-format
-msgid ""
-"For Seam applications with relatively freeform (ad hoc) navigation, JSF/Seam "
-"navigation rules are a perfectly good way to define the page flow. For "
-"applications with a more constrained style of navigation, especially for "
-"user interfaces which are more stateful, navigation rules make it difficult "
-"to really understand the flow of the system. To understand the flow, you "
-"need to piece it together from the view pages, the actions and the "
-"navigation rules."
+msgid "For Seam applications with relatively freeform (ad hoc) navigation, JSF/Seam navigation rules are a perfectly good way to define the page flow. For applications with a more constrained style of navigation, especially for user interfaces which are more stateful, navigation rules make it difficult to really understand the flow of the system. To understand the flow, you need to piece it together from the view pages, the actions and the navigation rules."
msgstr ""
#. Tag: para
#: Tutorial.xml:942
#, no-c-format
-msgid ""
-"Seam allows you to use a jPDL process definition to define pageflow. The "
-"simple number guessing example shows how this is done."
+msgid "Seam allows you to use a jPDL process definition to define pageflow. The simple number guessing example shows how this is done."
msgstr ""
#. Tag: para
#: Tutorial.xml:956
#, no-c-format
-msgid ""
-"The example is implemented using one JavaBean, three JSP pages and a jPDL "
-"pageflow definition. Let's begin with the pageflow:"
+msgid "The example is implemented using one JavaBean, three JSP pages and a jPDL pageflow definition. Let's begin with the pageflow:"
msgstr ""
#. Tag: title
#: Tutorial.xml:960
#, no-c-format
msgid "pageflow.jpdl.xml"
-msgstr ""
+msgstr "pageflow.jpdl.xml"
#. Tag: programlisting
#: Tutorial.xml:968
@@ -2298,8 +2406,7 @@
" xmlns=\"http://jboss.com/products/seam/pageflow\"\n"
" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
" xsi:schemaLocation=\"http://jboss.com/products/seam/pageflow \n"
-" http://jboss.com/products/seam/pageflow-2.1.xsd"
-"\"\n"
+" http://jboss.com/products/seam/pageflow-2.1.xsd\"\n"
" name=\"numberGuess\">\n"
" \n"
" <start-page name=\"displayGuess\" view-id=\"/numberGuess.jspx\">\n"
@@ -2311,14 +2418,12 @@
" <transition name=\"cheat\" to=\"cheat\"/>\n"
" </start-page>\n"
" \n"
-" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}"
-"\">\n"
+" <decision name=\"evaluateGuess\" expression=\"#{numberGuess.correctGuess}\">\n"
" <transition name=\"true\" to=\"win\"/>\n"
" <transition name=\"false\" to=\"evaluateRemainingGuesses\"/>\n"
" </decision>\n"
" \n"
-" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess."
-"lastGuess}\">\n"
+" <decision name=\"evaluateRemainingGuesses\" expression=\"#{numberGuess.lastGuess}\">\n"
" <transition name=\"true\" to=\"lose\"/>\n"
" <transition name=\"false\" to=\"displayGuess\"/>\n"
" </decision>\n"
@@ -2346,75 +2451,124 @@
" \n"
"</pageflow-definition>]]>"
msgstr ""
+"<![CDATA[<<?xml version=\"1.0\"?>\n"
+"<jsp:root xmlns:jsp=\"http://java.sun.com/JSP/Page\" \n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\"\n"
+" xmlns:s=\"http://jboss.com/products/seam/taglib\"\n"
+" xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" version=\"2.0\">\n"
+" <jsp:output doctype-root-element=\"html\" \n"
+" doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n"
+" <jsp:directive.page contentType=\"text/html\"/>\n"
+" <html>\n"
+" <head>\n"
+" <title>Guess a number...</title>\n"
+" <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n"
+" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms.js\" />\n"
+" </head>\n"
+" <body>\n"
+" <h1>Guess a number...</h1>\n"
+" <f:view>\n"
+" <h:form styleClass=\"niceform\">\n"
+" \n"
+" <div>\n"
+" <h:messages globalOnly=\"true\"/>\n"
+" <h:outputText value=\"Higher!\" \n"
+" rendered=\"#{numberGuess.randomNumber gt numberGuess.currentGuess}\"/>\n"
+" <h:outputText value=\"Lower!\" \n"
+" rendered=\"#{numberGuess.randomNumber lt numberGuess.currentGuess}\"/>\n"
+" </div>\n"
+" \n"
+" <div>\n"
+" I'm thinking of a number between \n"
+" <h:outputText value=\"#{numberGuess.smallest}\"/> and \n"
+" <h:outputText value=\"#{numberGuess.biggest}\"/>. You have \n"
+" <h:outputText value=\"#{numberGuess.remainingGuesses}\"/> guesses.\n"
+" </div>\n"
+" \n"
+" <div>\n"
+" Your guess: \n"
+" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess\" \n"
+" required=\"true\" size=\"3\" \n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) gt 20}\">\n"
+" <f:validateLongRange maximum=\"#{numberGuess.biggest}\" \n"
+" minimum=\"#{numberGuess.smallest}\"/>\n"
+" </h:inputText>\n"
+" <h:selectOneMenu value=\"#{numberGuess.currentGuess}\" \n"
+" id=\"selectGuessMenu\" required=\"true\"\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 20 and \n"
+" (numberGuess.biggest-numberGuess.smallest) gt 4}\">\n"
+" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n"
+" </h:selectOneMenu>\n"
+" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=\"selectGuessRadio\" \n"
+" required=\"true\"\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 4}\">\n"
+" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n"
+" </h:selectOneRadio>\n"
+" <h:commandButton value=\"Guess\" action=\"guess\"/>\n"
+" <s:button value=\"Cheat\" view=\"/confirm.jspx\"/>\n"
+" <s:button value=\"Give up\" action=\"giveup\"/>\n"
+" </div>\n"
+" \n"
+" <div>\n"
+" <h:message for=\"inputGuess\" style=\"color: red\"/>\n"
+" </div>\n"
+" \n"
+" </h:form>\n"
+" </f:view>\n"
+" </body>\n"
+" </html>\n"
+"</jsp:root>]]>"
#. Tag: para
#: Tutorial.xml:971
#, no-c-format
-msgid ""
-"The <literal><page></literal> element defines a wait state where the "
-"system displays a particular JSF view and waits for user input. The "
-"<literal>view-id</literal> is the same JSF view id used in plain JSF "
-"navigation rules. The <literal>redirect</literal> attribute tells Seam to "
-"use post-then-redirect when navigating to the page. (This results in "
-"friendly browser URLs.)"
+msgid "The <literal><page></literal> element defines a wait state where the system displays a particular JSF view and waits for user input. The <literal>view-id</literal> is the same JSF view id used in plain JSF navigation rules. The <literal>redirect</literal> attribute tells Seam to use post-then-redirect when navigating to the page. (This results in friendly browser URLs.)"
msgstr ""
#. Tag: para
#: Tutorial.xml:978
#, no-c-format
-msgid ""
-"The <literal><transition></literal> element names a JSF outcome. The "
-"transition is triggered when a JSF action results in that outcome. Execution "
-"will then proceed to the next node of the pageflow graph, after invocation "
-"of any jBPM transition actions."
+msgid "The <literal><transition></literal> element names a JSF outcome. The transition is triggered when a JSF action results in that outcome. Execution will then proceed to the next node of the pageflow graph, after invocation of any jBPM transition actions."
msgstr ""
#. Tag: para
#: Tutorial.xml:984
#, no-c-format
-msgid ""
-"A transition <literal><action></literal> is just like a JSF action, "
-"except that it occurs when a jBPM transition occurs. The transition action "
-"can invoke any Seam component."
+msgid "A transition <literal><action></literal> is just like a JSF action, except that it occurs when a jBPM transition occurs. The transition action can invoke any Seam component."
msgstr ""
#. Tag: para
#: Tutorial.xml:989
#, no-c-format
-msgid ""
-"A <literal><decision></literal> node branches the pageflow, and "
-"determines the next node to execute by evaluating a JSF EL expression."
+msgid "A <literal><decision></literal> node branches the pageflow, and determines the next node to execute by evaluating a JSF EL expression."
msgstr ""
#. Tag: para
#: Tutorial.xml:997
#, no-c-format
-msgid ""
-"Here is what the pageflow looks like in the JBoss Developer Studio pageflow "
-"editor:"
+msgid "Here is what the pageflow looks like in the JBoss Developer Studio pageflow editor:"
msgstr ""
#. Tag: para
#: Tutorial.xml:1008
#, no-c-format
-msgid ""
-"Now that we have seen the pageflow, it is very, very easy to understand the "
-"rest of the application!"
+msgid "Now that we have seen the pageflow, it is very, very easy to understand the rest of the application!"
msgstr ""
#. Tag: para
#: Tutorial.xml:1010
#, no-c-format
-msgid ""
-"Here is the main page of the application, <literal>numberGuess.jspx</"
-"literal>:"
+msgid "Here is the main page of the application, <literal>numberGuess.jspx</literal>:"
msgstr ""
#. Tag: title
#: Tutorial.xml:1013
#, no-c-format
msgid "numberGuess.jspx"
-msgstr ""
+msgstr "numberGuess.jspx"
#. Tag: programlisting
#: Tutorial.xml:1014
@@ -2429,15 +2583,13 @@
" version=\"2.0\">\n"
" <jsp:output doctype-root-element=\"html\" \n"
" doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
-" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-"
-"transitional.dtd\"/>\n"
+" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n"
" <jsp:directive.page contentType=\"text/html\"/>\n"
" <html>\n"
" <head>\n"
" <title>Guess a number...</title>\n"
" <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n"
-" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms."
-"js\" />\n"
+" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms.js\" />\n"
" </head>\n"
" <body>\n"
" <h1>Guess a number...</h1>\n"
@@ -2447,11 +2599,9 @@
" <div>\n"
" <h:messages globalOnly=\"true\"/>\n"
" <h:outputText value=\"Higher!\" \n"
-" rendered=\"#{numberGuess.randomNumber gt numberGuess."
-"currentGuess}\"/>\n"
+" rendered=\"#{numberGuess.randomNumber gt numberGuess.currentGuess}\"/>\n"
" <h:outputText value=\"Lower!\" \n"
-" rendered=\"#{numberGuess.randomNumber lt numberGuess."
-"currentGuess}\"/>\n"
+" rendered=\"#{numberGuess.randomNumber lt numberGuess.currentGuess}\"/>\n"
" </div>\n"
" \n"
" <div>\n"
@@ -2463,30 +2613,22 @@
" \n"
" <div>\n"
" Your guess: \n"
-" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess"
-"\" \n"
+" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess\" \n"
" required=\"true\" size=\"3\" \n"
-" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) "
-"gt 20}\">\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) gt 20}\">\n"
" <f:validateLongRange maximum=\"#{numberGuess.biggest}\" \n"
" minimum=\"#{numberGuess.smallest}\"/>\n"
" </h:inputText>\n"
" <h:selectOneMenu value=\"#{numberGuess.currentGuess}\" \n"
" id=\"selectGuessMenu\" required=\"true\"\n"
-" rendered=\"#{(numberGuess.biggest-numberGuess."
-"smallest) le 20 and \n"
-" (numberGuess.biggest-numberGuess."
-"smallest) gt 4}\">\n"
-" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" "
-"label=\"#{i}\"/>\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 20 and \n"
+" (numberGuess.biggest-numberGuess.smallest) gt 4}\">\n"
+" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n"
" </h:selectOneMenu>\n"
-" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id="
-"\"selectGuessRadio\" \n"
+" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=\"selectGuessRadio\" \n"
" required=\"true\"\n"
-" rendered=\"#{(numberGuess.biggest-numberGuess."
-"smallest) le 4}\">\n"
-" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" "
-"label=\"#{i}\"/>\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 4}\">\n"
+" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n"
" </h:selectOneRadio>\n"
" <h:commandButton value=\"Guess\" action=\"guess\"/>\n"
" <s:button value=\"Cheat\" view=\"/confirm.jspx\"/>\n"
@@ -2503,13 +2645,81 @@
" </html>\n"
"</jsp:root>]]>"
msgstr ""
+"<![CDATA[<<?xml version=\"1.0\"?>\n"
+"<jsp:root xmlns:jsp=\"http://java.sun.com/JSP/Page\" \n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\"\n"
+" xmlns:s=\"http://jboss.com/products/seam/taglib\"\n"
+" xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" version=\"2.0\">\n"
+" <jsp:output doctype-root-element=\"html\" \n"
+" doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n"
+" <jsp:directive.page contentType=\"text/html\"/>\n"
+" <html>\n"
+" <head>\n"
+" <title>Guess a number...</title>\n"
+" <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n"
+" <script language=\"javascript\" type=\"text/javascript\" src=\"niceforms.js\" />\n"
+" </head>\n"
+" <body>\n"
+" <h1>Guess a number...</h1>\n"
+" <f:view>\n"
+" <h:form styleClass=\"niceform\">\n"
+" \n"
+" <div>\n"
+" <h:messages globalOnly=\"true\"/>\n"
+" <h:outputText value=\"Higher!\" \n"
+" rendered=\"#{numberGuess.randomNumber gt numberGuess.currentGuess}\"/>\n"
+" <h:outputText value=\"Lower!\" \n"
+" rendered=\"#{numberGuess.randomNumber lt numberGuess.currentGuess}\"/>\n"
+" </div>\n"
+" \n"
+" <div>\n"
+" I'm thinking of a number between \n"
+" <h:outputText value=\"#{numberGuess.smallest}\"/> and \n"
+" <h:outputText value=\"#{numberGuess.biggest}\"/>. You have \n"
+" <h:outputText value=\"#{numberGuess.remainingGuesses}\"/> guesses.\n"
+" </div>\n"
+" \n"
+" <div>\n"
+" Your guess: \n"
+" <h:inputText value=\"#{numberGuess.currentGuess}\" id=\"inputGuess\" \n"
+" required=\"true\" size=\"3\" \n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) gt 20}\">\n"
+" <f:validateLongRange maximum=\"#{numberGuess.biggest}\" \n"
+" minimum=\"#{numberGuess.smallest}\"/>\n"
+" </h:inputText>\n"
+" <h:selectOneMenu value=\"#{numberGuess.currentGuess}\" \n"
+" id=\"selectGuessMenu\" required=\"true\"\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 20 and \n"
+" (numberGuess.biggest-numberGuess.smallest) gt 4}\">\n"
+" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n"
+" </h:selectOneMenu>\n"
+" <h:selectOneRadio value=\"#{numberGuess.currentGuess}\" id=\"selectGuessRadio\" \n"
+" required=\"true\"\n"
+" rendered=\"#{(numberGuess.biggest-numberGuess.smallest) le 4}\">\n"
+" <s:selectItems value=\"#{numberGuess.possibilities}\" var=\"i\" label=\"#{i}\"/>\n"
+" </h:selectOneRadio>\n"
+" <h:commandButton value=\"Guess\" action=\"guess\"/>\n"
+" <s:button value=\"Cheat\" view=\"/confirm.jspx\"/>\n"
+" <s:button value=\"Give up\" action=\"giveup\"/>\n"
+" </div>\n"
+" \n"
+" <div>\n"
+" <h:message for=\"inputGuess\" style=\"color: red\"/>\n"
+" </div>\n"
+" \n"
+" </h:form>\n"
+" </f:view>\n"
+" </body>\n"
+" </html>\n"
+"</jsp:root>]]>"
#. Tag: para
#: Tutorial.xml:1018
#, no-c-format
-msgid ""
-"Notice how the command button names the <literal>guess</literal> transition "
-"instead of calling an action directly."
+msgid "Notice how the command button names the <literal>guess</literal> transition instead of calling an action directly."
msgstr ""
#. Tag: para
@@ -2522,7 +2732,7 @@
#: Tutorial.xml:1023
#, no-c-format
msgid "win.jspx"
-msgstr ""
+msgstr "win.jspx"
#. Tag: programlisting
#: Tutorial.xml:1024
@@ -2535,8 +2745,7 @@
" version=\"2.0\">\n"
" <jsp:output doctype-root-element=\"html\"\n"
" doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
-" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-"
-"transitional.dtd\"/>\n"
+" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n"
" <jsp:directive.page contentType=\"text/html\"/>\n"
" <html>\n"
" <head>\n"
@@ -2546,10 +2755,8 @@
" <body>\n"
" <h1>You won!</h1>\n"
" <f:view>\n"
-" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}"
-"\" />.\n"
-" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> "
-"guesses.\n"
+" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}\" />.\n"
+" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> guesses.\n"
" <h:outputText value=\"But you cheated, so it doesn't count!\" \n"
" rendered=\"#{numberGuess.cheat}\"/>\n"
" Would you like to <a href=\"numberGuess.seam\">play again</a>?\n"
@@ -2559,13 +2766,38 @@
"</jsp:root>\n"
"]]>"
msgstr ""
+"<![CDATA[<jsp:root xmlns:jsp=\"http://java.sun.com/JSP/Page\" \n"
+" xmlns:h=\"http://java.sun.com/jsf/html\"\n"
+" xmlns:f=\"http://java.sun.com/jsf/core\"\n"
+" xmlns=\"http://www.w3.org/1999/xhtml\"\n"
+" version=\"2.0\">\n"
+" <jsp:output doctype-root-element=\"html\"\n"
+" doctype-public=\"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n"
+" doctype-system=\"http://www.w3c.org/TR/xhtml1/DTD/xhtml1-transitional.dtd\"/>\n"
+" <jsp:directive.page contentType=\"text/html\"/>\n"
+" <html>\n"
+" <head>\n"
+" <title>You won!</title>\n"
+" <link href=\"niceforms.css\" rel=\"stylesheet\" type=\"text/css\" />\n"
+" </head>\n"
+" <body>\n"
+" <h1>You won!</h1>\n"
+" <f:view>\n"
+" Yes, the answer was <h:outputText value=\"#{numberGuess.currentGuess}\" />.\n"
+" It took you <h:outputText value=\"#{numberGuess.guessCount}\" /> guesses.\n"
+" <h:outputText value=\"But you cheated, so it doesn't count!\" \n"
+" rendered=\"#{numberGuess.cheat}\"/>\n"
+" Would you like to <a href=\"numberGuess.seam\">play again</a>?\n"
+" </f:view>\n"
+" </body>\n"
+" </html>\n"
+"</jsp:root>\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1028
#, no-c-format
-msgid ""
-"The <literal>lose.jspx</literal> looks roughly the same, so we'll skip over "
-"it."
+msgid "The <literal>lose.jspx</literal> looks roughly the same, so we'll skip over it."
msgstr ""
#. Tag: para
@@ -2578,7 +2810,7 @@
#: Tutorial.xml:1033
#, no-c-format
msgid "NumberGuess.java"
-msgstr ""
+msgstr "NumberGuess.java"
#. Tag: programlisting
#: Tutorial.xml:1038
@@ -2688,30 +2920,127 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[@Name(\"numberGuess\")\n"
+"@Scope(ScopeType.CONVERSATION)\n"
+"public class NumberGuess implements Serializable {\n"
+" \n"
+" private int randomNumber;\n"
+" private Integer currentGuess;\n"
+" private int biggest;\n"
+" private int smallest;\n"
+" private int guessCount;\n"
+" private int maxGuesses;\n"
+" private boolean cheated;\n"
+" \n"
+" @Create\n"
+" public void begin()\n"
+" {\n"
+" randomNumber = new Random().nextInt(100);\n"
+" guessCount = 0;\n"
+" biggest = 100;\n"
+" smallest = 1;\n"
+" }\n"
+" \n"
+" public void setCurrentGuess(Integer guess)\n"
+" {\n"
+" this.currentGuess = guess;\n"
+" }\n"
+" \n"
+" public Integer getCurrentGuess()\n"
+" {\n"
+" return currentGuess;\n"
+" }\n"
+" \n"
+" public void guess()\n"
+" {\n"
+" if (currentGuess>randomNumber)\n"
+" {\n"
+" biggest = currentGuess - 1;\n"
+" }\n"
+" if (currentGuess<randomNumber)\n"
+" {\n"
+" smallest = currentGuess + 1;\n"
+" }\n"
+" guessCount ++;\n"
+" }\n"
+" \n"
+" public boolean isCorrectGuess()\n"
+" {\n"
+" return currentGuess==randomNumber;\n"
+" }\n"
+" \n"
+" public int getBiggest()\n"
+" {\n"
+" return biggest;\n"
+" }\n"
+" \n"
+" public int getSmallest()\n"
+" {\n"
+" return smallest;\n"
+" }\n"
+" \n"
+" public int getGuessCount()\n"
+" {\n"
+" return guessCount;\n"
+" }\n"
+" \n"
+" public boolean isLastGuess()\n"
+" {\n"
+" return guessCount==maxGuesses;\n"
+" }\n"
+"\n"
+" public int getRemainingGuesses() {\n"
+" return maxGuesses-guessCount;\n"
+" }\n"
+"\n"
+" public void setMaxGuesses(int maxGuesses) {\n"
+" this.maxGuesses = maxGuesses;\n"
+" }\n"
+"\n"
+" public int getMaxGuesses() {\n"
+" return maxGuesses;\n"
+" }\n"
+"\n"
+" public int getRandomNumber() {\n"
+" return randomNumber;\n"
+" }\n"
+"\n"
+" public void cheated()\n"
+" {\n"
+" cheated = true;\n"
+" }\n"
+" \n"
+" public boolean isCheat() {\n"
+" return cheated;\n"
+" }\n"
+" \n"
+" public List<Integer> getPossibilities()\n"
+" {\n"
+" List<Integer> result = new ArrayList<Integer>();\n"
+" for(int i=smallest; i<=biggest; i++) result.add(i);\n"
+" return result;\n"
+" }\n"
+" \n"
+"}\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1041
#, no-c-format
-msgid ""
-"The first time a JSP page asks for a <literal>numberGuess</literal> "
-"component, Seam will create a new one for it, and the <literal>@Create</"
-"literal> method will be invoked, allowing the component to initialize itself."
+msgid "The first time a JSP page asks for a <literal>numberGuess</literal> component, Seam will create a new one for it, and the <literal>@Create</literal> method will be invoked, allowing the component to initialize itself."
msgstr ""
#. Tag: para
#: Tutorial.xml:1051
#, no-c-format
-msgid ""
-"The <literal>pages.xml</literal> file starts a Seam <emphasis>conversation</"
-"emphasis> (much more about that later), and specifies the pageflow "
-"definition to use for the conversation's page flow."
+msgid "The <literal>pages.xml</literal> file starts a Seam <emphasis>conversation</emphasis> (much more about that later), and specifies the pageflow definition to use for the conversation's page flow."
msgstr ""
#. Tag: title
#: Tutorial.xml:1057
#, no-c-format
msgid "pages.xml"
-msgstr ""
+msgstr "pages.xml"
#. Tag: programlisting
#: Tutorial.xml:1060
@@ -2720,8 +3049,7 @@
"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
"<pages xmlns=\"http://jboss.com/products/seam/pages\"\n"
" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://"
-"jboss.com/products/seam/pages-2.1.xsd\">\n"
+" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.1.xsd\">\n"
"\n"
" <page view-id=\"/numberGuess.jspx\">\n"
" <begin-conversation join=\"true\" pageflow=\"numberGuess\"/>\n"
@@ -2730,93 +3058,58 @@
"</pages> \n"
"]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<pages xmlns=\"http://jboss.com/products/seam/pages\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\"http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.1.xsd\">\n"
+"\n"
+" <page view-id=\"/numberGuess.jspx\">\n"
+" <begin-conversation join=\"true\" pageflow=\"numberGuess\"/>\n"
+" </page>\n"
+"\n"
+"</pages> \n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1064
#, no-c-format
-msgid ""
-"As you can see, this Seam component is pure business logic! It doesn't need "
-"to know anything at all about the user interaction flow. This makes the "
-"component potentially more reuseable."
+msgid "As you can see, this Seam component is pure business logic! It doesn't need to know anything at all about the user interaction flow. This makes the component potentially more reuseable."
msgstr ""
#. Tag: para
#: Tutorial.xml:1071
#, no-c-format
-msgid ""
-"We'll step through basic flow of the application. The game starts with the "
-"<literal>numberGuess.jspx</literal> view. When the page is first displayed, "
-"the <literal>pages.xml</literal> configuration causes conversation to begin "
-"and associates the <literal>numberGuess</literal> pageflow with that "
-"conversation. The pageflow starts with a <literal>start-page</literal> tag, "
-"which is a wait state, so the <literal>numberGuess.xhtml</literal> is "
-"rendered."
+msgid "We'll step through basic flow of the application. The game starts with the <literal>numberGuess.jspx</literal> view. When the page is first displayed, the <literal>pages.xml</literal> configuration causes conversation to begin and associates the <literal>numberGuess</literal> pageflow with that conversation. The pageflow starts with a <literal>start-page</literal> tag, which is a wait state, so the <literal>numberGuess.xhtml</literal> is rendered."
msgstr ""
#. Tag: para
#: Tutorial.xml:1079
#, no-c-format
-msgid ""
-"The view references the <literal>numberGuess</literal> component, causing a "
-"new instance to be created and stored in the conversation. The "
-"<literal>@Create</literal> method is called, initializing the state of the "
-"game. The view displays an <literal>h:form</literal> that allows the user to "
-"edit <literal>#{numberGuess.currentGuess}</literal>."
+msgid "The view references the <literal>numberGuess</literal> component, causing a new instance to be created and stored in the conversation. The <literal>@Create</literal> method is called, initializing the state of the game. The view displays an <literal>h:form</literal> that allows the user to edit <literal>#{numberGuess.currentGuess}</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:1085
#, no-c-format
-msgid ""
-"The \"Guess\" button triggers the <literal>guess</literal> action. Seam "
-"defers to the pageflow to handle the action, which says that the pageflow "
-"should transition to the <literal>evaluateGuess</literal> state, first "
-"invoking <literal>#{numberGuess.guess}</literal>, which updates the guess "
-"count and highest/lowest suggestions in the <literal>numberGuess</literal> "
-"component."
+msgid "The \"Guess\" button triggers the <literal>guess</literal> action. Seam defers to the pageflow to handle the action, which says that the pageflow should transition to the <literal>evaluateGuess</literal> state, first invoking <literal>#{numberGuess.guess}</literal>, which updates the guess count and highest/lowest suggestions in the <literal>numberGuess</literal> component."
msgstr ""
#. Tag: para
#: Tutorial.xml:1091
#, no-c-format
-msgid ""
-"The <literal>evaluateGuess</literal> state checks the value of <literal>#"
-"{numberGuess.correctGuess}</literal> and transitions either to the "
-"<literal>win</literal> or <literal>evaluatingRemainingGuesses</literal> "
-"state. We'll assume the number was incorrect, in which case the pageflow "
-"transitions to <literal>evaluatingRemainingGuesses</literal>. That is also a "
-"decision state, which tests the <literal>#{numberGuess.lastGuess}</literal> "
-"state to determine whether or not the user has more guesses. If there are "
-"more guesses (<literal>lastGuess</literal> is <literal>false</literal>), we "
-"transition back to the original <literal>displayGuess</literal> state. "
-"Finally we've reached a page state, so the associated page <literal>/"
-"numberGuess.jspx</literal> is displayed. Since the page has a redirect "
-"element, Seam sends a redirect to the the user's browser, starting the "
-"process over."
+msgid "The <literal>evaluateGuess</literal> state checks the value of <literal>#{numberGuess.correctGuess}</literal> and transitions either to the <literal>win</literal> or <literal>evaluatingRemainingGuesses</literal> state. We'll assume the number was incorrect, in which case the pageflow transitions to <literal>evaluatingRemainingGuesses</literal>. That is also a decision state, which tests the <literal>#{numberGuess.lastGuess}</literal> state to determine whether or not the user has more guesses. If there are more guesses (<literal>lastGuess</literal> is <literal>false</literal>), we transition back to the original <literal>displayGuess</literal> state. Finally we've reached a page state, so the associated page <literal>/numberGuess.jspx</literal> is displayed. Since the page has a redirect element, Seam sends a redirect to the the user's browser, starting the process over."
msgstr ""
#. Tag: para
#: Tutorial.xml:1103
#, no-c-format
-msgid ""
-"We won't follow the state any more except to note that if on a future "
-"request either the <literal>win</literal> or the <literal>lose</literal> "
-"transition were taken, the user would be taken to either the <literal>/win."
-"jspx</literal> or <literal>/lose.jspx</literal>. Both states specify that "
-"Seam should end the conversation, tossing away all the game state and "
-"pageflow state, before redirecting the user to the final page."
+msgid "We won't follow the state any more except to note that if on a future request either the <literal>win</literal> or the <literal>lose</literal> transition were taken, the user would be taken to either the <literal>/win.jspx</literal> or <literal>/lose.jspx</literal>. Both states specify that Seam should end the conversation, tossing away all the game state and pageflow state, before redirecting the user to the final page."
msgstr ""
#. Tag: para
#: Tutorial.xml:1113
#, no-c-format
-msgid ""
-"The numberguess example also contains Giveup and Cheat buttons. You should "
-"be able to trace the pageflow state for both actions relatively easily. Pay "
-"particular attention to the <literal>cheat</literal> transtition, which "
-"loads a sub-process to handle that flow. Although it's overkill for this "
-"application, it does demonstrate how complex pageflows can be broken down "
-"into smaller parts to make them easier to understand."
+msgid "The numberguess example also contains Giveup and Cheat buttons. You should be able to trace the pageflow state for both actions relatively easily. Pay particular attention to the <literal>cheat</literal> transtition, which loads a sub-process to handle that flow. Although it's overkill for this application, it does demonstrate how complex pageflows can be broken down into smaller parts to make them easier to understand."
msgstr ""
#. Tag: title
@@ -2826,54 +3119,53 @@
msgstr ""
#. Tag: title
-#: Tutorial.xml:1128 Tutorial.xml:1506
+#: Tutorial.xml:1128
+#: Tutorial.xml:1506
#, no-c-format
msgid "Introduction"
-msgstr ""
+msgstr "Introduzione"
#. Tag: para
#: Tutorial.xml:1130
#, no-c-format
-msgid ""
-"The booking application is a complete hotel room reservation system "
-"incorporating the following features:"
+msgid "The booking application is a complete hotel room reservation system incorporating the following features:"
msgstr ""
#. Tag: para
#: Tutorial.xml:1135
#, no-c-format
msgid "User registration"
-msgstr ""
+msgstr "Registrazione utente"
#. Tag: para
#: Tutorial.xml:1138
#, no-c-format
msgid "Login"
-msgstr ""
+msgstr "Login"
#. Tag: para
#: Tutorial.xml:1141
#, no-c-format
msgid "Logout"
-msgstr ""
+msgstr "Logout"
#. Tag: para
#: Tutorial.xml:1144
#, no-c-format
msgid "Set password"
-msgstr ""
+msgstr "Impostazione password"
#. Tag: para
#: Tutorial.xml:1147
#, no-c-format
msgid "Hotel search"
-msgstr ""
+msgstr "Ricerca hotel"
#. Tag: para
#: Tutorial.xml:1150
#, no-c-format
msgid "Hotel selection"
-msgstr ""
+msgstr "Scelta hotel"
#. Tag: para
#: Tutorial.xml:1153
@@ -2902,34 +3194,19 @@
#. Tag: para
#: Tutorial.xml:1175
#, no-c-format
-msgid ""
-"The booking application uses JSF, EJB 3.0 and Seam, together with Facelets "
-"for the view. There is also a port of this application to JSF, Facelets, "
-"Seam, JavaBeans and Hibernate3."
+msgid "The booking application uses JSF, EJB 3.0 and Seam, together with Facelets for the view. There is also a port of this application to JSF, Facelets, Seam, JavaBeans and Hibernate3."
msgstr ""
#. Tag: para
#: Tutorial.xml:1178
#, no-c-format
-msgid ""
-"One of the things you'll notice if you play with this application for long "
-"enough is that it is extremely <emphasis>robust</emphasis>. You can play "
-"with back buttons and browser refresh and opening multiple windows and "
-"entering nonsensical data as much as you like and you will find it very "
-"difficult to make the application crash. You might think that we spent weeks "
-"testing and fixing bugs to achive this. Actually, this is not the case. Seam "
-"was designed to make it very straightforward to build robust web "
-"applications and a lot of robustness that you are probably used to having to "
-"code yourself comes naturally and automatically with Seam."
+msgid "One of the things you'll notice if you play with this application for long enough is that it is extremely <emphasis>robust</emphasis>. You can play with back buttons and browser refresh and opening multiple windows and entering nonsensical data as much as you like and you will find it very difficult to make the application crash. You might think that we spent weeks testing and fixing bugs to achive this. Actually, this is not the case. Seam was designed to make it very straightforward to build robust web applications and a lot of robustness that you are probably used to having to code yourself comes naturally and automatically with Seam."
msgstr ""
#. Tag: para
#: Tutorial.xml:1185
#, no-c-format
-msgid ""
-"As you browse the sourcecode of the example application, and learn how the "
-"application works, observe how the declarative state management and "
-"integrated validation has been used to achieve this robustness."
+msgid "As you browse the sourcecode of the example application, and learn how the application works, observe how the declarative state management and integrated validation has been used to achieve this robustness."
msgstr ""
#. Tag: title
@@ -2941,62 +3218,43 @@
#. Tag: para
#: Tutorial.xml:1193
#, no-c-format
-msgid ""
-"The project structure is identical to the previous one, to install and "
-"deploy this application, please refer to <xref linkend=\"try-examples\"/>. "
-"Once you've successfully started the application, you can access it by "
-"pointing your browser to <ulink url=\"http://localhost:8080/seam-booking/\"> "
-"<literal>http://localhost:8080/seam-booking/</literal> </ulink>"
+msgid "The project structure is identical to the previous one, to install and deploy this application, please refer to <xref linkend=\"try-examples\"/>. Once you've successfully started the application, you can access it by pointing your browser to <ulink url=\"http://localhost:8080/seam-booking/\"> <literal>http://localhost:8080/seam-booking/</literal> </ulink>"
msgstr ""
#. Tag: para
#: Tutorial.xml:1200
#, no-c-format
-msgid ""
-"The application uses six session beans for to implement the business logic "
-"for the listed features."
+msgid "The application uses six session beans for to implement the business logic for the listed features."
msgstr ""
#. Tag: para
#: Tutorial.xml:1204
#, no-c-format
-msgid ""
-"<literal>AuthenticatorAction</literal> provides the login authentication "
-"logic."
+msgid "<literal>AuthenticatorAction</literal> provides the login authentication logic."
msgstr ""
#. Tag: para
#: Tutorial.xml:1207
#, no-c-format
-msgid ""
-"<literal>BookingListAction</literal> retrieves existing bookings for the "
-"currently logged in user."
+msgid "<literal>BookingListAction</literal> retrieves existing bookings for the currently logged in user."
msgstr ""
#. Tag: para
#: Tutorial.xml:1210
#, no-c-format
-msgid ""
-"<literal>ChangePasswordAction</literal> updates the password of the "
-"currently logged in user."
+msgid "<literal>ChangePasswordAction</literal> updates the password of the currently logged in user."
msgstr ""
#. Tag: para
#: Tutorial.xml:1213
#, no-c-format
-msgid ""
-"<literal>HotelBookingAction</literal> implements booking and confirmation "
-"functionality. This functionality is implemented as a "
-"<emphasis>conversation</emphasis>, so this is one of the most interesting "
-"classes in the application."
+msgid "<literal>HotelBookingAction</literal> implements booking and confirmation functionality. This functionality is implemented as a <emphasis>conversation</emphasis>, so this is one of the most interesting classes in the application."
msgstr ""
#. Tag: para
#: Tutorial.xml:1218
#, no-c-format
-msgid ""
-"<literal>HotelSearchingAction</literal> implements the hotel search "
-"functionality."
+msgid "<literal>HotelSearchingAction</literal> implements the hotel search functionality."
msgstr ""
#. Tag: para
@@ -3020,17 +3278,13 @@
#. Tag: para
#: Tutorial.xml:1231
#, no-c-format
-msgid ""
-"<literal>Booking</literal> is an entity bean that represents an existing "
-"booking"
+msgid "<literal>Booking</literal> is an entity bean that represents an existing booking"
msgstr ""
#. Tag: para
#: Tutorial.xml:1233
#, no-c-format
-msgid ""
-"<literal>User</literal> is an entity bean to represents a user who can make "
-"hotel bookings"
+msgid "<literal>User</literal> is an entity bean to represents a user who can make hotel bookings"
msgstr ""
#. Tag: title
@@ -3042,123 +3296,55 @@
#. Tag: para
#: Tutorial.xml:1241
#, no-c-format
-msgid ""
-"We encourage you browse the sourcecode at your pleasure. In this tutorial "
-"we'll concentrate upon one particular piece of functionality: hotel search, "
-"selection, booking and confirmation. From the point of view of the user, "
-"everything from selecting a hotel to confirming a booking is one continuous "
-"unit of work, a <emphasis>conversation</emphasis>. Searching, however, is "
-"<emphasis>not</emphasis> part of the conversation. The user can select "
-"multiple hotels from the same search results page, in different browser tabs."
+msgid "We encourage you browse the sourcecode at your pleasure. In this tutorial we'll concentrate upon one particular piece of functionality: hotel search, selection, booking and confirmation. From the point of view of the user, everything from selecting a hotel to confirming a booking is one continuous unit of work, a <emphasis>conversation</emphasis>. Searching, however, is <emphasis>not</emphasis> part of the conversation. The user can select multiple hotels from the same search results page, in different browser tabs."
msgstr ""
#. Tag: para
#: Tutorial.xml:1247
#, no-c-format
-msgid ""
-"Most web application architectures have no first class construct to "
-"represent a conversation. This causes enormous problems managing "
-"conversational state. Usually, Java web applications use a combination of "
-"several techniques. Some state can be transfered in the URL. What can't is "
-"either thrown into the <literal>HttpSession</literal> or flushed to the "
-"database after every request, and reconstructed from the database at the "
-"beginning of each new request."
+msgid "Most web application architectures have no first class construct to represent a conversation. This causes enormous problems managing conversational state. Usually, Java web applications use a combination of several techniques. Some state can be transfered in the URL. What can't is either thrown into the <literal>HttpSession</literal> or flushed to the database after every request, and reconstructed from the database at the beginning of each new request."
msgstr ""
#. Tag: para
#: Tutorial.xml:1253
#, no-c-format
-msgid ""
-"Since the database is the least scalable tier, this often results in an "
-"utterly unacceptable lack of scalability. Added latency is also a problem, "
-"due to the extra traffic to and from the database on every request. To "
-"reduce this redundant traffic, Java applications often introduce a data "
-"(second-level) cache that keeps commonly accessed data between requests. "
-"This cache is necessarily inefficient, because invalidation is based upon an "
-"LRU policy instead of being based upon when the user has finished working "
-"with the data. Furthermore, because the cache is shared between many "
-"concurrent transactions, we've introduced a whole raft of problem's "
-"associated with keeping the cached state consistent with the database."
+msgid "Since the database is the least scalable tier, this often results in an utterly unacceptable lack of scalability. Added latency is also a problem, due to the extra traffic to and from the database on every request. To reduce this redundant traffic, Java applications often introduce a data (second-level) cache that keeps commonly accessed data between requests. This cache is necessarily inefficient, because invalidation is based upon an LRU policy instead of being based upon when the user has finished working with the data. Furthermore, because the cache is shared between many concurrent transactions, we've introduced a whole raft of problem's associated with keeping the cached state consistent with the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:1261
#, no-c-format
-msgid ""
-"Now consider the state held in the <literal>HttpSession</literal>. The "
-"HttpSession is great place for true session data, data that is common to all "
-"requests that the user has with the application. However, it's a bad place "
-"to store data related to individual series of requests. Using the session of "
-"conversational quickly breaks down when dealing with the back button and "
-"multiple windows. On top of that, without careful programming, data in the "
-"HTTP Session can grow quite large, making the HTTP session difficult to "
-"cluster. Developing mechanisms to isolate session state associated with "
-"different concurrent conversations, and incorporating failsafes to ensure "
-"that conversation state is destroyed when the user aborts one of the "
-"conversations by closing a browser window or tab is not for the faint "
-"hearted. Fortunately, with Seam, you don't have to worry about that."
+msgid "Now consider the state held in the <literal>HttpSession</literal>. The HttpSession is great place for true session data, data that is common to all requests that the user has with the application. However, it's a bad place to store data related to individual series of requests. Using the session of conversational quickly breaks down when dealing with the back button and multiple windows. On top of that, without careful programming, data in the HTTP Session can grow quite large, making the HTTP session difficult to cluster. Developing mechanisms to isolate session state associated with different concurrent conversations, and incorporating failsafes to ensure that conversation state is destroyed when the user aborts one of the conversations by closing a browser window or tab is not for the faint hearted. Fortunately, with Seam, you don't have to worry about that."
msgstr ""
#. Tag: para
#: Tutorial.xml:1274
#, no-c-format
-msgid ""
-"Seam introduces the <emphasis>conversation context</emphasis> as a first "
-"class construct. You can safely keep conversational state in this context, "
-"and be assured that it will have a well-defined lifecycle. Even better, you "
-"won't need to be continually pushing data back and forth between the "
-"application server and the database, since the conversation context is a "
-"natural cache of data that the user is currently working with."
+msgid "Seam introduces the <emphasis>conversation context</emphasis> as a first class construct. You can safely keep conversational state in this context, and be assured that it will have a well-defined lifecycle. Even better, you won't need to be continually pushing data back and forth between the application server and the database, since the conversation context is a natural cache of data that the user is currently working with."
msgstr ""
#. Tag: para
#: Tutorial.xml:1279
#, no-c-format
-msgid ""
-"In this application, we'll use the conversation context to store stateful "
-"session beans. There is an ancient canard in the Java community that "
-"stateful session beans are a scalability killer. This may have been true in "
-"the early days of enterprise Java, but it is no longer true today. Modern "
-"application servers have extremely sophisticated mechanisms for stateful "
-"session bean state replication. JBoss AS, for example, performs fine-grained "
-"replication, replicating only those bean attribute values which actually "
-"changed. Note that all the traditional technical arguments for why stateful "
-"beans are inefficient apply equally to the <literal>HttpSession</literal>, "
-"so the practice of shifting state from business tier stateful session bean "
-"components to the web session to try and improve performance is unbelievably "
-"misguided. It is certainly possible to write unscalable applications using "
-"stateful session beans, by using stateful beans incorrectly, or by using "
-"them for the wrong thing. But that doesn't mean you should <emphasis>never</"
-"emphasis> use them. If you remain unconvinced, Seam allows the use of POJOs "
-"instead of stateful session beans. With Seam, the choice is yours."
+msgid "In this application, we'll use the conversation context to store stateful session beans. There is an ancient canard in the Java community that stateful session beans are a scalability killer. This may have been true in the early days of enterprise Java, but it is no longer true today. Modern application servers have extremely sophisticated mechanisms for stateful session bean state replication. JBoss AS, for example, performs fine-grained replication, replicating only those bean attribute values which actually changed. Note that all the traditional technical arguments for why stateful beans are inefficient apply equally to the <literal>HttpSession</literal>, so the practice of shifting state from business tier stateful session bean components to the web session to try and improve performance is unbelievably misguided. It is certainly possible to write unscalable applications using stateful session beans, by using stateful beans incorrectly, or by using them for the w!
rong thing. But that doesn't mean you should <emphasis>never</emphasis> use them. If you remain unconvinced, Seam allows the use of POJOs instead of stateful session beans. With Seam, the choice is yours."
msgstr ""
#. Tag: para
#: Tutorial.xml:1297
#, no-c-format
-msgid ""
-"The booking example application shows how stateful components with different "
-"scopes can collaborate together to achieve complex behaviors. The main page "
-"of the booking application allows the user to search for hotels. The search "
-"results are kept in the Seam session scope. When the user navigates to one "
-"of these hotels, a conversation begins, and a conversation scoped component "
-"calls back to the session scoped component to retrieve the selected hotel."
+msgid "The booking example application shows how stateful components with different scopes can collaborate together to achieve complex behaviors. The main page of the booking application allows the user to search for hotels. The search results are kept in the Seam session scope. When the user navigates to one of these hotels, a conversation begins, and a conversation scoped component calls back to the session scoped component to retrieve the selected hotel."
msgstr ""
#. Tag: para
#: Tutorial.xml:1303
#, no-c-format
-msgid ""
-"The booking example also demonstrates the use of RichFaces Ajax to implement "
-"rich client behavior without the use of handwritten JavaScript."
+msgid "The booking example also demonstrates the use of RichFaces Ajax to implement rich client behavior without the use of handwritten JavaScript."
msgstr ""
#. Tag: para
#: Tutorial.xml:1306
#, no-c-format
-msgid ""
-"The search functionality is implemented using a session-scope stateful "
-"session bean, similar to the one we saw in the message list example."
+msgid "The search functionality is implemented using a session-scope stateful session bean, similar to the one we saw in the message list example."
msgstr ""
#. Tag: title
@@ -3202,8 +3388,7 @@
" private void queryHotels()\n"
" {\n"
" hotels = \n"
-" em.createQuery(\"select h from Hotel h where lower(h.name) like #"
-"{pattern} \" + \n"
+" em.createQuery(\"select h from Hotel h where lower(h.name) like #{pattern} \" + \n"
" \"or lower(h.city) like #{pattern} \" + \n"
" \"or lower(h.zip) like #{pattern} \" +\n"
" \"or lower(h.address) like #{pattern}\")\n"
@@ -3229,8 +3414,7 @@
" public String getSearchPattern()\n"
" {\n"
" return searchString==null ? \n"
-" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + "
-"'%';\n"
+" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + '%';\n"
" }\n"
" \n"
" public String getSearchString()\n"
@@ -3251,50 +3435,31 @@
#. Tag: para
#: Tutorial.xml:1322
#, no-c-format
-msgid ""
-"The EJB standard <literal>@Stateful</literal> annotation identifies this "
-"class as a stateful session bean. Stateful session beans are scoped to the "
-"conversation context by default."
+msgid "The EJB standard <literal>@Stateful</literal> annotation identifies this class as a stateful session bean. Stateful session beans are scoped to the conversation context by default."
msgstr ""
#. Tag: para
#: Tutorial.xml:1327
#, no-c-format
-msgid ""
-"The <literal>@Restrict</literal> annotation applies a security restriction "
-"to the component. It restricts access to the component allowing only logged-"
-"in users. The security chapter explains more about security in Seam."
+msgid "The <literal>@Restrict</literal> annotation applies a security restriction to the component. It restricts access to the component allowing only logged-in users. The security chapter explains more about security in Seam."
msgstr ""
#. Tag: para
#: Tutorial.xml:1332
#, no-c-format
-msgid ""
-"The <link linkend=\"datamodel-annotation\"> <literal>@DataModel</literal> </"
-"link> annotation exposes a <literal>List</literal> as a JSF "
-"<literal>ListDataModel</literal>. This makes it easy to implement clickable "
-"lists for search screens. In this case, the list of hotels is exposed to the "
-"page as a <literal>ListDataModel</literal> in the conversation variable "
-"named <literal>hotels</literal>."
+msgid "The <link linkend=\"datamodel-annotation\"> <literal>@DataModel</literal> </link> annotation exposes a <literal>List</literal> as a JSF <literal>ListDataModel</literal>. This makes it easy to implement clickable lists for search screens. In this case, the list of hotels is exposed to the page as a <literal>ListDataModel</literal> in the conversation variable named <literal>hotels</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:1341
#, no-c-format
-msgid ""
-"The EJB standard <literal>@Remove</literal> annotation specifies that a "
-"stateful session bean should be removed and its state destroyed after "
-"invocation of the annotated method. In Seam, all stateful session beans must "
-"define a method with no parameters marked <literal>@Remove</literal>. This "
-"method will be called when Seam destroys the session context."
+msgid "The EJB standard <literal>@Remove</literal> annotation specifies that a stateful session bean should be removed and its state destroyed after invocation of the annotated method. In Seam, all stateful session beans must define a method with no parameters marked <literal>@Remove</literal>. This method will be called when Seam destroys the session context."
msgstr ""
#. Tag: para
#: Tutorial.xml:1352
#, no-c-format
-msgid ""
-"The main page of the application is a Facelets page. Let's look at the "
-"fragment which relates to searching for hotels:"
+msgid "The main page of the application is a Facelets page. Let's look at the fragment which relates to searching for hotels:"
msgstr ""
#. Tag: title
@@ -3317,16 +3482,13 @@
"\n"
" <h:form id=\"searchCriteria\">\n"
" <fieldset> \n"
-" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}"
-"\" \n"
+" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}\" \n"
" style=\"width: 165px;\">\n"
-" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}"
-"\" \n"
+" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}\" \n"
" reRender=\"searchResults\" />\n"
" </h:inputText>\n"
"  \n"
-" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#"
-"{hotelSearch.find}\" \n"
+" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#{hotelSearch.find}\" \n"
" reRender=\"searchResults\"/>\n"
"  \n"
" <a:status>\n"
@@ -3335,8 +3497,7 @@
" </f:facet>\n"
" </a:status>\n"
" <br/>\n"
-" <h:outputLabel for=\"pageSize\">Maximum results:</h:"
-"outputLabel> \n"
+" <h:outputLabel for=\"pageSize\">Maximum results:</h:outputLabel> \n"
" <h:selectOneMenu value=\"#{hotelSearch.pageSize}\" id=\"pageSize\">\n"
" <f:selectItem itemLabel=\"5\" itemValue=\"5\"/>\n"
" <f:selectItem itemLabel=\"10\" itemValue=\"10\"/>\n"
@@ -3380,82 +3541,120 @@
" </div>\n"
"</a:outputPanel> ]]>"
msgstr ""
+"<![CDATA[<div class=\"section\">\n"
+" \n"
+" <span class=\"errors\">\n"
+" <h:messages globalOnly=\"true\"/>\n"
+" </span>\n"
+" \n"
+" <h1>Search Hotels</h1>\n"
+"\n"
+" <h:form id=\"searchCriteria\">\n"
+" <fieldset> \n"
+" <h:inputText id=\"searchString\" value=\"#{hotelSearch.searchString}\" \n"
+" style=\"width: 165px;\">\n"
+" <a:support event=\"onkeyup\" actionListener=\"#{hotelSearch.find}\" \n"
+" reRender=\"searchResults\" />\n"
+" </h:inputText>\n"
+"  \n"
+" <a:commandButton id=\"findHotels\" value=\"Find Hotels\" action=\"#{hotelSearch.find}\" \n"
+" reRender=\"searchResults\"/>\n"
+"  \n"
+" <a:status>\n"
+" <f:facet name=\"start\">\n"
+" <h:graphicImage value=\"/img/spinner.gif\"/>\n"
+" </f:facet>\n"
+" </a:status>\n"
+" <br/>\n"
+" <h:outputLabel for=\"pageSize\">Maximum results:</h:outputLabel> \n"
+" <h:selectOneMenu value=\"#{hotelSearch.pageSize}\" id=\"pageSize\">\n"
+" <f:selectItem itemLabel=\"5\" itemValue=\"5\"/>\n"
+" <f:selectItem itemLabel=\"10\" itemValue=\"10\"/>\n"
+" <f:selectItem itemLabel=\"20\" itemValue=\"20\"/>\n"
+" </h:selectOneMenu>\n"
+" </fieldset>\n"
+" </h:form>\n"
+" \n"
+"</div>\n"
+"\n"
+"<a:outputPanel id=\"searchResults\">\n"
+" <div class=\"section\">\n"
+" <h:outputText value=\"No Hotels Found\"\n"
+" rendered=\"#{hotels != null and hotels.rowCount==0}\"/>\n"
+" <h:dataTable id=\"hotels\" value=\"#{hotels}\" var=\"hot\" \n"
+" rendered=\"#{hotels.rowCount>0}\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Name</f:facet>\n"
+" #{hot.name}\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Address</f:facet>\n"
+" #{hot.address}\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">City, State</f:facet>\n"
+" #{hot.city}, #{hot.state}, #{hot.country}\n"
+" </h:column> \n"
+" <h:column>\n"
+" <f:facet name=\"header\">Zip</f:facet>\n"
+" #{hot.zip}\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Action</f:facet>\n"
+" <s:link id=\"viewHotel\" value=\"View Hotel\" \n"
+" action=\"#{hotelBooking.selectHotel(hot)}\"/>\n"
+" </h:column>\n"
+" </h:dataTable>\n"
+" <s:link value=\"More results\" action=\"#{hotelSearch.nextPage}\" \n"
+" rendered=\"#{hotelSearch.nextPageAvailable}\"/>\n"
+" </div>\n"
+"</a:outputPanel> ]]>"
#. Tag: para
#: Tutorial.xml:1367
#, no-c-format
-msgid ""
-"The RichFaces Ajax <literal><a:support></literal> tag allows a JSF "
-"action event listener to be called by asynchronous <literal>XMLHttpRequest</"
-"literal> when a JavaScript event like <literal>onkeyup</literal> occurs. "
-"Even better, the <literal>reRender</literal> attribute lets us render a "
-"fragment of the JSF page and perform a partial page update when the "
-"asynchronous response is received."
+msgid "The RichFaces Ajax <literal><a:support></literal> tag allows a JSF action event listener to be called by asynchronous <literal>XMLHttpRequest</literal> when a JavaScript event like <literal>onkeyup</literal> occurs. Even better, the <literal>reRender</literal> attribute lets us render a fragment of the JSF page and perform a partial page update when the asynchronous response is received."
msgstr ""
#. Tag: para
#: Tutorial.xml:1374
#, no-c-format
-msgid ""
-"The RichFaces Ajax <literal><a:status></literal> tag lets us display "
-"an animated image while we wait for asynchronous requests to return."
+msgid "The RichFaces Ajax <literal><a:status></literal> tag lets us display an animated image while we wait for asynchronous requests to return."
msgstr ""
#. Tag: para
#: Tutorial.xml:1378
#, no-c-format
-msgid ""
-"The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a "
-"region of the page which can be re-rendered by an asynchronous request."
+msgid "The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a region of the page which can be re-rendered by an asynchronous request."
msgstr ""
#. Tag: para
#: Tutorial.xml:1382
#, no-c-format
-msgid ""
-"The Seam <literal><s:link></literal> tag lets us attach a JSF action "
-"listener to an ordinary (non-JavaScript) HTML link. The advantage of this "
-"over the standard JSF <literal><h:commandLink></literal> is that it "
-"preserves the operation of \"open in new window\" and \"open in new tab\". "
-"Also notice that we use a method binding with a parameter: <literal>#"
-"{hotelBooking.selectHotel(hot)}</literal>. This is not possible in the "
-"standard Unified EL, but Seam provides an extension to the EL that lets you "
-"use parameters on any method binding expression."
+msgid "The Seam <literal><s:link></literal> tag lets us attach a JSF action listener to an ordinary (non-JavaScript) HTML link. The advantage of this over the standard JSF <literal><h:commandLink></literal> is that it preserves the operation of \"open in new window\" and \"open in new tab\". Also notice that we use a method binding with a parameter: <literal>#{hotelBooking.selectHotel(hot)}</literal>. This is not possible in the standard Unified EL, but Seam provides an extension to the EL that lets you use parameters on any method binding expression."
msgstr ""
#. Tag: para
#: Tutorial.xml:1389
#, no-c-format
-msgid ""
-"If you're wondering how navigation occurs, you can find all the rules in "
-"<literal>WEB-INF/pages.xml</literal>; this is discussed in <xref linkend="
-"\"events.pageaction.navigation\"/>."
+msgid "If you're wondering how navigation occurs, you can find all the rules in <literal>WEB-INF/pages.xml</literal>; this is discussed in <xref linkend=\"events.pageaction.navigation\"/>."
msgstr ""
#. Tag: para
#: Tutorial.xml:1398
#, no-c-format
-msgid ""
-"This page displays the search results dynamically as we type, and lets us "
-"choose a hotel and pass it to the <literal>selectHotel()</literal> method of "
-"the <literal>HotelBookingAction</literal>, which is where the "
-"<emphasis>really</emphasis> interesting stuff is going to happen."
+msgid "This page displays the search results dynamically as we type, and lets us choose a hotel and pass it to the <literal>selectHotel()</literal> method of the <literal>HotelBookingAction</literal>, which is where the <emphasis>really</emphasis> interesting stuff is going to happen."
msgstr ""
#. Tag: para
#: Tutorial.xml:1403
#, no-c-format
-msgid ""
-"Now let's see how the booking example application uses a conversation-scoped "
-"stateful session bean to achieve a natural cache of persistent data related "
-"to the conversation. The following code example is pretty long. But if you "
-"think of it as a list of scripted actions that implement the various steps "
-"of the conversation, it's understandable. Read the class from top to bottom, "
-"as if it were a story."
+msgid "Now let's see how the booking example application uses a conversation-scoped stateful session bean to achieve a natural cache of persistent data related to the conversation. The following code example is pretty long. But if you think of it as a list of scripted actions that implement the various steps of the conversation, it's understandable. Read the class from top to bottom, as if it were a story."
msgstr ""
#. Tag: title
-#: Tutorial.xml:1408 Tutorial.xml:1633
+#: Tutorial.xml:1408
+#: Tutorial.xml:1633
#, no-c-format
msgid "HotelBookingAction.java"
msgstr ""
@@ -3515,16 +3714,13 @@
" calendar.add(Calendar.DAY_OF_MONTH, -1);\n"
" if ( booking.getCheckinDate().before( calendar.getTime() ) )\n"
" {\n"
-" facesMessages.addToControl(\"checkinDate\", \"Check in date must be "
-"a future date\");\n"
+" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n"
" bookingValid=false;\n"
" }\n"
-" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate"
-"() ) )\n"
+" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n"
" {\n"
" facesMessages.addToControl(\"checkoutDate\", \n"
-" \"Check out date must be later than "
-"check in date\");\n"
+" \"Check out date must be later than check in date\");\n"
" bookingValid=false;\n"
" }\n"
" else\n"
@@ -3542,8 +3738,7 @@
" public void confirm()\n"
" {\n"
" em.persist(booking);\n"
-" facesMessages.add(\"Thank you, #{user.name}, your confimation number "
-"\" + \n"
+" facesMessages.add(\"Thank you, #{user.name}, your confimation number \" + \n"
" \" for #{hotel.name} is #{booki g.id}\");\n"
" log.info(\"New booking: #{booking.id} for #{user.username}\");\n"
" events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n"
@@ -3556,82 +3751,134 @@
" public void destroy() {}\n"
"]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"hotelBooking\")\n"
+"@Restrict(\"#{identity.loggedIn}\")\n"
+"public class HotelBookingAction implements HotelBooking\n"
+"{\n"
+" \n"
+" @PersistenceContext(type=EXTENDED)\n"
+" private EntityManager em;\n"
+" \n"
+" @In \n"
+" private User user;\n"
+" \n"
+" @In(required=false) @Out\n"
+" private Hotel hotel;\n"
+" \n"
+" @In(required=false) \n"
+" @Out(required=false)\n"
+" private Booking booking;\n"
+" \n"
+" @In\n"
+" private FacesMessages facesMessages;\n"
+" \n"
+" @In\n"
+" private Events events;\n"
+" \n"
+" @Logger \n"
+" private Log log;\n"
+" \n"
+" private boolean bookingValid;\n"
+" \n"
+" @Begin\n"
+" public void selectHotel(Hotel selectedHotel)\n"
+" {\n"
+" hotel = em.merge(selectedHotel);\n"
+" }\n"
+" \n"
+" public void bookHotel()\n"
+" { \n"
+" booking = new Booking(hotel, user);\n"
+" Calendar calendar = Calendar.getInstance();\n"
+" booking.setCheckinDate( calendar.getTime() );\n"
+" calendar.add(Calendar.DAY_OF_MONTH, 1);\n"
+" booking.setCheckoutDate( calendar.getTime() );\n"
+" }\n"
+" \n"
+" public void setBookingDetails()\n"
+" {\n"
+" Calendar calendar = Calendar.getInstance();\n"
+" calendar.add(Calendar.DAY_OF_MONTH, -1);\n"
+" if ( booking.getCheckinDate().before( calendar.getTime() ) )\n"
+" {\n"
+" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n"
+" bookingValid=false;\n"
+" }\n"
+" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n"
+" {\n"
+" facesMessages.addToControl(\"checkoutDate\", \n"
+" \"Check out date must be later than check in date\");\n"
+" bookingValid=false;\n"
+" }\n"
+" else\n"
+" {\n"
+" bookingValid=true;\n"
+" }\n"
+" }\n"
+" \n"
+" public boolean isBookingValid()\n"
+" {\n"
+" return bookingValid;\n"
+" }\n"
+" \n"
+" @End\n"
+" public void confirm()\n"
+" {\n"
+" em.persist(booking);\n"
+" facesMessages.add(\"Thank you, #{user.name}, your confimation number \" + \n"
+" \" for #{hotel.name} is #{booki g.id}\");\n"
+" log.info(\"New booking: #{booking.id} for #{user.username}\");\n"
+" events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n"
+" }\n"
+" \n"
+" @End\n"
+" public void cancel() {}\n"
+" \n"
+" @Remove\n"
+" public void destroy() {}\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1421
#, no-c-format
-msgid ""
-"This bean uses an EJB3 <emphasis>extended persistence context</emphasis>, so "
-"that any entity instances remain managed for the whole lifecycle of the "
-"stateful session bean."
+msgid "This bean uses an EJB3 <emphasis>extended persistence context</emphasis>, so that any entity instances remain managed for the whole lifecycle of the stateful session bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:1426
#, no-c-format
-msgid ""
-"The <link linkend=\"out-annotation\"> <literal>@Out</literal> </link> "
-"annotation declares that an attribute value is <emphasis>outjected</"
-"emphasis> to a context variable after method invocations. In this case, the "
-"context variable named <literal>hotel</literal> will be set to the value of "
-"the <literal>hotel</literal> instance variable after every action listener "
-"invocation completes."
+msgid "The <link linkend=\"out-annotation\"> <literal>@Out</literal> </link> annotation declares that an attribute value is <emphasis>outjected</emphasis> to a context variable after method invocations. In this case, the context variable named <literal>hotel</literal> will be set to the value of the <literal>hotel</literal> instance variable after every action listener invocation completes."
msgstr ""
#. Tag: para
#: Tutorial.xml:1434
#, no-c-format
-msgid ""
-"The <link linkend=\"begin-annotation\"> <literal>@Begin</literal> </link> "
-"annotation specifies that the annotated method begins a <emphasis>long-"
-"running conversation</emphasis>, so the current conversation context will "
-"not be destroyed at the end of the request. Instead, it will be reassociated "
-"with every request from the current window, and destroyed either by timeout "
-"due to conversation inactivity or invocation of a matching <literal>@End</"
-"literal> method."
+msgid "The <link linkend=\"begin-annotation\"> <literal>@Begin</literal> </link> annotation specifies that the annotated method begins a <emphasis>long-running conversation</emphasis>, so the current conversation context will not be destroyed at the end of the request. Instead, it will be reassociated with every request from the current window, and destroyed either by timeout due to conversation inactivity or invocation of a matching <literal>@End</literal> method."
msgstr ""
#. Tag: para
#: Tutorial.xml:1443
#, no-c-format
-msgid ""
-"The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> "
-"annotation specifies that the annotated method ends the current long-running "
-"conversation, so the current conversation context will be destroyed at the "
-"end of the request."
+msgid "The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> annotation specifies that the annotated method ends the current long-running conversation, so the current conversation context will be destroyed at the end of the request."
msgstr ""
#. Tag: para
#: Tutorial.xml:1450
#, no-c-format
-msgid ""
-"This EJB remove method will be called when Seam destroys the conversation "
-"context. Don't forget to define this method!"
+msgid "This EJB remove method will be called when Seam destroys the conversation context. Don't forget to define this method!"
msgstr ""
#. Tag: para
#: Tutorial.xml:1458
#, no-c-format
-msgid ""
-"<literal>HotelBookingAction</literal> contains all the action listener "
-"methods that implement selection, booking and booking confirmation, and "
-"holds state related to this work in its instance variables. We think you'll "
-"agree that this code is much cleaner and simpler than getting and setting "
-"<literal>HttpSession</literal> attributes."
+msgid "<literal>HotelBookingAction</literal> contains all the action listener methods that implement selection, booking and booking confirmation, and holds state related to this work in its instance variables. We think you'll agree that this code is much cleaner and simpler than getting and setting <literal>HttpSession</literal> attributes."
msgstr ""
#. Tag: para
#: Tutorial.xml:1464
#, no-c-format
-msgid ""
-"Even better, a user can have multiple isolated conversations per login "
-"session. Try it! Log in, run a search, and navigate to different hotel pages "
-"in multiple browser tabs. You'll be able to work on creating two different "
-"hotel reservations at the same time. If you leave any one conversation "
-"inactive for long enough, Seam will eventually time out that conversation "
-"and destroy its state. If, after ending a conversation, you backbutton to a "
-"page of that conversation and try to perform an action, Seam will detect "
-"that the conversation was already ended, and redirect you to the search page."
+msgid "Even better, a user can have multiple isolated conversations per login session. Try it! Log in, run a search, and navigate to different hotel pages in multiple browser tabs. You'll be able to work on creating two different hotel reservations at the same time. If you leave any one conversation inactive for long enough, Seam will eventually time out that conversation and destroy its state. If, after ending a conversation, you backbutton to a page of that conversation and try to perform an action, Seam will detect that the conversation was already ended, and redirect you to the search page."
msgstr ""
#. Tag: title
@@ -3643,27 +3890,19 @@
#. Tag: para
#: Tutorial.xml:1476
#, no-c-format
-msgid ""
-"The WAR also includes <literal>seam-debug.jar</literal>. The Seam debug page "
-"will be available if this jar is deployed in <literal>WEB-INF/lib</literal>, "
-"along with the Facelets, and if you set the debug property of the "
-"<literal>init</literal> component:"
+msgid "The WAR also includes <literal>seam-debug.jar</literal>. The Seam debug page will be available if this jar is deployed in <literal>WEB-INF/lib</literal>, along with the Facelets, and if you set the debug property of the <literal>init</literal> component:"
msgstr ""
#. Tag: programlisting
#: Tutorial.xml:1481
#, no-c-format
msgid "<![CDATA[<core:init jndi-pattern=\"@jndiPattern@\" debug=\"true\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<core:init jndi-pattern=\"@jndiPattern@\" debug=\"true\"/>]]>"
#. Tag: para
#: Tutorial.xml:1483
#, no-c-format
-msgid ""
-"This page lets you browse and inspect the Seam components in any of the Seam "
-"contexts associated with your current login session. Just point your browser "
-"at <ulink url=\"http://localhost:8080/seam-booking/debug.seam\"> "
-"<literal>http://localhost:8080/seam-booking/debug.seam</literal> </ulink>."
+msgid "This page lets you browse and inspect the Seam components in any of the Seam contexts associated with your current login session. Just point your browser at <ulink url=\"http://localhost:8080/seam-booking/debug.seam\"> <literal>http://localhost:8080/seam-booking/debug.seam</literal> </ulink>."
msgstr ""
#. Tag: title
@@ -3675,58 +3914,31 @@
#. Tag: para
#: Tutorial.xml:1508
#, no-c-format
-msgid ""
-"Long-running conversations make it simple to maintain consistency of state "
-"in an application even in the face of multi-window operation and back-"
-"buttoning. Unfortunately, simply beginning and ending a long-running "
-"conversation is not always enough. Depending on the requirements of the "
-"application, inconsistencies between what the user's expectations and the "
-"reality of the application’s state can still result."
+msgid "Long-running conversations make it simple to maintain consistency of state in an application even in the face of multi-window operation and back-buttoning. Unfortunately, simply beginning and ending a long-running conversation is not always enough. Depending on the requirements of the application, inconsistencies between what the user's expectations and the reality of the application’s state can still result."
msgstr ""
#. Tag: para
#: Tutorial.xml:1513
#, no-c-format
-msgid ""
-"The nested booking application extends the features of the hotel booking "
-"application to incorporate the selection of rooms. Each hotel has available "
-"rooms with descriptions for a user to select from. This requires the "
-"addition of a room selection page in the hotel reservation flow."
+msgid "The nested booking application extends the features of the hotel booking application to incorporate the selection of rooms. Each hotel has available rooms with descriptions for a user to select from. This requires the addition of a room selection page in the hotel reservation flow."
msgstr ""
#. Tag: para
#: Tutorial.xml:1526
#, no-c-format
-msgid ""
-"The user now has the option to select any available room to be included in "
-"the booking. As with the hotel booking application we saw previously, this "
-"can lead to issues with state consistency. As with storing state in the "
-"<varname>HTTPSession</varname>, if a conversation variable changes it "
-"affects all windows operating within the same conversation context."
+msgid "The user now has the option to select any available room to be included in the booking. As with the hotel booking application we saw previously, this can lead to issues with state consistency. As with storing state in the <varname>HTTPSession</varname>, if a conversation variable changes it affects all windows operating within the same conversation context."
msgstr ""
#. Tag: para
#: Tutorial.xml:1531
#, no-c-format
-msgid ""
-"To demonstrate this, let’s suppose the user clones the room selection screen "
-"in a new window. The user then selects the <emphasis>Wonderful Room</"
-"emphasis> and proceeds to the confirmation screen. To see just how much it "
-"would cost to live the high-life, the user returns to the original window, "
-"selects the <emphasis>Fantastic Suite</emphasis> for booking, and again "
-"proceeds to confirmation. After reviewing the total cost, the user decides "
-"that practicality wins out and returns to the window showing "
-"<emphasis>Wonderful Room</emphasis> to confirm."
+msgid "To demonstrate this, let’s suppose the user clones the room selection screen in a new window. The user then selects the <emphasis>Wonderful Room</emphasis> and proceeds to the confirmation screen. To see just how much it would cost to live the high-life, the user returns to the original window, selects the <emphasis>Fantastic Suite</emphasis> for booking, and again proceeds to confirmation. After reviewing the total cost, the user decides that practicality wins out and returns to the window showing <emphasis>Wonderful Room</emphasis> to confirm."
msgstr ""
#. Tag: para
#: Tutorial.xml:1537
#, no-c-format
-msgid ""
-"In this scenario, if we simply store all state in the conversation, we are "
-"not protected from multi-window operation within the same conversation. "
-"Nested conversations allow us to achieve correct behavior even when context "
-"can vary within the same conversation."
+msgid "In this scenario, if we simply store all state in the conversation, we are not protected from multi-window operation within the same conversation. Nested conversations allow us to achieve correct behavior even when context can vary within the same conversation."
msgstr ""
#. Tag: title
@@ -3738,10 +3950,7 @@
#. Tag: para
#: Tutorial.xml:1545
#, no-c-format
-msgid ""
-"Now let's see how the nested booking example extends the behavior of the "
-"hotel booking application through use of nested conversations. Again, we can "
-"read the class from top to bottom, as if it were a story."
+msgid "Now let's see how the nested booking example extends the behavior of the hotel booking application through use of nested conversations. Again, we can read the class from top to bottom, as if it were a story."
msgstr ""
#. Tag: title
@@ -3780,8 +3989,7 @@
" @Factory(\"availableRooms\")\n"
" public void loadAvailableRooms()\n"
" {\n"
-" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), "
-"booking.getCheckoutDate());\n"
+" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), booking.getCheckoutDate());\n"
" log.info(\"Retrieved #0 available rooms\", availableRooms.size());\n"
" }\n"
"\n"
@@ -3804,8 +4012,7 @@
"\n"
" public String requestConfirmation()\n"
" {\n"
-" // all validations are performed through the s:validateAll, so checks "
-"are already\n"
+" // all validations are performed through the s:validateAll, so checks are already\n"
" // performed\n"
" log.info(\"Request confirmation from user\");\n"
" \n"
@@ -3820,68 +4027,108 @@
" return \"cancel\";\n"
" }\n"
"\n"
-" @Destroy "
-"@Remove \n"
+" @Destroy @Remove \n"
" public void destroy() {} \n"
"}\n"
"]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"roomPreference\")\n"
+"@Restrict(\"#{identity.loggedIn}\")\n"
+"public class RoomPreferenceAction implements RoomPreference \n"
+"{\n"
+"\n"
+" @Logger \n"
+" private Log log;\n"
+"\n"
+" @In private Hotel hotel;\n"
+" \n"
+" @In private Booking booking;\n"
+"\n"
+" @DataModel(value=\"availableRooms\")\n"
+" private List<Room> availableRooms;\n"
+"\n"
+" @DataModelSelection(value=\"availableRooms\")\n"
+" private Room roomSelection;\n"
+" \n"
+" @In(required=false, value=\"roomSelection\")\n"
+" @Out(required=false, value=\"roomSelection\")\n"
+" private Room room;\n"
+"\n"
+" @Factory(\"availableRooms\")\n"
+" public void loadAvailableRooms()\n"
+" {\n"
+" availableRooms = hotel.getAvailableRooms(booking.getCheckinDate(), booking.getCheckoutDate());\n"
+" log.info(\"Retrieved #0 available rooms\", availableRooms.size());\n"
+" }\n"
+"\n"
+" public BigDecimal getExpectedPrice()\n"
+" {\n"
+" log.info(\"Retrieving price for room #0\", roomSelection.getName());\n"
+" \n"
+" return booking.getTotal(roomSelection);\n"
+" }\n"
+"\n"
+" @Begin(nested=true)\n"
+" public String selectPreference()\n"
+" {\n"
+" log.info(\"Room selected\");\n"
+" \n"
+" this.room = this.roomSelection;\n"
+" \n"
+" return \"payment\";\n"
+" }\n"
+"\n"
+" public String requestConfirmation()\n"
+" {\n"
+" // all validations are performed through the s:validateAll, so checks are already\n"
+" // performed\n"
+" log.info(\"Request confirmation from user\");\n"
+" \n"
+" return \"confirm\";\n"
+" }\n"
+"\n"
+" @End(beforeRedirect=true)\n"
+" public String cancel()\n"
+" {\n"
+" log.info(\"ending conversation\");\n"
+"\n"
+" return \"cancel\";\n"
+" }\n"
+"\n"
+" @Destroy @Remove \n"
+" public void destroy() {} \n"
+"}\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1561
#, no-c-format
-msgid ""
-"The <varname>hotel</varname> instance is injected from the conversation "
-"context. The hotel is loaded through an <emphasis>extended persistence "
-"context</emphasis> so that the entity remains managed throughout the "
-"conversation. This allows us to lazily load the <varname>availableRooms</"
-"varname> through an <varname>@Factory</varname> method by simply walking the "
-"assocation."
+msgid "The <varname>hotel</varname> instance is injected from the conversation context. The hotel is loaded through an <emphasis>extended persistence context</emphasis> so that the entity remains managed throughout the conversation. This allows us to lazily load the <varname>availableRooms</varname> through an <varname>@Factory</varname> method by simply walking the assocation."
msgstr ""
#. Tag: para
#: Tutorial.xml:1569
#, no-c-format
-msgid ""
-"When <link linkend=\"begin-annotation\"> <literal>@Begin(nested=true)</"
-"literal> </link> is encountered, a nested conversation is pushed onto the "
-"conversation stack. When executing within a nested conversation, components "
-"still have access to all outer conversation state, but setting any values in "
-"the nested conversation’s state container does not affect the outer "
-"conversation. In addition, nested conversations can exist concurrently "
-"stacked on the same outer conversation, allowing independent state for each."
+msgid "When <link linkend=\"begin-annotation\"> <literal>@Begin(nested=true)</literal> </link> is encountered, a nested conversation is pushed onto the conversation stack. When executing within a nested conversation, components still have access to all outer conversation state, but setting any values in the nested conversation’s state container does not affect the outer conversation. In addition, nested conversations can exist concurrently stacked on the same outer conversation, allowing independent state for each."
msgstr ""
#. Tag: para
#: Tutorial.xml:1578
#, no-c-format
-msgid ""
-"The <varname>roomSelection</varname> is outjected to the conversation based "
-"on the <varname>@DataModelSelection</varname>. Note that because the nested "
-"conversation has an independent context, the <varname>roomSelection</"
-"varname> is only set into the new nested conversation. Should the user "
-"select a different preference in another window or tab a new nested "
-"conversation would be started."
+msgid "The <varname>roomSelection</varname> is outjected to the conversation based on the <varname>@DataModelSelection</varname>. Note that because the nested conversation has an independent context, the <varname>roomSelection</varname> is only set into the new nested conversation. Should the user select a different preference in another window or tab a new nested conversation would be started."
msgstr ""
#. Tag: para
#: Tutorial.xml:1585
#, no-c-format
-msgid ""
-"The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> "
-"annotation pops the conversation stack and resumes the outer conversation. "
-"The <varname>roomSelection</varname> is destroyed along with the "
-"conversation context."
+msgid "The <link linkend=\"end-annotation\"> <literal>@End</literal> </link> annotation pops the conversation stack and resumes the outer conversation. The <varname>roomSelection</varname> is destroyed along with the conversation context."
msgstr ""
#. Tag: para
#: Tutorial.xml:1594
#, no-c-format
-msgid ""
-"When we being a nested conversation it is pushed onto the conversation "
-"stack. In the <varname>nestedbooking</varname> example, the conversation "
-"stack consists of the outer long-running conversation (the booking) and each "
-"of the nested conversations (room selections)."
+msgid "When we being a nested conversation it is pushed onto the conversation stack. In the <varname>nestedbooking</varname> example, the conversation stack consists of the outer long-running conversation (the booking) and each of the nested conversations (room selections)."
msgstr ""
#. Tag: title
@@ -3903,17 +4150,13 @@
" <div class=\"section\">\n"
" <h:outputText styleClass=\"output\" \n"
" value=\"No rooms available for the dates selected: \" \n"
-" rendered=\"#{availableRooms != null and availableRooms."
-"rowCount == 0}\"/>\n"
+" rendered=\"#{availableRooms != null and availableRooms.rowCount == 0}\"/>\n"
" <h:outputText styleClass=\"output\" \n"
" value=\"Rooms available for the dates selected: \" \n"
-" rendered=\"#{availableRooms != null and availableRooms."
-"rowCount > 0}\"/>\n"
+" rendered=\"#{availableRooms != null and availableRooms.rowCount > 0}\"/>\n"
" \n"
-" <h:outputText styleClass=\"output\" value=\"#{booking."
-"checkinDate}\"/> -\n"
-" <h:outputText styleClass=\"output\" value=\"#{booking."
-"checkoutDate}\"/>\n"
+" <h:outputText styleClass=\"output\" value=\"#{booking.checkinDate}\"/> -\n"
+" <h:outputText styleClass=\"output\" value=\"#{booking.checkoutDate}\"/>\n"
" \n"
" <br/><br/>\n"
" \n"
@@ -3930,70 +4173,100 @@
" <h:column>\n"
" <f:facet name=\"header\">Per Night</f:facet>\n"
" <h:outputText value=\"#{room.price}\">\n"
-" <f:convertNumber type=\"currency\" currencySymbol=\"$"
-"\"/>\n"
+" <f:convertNumber type=\"currency\" currencySymbol=\"$\"/>\n"
" </h:outputText>\n"
" </h:column>\n"
" <h:column>\n"
" <f:facet name=\"header\">Action</f:facet>\n"
" <h:commandLink id=\"selectRoomPreference\" \n"
-" action=\"#{roomPreference.selectPreference}"
-"\">Select</h:commandLink>\n"
+" action=\"#{roomPreference.selectPreference}\">Select</h:commandLink>\n"
" </h:column>\n"
" </h:dataTable>\n"
" </div>\n"
" <div class=\"entry\">\n"
" <div class=\"label\"> </div>\n"
" <div class=\"input\">\n"
-" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book."
-"xhtml\"/>\n"
+" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book.xhtml\"/>\n"
" </div>\n"
" </div> \n"
" </h:form>\n"
"</div>\n"
"]]>"
msgstr ""
+"<![CDATA[<div class=\"section\">\n"
+" <h1>Room Preference</h1>\n"
+"</div>\n"
+"\n"
+"<div class=\"section\">\n"
+" <h:form id=\"room_selections_form\">\n"
+" <div class=\"section\">\n"
+" <h:outputText styleClass=\"output\" \n"
+" value=\"No rooms available for the dates selected: \" \n"
+" rendered=\"#{availableRooms != null and availableRooms.rowCount == 0}\"/>\n"
+" <h:outputText styleClass=\"output\" \n"
+" value=\"Rooms available for the dates selected: \" \n"
+" rendered=\"#{availableRooms != null and availableRooms.rowCount > 0}\"/>\n"
+" \n"
+" <h:outputText styleClass=\"output\" value=\"#{booking.checkinDate}\"/> -\n"
+" <h:outputText styleClass=\"output\" value=\"#{booking.checkoutDate}\"/>\n"
+" \n"
+" <br/><br/>\n"
+" \n"
+" <h:dataTable value=\"#{availableRooms}\" var=\"room\" \n"
+" rendered=\"#{availableRooms.rowCount > 0}\">\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Name</f:facet>\n"
+" #{room.name}\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Description</f:facet>\n"
+" #{room.description}\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Per Night</f:facet>\n"
+" <h:outputText value=\"#{room.price}\">\n"
+" <f:convertNumber type=\"currency\" currencySymbol=\"$\"/>\n"
+" </h:outputText>\n"
+" </h:column>\n"
+" <h:column>\n"
+" <f:facet name=\"header\">Action</f:facet>\n"
+" <h:commandLink id=\"selectRoomPreference\" \n"
+" action=\"#{roomPreference.selectPreference}\">Select</h:commandLink>\n"
+" </h:column>\n"
+" </h:dataTable>\n"
+" </div>\n"
+" <div class=\"entry\">\n"
+" <div class=\"label\"> </div>\n"
+" <div class=\"input\">\n"
+" <s:button id=\"cancel\" value=\"Revise Dates\" view=\"/book.xhtml\"/>\n"
+" </div>\n"
+" </div> \n"
+" </h:form>\n"
+"</div>\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1610
#, no-c-format
-msgid ""
-"When requested from EL, the <varname>#{availableRooms}</varname> are loaded "
-"by the <varname>@Factory</varname> method defined in "
-"<varname>RoomPreferenceAction</varname>. The <varname>@Factory</varname> "
-"method will only be executed once to load the values into the current "
-"context as a <link linkend=\"datamodel-annotation\"> <varname>@DataModel</"
-"varname> </link> instance."
+msgid "When requested from EL, the <varname>#{availableRooms}</varname> are loaded by the <varname>@Factory</varname> method defined in <varname>RoomPreferenceAction</varname>. The <varname>@Factory</varname> method will only be executed once to load the values into the current context as a <link linkend=\"datamodel-annotation\"> <varname>@DataModel</varname> </link> instance."
msgstr ""
#. Tag: para
#: Tutorial.xml:1617
#, no-c-format
-msgid ""
-"Invoking the <varname>#{roomPreference.selectPreference}</varname> action "
-"results in the row being selected and set into the "
-"<varname>@DataModelSelection</varname>. This value is then outjected to the "
-"nested conversation context."
+msgid "Invoking the <varname>#{roomPreference.selectPreference}</varname> action results in the row being selected and set into the <varname>@DataModelSelection</varname>. This value is then outjected to the nested conversation context."
msgstr ""
#. Tag: para
#: Tutorial.xml:1621
#, no-c-format
-msgid ""
-"Revising the dates simply returns to the <varname>/book.xhtml</varname>. "
-"Note that we have not yet nested a conversation (no room preference has been "
-"selected), so the current conversation can simply be resumed. The "
-"<varname><s:button></varname> component simply propagates the current "
-"conversation when displaying the <varname>/book.xhtml</varname> view."
+msgid "Revising the dates simply returns to the <varname>/book.xhtml</varname>. Note that we have not yet nested a conversation (no room preference has been selected), so the current conversation can simply be resumed. The <varname><s:button></varname> component simply propagates the current conversation when displaying the <varname>/book.xhtml</varname> view."
msgstr ""
#. Tag: para
#: Tutorial.xml:1629
#, no-c-format
-msgid ""
-"Now that we have seen how to nest a conversation, let's see how we can "
-"confirm the booking once a room has been selected. This can be achieved by "
-"simply extending the behavior of the <varname>HotelBookingAction</varname>."
+msgid "Now that we have seen how to nest a conversation, let's see how we can confirm the booking once a room has been selected. This can be achieved by simply extending the behavior of the <varname>HotelBookingAction</varname>."
msgstr ""
#. Tag: programlisting
@@ -4040,12 +4313,9 @@
" \n"
" public String setBookingDates()\n"
" {\n"
-" // the result will indicate whether or not to begin the nested "
-"conversation\n"
-" // as well as the navigation. if a null result is returned, the "
-"nested\n"
-" // conversation will not begin, and the user will be returned to the "
-"current\n"
+" // the result will indicate whether or not to begin the nested conversation\n"
+" // as well as the navigation. if a null result is returned, the nested\n"
+" // conversation will not begin, and the user will be returned to the current\n"
" // page to fix validation issues\n"
" String result = null;\n"
"\n"
@@ -4055,14 +4325,11 @@
" // validate what we have received from the user so far\n"
" if ( booking.getCheckinDate().before( calendar.getTime() ) )\n"
" {\n"
-" facesMessages.addToControl(\"checkinDate\", \"Check in date must be "
-"a future date\");\n"
+" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n"
" }\n"
-" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate"
-"() ) )\n"
+" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n"
" {\n"
-" facesMessages.addToControl(\"checkoutDate\", \"Check out date must "
-"be later than check in date\");\n"
+" facesMessages.addToControl(\"checkoutDate\", \"Check out date must be later than check in date\");\n"
" }\n"
" else\n"
" {\n"
@@ -4084,14 +4351,12 @@
" @End(root=true)\n"
" public void confirm()\n"
" {\n"
-" // on confirmation we set the room preference in the booking. the "
-"room preference\n"
+" // on confirmation we set the room preference in the booking. the room preference\n"
" // will be injected based on the nested conversation we are in.\n"
" booking.setRoomPreference(roomSelection);\n"
"\n"
" em.persist(booking);\n"
-" facesMessages.add(\"Thank you, #{user.name}, your confimation number "
-"for #{hotel.name} is #{booking.id}\");\n"
+" facesMessages.add(\"Thank you, #{user.name}, your confimation number for #{hotel.name} is #{booking.id}\");\n"
" log.info(\"New booking: #{booking.id} for #{user.username}\");\n"
" events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n"
" }\n"
@@ -4104,49 +4369,124 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[@Stateful\n"
+"@Name(\"hotelBooking\")\n"
+"@Restrict(\"#{identity.loggedIn}\")\n"
+"public class HotelBookingAction implements HotelBooking\n"
+"{\n"
+" \n"
+" @PersistenceContext(type=EXTENDED)\n"
+" private EntityManager em;\n"
+" \n"
+" @In \n"
+" private User user;\n"
+" \n"
+" @In(required=false) @Out\n"
+" private Hotel hotel;\n"
+" \n"
+" @In(required=false) \n"
+" @Out(required=false)\n"
+" private Booking booking;\n"
+" \n"
+" @In(required=false)\n"
+" private Room roomSelection;\n"
+" \n"
+" @In\n"
+" private FacesMessages facesMessages;\n"
+" \n"
+" @In\n"
+" private Events events;\n"
+" \n"
+" @Logger \n"
+" private Log log;\n"
+" \n"
+" @Begin\n"
+" public void selectHotel(Hotel selectedHotel)\n"
+" {\n"
+" log.info(\"Selected hotel #0\", selectedHotel.getName());\n"
+" hotel = em.merge(selectedHotel);\n"
+" }\n"
+" \n"
+" public String setBookingDates()\n"
+" {\n"
+" // the result will indicate whether or not to begin the nested conversation\n"
+" // as well as the navigation. if a null result is returned, the nested\n"
+" // conversation will not begin, and the user will be returned to the current\n"
+" // page to fix validation issues\n"
+" String result = null;\n"
+"\n"
+" Calendar calendar = Calendar.getInstance();\n"
+" calendar.add(Calendar.DAY_OF_MONTH, -1);\n"
+"\n"
+" // validate what we have received from the user so far\n"
+" if ( booking.getCheckinDate().before( calendar.getTime() ) )\n"
+" {\n"
+" facesMessages.addToControl(\"checkinDate\", \"Check in date must be a future date\");\n"
+" }\n"
+" else if ( !booking.getCheckinDate().before( booking.getCheckoutDate() ) )\n"
+" {\n"
+" facesMessages.addToControl(\"checkoutDate\", \"Check out date must be later than check in date\");\n"
+" }\n"
+" else\n"
+" {\n"
+" result = \"rooms\";\n"
+" }\n"
+"\n"
+" return result;\n"
+" }\n"
+" \n"
+" public void bookHotel()\n"
+" { \n"
+" booking = new Booking(hotel, user);\n"
+" Calendar calendar = Calendar.getInstance();\n"
+" booking.setCheckinDate( calendar.getTime() );\n"
+" calendar.add(Calendar.DAY_OF_MONTH, 1);\n"
+" booking.setCheckoutDate( calendar.getTime() );\n"
+" }\n"
+" \n"
+" @End(root=true)\n"
+" public void confirm()\n"
+" {\n"
+" // on confirmation we set the room preference in the booking. the room preference\n"
+" // will be injected based on the nested conversation we are in.\n"
+" booking.setRoomPreference(roomSelection);\n"
+"\n"
+" em.persist(booking);\n"
+" facesMessages.add(\"Thank you, #{user.name}, your confimation number for #{hotel.name} is #{booking.id}\");\n"
+" log.info(\"New booking: #{booking.id} for #{user.username}\");\n"
+" events.raiseTransactionSuccessEvent(\"bookingConfirmed\");\n"
+" }\n"
+" \n"
+" @End(root=true, beforeRedirect=true)\n"
+" public void cancel() {}\n"
+" \n"
+" @Destroy @Remove\n"
+" public void destroy() {}\n"
+"}\n"
+"]]>"
#. Tag: para
#: Tutorial.xml:1644
#, no-c-format
-msgid ""
-"Annotating an action with <link linkend=\"end-annotation\"> <varname>@End"
-"(root=true)</varname> </link> ends the root conversation which effectively "
-"destroys the entire conversation stack. When any conversation is ended, it's "
-"nested conversations are ended as well. As the root is the conversation that "
-"started it all, this is a simple way to destroy and release all state "
-"associated with a workspace once the booking is confirmed."
+msgid "Annotating an action with <link linkend=\"end-annotation\"> <varname>@End(root=true)</varname> </link> ends the root conversation which effectively destroys the entire conversation stack. When any conversation is ended, it's nested conversations are ended as well. As the root is the conversation that started it all, this is a simple way to destroy and release all state associated with a workspace once the booking is confirmed."
msgstr ""
#. Tag: para
#: Tutorial.xml:1652
#, no-c-format
-msgid ""
-"The <varname>roomSelection</varname> is only associated with the "
-"<varname>booking</varname> on user confirmation. While outjecting values to "
-"the nested conversation context will not impact the outer conversation, any "
-"objects injected from the outer conversation are injected by reference. This "
-"means that any changing to these objects will be reflected in the parent "
-"conversation as well as other concurrent nested conversations."
+msgid "The <varname>roomSelection</varname> is only associated with the <varname>booking</varname> on user confirmation. While outjecting values to the nested conversation context will not impact the outer conversation, any objects injected from the outer conversation are injected by reference. This means that any changing to these objects will be reflected in the parent conversation as well as other concurrent nested conversations."
msgstr ""
#. Tag: para
#: Tutorial.xml:1659
#, no-c-format
-msgid ""
-"By simply annotating the cancellation action with <link linkend=\"end-"
-"annotation\"> <varname>@End(root=true, beforeRedirect=true)</varname> </"
-"link> we can easily destroy and release all state associated with the "
-"workspace prior to redirecting the user back to the hotel selection view."
+msgid "By simply annotating the cancellation action with <link linkend=\"end-annotation\"> <varname>@End(root=true, beforeRedirect=true)</varname> </link> we can easily destroy and release all state associated with the workspace prior to redirecting the user back to the hotel selection view."
msgstr ""
#. Tag: para
#: Tutorial.xml:1669
#, no-c-format
-msgid ""
-"Feel free to deploy the application, open many windows or tabs and attempt "
-"combinations of various hotels with various room preferences. Confirming a "
-"booking always results in the correct hotel and room preference thanks to "
-"the nested conversation model."
+msgid "Feel free to deploy the application, open many windows or tabs and attempt combinations of various hotels with various room preferences. Confirming a booking always results in the correct hotel and room preference thanks to the nested conversation model."
msgstr ""
#. Tag: title
@@ -4158,21 +4498,18 @@
#. Tag: para
#: Tutorial.xml:1678
#, no-c-format
-msgid ""
-"The DVD Store demo application shows the practical usage of jBPM for both "
-"task management and pageflow."
+msgid "The DVD Store demo application shows the practical usage of jBPM for both task management and pageflow."
msgstr ""
#. Tag: para
#: Tutorial.xml:1680
#, no-c-format
-msgid ""
-"The user screens take advantage of a jPDL pageflow to implement searching "
-"and shopping cart functionality."
+msgid "The user screens take advantage of a jPDL pageflow to implement searching and shopping cart functionality."
msgstr ""
#. Tag: screeninfo
-#: Tutorial.xml:1684 Tutorial.xml:1699
+#: Tutorial.xml:1684
+#: Tutorial.xml:1699
#, no-c-format
msgid "DVD Store example"
msgstr ""
@@ -4180,18 +4517,13 @@
#. Tag: para
#: Tutorial.xml:1695
#, no-c-format
-msgid ""
-"The administration screens take use jBPM to manage the approval and shipping "
-"cycle for orders. The business process may even be changed dynamically, by "
-"selecting a different process definition!"
+msgid "The administration screens take use jBPM to manage the approval and shipping cycle for orders. The business process may even be changed dynamically, by selecting a different process definition!"
msgstr ""
#. Tag: para
#: Tutorial.xml:1711
#, no-c-format
-msgid ""
-"The Seam DVD Store demo can be run from <literal>dvdstore</literal> "
-"directory, just like the other demo applications."
+msgid "The Seam DVD Store demo can be run from <literal>dvdstore</literal> directory, just like the other demo applications."
msgstr ""
#. Tag: title
@@ -4203,16 +4535,7 @@
#. Tag: para
#: Tutorial.xml:1720
#, no-c-format
-msgid ""
-"Seam makes it very easy to implement applications which keep state on the "
-"server-side. However, server-side state is not always appropriate, "
-"especially in for functionality that serves up <emphasis>content</emphasis>. "
-"For this kind of problem we often want to keep application state in the URL "
-"so that any page can be accessed at any time through a bookmark. The blog "
-"example shows how to a implement an application that supports bookmarking "
-"throughout, even on the search results page. This example demonstrates how "
-"Seam can manage application state in the URL as well as how Seam can rewrite "
-"those URLs to be even"
+msgid "Seam makes it very easy to implement applications which keep state on the server-side. However, server-side state is not always appropriate, especially in for functionality that serves up <emphasis>content</emphasis>. For this kind of problem we often want to keep application state in the URL so that any page can be accessed at any time through a bookmark. The blog example shows how to a implement an application that supports bookmarking throughout, even on the search results page. This example demonstrates how Seam can manage application state in the URL as well as how Seam can rewrite those URLs to be even"
msgstr ""
#. Tag: screeninfo
@@ -4224,10 +4547,7 @@
#. Tag: para
#: Tutorial.xml:1744
#, no-c-format
-msgid ""
-"The Blog example demonstrates the use of \"pull\"-style MVC, where instead "
-"of using action listener methods to retrieve data and prepare the data for "
-"the view, the view pulls data from components as it is being rendered."
+msgid "The Blog example demonstrates the use of \"pull\"-style MVC, where instead of using action listener methods to retrieve data and prepare the data for the view, the view pulls data from components as it is being rendered."
msgstr ""
#. Tag: title
@@ -4239,27 +4559,22 @@
#. Tag: para
#: Tutorial.xml:1751
#, no-c-format
-msgid ""
-"This snippet from the <literal>index.xhtml</literal> facelets page displays "
-"a list of recent blog entries:"
+msgid "This snippet from the <literal>index.xhtml</literal> facelets page displays a list of recent blog entries:"
msgstr ""
#. Tag: programlisting
#: Tutorial.xml:1755
#, no-c-format
msgid ""
-"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" "
-"rows=\"3\">\n"
+"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" rows=\"3\">\n"
" <h:column>\n"
" <div class=\"blogEntry\">\n"
" <h3>#{blogEntry.title}</h3>\n"
" <div>\n"
-" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry."
-"body : blogEntry.excerpt}\"/>\n"
+" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry.body : blogEntry.excerpt}\"/>\n"
" </div>\n"
" <p>\n"
-" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}"
-"\" propagation=\"none\"\n"
+" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}\" propagation=\"none\"\n"
" value=\"Read more...\">\n"
" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
" </s:link>\n"
@@ -4267,12 +4582,10 @@
" <p>\n"
" [Posted on \n"
" <h:outputText value=\"#{blogEntry.date}\">\n"
-" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#"
-"{blog.locale}\" type=\"both\"/>\n"
+" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n"
" </h:outputText>]\n"
"  \n"
-" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]"
-"\">\n"
+" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]\">\n"
" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
" </s:link>\n"
" </p>\n"
@@ -4280,17 +4593,37 @@
" </h:column>\n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" rows=\"3\">\n"
+" <h:column>\n"
+" <div class=\"blogEntry\">\n"
+" <h3>#{blogEntry.title}</h3>\n"
+" <div>\n"
+" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry.body : blogEntry.excerpt}\"/>\n"
+" </div>\n"
+" <p>\n"
+" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}\" propagation=\"none\"\n"
+" value=\"Read more...\">\n"
+" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
+" </s:link>\n"
+" </p>\n"
+" <p>\n"
+" [Posted on \n"
+" <h:outputText value=\"#{blogEntry.date}\">\n"
+" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n"
+" </h:outputText>]\n"
+"  \n"
+" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"[Link]\">\n"
+" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
+" </s:link>\n"
+" </p>\n"
+" </div>\n"
+" </h:column>\n"
+"</h:dataTable>]]>"
#. Tag: para
#: Tutorial.xml:1759
#, no-c-format
-msgid ""
-"If we navigate to this page from a bookmark, how does the <literal>#{blog."
-"recentBlogEntries}</literal> data used by the <literal><h:dataTable></"
-"literal> actually get initialized? The <literal>Blog</literal> is retrieved "
-"lazily—\"pulled\"—when needed, by a Seam component named "
-"<literal>blog</literal>. This is the opposite flow of control to what is "
-"used in traditional action-based web frameworks like Struts."
+msgid "If we navigate to this page from a bookmark, how does the <literal>#{blog.recentBlogEntries}</literal> data used by the <literal><h:dataTable></literal> actually get initialized? The <literal>Blog</literal> is retrieved lazily—\"pulled\"—when needed, by a Seam component named <literal>blog</literal>. This is the opposite flow of control to what is used in traditional action-based web frameworks like Struts."
msgstr ""
#. Tag: programlisting
@@ -4308,42 +4641,47 @@
" @Unwrap\n"
" public Blog getBlog()\n"
" {\n"
-" return (Blog) entityManager.createQuery(\"select distinct b from Blog "
-"b left join fetch b.blogEntries\")\n"
+" return (Blog) entityManager.createQuery(\"select distinct b from Blog b left join fetch b.blogEntries\")\n"
" .setHint(\"org.hibernate.cacheable\", true)\n"
" .getSingleResult();\n"
" }\n"
"\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"blog\")\n"
+"@Scope(ScopeType.STATELESS)\n"
+"@AutoCreate\n"
+"public class BlogService \n"
+"{\n"
+" \n"
+" @In EntityManager entityManager;\n"
+" \n"
+" @Unwrap\n"
+" public Blog getBlog()\n"
+" {\n"
+" return (Blog) entityManager.createQuery(\"select distinct b from Blog b left join fetch b.blogEntries\")\n"
+" .setHint(\"org.hibernate.cacheable\", true)\n"
+" .getSingleResult();\n"
+" }\n"
+"\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:1775
#, no-c-format
-msgid ""
-"This component uses a <emphasis>seam-managed persistence context</emphasis>. "
-"Unlike the other examples we've seen, this persistence context is managed by "
-"Seam, instead of by the EJB3 container. The persistence context spans the "
-"entire web request, allowing us to avoid any exceptions that occur when "
-"accessing unfetched associations in the view."
+msgid "This component uses a <emphasis>seam-managed persistence context</emphasis>. Unlike the other examples we've seen, this persistence context is managed by Seam, instead of by the EJB3 container. The persistence context spans the entire web request, allowing us to avoid any exceptions that occur when accessing unfetched associations in the view."
msgstr ""
#. Tag: para
#: Tutorial.xml:1782
#, no-c-format
-msgid ""
-"The <literal>@Unwrap</literal> annotation tells Seam to provide the return "
-"value of the method—the <literal>Blog</literal>—instead of the "
-"actual <literal>BlogService</literal> component to clients. This is the Seam "
-"<emphasis>manager component pattern</emphasis>."
+msgid "The <literal>@Unwrap</literal> annotation tells Seam to provide the return value of the method—the <literal>Blog</literal>—instead of the actual <literal>BlogService</literal> component to clients. This is the Seam <emphasis>manager component pattern</emphasis>."
msgstr ""
#. Tag: para
#: Tutorial.xml:1792
#, no-c-format
-msgid ""
-"This is good so far, but what about bookmarking the result of form "
-"submissions, such as a search results page?"
+msgid "This is good so far, but what about bookmarking the result of form submissions, such as a search results page?"
msgstr ""
#. Tag: title
@@ -4355,11 +4693,7 @@
#. Tag: para
#: Tutorial.xml:1800
#, no-c-format
-msgid ""
-"The blog example has a tiny form in the top right of each page that allows "
-"the user to search for blog entries. This is defined in a file, "
-"<literal>menu.xhtml</literal>, included by the facelets template, "
-"<literal>template.xhtml</literal>:"
+msgid "The blog example has a tiny form in the top right of each page that allows the user to search for blog entries. This is defined in a file, <literal>menu.xhtml</literal>, included by the facelets template, <literal>template.xhtml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -4373,16 +4707,17 @@
" </h:form>\n"
"</div>]]>"
msgstr ""
+"<![CDATA[<div id=\"search\">\n"
+" <h:form>\n"
+" <h:inputText value=\"#{searchAction.searchPattern}\"/>\n"
+" <h:commandButton value=\"Search\" action=\"/search.xhtml\"/>\n"
+" </h:form>\n"
+"</div>]]>"
#. Tag: para
#: Tutorial.xml:1808
#, no-c-format
-msgid ""
-"To implement a bookmarkable search results page, we need to perform a "
-"browser redirect after processing the search form submission. Because we "
-"used the JSF view id as the action outcome, Seam automatically redirects to "
-"the view id when the form is submitted. Alternatively, we could have defined "
-"a navigation rule like this:"
+msgid "To implement a bookmarkable search results page, we need to perform a browser redirect after processing the search form submission. Because we used the JSF view id as the action outcome, Seam automatically redirects to the view id when the form is submitted. Alternatively, we could have defined a navigation rule like this:"
msgstr ""
#. Tag: programlisting
@@ -4397,6 +4732,13 @@
" </navigation-case>\n"
"</navigation-rule>]]>"
msgstr ""
+"<![CDATA[<navigation-rule>\n"
+" <navigation-case>\n"
+" <from-outcome>searchResults</from-outcome>\n"
+" <to-view-id>/search.xhtml</to-view-id>\n"
+" <redirect/>\n"
+" </navigation-case>\n"
+"</navigation-rule>]]>"
#. Tag: para
#: Tutorial.xml:1816
@@ -4415,17 +4757,17 @@
" </h:form>\n"
"</div>]]>"
msgstr ""
+"<![CDATA[<div id=\"search\">\n"
+" <h:form>\n"
+" <h:inputText value=\"#{searchAction.searchPattern}\"/>\n"
+" <h:commandButton value=\"Search\" action=\"searchResults\"/>\n"
+" </h:form>\n"
+"</div>]]>"
#. Tag: para
#: Tutorial.xml:1821
#, no-c-format
-msgid ""
-"But when we redirect, we need to include the values submitted with the form "
-"in the URL get a bookmarkable URL like <literal>http://localhost:8080/seam-"
-"blog/search/</literal>. JSF does not provide an easy way to do this, but "
-"Seam does. We use two Seam features to accomplish this: <emphasis>page "
-"parameters</emphasis> and <emphasis>URL rewriting</emphasis>. Both are "
-"defined in <literal>WEB-INF/pages.xml</literal>:"
+msgid "But when we redirect, we need to include the values submitted with the form in the URL get a bookmarkable URL like <literal>http://localhost:8080/seam-blog/search/</literal>. JSF does not provide an easy way to do this, but Seam does. We use two Seam features to accomplish this: <emphasis>page parameters</emphasis> and <emphasis>URL rewriting</emphasis>. Both are defined in <literal>WEB-INF/pages.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -4437,52 +4779,39 @@
" <rewrite pattern=\"/search/{searchPattern}\"/> \n"
" <rewrite pattern=\"/search\"/>\n"
" \n"
-" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/"
-">\n"
+" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/>\n"
"\n"
" </page>\n"
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" <page view-id=\"/search.xhtml\">\n"
+" <rewrite pattern=\"/search/{searchPattern}\"/> \n"
+" <rewrite pattern=\"/search\"/>\n"
+" \n"
+" <param name=\"searchPattern\" value=\"#{searchService.searchPattern}\"/>\n"
+"\n"
+" </page>\n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Tutorial.xml:1833
#, no-c-format
-msgid ""
-"The page parameter instructs Seam to link the request parameter named "
-"<literal>searchPattern</literal> to the value of <literal>#{searchService."
-"searchPattern}</literal>, both whenever a request for the Search page comes "
-"in and whenever a link to the search page is generated. Seam takes "
-"responsibility for maintaining the link between URL state and application "
-"state, and you, the developer, don't have to worry about it."
+msgid "The page parameter instructs Seam to link the request parameter named <literal>searchPattern</literal> to the value of <literal>#{searchService.searchPattern}</literal>, both whenever a request for the Search page comes in and whenever a link to the search page is generated. Seam takes responsibility for maintaining the link between URL state and application state, and you, the developer, don't have to worry about it."
msgstr ""
#. Tag: para
#: Tutorial.xml:1840
#, no-c-format
-msgid ""
-"Without URL rewriting, the URL for a search on the term <literal>book</"
-"literal> would be <literal>http://localhost:8080/seam-blog/seam/search.xhtml?"
-"searchPattern=book</literal>. This is nice, but Seam can make the URL even "
-"simpler using a rewrite rule. The first rewrite rule, for the pattern "
-"<literal>/search/{searchPattern}</literal>, says that any time we have have "
-"a URL for search.xhtml with a searchPattern request parameter, we can fold "
-"that URL into the simpler URL. So,the URL we saw earlier, <literal>http://"
-"localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal> can "
-"be written instead as <literal>http://localhost:8080/seam-blog/search/book</"
-"literal>."
+msgid "Without URL rewriting, the URL for a search on the term <literal>book</literal> would be <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal>. This is nice, but Seam can make the URL even simpler using a rewrite rule. The first rewrite rule, for the pattern <literal>/search/{searchPattern}</literal>, says that any time we have have a URL for search.xhtml with a searchPattern request parameter, we can fold that URL into the simpler URL. So,the URL we saw earlier, <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal> can be written instead as <literal>http://localhost:8080/seam-blog/search/book</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:1850
#, no-c-format
-msgid ""
-"Just like with page parameters, URL rewriting is bi-directional. That means "
-"that Seam forwards requests for the simpler URL to the the right view, and "
-"it also automatically generates the simpler view for you. You never need to "
-"worry about constructing URLs. It's all handled transparently behind the "
-"scenes. The only requirement is that to use URL rewriting, the rewrite "
-"filter needs to be enabled in <literal>components.xml</literal>."
+msgid "Just like with page parameters, URL rewriting is bi-directional. That means that Seam forwards requests for the simpler URL to the the right view, and it also automatically generates the simpler view for you. You never need to worry about constructing URLs. It's all handled transparently behind the scenes. The only requirement is that to use URL rewriting, the rewrite filter needs to be enabled in <literal>components.xml</literal>."
msgstr ""
#. Tag: programlisting
@@ -4504,26 +4833,35 @@
"<![CDATA[<h:dataTable value=\"#{searchResults}\" var=\"blogEntry\">\n"
" <h:column>\n"
" <div>\n"
-" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#"
-"{blogEntry.title}\">\n"
+" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#{blogEntry.title}\">\n"
" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
" </s:link>\n"
" posted on \n"
" <h:outputText value=\"#{blogEntry.date}\">\n"
-" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog."
-"locale}\" type=\"both\"/>\n"
+" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n"
" </h:outputText>\n"
" </div>\n"
" </h:column>\n"
"</h:dataTable>]]>"
msgstr ""
+"<![CDATA[<h:dataTable value=\"#{searchResults}\" var=\"blogEntry\">\n"
+" <h:column>\n"
+" <div>\n"
+" <s:link view=\"/entry.xhtml\" propagation=\"none\" value=\"#{blogEntry.title}\">\n"
+" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
+" </s:link>\n"
+" posted on \n"
+" <h:outputText value=\"#{blogEntry.date}\">\n"
+" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n"
+" </h:outputText>\n"
+" </div>\n"
+" </h:column>\n"
+"</h:dataTable>]]>"
#. Tag: para
#: Tutorial.xml:1865
#, no-c-format
-msgid ""
-"Which again uses \"pull\"-style MVC to retrieve the actual search results "
-"using Hibernate Search."
+msgid "Which again uses \"pull\"-style MVC to retrieve the actual search results using Hibernate Search."
msgstr ""
#. Tag: programlisting
@@ -4544,8 +4882,7 @@
" {\n"
" if (searchPattern==null || \"\".equals(searchPattern) ) {\n"
" searchPattern = null;\n"
-" return entityManager.createQuery(\"select be from BlogEntry be "
-"order by date desc\").getResultList();\n"
+" return entityManager.createQuery(\"select be from BlogEntry be order by date desc\").getResultList();\n"
" }\n"
" else\n"
" {\n"
@@ -4553,8 +4890,7 @@
" boostPerField.put( \"title\", 4f );\n"
" boostPerField.put( \"body\", 1f );\n"
" String[] productFields = {\"title\", \"body\"};\n"
-" QueryParser parser = new MultiFieldQueryParser(productFields, new "
-"StandardAnalyzer(), boostPerField);\n"
+" QueryParser parser = new MultiFieldQueryParser(productFields, new StandardAnalyzer(), boostPerField);\n"
" parser.setAllowLeadingWildcard(true);\n"
" org.apache.lucene.search.Query luceneQuery;\n"
" try\n"
@@ -4566,8 +4902,7 @@
" return null;\n"
" }\n"
"\n"
-" return entityManager.createFullTextQuery(luceneQuery, BlogEntry."
-"class)\n"
+" return entityManager.createFullTextQuery(luceneQuery, BlogEntry.class)\n"
" .setMaxResults(100)\n"
" .getResultList();\n"
" }\n"
@@ -4586,6 +4921,58 @@
"}\n"
"]]>"
msgstr ""
+"<![CDATA[@Name(\"searchService\")\n"
+"public class SearchService \n"
+"{\n"
+" \n"
+" @In\n"
+" private FullTextEntityManager entityManager;\n"
+" \n"
+" private String searchPattern;\n"
+" \n"
+" @Factory(\"searchResults\")\n"
+" public List<BlogEntry> getSearchResults()\n"
+" {\n"
+" if (searchPattern==null || \"\".equals(searchPattern) ) {\n"
+" searchPattern = null;\n"
+" return entityManager.createQuery(\"select be from BlogEntry be order by date desc\").getResultList();\n"
+" }\n"
+" else\n"
+" {\n"
+" Map<String,Float> boostPerField = new HashMap<String,Float>();\n"
+" boostPerField.put( \"title\", 4f );\n"
+" boostPerField.put( \"body\", 1f );\n"
+" String[] productFields = {\"title\", \"body\"};\n"
+" QueryParser parser = new MultiFieldQueryParser(productFields, new StandardAnalyzer(), boostPerField);\n"
+" parser.setAllowLeadingWildcard(true);\n"
+" org.apache.lucene.search.Query luceneQuery;\n"
+" try\n"
+" {\n"
+" luceneQuery = parser.parse(searchPattern);\n"
+" }\n"
+" catch (ParseException e)\n"
+" {\n"
+" return null;\n"
+" }\n"
+"\n"
+" return entityManager.createFullTextQuery(luceneQuery, BlogEntry.class)\n"
+" .setMaxResults(100)\n"
+" .getResultList();\n"
+" }\n"
+" }\n"
+"\n"
+" public String getSearchPattern()\n"
+" {\n"
+" return searchPattern;\n"
+" }\n"
+"\n"
+" public void setSearchPattern(String searchPattern)\n"
+" {\n"
+" this.searchPattern = searchPattern;\n"
+" }\n"
+"\n"
+"}\n"
+"]]>"
#. Tag: title
#: Tutorial.xml:1874
@@ -4596,20 +4983,13 @@
#. Tag: para
#: Tutorial.xml:1876
#, no-c-format
-msgid ""
-"Very occasionally, it makes more sense to use push-style MVC for processing "
-"RESTful pages, and so Seam provides the notion of a <emphasis>page action</"
-"emphasis>. The Blog example uses a page action for the blog entry page, "
-"<literal>entry.xhtml</literal>. Note that this is a little bit contrived, it "
-"would have been easier to use pull-style MVC here as well."
+msgid "Very occasionally, it makes more sense to use push-style MVC for processing RESTful pages, and so Seam provides the notion of a <emphasis>page action</emphasis>. The Blog example uses a page action for the blog entry page, <literal>entry.xhtml</literal>. Note that this is a little bit contrived, it would have been easier to use pull-style MVC here as well."
msgstr ""
#. Tag: para
#: Tutorial.xml:1881
#, no-c-format
-msgid ""
-"The <literal>entryAction</literal> component works much like an action class "
-"in a traditional push-MVC action-oriented framework like Struts:"
+msgid "The <literal>entryAction</literal> component works much like an action class in a traditional push-MVC action-oriented framework like Struts:"
msgstr ""
#. Tag: programlisting
@@ -4632,6 +5012,21 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"entryAction\")\n"
+"@Scope(STATELESS)\n"
+"public class EntryAction\n"
+"{\n"
+" @In Blog blog;\n"
+" \n"
+" @Out BlogEntry blogEntry;\n"
+" \n"
+" public void loadBlogEntry(String id) throws EntryNotFoundException\n"
+" {\n"
+" blogEntry = blog.getBlogEntry(id);\n"
+" if (blogEntry==null) throw new EntryNotFoundException(id);\n"
+" }\n"
+" \n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:1887
@@ -4676,27 +5071,49 @@
"\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" ...\n"
+"\n"
+" <page view-id=\"/entry.xhtml\"> \n"
+" <rewrite pattern=\"/entry/{blogEntryId}\" />\n"
+" <rewrite pattern=\"/entry\" />\n"
+" \n"
+" <param name=\"blogEntryId\" \n"
+" value=\"#{blogEntry.id}\"/>\n"
+" \n"
+" <action execute=\"#{entryAction.loadBlogEntry(blogEntry.id)}\"/>\n"
+" </page>\n"
+" \n"
+" <page view-id=\"/post.xhtml\" login-required=\"true\">\n"
+" <rewrite pattern=\"/post\" />\n"
+" \n"
+" <action execute=\"#{postAction.post}\"\n"
+" if=\"#{validation.succeeded}\"/>\n"
+" \n"
+" <action execute=\"#{postAction.invalid}\"\n"
+" if=\"#{validation.failed}\"/>\n"
+" \n"
+" <navigation from-action=\"#{postAction.post}\">\n"
+" <redirect view-id=\"/index.xhtml\"/>\n"
+" </navigation>\n"
+" </page>\n"
+"\n"
+" <page view-id=\"*\">\n"
+" <action execute=\"#{blog.hitCount.hit}\"/>\n"
+" </page>\n"
+"\n"
+"</pages>]]>"
#. Tag: para
#: Tutorial.xml:1892
#, no-c-format
-msgid ""
-"Notice that the example is using page actions for post validation and the "
-"pageview counter. Also notice the use of a parameter in the page action "
-"method binding. This is not a standard feature of JSF EL, but Seam lets you "
-"use it, not just for page actions but also in JSF method bindings."
+msgid "Notice that the example is using page actions for post validation and the pageview counter. Also notice the use of a parameter in the page action method binding. This is not a standard feature of JSF EL, but Seam lets you use it, not just for page actions but also in JSF method bindings."
msgstr ""
#. Tag: para
#: Tutorial.xml:1897
#, no-c-format
-msgid ""
-"When the <literal>entry.xhtml</literal> page is requested, Seam first binds "
-"the page parameter <literal>blogEntryId</literal> to the model. Keep in mind "
-"that because of the URL rewriting, the blogEntryId parameter name won't show "
-"up in the URL. Seam then runs the page action, which retrieves the needed "
-"data—the <literal>blogEntry</literal>—and places it in the Seam "
-"event context. Finally, the following is rendered:"
+msgid "When the <literal>entry.xhtml</literal> page is requested, Seam first binds the page parameter <literal>blogEntryId</literal> to the model. Keep in mind that because of the URL rewriting, the blogEntryId parameter name won't show up in the URL. Seam then runs the page action, which retrieves the needed data—the <literal>blogEntry</literal>—and places it in the Seam event context. Finally, the following is rendered:"
msgstr ""
#. Tag: programlisting
@@ -4711,21 +5128,28 @@
" <p>\n"
" [Posted on \n"
" <h:outputText value=\"#{blogEntry.date}\">\n"
-" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog."
-"locale}\" type=\"both\"/>\n"
+" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n"
" </h:outputText>]\n"
" </p>\n"
"</div>]]>"
msgstr ""
+"<![CDATA[<div class=\"blogEntry\">\n"
+" <h3>#{blogEntry.title}</h3>\n"
+" <div>\n"
+" <s:formattedText value=\"#{blogEntry.body}\"/>\n"
+" </div>\n"
+" <p>\n"
+" [Posted on \n"
+" <h:outputText value=\"#{blogEntry.date}\">\n"
+" <f:convertDateTime timeZone=\"#{blog.timeZone}\" locale=\"#{blog.locale}\" type=\"both\"/>\n"
+" </h:outputText>]\n"
+" </p>\n"
+"</div>]]>"
#. Tag: para
#: Tutorial.xml:1907
#, no-c-format
-msgid ""
-"If the blog entry is not found in the database, the "
-"<literal>EntryNotFoundException</literal> exception is thrown. We want this "
-"exception to result in a 404 error, not a 505, so we annotate the exception "
-"class:"
+msgid "If the blog entry is not found in the database, the <literal>EntryNotFoundException</literal> exception is thrown. We want this exception to result in a 404 error, not a 505, so we annotate the exception class:"
msgstr ""
#. Tag: programlisting
@@ -4742,13 +5166,20 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@ApplicationException(rollback=true)\n"
+"@HttpError(errorCode=HttpServletResponse.SC_NOT_FOUND)\n"
+"public class EntryNotFoundException extends Exception\n"
+"{\n"
+" EntryNotFoundException(String id)\n"
+" {\n"
+" super(\"entry not found: \" + id);\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Tutorial.xml:1914
#, no-c-format
-msgid ""
-"An alternative implementation of the example does not use the parameter in "
-"the method binding:"
+msgid "An alternative implementation of the example does not use the parameter in the method binding:"
msgstr ""
#. Tag: programlisting
@@ -4772,6 +5203,22 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"entryAction\")\n"
+"@Scope(STATELESS)\n"
+"public class EntryAction\n"
+"{\n"
+" @In(create=true) \n"
+" private Blog blog;\n"
+" \n"
+" @In @Out\n"
+" private BlogEntry blogEntry;\n"
+" \n"
+" public void loadBlogEntry() throws EntryNotFoundException\n"
+" {\n"
+" blogEntry = blog.getBlogEntry( blogEntry.getId() );\n"
+" if (blogEntry==null) throw new EntryNotFoundException(id);\n"
+" }\n"
+"}]]>"
#. Tag: programlisting
#: Tutorial.xml:1918
@@ -4787,17 +5234,25 @@
" ...\n"
"</pages>]]>"
msgstr ""
+"<![CDATA[<pages>\n"
+" ...\n"
+"\n"
+" <page view-id=\"/entry.xhtml\" action=\"#{entryAction.loadBlogEntry}\">\n"
+" <param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
+" </page>\n"
+" \n"
+" ...\n"
+"</pages>]]>"
#. Tag: para
#: Tutorial.xml:1921
#, no-c-format
msgid "It is a matter of taste which implementation you prefer."
-msgstr ""
+msgstr "E' una questione di gusti su quale implementazione tu preferisca."
#. Tag: para
#: Tutorial.xml:1924
#, no-c-format
-msgid ""
-"The blog demo also demonstrates very simple password authentication, posting "
-"to the blog, page fragment caching and atom feed generation."
+msgid "The blog demo also demonstrates very simple password authentication, posting to the blog, page fragment caching and atom feed generation."
msgstr ""
+
More information about the seam-commits
mailing list