Seam SVN: r9781 - trunk/examples/seamspace/resources/WEB-INF.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-15 10:46:20 -0500 (Mon, 15 Dec 2008)
New Revision: 9781
Modified:
trunk/examples/seamspace/resources/WEB-INF/pages.xml
Log:
JBSEAM-3843
Modified: trunk/examples/seamspace/resources/WEB-INF/pages.xml
===================================================================
--- trunk/examples/seamspace/resources/WEB-INF/pages.xml 2008-12-15 15:39:19 UTC (rev 9780)
+++ trunk/examples/seamspace/resources/WEB-INF/pages.xml 2008-12-15 15:46:20 UTC (rev 9781)
@@ -124,7 +124,7 @@
</navigation>
</page>
- <exception class="org.jboss.seam.security.NotLoggedInException" log="true" logLevel="info">
+ <exception class="org.jboss.seam.security.NotLoggedInException" log="true" log-level="info">
<redirect view-id="/register.xhtml">
<message severity="warn">You must be a member to use this feature</message>
</redirect>
16 years
- 1
- 0
Seam SVN: r9780 - tags/JBoss_Seam_2_1_1_GA/examples/seamspace/resources/WEB-INF.
by seam-commits＠lists.jboss.org
Author: norman.richards(a)jboss.com
Date: 2008-12-15 10:39:19 -0500 (Mon, 15 Dec 2008)
New Revision: 9780
Modified:
tags/JBoss_Seam_2_1_1_GA/examples/seamspace/resources/WEB-INF/pages.xml
Log:
JBSEAM-3843
Modified: tags/JBoss_Seam_2_1_1_GA/examples/seamspace/resources/WEB-INF/pages.xml
===================================================================
--- tags/JBoss_Seam_2_1_1_GA/examples/seamspace/resources/WEB-INF/pages.xml 2008-12-15 05:59:33 UTC (rev 9779)
+++ tags/JBoss_Seam_2_1_1_GA/examples/seamspace/resources/WEB-INF/pages.xml 2008-12-15 15:39:19 UTC (rev 9780)
@@ -124,7 +124,7 @@
</navigation>
</page>
- <exception class="org.jboss.seam.security.NotLoggedInException" log="true" logLevel="info">
+ <exception class="org.jboss.seam.security.NotLoggedInException" log="true" log-level="info">
<redirect view-id="/register.xhtml">
<message severity="warn">You must be a member to use this feature</message>
</redirect>
16 years
- 1
- 0
Seam SVN: r9779 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-15 00:59:33 -0500 (Mon, 15 Dec 2008)
New Revision: 9779
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-15 05:48:01 UTC (rev 9778)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-15 05:59:33 UTC (rev 9779)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-13 23:54+0100\n"
+"PO-Revision-Date: 2008-12-15 06:59+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,7 +23,7 @@
#: Elenhancements.xml:7
#, no-c-format
msgid "Seam uses JBoss EL which provides an extension to the standard Unified Expression Language (EL). JBoss EL provides a number of enhancements that increase the expressiveness and power of EL expressions."
-msgstr "Seam utilizza JBoss EL, il quale fornisce un'estensione allo standard Unified Expression Language (EL). JBoss EL apporta un numero di miglioramenti che incrementa l'espressività e la potenza delle espressioni EL. "
+msgstr "Seam utilizza JBoss EL, il quale fornisce un'estensione allo standard Unified Expression Language (EL). JBoss EL apporta un numero di miglioramenti che incrementano l'espressività e la potenza delle espressioni EL. "
#. Tag: title
#: Elenhancements.xml:14
16 years
- 1
- 0
Seam SVN: r9778 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-15 00:48:01 -0500 (Mon, 15 Dec 2008)
New Revision: 9778
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-14 23:21:33 UTC (rev 9777)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-15 05:48:01 UTC (rev 9778)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-14 22:11+0100\n"
+"PO-Revision-Date: 2008-12-15 06:47+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -29,31 +29,31 @@
#: Jbpm.xml:16
#, no-c-format
msgid "Seam applications use jBPM for two different problems:"
-msgstr ""
+msgstr "Le applicazioni Seam utilizzano jBPM per due tipi di problemi:"
#. 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."
-msgstr ""
+msgstr "Complesse interazioni da parte dell'utente comportano la definizione un pageflow (flusso di pagina). Una definizione di un processo con jPDL stabilisce il flusso delle pagine per una singola conversazione. Una conversazione in Seam è considerata un'interazione di breve durata con un singolo utente."
#. 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."
-msgstr ""
+msgstr "Definizione del processo di business sottostante. Il processo di business può comportare una serie di conversazioni con più utenti. Il suo stato viene persistito nel database jBPM, divenendo così di lunga durata. Il coordinamento delle attività di più utenti è un problema molto più complesso che descrivere l'interazione di un singolo utente, cosicché jBPM offre dei modi sofisticati per la gestione dei compiti (task) e per la gestione di più percorsi concorrenti di esecuzione ."
#. 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."
-msgstr ""
+msgstr "Non confondere le due cose! Queste operano a livelli molto diversi e con diverso grado di granularità. <emphasis>Pageflow</emphasis>, <emphasis>conversazione</emphasis> e <emphasis>task</emphasis> si riferiscono tutti alla singola interazione con il singolo utente. Un processo di business comporta più task. Quindi le due applicazione di jBPM sono totalmente ortogonali. Puoi usarle assieme, in modo indipendente, o puoi non usarle affatto."
#. 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."
-msgstr ""
+msgstr "Non serve che tu conosca jPDL per usare Seam. Se ti trovi bene nel definire un pageflow con JSF o con le regole di navigazione di Seam, e se l'applicazione è guida più dai dati che dal processo, probabilmente non ti serve usare jBPM. Ma noi pensiamo che strutturare l'interazione dell'utente in termini di rappresentazione grafical ben definita aiuti a costruire applicazioni più robuste."
#. Tag: title
#: Jbpm.xml:60
@@ -65,7 +65,7 @@
#: Jbpm.xml:61
#, no-c-format
msgid "There are two ways to define pageflow in Seam:"
-msgstr ""
+msgstr "Ci sono due modi per definire il pageflow in Seam:"
#. Tag: para
#: Jbpm.xml:67
@@ -77,13 +77,13 @@
#: Jbpm.xml:73
#, no-c-format
msgid "Using jPDL - the <emphasis>stateful navigation model</emphasis>"
-msgstr ""
+msgstr "Utilizzo di jPDL - il <emphasis>modello di navigazione stateful</emphasis>"
#. 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!"
-msgstr ""
+msgstr "Applicazioni molto semplici richiedono soltanto un modello di navigazione stateless. Invece applicazioni molto complesse impiegano entrambi i modelli in differenti punti. Ciascun modello ha i suoi punti di forza e le sue debolezze!"
#. Tag: title
#: Jbpm.xml:86
@@ -91,17 +91,18 @@
msgid "The two navigation models"
msgstr "I due modelli di navigazione"
+# rivedere la frase
#. 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."
-msgstr ""
+msgstr "Il modello stateless definisce una mappatura tra un set di esiti di un evento e la pagina della vista. Le regole di navigazione sono interamente senza memoria rispetto alla stato mantenuto dall'applicazione oltre che alla pagina origine dell'evento. Questo significa che i metodi dell'action listener devono di tanto in tanto prendere decisioni sul pageflow, poiché solo loro hanno accesso allo stato corrente dell'applicazione."
#. Tag: para
#: Jbpm.xml:98
#, no-c-format
msgid "Here is an example page flow definition using JSF navigation rules:"
-msgstr ""
+msgstr "Ecco ora un esempio di definizione di pageflow usando le regole di navigazione JSF:"
#. Tag: programlisting
#: Jbpm.xml:103
@@ -157,7 +158,7 @@
#: Jbpm.xml:105
#, no-c-format
msgid "Here is the same example page flow definition using Seam navigation rules:"
-msgstr ""
+msgstr "Ecco lo stesso esempio di definizione di pageflow usando le regole di navigazione di Seam:"
#. Tag: programlisting
#: Jbpm.xml:110
@@ -199,7 +200,7 @@
#: 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:"
-msgstr ""
+msgstr "Se ritieni che le regole di navigazione siano troppo lunghe, puoi restituire l'id della vista direttamente dai metodi dell'action listener:"
#. Tag: programlisting
#: Jbpm.xml:117
@@ -221,7 +222,7 @@
#: 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:"
-msgstr ""
+msgstr "Si noti che questo comporta un redirect. Puoi persino specificare i parametri da usare nel redirect:"
#. Tag: programlisting
#: Jbpm.xml:124
@@ -235,17 +236,18 @@
" return \"/searchResults.jsp?searchPattern=#{searchAction.searchPattern}\";\n"
"}]]>"
+# rivedere la frase.
#. 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."
-msgstr ""
+msgstr "Il modello stateful definisce un set di transizioni tra gli stati dell'applicazione. In questo modello è possibile esprimere il flusso di qualsiasi interazione utente interamente nella definizione jPDL di pageflow, e scrivere i metodi action listener completamente slegati dal flusso dell'interazione."
#. Tag: para
#: Jbpm.xml:134
#, no-c-format
msgid "Here is an example page flow definition using jPDL:"
-msgstr ""
+msgstr "Ecco ora un esempio di definizione di pageflow usando jPDL:"
#. Tag: programlisting
#: Jbpm.xml:138
@@ -317,25 +319,25 @@
#: Jbpm.xml:149
#, no-c-format
msgid "There are two things we notice immediately here:"
-msgstr ""
+msgstr "Ci sono due cose da notare immediatamente:"
#. 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.)"
-msgstr ""
+msgstr "Le regole di navigazione JSF/Seam sono <emphasis>molto</emphasis> più semplici. (Comunque questo nasconde il fatto che il codice Java sottostante è molto complesso.)"
#. 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."
-msgstr ""
+msgstr "jPDL rende l'interazione utente immediatamente comprensibile senza dover guardare il codice JSP o Java."
#. 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."
-msgstr ""
+msgstr "In aggiunta il modello stateful è più <emphasis>vincolato</emphasis>. Per ogni stato logico (ogni passo del pageflow) c'è un set vincolato di possibili transizioni verso altri stati. Il modello stateless è un modello <emphasis>ad hoc</emphasis> adatto ad una navigazione libera e senza vincoli in cui l'utente decide dove andare, non l'applicazione."
#. Tag: para
#: Jbpm.xml:178
@@ -347,13 +349,13 @@
#: Jbpm.xml:191
#, no-c-format
msgid "The biggest contrast between the two models is the back-button behavior."
-msgstr ""
+msgstr "Il maggior contrasto fra i due modelli è nel comportamento col pulsante indietro."
#. Tag: title
#: Jbpm.xml:199
#, no-c-format
msgid "Seam and the back button"
-msgstr ""
+msgstr "Seam ed il pulsante indietro"
#. Tag: para
#: Jbpm.xml:201
@@ -441,19 +443,19 @@
#: 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."
-msgstr ""
+msgstr "In pratica entrambi i modelli di navigazione hanno la loro utilità ed imparerai presto a riconoscere quando impiegare uno o l'altro."
#. Tag: title
#: Jbpm.xml:273
#, no-c-format
msgid "Using jPDL pageflows"
-msgstr ""
+msgstr "Utilizzo dei pageflow jPDL"
#. Tag: title
#: Jbpm.xml:276
#, no-c-format
msgid "Installing pageflows"
-msgstr ""
+msgstr "Installazione dei pageflow"
#. Tag: para
#: Jbpm.xml:278
@@ -493,7 +495,7 @@
#: Jbpm.xml:297
#, no-c-format
msgid "Starting pageflows"
-msgstr ""
+msgstr "Avvio dei pageflow"
#. Tag: para
#: Jbpm.xml:299
@@ -589,7 +591,7 @@
#: Jbpm.xml:333
#, no-c-format
msgid "Page nodes and transitions"
-msgstr ""
+msgstr "Nodi e transizioni di pagina"
#. Tag: para
#: Jbpm.xml:335
@@ -651,11 +653,12 @@
msgid "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\"/>]]>"
msgstr "<![CDATA[<h:commandButton type=\"submit\" value=\"Guess\"/>]]>"
+# vedere la frase nel contesto
#. Tag: para
#: Jbpm.xml:378
#, no-c-format
msgid "Would fire the following un-named transition:"
-msgstr ""
+msgstr "Esegue la seguente transizione senza nome:"
#. Tag: programlisting
#: Jbpm.xml:382
@@ -711,7 +714,7 @@
#: Jbpm.xml:402
#, no-c-format
msgid "Controlling the flow"
-msgstr ""
+msgstr "Controllo del flusso"
#. Tag: para
#: Jbpm.xml:404
@@ -743,7 +746,7 @@
#: Jbpm.xml:418
#, no-c-format
msgid "Ending the flow"
-msgstr ""
+msgstr "Fine del flusso"
#. Tag: para
#: Jbpm.xml:420
@@ -821,7 +824,7 @@
#: Jbpm.xml:462
#, no-c-format
msgid "Business process management in Seam"
-msgstr ""
+msgstr "La gestione del processo di business in Seam"
#. Tag: para
#: Jbpm.xml:463
@@ -883,7 +886,7 @@
#: Jbpm.xml:507
#, no-c-format
msgid "Using jPDL business process definitions"
-msgstr ""
+msgstr "Uso di jPDL nella definizione del processo di business"
#. Tag: title
#: Jbpm.xml:510
@@ -895,7 +898,7 @@
#: Jbpm.xml:512
#, no-c-format
msgid "We need to install jBPM, and tell it where to find the business process definitions:"
-msgstr ""
+msgstr "Occorre installare jBPM ed indicare dove si trovano le definizioni dei processi di business:"
#. Tag: programlisting
#: Jbpm.xml:517
@@ -923,7 +926,7 @@
#: Jbpm.xml:532
#, no-c-format
msgid "Initializing actor ids"
-msgstr ""
+msgstr "Inizializzazione degli actor id"
#. Tag: para
#: Jbpm.xml:534
@@ -957,7 +960,7 @@
#: Jbpm.xml:547
#, no-c-format
msgid "Initiating a business process"
-msgstr ""
+msgstr "Iniziare un processo di business"
#. Tag: para
#: Jbpm.xml:549
@@ -1169,13 +1172,13 @@
#: 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."
-msgstr ""
+msgstr "Queste annotazioni iniziano uno speciale tipo di conversazione che ha significato in termini di processo di business. Il lavoro fatto da questa conversazione ha accesso allo stato mantenuto nel contesto di business process. "
#. 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:"
-msgstr ""
+msgstr "Se terminiamo un conversazione usando <literal>@EndTask</literal>, Seam segnalerà il completamento del task:"
#. Tag: programlisting
#: Jbpm.xml:640
@@ -1191,7 +1194,7 @@
#: Jbpm.xml:642
#, no-c-format
msgid "Alternatively we can use pages.xml:"
-msgstr ""
+msgstr "In alternativa usiamo pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:644
@@ -1209,17 +1212,17 @@
#: Jbpm.xml:646
#, no-c-format
msgid "You can also use EL to specify the transition in pages.xml."
-msgstr ""
+msgstr "Puoi anche usare EL per specificare la transizione in pages.xml."
#. 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.)"
-msgstr ""
+msgstr "A questo punto jBPM assume il controllo e continua l'esecuzione della definizione del processo di business. (In processi più complessi, parecchi task potrebbero aver bisogno di essere completati prima che l'esecuzione del processo possa riprendere.)"
#. 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."
-msgstr ""
+msgstr "Fare riferimento alla documentazione jBPM per una panoramica delle funzionalità che jBPM fornisce per la gestione di processi complessi di business."
16 years
- 1
- 0
Seam SVN: r9777 - trunk/seam-gen/resources/WEB-INF.
by seam-commits＠lists.jboss.org
Author: shane.bryzak(a)jboss.com
Date: 2008-12-14 18:21:33 -0500 (Sun, 14 Dec 2008)
New Revision: 9777
Modified:
trunk/seam-gen/resources/WEB-INF/pages.xml
Log:
Change attribute name to log-level
Modified: trunk/seam-gen/resources/WEB-INF/pages.xml
===================================================================
--- trunk/seam-gen/resources/WEB-INF/pages.xml 2008-12-14 21:16:33 UTC (rev 9776)
+++ trunk/seam-gen/resources/WEB-INF/pages.xml 2008-12-14 23:21:33 UTC (rev 9777)
@@ -57,7 +57,7 @@
</redirect>
</exception>
- <exception class="org.jboss.seam.ConcurrentRequestTimeoutException" logLevel="trace">
+ <exception class="org.jboss.seam.ConcurrentRequestTimeoutException" log-level="trace">
<http-error error-code="503" />
</exception>
16 years
- 1
- 0
Seam SVN: r9776 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-14 16:16:33 -0500 (Sun, 14 Dec 2008)
New Revision: 9776
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.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/Testing.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/Gettingstarted.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Gettingstarted.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-11-06 00:23+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-14 19:09+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,85 +17,54 @@
#: Gettingstarted.xml:5
#, no-c-format
msgid "Getting started with Seam, using seam-gen"
-msgstr ""
+msgstr "Iniziare con Seam usando seam-gen"
#. Tag: para
#: Gettingstarted.xml:7
#, no-c-format
-msgid ""
-"The Seam distribution includes a command line utility that makes it really "
-"easy to set up an Eclipse project, generate some simple Seam skeleton code, "
-"and reverse engineer an application from a preexisting database."
+msgid "The Seam distribution includes a command line utility that makes it really easy to set up an Eclipse project, generate some simple Seam skeleton code, and reverse engineer an application from a preexisting database."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:10
#, no-c-format
-msgid ""
-"This is the easy way to get your feet wet with Seam, and gives you some "
-"ammunition for next time you find yourself trapped in an elevator with one "
-"of those tedious Ruby guys ranting about how great and wonderful his new toy "
-"is for building totally trivial applications that put things in databases."
-msgstr ""
+msgid "This is the easy way to get your feet wet with Seam, and gives you some ammunition for next time you find yourself trapped in an elevator with one of those tedious Ruby guys ranting about how great and wonderful his new toy is for building totally trivial applications that put things in databases."
+msgstr "Questo è il modo più semplice di sporcarti le mani con Seam e di preparare il colpo in canna per la prossima volta che ti troverai intrappolato in ascensore con uno di quei noiosi tipi di Ruby-on-Rail che farneticano quanto magnifico e meraviglioso sia l'ultimo giochino che hanno scoperto per realizzare applicazioni completamente banali che schiaffano delle cose nel database."
#. Tag: para
#: Gettingstarted.xml:14
#, no-c-format
-msgid ""
-"In this release, seam-gen works best for people with JBoss AS. You can use "
-"the generated project with other J2EE or Java EE 5 application servers by "
-"making a few manual changes to the project configuration."
+msgid "In this release, seam-gen works best for people with JBoss AS. You can use the generated project with other J2EE or Java EE 5 application servers by making a few manual changes to the project configuration."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:17
#, no-c-format
-msgid ""
-"You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this "
-"tutorial, we want to show you how to use it in conjunction with Eclipse for "
-"debugging and integration testing. If you don't want to install Eclipse, you "
-"can still follow along with this tutorial—all steps can be performed from "
-"the command line."
+msgid "You <emphasis>can</emphasis> use seam-gen without Eclipse, but in this tutorial, we want to show you how to use it in conjunction with Eclipse for debugging and integration testing. If you don't want to install Eclipse, you can still follow along with this tutorial—all steps can be performed from the command line."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:21
#, no-c-format
-msgid ""
-"Seam-gen is basically just a big ugly Ant script wrapped around Hibernate "
-"Tools, together with some templates. That makes it easy to customize if you "
-"need to."
+msgid "Seam-gen is basically just a big ugly Ant script wrapped around Hibernate Tools, together with some templates. That makes it easy to customize if you need to."
msgstr ""
#. Tag: title
#: Gettingstarted.xml:25
#, no-c-format
msgid "Before you start"
-msgstr ""
+msgstr "Prima di iniziare"
#. Tag: para
#: Gettingstarted.xml:27
#, no-c-format
-msgid ""
-"Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> "
-"for details), JBoss AS 4.2 and Ant 1.6, along with recent versions of "
-"Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse "
-"correctly installed before starting. Add your JBoss installation to the "
-"JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a "
-"command prompt in the directory where you unzipped the Seam distribution."
+msgid "Make sure you have JDK 5 or JDK 6 (see <xref linkend=\"jdk_dependencies\"/> for details), JBoss AS 4.2 and Ant 1.6, along with recent versions of Eclipse, the JBoss IDE plugin for Eclipse and the TestNG plugin for Eclipse correctly installed before starting. Add your JBoss installation to the JBoss Server View in Eclipse. Start JBoss in debug mode. Finally, start a command prompt in the directory where you unzipped the Seam distribution."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:33
#, no-c-format
-msgid ""
-"JBoss has sophisticated support for hot re-deployment of WARs and EARs. "
-"Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which "
-"is common during development—eventually causes the JVM to run out of perm "
-"gen space. For this reason, we recommend running JBoss in a JVM with a large "
-"perm gen space at development time. If you're running JBoss from JBoss IDE, "
-"you can configure this in the server launch configuration, under \"VM "
-"arguments\". We suggest the following values:"
+msgid "JBoss has sophisticated support for hot re-deployment of WARs and EARs. Unfortunately, due to bugs in the JVM, repeated redeployment of an EAR—which is common during development—eventually causes the JVM to run out of perm gen space. For this reason, we recommend running JBoss in a JVM with a large perm gen space at development time. If you're running JBoss from JBoss IDE, you can configure this in the server launch configuration, under \"VM arguments\". We suggest the following values:"
msgstr ""
#. Tag: programlisting
@@ -107,9 +76,7 @@
#. Tag: para
#: Gettingstarted.xml:41
#, no-c-format
-msgid ""
-"If you don't have so much memory available, the following is our minimum "
-"recommendation:"
+msgid "If you don't have so much memory available, the following is our minimum recommendation:"
msgstr ""
#. Tag: programlisting
@@ -121,17 +88,13 @@
#. Tag: para
#: Gettingstarted.xml:45
#, no-c-format
-msgid ""
-"If you're running JBoss from the command line, you can configure the JVM "
-"options in <literal>bin/run.conf</literal>."
+msgid "If you're running JBoss from the command line, you can configure the JVM options in <literal>bin/run.conf</literal>."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:48
#, no-c-format
-msgid ""
-"If you don't want to bother with this stuff now, you don't have to—come back "
-"to it later, when you get your first <literal>OutOfMemoryException</literal>."
+msgid "If you don't want to bother with this stuff now, you don't have to—come back to it later, when you get your first <literal>OutOfMemoryException</literal>."
msgstr ""
#. Tag: title
@@ -143,10 +106,7 @@
#. Tag: para
#: Gettingstarted.xml:55
#, no-c-format
-msgid ""
-"The first thing we need to do is configure seam-gen for your environment: "
-"JBoss AS installation directory, Eclipse workspace, and database connection. "
-"It's easy, just type:"
+msgid "The first thing we need to do is configure seam-gen for your environment: JBoss AS installation directory, Eclipse workspace, and database connection. It's easy, just type:"
msgstr ""
#. Tag: programlisting
@@ -174,66 +134,47 @@
"\n"
"setup:\n"
" [echo] Welcome to seam-gen :-)\n"
-" [input] Enter your Java project workspace (the directory that contains "
-"your Seam projects) [C:/Projects] [C:/Projects]\n"
+" [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects]\n"
"/Users/pmuir/workspace\n"
-" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2."
-"GA] [C:/Program Files/jboss-4.2.2.GA]\n"
+" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2.GA] [C:/Program Files/jboss-4.2.2.GA]\n"
"/Applications/jboss-4.2.2.GA\n"
" [input] Enter the project name [myproject] [myproject]\n"
"helloworld\n"
" [echo] Accepted project name as: helloworld\n"
-" [input] Select a RichFaces skin (not applicable if using ICEFaces) "
-"[blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, "
-"DEFAULT)\n"
+" [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n"
"\n"
-" [input] Is this project deployed as an EAR (with EJB components) or a "
-"WAR (with no EJB support) [ear] ([ear], war, )\n"
+" [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, )\n"
"\n"
-" [input] Enter the Java package name for your session beans [com.mydomain."
-"helloworld] [com.mydomain.helloworld]\n"
+" [input] Enter the Java package name for your session beans [com.mydomain.helloworld] [com.mydomain.helloworld]\n"
"org.jboss.helloworld\n"
-" [input] Enter the Java package name for your entity beans [org.jboss."
-"helloworld] [org.jboss.helloworld]\n"
+" [input] Enter the Java package name for your entity beans [org.jboss.helloworld] [org.jboss.helloworld]\n"
"\n"
-" [input] Enter the Java package name for your test cases [org.jboss."
-"helloworld.test] [org.jboss.helloworld.test]\n"
+" [input] Enter the Java package name for your test cases [org.jboss.helloworld.test] [org.jboss.helloworld.test]\n"
"\n"
-" [input] What kind of database are you using? [hsql] ([hsql], mysql, "
-"oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
+" [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2)\n"
"mysql\n"
-" [input] Enter the Hibernate dialect for your database [org.hibernate."
-"dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
+" [input] Enter the Hibernate dialect for your database [org.hibernate.dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
"\n"
-" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb."
-"jar] [lib/hsqldb.jar]\n"
+" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb.jar] [lib/hsqldb.jar]\n"
"/Users/pmuir/java/mysql.jar\n"
-" [input] Enter JDBC driver class for your database [com.mysql.jdbc."
-"Driver] [com.mysql.jdbc.Driver]\n"
+" [input] Enter JDBC driver class for your database [com.mysql.jdbc.Driver] [com.mysql.jdbc.Driver]\n"
"\n"
-" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:"
-"mysql:///test]\n"
+" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] [jdbc:mysql:///test]\n"
"jdbc:mysql:///helloworld\n"
" [input] Enter database username [sa] [sa]\n"
"pmuir\n"
" [input] Enter database password [] []\n"
"\n"
-" [input] skipping input as property hibernate.default_schema.new has "
-"already been set.\n"
-" [input] Enter the database catalog name (it is OK to leave this blank) "
-"[] []\n"
+" [input] skipping input as property hibernate.default_schema.new has already been set.\n"
+" [input] Enter the database catalog name (it is OK to leave this blank) [] []\n"
"\n"
-" [input] Are you working with tables that already exist in the database? "
-"[n] (y, [n], )\n"
+" [input] Are you working with tables that already exist in the database? [n] (y, [n], )\n"
"y\n"
-" [input] Do you want to drop and recreate the database tables and data in "
-"import.sql each time you deploy? [n] (y, [n], )\n"
+" [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], )\n"
"n\n"
-" [input] Enter your ICEfaces home directory (leave blank to omit "
-"ICEfaces) [] []\n"
+" [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] []\n"
"\n"
-"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/"
-"seam-gen/build.properties\n"
+"[propertyfile] Creating new property file: /Users/pmuir/workspace/jboss-seam/seam-gen/build.properties\n"
" [echo] Installing JDBC driver jar to JBoss server\n"
" [echo] Type 'seam create-project' to create the new project\n"
"\n"
@@ -245,48 +186,31 @@
#. Tag: para
#: Gettingstarted.xml:64
#, no-c-format
-msgid ""
-"The tool provides sensible defaults, which you can accept by just pressing "
-"enter at the prompt."
+msgid "The tool provides sensible defaults, which you can accept by just pressing enter at the prompt."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:66
#, no-c-format
-msgid ""
-"The most important choice you need to make is between EAR deployment and WAR "
-"deployment of your project. EAR projects support EJB 3.0 and require Java EE "
-"5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE "
-"environment. The packaging of a WAR is also simpler to understand. If you "
-"installed an EJB3-ready application server like JBoss, choose <literal>ear</"
-"literal>. Otherwise, choose <literal>war</literal>. We'll assume that you've "
-"chosen an EAR deployment for the rest of the tutorial, but you can follow "
-"exactly the same steps for a WAR deployment."
+msgid "The most important choice you need to make is between EAR deployment and WAR deployment of your project. EAR projects support EJB 3.0 and require Java EE 5. WAR projects do not support EJB 3.0, but may be deployed to a J2EE environment. The packaging of a WAR is also simpler to understand. If you installed an EJB3-ready application server like JBoss, choose <literal>ear</literal>. Otherwise, choose <literal>war</literal>. We'll assume that you've chosen an EAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a WAR deployment."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:73
#, no-c-format
-msgid ""
-"If you are working with an existing data model, make sure you tell seam-gen "
-"that the tables already exist in the database."
+msgid "If you are working with an existing data model, make sure you tell seam-gen that the tables already exist in the database."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:76
#, no-c-format
-msgid ""
-"The settings are stored in <literal>seam-gen/build.properties</literal>, but "
-"you can also modify them simply by running <literal>seam setup</literal> a "
-"second time."
+msgid "The settings are stored in <literal>seam-gen/build.properties</literal>, but you can also modify them simply by running <literal>seam setup</literal> a second time."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:79
#, no-c-format
-msgid ""
-"Now we can create a new project in our Eclipse workspace directory, by "
-"typing:"
+msgid "Now we can create a new project in our Eclipse workspace directory, by typing:"
msgstr ""
#. Tag: programlisting
@@ -305,11 +229,9 @@
"...\n"
"\n"
"new-project:\n"
-" [echo] A new Seam project named 'helloworld' was created in the C:"
-"\\Projects directory\n"
+" [echo] A new Seam project named 'helloworld' was created in the C:\\Projects directory\n"
" [echo] Type 'seam explode' and go to http://localhost:8080/helloworld\n"
-" [echo] Eclipse Users: Add the project into Eclipse using File > New "
-"> Project and select General > Project (not Java Project)\n"
+" [echo] Eclipse Users: Add the project into Eclipse using File > New > Project and select General > Project (not Java Project)\n"
" [echo] NetBeans Users: Open the project in NetBeans\n"
"\n"
"BUILD SUCCESSFUL\n"
@@ -320,75 +242,37 @@
#. Tag: para
#: Gettingstarted.xml:85
#, no-c-format
-msgid ""
-"This copies the Seam jars, dependent jars and the JDBC driver jar to a new "
-"Eclipse project, and generates all needed resources and configuration files, "
-"a facelets template file and stylesheet, along with Eclipse metadata and an "
-"Ant build script. The Eclipse project will be automatically deployed to an "
-"exploded directory structure in JBoss AS as soon as you add the project "
-"using <literal>New -> Project... -> General -> Project -> Next</"
-"literal>, typing the <literal>Project name</literal> (<literal>helloworld</"
-"literal> in this case), and then clicking <literal>Finish</literal>. Do not "
-"select <literal>Java Project</literal> from the New Project wizard."
+msgid "This copies the Seam jars, dependent jars and the JDBC driver jar to a new Eclipse project, and generates all needed resources and configuration files, a facelets template file and stylesheet, along with Eclipse metadata and an Ant build script. The Eclipse project will be automatically deployed to an exploded directory structure in JBoss AS as soon as you add the project using <literal>New -> Project... -> General -> Project -> Next</literal>, typing the <literal>Project name</literal> (<literal>helloworld</literal> in this case), and then clicking <literal>Finish</literal>. Do not select <literal>Java Project</literal> from the New Project wizard."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:93
#, no-c-format
-msgid ""
-"If your default JDK in Eclipse is not a Java SE 5 or Java SE 6 JDK, you will "
-"need to select a Java SE 5 compliant JDK using <literal>Project -> "
-"Properties -> Java Compiler</literal>."
+msgid "If your default JDK in Eclipse is not a Java SE 5 or Java SE 6 JDK, you will need to select a Java SE 5 compliant JDK using <literal>Project -> Properties -> Java Compiler</literal>."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:96
#, no-c-format
-msgid ""
-"Alternatively, you can deploy the project from outside Eclipse by typing "
-"<literal>seam explode</literal>."
+msgid "Alternatively, you can deploy the project from outside Eclipse by typing <literal>seam explode</literal>."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:98
#, no-c-format
-msgid ""
-"Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome "
-"page. This is a facelets page, <literal>view/home.xhtml</literal>, using the "
-"template <literal>view/layout/template.xhtml</literal>. You can edit this "
-"page, or the template, in eclipse, and see the results "
-"<emphasis>immediately</emphasis>, by clicking refresh in your browser."
+msgid "Go to <literal>http://localhost:8080/helloworld</literal> to see a welcome page. This is a facelets page, <literal>view/home.xhtml</literal>, using the template <literal>view/layout/template.xhtml</literal>. You can edit this page, or the template, in eclipse, and see the results <emphasis>immediately</emphasis>, by clicking refresh in your browser."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:103
#, no-c-format
-msgid ""
-"Don't get scared by the XML configuration documents that were generated into "
-"the project directory. They are mostly standard Java EE stuff, the stuff you "
-"need to create once and then never look at again, and they are 90% the same "
-"between all Seam projects. (They are so easy to write that even seam-gen can "
-"do it.)"
+msgid "Don't get scared by the XML configuration documents that were generated into the project directory. They are mostly standard Java EE stuff, the stuff you need to create once and then never look at again, and they are 90% the same between all Seam projects. (They are so easy to write that even seam-gen can do it.)"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:107
#, no-c-format
-msgid ""
-"The generated project includes three database and persistence "
-"configurations. The <literal>persistence-test.xml</literal> and "
-"<literal>import-test.sql</literal> files are used when running the TestNG "
-"unit tests against HSQLDB. The database schema and the test data in "
-"<literal>import-test.sql</literal> is always exported to the database before "
-"running tests. The <literal>myproject-dev-ds.xml</literal>, "
-"<literal>persistence-dev.xml</literal>and <literal>import-dev.sql</literal> "
-"files are for use when deploying the application to your development "
-"database. The schema might be exported automatically at deployment, "
-"depending upon whether you told seam-gen that you are working with an "
-"existing database. The <literal>myproject-prod-ds.xml</literal>, "
-"<literal>persistence-prod.xml</literal>and <literal>import-prod.sql</"
-"literal> files are for use when deploying the application to your production "
-"database. The schema is not exported automatically at deployment."
+msgid "The generated project includes three database and persistence configurations. The <literal>persistence-test.xml</literal> and <literal>import-test.sql</literal> files are used when running the TestNG unit tests against HSQLDB. The database schema and the test data in <literal>import-test.sql</literal> is always exported to the database before running tests. The <literal>myproject-dev-ds.xml</literal>, <literal>persistence-dev.xml</literal>and <literal>import-dev.sql</literal> files are for use when deploying the application to your development database. The schema might be exported automatically at deployment, depending upon whether you told seam-gen that you are working with an existing database. The <literal>myproject-prod-ds.xml</literal>, <literal>persistence-prod.xml</literal>and <literal>import-prod.sql</literal> files are for use when deploying the application to your production database. The schema is not exported automatically at deployment."
msgstr ""
#. Tag: title
@@ -400,10 +284,7 @@
#. Tag: para
#: Gettingstarted.xml:123
#, no-c-format
-msgid ""
-"If you're used to traditional action-style web frameworks, you're probably "
-"wondering how you can create a simple web page with a stateless action "
-"method in Java. If you type:"
+msgid "If you're used to traditional action-style web frameworks, you're probably wondering how you can create a simple web page with a stateless action method in Java. If you type:"
msgstr ""
#. Tag: programlisting
@@ -415,9 +296,7 @@
#. Tag: para
#: Gettingstarted.xml:128
#, no-c-format
-msgid ""
-"Seam will prompt for some information, and generate a new facelets page and "
-"Seam component for your project."
+msgid "Seam will prompt for some information, and generate a new facelets page and Seam component for your project."
msgstr ""
#. Tag: programlisting
@@ -446,19 +325,13 @@
"setup-filters:\n"
"\n"
"new-action:\n"
-" [echo] Creating a new stateless session bean component with an action "
-"method\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\\test\n"
-" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss"
-"\\helloworld\\test\n"
+" [echo] Creating a new stateless session bean component with an action method\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\helloworld\\src\\hot\\org\\jboss\\helloworld\\test\n"
" [copy] Copying 1 file to C:\\Projects\\helloworld\\view\n"
-" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/"
-"ping.seam\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/helloworld/ping.seam\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 13 seconds\n"
@@ -468,34 +341,19 @@
#. Tag: para
#: Gettingstarted.xml:133
#, no-c-format
-msgid ""
-"Because we've added a new Seam component, we need to restart the exploded "
-"directory deployment. You can do this by typing <literal>seam restart</"
-"literal>, or by running the <literal>restart</literal> target in the "
-"generated project <literal>build.xml</literal> file from inside Eclipse. "
-"Another way to force a restart is to edit the file <literal>resources/META-"
-"INF/application.xml</literal> in Eclipse. <emphasis>Note that you do not "
-"need to restart JBoss each time you change the application.</emphasis>"
+msgid "Because we've added a new Seam component, we need to restart the exploded directory deployment. You can do this by typing <literal>seam restart</literal>, or by running the <literal>restart</literal> target in the generated project <literal>build.xml</literal> file from inside Eclipse. Another way to force a restart is to edit the file <literal>resources/META-INF/application.xml</literal> in Eclipse. <emphasis>Note that you do not need to restart JBoss each time you change the application.</emphasis>"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:139
#, no-c-format
-msgid ""
-"Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and "
-"click the button. You can see the code behind this action by looking in the "
-"project <literal>src</literal> directory. Put a breakpoint in the "
-"<literal>ping()</literal> method, and click the button again."
+msgid "Now go to <literal>http://localhost:8080/helloworld/ping.seam</literal> and click the button. You can see the code behind this action by looking in the project <literal>src</literal> directory. Put a breakpoint in the <literal>ping()</literal> method, and click the button again."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:143
#, no-c-format
-msgid ""
-"Finally, locate the <literal>PingTest.xml</literal> file in the test package "
-"and run the integration tests using the TestNG plugin for Eclipse. "
-"Alternatively, run the tests using <literal>seam test</literal> or the "
-"<literal>test</literal> target of the generated build."
+msgid "Finally, locate the <literal>PingTest.xml</literal> file in the test package and run the integration tests using the TestNG plugin for Eclipse. Alternatively, run the tests using <literal>seam test</literal> or the <literal>test</literal> target of the generated build."
msgstr ""
#. Tag: title
@@ -542,17 +400,13 @@
"setup-filters:\n"
"\n"
"new-form:\n"
-" [echo] Creating a new stateful session bean component with an action "
-"method\n"
+" [echo] Creating a new stateful session bean component with an action method\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\n"
-" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello"
-"\\test\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
" [copy] Copying 1 file to C:\\Projects\\hello\\view\n"
-" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello"
-"\\test\n"
-" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello."
-"seam\n"
+" [copy] Copying 1 file to C:\\Projects\\hello\\src\\hot\\com\\hello\\test\n"
+" [echo] Type 'seam restart' and go to http://localhost:8080/hello/hello.seam\n"
"\n"
"BUILD SUCCESSFUL\n"
"Total time: 5 seconds\n"
@@ -562,11 +416,7 @@
#. Tag: para
#: Gettingstarted.xml:157
#, no-c-format
-msgid ""
-"Restart the application again, and go to <literal>http://localhost:8080/"
-"helloworld/hello.seam</literal>. Then take a look at the generated code. Run "
-"the test. Try adding some new fields to the form and Seam component "
-"(remember to restart the deployment each time you change the Java code)."
+msgid "Restart the application again, and go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Then take a look at the generated code. Run the test. Try adding some new fields to the form and Seam component (remember to restart the deployment each time you change the Java code)."
msgstr ""
#. Tag: title
@@ -578,9 +428,7 @@
#. Tag: para
#: Gettingstarted.xml:165
#, no-c-format
-msgid ""
-"Manually create some tables in your database. (If you need to switch to a "
-"different database, just run <literal>seam setup</literal> again.) Now type:"
+msgid "Manually create some tables in your database. (If you need to switch to a different database, just run <literal>seam setup</literal> again.) Now type:"
msgstr ""
#. Tag: programlisting
@@ -592,12 +440,7 @@
#. Tag: para
#: Gettingstarted.xml:170
#, no-c-format
-msgid ""
-"Restart the deployment, and go to <literal>http://localhost:8080/helloworld</"
-"literal>. You can browse the database, edit existing objects, and create new "
-"objects. If you look at the generated code, you'll probably be amazed how "
-"simple it is! Seam was designed so that data access code is easy to write by "
-"hand, even for people who don't want to cheat by using seam-gen."
+msgid "Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>. You can browse the database, edit existing objects, and create new objects. If you look at the generated code, you'll probably be amazed how simple it is! Seam was designed so that data access code is easy to write by hand, even for people who don't want to cheat by using seam-gen."
msgstr ""
#. Tag: title
@@ -609,9 +452,7 @@
#. Tag: para
#: Gettingstarted.xml:179
#, no-c-format
-msgid ""
-"Place your existing, valid entity classes inside the <literal>src/main</"
-"literal>. Now type"
+msgid "Place your existing, valid entity classes inside the <literal>src/main</literal>. Now type"
msgstr ""
#. Tag: programlisting
@@ -623,9 +464,7 @@
#. Tag: para
#: Gettingstarted.xml:183
#, no-c-format
-msgid ""
-"Restart the deployment, and go to <literal>http://localhost:8080/helloworld</"
-"literal>."
+msgid "Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>."
msgstr ""
#. Tag: title
@@ -637,25 +476,13 @@
#. Tag: para
#: Gettingstarted.xml:189
#, no-c-format
-msgid ""
-"Finally, we want to be able to deploy the application using standard Java EE "
-"5 packaging. First, we need to remove the exploded directory by running "
-"<literal>seam unexplode</literal>. To deploy the EAR, we can type "
-"<literal>seam deploy</literal> at the command prompt, or run the "
-"<literal>deploy</literal> target of the generated project build script. You "
-"can undeploy using <literal>seam undeploy</literal> or the "
-"<literal>undeploy</literal> target."
+msgid "Finally, we want to be able to deploy the application using standard Java EE 5 packaging. First, we need to remove the exploded directory by running <literal>seam unexplode</literal>. To deploy the EAR, we can type <literal>seam deploy</literal> at the command prompt, or run the <literal>deploy</literal> target of the generated project build script. You can undeploy using <literal>seam undeploy</literal> or the <literal>undeploy</literal> target."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:195
#, no-c-format
-msgid ""
-"By default, the application will be deployed with the <emphasis>dev profile</"
-"emphasis>. The EAR will include the <literal>persistence-dev.xml</literal> "
-"and <literal>import-dev.sql</literal> files, and the <literal>myproject-dev-"
-"ds.xml</literal> file will be deployed. You can change the profile, and use "
-"the <emphasis>prod profile</emphasis>, by typing"
+msgid "By default, the application will be deployed with the <emphasis>dev profile</emphasis>. The EAR will include the <literal>persistence-dev.xml</literal> and <literal>import-dev.sql</literal> files, and the <literal>myproject-dev-ds.xml</literal> file will be deployed. You can change the profile, and use the <emphasis>prod profile</emphasis>, by typing"
msgstr ""
#. Tag: programlisting
@@ -667,12 +494,7 @@
#. Tag: para
#: Gettingstarted.xml:202
#, no-c-format
-msgid ""
-"You can even define new deployment profiles for your application. Just add "
-"appropriately named files to your project—for example, <literal>persistence-"
-"staging.xml</literal>, <literal>import-staging.sql</literal> and "
-"<literal>myproject-staging-ds.xml</literal>—and select the name of the "
-"profile using <literal>-Dprofile=staging</literal>."
+msgid "You can even define new deployment profiles for your application. Just add appropriately named files to your project—for example, <literal>persistence-staging.xml</literal>, <literal>import-staging.sql</literal> and <literal>myproject-staging-ds.xml</literal>—and select the name of the profile using <literal>-Dprofile=staging</literal>."
msgstr ""
#. Tag: title
@@ -684,11 +506,7 @@
#. Tag: para
#: Gettingstarted.xml:211
#, no-c-format
-msgid ""
-"When you deploy your Seam application as an exploded directory, you'll get "
-"some support for incremental hot deployment at development time. You need to "
-"enable debug mode in both Seam and Facelets, by adding this line to "
-"<literal>components.xml</literal>:"
+msgid "When you deploy your Seam application as an exploded directory, you'll get some support for incremental hot deployment at development time. You need to enable debug mode in both Seam and Facelets, by adding this line to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -700,9 +518,7 @@
#. Tag: para
#: Gettingstarted.xml:217
#, no-c-format
-msgid ""
-"Now, the following files may be redeployed without requiring a full restart "
-"of the web application:"
+msgid "Now, the following files may be redeployed without requiring a full restart of the web application:"
msgstr ""
#. Tag: para
@@ -720,22 +536,13 @@
#. Tag: para
#: Gettingstarted.xml:229
#, no-c-format
-msgid ""
-"But if we want to change any Java code, we still need to do a full restart "
-"of the application. (In JBoss this may be accomplished by touching the top "
-"level deployment descriptor: <literal>application.xml</literal> for an EAR "
-"deployment, or <literal>web.xml</literal> for a WAR deployment.)"
+msgid "But if we want to change any Java code, we still need to do a full restart of the application. (In JBoss this may be accomplished by touching the top level deployment descriptor: <literal>application.xml</literal> for an EAR deployment, or <literal>web.xml</literal> for a WAR deployment.)"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:233
#, no-c-format
-msgid ""
-"But if you really want a fast edit/compile/test cycle, Seam supports "
-"incremental redeployment of JavaBean components. To make use of this "
-"functionality, you must deploy the JavaBean components into the <literal>WEB-"
-"INF/dev</literal> directory, so that they will be loaded by a special Seam "
-"classloader, instead of by the WAR or EAR classloader."
+msgid "But if you really want a fast edit/compile/test cycle, Seam supports incremental redeployment of JavaBean components. To make use of this functionality, you must deploy the JavaBean components into the <literal>WEB-INF/dev</literal> directory, so that they will be loaded by a special Seam classloader, instead of by the WAR or EAR classloader."
msgstr ""
#. Tag: para
@@ -747,9 +554,7 @@
#. Tag: para
#: Gettingstarted.xml:242
#, no-c-format
-msgid ""
-"the components must be JavaBean components, they cannot be EJB3 beans (we "
-"are working on fixing this limitation)"
+msgid "the components must be JavaBean components, they cannot be EJB3 beans (we are working on fixing this limitation)"
msgstr ""
#. Tag: para
@@ -761,25 +566,19 @@
#. Tag: para
#: Gettingstarted.xml:251
#, no-c-format
-msgid ""
-"components deployed via <literal>components.xml</literal> may not be hot-"
-"deployed"
+msgid "components deployed via <literal>components.xml</literal> may not be hot-deployed"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:255
#, no-c-format
-msgid ""
-"the hot-deployable components will not be visible to any classes deployed "
-"outside of <literal>WEB-INF/dev</literal>"
+msgid "the hot-deployable components will not be visible to any classes deployed outside of <literal>WEB-INF/dev</literal>"
msgstr ""
#. Tag: para
#: Gettingstarted.xml:260
#, no-c-format
-msgid ""
-"Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> "
-"must be in <literal>WEB-INF/lib</literal>"
+msgid "Seam debug mode must be enabled and <literal>jboss-seam-debug.jar</literal> must be in <literal>WEB-INF/lib</literal>"
msgstr ""
#. Tag: para
@@ -791,19 +590,13 @@
#. Tag: para
#: Gettingstarted.xml:269
#, no-c-format
-msgid ""
-"You may see errors if the system is placed under any load and debug is "
-"enabled."
+msgid "You may see errors if the system is placed under any load and debug is enabled."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:274
#, no-c-format
-msgid ""
-"If you create a WAR project using seam-gen, incremental hot deployment is "
-"available out of the box for classes in the <literal>src/hot</literal> "
-"source directory. However, seam-gen does not support incremental hot "
-"deployment for EAR projects."
+msgid "If you create a WAR project using seam-gen, incremental hot deployment is available out of the box for classes in the <literal>src/hot</literal> source directory. However, seam-gen does not support incremental hot deployment for EAR projects."
msgstr ""
#. Tag: title
@@ -815,14 +608,7 @@
#. Tag: para
#: Gettingstarted.xml:282
#, no-c-format
-msgid ""
-"Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss AS, we "
-"recommend using JBoss 4.2, which bundles the JSF 1.2 reference "
-"implementation. However, it is still possible to use Seam 2.0 on the JBoss "
-"4.0 platform. There are two basic steps required to do this: install an EJB3-"
-"enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference "
-"implementation. Once you complete these steps, Seam 2.0 applications can be "
-"deployed to JBoss 4.0."
+msgid "Seam 2.0 was developed for JavaServer Faces 1.2. When using JBoss AS, we recommend using JBoss 4.2, which bundles the JSF 1.2 reference implementation. However, it is still possible to use Seam 2.0 on the JBoss 4.0 platform. There are two basic steps required to do this: install an EJB3-enabled version of JBoss 4.0 and replace MyFaces with the JSF 1.2 reference implementation. Once you complete these steps, Seam 2.0 applications can be deployed to JBoss 4.0."
msgstr ""
#. Tag: title
@@ -834,13 +620,7 @@
#. Tag: para
#: Gettingstarted.xml:290
#, no-c-format
-msgid ""
-"JBoss 4.0 does not ship a default configuration compatible with Seam. To run "
-"Seam, you must install JBoss 4.0.5 using the JEMS 1.2 installer with the "
-"ejb3 profile selected. Seam will not run with an installation that doesn't "
-"include EJB3 support. The JEMS installer can be downloaded from <ulink url="
-"\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/"
-"jemsinstaller/downloads</ulink>."
+msgid "JBoss 4.0 does not ship a default configuration compatible with Seam. To run Seam, you must install JBoss 4.0.5 using the JEMS 1.2 installer with the ejb3 profile selected. Seam will not run with an installation that doesn't include EJB3 support. The JEMS installer can be downloaded from <ulink url=\"http://labs.jboss.com/jemsinstaller/downloads\">http://labs.jboss.com/jemsinstaller/downloads</ulink>."
msgstr ""
#. Tag: title
@@ -852,21 +632,12 @@
#. Tag: para
#: Gettingstarted.xml:299
#, no-c-format
-msgid ""
-"The web configuration for JBoss 4.0 can be found in the <literal>server/"
-"default/deploy/jbossweb-tomcat55.sar</literal>. You'll need to delete "
-"<literal>myfaces-api.jar</literal> any <literal>myfaces-impl.jar</literal> "
-"from the <literal>jsf-libs </literal>directory. Then, you'll need to copy "
-"<literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-"
-"api.jar</literal>, and <literal>el-ri.jar</literal> to that directory. The "
-"JSF JARs can be found in the Seam <literal>lib</literal> directory. The el "
-"JARs can be obtained from the Seam 1.2 release."
+msgid "The web configuration for JBoss 4.0 can be found in the <literal>server/default/deploy/jbossweb-tomcat55.sar</literal>. You'll need to delete <literal>myfaces-api.jar</literal> any <literal>myfaces-impl.jar</literal> from the <literal>jsf-libs </literal>directory. Then, you'll need to copy <literal>jsf-api.jar</literal>, <literal>jsf-impl.jar</literal>, <literal>el-api.jar</literal>, and <literal>el-ri.jar</literal> to that directory. The JSF JARs can be found in the Seam <literal>lib</literal> directory. The el JARs can be obtained from the Seam 1.2 release."
msgstr ""
#. Tag: para
#: Gettingstarted.xml:307
#, no-c-format
-msgid ""
-"You'll also need to edit the <literal>conf/web.xml</literal>, replacing "
-"<literal>myfaces-impl.jar</literal> with <literal>jsf-impl.jar</literal>."
+msgid "You'll also need to edit the <literal>conf/web.xml</literal>, replacing <literal>myfaces-impl.jar</literal> with <literal>jsf-impl.jar</literal>."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-12 00:17+0100\n"
+"PO-Revision-Date: 2008-12-14 22:11+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,7 +23,7 @@
#: 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."
-msgstr ""
+msgstr "JBoss jBPM è un motore di gestione dei processi di business per ambiente Java SE o EE. jBPM ti consente di rappresentare un processo di business o un'interazione utente come un grafo di nodi, raffiguranti stati d'attesa, decisioni, compiti (task), pagine web, ecc. Il grafo viene definito usando un dialetto XML semplice, molto leggibile, chiamato jPDL, che può essere editato e visualizzato graficamente usando un plugin di eclipse. jPDL è un linguaggio estendibile ed è adatto per un range di problemi, dalla definizione di un flusso di pagine dell'applicazione web alla gestione tradizionale del workflow, fino all'orchestrazione di servizi in un ambiente SOA."
#. Tag: para
#: Jbpm.xml:16
@@ -71,7 +71,7 @@
#: Jbpm.xml:67
#, no-c-format
msgid "Using JSF or Seam navigation rules - the <emphasis>stateless navigation model</emphasis>"
-msgstr ""
+msgstr "Uso di JSF o delle regole di navigazione di Seam - il <emphasis>modello di navigazione stateless</emphasis>"
#. Tag: para
#: Jbpm.xml:73
@@ -89,7 +89,7 @@
#: Jbpm.xml:86
#, no-c-format
msgid "The two navigation models"
-msgstr ""
+msgstr "I due modelli di navigazione"
#. Tag: para
#: Jbpm.xml:88
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-14 00:24+0100\n"
+"PO-Revision-Date: 2008-12-14 21:05+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -223,7 +223,7 @@
#: 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."
-msgstr "Pensiamo che l'ultima incarnazione di Java EE sia ottima. Ma sappiamo che non sarà mai perfetta. Dove ci sono dei buchi nella specifica) per esempio, limitazioni nel ciclo di vita JSF per le richieste GET), Seam li risolve. E gli autori di Seam stanno lavorando con i gruppi esperti JCP per assicurare che queste soluzioni siano incorporate nelle prossime revisioni degli standard."
+msgstr "Pensiamo che l'ultima incarnazione di Java EE sia ottima. Ma sappiamo che non sarà mai perfetta. Dove ci sono dei buchi nella specifica (per esempio limitazioni nel ciclo di vita JSF per le richieste GET), Seam li risolve. E gli autori di Seam stanno lavorando con i gruppi esperti JCP per assicurare che queste soluzioni siano incorporate nelle prossime revisioni degli standard."
#. Tag: emphasis
#: Preface.xml:245
@@ -253,11 +253,11 @@
#: 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 "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."
+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 a 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 "Risulta che la combinazione di Seam, JSF e EJB3 è <emphasis>il</emphasis> modo più semplice per scrivere un'applicazione web complessa in Java. Ti stupirai di quanto poco codice viene richiesto!"
+msgstr "La combinazione di Seam, JSF e EJB3 è <emphasis>il</emphasis> modo più semplice per scrivere una complessa applicazione web in Java. Ti stupirai di quanto poco codice viene richiesto!"
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Testing.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:39+0000\n"
-"PO-Revision-Date: 2008-12-13 20:13+0100\n"
+"PO-Revision-Date: 2008-12-14 21:53+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -23,13 +23,13 @@
#: Testing.xml:3
#, no-c-format
msgid "Most Seam applications will need at least two kinds of automated tests: <emphasis>unit tests</emphasis>, which test a particular Seam component in isolation, and scripted <emphasis>integration tests</emphasis> which exercise all Java layers of the application (that is, everything except the view pages)."
-msgstr ""
+msgstr "La maggior parte delle applicazioni Seam hanno bisogno di almeno due tipi di test automatici: <emphasis>test di unità</emphasis> per testare un particolare componente Seam in isolamento, e <emphasis>test d'integrazione</emphasis> per provare tutti i layer java dell'applicazione (cioè tutto, tranne le pagine di vista)."
#. Tag: para
#: Testing.xml:10
#, no-c-format
msgid "Both kinds of tests are very easy to write."
-msgstr ""
+msgstr "Entrambi i tipi di test sono facili da scrivere."
#. Tag: title
#: Testing.xml:15
@@ -163,7 +163,7 @@
#: Testing.xml:44
#, no-c-format
msgid "However, if you want to test the entire application, read on."
-msgstr ""
+msgstr "Comunque se vuoi testare l'intera applicazione, continua nella lettura."
#. Tag: title
#: Testing.xml:51
@@ -987,5 +987,5 @@
#: Testing.xml:484
#, no-c-format
msgid "There is no support for rendering standard JSF components so you can't test the content body of the mail message easily."
-msgstr ""
+msgstr "Non c'è alcun supporto per il rendering dei componenti JSF standard, così non è possibile testare facilmente il corpo dei messaggi email."
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 23:24:40 UTC (rev 9775)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-14 21:16:33 UTC (rev 9776)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-13 17:58+0000\n"
-"PO-Revision-Date: 2008-12-14 00:06+0100\n"
+"PO-Revision-Date: 2008-12-14 21:19+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -95,7 +95,7 @@
#: 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."
-msgstr ""
+msgstr "Questi esempi sono configurati anche per essere usati in Tomcat 6.0. Occorreràseguire le istruzioni in <xref linkend=\"config.install.embedded\"/> per installare JBoss Embedded in Tomcat 6.0. JBoss Embedded è richiesto per eseguire le demo di Seam che usano componenti EJB3 in Tomcat. Ci sono anche esempio di applicazioni non-EJB3 che possono funzionare in Tomcat senza JBoss Embedded."
#. Tag: para
#: Tutorial.xml:79
@@ -107,7 +107,7 @@
#: 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."
-msgstr ""
+msgstr "Dovrai usare un diverso target Ant per utilizzare Tomcat. Usa <literal>ant tomcat.deploy</literal> nella sotto-directory d'esempio per il build ed il deploy in Tomcat."
#. Tag: para
#: Tutorial.xml:90
@@ -143,7 +143,7 @@
#: Tutorial.xml:119
#, no-c-format
msgid "We'll go slowly, since we realize you might not yet be familiar with EJB 3.0."
-msgstr ""
+msgstr "Andiamo piano, poiché ci rendiamo conto che EJB 3.0 potrebbe non esserti familiare."
#. Tag: para
#: Tutorial.xml:121
@@ -4560,13 +4560,13 @@
#: 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."
-msgstr ""
+msgstr "Prova il deploy dell'applicazione, apri più finestre o tab e prova combinzioni di vari hotel con varie opzioni di camera. La conferma risulterà sempre nel giusto hotel e con la corretta opzione grazie al modello di conversazioni innestate."
#. Tag: title
#: Tutorial.xml:1676
#, no-c-format
msgid "A complete application featuring Seam and jBPM: the DVD Store example"
-msgstr ""
+msgstr "Un'applicazione completa di Seam e jBPM: esempio di Negozio DVD"
#. Tag: para
#: Tutorial.xml:1678
@@ -4761,7 +4761,7 @@
#: Tutorial.xml:1798
#, no-c-format
msgid "Bookmarkable search results page"
-msgstr ""
+msgstr "Pagina bookmarkable dei risultati di ricerca"
#. Tag: para
#: Tutorial.xml:1800
@@ -4897,7 +4897,7 @@
#: Tutorial.xml:1860
#, no-c-format
msgid "The redirect takes us to the <literal>search.xhtml</literal> page:"
-msgstr ""
+msgstr "Il redirect di porta alla pagina <literal>search.xhtml</literal>:"
#. Tag: programlisting
#: Tutorial.xml:1862
@@ -5051,7 +5051,7 @@
#: Tutorial.xml:1874
#, no-c-format
msgid "Using \"push\"-style MVC in a RESTful application"
-msgstr ""
+msgstr "Uso di MVC push in un'applicazione RESTful"
#. Tag: para
#: Tutorial.xml:1876
@@ -5063,7 +5063,7 @@
#: 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:"
-msgstr ""
+msgstr "Il componente <literal>entryAction</literal> funziona come una action class in un framework tradizionale orientato alle azioni e push-MVC come Struts:"
#. Tag: programlisting
#: Tutorial.xml:1884
16 years
- 1
- 0
Seam SVN: r9775 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-13 18:24:40 -0500 (Sat, 13 Dec 2008)
New Revision: 9775
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-13 21:11:22 UTC (rev 9774)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Elenhancements.po 2008-12-13 23:24:40 UTC (rev 9775)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-13 14:10+0100\n"
+"PO-Revision-Date: 2008-12-13 23:54+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -121,7 +121,7 @@
#: Elenhancements.xml:60
#, no-c-format
msgid "You must ensure that the parameters are available not only when the page is rendered, but also when it is submittedIf the arguments can not be resolved when the page is submitted the action method will be called with <literal>null</literal> arguments!"
-msgstr "Devi assicurarti che i paramentri siano disponibili non solo quando la pagina viene generata, ma anche quando ne viene fatto il submit. Se gli argomenti non possono essere risolti quando la pagina viene inviata, il metodo d'azione verrà chiamato con argomenti <literal>null</literal>!"
+msgstr "Devi assicurarti che i parametri siano disponibili non solo quando la pagina viene generata, ma anche quando ne viene fatto il submit. Se gli argomenti non possono essere risolti quando la pagina viene inviata, il metodo d'azione verrà chiamato con argomenti <literal>null</literal>!"
#. Tag: para
#: Elenhancements.xml:67
@@ -206,7 +206,7 @@
#: Elenhancements.xml:127
#, no-c-format
msgid "<emphasis>Use inside iterative components</emphasis> — Components like <literal><c:forEach /></literal> and <literal><ui:repeat /></literal>iterate over a List or array, exposing each item in the list to nested components. This works great if you are selecting a row using a <literal><h:commandButton /></literal> or <literal><h:commandLink /></literal>:"
-msgstr "<emphasis>Utilizzo all'interno di componenti iterativi</emphasis> — Componenti quali <literal><c:forEach /></literal> e <literal><ui:repeat /></literal>iterano su una lista o un array, esponendo ogni item della lista ai componenti innestati. Questo funziona bene se si sta selezionando unriga con <literal><h:commandButton /></literal> o <literal><h:commandLink /></literal>:"
+msgstr "<emphasis>Utilizzo all'interno di componenti iterativi</emphasis> — Componenti quali <literal><c:forEach /></literal> e <literal><ui:repeat /></literal>iterano su una lista o un array, esponendo ogni item della lista ai componenti innestati. Questo funziona bene selezionando una riga con <literal><h:commandButton /></literal> o <literal><h:commandLink /></literal>:"
#. Tag: programlisting
#: Elenhancements.xml:136
@@ -242,7 +242,7 @@
#: Elenhancements.xml:138
#, no-c-format
msgid "However if you want to use <literal><s:link /></literal> or <literal><s:button /></literal> you <emphasis>must</emphasis> expose the items as a <literal>DataModel</literal>, and use a <literal><dataTable /></literal> (or equivalent from a component set like <literal><rich:dataTable /></literal> ). Neither <literal><s:link /></literal> or <literal><s:button /></literal> submit the form (and therefore produce a bookmarkable link) so a \"magic\" parameter is needed to recreate the item when the action method is called. This magic parameter can only be added when a data table backed by a <literal>DataModel</literal> is used."
-msgstr "Comunque si voglia usare <literal><s:link /></literal> o <literal><s:button /></literal> si <emphasis>deve</emphasis> esporre gli item come <literal>DataModel</literal> e usare <literal><dataTable /></literal> (o equivalente da componente impostato come <literal><rich:dataTable /></literal> ). Né <literal><s:link /></literal> né <literal><s:button /></literal> eseguono il submit della form (e quindi producono un bookmarkable link) quindi un parametro \"magico\" serve per ricreare l'item quando l'action method viene chiamato. Questo parametro magico può essere aggiunto soltanto quando viene usata una data table con dietro un <literal>DataModel</literal>."
+msgstr "Comunque si voglia usare <literal><s:link/></literal> o <literal><s:button/></literal> si <emphasis>deve</emphasis> esporre gli item come <literal>DataModel</literal> e usare <literal><dataTable /></literal> (o equivalente da componente impostato come <literal><rich:dataTable /></literal> ). Né <literal><s:link /></literal> né <literal><s:button /></literal> eseguono il submit della form (e quindi producono un bookmarkable link) quindi serve un parametro \"magico\" per ricreare l'item quando viene chiamato l'action method. Questo parametro magico può essere aggiunto soltanto quando viene usata una data table con dietro un <literal>DataModel</literal>."
#. Tag: para
#: Elenhancements.xml:154
@@ -260,13 +260,13 @@
#: Elenhancements.xml:175
#, no-c-format
msgid "Ordinarily, it is safe to call <literal>methodExpression.getMethodInfo().getParamTypes()</literal> at any time. For an expression with parameters, you must first invoke the <literal>MethodExpression</literal> before calling <literal>getParamTypes()</literal>."
-msgstr "Solitamente è sicuro chiamare in ogni momento <literal>methodExpression.getMethodInfo().getParamTypes()</literal>. Per un'espressione con parametri occorre prima invocare il <literal>MethodExpression</literal> prima di chiamare <literal>getParamTypes()</literal>."
+msgstr "Solitamente è sicuro chiamare in ogni momento <literal>methodExpression.getMethodInfo().getParamTypes()</literal>. Per un'espressione con parametri occorre invocare il <literal>MethodExpression</literal> prima di chiamare <literal>getParamTypes()</literal>."
#. Tag: para
#: Elenhancements.xml:185
#, no-c-format
msgid "Both of these cases are exceedingly rare and only apply when you want to invoke the <literal>MethodExpression</literal> by hand in Java code."
-msgstr "Entrambi questi casi sono estremamente rari e si applicano solo quando vuoi invocare <literal>MethodExpression</literal> manualmente nel codice Java."
+msgstr "Entrambi questi casi sono estremamente rari e si applicano solo quando vuoi invocare manualmente <literal>MethodExpression</literal> nel codice Java."
#. Tag: title
#: Elenhancements.xml:196
@@ -290,7 +290,7 @@
#: Elenhancements.xml:206
#, no-c-format
msgid "might return a list of departments. If you only need a list of department names, your only option is to iterate over the list to retrieve the values. JBoss EL allows this with a projection expression:"
-msgstr "potrebbe restituire una lista di dipartimenti. Se tu avessi bisogno di una lista di nommi di dipartimento, la tua unica opzione è quella di iterare sulla lista per recuperare i valori. JBoss EL permette questo con l'espressione di proiezione:"
+msgstr "potrebbe restituire una lista di dipartimenti. Se tu avessi bisogno di una lista di nomi di dipartimento, l'unica opzione è quella di iterare sulla lista per recuperare i valori. JBoss EL permette questo con l'espressione di proiezione:"
#. Tag: programlisting
#: Elenhancements.xml:212
@@ -356,5 +356,5 @@
#: Elenhancements.xml:252
#, no-c-format
msgid "It is important to note that this syntax cannot be parsed by Facelets or JSP and thus cannot be used in xhtml or JSP files. We anticipate that the projection syntax will change in future versions of JBoss EL."
-msgstr "E' importante notare che questa sintassi non può essere analizzata da Facelet o JSP e quindi non può essere usata in file xhtml o jsp. Anticipiamo che la sintassi di proiezione cambierà nelle future versioni di JBoss EL."
+msgstr "E' importante notare che questa sintassi non può essere analizzata da Facelets o JSP e quindi non può essere usata in file xhtml o jsp. Anticipiamo che la sintassi di proiezione cambierà nelle future versioni di JBoss EL."
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 21:11:22 UTC (rev 9774)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 23:24:40 UTC (rev 9775)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-13 22:11+0100\n"
+"PO-Revision-Date: 2008-12-14 00:24+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -71,7 +71,7 @@
#: 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!"
-msgstr "E' possibile scrivere applicazioni Seam dove \"qualsiasi cosa\" sia un EJB. Questo potrebbe essere per te sorprendente, se sei abituato a pensare agli EJB come ad oggetti cosiddetti a grana-grossa, \"di peso massimo\". Comunque la versione 3.0 ha completamente cambiato la natura di EJB dal puntodivista dello sviluppatore. Un EJB è un oggetto a grana-fine— non più complesso di un JavaBean con annotazioni. Seam ti incoraggia ad usare session bean come action listeners JSF! "
+msgstr "E' possibile scrivere applicazioni Seam dove \"qualsiasi cosa\" sia un EJB. Questo potrebbe essere per te sorprendente, se sei abituato a pensare agli EJB come ad oggetti cosiddetti a grana-grossa, \"di peso massimo\". Comunque la versione 3.0 ha completamente cambiato la natura di EJB dal punto di vista dello sviluppatore. Un EJB è un oggetto a grana-fine— non più complesso di un JavaBean con annotazioni. Seam ti incoraggia ad usare i session bean come action listener JSF! "
#. Tag: para
#: Preface.xml:69
@@ -101,7 +101,7 @@
#: 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."
-msgstr "Nessuno di questi approcci funzionerebbe bene, se non fosse per la gestione interna a grana-fine di Seam della concorrenza e dello stato, la quale assicura che molte richieste (fine-grained) AJAX concorrenti e asincrone vengano gestite in modo sicuro ed efficiente lato server."
+msgstr "Nessuno di questi approcci funzionerebbe bene, se non fosse per la gestione interna di Seam della concorrenza e dello stato, la quale assicura che molte richieste AJAX a grana fine (fine-grained) concorrenti e asincrone vengano gestite in modo sicuro ed efficiente lato server."
# da rivedere FIRST CLASS CONSTRUCT
#. Tag: emphasis
@@ -259,5 +259,5 @@
#: 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 "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!"
+msgstr "Risulta che la combinazione di Seam, JSF e EJB3 è <emphasis>il</emphasis> modo più semplice per scrivere un'applicazione web complessa in Java. Ti stupirai di 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-13 21:11:22 UTC (rev 9774)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-13 23:24:40 UTC (rev 9775)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-13 17:58+0000\n"
-"PO-Revision-Date: 2008-12-13 15:49+0100\n"
+"PO-Revision-Date: 2008-12-14 00:06+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -28,21 +28,8 @@
#. Tag: para
#: Tutorial.xml:9
#, no-c-format
-msgid ""
-"Seam provides a number of example applications demonstrating how to use the "
-"various features of Seam. This tutorial will guide you through a few of "
-"those examples to help you get started learning Seam. The Seam examples are "
-"located in the <filename>examples</filename> subdirectory of the Seam "
-"distribution. The registration example, which will be the first example we "
-"look at, is in the <filename>examples/registration</filename> directory."
-msgstr ""
-"Seam fornisce un ampio numeri di applicazioni d'esempio che dimostrano l'uso "
-"delle varie funzionalità di Seam. Questo tutorial ti guiderà attraverso "
-"alcuni di questi esempi per aiutarti nell'apprendimento di Seam. Gli esempi "
-"di Seam sono posizionati nella sottodirectory <filename>examples</filename> "
-"della distribuzione Seam. L'esempio di registrazione, che è il primo esempio "
-"che vediamo, si trova nella directoyry <filename>examples/registration</"
-"filename>."
+msgid "Seam provides a number of example applications demonstrating how to use the various features of Seam. This tutorial will guide you through a few of those examples to help you get started learning Seam. The Seam examples are located in the <filename>examples</filename> subdirectory of the Seam distribution. The registration example, which will be the first example we look at, is in the <filename>examples/registration</filename> directory."
+msgstr "Seam fornisce un ampio numero di applicazioni d'esempio per mostrare l'uso delle varie funzionalità di Seam. Questo tutorial ti guiderà attraverso alcuni di questi esempi per aiutarti nell'apprendimento di Seam. Gli esempi di Seam sono posizionati nella sottodirectory <filename>examples</filename> della distribuzione Seam. L'esempio di registrazione, che è il primo esempio che vediamo, si trova nella directory <filename>examples/registration</filename>."
#. Tag: para
#: Tutorial.xml:15
@@ -53,41 +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."
-msgstr ""
-"La directory <filename>view</filename> contiene i file relativi alla vista "
-"come template di pagine web, immagini e fogli di stile."
+msgid "The <filename>view</filename> directory contains view-related files such as web page templates, images and stylesheets."
+msgstr "La directory <filename>view</filename> contiene i file relativi alla vista come template di pagine web, immagini e fogli di stile."
#. Tag: para
#: Tutorial.xml:25
#, no-c-format
-msgid ""
-"The <filename>resources</filename> directory contains deployment descriptors "
-"and other configuration files."
-msgstr ""
-"La directory <filename>resources</filename> contiene i descrittori per il "
-"deploy ed altri file di configurazione."
+msgid "The <filename>resources</filename> directory contains deployment descriptors and other configuration files."
+msgstr "La directory <filename>resources</filename> contiene i descrittori per il deploy ed altri file di configurazione."
#. Tag: para
#: Tutorial.xml:30
#, no-c-format
-msgid ""
-"The <filename>src</filename> directory contains the application source code."
-msgstr ""
-"La directory <filename>src</filename> contiene il codice sorgente "
-"dell'applicazione."
+msgid "The <filename>src</filename> directory contains the application source code."
+msgstr "La directory <filename>src</filename> contiene il codice sorgente dell'applicazione."
#. Tag: para
#: Tutorial.xml:35
#, no-c-format
-msgid ""
-"The example applications run both on JBoss AS and Tomcat with no additional "
-"configuration. The following sections will explain the procedure in both "
-"cases. Note that all the examples are built and run from the Ant "
-"<filename>build.xml</filename>, so you'll need a recent version of Ant "
-"installed before you get started."
+msgid "The example applications run both on JBoss AS and Tomcat with no additional configuration. The following sections will explain the procedure in both cases. Note that all the examples are built and run from the Ant <filename>build.xml</filename>, so you'll need a recent version of Ant installed before you get started."
msgstr ""
#. Tag: title
@@ -99,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
@@ -145,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
@@ -194,49 +124,38 @@
#. 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
#: Tutorial.xml:112
#, no-c-format
msgid "Your first Seam application: the registration example"
-msgstr ""
+msgstr "La prima applicazione di Seam: esempio di registrazione"
#. 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."
-msgstr ""
+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 "L'esempio di registrazione è una semplice applicazione per consentire all'utente di memorizzare nel database il proprio username, il nome vero e la password. L'esempio non vuole mostrare tutte le funzionalità di Seam. Comunque mostra l'uso di un EJB3 session bean come JSF action listener e la configurazione base di Seam."
#. Tag: para
#: Tutorial.xml:119
#, no-c-format
-msgid ""
-"We'll go slowly, since we realize you might not yet be familiar with EJB 3.0."
+msgid "We'll go slowly, since we realize you might not yet be familiar with EJB 3.0."
msgstr ""
#. Tag: para
#: Tutorial.xml:121
#, no-c-format
-msgid ""
-"The start page displays a very basic form with three input fields. Try "
-"filling them in and then submitting the form. This will save a user object "
-"in the database."
+msgid "The start page displays a very basic form with three input fields. Try filling them in and then submitting the form. This will save a user object in the database."
msgstr ""
#. Tag: title
-#: Tutorial.xml:134 Tutorial.xml:533 Tutorial.xml:722 Tutorial.xml:955
+#: Tutorial.xml:134
+#: Tutorial.xml:533
+#: Tutorial.xml:722
+#: Tutorial.xml:955
#, no-c-format
msgid "Understanding the code"
msgstr "Capire il codice"
@@ -244,26 +163,19 @@
#. 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
#: Tutorial.xml:141
#, no-c-format
msgid "The entity bean: <literal>User.java</literal>"
-msgstr ""
+msgstr "Entity bean: <literal>User.java</literal>"
#. 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
@@ -391,135 +303,85 @@
#. Tag: para
#: Tutorial.xml:163
#, no-c-format
-msgid ""
-"The EJB3 standard <literal>@Entity</literal> annotation indicates that the "
-"<literal>User</literal> class is an entity bean."
+msgid "The EJB3 standard <literal>@Entity</literal> annotation indicates that the <literal>User</literal> class is an entity bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:167
#, no-c-format
-msgid ""
-"A Seam component needs a <emphasis>component name</emphasis> specified by "
-"the <link linkend=\"name-annotation\"> <literal>@Name</literal> </link> "
-"annotation. This name must be unique within the Seam application. When JSF "
-"asks Seam to resolve a context variable with a name that is the same as a "
-"Seam component name, and the context variable is currently undefined (null), "
-"Seam will instantiate that component, and bind the new instance to the "
-"context variable. In this case, Seam will instantiate a <literal>User</"
-"literal> the first time JSF encounters a variable named <literal>user</"
-"literal>."
+msgid "A Seam component needs a <emphasis>component name</emphasis> specified by the <link linkend=\"name-annotation\"> <literal>@Name</literal> </link> annotation. This name must be unique within the Seam application. When JSF asks Seam to resolve a context variable with a name that is the same as a Seam component name, and the context variable is currently undefined (null), Seam will instantiate that component, and bind the new instance to the context variable. In this case, Seam will instantiate a <literal>User</literal> the first time JSF encounters a variable named <literal>user</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:178
#, no-c-format
-msgid ""
-"Whenever Seam instantiates a component, it binds the new instance to a "
-"context variable in the component's <emphasis>default context</emphasis>. "
-"The default context is specified using the <link linkend=\"scope-annotation"
-"\"> <literal>@Scope</literal> </link> annotation. The <literal>User</"
-"literal> bean is a session scoped component."
+msgid "Whenever Seam instantiates a component, it binds the new instance to a context variable in the component's <emphasis>default context</emphasis>. The default context is specified using the <link linkend=\"scope-annotation\"> <literal>@Scope</literal> </link> annotation. The <literal>User</literal> bean is a session scoped component."
msgstr ""
#. Tag: para
#: Tutorial.xml:186
#, no-c-format
-msgid ""
-"The EJB standard <literal>@Table</literal> annotation indicates that the "
-"<literal>User</literal> class is mapped to the <literal>users</literal> "
-"table."
+msgid "The EJB standard <literal>@Table</literal> annotation indicates that the <literal>User</literal> class is mapped to the <literal>users</literal> table."
msgstr ""
#. Tag: para
#: Tutorial.xml:191
#, no-c-format
-msgid ""
-"<literal>name</literal>, <literal>password</literal> and <literal>username</"
-"literal> are the persistent attributes of the entity bean. All of our "
-"persistent attributes define accessor methods. These are needed when this "
-"component is used by JSF in the render response and update model values "
-"phases."
+msgid "<literal>name</literal>, <literal>password</literal> and <literal>username</literal> are the persistent attributes of the entity bean. All of our persistent attributes define accessor methods. These are needed when this component is used by JSF in the render response and update model values phases."
msgstr ""
#. Tag: para
#: Tutorial.xml:198
#, no-c-format
-msgid ""
-"An empty constructor is both required by both the EJB specification and by "
-"Seam."
+msgid "An empty constructor is both required by both the EJB specification and by Seam."
msgstr "Un costruttore vuoto è richiesto sia dalla specifica EJB sia da Seam."
#. Tag: para
#: Tutorial.xml:202
#, no-c-format
-msgid ""
-"The <literal>@NotNull</literal> and <literal>@Length</literal> annotations "
-"are part of the Hibernate Validator framework. Seam integrates Hibernate "
-"Validator and lets you use it for data validation (even if you are not using "
-"Hibernate for persistence)."
+msgid "The <literal>@NotNull</literal> and <literal>@Length</literal> annotations are part of the Hibernate Validator framework. Seam integrates Hibernate Validator and lets you use it for data validation (even if you are not using Hibernate for persistence)."
msgstr ""
#. Tag: para
#: Tutorial.xml:208
#, no-c-format
-msgid ""
-"The EJB standard <literal>@Id</literal> annotation indicates the primary key "
-"attribute of the entity bean."
+msgid "The EJB standard <literal>@Id</literal> annotation indicates the primary key attribute of the entity bean."
msgstr ""
#. Tag: para
#: Tutorial.xml:214
#, no-c-format
-msgid ""
-"The most important things to notice in this example are the <literal>@Name</"
-"literal> and <literal>@Scope</literal> annotations. These annotations "
-"establish that this class is a Seam component."
+msgid "The most important things to notice in this example are the <literal>@Name</literal> and <literal>@Scope</literal> annotations. These annotations establish that this class is a Seam component."
msgstr ""
#. Tag: para
#: Tutorial.xml:216
#, no-c-format
-msgid ""
-"We'll see below that the properties of our <literal>User</literal> class are "
-"bound directly to JSF components and are populated by JSF during the update "
-"model values phase. We don't need any tedious glue code to copy data back "
-"and forth between the JSP pages and the entity bean domain model."
+msgid "We'll see below that the properties of our <literal>User</literal> class are bound directly to JSF components and are populated by JSF during the update model values phase. We don't need any tedious glue code to copy data back and forth between the JSP pages and the entity bean domain model."
msgstr ""
#. Tag: para
#: Tutorial.xml:220
#, no-c-format
-msgid ""
-"However, entity beans shouldn't do transaction management or database "
-"access. So we can't use this component as a JSF action listener. For that we "
-"need a session bean."
+msgid "However, entity beans shouldn't do transaction management or database access. So we can't use this component as a JSF action listener. For that we need a session bean."
msgstr ""
#. Tag: title
#: Tutorial.xml:226
#, no-c-format
-msgid ""
-"The stateless session bean class: <literal>RegisterAction.java</literal>"
-msgstr ""
-"Classe del bean di sessione stateless: <literal>RegisterAction.java</literal>"
+msgid "The stateless session bean class: <literal>RegisterAction.java</literal>"
+msgstr "Classe del bean di sessione stateless: <literal>RegisterAction.java</literal>"
#. Tag: para
#: Tutorial.xml:228
#, no-c-format
-msgid ""
-"Most Seam application use session beans as JSF action listeners (you can use "
-"JavaBeans instead if you like)."
+msgid "Most Seam application use session beans as JSF action listeners (you can use JavaBeans instead if you like)."
msgstr ""
#. Tag: para
#: Tutorial.xml:230
#, no-c-format
-msgid ""
-"We have exactly one JSF action in our application, and one session bean "
-"method attached to it. In this case, we'll use a stateless session bean, "
-"since all the state associated with our action is held by the <literal>User</"
-"literal> bean."
+msgid "We have exactly one JSF action in our application, and one session bean method attached to it. In this case, we'll use a stateless session bean, since all the state associated with our action is held by the <literal>User</literal> bean."
msgstr ""
#. Tag: para
@@ -565,8 +427,7 @@
" }\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"
@@ -600,8 +461,7 @@
" }\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"
@@ -611,136 +471,86 @@
#. 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
#: Tutorial.xml:333
#, no-c-format
msgid "The session bean local interface: <literal>Register.java</literal>"
-msgstr ""
+msgstr "Interfaccia locale del session bean: <literal>Register.java</literal>"
#. Tag: para
#: Tutorial.xml:335
#, no-c-format
msgid "Naturally, our session bean needs a local interface."
-msgstr ""
+msgstr "Certamente il nostro session bean richiede un'interfaccia locale."
#. Tag: title
#: Tutorial.xml:337
@@ -768,23 +578,18 @@
#: Tutorial.xml:341
#, no-c-format
msgid "That's the end of the Java code. Now we'll look at the view."
-msgstr ""
+msgstr "Questa è la fine del codice Java. Vediamo ora la vista."
#. Tag: title
#: Tutorial.xml:346
#, no-c-format
-msgid ""
-"The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</"
-"literal>"
-msgstr ""
+msgid "The view: <literal>register.xhtml</literal> and <literal>registered.xhtml</literal>"
+msgstr "La vista: <literal>register.xhtml</literal> e <literal>registered.xhtml</literal>"
#. 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
@@ -813,17 +618,13 @@
" <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"
@@ -846,17 +647,13 @@
" <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"
@@ -866,11 +663,7 @@
#. 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
@@ -894,8 +687,7 @@
" </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"
@@ -913,8 +705,7 @@
" </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"
@@ -924,53 +715,31 @@
#. 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
@@ -1014,13 +783,7 @@
#. 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
@@ -1032,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
@@ -1056,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"
@@ -1091,8 +851,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"
@@ -1120,25 +879,19 @@
#. 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
#: Tutorial.xml:420
#, no-c-format
msgid "The JSF configration: <literal>faces-config.xml</literal>"
-msgstr ""
+msgstr "Configurazione JSF: <literal>faces-config.xml</literal>"
#. 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
@@ -1182,46 +935,31 @@
#. Tag: para
#: Tutorial.xml:432
#, no-c-format
-msgid ""
-"Note that we don't need any JSF managed bean declarations! Our managed beans "
-"are annotated Seam components. In Seam applications, the <literal>faces-"
-"config.xml</literal> is used much less often than in plain JSF. Here, we are "
-"simply using it to enable Facelets as the view handler instead of JSP."
+msgid "Note that we don't need any JSF managed bean declarations! Our managed beans are annotated Seam components. In Seam applications, the <literal>faces-config.xml</literal> is used much less often than in plain JSF. Here, we are simply using it to enable Facelets as the view handler instead of JSP."
msgstr ""
#. Tag: para
#: Tutorial.xml:437
#, no-c-format
-msgid ""
-"In fact, once you have all the basic descriptors set up, the <emphasis>only</"
-"emphasis> XML you need to write as you add new functionality to a Seam "
-"application is orchestration: navigation rules or jBPM process definitions. "
-"Seam's stand is that <emphasis>process flow</emphasis> and "
-"<emphasis>configuration data</emphasis> are the only things that truly "
-"belong in XML."
+msgid "In fact, once you have all the basic descriptors set up, the <emphasis>only</emphasis> XML you need to write as you add new functionality to a Seam application is orchestration: navigation rules or jBPM process definitions. Seam's stand is that <emphasis>process flow</emphasis> and <emphasis>configuration data</emphasis> are the only things that truly belong in XML."
msgstr ""
#. Tag: para
#: Tutorial.xml:442
#, no-c-format
-msgid ""
-"In this simple example, we don't even need a navigation rule, since we "
-"decided to embed the view id in our action code."
+msgid "In this simple example, we don't even need a navigation rule, since we decided to embed the view id in our action code."
msgstr ""
#. Tag: title
#: Tutorial.xml:448
#, no-c-format
msgid "The EJB deployment descriptor: <literal>ejb-jar.xml</literal>"
-msgstr ""
+msgstr "Descrittore di deploy EJB: <literal>ejb-jar.xml</literal>"
#. 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
@@ -1238,16 +976,14 @@
" \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"
@@ -1263,16 +999,14 @@
" \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"
@@ -1281,17 +1015,13 @@
#. 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
@@ -1310,8 +1040,7 @@
" <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"
@@ -1329,8 +1058,7 @@
" <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"
@@ -1340,21 +1068,19 @@
#: Tutorial.xml:469
#, no-c-format
msgid "The EAR deployment descriptor: <literal>application.xml</literal>"
-msgstr ""
+msgstr "Descrittore di deploy EAR: <literal>application.xml</literal>"
#. 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
#: Tutorial.xml:473
#, no-c-format
msgid "registration application"
-msgstr ""
+msgstr "applicazione di registrazione"
#. Tag: programlisting
#: Tutorial.xml:474
@@ -1419,21 +1145,20 @@
#. Tag: para
#: Tutorial.xml:477
#, no-c-format
-msgid ""
-"This deployment descriptor links modules in the enterprise archive and binds "
-"the web application to the context root <literal>/seam-registration</"
-"literal>."
+msgid "This deployment descriptor links modules in the enterprise archive and binds the web application to the context root <literal>/seam-registration</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:480
#, no-c-format
-msgid ""
-"We've now seen <emphasis>all</emphasis> the files in the entire application!"
+msgid "We've now seen <emphasis>all</emphasis> the files in the entire application!"
msgstr ""
#. Tag: title
-#: Tutorial.xml:486 Tutorial.xml:673 Tutorial.xml:887 Tutorial.xml:1070
+#: Tutorial.xml:486
+#: Tutorial.xml:673
+#: Tutorial.xml:887
+#: Tutorial.xml:1070
#, no-c-format
msgid "How it works"
msgstr "Come funziona"
@@ -1441,104 +1166,67 @@
#. 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
#: Tutorial.xml:516
#, no-c-format
msgid "Clickable lists in Seam: the messages example"
-msgstr ""
+msgstr "Liste cliccabili in Seam: esempio di messaggi"
#. 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
#: Tutorial.xml:538
#, no-c-format
msgid "The entity bean: <literal>Message.java</literal>"
-msgstr ""
+msgstr "Entity bean: <literal>Message.java</literal>"
#. 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
@@ -1688,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
@@ -1745,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"
@@ -1785,8 +1458,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"
@@ -1810,99 +1482,61 @@
#. 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 every time a row of the clickable list is selected, "
-"the <literal>Message</literal> is injected to the attribute of the stateful "
-"bean, and the subsequently <emphasis>outjected</emphasis> to the event "
-"context variable named <literal>message</literal>."
+msgid "The <literal>@Out</literal> annotation then exposes the selected value directly to the page. So every time a row of the clickable list is selected, the <literal>Message</literal> is injected to the attribute of the stateful bean, and the subsequently <emphasis>outjected</emphasis> to the event context variable named <literal>message</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:602
#, no-c-format
-msgid ""
-"This stateful bean has an EJB3 <emphasis>extended persistence context</"
-"emphasis>. The messages retrieved in the query remain in the managed state "
-"as long as the bean exists, so any subsequent method calls to the stateful "
-"bean can update them without needing to make any explicit call to the "
-"<literal>EntityManager</literal>."
+msgid "This stateful bean has an EJB3 <emphasis>extended persistence context</emphasis>. The messages retrieved in the query remain in the managed state as long as the bean exists, so any subsequent method calls to the stateful bean can update them without needing to make any explicit call to the <literal>EntityManager</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:608
#, no-c-format
-msgid ""
-"The first time we navigate to the JSP page, there will be no value in the "
-"<literal>messageList</literal> context variable. The <literal>@Factory</"
-"literal> annotation tells Seam to create an instance of "
-"<literal>MessageManagerBean</literal> and invoke the <literal>findMessages()"
-"</literal> method to initialize the value. We call <literal>findMessages()</"
-"literal> a <emphasis>factory method</emphasis> for <literal>messages</"
-"literal>."
+msgid "The first time we navigate to the JSP page, there will be no value in the <literal>messageList</literal> context variable. The <literal>@Factory</literal> annotation tells Seam to create an instance of <literal>MessageManagerBean</literal> and invoke the <literal>findMessages()</literal> method to initialize the value. We call <literal>findMessages()</literal> a <emphasis>factory method</emphasis> for <literal>messages</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:616
#, no-c-format
-msgid ""
-"The <literal>select()</literal> action listener method marks the selected "
-"<literal>Message</literal> as read, and updates it in the database."
+msgid "The <literal>select()</literal> action listener method marks the selected <literal>Message</literal> as read, and updates it in the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:620
#, no-c-format
-msgid ""
-"The <literal>delete()</literal> action listener method removes the selected "
-"<literal>Message</literal> from the database."
+msgid "The <literal>delete()</literal> action listener method removes the selected <literal>Message</literal> from the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:624
#, no-c-format
-msgid ""
-"All stateful session bean Seam components <emphasis>must</emphasis> have a "
-"method with no parameters marked <literal>@Remove</literal> that Seam uses "
-"to remove the stateful bean when the Seam context ends, and clean up any "
-"server-side state."
+msgid "All stateful session bean Seam components <emphasis>must</emphasis> have a method with no parameters marked <literal>@Remove</literal> that Seam uses to remove the stateful bean when the Seam context ends, and clean up any server-side state."
msgstr ""
#. Tag: para
#: Tutorial.xml:633
#, no-c-format
-msgid ""
-"Note that this is a session-scoped Seam component. It is associated with the "
-"user login session, and all requests from a login session share the same "
-"instance of the component. (In Seam applications, we usually use session-"
-"scoped components sparingly.)"
+msgid "Note that this is a session-scoped Seam component. It is associated with the user login session, and all requests from a login session share the same instance of the component. (In Seam applications, we usually use session-scoped components sparingly.)"
msgstr ""
#. Tag: title
#: Tutorial.xml:640
#, no-c-format
-msgid ""
-"The session bean local interface: <literal>MessageManager.java</literal>"
+msgid "The session bean local interface: <literal>MessageManager.java</literal>"
msgstr ""
#. Tag: para
@@ -1948,26 +1582,19 @@
#. 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
#: Tutorial.xml:658
#, no-c-format
msgid "The view: <literal>messages.jsp</literal>"
-msgstr ""
+msgstr "La vista: <literal>messages.jsp</literal>"
#. 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
@@ -1998,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"
@@ -2047,28 +1670,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"
@@ -2081,73 +1700,37 @@
#. 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
#: Tutorial.xml:706
#, no-c-format
msgid "Seam and jBPM: the todo list example"
-msgstr ""
+msgstr "Seam e jBPM: esempio di lista todo"
#. 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
@@ -2197,77 +1780,49 @@
#. 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
@@ -2333,9 +1888,7 @@
#. 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
@@ -2395,12 +1948,8 @@
#. Tag: para
#: Tutorial.xml:807
#, no-c-format
-msgid ""
-"The second JavaBean is responsible for starting business process instances, "
-"and ending tasks."
-msgstr ""
-"Il secondo JavaBean è responsabile per l'avvio delle istanze del processo di "
-"business e della fine dei task."
+msgid "The second JavaBean is responsible for starting business process instances, and ending tasks."
+msgstr "Il secondo JavaBean è responsabile per l'avvio delle istanze del processo di business e della fine dei task."
#. Tag: title
#: Tutorial.xml:811
@@ -2461,36 +2010,25 @@
#. 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
@@ -2500,7 +2038,8 @@
msgstr ""
#. Tag: title
-#: Tutorial.xml:844 Tutorial.xml:854
+#: Tutorial.xml:844
+#: Tutorial.xml:854
#, no-c-format
msgid "todo.jsp"
msgstr "todo.jsp"
@@ -2535,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"
@@ -2544,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"
@@ -2572,8 +2107,7 @@
" <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"
@@ -2606,8 +2140,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"
@@ -2615,21 +2148,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"
@@ -2643,8 +2173,7 @@
" <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"
@@ -2660,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
@@ -2672,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"
@@ -2683,8 +2208,7 @@
msgstr ""
"<![CDATA[<h:form id=\"list\">\n"
" <div>\n"
-" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty "
-"taskInstanceList}\"/>\n"
+" <h:outputText value=\"There are no todo items.\" rendered=\"#{empty taskInstanceList}\"/>\n"
" <h:dataTable value=\"#{taskInstanceList}\" var=\"task\" \n"
" rendered=\"#{not empty taskInstanceList}\">\n"
" ...\n"
@@ -2695,12 +2219,7 @@
#. 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
@@ -2768,10 +2287,7 @@
#. 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
@@ -2779,39 +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"
+" <s:button value=\"Done\" action=\"#{todoList.done}\" taskInstance=\"#{task}\"/>\n"
"</h:column>]]>"
#. Tag: para
#: Tutorial.xml:870
#, no-c-format
-msgid ""
-"Note that this is using a Seam <literal><s:button></literal> JSF "
-"control from the <literal>seam-ui.jar</literal> package. This button is used "
-"to update the properties of the tasks. When the form is submitted, Seam and "
-"jBPM will make any changes to the tasks persistent. There is no need for any "
-"action listener method:"
+msgid "Note that this is using a Seam <literal><s:button></literal> JSF control from the <literal>seam-ui.jar</literal> package. This button is used to update the properties of the tasks. When the form is submitted, Seam and jBPM will make any changes to the tasks persistent. There is no need for any action listener method:"
msgstr ""
#. Tag: programlisting
#: Tutorial.xml:875
#, no-c-format
msgid "<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>"
-msgstr ""
-"<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>"
+msgstr "<![CDATA[<h:commandButton value=\"Update Items\" action=\"update\"/>]]>"
#. Tag: para
#: Tutorial.xml:877
#, no-c-format
-msgid ""
-"A second form on the page is used to create new items, by calling the action "
-"method annotated <literal>@CreateProcess</literal>."
+msgid "A second form on the page is used to create new items, by calling the action method annotated <literal>@CreateProcess</literal>."
msgstr ""
#. Tag: programlisting
@@ -2821,114 +2327,69 @@
"<![CDATA[<h:form id=\"new\">\n"
" <div>\n"
" <h:inputText value=\"#{todoList.description}\"/>\n"
-" <h:commandButton value=\"Create New Item\" action=\"#{todoList."
-"createTodo}\"/>\n"
+" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n"
" </div>\n"
"</h:form>]]>"
msgstr ""
"<![CDATA[<h:form id=\"new\">\n"
" <div>\n"
" <h:inputText value=\"#{todoList.description}\"/>\n"
-" <h:commandButton value=\"Create New Item\" action=\"#{todoList."
-"createTodo}\"/>\n"
+" <h:commandButton value=\"Create New Item\" action=\"#{todoList.createTodo}\"/>\n"
" </div>\n"
"</h:form>]]>"
#. Tag: para
#: Tutorial.xml:888
#, no-c-format
-msgid ""
-"After logging in, todo.jsp uses the <literal>taskInstanceList</literal> "
-"component to display a table of outstanding todo items for a the current "
-"user. Initially there are none. It also presents a form to enter a new "
-"entry. When the user types the todo item and hits the \"Create New Item\" "
-"button, <literal>#{todoList.createTodo}</literal> is called. This starts the "
-"todo process, as defined in <literal>todo.jpdl.xml</literal>."
+msgid "After logging in, todo.jsp uses the <literal>taskInstanceList</literal> component to display a table of outstanding todo items for a the current user. Initially there are none. It also presents a form to enter a new entry. When the user types the todo item and hits the \"Create New Item\" button, <literal>#{todoList.createTodo}</literal> is called. This starts the todo process, as defined in <literal>todo.jpdl.xml</literal>."
msgstr ""
#. Tag: para
#: Tutorial.xml:894
#, no-c-format
-msgid ""
-"The process instance is created, starting in the start state and immediately "
-"transition to the <literal>todo</literal> state, where a new task is "
-"created. The task description is set based on the user's input, which was "
-"saved to <literal>#{todoList.description}</literal>. Then, the task is "
-"assigned to the current user, which was stored in the seam actor component. "
-"Note that in this example, the process has no extra process state. All the "
-"state in this example is stored in the task definition. The process and task "
-"information is stored in the database at the end of the request."
+msgid "The process instance is created, starting in the start state and immediately transition to the <literal>todo</literal> state, where a new task is created. The task description is set based on the user's input, which was saved to <literal>#{todoList.description}</literal>. Then, the task is assigned to the current user, which was stored in the seam actor component. Note that in this example, the process has no extra process state. All the state in this example is stored in the task definition. The process and task information is stored in the database at the end of the request."
msgstr ""
#. Tag: para
#: Tutorial.xml:905
#, no-c-format
-msgid ""
-"When <literal>todo.jsp</literal> is redisplayed, <literal>taskInstanceList</"
-"literal> now finds the task that was just created. The task is shown in an "
-"<literal>h:dataTable</literal>. The internal state of the task is displayed "
-"in each column: <literal>#{task.description}</literal>, <literal>#{task."
-"priority}</literal>, <literal>#{task.dueDate}</literal>, etc... These fields "
-"can all be edited and saved back to the database."
+msgid "When <literal>todo.jsp</literal> is redisplayed, <literal>taskInstanceList</literal> now finds the task that was just created. The task is shown in an <literal>h:dataTable</literal>. The internal state of the task is displayed in each column: <literal>#{task.description}</literal>, <literal>#{task.priority}</literal>, <literal>#{task.dueDate}</literal>, etc... These fields can all be edited and saved back to the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:915
#, no-c-format
-msgid ""
-"Each todo item also has \"Done\" button, which calls <literal>#{todoList."
-"done}</literal>. The <literal>todoList</literal> component knows which task "
-"the button is for because each s:button specificies <literal>taskInstance=\"#"
-"{task}\"</literal>, referring to the task for that particular line of of the "
-"table. The <literal>@StartTast</literal> and <literal>@EndTask</literal> "
-"annotations cause seam to make the task active and immediately complete the "
-"task. The original process then transitions into the <literal>done</literal> "
-"state, according to the process definition, where it ends. The state of the "
-"task and process are both updated in the database."
+msgid "Each todo item also has \"Done\" button, which calls <literal>#{todoList.done}</literal>. The <literal>todoList</literal> component knows which task the button is for because each s:button specificies <literal>taskInstance=\"#{task}\"</literal>, referring to the task for that particular line of of the table. The <literal>@StartTast</literal> and <literal>@EndTask</literal> annotations cause seam to make the task active and immediately complete the task. The original process then transitions into the <literal>done</literal> state, according to the process definition, where it ends. The state of the task and process are both updated in the database."
msgstr ""
#. Tag: para
#: Tutorial.xml:926
#, no-c-format
-msgid ""
-"When <literal>todo.jsp</literal> is displayed again, the now-completed task "
-"is no longer displayed in the <literal>taskInstanceList</literal>, since "
-"that component only display active tasks for the user."
+msgid "When <literal>todo.jsp</literal> is displayed again, the now-completed task is no longer displayed in the <literal>taskInstanceList</literal>, since that component only display active tasks for the user."
msgstr ""
#. Tag: title
#: Tutorial.xml:934
#, no-c-format
msgid "Seam pageflow: the numberguess example"
-msgstr ""
+msgstr "Seam pageflow: esempio di indovina-numero"
#. 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
@@ -2945,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"
@@ -2958,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"
@@ -3002,15 +2460,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"
@@ -3020,11 +2476,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"
@@ -3036,30 +2490,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"
@@ -3079,64 +2525,43 @@
#. 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
@@ -3158,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"
@@ -3176,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"
@@ -3192,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"
@@ -3241,15 +2654,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"
@@ -3259,11 +2670,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"
@@ -3275,30 +2684,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"
@@ -3318,9 +2719,7 @@
#. 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
@@ -3346,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"
@@ -3357,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"
@@ -3377,8 +2773,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"
@@ -3388,10 +2783,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"
@@ -3404,9 +2797,7 @@
#. 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
@@ -3636,19 +3027,13 @@
#. 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
@@ -3664,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"
@@ -3677,8 +3061,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"
@@ -3690,89 +3073,43 @@
#. 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
@@ -3782,7 +3119,8 @@
msgstr ""
#. Tag: title
-#: Tutorial.xml:1128 Tutorial.xml:1506
+#: Tutorial.xml:1128
+#: Tutorial.xml:1506
#, no-c-format
msgid "Introduction"
msgstr "Introduzione"
@@ -3790,9 +3128,7 @@
#. 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
@@ -3858,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
@@ -3897,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
@@ -3976,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
@@ -3998,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
@@ -4158,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"
@@ -4185,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"
@@ -4234,8 +3462,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"
@@ -4261,8 +3488,7 @@
" public String getSearchPattern()\n"
" {\n"
" return searchString==null ? \n"
-" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + "
-"'%';\n"
+" \"%\" : '%' + searchString.toLowerCase().replace('*', '%') + '%';\n"
" }\n"
" \n"
" public String getSearchString()\n"
@@ -4282,50 +3508,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
@@ -4348,16 +3555,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"
@@ -4366,8 +3570,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"
@@ -4421,16 +3624,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"
@@ -4439,8 +3639,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"
@@ -4487,78 +3686,48 @@
#. Tag: para
#: Tutorial.xml:1367
#, no-c-format
-msgid ""
-"The RichFaces Ajax <literal><a:support></literal> tag allows a JSF "
-"action event listener to be called by asynchronous <literal>XMLHttpRequest</"
-"literal> when a JavaScript event like <literal>onkeyup</literal> occurs. "
-"Even better, the <literal>reRender</literal> attribute lets us render a "
-"fragment of the JSF page and perform a partial page update when the "
-"asynchronous response is received."
+msgid "The RichFaces Ajax <literal><a:support></literal> tag allows a JSF action event listener to be called by asynchronous <literal>XMLHttpRequest</literal> when a JavaScript event like <literal>onkeyup</literal> occurs. Even better, the <literal>reRender</literal> attribute lets us render a fragment of the JSF page and perform a partial page update when the asynchronous response is received."
msgstr ""
#. Tag: para
#: Tutorial.xml:1374
#, no-c-format
-msgid ""
-"The RichFaces Ajax <literal><a:status></literal> tag lets us display "
-"an animated image while we wait for asynchronous requests to return."
+msgid "The RichFaces Ajax <literal><a:status></literal> tag lets us display an animated image while we wait for asynchronous requests to return."
msgstr ""
#. Tag: para
#: Tutorial.xml:1378
#, no-c-format
-msgid ""
-"The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a "
-"region of the page which can be re-rendered by an asynchronous request."
+msgid "The RichFaces Ajax <literal><a:outputPanel></literal> tag defines a region of the page which can be re-rendered by an asynchronous request."
msgstr ""
#. Tag: para
#: Tutorial.xml:1382
#, no-c-format
-msgid ""
-"The Seam <literal><s:link></literal> tag lets us attach a JSF action "
-"listener to an ordinary (non-JavaScript) HTML link. The advantage of this "
-"over the standard JSF <literal><h:commandLink></literal> is that it "
-"preserves the operation of \"open in new window\" and \"open in new tab\". "
-"Also notice that we use a method binding with a parameter: <literal>#"
-"{hotelBooking.selectHotel(hot)}</literal>. This is not possible in the "
-"standard Unified EL, but Seam provides an extension to the EL that lets you "
-"use parameters on any method binding expression."
+msgid "The Seam <literal><s:link></literal> tag lets us attach a JSF action listener to an ordinary (non-JavaScript) HTML link. The advantage of this over the standard JSF <literal><h:commandLink></literal> is that it preserves the operation of \"open in new window\" and \"open in new tab\". Also notice that we use a method binding with a parameter: <literal>#{hotelBooking.selectHotel(hot)}</literal>. This is not possible in the standard Unified EL, but Seam provides an extension to the EL that lets you use parameters on any method binding expression."
msgstr ""
#. Tag: para
#: Tutorial.xml:1389
#, no-c-format
-msgid ""
-"If you're wondering how navigation occurs, you can find all the rules in "
-"<literal>WEB-INF/pages.xml</literal>; this is discussed in <xref linkend="
-"\"events.pageaction.navigation\"/>."
+msgid "If you're wondering how navigation occurs, you can find all the rules in <literal>WEB-INF/pages.xml</literal>; this is discussed in <xref linkend=\"events.pageaction.navigation\"/>."
msgstr ""
#. Tag: para
#: Tutorial.xml:1398
#, no-c-format
-msgid ""
-"This page displays the search results dynamically as we type, and lets us "
-"choose a hotel and pass it to the <literal>selectHotel()</literal> method of "
-"the <literal>HotelBookingAction</literal>, which is where the "
-"<emphasis>really</emphasis> interesting stuff is going to happen."
+msgid "This page displays the search results dynamically as we type, and lets us choose a hotel and pass it to the <literal>selectHotel()</literal> method of the <literal>HotelBookingAction</literal>, which is where the <emphasis>really</emphasis> interesting stuff is going to happen."
msgstr ""
#. Tag: para
#: Tutorial.xml:1403
#, no-c-format
-msgid ""
-"Now let's see how the booking example application uses a conversation-scoped "
-"stateful session bean to achieve a natural cache of persistent data related "
-"to the conversation. The following code example is pretty long. But if you "
-"think of it as a list of scripted actions that implement the various steps "
-"of the conversation, it's understandable. Read the class from top to bottom, "
-"as if it were a story."
+msgid "Now let's see how the booking example application uses a conversation-scoped stateful session bean to achieve a natural cache of persistent data related to the conversation. The following code example is pretty long. But if you think of it as a list of scripted actions that implement the various steps of the conversation, it's understandable. Read the class from top to bottom, as if it were a story."
msgstr ""
#. Tag: title
-#: Tutorial.xml:1408 Tutorial.xml:1633
+#: Tutorial.xml:1408
+#: Tutorial.xml:1633
#, no-c-format
msgid "HotelBookingAction.java"
msgstr "HotelBookingAction.java"
@@ -4618,16 +3787,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"
@@ -4645,8 +3811,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"
@@ -4710,16 +3875,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"
@@ -4737,8 +3899,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"
@@ -4754,78 +3915,43 @@
#. 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
@@ -4837,11 +3963,7 @@
#. 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
@@ -4853,11 +3975,7 @@
#. 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
@@ -4869,58 +3987,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
@@ -4932,10 +4023,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
@@ -4974,8 +4062,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"
@@ -4998,8 +4085,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"
@@ -5014,8 +4100,7 @@
" return \"cancel\";\n"
" }\n"
"\n"
-" @Destroy "
-"@Remove \n"
+" @Destroy @Remove \n"
" public void destroy() {} \n"
"}\n"
"]]>"
@@ -5046,8 +4131,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"
@@ -5070,8 +4154,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"
@@ -5086,8 +4169,7 @@
" return \"cancel\";\n"
" }\n"
"\n"
-" @Destroy "
-"@Remove \n"
+" @Destroy @Remove \n"
" public void destroy() {} \n"
"}\n"
"]]>"
@@ -5095,58 +4177,31 @@
#. 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
@@ -5168,17 +4223,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"
@@ -5195,23 +4246,20 @@
" <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"
@@ -5227,17 +4275,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"
@@ -5254,23 +4298,20 @@
" <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"
@@ -5280,43 +4321,25 @@
#. 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
@@ -5363,12 +4386,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"
@@ -5378,14 +4398,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"
@@ -5407,14 +4424,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"
@@ -5467,12 +4482,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"
@@ -5482,14 +4494,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"
@@ -5511,14 +4520,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"
@@ -5534,45 +4541,25 @@
#. 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
@@ -5584,21 +4571,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 "Esempio di Negozio DVD"
@@ -5606,18 +4590,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
@@ -5629,16 +4608,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
@@ -5650,10 +4620,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
@@ -5665,27 +4632,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"
@@ -5693,12 +4655,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"
@@ -5706,18 +4666,15 @@
" </h:column>\n"
"</h:dataTable>]]>"
msgstr ""
-"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" "
-"rows=\"3\">\n"
+"<![CDATA[<h:dataTable value=\"#{blog.recentBlogEntries}\" var=\"blogEntry\" rows=\"3\">\n"
" <h:column>\n"
" <div class=\"blogEntry\">\n"
" <h3>#{blogEntry.title}</h3>\n"
" <div>\n"
-" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry."
-"body : blogEntry.excerpt}\"/>\n"
+" <s:formattedText value=\"#{blogEntry.excerpt==null ? blogEntry.body : blogEntry.excerpt}\"/>\n"
" </div>\n"
" <p>\n"
-" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}"
-"\" propagation=\"none\"\n"
+" <s:link view=\"/entry.xhtml\" rendered=\"#{blogEntry.excerpt!=null}\" propagation=\"none\"\n"
" value=\"Read more...\">\n"
" <f:param name=\"blogEntryId\" value=\"#{blogEntry.id}\"/>\n"
" </s:link>\n"
@@ -5725,12 +4682,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"
@@ -5741,13 +4696,7 @@
#. 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
@@ -5765,8 +4714,7 @@
" @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"
@@ -5784,8 +4732,7 @@
" @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"
@@ -5795,30 +4742,19 @@
#. 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
@@ -5830,11 +4766,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
@@ -5858,12 +4790,7 @@
#. 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
@@ -5913,13 +4840,7 @@
#. 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
@@ -5931,8 +4852,7 @@
" <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"
@@ -5943,8 +4863,7 @@
" <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"
@@ -5953,48 +4872,26 @@
#. 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
#: Tutorial.xml:1858
#, no-c-format
msgid "<web:rewrite-filter view-mapping="/seam/*" />"
-msgstr ""
+msgstr "<web:rewrite-filter view-mapping="/seam/*" />"
#. Tag: para
#: Tutorial.xml:1860
@@ -6009,14 +4906,12 @@
"<![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"
@@ -6025,14 +4920,12 @@
"<![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"
@@ -6041,9 +4934,7 @@
#. 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
@@ -6064,8 +4955,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"
@@ -6073,8 +4963,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"
@@ -6086,8 +4975,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"
@@ -6120,8 +5008,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"
@@ -6129,8 +5016,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"
@@ -6142,8 +5028,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"
@@ -6171,20 +5056,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
@@ -6227,7 +5105,7 @@
#: Tutorial.xml:1887
#, no-c-format
msgid "Page actions are also declared in <literal>pages.xml</literal>:"
-msgstr ""
+msgstr "Le azione nella pagina vengono anche dichiarate in <literal>pages.xml</literal>:"
#. Tag: programlisting
#: Tutorial.xml:1889
@@ -6302,23 +5180,13 @@
#. 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
@@ -6333,8 +5201,7 @@
" <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>]]>"
@@ -6347,8 +5214,7 @@
" <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>]]>"
@@ -6356,12 +5222,8 @@
#. 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:"
-msgstr ""
+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 "Se l'entry del blog non viene trovata nel database, viene lanciata l'eccezione <literal>EntryNotFoundException</literal>. Vogliamo che quest'eccezione venga evidenziata come errore 404, non 505, e quindi annotiamo la classe dell'eccezione:"
#. Tag: programlisting
#: Tutorial.xml:1911
@@ -6390,10 +5252,8 @@
#. Tag: para
#: Tutorial.xml:1914
#, no-c-format
-msgid ""
-"An alternative implementation of the example does not use the parameter in "
-"the method binding:"
-msgstr ""
+msgid "An alternative implementation of the example does not use the parameter in the method binding:"
+msgstr "Un'implementazione alternativa dell'esempio non utilizza il parametro nel method binding:"
#. Tag: programlisting
#: Tutorial.xml:1916
@@ -6467,10 +5327,6 @@
#. Tag: para
#: Tutorial.xml:1924
#, no-c-format
-msgid ""
-"The blog demo also demonstrates very simple password authentication, posting "
-"to the blog, page fragment caching and atom feed generation."
-msgstr ""
-"La demo del blog mostra anche una semplice autenticazione di password, un "
-"invio di un post al blog, un esempio di caching frammentato della pagina e "
-"la generazione di atom feed."
+msgid "The blog demo also demonstrates very simple password authentication, posting to the blog, page fragment caching and atom feed generation."
+msgstr "La demo del blog mostra anche una semplice autenticazione di password, un invio di un post al blog, un esempio di caching frammentato della pagina e la generazione di atom feed."
+
16 years
- 1
- 0
Seam SVN: r9774 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-13 16:11:22 -0500 (Sat, 13 Dec 2008)
New Revision: 9774
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 21:05:00 UTC (rev 9773)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 21:11:22 UTC (rev 9774)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-13 20:10+0100\n"
+"PO-Revision-Date: 2008-12-13 22:11+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -89,7 +89,7 @@
#: 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 "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."
+msgstr "Seam supporta le migliori soluzioni open source AJAX basate su JSF: JBoss RichFaces e ICEFaces. Queste soluzioni ti permettono di aggiungere funzionalità AJAX all'interfaccia utente senza il bisogno di scrivere codice JavaScript."
#. Tag: para
#: Preface.xml:86
@@ -114,7 +114,7 @@
#: Preface.xml:103
#, no-c-format
msgid "Optionally, Seam provides transparent business process management via jBPM. You won't believe how easy it is to implement complex workflows, collaboration and and task management using jBPM and Seam."
-msgstr "Opzionalmente Seam può fornire una gestione trasparente di processo di business tramire jBPM. Non ci crederai quanto è facile implementare workflow complessi, collaborazioni e gestione dei compiti utilizzando jBPM e Seam."
+msgstr "Opzionalmente Seam può fornire una gestione trasparente del processo di business tramite jBPM. Non ci crederai quanto è facile implementare dei workflow complessi, delle collaborazioni ed una gestione dei compiti utilizzando jBPM e Seam."
#. Tag: para
#: Preface.xml:108
@@ -162,13 +162,13 @@
#: 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."
-msgstr "La nozione di <emphasis>Inversione del Controllo</emphasis> o <emphasis>dependency injection</emphasis> esiste in entrambi JSF e EJB3, così come in numerosi così chiamati \"contenitori a peso leggero\" (lightweight containers). La maggior parte di questi contenitori predilige l'injection di componenti che implementano <emphasis>servizi stateless</emphasis>. Anche quando l'injection di componenti stateful è supportata (come in JSF), è virtualmente inutile per la gestione dello stato dell'applicazione poiché lo scope del componente stateful non può essere definita con sufficiente flessibilità e poiché i componenti appartenenti a scope più ampi potrebbero non essere iniettati nei componenti appartenenti a scope più ristretti."
+msgstr "La nozione di <emphasis>Inversione del Controllo</emphasis> o <emphasis>dependency injection</emphasis> esiste in entrambi JSF e EJB3, così come in numerosi così chiamati lightweight container. La maggior parte di questi container predilige l'injection di componenti che implementano <emphasis>servizi stateless</emphasis>. Anche quando l'injection di componenti stateful è supportata (come in JSF), è virtualmente inutile per la gestione dello stato dell'applicazione poiché lo scope del componente stateful non può essere definita con sufficiente flessibilità e poiché i componenti appartenenti a scope più ampi potrebbero non essere iniettati nei componenti appartenenti a scope più ristretti."
#. 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 "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. "
+msgstr "La <emphasis>Bijection</emphasis> differisce da IoC poiché è <emphasis>dinamica</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
@@ -180,7 +180,7 @@
#: 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!"
-msgstr "Le applicazioni Seam consentono all'utente di passare liberamente a più tab del browser, ciascuno associato ad una differente ed isolata conversazione. Le applicazioni possono addirittura avvantaggiarsi della <emphasis>gestione del workspace</emphasis>, consentendo all'utente di spostarsi fra le varie conversazioni (workspace) all'interno del singolo tab del browser. Seam fornisce non solo una corretta funzionalità multi-finestra, ma anche funzionalità multi-finestra in una singola finestra!"
+msgstr "Le applicazioni Seam consentono all'utente di passare liberamente a più tab del browser, ciascuno associato ad una conversazione differente ed isolata. Le applicazioni possono addirittura avvantaggiarsi della <emphasis>gestione del workspace</emphasis>, consentendo all'utente di spostarsi fra le varie conversazioni (workspace) all'interno del singolo tab del browser. Seam fornisce non solo una corretta funzionalità multi-finestra, ma anche funzionalità multi-finestra in una singola finestra!"
#. Tag: emphasis
#: Preface.xml:194
@@ -193,13 +193,13 @@
#: 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."
-msgstr "Tradizionalmente la comunità Java è restata in uno stato di profonda confusione su quali tipologie di meta-informazione debbano essere considerate configurazione. J2EE ed i più noti contenitori \"a peso leggero\" (lightweight container) hanno entrambi fornito descrittori per il deploy basati su XML per cose che sono configurabili tra differenti deploy del sistema e per altri tipi di cose o dichiarazioni che non sono facilmente esprimibili in Java. Le annotazioni Java 5 hanno cambiato tutto questo."
+msgstr "Tradizionalmente la comunità Java è restata in uno stato di profonda confusione su quali tipologie di meta-informazione debbano essere considerate configurazione. J2EE ed i più noti lightweight container hanno entrambi fornito descrittori per il deploy basati su XML per cose che sono configurabili tra differenti deploy del sistema e per altri tipi di cose o dichiarazioni che non sono facilmente esprimibili in Java. Le annotazioni Java 5 hanno cambiato tutto questo."
#. 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)."
-msgstr "EJB 3.0 sceglie le annotazioni e la \"configurazione tramite eccezione\" come il miglior modo per fornire informazioni al contenitore in una forma dichiarativa. Sfortunatamente JSF è fortemente dipendente da file XML di configurazione molto lunghi. Seam estende le annotazioni fornite da EJB 3.0 con un set di annotazioni per la gestione dichiarativa dello stato e la demarcazione dichiarativa del contesto. Questo consente di eliminare le noiose dichiarazioni JSF dei bean gestiti e riduce l'XML richiesto alla sola informazione che veramente appartiene a XML (le regole di navigazione JSF)."
+msgstr "EJB 3.0 sceglie le annotazioni e la \"configurazione tramite eccezione\" come il miglior modo per fornire informazioni al container in una forma dichiarativa. Sfortunatamente JSF è fortemente dipendente da file XML di configurazione molto lunghi. Seam estende le annotazioni fornite da EJB 3.0 con un set di annotazioni per la gestione dichiarativa dello stato e la demarcazione dichiarativa del contesto. Questo consente di eliminare le noiose dichiarazioni JSF dei bean gestiti e riduce l'XML richiesto alla sola informazione che veramente appartiene a XML (le regole di navigazione JSF)."
#. Tag: emphasis
#: Preface.xml:217
16 years
- 1
- 0
Seam SVN: r9773 - in trunk/src/excel/org/jboss/seam/excel: jxl and 1 other directory.
by seam-commits＠lists.jboss.org
Author: nickarls
Date: 2008-12-13 16:05:00 -0500 (Sat, 13 Dec 2008)
New Revision: 9773
Modified:
trunk/src/excel/org/jboss/seam/excel/css/Parser.java
trunk/src/excel/org/jboss/seam/excel/css/PropertyBuilders.java
trunk/src/excel/org/jboss/seam/excel/jxl/JXLExcelWorkbook.java
Log:
JBSEAM-3839
Modified: trunk/src/excel/org/jboss/seam/excel/css/Parser.java
===================================================================
--- trunk/src/excel/org/jboss/seam/excel/css/Parser.java 2008-12-13 19:45:32 UTC (rev 9772)
+++ trunk/src/excel/org/jboss/seam/excel/css/Parser.java 2008-12-13 21:05:00 UTC (rev 9773)
@@ -345,20 +345,19 @@
String[] styles = trimArray(styleString.split(STYLES_SEPARATOR));
for (String style : styles)
{
- String[] styleParts = style.split(STYLE_NAME_VALUE_SEPARATOR);
- if (styleParts.length != 2)
- {
- log.warn("Style component #0 should be of form <key>#1<value>", style, STYLE_NAME_VALUE_SEPARATOR);
- continue;
+ int breakpoint = style.indexOf(STYLE_NAME_VALUE_SEPARATOR);
+ if (breakpoint < 0) {
+ log.warn("Style component #0 should be of form <key>#1<value>", style, STYLE_NAME_VALUE_SEPARATOR);
+ continue;
}
- String styleName = styleParts[0].toLowerCase().trim();
+ String styleName = style.substring(0, breakpoint).toLowerCase().trim();
if (!propertyBuilders.containsKey(styleName))
{
log.warn("No property builder (unknown style) for property #0", styleName);
continue;
}
PropertyBuilder propertyBuilder = propertyBuilders.get(styleName);
- String styleValue = styleParts[1];
+ String styleValue = style.substring(breakpoint + 1);
String[] styleValues = trimArray(styleValue.trim().split(STYLE_SHORTHAND_SEPARATOR));
styleMap.putAll(propertyBuilder.parseProperty(styleName, styleValues));
}
Modified: trunk/src/excel/org/jboss/seam/excel/css/PropertyBuilders.java
===================================================================
--- trunk/src/excel/org/jboss/seam/excel/css/PropertyBuilders.java 2008-12-13 19:45:32 UTC (rev 9772)
+++ trunk/src/excel/org/jboss/seam/excel/css/PropertyBuilders.java 2008-12-13 21:05:00 UTC (rev 9773)
@@ -404,7 +404,7 @@
{
}
- public static class FormatMask extends StringPropertyBuilder
+ public static class FormatMask extends MergingStringPropertyBuilder
{
}
Modified: trunk/src/excel/org/jboss/seam/excel/jxl/JXLExcelWorkbook.java
===================================================================
--- trunk/src/excel/org/jboss/seam/excel/jxl/JXLExcelWorkbook.java 2008-12-13 19:45:32 UTC (rev 9772)
+++ trunk/src/excel/org/jboss/seam/excel/jxl/JXLExcelWorkbook.java 2008-12-13 21:05:00 UTC (rev 9773)
@@ -494,7 +494,7 @@
if (!((UIComponent) item).isRendered()) {
return;
}
- if (item.getValue() == null) {
+ if (item.getValue() == null || "".equals(item.getValue())) {
if (item.getColumn() == null && item.getRow() == null) {
nextRow();
}
16 years
- 1
- 0
Seam SVN: r9772 - trunk/doc/Seam_Reference_Guide/it-IT.
by seam-commits＠lists.jboss.org
Author: nico.ben
Date: 2008-12-13 14:45:32 -0500 (Sat, 13 Dec 2008)
New Revision: 9772
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po
trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
trunk/doc/Seam_Reference_Guide/it-IT/Testing.po
trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Author_Group.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,7 +6,7 @@
"Project-Id-Version: seam 2_0\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-13 17:58+0000\n"
-"PO-Revision-Date: 2008-11-23 17:06+0100\n"
+"PO-Revision-Date: 2008-12-13 16:40+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -141,19 +141,19 @@
#: Author_Group.xml:88
#, no-c-format
msgid "<firstname>Steve</firstname> <surname>Ebersole</surname>"
-msgstr ""
+msgstr "<firstname>Steve</firstname> <surname>Ebersole</surname>"
#. Tag: othercredit
#: Author_Group.xml:92
#, no-c-format
msgid "<firstname>Michael</firstname> <surname>Courcy</surname>"
-msgstr ""
+msgstr "<firstname>Michael</firstname> <surname>Courcy</surname>"
#. Tag: shortaffil
#: Author_Group.xml:96
#, no-c-format
msgid "French Translation"
-msgstr ""
+msgstr "Traduzione in francese"
#. Tag: editor
#: Author_Group.xml:99
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Book_Info.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -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-13 16:38+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,10 +17,11 @@
#: Book_Info.xml:5
#, no-c-format
msgid "Seam - Contextual Components"
-msgstr ""
+msgstr "Seam - Componenti Contestuali"
#. Tag: subtitle
#: Book_Info.xml:6
#, no-c-format
msgid "A Framework for Enterprise Java"
-msgstr ""
+msgstr "Un framework per Java Enterprise"
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-12 19:46+0100\n"
+"PO-Revision-Date: 2008-12-13 20:10+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -35,7 +35,7 @@
#: 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 "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."
+msgstr "Seam definisce un modello uniforme a componenti per tutte le business logic dell'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 del processo di business</emphasis> e il <emphasis>contesto conversazionale</emphasis>, che viene preservato lungo le diverse richieste web durante l'interazione dell'utente."
#. Tag: para
#: Preface.xml:25
@@ -47,7 +47,7 @@
#: 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."
-msgstr "A differenza dei componenti J2EE o del semplice Java EE, i componenti Seam possono <emphasis>simultaneamente</emphasis> accedere allo stato associato allarichiesta web e allo stato mantenuto nelle risorse transazionali (senza il bisogno di propagare manualmente lo stato della richiesta web attraverso i parametri). Si potrebbe obbiettare che la stratificazione dell'applicazione impostadalla vecchia piattaforma J2EE fosse una Cosa Buona. Bene, niente ti vieta di creare un'architettura a strati equivalente usando Seam— la differenza è che <emphasis>tu</emphasis> decidi l'architettura della tua applicazione e decidi quali sono i layer e come lavorano assieme"
+msgstr "A differenza dei componenti J2EE o del semplice Java EE, i componenti Seam possono <emphasis>simultaneamente</emphasis> accedere allo stato associato alla richiesta web e allo stato mantenuto nelle risorse transazionali (senza il bisogno di propagare manualmente lo stato della richiesta web attraverso i parametri). Si potrebbe obbiettare che la stratificazione dell'applicazione impostadalla vecchia piattaforma J2EE fosse una Cosa Buona. Bene, niente ti vieta di creare un'architettura a strati equivalente usando Seam— la differenza è che <emphasis>tu</emphasis> decidi l'architettura della tua applicazione e decidi quali sono i layer e come lavorano assieme"
#. Tag: emphasis
#: Preface.xml:45
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Testing.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Testing.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:39+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-13 20:13+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,17 +17,12 @@
#: Testing.xml:2
#, no-c-format
msgid "Testing Seam applications"
-msgstr ""
+msgstr "Test delle applicazioni Seam"
#. Tag: para
#: Testing.xml:3
#, no-c-format
-msgid ""
-"Most Seam applications will need at least two kinds of automated tests: "
-"<emphasis>unit tests</emphasis>, which test a particular Seam component in "
-"isolation, and scripted <emphasis>integration tests</emphasis> which "
-"exercise all Java layers of the application (that is, everything except the "
-"view pages)."
+msgid "Most Seam applications will need at least two kinds of automated tests: <emphasis>unit tests</emphasis>, which test a particular Seam component in isolation, and scripted <emphasis>integration tests</emphasis> which exercise all Java layers of the application (that is, everything except the view pages)."
msgstr ""
#. Tag: para
@@ -40,24 +35,18 @@
#: Testing.xml:15
#, no-c-format
msgid "Unit testing Seam components"
-msgstr ""
+msgstr "Test d'unità dei componenti Seam"
#. Tag: para
#: Testing.xml:16
#, no-c-format
-msgid ""
-"All Seam components are POJOs. This is a great place to start if you want "
-"easy unit testing. And since Seam emphasises the use of bijection for inter-"
-"component interactions and access to contextual objects, it's very easy to "
-"test a Seam component outside of its normal runtime environment."
+msgid "All Seam components are POJOs. This is a great place to start if you want easy unit testing. And since Seam emphasises the use of bijection for inter-component interactions and access to contextual objects, it's very easy to test a Seam component outside of its normal runtime environment."
msgstr ""
#. Tag: para
#: Testing.xml:23
#, no-c-format
-msgid ""
-"Consider the following Seam Component which creates a statement of account "
-"for a customer:"
+msgid "Consider the following Seam Component which creates a statement of account for a customer:"
msgstr ""
#. Tag: programlisting
@@ -79,8 +68,7 @@
" @Create\n"
" public void create() {\n"
" List<Invoice> invoices = entityManager\n"
-" .createQuery(\"select invoice from Invoice invoice where invoice."
-"customer = :customer\")\n"
+" .createQuery(\"select invoice from Invoice invoice where invoice.customer = :customer\")\n"
" .setParameter(\"customer\", customer)\n"
" .getResultList();\n"
" statementTotal = calculateTotal(invoices);\n"
@@ -99,13 +87,44 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[@Stateless\n"
+"@Scope(EVENT)\n"
+"@Name(\"statementOfAccount\")\n"
+"public class StatementOfAccount {\n"
+" \n"
+" @In(create=true) EntityManager entityManager\n"
+" \n"
+" private double statementTotal;\n"
+" \n"
+" @In\n"
+" private Customer customer;\n"
+" \n"
+" @Create\n"
+" public void create() {\n"
+" List<Invoice> invoices = entityManager\n"
+" .createQuery(\"select invoice from Invoice invoice where invoice.customer = :customer\")\n"
+" .setParameter(\"customer\", customer)\n"
+" .getResultList();\n"
+" statementTotal = calculateTotal(invoices);\n"
+" }\n"
+" \n"
+" public double calculateTotal(List<Invoice> invoices) {\n"
+" double total = 0.0;\n"
+" for (Invoice invoice: invoices)\n"
+" {\n"
+" double += invoice.getTotal();\n"
+" }\n"
+" return total;\n"
+" }\n"
+" \n"
+" // getter and setter for statementTotal\n"
+" \n"
+"}]]>"
#. Tag: para
#: Testing.xml:30
#, no-c-format
-msgid ""
-"We could write a unit test for the calculateTotal method (which tests the "
-"business logic of the component) as follows:"
+msgid "We could write a unit test for the calculateTotal method (which tests the business logic of the component) as follows:"
msgstr ""
#. Tag: programlisting
@@ -116,25 +135,28 @@
" \n"
" @Test\n"
" public testCalculateTotal {\n"
-" List<Invoice> invoices = generateTestInvoices(); // A test data "
-"generator\n"
-" double statementTotal = new StatementOfAccount().calculateTotal"
-"(invoices);\n"
+" List<Invoice> invoices = generateTestInvoices(); // A test data generator\n"
+" double statementTotal = new StatementOfAccount().calculateTotal(invoices);\n"
" assert statementTotal = 123.45;\n"
" } \n"
"}\n"
"]]>"
msgstr ""
+"<![CDATA[public class StatementOfAccountTest {\n"
+" \n"
+" @Test\n"
+" public testCalculateTotal {\n"
+" List<Invoice> invoices = generateTestInvoices(); // A test data generator\n"
+" double statementTotal = new StatementOfAccount().calculateTotal(invoices);\n"
+" assert statementTotal = 123.45;\n"
+" } \n"
+"}\n"
+"]]>"
#. Tag: para
#: Testing.xml:37
#, no-c-format
-msgid ""
-"You'll notice we aren't testing retrieving data from or persisting data to "
-"the database; nor are we testing any functionality provided by Seam. We are "
-"just testing the logic of our POJOs. Seam components don't usually depend "
-"directly upon container infrastructure, so most unit testing as as easy as "
-"that!"
+msgid "You'll notice we aren't testing retrieving data from or persisting data to the database; nor are we testing any functionality provided by Seam. We are just testing the logic of our POJOs. Seam components don't usually depend directly upon container infrastructure, so most unit testing as as easy as that!"
msgstr ""
#. Tag: para
@@ -147,29 +169,18 @@
#: Testing.xml:51
#, no-c-format
msgid "Integration testing Seam components"
-msgstr ""
+msgstr "Test d'integrazione dei componenti Seam"
#. Tag: para
#: Testing.xml:53
#, no-c-format
-msgid ""
-"Integration testing is slightly more difficult. In this case, we can't "
-"eliminate the container infrastructure; indeed, that is part of what is "
-"being tested! At the same time, we don't want to be forced to deploy our "
-"application to an application server to run the automated tests. We need to "
-"be able to reproduce just enough of the container infrastructure inside our "
-"testing environment to be able to exercise the whole application, without "
-"hurting performance too much."
+msgid "Integration testing is slightly more difficult. In this case, we can't eliminate the container infrastructure; indeed, that is part of what is being tested! At the same time, we don't want to be forced to deploy our application to an application server to run the automated tests. We need to be able to reproduce just enough of the container infrastructure inside our testing environment to be able to exercise the whole application, without hurting performance too much."
msgstr ""
#. Tag: para
#: Testing.xml:62
#, no-c-format
-msgid ""
-"The approach taken by Seam is to let you write tests that exercise your "
-"components while running inside a pruned down container environment (Seam, "
-"together with the JBoss Embedded container; see <xref linkend=\"config."
-"install.embedded\"/> for configuration details)"
+msgid "The approach taken by Seam is to let you write tests that exercise your components while running inside a pruned down container environment (Seam, together with the JBoss Embedded container; see <xref linkend=\"config.install.embedded\"/> for configuration details)"
msgstr ""
#. Tag: programlisting
@@ -190,8 +201,7 @@
" setValue(\"#{user.username}\", \"1ovthafew\");\n"
" setValue(\"#{user.name}\", \"Gavin King\");\n"
" setValue(\"#{user.password}\", \"secret\");\n"
-" assert invokeMethod(\"#{register.register}\").equals(\"success"
-"\");\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
" assert getValue(\"#{user.username}\").equals(\"1ovthafew\");\n"
" assert getValue(\"#{user.name}\").equals(\"Gavin King\");\n"
" assert getValue(\"#{user.password}\").equals(\"secret\");\n"
@@ -205,6 +215,33 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[public class RegisterTest extends SeamTest\n"
+"{\n"
+" \n"
+" @Test\n"
+" public void testRegisterComponent() throws Exception\n"
+" {\n"
+" \n"
+" new ComponentTest() {\n"
+"\n"
+" protected void testComponents() throws Exception\n"
+" {\n"
+" setValue(\"#{user.username}\", \"1ovthafew\");\n"
+" setValue(\"#{user.name}\", \"Gavin King\");\n"
+" setValue(\"#{user.password}\", \"secret\");\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
+" assert getValue(\"#{user.username}\").equals(\"1ovthafew\");\n"
+" assert getValue(\"#{user.name}\").equals(\"Gavin King\");\n"
+" assert getValue(\"#{user.password}\").equals(\"secret\");\n"
+" }\n"
+" \n"
+" }.run();\n"
+" \n"
+" }\n"
+"\n"
+" ...\n"
+" \n"
+"}]]>"
#. Tag: title
#: Testing.xml:73
@@ -215,11 +252,7 @@
#. Tag: para
#: Testing.xml:75
#, no-c-format
-msgid ""
-"Occasionally, we need to be able to replace the implementation of some Seam "
-"component that depends upon resources which are not available in the "
-"integration test environment. For example, suppose we have some Seam "
-"component which is a facade to some payment processing system:"
+msgid "Occasionally, we need to be able to replace the implementation of some Seam component that depends upon resources which are not available in the integration test environment. For example, suppose we have some Seam component which is a facade to some payment processing system:"
msgstr ""
#. Tag: programlisting
@@ -231,6 +264,10 @@
" public boolean processPayment(Payment payment) { .... }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"paymentProcessor\")\n"
+"public class PaymentProcessor {\n"
+" public boolean processPayment(Payment payment) { .... }\n"
+"}]]>"
#. Tag: para
#: Testing.xml:84
@@ -250,16 +287,18 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[@Name(\"paymentProcessor\")\n"
+"@Install(precedence=MOCK)\n"
+"public class MockPaymentProcessor extends PaymentProcessor {\n"
+" public boolean processPayment(Payment payment) {\n"
+" return true;\n"
+" }\n"
+"}]]>"
#. Tag: para
#: Testing.xml:90
#, no-c-format
-msgid ""
-"Since the <literal>MOCK</literal> precedence is higher than the default "
-"precedence of application components, Seam will install the mock "
-"implementation whenever it is in the classpath. When deployed into "
-"production, the mock implementation is absent, so the real component will be "
-"installed."
+msgid "Since the <literal>MOCK</literal> precedence is higher than the default precedence of application components, Seam will install the mock implementation whenever it is in the classpath. When deployed into production, the mock implementation is absent, so the real component will be installed."
msgstr ""
#. Tag: title
@@ -271,22 +310,13 @@
#. Tag: para
#: Testing.xml:105
#, no-c-format
-msgid ""
-"An even harder problem is emulating user interactions. A third problem is "
-"where to put our assertions. Some test frameworks let us test the whole "
-"application by reproducing user interactions with the web browser. These "
-"frameworks have their place, but they are not appropriate for use at "
-"development time."
+msgid "An even harder problem is emulating user interactions. A third problem is where to put our assertions. Some test frameworks let us test the whole application by reproducing user interactions with the web browser. These frameworks have their place, but they are not appropriate for use at development time."
msgstr ""
#. Tag: para
#: Testing.xml:112
#, no-c-format
-msgid ""
-"<literal>SeamTest</literal> lets you write <emphasis>scripted</emphasis> "
-"tests, in a simulated JSF environment. The role of a scripted test is to "
-"reproduce the interaction between the view and the Seam components. In other "
-"words, you get to pretend you are the JSF implementation!"
+msgid "<literal>SeamTest</literal> lets you write <emphasis>scripted</emphasis> tests, in a simulated JSF environment. The role of a scripted test is to reproduce the interaction between the view and the Seam components. In other words, you get to pretend you are the JSF implementation!"
msgstr ""
#. Tag: para
@@ -327,21 +357,44 @@
" </tr>\n"
" </table>\n"
" <h:messages/>\n"
-" <h:commandButton type=\"submit\" value=\"Register\" action=\"#{register."
-"register}\"/>\n"
+" <h:commandButton type=\"submit\" value=\"Register\" action=\"#{register.register}\"/>\n"
" </h:form>\n"
" </f:view>\n"
" </body>\n"
"</html>]]>"
msgstr ""
+"<![CDATA[<html>\n"
+" <head>\n"
+" <title>Register New User</title>\n"
+" </head>\n"
+" <body>\n"
+" <f:view>\n"
+" <h:form>\n"
+" <table border=\"0\">\n"
+" <tr>\n"
+" <td>Username</td>\n"
+" <td><h:inputText value=\"#{user.username}\"/></td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>Real Name</td>\n"
+" <td><h:inputText value=\"#{user.name}\"/></td>\n"
+" </tr>\n"
+" <tr>\n"
+" <td>Password</td>\n"
+" <td><h:inputSecret value=\"#{user.password}\"/></td>\n"
+" </tr>\n"
+" </table>\n"
+" <h:messages/>\n"
+" <h:commandButton type=\"submit\" value=\"Register\" action=\"#{register.register}\"/>\n"
+" </h:form>\n"
+" </f:view>\n"
+" </body>\n"
+"</html>]]>"
#. Tag: para
#: Testing.xml:129
#, no-c-format
-msgid ""
-"We want to test the registration functionality of our application (the stuff "
-"that happens when the user clicks the Register button). We'll reproduce the "
-"JSF request lifecycle in an automated TestNG test:"
+msgid "We want to test the registration functionality of our application (the stuff that happens when the user clicks the Register button). We'll reproduce the JSF request lifecycle in an automated TestNG test:"
msgstr ""
#. Tag: programlisting
@@ -377,8 +430,7 @@
" @Override\n"
" protected void invokeApplication()\n"
" {\n"
-" assert invokeMethod(\"#{register.register}\").equals(\"success"
-"\");\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
" }\n"
"\n"
" @Override\n"
@@ -397,43 +449,76 @@
" \n"
"}]]>"
msgstr ""
+"<![CDATA[public class RegisterTest extends SeamTest\n"
+"{\n"
+" \n"
+" @Test\n"
+" public void testRegister() throws Exception\n"
+" {\n"
+" \n"
+" new FacesRequest() {\n"
+"\n"
+" @Override\n"
+" protected void processValidations() throws Exception\n"
+" {\n"
+" validateValue(\"#{user.username}\", \"1ovthafew\");\n"
+" validateValue(\"#{user.name}\", \"Gavin King\");\n"
+" validateValue(\"#{user.password}\", \"secret\");\n"
+" assert !isValidationFailure();\n"
+" }\n"
+" \n"
+" @Override\n"
+" protected void updateModelValues() throws Exception\n"
+" {\n"
+" setValue(\"#{user.username}\", \"1ovthafew\");\n"
+" setValue(\"#{user.name}\", \"Gavin King\");\n"
+" setValue(\"#{user.password}\", \"secret\");\n"
+" }\n"
+"\n"
+" @Override\n"
+" protected void invokeApplication()\n"
+" {\n"
+" assert invokeMethod(\"#{register.register}\").equals(\"success\");\n"
+" }\n"
+"\n"
+" @Override\n"
+" protected void renderResponse()\n"
+" {\n"
+" assert getValue(\"#{user.username}\").equals(\"1ovthafew\");\n"
+" assert getValue(\"#{user.name}\").equals(\"Gavin King\");\n"
+" assert getValue(\"#{user.password}\").equals(\"secret\");\n"
+" }\n"
+" \n"
+" }.run();\n"
+" \n"
+" }\n"
+"\n"
+" ...\n"
+" \n"
+"}]]>"
#. Tag: para
#: Testing.xml:137
#, no-c-format
-msgid ""
-"Notice that we've extended <literal>SeamTest</literal>, which provides a "
-"Seam environment for our components, and written our test script as an "
-"anonymous class that extends <literal>SeamTest.FacesRequest</literal>, which "
-"provides an emulated JSF request lifecycle. (There is also a "
-"<literal>SeamTest.NonFacesRequest</literal> for testing GET requests.) We've "
-"written our code in methods which are named for the various JSF phases, to "
-"emulate the calls that JSF would make to our components. Then we've thrown "
-"in various assertions."
+msgid "Notice that we've extended <literal>SeamTest</literal>, which provides a Seam environment for our components, and written our test script as an anonymous class that extends <literal>SeamTest.FacesRequest</literal>, which provides an emulated JSF request lifecycle. (There is also a <literal>SeamTest.NonFacesRequest</literal> for testing GET requests.) We've written our code in methods which are named for the various JSF phases, to emulate the calls that JSF would make to our components. Then we've thrown in various assertions."
msgstr ""
#. Tag: para
#: Testing.xml:148
#, no-c-format
-msgid ""
-"You'll find plenty of integration tests for the Seam example applications "
-"which demonstrate more complex cases. There are instructions for running "
-"these tests using Ant, or using the TestNG plugin for eclipse:"
+msgid "You'll find plenty of integration tests for the Seam example applications which demonstrate more complex cases. There are instructions for running these tests using Ant, or using the TestNG plugin for eclipse:"
msgstr ""
#. Tag: title
#: Testing.xml:164
#, no-c-format
msgid "Configuration"
-msgstr ""
+msgstr "Configurazione"
#. Tag: para
#: Testing.xml:166
#, no-c-format
-msgid ""
-"If you used seam-gen to create your project you are ready to start writing "
-"tests. Otherwise you'll need to setup the testing environment in your "
-"favorite build tool (e.g. ant, maven, eclipse)."
+msgid "If you used seam-gen to create your project you are ready to start writing tests. Otherwise you'll need to setup the testing environment in your favorite build tool (e.g. ant, maven, eclipse)."
msgstr ""
#. Tag: para
@@ -446,13 +531,13 @@
#: Testing.xml:182
#, no-c-format
msgid "Group Id"
-msgstr ""
+msgstr "Group Id"
#. Tag: entry
#: Testing.xml:185
#, no-c-format
msgid "Artifact Id"
-msgstr ""
+msgstr "Artifact Id"
#. Tag: entry
#: Testing.xml:188
@@ -461,184 +546,169 @@
msgstr ""
#. Tag: literal
-#: Testing.xml:196 Testing.xml:207 Testing.xml:218 Testing.xml:229
+#: Testing.xml:196
+#: Testing.xml:207
+#: Testing.xml:218
+#: Testing.xml:229
#, no-c-format
msgid "org.jboss.seam.embedded"
-msgstr ""
+msgstr "org.jboss.seam.embedded"
#. Tag: literal
#: Testing.xml:199
#, no-c-format
msgid "hibernate-all"
-msgstr ""
+msgstr "hibernate-all"
#. Tag: literal
#: Testing.xml:202
#, no-c-format
msgid "lib/test/hibernate-all.jar"
-msgstr ""
+msgstr "lib/test/hibernate-all.jar"
#. Tag: literal
#: Testing.xml:210
#, no-c-format
msgid "jboss-embedded-all"
-msgstr ""
+msgstr "jboss-embedded-all"
#. Tag: literal
#: Testing.xml:213
#, no-c-format
msgid "lib/test/jboss-embedded-all.jar"
-msgstr ""
+msgstr "lib/test/jboss-embedded-all.jar"
#. Tag: literal
#: Testing.xml:221
#, no-c-format
msgid "thirdparty-all"
-msgstr ""
+msgstr "thirdparty-all"
#. Tag: literal
#: Testing.xml:224
#, no-c-format
msgid "lib/test/thirdparty-all.jar"
-msgstr ""
+msgstr "lib/test/thirdparty-all.jar"
#. Tag: literal
#: Testing.xml:232
#, no-c-format
msgid "jboss-embedded-api"
-msgstr ""
+msgstr "jboss-embedded-api"
#. Tag: literal
#: Testing.xml:235
#, no-c-format
msgid "lib/jboss-embedded-api.jar"
-msgstr ""
+msgstr "lib/jboss-embedded-api.jar"
#. Tag: literal
#: Testing.xml:240
#, no-c-format
msgid "org.jboss.seam"
-msgstr ""
+msgstr "org.jboss.seam"
#. Tag: literal
#: Testing.xml:243
#, no-c-format
msgid "jboss-seam"
-msgstr ""
+msgstr "jboss-seam"
#. Tag: literal
#: Testing.xml:246
#, no-c-format
msgid "lib/jboss-seam.jar"
-msgstr ""
+msgstr "lib/jboss-seam.jar"
#. Tag: literal
#: Testing.xml:251
#, no-c-format
msgid "org.jboss.el"
-msgstr ""
+msgstr "org.jboss.el"
#. Tag: literal
#: Testing.xml:254
#, no-c-format
msgid "jboss-el"
-msgstr ""
+msgstr "jboss-el"
#. Tag: literal
#: Testing.xml:257
#, no-c-format
msgid "lib/jboss-el.jar"
-msgstr ""
+msgstr "lib/jboss-el.jar"
#. Tag: literal
#: Testing.xml:262
#, no-c-format
msgid "javax.faces"
-msgstr ""
+msgstr "javax.faces"
#. Tag: literal
#: Testing.xml:265
#, no-c-format
msgid "jsf-api"
-msgstr ""
+msgstr "jsf-api"
#. Tag: literal
#: Testing.xml:268
#, no-c-format
msgid "lib/jsf-api.jar"
-msgstr ""
+msgstr "lib/jsf-api.jar"
#. Tag: literal
#: Testing.xml:273
#, no-c-format
msgid "javax.el"
-msgstr ""
+msgstr "javax.el"
#. Tag: literal
#: Testing.xml:276
#, no-c-format
msgid "el-api"
-msgstr ""
+msgstr "el-api"
#. Tag: literal
#: Testing.xml:279
#, no-c-format
msgid "lib/el-api.jar"
-msgstr ""
+msgstr "lib/el-api.jar"
#. Tag: literal
-#: Testing.xml:284 Testing.xml:287
+#: Testing.xml:284
+#: Testing.xml:287
#, no-c-format
msgid "javax.activation"
-msgstr ""
+msgstr "javax.activation"
#. Tag: literal
#: Testing.xml:290
#, no-c-format
msgid "lib/activation.jar"
-msgstr ""
+msgstr "lib/activation.jar"
#. Tag: para
#: Testing.xml:297
#, no-c-format
-msgid ""
-"It's very important you don't put the compile time JBoss AS dependencies "
-"from <literal>lib/</literal> (e.g. <literal>jboss-system.jar</literal>) on "
-"the classpath, these will cause Embedded JBoss to not boot. So, just add the "
-"dependencies (e.g. Drools, jBPM)you need as you go."
+msgid "It's very important you don't put the compile time JBoss AS dependencies from <literal>lib/</literal> (e.g. <literal>jboss-system.jar</literal>) on the classpath, these will cause Embedded JBoss to not boot. So, just add the dependencies (e.g. Drools, jBPM)you need as you go."
msgstr ""
#. Tag: para
#: Testing.xml:305
#, no-c-format
-msgid ""
-"You also need to include the <literal>bootstrap/</literal> directory on the "
-"classpath; <literal>bootstrap/</literal> contains the configuration for "
-"Embedded JBoss."
+msgid "You also need to include the <literal>bootstrap/</literal> directory on the classpath; <literal>bootstrap/</literal> contains the configuration for Embedded JBoss."
msgstr ""
#. Tag: para
#: Testing.xml:311
#, no-c-format
-msgid ""
-"And, of course you need to put your built project and tests onto the "
-"classpath as well as jar for your test framework. Don't forget to put all "
-"the correct configuration files for JPA and Seam onto the classpath as well."
-"Seam asks Embedded JBoss to deploy any resource (jar or directory) which has "
-"<literal>seam.properties</literal> in it's root. Therefore, if you don't "
-"assemble a directory structure that resembles a deployable archive "
-"containing your built project, you must put a <literal>seam.properties</"
-"literal> in each resource."
+msgid "And, of course you need to put your built project and tests onto the classpath as well as jar for your test framework. Don't forget to put all the correct configuration files for JPA and Seam onto the classpath as well.Seam asks Embedded JBoss to deploy any resource (jar or directory) which has <literal>seam.properties</literal> in it's root. Therefore, if you don't assemble a directory structure that resembles a deployable archive containing your built project, you must put a <literal>seam.properties</literal> in each resource."
msgstr ""
#. Tag: para
#: Testing.xml:323
#, no-c-format
-msgid ""
-"By default, a generated project will use the <literal>java:/DefaultDS</"
-"literal> (a built in HSQL datasource in Embedded JBoss) for testing. If you "
-"want to use another datasource place the <literal>foo-ds.xml</literal> into "
-"<literal>bootstrap/deploy</literal> directory."
+msgid "By default, a generated project will use the <literal>java:/DefaultDS</literal> (a built in HSQL datasource in Embedded JBoss) for testing. If you want to use another datasource place the <literal>foo-ds.xml</literal> into <literal>bootstrap/deploy</literal> directory."
msgstr ""
#. Tag: title
@@ -650,17 +720,13 @@
#. Tag: para
#: Testing.xml:336
#, no-c-format
-msgid ""
-"Seam provides TestNG support out of the box, but you can also use another "
-"test framework, such as JUnit, if you want."
+msgid "Seam provides TestNG support out of the box, but you can also use another test framework, such as JUnit, if you want."
msgstr ""
#. Tag: para
#: Testing.xml:341
#, no-c-format
-msgid ""
-"You'll need to provide an implementation of <literal>AbstractSeamTest</"
-"literal> which does the following:"
+msgid "You'll need to provide an implementation of <literal>AbstractSeamTest</literal> which does the following:"
msgstr ""
#. Tag: para
@@ -678,33 +744,25 @@
#. Tag: para
#: Testing.xml:360
#, no-c-format
-msgid ""
-"Calls <literal>super.setupClass()</literal> to setup integration test "
-"environment. This should be called before any test methods are called."
+msgid "Calls <literal>super.setupClass()</literal> to setup integration test environment. This should be called before any test methods are called."
msgstr ""
#. Tag: para
#: Testing.xml:367
#, no-c-format
-msgid ""
-"Calls <literal>super.cleanupClass()</literal> to clean up the integration "
-"test environment."
+msgid "Calls <literal>super.cleanupClass()</literal> to clean up the integration test environment."
msgstr ""
#. Tag: para
#: Testing.xml:373
#, no-c-format
-msgid ""
-"Calls <literal>super.startSeam()</literal> to start Seam at the start of "
-"integration testing."
+msgid "Calls <literal>super.startSeam()</literal> to start Seam at the start of integration testing."
msgstr ""
#. Tag: para
#: Testing.xml:379
#, no-c-format
-msgid ""
-"Calls <literal>super.stopSeam()</literal> to cleanly shut down Seam at the "
-"end of integration testing."
+msgid "Calls <literal>super.stopSeam()</literal> to cleanly shut down Seam at the end of integration testing."
msgstr ""
#. Tag: title
@@ -716,25 +774,19 @@
#. Tag: para
#: Testing.xml:390
#, no-c-format
-msgid ""
-"If you need to insert or clean data in your database before each test you "
-"can use Seam's integration with DBUnit. To do this, extend DBUnitSeamTest "
-"rather than SeamTest."
+msgid "If you need to insert or clean data in your database before each test you can use Seam's integration with DBUnit. To do this, extend DBUnitSeamTest rather than SeamTest."
msgstr ""
#. Tag: para
#: Testing.xml:396
#, no-c-format
msgid "You need to provide a dataset for DBUnit."
-msgstr ""
+msgstr "Devi fornire un dataset per DBUnit."
#. Tag: caution
#: Testing.xml:400
#, no-c-format
-msgid ""
-"DBUnit supports two formats for dataset files, flat and XML. Seam's "
-"DBUnitSeamTest assumes the flat format is used, so make sure that your "
-"dataset is in this format."
+msgid "DBUnit supports two formats for dataset files, flat and XML. Seam's DBUnitSeamTest assumes the flat format is used, so make sure that your dataset is in this format."
msgstr ""
#. Tag: programlisting
@@ -755,13 +807,24 @@
" \n"
"</dataset>]]>"
msgstr ""
+"<![CDATA[<dataset>\n"
+" \n"
+" <ARTIST \n"
+" id=\"1\"\n"
+" dtype=\"Band\"\n"
+" name=\"Pink Floyd\" />\n"
+" \n"
+" <DISC\n"
+" id=\"1\"\n"
+" name=\"Dark Side of the Moon\"\n"
+" artist_id=\"1\" />\n"
+" \n"
+"</dataset>]]>"
#. Tag: para
#: Testing.xml:408
#, no-c-format
-msgid ""
-"and tell Seam about it by overriding <literal>prepareDBUnitOperations()</"
-"literal>:"
+msgid "and tell Seam about it by overriding <literal>prepareDBUnitOperations()</literal>:"
msgstr ""
#. Tag: programlisting
@@ -774,104 +837,89 @@
" );\n"
" }]]>"
msgstr ""
+"<![CDATA[protected void prepareDBUnitOperations() {\n"
+" beforeTestOperations.add(\n"
+" new DataSetOperation(\"my/datasets/BaseData.xml\")\n"
+" );\n"
+" }]]>"
#. Tag: para
#: Testing.xml:414
#, no-c-format
-msgid ""
-"<literal>DataSetOperation</literal> defaults to <literal>DatabaseOperation."
-"CLEAN_INSERT</literal> if no other operation is specified as a constructor "
-"argument. The above example cleans all tables defined <literal>BaseData.xml</"
-"literal>, then inserts all rows declared in <literal>BaseData.xml</literal> "
-"before each <literal>@Test</literal> method is invoked."
+msgid "<literal>DataSetOperation</literal> defaults to <literal>DatabaseOperation.CLEAN_INSERT</literal> if no other operation is specified as a constructor argument. The above example cleans all tables defined <literal>BaseData.xml</literal>, then inserts all rows declared in <literal>BaseData.xml</literal> before each <literal>@Test</literal> method is invoked."
msgstr ""
#. Tag: para
#: Testing.xml:422
#, no-c-format
-msgid ""
-"If you require extra cleanup after a test method executes, add operations to "
-"<literal>afterTestOperations</literal> list."
+msgid "If you require extra cleanup after a test method executes, add operations to <literal>afterTestOperations</literal> list."
msgstr ""
#. Tag: para
#: Testing.xml:427
#, no-c-format
-msgid ""
-"You need to tell DBUnit about the datasource you are using by setting a "
-"TestNG test parameter named <literal>datasourceJndiName</literal>:"
+msgid "You need to tell DBUnit about the datasource you are using by setting a TestNG test parameter named <literal>datasourceJndiName</literal>:"
msgstr ""
#. Tag: programlisting
#: Testing.xml:432
#, no-c-format
-msgid ""
-"<![CDATA[<parameter name=\"datasourceJndiName\" value=\"java:/"
-"seamdiscsDatasource\"/>]]>"
-msgstr ""
+msgid "<![CDATA[<parameter name=\"datasourceJndiName\" value=\"java:/seamdiscsDatasource\"/>]]>"
+msgstr "<![CDATA[<parameter name=\"datasourceJndiName\" value=\"java:/seamdiscsDatasource\"/>]]>"
#. Tag: para
#: Testing.xml:434
#, no-c-format
-msgid ""
-"DBUnitSeamTest has support for MySQL and HSQL - you need to tell it which "
-"database is being used:"
+msgid "DBUnitSeamTest has support for MySQL and HSQL - you need to tell it which database is being used:"
msgstr ""
#. Tag: programlisting
#: Testing.xml:439
#, no-c-format
msgid "<![CDATA[<parameter name=\"database\" value=\"HSQL\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<parameter name=\"database\" value=\"HSQL\" />]]>"
#. Tag: para
#: Testing.xml:441
#, no-c-format
-msgid ""
-"It also allows you to insert binary data into the test data set (n.b. this "
-"is untested on Windows). You need to tell it where to locate these resources:"
+msgid "It also allows you to insert binary data into the test data set (n.b. this is untested on Windows). You need to tell it where to locate these resources:"
msgstr ""
#. Tag: programlisting
#: Testing.xml:447
#, no-c-format
msgid "<![CDATA[<parameter name=\"binaryDir\" value=\"images/\" />]]>"
-msgstr ""
+msgstr "<![CDATA[<parameter name=\"binaryDir\" value=\"images/\" />]]>"
#. Tag: para
#: Testing.xml:449
#, no-c-format
-msgid ""
-"You <emphasis>must</emphasis> specify these three parameters in your "
-"<literal>testng.xml</literal>."
+msgid "You <emphasis>must</emphasis> specify these three parameters in your <literal>testng.xml</literal>."
msgstr ""
#. Tag: para
#: Testing.xml:454
#, no-c-format
-msgid ""
-"If you want to use DBUnitSeamTest with another database, you'll need to "
-"implement some methods. Read the javadoc of <literal>AbstractDBUnitSeamTest</"
-"literal> for more."
+msgid "If you want to use DBUnitSeamTest with another database, you'll need to implement some methods. Read the javadoc of <literal>AbstractDBUnitSeamTest</literal> for more."
msgstr ""
#. Tag: title
#: Testing.xml:463
#, no-c-format
msgid "Integration Testing Seam Mail"
-msgstr ""
+msgstr "Test d'integrazione di Seam Mail"
#. Tag: caution
#: Testing.xml:465
#, no-c-format
msgid "Warning! This feature is still under development."
-msgstr ""
+msgstr "Attenzione! Questa funzionalità è ancora in fase di sviluppo."
#. Tag: para
#: Testing.xml:469
#, no-c-format
msgid "It's very easy to integration test your Seam Mail:"
-msgstr ""
+msgstr "E' facilissimo eseguire il test d'integrazione con Seam Mail:"
#. Tag: programlisting
#: Testing.xml:473
@@ -893,11 +941,9 @@
" \n"
" @Override\n"
" protected void invokeApplication() throws Exception {\n"
-" MimeMessage renderedMessage = getRenderedMailMessage(\"/simple."
-"xhtml\");\n"
+" MimeMessage renderedMessage = getRenderedMailMessage(\"/simple.xhtml\");\n"
" assert renderedMessage.getAllRecipients().length == 1;\n"
-" InternetAddress to = (InternetAddress) renderedMessage."
-"getAllRecipients()[0];\n"
+" InternetAddress to = (InternetAddress) renderedMessage.getAllRecipients()[0];\n"
" assert to.getAddress().equals(\"test(a)example.com\");\n"
" }\n"
" \n"
@@ -905,23 +951,41 @@
" }\n"
"}]]>"
msgstr ""
+"<![CDATA[public class MailTest extends SeamTest {\n"
+" \n"
+" @Test\n"
+" public void testSimpleMessage() throws Exception {\n"
+" \n"
+" new FacesRequest() {\n"
+"\n"
+" @Override\n"
+" protected void updateModelValues() throws Exception {\n"
+" setValue(\"#{person.firstname}\", \"Pete\");\n"
+" setValue(\"#{person.lastname}\", \"Muir\");\n"
+" setValue(\"#{person.address}\", \"test(a)example.com\");\n"
+" }\n"
+" \n"
+" @Override\n"
+" protected void invokeApplication() throws Exception {\n"
+" MimeMessage renderedMessage = getRenderedMailMessage(\"/simple.xhtml\");\n"
+" assert renderedMessage.getAllRecipients().length == 1;\n"
+" InternetAddress to = (InternetAddress) renderedMessage.getAllRecipients()[0];\n"
+" assert to.getAddress().equals(\"test(a)example.com\");\n"
+" }\n"
+" \n"
+" }.run(); \n"
+" }\n"
+"}]]>"
#. Tag: para
#: Testing.xml:475
#, no-c-format
-msgid ""
-"We create a new <literal>FacesRequest</literal> as normal. Inside the "
-"invokeApplication hook we render the message using "
-"<literal>getRenderedMailMessage(viewId);</literal>, passing the viewId of "
-"the message to render. The method returns the rendered message on which you "
-"can do your tests. You can of course also use any of the standard JSF "
-"lifecycle methods."
+msgid "We create a new <literal>FacesRequest</literal> as normal. Inside the invokeApplication hook we render the message using <literal>getRenderedMailMessage(viewId);</literal>, passing the viewId of the message to render. The method returns the rendered message on which you can do your tests. You can of course also use any of the standard JSF lifecycle methods."
msgstr ""
#. Tag: para
#: Testing.xml:484
#, no-c-format
-msgid ""
-"There is no support for rendering standard JSF components so you can't test "
-"the content body of the mail message easily."
+msgid "There is no support for rendering standard JSF components so you can't test the content body of the mail message easily."
msgstr ""
+
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-13 18:59:46 UTC (rev 9771)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-13 19:45:32 UTC (rev 9772)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:39+0000\n"
-"PO-Revision-Date: 2008-12-13 16:30+0100\n"
+"PO-Revision-Date: 2008-12-13 20:44+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -123,7 +123,7 @@
#: Validation.xml:24
#, no-c-format
msgid "Well, that's a decent first cut, but in practice it might be more elegant to use custom constraints instead of the ones built into Hibernate Validator:"
-msgstr ""
+msgstr "Bene, questo è una buona riduzione, ma in pratica puoi essere più elegante se utilizzi dei vincoli personalizzati invece di quelli interni a Hibernate Validator:"
#. Tag: programlisting
#: Validation.xml:30
@@ -163,7 +163,7 @@
#: Validation.xml:32
#, no-c-format
msgid "Whichever route we take, we no longer need to specify the type of validation to be used in the JSF page. Instead, we can use <literal><s:validate></literal> to validate against the constraint defined on the model object."
-msgstr ""
+msgstr "Qualsiasi strada prendiamo non dobbiamo più specificare il tipo di validazione da usare nelle pagine JSF. Invece possiamo usare <literal><s:validate></literal> per validare il vincolo definito nell'oggetto modello."
#. Tag: programlisting
#: Validation.xml:39
@@ -215,13 +215,13 @@
#: Validation.xml:41
#, no-c-format
msgid "<emphasis>Note:</emphasis> specifying <literal>@NotNull</literal> on the model does <emphasis>not</emphasis> eliminate the requirement for <literal>required=\"true\"</literal> to appear on the control! This is due to a limitation of the JSF validation architecture."
-msgstr ""
+msgstr "<emphasis>Nota:</emphasis> specificare <literal>@NotNull</literal> nel modello <emphasis>non</emphasis> elimina la necessità di <literal>required=\"true\"</literal> per farlo apparire nel controllo! Questo è dovuto ad una limitazione nell'architettura di validazione in JSF."
#. Tag: para
#: Validation.xml:48
#, no-c-format
msgid "This approach <emphasis>defines</emphasis> constraints on the model, and <emphasis>presents</emphasis> constraint violations in the view—a significantly better design."
-msgstr ""
+msgstr "Quest'approccio <emphasis>definisce</emphasis> i vincoli sul modello e <emphasis>presenta</emphasis> le violazioni al vincolo nella vista—di gran lunga un miglior design."
#. Tag: para
#: Validation.xml:54
@@ -287,7 +287,7 @@
#: Validation.xml:67
#, no-c-format
msgid "Now we need to do something about displaying feedback to the user when validation fails. Currently we are displaying all messages at the top of the form. In order for the user to correlate the message with an input, you need to define a label using the standard <literal>label</literal> attribute on the input component."
-msgstr ""
+msgstr "Adesso occorre fare qualcosa per mostrare all'utente un messaggio quando la validazione fallisce. Ora vengono mostrati tutti i messaggi in cima alla form. Per consentire all'utente di associare il messaggio al singolo input, occorre definire un'etichetta e usare l'attributo standard <literal>label</literal> sul componente d'input."
#. Tag: programlisting
#: Validation.xml:73
@@ -305,7 +305,7 @@
#: Validation.xml:75
#, no-c-format
msgid "You can then inject this value into the message string using the placeholder {0} (the first and only parameter passed to a JSF message for a Hiberate Validator restriction). See the internationalization section for more information regarding where to define these messages."
-msgstr ""
+msgstr "Puoi iniettare questo valore nella stringa del messaggio usando il placeholder {0} (il primo ed unico parametro passato al messaggio JSF a causa di una restrizione in Hibernate Validator). Vedere la sezione Internazionalizzazione per ulteriori informazioni sulla definizione dei messaggi."
#. Tag: programlisting
#: Validation.xml:83
@@ -317,13 +317,13 @@
#: Validation.xml:85
#, no-c-format
msgid "What we would really like to do, though, is display the message next to the field with the error (this is possible in plain JSF), highlight the field and label (this is not possible) and, for good measure, display some image next to the field (also not possible). We also want to display a little colored asterisk next to the label for each required form field. Using this approach, the identifying label is not necessary."
-msgstr ""
+msgstr "Ciò che vorremmo fare, tuttavia, è mostrare il messaggio vicino al campo con l'errore (questo è possibile nel semplice JSF), ed evidenziare il campo e l'etichetta (questo non è possibile) ed, eventualmente, mostrare un'immagine vicino al campo (anche questo non è possibile). Vogliamo anche mostrare un piccolo asterisco colorato vicino all'etichetta per ciascun campo richiesto. Utilizzando quest'approccio non è più necessario identificare l'etichetta."
#. Tag: para
#: Validation.xml:95
#, no-c-format
msgid "That's quite a lot of functionality we need for each field of our form. We wouldn't want to have to specify higlighting and the layout of the image, message and input field for every field on the form. So, instead, we'll specify the common layout in a facelets template:"
-msgstr ""
+msgstr "Abbiamo quindi bisogno di parecchia funzionalità per ogni singolo campo della form. Ma non vogliamo essere costretti a specificare per ogni campo della form come evidenziare, come disporre l'immagine, quale messaggio scrivere e quale è il campo d'input da associare."
#. Tag: programlisting
#: Validation.xml:103
@@ -385,7 +385,7 @@
#: Validation.xml:105
#, no-c-format
msgid "We can include this template for each of our form fields using <literal><s:decorate></literal>."
-msgstr ""
+msgstr "Possiamo includere questo template per ciascuna campo della form utilizzando <literal><s:decorate></literal>."
#. Tag: programlisting
#: Validation.xml:110
@@ -485,7 +485,7 @@
#: Validation.xml:119
#, no-c-format
msgid "It's better style to define explicit ids for important controls on the page, especially if you want to do automated testing for the UI, using some toolkit like Selenium. If you don't provide explicit ids, JSF will generate them, but the generated values will change if you change anything on the page."
-msgstr ""
+msgstr "E' uno stile migliore definire esplicitamente gli id per i controlli importanti all'interno della pagina, specialmente in caso di test automatico della UI, utilizzando dei toolkit quale Selenium. Se non vengono forniti gli id in modo esplicito, JSF li genererà, mai valori generati cambieranno se si cambia qualcosa nella pagina."
#. Tag: programlisting
#: Validation.xml:128
@@ -535,11 +535,12 @@
"\n"
"</h:form>]]>"
+# message bundle = ?
#. Tag: para
#: Validation.xml:130
#, no-c-format
msgid "And what if you want to specify a different message to be displayed when validation fails? You can use the Seam message bundle (and all it's goodies like el expressions inside the message, and per-view message bundles) with the Hibernate Validator:"
-msgstr ""
+msgstr "E se vuoi specificare un messaggio diverso quando la validazione fallisce? Puoi utilizzare il message bundle di Seam con Hibernate Validator (e tutte le altre finezze come le espressioni EL dentro il messaggio ed i message bundle per ogni singola vista)."
#. Tag: programlisting
#: Validation.xml:137
16 years
- 1
- 0