[seam-commits] Seam SVN: r9841 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Thu Dec 25 09:16:55 EST 2008
Author: nico.ben
Date: 2008-12-25 09:16:54 -0500 (Thu, 25 Dec 2008)
New Revision: 9841
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
trunk/doc/Seam_Reference_Guide/it-IT/Xml.po
Log:
JBSEAM-3767: Italian translation of Seam guide
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-16 12:44+0100\n"
+"PO-Revision-Date: 2008-12-25 15:04+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -157,7 +157,7 @@
#: Drools.xml:67
#, no-c-format
msgid "Notice that we gave the <literal>policyPricingWorkingMemory</literal> a reference back to our rule base via the <literal>ruleBase</literal> configuration property."
-msgstr "Notare che abbiamo dato a <literal>policyPricingWorkingMemory</literal> un riferimento alla base di regole tramite la proprietà di configurazione <literal>ruleBase</literal>."
+msgstr "Notare che è stato dato a <literal>policyPricingWorkingMemory</literal> un riferimento alla base di regole tramite la proprietà di configurazione <literal>ruleBase</literal>."
#. Tag: title
#: Drools.xml:76
@@ -169,7 +169,7 @@
#: Drools.xml:78
#, no-c-format
msgid "We can now inject our <literal>WorkingMemory</literal> into any Seam component, assert facts, and fire rules:"
-msgstr "Ora possiamo iniettare la <literal>WorkingMemory</literal> in un qualsiasi componente di Seam, asserire i fatti e lanciare le regole:"
+msgstr "Ora è possibile iniettare la <literal>WorkingMemory</literal> in un qualsiasi componente di Seam, asserire i fatti e lanciare le regole:"
#. Tag: programlisting
#: Drools.xml:83
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,7 +6,7 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-10-14 11:38+0000\n"
-"PO-Revision-Date: 2008-12-16 11:18+0100\n"
+"PO-Revision-Date: 2008-12-25 15:16+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -53,7 +53,7 @@
#: 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 "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."
+msgstr "Non serve conoscere jPDL per usare Seam. Se ci si trova 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 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
@@ -473,7 +473,7 @@
#: Jbpm.xml:287
#, no-c-format
msgid "We can also explicitly tell Seam where to find our pageflow definition. We specify this in <literal>components.xml</literal>:"
-msgstr "Possiamo anche comunicare esplicitamente a Seam dove trovare le definizioni dei pageflow. Questo viene specificato dentro <literal>components.xml</literal>:"
+msgstr "Si può anche comunicare esplicitamente a Seam dove trovare le definizioni dei pageflow. Questo viene specificato dentro <literal>components.xml</literal>:"
#. Tag: programlisting
#: Jbpm.xml:292
@@ -501,7 +501,7 @@
#: Jbpm.xml:299
#, no-c-format
msgid "We \"start\" a jPDL-based pageflow by specifying the name of the process definition using a <literal>@Begin</literal>, <literal>@BeginTask</literal> or <literal>@StartTask</literal> annotation:"
-msgstr ""
+msgstr "Si \"inizia\" un pageflow basato su jPDLspecificando il nome della definizione del processo usando un'annotazione <literal>@Begin</literal>, <literal>@BeginTask</literal> oppure <literal>@StartTask</literal>:"
#. Tag: programlisting
#: Jbpm.xml:306
@@ -517,7 +517,7 @@
#: Jbpm.xml:308
#, no-c-format
msgid "Alternatively we can start a pageflow using pages.xml:"
-msgstr "In alternativa possiamo iniziare un pageflow usando pages.xml:"
+msgstr "In alternativa si può iniziare un pageflow usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:310
@@ -535,13 +535,13 @@
#: Jbpm.xml:312
#, no-c-format
msgid "If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal> phase—during a <literal>@Factory</literal> or <literal>@Create</literal> method, for example—we consider ourselves to be already at the page being rendered, and use a <literal><start-page></literal> node as the first node in the pageflow, as in the example above."
-msgstr ""
+msgstr "Se il pageflow viene iniziato durante la fase <literal>RENDER_RESPONSE</literal>—durante un metodo <literal>@Factory</literal> o <literal>@Create</literal>, per esempio—si presume di essere già nella pagina da generare, e si usa un nodo <literal><start-page></literal> come primo nodo nel pageflow, come nell'esempio sopra."
#. Tag: para
#: Jbpm.xml:320
#, no-c-format
msgid "But if the pageflow is begun as the result of an action listener invocation, the outcome of the action listener determines which is the first page to be rendered. In this case, we use a <literal><start-state></literal> as the first node in the pageflow, and declare a transition for each possible outcome:"
-msgstr ""
+msgstr "Ma se il pageflow viene iniziato come risultato di un'invocazione di un action listener, l'esito dell'action listener determina quale è la prima pagina da generare. In questo caso si usa un <literal><start-state></literal> come primo nodo del pageflow, e si dichiara una transizione per ogni possibile esito:"
#. Tag: programlisting
#: Jbpm.xml:328
@@ -772,7 +772,7 @@
#: Jbpm.xml:428
#, no-c-format
msgid "Optionally, we can end a task, specify a jBPM <literal>transition</literal> name. In this case, Seam will signal the end of the current task in the overarching business process."
-msgstr "Opzionalmente possiamo terminare un task specificando un nome alla <literal>transition</literal> jBPM. In questo modo Seam segnalerà la fine del task corrente al processo di business sottostante."
+msgstr "Opzionalmente è possibile terminare un task specificando un nome alla <literal>transition</literal> jBPM. In questo modo Seam segnalerà la fine del task corrente al processo di business sottostante."
#. Tag: programlisting
#: Jbpm.xml:434
@@ -966,7 +966,7 @@
#: Jbpm.xml:549
#, no-c-format
msgid "To initiate a business process instance, we use the <literal>@CreateProcess</literal> annotation:"
-msgstr "Per iniziare un'istanza di processo di business, usiamo l'annotazione <literal>@CreateProcess</literal>:"
+msgstr "Per iniziare un'istanza di processo di business, si usa l'annotazione <literal>@CreateProcess</literal>:"
#. Tag: programlisting
#: Jbpm.xml:554
@@ -982,7 +982,7 @@
#: Jbpm.xml:556
#, no-c-format
msgid "Alternatively we can initiate a business process using pages.xml:"
-msgstr "In alternativa possiamo iniziare un processo di business usando pages.xml:"
+msgstr "In alternativa è possibile iniziare un processo di business usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:558
@@ -1006,7 +1006,7 @@
#: Jbpm.xml:565
#, no-c-format
msgid "When a process reaches a task node, task instances are created. These must be assigned to users or user groups. We can either hardcode our actor ids, or delegate to a Seam component:"
-msgstr "Quando un processo raggiunge un task node, vengono create istante di compiti. Queste devono essere assegnate a utenti o gruppi di utenti. Possiamo codificare gli id degli attori (actor id) o delegare ad un componente Seam:"
+msgstr "Quando un processo raggiunge un task node, vengono create istante di compiti. Queste devono essere assegnate a utenti o gruppi di utenti. Si può codificare gli id degli attori (actor id) o delegare ad un componente Seam:"
#. Tag: programlisting
#: Jbpm.xml:571
@@ -1025,7 +1025,7 @@
#: Jbpm.xml:573
#, no-c-format
msgid "In this case, we have simply assigned the task to the current user. We can also assign tasks to a pool:"
-msgstr "In questo caso abbiamo semplicemente assegnato il task all'utente corrente. Possiamo anche assegnare compiti ad un pool (gruppo):"
+msgstr "In questo caso si è semplicemente assegnato il task all'utente corrente. Possiamo anche assegnare compiti ad un pool (gruppo):"
#. Tag: programlisting
#: Jbpm.xml:578
@@ -1156,7 +1156,7 @@
#: Jbpm.xml:624
#, no-c-format
msgid "Alternatively we can begin work on a task using pages.xml:"
-msgstr "In alternativa possiamo iniziare a lavorare su un task usando pages.xml:"
+msgstr "In alternativa si può iniziare a lavorare su un task usando pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:626
@@ -1180,7 +1180,7 @@
#: 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 "Se terminiamo un conversazione usando <literal>@EndTask</literal>, Seam segnalerà il completamento del task:"
+msgstr "Se si termina una conversazione usando <literal>@EndTask</literal>, Seam segnalerà il completamento del task:"
#. Tag: programlisting
#: Jbpm.xml:640
@@ -1196,7 +1196,7 @@
#: Jbpm.xml:642
#, no-c-format
msgid "Alternatively we can use pages.xml:"
-msgstr "In alternativa usiamo pages.xml:"
+msgstr "In alternativa si usa pages.xml:"
#. Tag: programlisting
#: Jbpm.xml:644
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -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-21 14:58+0100\n"
+"PO-Revision-Date: 2008-12-25 14:54+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -164,7 +164,7 @@
#: 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\"."
-msgstr "Questo esempio è implementato con due template Facelets, un entity bean e un session bean stateless. Guardiamo ora il codice, partendo dal \"basso\"."
+msgstr "Questo esempio è implementato con due template Facelets, un entity bean e un session bean stateless. Si guardi ora il codice, partendo dal \"basso\"."
#. Tag: title
#: Tutorial.xml:141
@@ -5223,7 +5223,7 @@
#: 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 "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:"
+msgstr "Se l'entry del blog non viene trovata nel database, viene lanciata l'eccezione <literal>EntryNotFoundException</literal>. Si vuole che quest'eccezione venga evidenziata come errore 404, non 505, e quindi viene annotata la classe dell'eccezione:"
#. Tag: programlisting
#: Tutorial.xml:1911
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -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:44+0100\n"
+"PO-Revision-Date: 2008-12-25 14:52+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -81,7 +81,7 @@
#: Validation.xml:17
#, no-c-format
msgid "Let's start by defining our constraints, on our <literal>Location</literal> class:"
-msgstr "Iniziamo definendo i vincoli sulla classe <literal>Location</literal>: "
+msgstr "Si cominci col definire i vincoli sulla classe <literal>Location</literal>: "
#. Tag: programlisting
#: Validation.xml:22
@@ -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 "Bene, questo è una buona riduzione, ma in pratica è possibile essere più elegante utilizzando dei vincoli personalizzati invece di quelli interni a Hibernate Validator:"
+msgstr "Bene, questa è una prima buona riduzione, ma in pratica è possibile essere più eleganti utilizzando 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 "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."
+msgstr "Qualsiasi strada si prenda non occorre più specificare il tipo di validazione da usare nelle pagine JSF. Invece è possibile usare <literal><s:validate></literal> per validare il vincolo definito nell'oggetto modello."
#. Tag: programlisting
#: Validation.xml:39
@@ -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 "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."
+msgstr "Ciò che si vuole 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). Si vuole 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 "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."
+msgstr "Si ha quindi bisogno di parecchia funzionalità per ogni singolo campo della form. Ma non si vuole 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 "Possiamo includere questo template per ciascuna campo della form utilizzando <literal><s:decorate></literal>."
+msgstr "Si può includere questo template per ciascuna campo della form utilizzando <literal><s:decorate></literal>."
#. Tag: programlisting
#: Validation.xml:110
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Xml.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Xml.po 2008-12-24 17:57:31 UTC (rev 9840)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Xml.po 2008-12-25 14:16:54 UTC (rev 9841)
@@ -6,8 +6,8 @@
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-12-04 00:59+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
+"PO-Revision-Date: 2008-12-25 15:03+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -17,61 +17,36 @@
#: Xml.xml:6
#, no-c-format
msgid "Configuring Seam components"
-msgstr ""
+msgstr "Configurare i componenti Seam"
#. Tag: para
#: Xml.xml:8
#, no-c-format
-msgid ""
-"The philosophy of minimizing XML-based configuration is extremely strong in "
-"Seam. Nevertheless, there are various reasons why we might want to configure "
-"a Seam component using XML: to isolate deployment-specific information from "
-"the Java code, to enable the creation of re-usable frameworks, to configure "
-"Seam's built-in functionality, etc. Seam provides two basic approaches to "
-"configuring components: configuration via property settings in a properties "
-"file or in <literal>web.xml</literal>, and configuration via "
-"<literal>components.xml</literal>."
-msgstr ""
+msgid "The philosophy of minimizing XML-based configuration is extremely strong in Seam. Nevertheless, there are various reasons why we might want to configure a Seam component using XML: to isolate deployment-specific information from the Java code, to enable the creation of re-usable frameworks, to configure Seam's built-in functionality, etc. Seam provides two basic approaches to configuring components: configuration via property settings in a properties file or in <literal>web.xml</literal>, and configuration via <literal>components.xml</literal>."
+msgstr "La filosofia di minimizzare la configurazione basata su XML è estremamente forte in Seam. Tuttavia ci sono varie ragioni per voler configurare i componente Seam tramite XML: per isolare le informazioni specifiche del deploy dal codice Java, per abilitare la creazione di framework riutilizzabili, per configurare le funzionalità predefinite di Seam, ecc. Seam fornisce due approcci base per configurare i componenti: configurazione tramire impostazioni di proprietà in un file di proprietà o in <literal>web.xml</literal>, e configurazione tramite <literal>components.xml</literal>."
#. Tag: title
#: Xml.xml:18
#, no-c-format
msgid "Configuring components via property settings"
-msgstr ""
+msgstr "Configurare i componenti tramire impostazioni di proprietà"
#. Tag: para
#: Xml.xml:19
#, no-c-format
-msgid ""
-"Seam components may be provided with configuration properties either via "
-"servlet context parameters, or via a properties file named <literal>seam."
-"properties</literal> in the root of the classpath."
+msgid "Seam components may be provided with configuration properties either via servlet context parameters, or via a properties file named <literal>seam.properties</literal> in the root of the classpath."
msgstr ""
#. Tag: para
#: Xml.xml:23
#, no-c-format
-msgid ""
-"The configurable Seam component must expose JavaBeans-style property setter "
-"methods for the configurable attributes. If a Seam component named "
-"<literal>com.jboss.myapp.settings</literal> has a setter method named "
-"<literal>setLocale()</literal>, we can provide a property named <literal>com."
-"jboss.myapp.settings.locale</literal> in the <literal>seam.properties</"
-"literal> file or as a servlet context parameter, and Seam will set the value "
-"of the <literal>locale</literal> attribute whenever it instantiates the "
-"component."
+msgid "The configurable Seam component must expose JavaBeans-style property setter methods for the configurable attributes. If a Seam component named <literal>com.jboss.myapp.settings</literal> has a setter method named <literal>setLocale()</literal>, we can provide a property named <literal>com.jboss.myapp.settings.locale</literal> in the <literal>seam.properties</literal> file or as a servlet context parameter, and Seam will set the value of the <literal>locale</literal> attribute whenever it instantiates the component."
msgstr ""
#. Tag: para
#: Xml.xml:31
#, no-c-format
-msgid ""
-"The same mechanism is used to configure Seam itself. For example, to set the "
-"conversation timeout, we provide a value for <literal>org.jboss.seam.core."
-"manager.conversationTimeout</literal> in <literal>web.xml</literal> or "
-"<literal>seam.properties</literal>. (There is a built-in Seam component "
-"named <literal>org.jboss.seam.core.manager</literal> with a setter method "
-"named <literal>setConversationTimeout()</literal>.)"
+msgid "The same mechanism is used to configure Seam itself. For example, to set the conversation timeout, we provide a value for <literal>org.jboss.seam.core.manager.conversationTimeout</literal> in <literal>web.xml</literal> or <literal>seam.properties</literal>. (There is a built-in Seam component named <literal>org.jboss.seam.core.manager</literal> with a setter method named <literal>setConversationTimeout()</literal>.)"
msgstr ""
#. Tag: title
@@ -83,53 +58,37 @@
#. Tag: para
#: Xml.xml:43
#, no-c-format
-msgid ""
-"The <literal>components.xml</literal> file is a bit more powerful than "
-"property settings. It lets you:"
+msgid "The <literal>components.xml</literal> file is a bit more powerful than property settings. It lets you:"
msgstr ""
#. Tag: para
#: Xml.xml:50
#, no-c-format
-msgid ""
-"Configure components that have been installed automatically—including "
-"both built-in components, and application components that have been "
-"annotated with the <literal>@Name</literal> annotation and picked up by "
-"Seam's deployment scanner."
+msgid "Configure components that have been installed automatically—including both built-in components, and application components that have been annotated with the <literal>@Name</literal> annotation and picked up by Seam's deployment scanner."
msgstr ""
#. Tag: para
#: Xml.xml:55
#, no-c-format
-msgid ""
-"Install classes with no <literal>@Name</literal> annotation as Seam "
-"components—this is most useful for certain kinds of infrastructural "
-"components which can be installed multiple times different names (for "
-"example Seam-managed persistence contexts)."
+msgid "Install classes with no <literal>@Name</literal> annotation as Seam components—this is most useful for certain kinds of infrastructural components which can be installed multiple times different names (for example Seam-managed persistence contexts)."
msgstr ""
#. Tag: para
#: Xml.xml:60
#, no-c-format
-msgid ""
-"Install components that <emphasis>do</emphasis> have a <literal>@Name</"
-"literal> annotation but are not installed by default because of an "
-"<literal>@Install</literal> annotation that indicates the component should "
-"not be installed."
+msgid "Install components that <emphasis>do</emphasis> have a <literal>@Name</literal> annotation but are not installed by default because of an <literal>@Install</literal> annotation that indicates the component should not be installed."
msgstr ""
#. Tag: para
#: Xml.xml:65
#, no-c-format
msgid "Override the scope of a component."
-msgstr ""
+msgstr "Override dello scope di un componente"
#. Tag: para
#: Xml.xml:69
#, no-c-format
-msgid ""
-"A <literal>components.xml</literal> file may appear in one of three "
-"different places:"
+msgid "A <literal>components.xml</literal> file may appear in one of three different places:"
msgstr ""
#. Tag: para
@@ -147,30 +106,19 @@
#. Tag: para
#: Xml.xml:81
#, no-c-format
-msgid ""
-"Any directory of a <literal>jar</literal> that contains classes with an "
-"<literal>@Name</literal> annotation."
+msgid "Any directory of a <literal>jar</literal> that contains classes with an <literal>@Name</literal> annotation."
msgstr ""
#. Tag: para
#: Xml.xml:88
#, no-c-format
-msgid ""
-"Usually, Seam components are installed when the deployment scanner discovers "
-"a class with a <literal>@Name</literal> annotation sitting in an archive "
-"with a <literal>seam.properties</literal> file or a <literal>META-INF/"
-"components.xml</literal> file. (Unless the component has an "
-"<literal>@Install</literal> annotation indicating it should not be installed "
-"by default.) The <literal>components.xml</literal> file lets us handle "
-"special cases where we need to override the annotations."
+msgid "Usually, Seam components are installed when the deployment scanner discovers a class with a <literal>@Name</literal> annotation sitting in an archive with a <literal>seam.properties</literal> file or a <literal>META-INF/components.xml</literal> file. (Unless the component has an <literal>@Install</literal> annotation indicating it should not be installed by default.) The <literal>components.xml</literal> file lets us handle special cases where we need to override the annotations."
msgstr ""
#. Tag: para
#: Xml.xml:97
#, no-c-format
-msgid ""
-"For example, the following <literal>components.xml</literal> file installs "
-"jBPM:"
+msgid "For example, the following <literal>components.xml</literal> file installs jBPM:"
msgstr ""
#. Tag: programlisting
@@ -183,6 +131,11 @@
" <bpm:jbpm/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xmlns:bpm=\"http://jboss.com/products/seam/bpm\">\n"
+" <bpm:jbpm/>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:103
@@ -198,13 +151,14 @@
" <component class=\"org.jboss.seam.bpm.Jbpm\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <component class=\"org.jboss.seam.bpm.Jbpm\"/>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:109
#, no-c-format
-msgid ""
-"This one installs and configures two different Seam-managed persistence "
-"contexts:"
+msgid "This one installs and configures two different Seam-managed persistence contexts:"
msgstr ""
#. Tag: programlisting
@@ -212,19 +166,26 @@
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
-" xmlns:persistence=\"http://jboss.com/products/seam/persistence"
-"\"\n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
"\n"
" <persistence:managed-persistence-context name=\"customerDatabase\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"customerEntityManagerFactory\"/>\n"
+" persistence-unit-jndi-name=\"java:/customerEntityManagerFactory\"/>\n"
" \n"
" <persistence:managed-persistence-context name=\"accountingDatabase\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"accountingEntityManagerFactory\"/> \n"
+" persistence-unit-jndi-name=\"java:/accountingEntityManagerFactory\"/> \n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
+"\n"
+" <persistence:managed-persistence-context name=\"customerDatabase\"\n"
+" persistence-unit-jndi-name=\"java:/customerEntityManagerFactory\"/>\n"
+" \n"
+" <persistence:managed-persistence-context name=\"accountingDatabase\"\n"
+" persistence-unit-jndi-name=\"java:/accountingEntityManagerFactory\"/> \n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:115
@@ -238,27 +199,32 @@
msgid ""
"<![CDATA[<components>\n"
" <component name=\"customerDatabase\" \n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"customerEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/customerEntityManagerFactory</property>\n"
" </component>\n"
" \n"
" <component name=\"accountingDatabase\"\n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"accountingEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/accountingEntityManagerFactory</property>\n"
" </component>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <component name=\"customerDatabase\" \n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/customerEntityManagerFactory</property>\n"
+" </component>\n"
+" \n"
+" <component name=\"accountingDatabase\"\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/accountingEntityManagerFactory</property>\n"
+" </component>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:121
#, no-c-format
-msgid ""
-"This example creates a session-scoped Seam-managed persistence context (this "
-"is not recommended in practice):"
+msgid "This example creates a session-scoped Seam-managed persistence context (this is not recommended in practice):"
msgstr ""
#. Tag: programlisting
@@ -266,16 +232,22 @@
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
-" xmlns:persistence=\"http://jboss.com/products/seam/persistence"
-"\"\n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
"\n"
" <persistence:managed-persistence-context name=\"productDatabase\" \n"
" scope=\"session\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"productEntityManagerFactory\"/> \n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
+"\n"
+" <persistence:managed-persistence-context name=\"productDatabase\" \n"
+" scope=\"session\"\n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
+"\n"
+"</components>]]>"
#. Tag: programlisting
#: Xml.xml:128
@@ -285,23 +257,26 @@
" \n"
" <component name=\"productDatabase\"\n"
" scope=\"session\"\n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"productEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
" </component>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" \n"
+" <component name=\"productDatabase\"\n"
+" scope=\"session\"\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
+" </component>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:130
#, no-c-format
-msgid ""
-"It is common to use the <literal>auto-create</literal> option for "
-"infrastructural objects like persistence contexts, which saves you from "
-"having to explicitly specify <literal>create=true</literal> when you use the "
-"<literal>@In</literal> annotation."
+msgid "It is common to use the <literal>auto-create</literal> option for infrastructural objects like persistence contexts, which saves you from having to explicitly specify <literal>create=true</literal> when you use the <literal>@In</literal> annotation."
msgstr ""
#. Tag: programlisting
@@ -309,16 +284,22 @@
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
-" xmlns:persistence=\"http://jboss.com/products/seam/persistence"
-"\"\n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
"\n"
" <persistence:managed-persistence-context name=\"productDatabase\" \n"
" auto-create=\"true\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"productEntityManagerFactory\"/> \n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
+" xmlns:persistence=\"http://jboss.com/products/seam/persistence\"\n"
+"\n"
+" <persistence:managed-persistence-context name=\"productDatabase\" \n"
+" auto-create=\"true\"\n"
+" persistence-unit-jndi-name=\"java:/productEntityManagerFactory\"/> \n"
+"\n"
+"</components>]]>"
#. Tag: programlisting
#: Xml.xml:139
@@ -328,22 +309,26 @@
" \n"
" <component name=\"productDatabase\"\n"
" auto-create=\"true\"\n"
-" class=\"org.jboss.seam.persistence.ManagedPersistenceContext"
-"\">\n"
-" <property name=\"persistenceUnitJndiName\">java:/"
-"productEntityManagerFactory</property>\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
" </component>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" \n"
+" <component name=\"productDatabase\"\n"
+" auto-create=\"true\"\n"
+" class=\"org.jboss.seam.persistence.ManagedPersistenceContext\">\n"
+" <property name=\"persistenceUnitJndiName\">java:/productEntityManagerFactory</property>\n"
+" </component>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:141
#, no-c-format
-msgid ""
-"The <literal><factory></literal> declaration lets you specify a value "
-"or method binding expression that will be evaluated to initialize the value "
-"of a context variable when it is first referenced."
+msgid "The <literal><factory></literal> declaration lets you specify a value or method binding expression that will be evaluated to initialize the value of a context variable when it is first referenced."
msgstr ""
#. Tag: programlisting
@@ -352,17 +337,20 @@
msgid ""
"<![CDATA[<components>\n"
"\n"
-" <factory name=\"contact\" method=\"#{contactManager.loadContact}\" scope="
-"\"CONVERSATION\"/>\n"
+" <factory name=\"contact\" method=\"#{contactManager.loadContact}\" scope=\"CONVERSATION\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"contact\" method=\"#{contactManager.loadContact}\" scope=\"CONVERSATION\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:149
#, no-c-format
-msgid ""
-"You can create an \"alias\" (a second name) for a Seam component like so:"
+msgid "You can create an \"alias\" (a second name) for a Seam component like so:"
msgstr ""
#. Tag: programlisting
@@ -375,6 +363,11 @@
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"user\" value=\"#{actor}\" scope=\"STATELESS\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:155
@@ -388,18 +381,20 @@
msgid ""
"<![CDATA[<components>\n"
"\n"
-" <factory name=\"contact\" value=\"#{contactManager.contact}\" scope="
-"\"STATELESS\"/>\n"
+" <factory name=\"contact\" value=\"#{contactManager.contact}\" scope=\"STATELESS\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"contact\" value=\"#{contactManager.contact}\" scope=\"STATELESS\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:161
#, no-c-format
-msgid ""
-"It is especially common to see the use of <literal>auto-create=\"true\"</"
-"literal> with the <literal><factory></literal> declaration:"
+msgid "It is especially common to see the use of <literal>auto-create=\"true\"</literal> with the <literal><factory></literal> declaration:"
msgstr ""
#. Tag: programlisting
@@ -408,23 +403,20 @@
msgid ""
"<![CDATA[<components>\n"
"\n"
-" <factory name=\"session\" value=\"#{entityManager.delegate}\" scope="
-"\"STATELESS\" auto-create=\"true\"/>\n"
+" <factory name=\"session\" value=\"#{entityManager.delegate}\" scope=\"STATELESS\" auto-create=\"true\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+"\n"
+" <factory name=\"session\" value=\"#{entityManager.delegate}\" scope=\"STATELESS\" auto-create=\"true\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:168
#, no-c-format
-msgid ""
-"Sometimes we want to reuse the same <literal>components.xml</literal> file "
-"with minor changes during both deployment and testing. Seam lets you place "
-"wildcards of the form <literal>@wildcard@</literal> in the "
-"<literal>components.xml</literal> file which can be replaced either by your "
-"Ant build script (at deployment time) or by providing a file named "
-"<literal>components.properties</literal> in the classpath (at development "
-"time). You'll see this approach used in the Seam examples."
+msgid "Sometimes we want to reuse the same <literal>components.xml</literal> file with minor changes during both deployment and testing. Seam lets you place wildcards of the form <literal>@wildcard@</literal> in the <literal>components.xml</literal> file which can be replaced either by your Ant build script (at deployment time) or by providing a file named <literal>components.properties</literal> in the classpath (at development time). You'll see this approach used in the Seam examples."
msgstr ""
#. Tag: title
@@ -436,15 +428,7 @@
#. Tag: para
#: Xml.xml:180
#, no-c-format
-msgid ""
-"If you have a large number of components that need to be configured in XML, "
-"it makes much more sense to split up the information in <literal>components."
-"xml</literal> into many small files. Seam lets you put configuration for a "
-"class named, for example, <literal>com.helloworld.Hello</literal> in a "
-"resource named <literal>com/helloworld/Hello.component.xml</literal>. (You "
-"might be familiar with this pattern, since it is the same one we use in "
-"Hibernate.) The root element of the file may be either a <literal><"
-"components></literal> or <literal><component></literal> element."
+msgid "If you have a large number of components that need to be configured in XML, it makes much more sense to split up the information in <literal>components.xml</literal> into many small files. Seam lets you put configuration for a class named, for example, <literal>com.helloworld.Hello</literal> in a resource named <literal>com/helloworld/Hello.component.xml</literal>. (You might be familiar with this pattern, since it is the same one we use in Hibernate.) The root element of the file may be either a <literal><components></literal> or <literal><component></literal> element."
msgstr ""
#. Tag: para
@@ -464,13 +448,17 @@
" <factory name=\"message\" value=\"#{hello.message}\"/>\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components>\n"
+" <component class=\"com.helloworld.Hello\" name=\"hello\">\n"
+" <property name=\"name\">#{user.name}</property>\n"
+" </component>\n"
+" <factory name=\"message\" value=\"#{hello.message}\"/>\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:195
#, no-c-format
-msgid ""
-"The second option only lets you define or configure one component, but is "
-"less noisy:"
+msgid "The second option only lets you define or configure one component, but is less noisy:"
msgstr ""
#. Tag: programlisting
@@ -481,22 +469,20 @@
" <property name=\"name\">#{user.name}</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"hello\">\n"
+" <property name=\"name\">#{user.name}</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:201
#, no-c-format
-msgid ""
-"In the second option, the class name is implied by the file in which the "
-"component definition appears."
+msgid "In the second option, the class name is implied by the file in which the component definition appears."
msgstr ""
#. Tag: para
#: Xml.xml:206
#, no-c-format
-msgid ""
-"Alternatively, you may put configuration for all classes in the <literal>com."
-"helloworld</literal> package in <literal>com/helloworld/components.xml</"
-"literal>."
+msgid "Alternatively, you may put configuration for all classes in the <literal>com.helloworld</literal> package in <literal>com/helloworld/components.xml</literal>."
msgstr ""
#. Tag: title
@@ -508,22 +494,20 @@
#. Tag: para
#: Xml.xml:214
#, no-c-format
-msgid ""
-"Properties of string, primitive or primitive wrapper type may be configured "
-"just as you would expect:"
+msgid "Properties of string, primitive or primitive wrapper type may be configured just as you would expect:"
msgstr ""
#. Tag: programlisting
#: Xml.xml:218
#, no-c-format
msgid "<![CDATA[org.jboss.seam.core.manager.conversationTimeout 60000]]>"
-msgstr ""
+msgstr "<![CDATA[org.jboss.seam.core.manager.conversationTimeout 60000]]>"
#. Tag: programlisting
#: Xml.xml:220
#, no-c-format
msgid "<![CDATA[<core:manager conversation-timeout=\"60000\"/>]]>"
-msgstr ""
+msgstr "<![CDATA[<core:manager conversation-timeout=\"60000\"/>]]>"
#. Tag: programlisting
#: Xml.xml:222
@@ -533,6 +517,9 @@
" <property name=\"conversationTimeout\">60000</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"org.jboss.seam.core.manager\">\n"
+" <property name=\"conversationTimeout\">60000</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:224
@@ -543,10 +530,8 @@
#. Tag: programlisting
#: Xml.xml:228
#, no-c-format
-msgid ""
-"<![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return."
-"jpdl.xml, inventory.jpdl.xml]]>"
-msgstr ""
+msgid "<![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return.jpdl.xml, inventory.jpdl.xml]]>"
+msgstr "<![CDATA[org.jboss.seam.bpm.jbpm.processDefinitions order.jpdl.xml, return.jpdl.xml, inventory.jpdl.xml]]>"
#. Tag: programlisting
#: Xml.xml:230
@@ -560,6 +545,13 @@
" </bpm:process-definitions>\n"
"</bpm:jbpm>]]>"
msgstr ""
+"<![CDATA[<bpm:jbpm>\n"
+" <bpm:process-definitions>\n"
+" <value>order.jpdl.xml</value>\n"
+" <value>return.jpdl.xml</value>\n"
+" <value>inventory.jpdl.xml</value>\n"
+" </bpm:process-definitions>\n"
+"</bpm:jbpm>]]>"
#. Tag: programlisting
#: Xml.xml:232
@@ -573,13 +565,18 @@
" </property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"org.jboss.seam.bpm.jbpm\">\n"
+" <property name=\"processDefinitions\">\n"
+" <value>order.jpdl.xml</value>\n"
+" <value>return.jpdl.xml</value>\n"
+" <value>inventory.jpdl.xml</value>\n"
+" </property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:234
#, no-c-format
-msgid ""
-"Even maps with String-valued keys and string or primitive values are "
-"supported:"
+msgid "Even maps with String-valued keys and string or primitive values are supported:"
msgstr ""
#. Tag: programlisting
@@ -594,24 +591,24 @@
" </property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"issueEditor\">\n"
+" <property name=\"issueStatuses\">\n"
+" <key>open</key> <value>open issue</value>\n"
+" <key>resolved</key> <value>issue resolved by developer</value>\n"
+" <key>closed</key> <value>resolution accepted by user</value>\n"
+" </property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:240
#, no-c-format
-msgid ""
-"When configuring multi-valued properties, by default, Seam will preserve the "
-"order in which you place the attributes in <literal>components.xml</literal> "
-"(unless you use a <literal>SortedSet</literal>/<literal>SortedMap</literal> "
-"then Seam will use <literal>TreeMap</literal>/<literal>TreeSet</literal>). "
-"If the property has a concrete type (for example <literal>LinkedList</"
-"literal> Seam will use that type."
+msgid "When configuring multi-valued properties, by default, Seam will preserve the order in which you place the attributes in <literal>components.xml</literal> (unless you use a <literal>SortedSet</literal>/<literal>SortedMap</literal> then Seam will use <literal>TreeMap</literal>/<literal>TreeSet</literal>). If the property has a concrete type (for example <literal>LinkedList</literal> Seam will use that type."
msgstr ""
#. Tag: para
#: Xml.xml:246
#, no-c-format
-msgid ""
-"You can also override the type by specifying a fully qualified class name:"
+msgid "You can also override the type by specifying a fully qualified class name:"
msgstr ""
#. Tag: programlisting
@@ -626,16 +623,18 @@
" </property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"issueEditor\">\n"
+" <property name=\"issueStatusOptions\" type=\"java.util.LinkedHashMap\">\n"
+" <key>open</key> <value>open issue</value>\n"
+" <key>resolved</key> <value>issue resolved by developer</value>\n"
+" <key>closed</key> <value>resolution accepted by user</value>\n"
+" </property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:252
#, no-c-format
-msgid ""
-"Finally, you may wire together components using a value-binding expression. "
-"Note that this is quite different to injection using <literal>@In</literal>, "
-"since it happens at component instantiation time instead of invocation time. "
-"It is therefore much more similar to the dependency injection facilities "
-"offered by traditional IoC containers like JSF or Spring."
+msgid "Finally, you may wire together components using a value-binding expression. Note that this is quite different to injection using <literal>@In</literal>, since it happens at component instantiation time instead of invocation time. It is therefore much more similar to the dependency injection facilities offered by traditional IoC containers like JSF or Spring."
msgstr ""
#. Tag: programlisting
@@ -645,6 +644,8 @@
"<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\"\n"
" rule-base=\"#{policyPricingRules}\"/>]]>"
msgstr ""
+"<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\"\n"
+" rule-base=\"#{policyPricingRules}\"/>]]>"
#. Tag: programlisting
#: Xml.xml:262
@@ -655,14 +656,15 @@
" <property name=\"ruleBase\">#{policyPricingRules}</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"policyPricingWorkingMemory\"\n"
+" class=\"org.jboss.seam.drools.ManagedWorkingMemory\">\n"
+" <property name=\"ruleBase\">#{policyPricingRules}</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:264
#, no-c-format
-msgid ""
-"Seam also resolves an EL expression string prior to assigning the initial "
-"value to the bean property of the component. So you can inject some "
-"contextual data into your components."
+msgid "Seam also resolves an EL expression string prior to assigning the initial value to the bean property of the component. So you can inject some contextual data into your components."
msgstr ""
#. Tag: programlisting
@@ -670,22 +672,17 @@
#, no-c-format
msgid ""
"<![CDATA[<component name=\"greeter\" class=\"com.example.action.Greeter\">\n"
-" <property name=\"message\">Nice to see you, #{identity.username}!</"
-"property>\n"
+" <property name=\"message\">Nice to see you, #{identity.username}!</property>\n"
"</component>]]>"
msgstr ""
+"<![CDATA[<component name=\"greeter\" class=\"com.example.action.Greeter\">\n"
+" <property name=\"message\">Nice to see you, #{identity.username}!</property>\n"
+"</component>]]>"
#. Tag: para
#: Xml.xml:271
#, no-c-format
-msgid ""
-"However, there is one important exception. If the type of the property to "
-"which the initial value is being assigned is either a Seam "
-"<literal>ValueExpression</literal> or <literal>MethodExpression</literal>, "
-"then the evaluation of the EL is deferred. Instead, the appropriate "
-"expression wrapper is created and assigned to the property. The message "
-"templates on the Home component from the Seam Application Framework serve as "
-"an example."
+msgid "However, there is one important exception. If the type of the property to which the initial value is being assigned is either a Seam <literal>ValueExpression</literal> or <literal>MethodExpression</literal>, then the evaluation of the EL is deferred. Instead, the appropriate expression wrapper is created and assigned to the property. The message templates on the Home component from the Seam Application Framework serve as an example."
msgstr ""
#. Tag: programlisting
@@ -693,40 +690,29 @@
#, no-c-format
msgid ""
"<![CDATA[<framework:entity-home name=\"myEntityHome\"\n"
-" class=\"com.example.action.MyEntityHome\" entity-class=\"com.example."
-"model.MyEntity\"\n"
-" created-message=\"'#{myEntityHome.instance.name}' has been successfully "
-"added.\"/>]]>"
+" class=\"com.example.action.MyEntityHome\" entity-class=\"com.example.model.MyEntity\"\n"
+" created-message=\"'#{myEntityHome.instance.name}' has been successfully added.\"/>]]>"
msgstr ""
+"<![CDATA[<framework:entity-home name=\"myEntityHome\"\n"
+" class=\"com.example.action.MyEntityHome\" entity-class=\"com.example.model.MyEntity\"\n"
+" created-message=\"'#{myEntityHome.instance.name}' has been successfully added.\"/>]]>"
#. Tag: para
#: Xml.xml:281
#, no-c-format
-msgid ""
-"Inside the component, you can access the expression string by calling "
-"<literal>getExpressionString()</literal> on the <literal>ValueExpression</"
-"literal> or <literal>MethodExpression</literal>. If the property is a "
-"<literal>ValueExpression</literal>, you can resolve the value using "
-"<literal>getValue()</literal> and if the property is a "
-"<literal>MethodExpression</literal>, you can invoke the method using "
-"<literal>invoke(Object args...)</literal>. Obviously, to assign a value to a "
-"<literal>MethodExpression</literal> property, the entire initial value must "
-"be a single EL expression."
+msgid "Inside the component, you can access the expression string by calling <literal>getExpressionString()</literal> on the <literal>ValueExpression</literal> or <literal>MethodExpression</literal>. If the property is a <literal>ValueExpression</literal>, you can resolve the value using <literal>getValue()</literal> and if the property is a <literal>MethodExpression</literal>, you can invoke the method using <literal>invoke(Object args...)</literal>. Obviously, to assign a value to a <literal>MethodExpression</literal> property, the entire initial value must be a single EL expression."
msgstr ""
#. Tag: title
#: Xml.xml:294
#, no-c-format
msgid "Using XML Namespaces"
-msgstr ""
+msgstr "Uso dei namespace XML"
#. Tag: para
#: Xml.xml:295
#, no-c-format
-msgid ""
-"Throughout the examples, there have been two competing ways of declaring "
-"components: with and without the use of XML namespaces. The following shows "
-"a typical <literal>components.xml</literal> file without namespaces:"
+msgid "Throughout the examples, there have been two competing ways of declaring components: with and without the use of XML namespaces. The following shows a typical <literal>components.xml</literal> file without namespaces:"
msgstr ""
#. Tag: programlisting
@@ -735,8 +721,7 @@
msgid ""
"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
-" xsi:schemaLocation=\"http://jboss.com/products/seam/components "
-"http://jboss.com/products/seam/components-2.1.xsd\">\n"
+" xsi:schemaLocation=\"http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
"\n"
" <component class=\"org.jboss.seam.core.init\">\n"
" <property name=\"debug\">true</property>\n"
@@ -745,13 +730,21 @@
" \n"
"</components>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xsi:schemaLocation=\"http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
+"\n"
+" <component class=\"org.jboss.seam.core.init\">\n"
+" <property name=\"debug\">true</property>\n"
+" <property name=\"jndiPattern\">@jndiPattern@</property>\n"
+" </component>\n"
+" \n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:303
#, no-c-format
-msgid ""
-"As you can see, this is somewhat verbose. Even worse, the component and "
-"attribute names cannot be validated at development time."
+msgid "As you can see, this is somewhat verbose. Even worse, the component and attribute names cannot be validated at development time."
msgstr ""
#. Tag: para
@@ -769,47 +762,41 @@
" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
" xsi:schemaLocation=\n"
-" \"http://jboss.com/products/seam/core http://jboss.com/"
-"products/seam/core-2.1.xsd \n"
-" http://jboss.com/products/seam/components http://jboss.com/"
-"products/seam/components-2.1.xsd\">\n"
+" \"http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.1.xsd \n"
+" http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
"\n"
" <core:init debug=\"true\" jndi-pattern=\"@jndiPattern@\"/>\n"
"\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
+"<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:core=\"http://jboss.com/products/seam/core\"\n"
+" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
+" xsi:schemaLocation=\n"
+" \"http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.1.xsd \n"
+" http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.1.xsd\">\n"
+"\n"
+" <core:init debug=\"true\" jndi-pattern=\"@jndiPattern@\"/>\n"
+"\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:312
#, no-c-format
-msgid ""
-"Even though the schema declarations are verbose, the actual XML content is "
-"lean and easy to understand. The schemas provide detailed information about "
-"each component and the attributes available, allowing XML editors to offer "
-"intelligent autocomplete. The use of namespaced elements makes generating "
-"and maintaining correct <literal>components.xml</literal> files much simpler."
+msgid "Even though the schema declarations are verbose, the actual XML content is lean and easy to understand. The schemas provide detailed information about each component and the attributes available, allowing XML editors to offer intelligent autocomplete. The use of namespaced elements makes generating and maintaining correct <literal>components.xml</literal> files much simpler."
msgstr ""
#. Tag: para
#: Xml.xml:319
#, no-c-format
-msgid ""
-"Now, this works great for the built-in Seam components, but what about user "
-"components? There are two options. First, Seam supports mixing the two "
-"models, allowing the use of the generic <literal><component></literal> "
-"declarations for user components, along with namespaced declarations for "
-"built-in components. But even better, Seam allows you to quickly declare "
-"namespaces for your own components."
+msgid "Now, this works great for the built-in Seam components, but what about user components? There are two options. First, Seam supports mixing the two models, allowing the use of the generic <literal><component></literal> declarations for user components, along with namespaced declarations for built-in components. But even better, Seam allows you to quickly declare namespaces for your own components."
msgstr ""
#. Tag: para
#: Xml.xml:326
#, no-c-format
-msgid ""
-"Any Java package can be associated with an XML namespace by annotating the "
-"package with the <literal>@Namespace</literal> annotation. (Package-level "
-"annotations are declared in a file named <literal>package-info.java</"
-"literal> in the package directory.) Here is an example from the seampay demo:"
+msgid "Any Java package can be associated with an XML namespace by annotating the package with the <literal>@Namespace</literal> annotation. (Package-level annotations are declared in a file named <literal>package-info.java</literal> in the package directory.) Here is an example from the seampay demo:"
msgstr ""
#. Tag: programlisting
@@ -821,13 +808,15 @@
"\n"
"import org.jboss.seam.annotations.Namespace;"
msgstr ""
+"@Namespace(value=\"http://jboss.com/products/seam/examples/seampay\")\n"
+"package org.jboss.seam.example.seampay;\n"
+"\n"
+"import org.jboss.seam.annotations.Namespace;"
#. Tag: para
#: Xml.xml:334
#, no-c-format
-msgid ""
-"That is all you need to do to use the namespaced style in "
-"<literal>components.xml</literal>! Now we can write:"
+msgid "That is all you need to do to use the namespaced style in <literal>components.xml</literal>! Now we can write:"
msgstr ""
#. Tag: programlisting
@@ -839,8 +828,7 @@
" ... >\n"
"\n"
" <pay:payment-home new-instance=\"#{newPayment}\"\n"
-" created-message=\"Created a new payment to #"
-"{newPayment.payee}\" />\n"
+" created-message=\"Created a new payment to #{newPayment.payee}\" />\n"
"\n"
" <pay:payment name=\"newPayment\"\n"
" payee=\"Somebody\"\n"
@@ -850,12 +838,26 @@
" ...\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:pay=\"http://jboss.com/products/seam/examples/seampay\"\n"
+" ... >\n"
+"\n"
+" <pay:payment-home new-instance=\"#{newPayment}\"\n"
+" created-message=\"Created a new payment to #{newPayment.payee}\" />\n"
+"\n"
+" <pay:payment name=\"newPayment\"\n"
+" payee=\"Somebody\"\n"
+" account=\"#{selectedAccount}\"\n"
+" payment-date=\"#{currentDatetime}\"\n"
+" created-date=\"#{currentDatetime}\" />\n"
+" ...\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:341
#, no-c-format
msgid "<para>Or:</para>"
-msgstr ""
+msgstr "<para>Oppure:</para>"
#. Tag: programlisting
#: Xml.xml:343
@@ -867,8 +869,7 @@
"\n"
" <pay:payment-home>\n"
" <pay:new-instance>\"#{newPayment}\"</pay:new-instance>\n"
-" <pay:created-message>Created a new payment to #{newPayment.payee}</"
-"pay:created-message>\n"
+" <pay:created-message>Created a new payment to #{newPayment.payee}</pay:created-message>\n"
" </pay:payment-home>\n"
" \n"
" <pay:payment name=\"newPayment\">\n"
@@ -880,14 +881,28 @@
" ...\n"
"</components>]]>"
msgstr ""
+"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
+" xmlns:pay=\"http://jboss.com/products/seam/examples/seampay\"\n"
+" ... >\n"
+"\n"
+" <pay:payment-home>\n"
+" <pay:new-instance>\"#{newPayment}\"</pay:new-instance>\n"
+" <pay:created-message>Created a new payment to #{newPayment.payee}</pay:created-message>\n"
+" </pay:payment-home>\n"
+" \n"
+" <pay:payment name=\"newPayment\">\n"
+" <pay:payee>Somebody\"</pay:payee>\n"
+" <pay:account>#{selectedAccount}</pay:account>\n"
+" <pay:payment-date>#{currentDatetime}</pay:payment-date>\n"
+" <pay:created-date>#{currentDatetime}</pay:created-date>\n"
+" </pay:payment>\n"
+" ...\n"
+"</components>]]>"
#. Tag: para
#: Xml.xml:345
#, no-c-format
-msgid ""
-"These examples illustrate the two usage models of a namespaced element. In "
-"the first declaration, the <literal><pay:payment-home></literal> "
-"references the <literal>paymentHome</literal> component:"
+msgid "These examples illustrate the two usage models of a namespaced element. In the first declaration, the <literal><pay:payment-home></literal> references the <literal>paymentHome</literal> component:"
msgstr ""
#. Tag: programlisting
@@ -903,23 +918,25 @@
" ... \n"
"}]]>"
msgstr ""
+"<![CDATA[package org.jboss.seam.example.seampay;\n"
+"...\n"
+"@Name(\"paymentHome\")\n"
+"public class PaymentController\n"
+" extends EntityHome<Payment>\n"
+"{\n"
+" ... \n"
+"}]]>"
#. Tag: para
#: Xml.xml:353
#, no-c-format
-msgid ""
-"The element name is the hyphenated form of the component name. The "
-"attributes of the element are the hyphenated form of the property names."
+msgid "The element name is the hyphenated form of the component name. The attributes of the element are the hyphenated form of the property names."
msgstr ""
#. Tag: para
#: Xml.xml:358
#, no-c-format
-msgid ""
-"In the second declaration, the <literal><pay:payment></literal> "
-"element refers to the <literal>Payment</literal> class in the <literal>org."
-"jboss.seam.example.seampay</literal> package. In this case <literal>Payment</"
-"literal> is an entity that is being declared as a Seam component:"
+msgid "In the second declaration, the <literal><pay:payment></literal> element refers to the <literal>Payment</literal> class in the <literal>org.jboss.seam.example.seampay</literal> package. In this case <literal>Payment</literal> is an entity that is being declared as a Seam component:"
msgstr ""
#. Tag: programlisting
@@ -935,97 +952,96 @@
" ...\n"
"}]]>"
msgstr ""
+"<![CDATA[package org.jboss.seam.example.seampay;\n"
+"...\n"
+"@Name(\"paymentHome\")\n"
+"public class PaymentController\n"
+" extends EntityHome<Payment>\n"
+"{\n"
+" ... \n"
+"}]]>"
#. Tag: para
#: Xml.xml:366
#, no-c-format
-msgid ""
-"If we want validation and autocompletion to work for user-defined "
-"components, we will need a schema. Seam does not yet provide a mechanism to "
-"automatically generate a schema for a set of components, so it is necessary "
-"to generate one manually. The schema definitions for the standard Seam "
-"packages can be used for guidance."
+msgid "If we want validation and autocompletion to work for user-defined components, we will need a schema. Seam does not yet provide a mechanism to automatically generate a schema for a set of components, so it is necessary to generate one manually. The schema definitions for the standard Seam packages can be used for guidance."
msgstr ""
#. Tag: para
#: Xml.xml:373
#, no-c-format
msgid "The following are the the namespaces used by Seam:"
-msgstr ""
+msgstr "Seam utilizza i seguenti namespace:"
#. Tag: para
#: Xml.xml:377
#, no-c-format
-msgid ""
-"components — <literal>http://jboss.com/products/seam/components</"
-"literal>"
-msgstr ""
+msgid "components — <literal>http://jboss.com/products/seam/components</literal>"
+msgstr "components — <literal>http://jboss.com/products/seam/components</literal>"
#. Tag: para
#: Xml.xml:380
#, no-c-format
msgid "core — <literal>http://jboss.com/products/seam/core</literal>"
-msgstr ""
+msgstr "core — <literal>http://jboss.com/products/seam/core</literal>"
#. Tag: para
#: Xml.xml:383
#, no-c-format
msgid "drools — <literal>http://jboss.com/products/seam/drools</literal>"
-msgstr ""
+msgstr "drools — <literal>http://jboss.com/products/seam/drools</literal>"
#. Tag: para
#: Xml.xml:386
#, no-c-format
-msgid ""
-"framework — <literal>http://jboss.com/products/seam/framework</literal>"
-msgstr ""
+msgid "framework — <literal>http://jboss.com/products/seam/framework</literal>"
+msgstr "framework — <literal>http://jboss.com/products/seam/framework</literal>"
#. Tag: para
#: Xml.xml:389
#, no-c-format
msgid "jms — <literal>http://jboss.com/products/seam/jms</literal>"
-msgstr ""
+msgstr "jms — <literal>http://jboss.com/products/seam/jms</literal>"
#. Tag: para
#: Xml.xml:392
#, no-c-format
-msgid ""
-"remoting — <literal>http://jboss.com/products/seam/remoting</literal>"
-msgstr ""
+msgid "remoting — <literal>http://jboss.com/products/seam/remoting</literal>"
+msgstr "remoting — <literal>http://jboss.com/products/seam/remoting</literal>"
#. Tag: para
#: Xml.xml:395
#, no-c-format
msgid "theme — <literal>http://jboss.com/products/seam/theme</literal>"
-msgstr ""
+msgstr "theme — <literal>http://jboss.com/products/seam/theme</literal>"
#. Tag: para
#: Xml.xml:398
#, no-c-format
-msgid ""
-"security — <literal>http://jboss.com/products/seam/security</literal>"
-msgstr ""
+msgid "security — <literal>http://jboss.com/products/seam/security</literal>"
+msgstr "security — <literal>http://jboss.com/products/seam/security</literal>"
#. Tag: para
#: Xml.xml:401
#, no-c-format
msgid "mail — <literal>http://jboss.com/products/seam/mail</literal>"
-msgstr ""
+msgstr "mail — <literal>http://jboss.com/products/seam/mail</literal>"
#. Tag: para
#: Xml.xml:404
#, no-c-format
msgid "web — <literal>http://jboss.com/products/seam/web</literal>"
-msgstr ""
+msgstr "web — <literal>http://jboss.com/products/seam/web</literal>"
#. Tag: para
#: Xml.xml:407
#, no-c-format
msgid "pdf — <literal>http://jboss.com/products/seam/pdf</literal>"
-msgstr ""
+msgstr "pdf — <literal>http://jboss.com/products/seam/pdf</literal>"
#. Tag: para
#: Xml.xml:410
#, no-c-format
msgid "spring — <literal>http://jboss.com/products/seam/spring</literal>"
-msgstr ""
+msgstr "spring — <literal>http://jboss.com/products/seam/spring</literal>"
+
More information about the seam-commits
mailing list