[seam-commits] Seam SVN: r9948 - trunk/doc/Seam_Reference_Guide/it-IT.
seam-commits at lists.jboss.org
seam-commits at lists.jboss.org
Sun Jan 18 10:27:23 EST 2009
Author: nico.ben
Date: 2009-01-18 10:27:22 -0500 (Sun, 18 Jan 2009)
New Revision: 9948
Modified:
trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po
trunk/doc/Seam_Reference_Guide/it-IT/Cache.po
trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po
trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po
trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po
trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
trunk/doc/Seam_Reference_Guide/it-IT/Events.po
trunk/doc/Seam_Reference_Guide/it-IT/Excel.po
trunk/doc/Seam_Reference_Guide/it-IT/Framework.po
trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po
trunk/doc/Seam_Reference_Guide/it-IT/Itext.po
trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
trunk/doc/Seam_Reference_Guide/it-IT/Jms.po
trunk/doc/Seam_Reference_Guide/it-IT/Persistence.po
trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
trunk/doc/Seam_Reference_Guide/it-IT/Rss.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/Annotations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Annotations.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-01-05 00:18+0000\n"
-"PO-Revision-Date: 2009-01-13 22:36+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:10+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -583,7 +583,7 @@
#. Tag: para
#: Annotations.xml:434
#, no-c-format
-msgid "The next annotation supports the <emphasis>manager component</emphasis> pattern, where a Seam component that manages the lifecycle of an instance of some other class that is to be injected. It appears on a component getter method."
+msgid "The next annotation supports the <emphasis>manager component</emphasis> pattern; a Seam component manages the lifecycle of an instance of some other class that is to be injected. It appears on a component getter method."
msgstr "La prossima annotazione supporta il pattern <emphasis>manager component</emphasis>, dove un componente Seam che gestisce il ciclo di vita di un'istanza di qualche altra classe deve essere iniettata. Appare sul metodo getter del componente."
#. Tag: literal
@@ -607,7 +607,7 @@
#. Tag: para
#: Annotations.xml:457
#, no-c-format
-msgid "The next annotation supports the <emphasis>factory component</emphasis> pattern, where a Seam component is responsible for initializing the value of a context variable. This is especially useful for initializing any state needed for rendering the response to a non-faces request. It appears on a component method."
+msgid "The next annotation supports the <emphasis>factory component</emphasis> pattern; a Seam component is responsible for initializing the value of a context variable. This is especially useful for initializing any state needed for rendering the response to a non-faces request. It appears on a component method."
msgstr "La prossima annotazione supporta il pattern <emphasis>factory component</emphasis> dove un componente Seam è responsabile dell'inizializzazione del valore di una variabile di contesto. Questo è utile in particolare per inizializzare qualsiasi stato occorrente per il rendering della risposta in una richiesta non-faces. Appare su un metodo di componente."
#. Tag: literal
@@ -890,7 +890,7 @@
#: Annotations.xml:702
#, no-c-format
msgid "<literal>join</literal> — determines the behavior when a long-running conversation is already in progress. If <literal>true</literal>, the context is propagated. If <literal>false</literal>, an exception is thrown. Default to <literal>false</literal>. This setting is ignored when <literal>nested=true</literal> is specified."
-msgstr "<literal>join</literal> — determina il comportamento quando una conversazione long-running è già attiva. Se <literal>true</literal>, il contesto viene propagato. Se <literal>false</literal>, viene lanciata un'eccezione. Di default è <literal>falseliteral>. Quest'impostazione è ignorata quando è specificato <literal>nested=true</literal>."
+msgstr "<literal>join</literal> — determina il comportamento quando una conversazione long-running è già attiva. Se <literal>true</literal>, il contesto viene propagato. Se <literal>false</literal>, viene lanciata un'eccezione. Di default è <literal>false</literal>. Quest'impostazione è ignorata quando è specificato <literal>nested=true</literal>."
#. Tag: para
#: Annotations.xml:713
@@ -910,7 +910,7 @@
#: Annotations.xml:728
#, no-c-format
msgid "<literal>pageflow</literal> — a process definition name of a jBPM process definition deployed via <literal>org.jboss.seam.bpm.jbpm.pageflowDefinitions.</literal>"
-msgstr "<literal>pageflow</literal> — un nome di definizione di processo jBPM deployato via <literal>org.jboss.seam.bpm.jbpm.pageflowDefinitions.</literal"
+msgstr "<literal>pageflow</literal> — un nome di definizione di processo jBPM deployato via <literal>org.jboss.seam.bpm.jbpm.pageflowDefinitions.</literal>"
#. Tag: literal
#: Annotations.xml:739
@@ -964,7 +964,7 @@
#. Tag: para
#: Annotations.xml:790
#, no-c-format
-msgid "The jBPM <literal>TaskInstance</literal> will be available in a request context variable named <literal>taskInstance</literal>. The jPBM <literal>ProcessInstance</literal> will be available in a request context variable named <literal>processInstance</literal>. (Of course, these objects are available for injection via <literal>@In</literal>.)"
+msgid "The jBPM <literal>TaskInstance</literal> will be available in a request context variable named <literal>taskInstance</literal>. The jBPM <literal>ProcessInstance</literal> will be available in a request context variable named <literal>processInstance</literal>. (Of course, these objects are available for injection via <literal>@In</literal>.)"
msgstr "La <literal>TaskInstance</literal> di jBPM sarà disponibile in una variabile di contesto di richiesta chiamato <literal>taskInstance</literal>. La <literal>ProcessInstance</literal> di jBPM sarà disponibile in una variabile di contesto di richiesta chiamata <literal>processInstance</literal>. (Sicuramente questo oggetti sono disponibili per l'iniezione via <literal>@In</literal>.)"
#. Tag: para
@@ -995,7 +995,7 @@
#. Tag: para
#: Annotations.xml:839
#, no-c-format
-msgid "The jBPM <literal>org.jbpm.taskmgmt.exe.TaskInstance</literal> will be available in a request context variable named <literal>taskInstance</literal>. The jPBM <literal>org.jbpm.graph.exe.ProcessInstance</literal> will be available in a request context variable named <literal>processInstance</literal>."
+msgid "The jBPM <literal>org.jbpm.taskmgmt.exe.TaskInstance</literal> will be available in a request context variable named <literal>taskInstance</literal>. The jBPM <literal>org.jbpm.graph.exe.ProcessInstance</literal> will be available in a request context variable named <literal>processInstance</literal>."
msgstr "La <literal>org.jbpm.taskmgmt.exe.TaskInstance</literal> jBPM sarà disponibile in una variabile di contesto richiesta chiamata <literal>taskInstance</literal>. La <literal>org.jbpm.graph.exe.ProcessInstance</literal> jBPM sarà disponibile in una variabile di contesto richiesta chiamata <literal>processInstance</literal>."
#. Tag: literal
@@ -1308,8 +1308,8 @@
#. Tag: para
#: Annotations.xml:1159
#, no-c-format
-msgid "Indicates that the annotated method may be called from client-side JavaScript. The <literal>exclude</literal> property is optional and allows objects to be excluded from the result's object graph (see the Remoting chapter for more details)."
-msgstr "Indica che il metodo annotato può essere chiamato da JavaScript lato client. La proprietà <literal>exclude</literal>è opzionale e consente agli oggetti di essere esclusi dal grafo dell'oggetto dei risultati (vedere il capitolo Remoting per maggiori dettagli)."
+msgid "Indicates that the annotated method may be called from client-side JavaScript. The <literal>exclude</literal> property is optional and allows objects to be excluded from the result's object graph (see the <xref linkend=\"remoting\"/> chapter for more details)."
+msgstr "Indica che il metodo annotato può essere chiamato da JavaScript lato client. La proprietà <literal>exclude</literal> è opzionale e consente agli oggetti di essere esclusi dal grafo dell'oggetto dei risultati (vedere il capitolo Remoting per maggiori dettagli)."
#. Tag: title
#: Annotations.xml:1173
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Cache.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Cache.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Cache.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,9 +5,9 @@
msgstr ""
"Project-Id-Version: Cache\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-11-06 00:22+0000\n"
-"PO-Revision-Date: 2009-01-04 23:33+0100\n"
-"Last-Translator: \n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:10+0100\n"
+"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: Italian <stefano.travelli at gmail.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -24,10 +24,8 @@
#. Tag: para
#: Cache.xml:7
#, no-c-format
-msgid "In almost all enterprise applications, the database is the primary bottleneck, and the least scalable tier of the runtime environment. People from a PHP/Ruby environment will try to tell you that so-called \"shared nothing\" architectures scale well. While that may be literally true, I don't know of many interesting multi-user applications which can be implemented with no sharing of resources between different nodes of the cluster. What these silly people are really thinking of is a \"share nothing except for the database\" architecture. Of course, sharing the database is the primary problem with scaling a multi-user application—so the claim that this architecture is highly scalable is absurd, and tells you a lot about the kind of applications that these folks spend most of their time working on."
-msgstr ""
-"In quasi tutte le applicazioni gestionali il database è il principale collo di bottiglia e lo strato meno scalabile dell'ambiente di esecuzione. Chi utilizza ambienti PHP/Ruby cercherà di sostenere che le architetture cosiddette \"shared nothing\" (nessuna condivisione) hanno una buona scalabilità. Benché questo possa essere letteralmente vero, non si conoscono molte applicazioni multi utente che possano essere implementate senza la condivisione di risorse tra diversi nodi di un cluster. In effetti ciò a cui questi sprovveduti stanno pensando è un'architettura con \"nessuna condivisione eccetto il database\". Ovviamente condividere il database è il principale problema di scalabilità di una applicazione multi utente, perciò affermare che questa architettura è altamente scalabile è assurdo e ci dice molto sul tipo di applicazioni sul cui sviluppo questi signori spendono la maggior parte del "
-"tempo."
+msgid "In almost all enterprise applications, the database is the primary bottleneck, and the least scalable tier of the runtime environment. People from a PHP/Ruby environment will try to tell you that so-called \"shared nothing\" architectures scale well. While that may be literally true, I don't know of many interesting multi-user applications which can be implemented with no sharing of resources between different nodes of the cluster. What these silly people are really thinking of is a \"share nothing except for the database\" architecture. Of course, sharing the database is the primary problem with scaling a multi-user application — so the claim that this architecture is highly scalable is absurd, and tells you a lot about the kind of applications that these folks spend most of their time working on."
+msgstr "In quasi tutte le applicazioni gestionali il database è il principale collo di bottiglia e lo strato meno scalabile dell'ambiente di esecuzione. Chi utilizza ambienti PHP/Ruby cercherà di sostenere che le architetture cosiddette \"shared nothing\" (nessuna condivisione) hanno una buona scalabilità. Benché questo possa essere letteralmente vero, non si conoscono molte applicazioni multi utente che possano essere implementate senza la condivisione di risorse tra diversi nodi di un cluster. In effetti ciò a cui questi sprovveduti stanno pensando è un'architettura con \"nessuna condivisione eccetto il database\". Ovviamente condividere il database è il principale problema di scalabilità di una applicazione multi utente, perciò affermare che questa architettura è altamente scalabile è assurdo e ci dice molto sul tipo di applicazioni sul cui sviluppo questi signori spendono la maggior parte del tempo."
#. Tag: para
#: Cache.xml:22
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Concepts.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,7 +5,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-12-04 00:58+0000\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
"PO-Revision-Date: 2008-12-12 15:45+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
@@ -22,7 +22,14 @@
#. Tag: para
#: Concepts.xml:6
#, no-c-format
-msgid "The two core concepts in Seam are the notion of a <emphasis>context</emphasis> and the notion of a <emphasis>component</emphasis>. Components are stateful objects, usually EJBs, and an instance of a component is associated with a context, and given a name in that context. <emphasis>Bijection</emphasis> provides a mechanism for aliasing internal component names (instance variables) to contextual names, allowing component trees to be dynamically assembled, and reassembled by Seam."
+msgid ""
+"The two core concepts in Seam are the notion of a <emphasis>context</"
+"emphasis> and the notion of a <emphasis>component</emphasis>. Components are "
+"stateful objects, usually EJBs, and an instance of a component is associated "
+"with a context, and given a name in that context. <emphasis>Bijection</"
+"emphasis> provides a mechanism for aliasing internal component names "
+"(instance variables) to contextual names, allowing component trees to be "
+"dynamically assembled, and reassembled by Seam."
msgstr ""
#. Tag: para
@@ -40,7 +47,11 @@
#. Tag: para
#: Concepts.xml:20
#, no-c-format
-msgid "Seam contexts are created and destroyed by the framework. The application does not control context demarcation via explicit Java API calls. Context are usually implicit. In some cases, however, contexts are demarcated via annotations."
+msgid ""
+"Seam contexts are created and destroyed by the framework. The application "
+"does not control context demarcation via explicit Java API calls. Context "
+"are usually implicit. In some cases, however, contexts are demarcated via "
+"annotations."
msgstr ""
#. Tag: para
@@ -62,36 +73,31 @@
msgstr ""
#. Tag: para
-#: Concepts.xml:33
-#: Concepts.xml:225
+#: Concepts.xml:33 Concepts.xml:225
#, no-c-format
msgid "<para>Page context</para>"
msgstr ""
#. Tag: para
-#: Concepts.xml:36
-#: Concepts.xml:228
+#: Concepts.xml:36 Concepts.xml:228
#, no-c-format
msgid "<para>Conversation context</para>"
msgstr ""
#. Tag: para
-#: Concepts.xml:39
-#: Concepts.xml:231
+#: Concepts.xml:39 Concepts.xml:231
#, no-c-format
msgid "<para>Session context</para>"
msgstr ""
#. Tag: para
-#: Concepts.xml:42
-#: Concepts.xml:234
+#: Concepts.xml:42 Concepts.xml:234
#, no-c-format
msgid "<para>Business process context</para>"
msgstr ""
#. Tag: para
-#: Concepts.xml:45
-#: Concepts.xml:237
+#: Concepts.xml:45 Concepts.xml:237
#, no-c-format
msgid "<para>Application context</para>"
msgstr ""
@@ -99,7 +105,18 @@
#. Tag: para
#: Concepts.xml:49
#, no-c-format
-msgid "You will recognize some of these contexts from servlet and related specifications. However, two of them might be new to you: <emphasis>conversation context</emphasis>, and <emphasis>business process context</emphasis>. One reason state management in web applications is so fragile and error-prone is that the three built-in contexts (request, session and application) are not especially meaningful from the point of view of the business logic. A user login session, for example, is a fairly arbitrary construct in terms of the actual application work flow. Therefore, most Seam components are scoped to the conversation or business process contexts, since they are the contexts which are most meaningful in terms of the application."
+msgid ""
+"You will recognize some of these contexts from servlet and related "
+"specifications. However, two of them might be new to you: "
+"<emphasis>conversation context</emphasis>, and <emphasis>business process "
+"context</emphasis>. One reason state management in web applications is so "
+"fragile and error-prone is that the three built-in contexts (request, "
+"session and application) are not especially meaningful from the point of "
+"view of the business logic. A user login session, for example, is a fairly "
+"arbitrary construct in terms of the actual application work flow. Therefore, "
+"most Seam components are scoped to the conversation or business process "
+"contexts, since they are the contexts which are most meaningful in terms of "
+"the application."
msgstr ""
#. Tag: para
@@ -117,7 +134,13 @@
#. Tag: para
#: Concepts.xml:66
#, no-c-format
-msgid "Components which are truly stateless (stateless session beans, primarily) always live in the stateless context (which is basically the absense of a context since the instance Seam resolves is not stored). Stateless components are not very interesting, and are arguably not very object-oriented. Nevertheless, they do get developed and used and are thus an important part of any Seam application."
+msgid ""
+"Components which are truly stateless (stateless session beans, primarily) "
+"always live in the stateless context (which is basically the absense of a "
+"context since the instance Seam resolves is not stored). Stateless "
+"components are not very interesting, and are arguably not very object-"
+"oriented. Nevertheless, they do get developed and used and are thus an "
+"important part of any Seam application."
msgstr ""
#. Tag: title
@@ -129,13 +152,22 @@
#. Tag: para
#: Concepts.xml:76
#, no-c-format
-msgid "The event context is the \"narrowest\" stateful context, and is a generalization of the notion of the web request context to cover other kinds of events. Nevertheless, the event context associated with the lifecycle of a JSF request is the most important example of an event context, and the one you will work with most often. Components associated with the event context are destroyed at the end of the request, but their state is available and well-defined for at least the lifecycle of the request."
+msgid ""
+"The event context is the \"narrowest\" stateful context, and is a "
+"generalization of the notion of the web request context to cover other kinds "
+"of events. Nevertheless, the event context associated with the lifecycle of "
+"a JSF request is the most important example of an event context, and the one "
+"you will work with most often. Components associated with the event context "
+"are destroyed at the end of the request, but their state is available and "
+"well-defined for at least the lifecycle of the request."
msgstr ""
#. Tag: para
#: Concepts.xml:83
#, no-c-format
-msgid "When you invoke a Seam component via RMI, or Seam Remoting, the event context is created and destroyed just for the invocation."
+msgid ""
+"When you invoke a Seam component via RMI, or Seam Remoting, the event "
+"context is created and destroyed just for the invocation."
msgstr ""
#. Tag: title
@@ -147,7 +179,14 @@
#. Tag: para
#: Concepts.xml:91
#, no-c-format
-msgid "The page context allows you to associate state with a particular instance of a rendered page. You can initialize state in your event listener, or while actually rendering the page, and then have access to it from any event that originates from that page. This is especially useful for functionality like clickable lists, where the list is backed by changing data on the server side. The state is actually serialized to the client, so this construct is extremely robust with respect to multi-window operation and the back button."
+msgid ""
+"The page context allows you to associate state with a particular instance of "
+"a rendered page. You can initialize state in your event listener, or while "
+"actually rendering the page, and then have access to it from any event that "
+"originates from that page. This is especially useful for functionality like "
+"clickable lists, where the list is backed by changing data on the server "
+"side. The state is actually serialized to the client, so this construct is "
+"extremely robust with respect to multi-window operation and the back button."
msgstr ""
#. Tag: title
@@ -159,55 +198,89 @@
#. Tag: para
#: Concepts.xml:103
#, no-c-format
-msgid "The conversation context is a truly central concept in Seam. A <emphasis>conversation</emphasis> is a unit of work from the point of view of the user. It might span several interactions with the user, several requests, and several database transactions. But to the user, a conversation solves a single problem. For example, \"book hotel\", \"approve contract\", \"create order\" are all conversations. You might like to think of a conversation implementing a single \"use case\" or \"user story\", but the relationship is not necessarily quite exact."
+msgid ""
+"The conversation context is a truly central concept in Seam. A "
+"<emphasis>conversation</emphasis> is a unit of work from the point of view "
+"of the user. It might span several interactions with the user, several "
+"requests, and several database transactions. But to the user, a conversation "
+"solves a single problem. For example, \"book hotel\", \"approve contract\", "
+"\"create order\" are all conversations. You might like to think of a "
+"conversation implementing a single \"use case\" or \"user story\", but the "
+"relationship is not necessarily quite exact."
msgstr ""
#. Tag: para
#: Concepts.xml:111
#, no-c-format
-msgid "A conversation holds state associated with \"what the user is doing now, in this window\". A single user may have multiple conversations in progress at any point in time, usually in multiple windows. The conversation context allows us to ensure that state from the different conversations does not collide and cause bugs."
+msgid ""
+"A conversation holds state associated with \"what the user is doing now, in "
+"this window\". A single user may have multiple conversations in progress at "
+"any point in time, usually in multiple windows. The conversation context "
+"allows us to ensure that state from the different conversations does not "
+"collide and cause bugs."
msgstr ""
#. Tag: para
#: Concepts.xml:117
#, no-c-format
-msgid "It might take you some time to get used to thinking of applications in terms of conversations. But once you get used to it, we think you'll love the notion, and never be able to not think in terms of conversations again!"
+msgid ""
+"It might take you some time to get used to thinking of applications in terms "
+"of conversations. But once you get used to it, we think you'll love the "
+"notion, and never be able to not think in terms of conversations again!"
msgstr ""
#. Tag: para
#: Concepts.xml:122
#, no-c-format
-msgid "Some conversations last for just a single request. Conversations that span multiple requests must be demarcated using annotations provided by Seam."
+msgid ""
+"Some conversations last for just a single request. Conversations that span "
+"multiple requests must be demarcated using annotations provided by Seam."
msgstr ""
#. Tag: para
#: Concepts.xml:126
#, no-c-format
-msgid "Some conversations are also <emphasis>tasks</emphasis>. A task is a conversation that is significant in terms of a long-running business process, and has the potential to trigger a business process state transition when it is successfully completed. Seam provides a special set of annotations for task demarcation."
+msgid ""
+"Some conversations are also <emphasis>tasks</emphasis>. A task is a "
+"conversation that is significant in terms of a long-running business "
+"process, and has the potential to trigger a business process state "
+"transition when it is successfully completed. Seam provides a special set of "
+"annotations for task demarcation."
msgstr ""
#. Tag: para
#: Concepts.xml:132
#, no-c-format
-msgid "Conversations may be <emphasis>nested</emphasis>, with one conversation taking place \"inside\" a wider conversation. This is an advanced feature."
+msgid ""
+"Conversations may be <emphasis>nested</emphasis>, with one conversation "
+"taking place \"inside\" a wider conversation. This is an advanced feature."
msgstr ""
#. Tag: para
#: Concepts.xml:136
#, no-c-format
-msgid "Usually, conversation state is actually held by Seam in the servlet session between requests. Seam implements configurable <emphasis>conversation timeout</emphasis>, automatically destroying inactive conversations, and thus ensuring that the state held by a single user login session does not grow without bound if the user abandons conversations."
+msgid ""
+"Usually, conversation state is actually held by Seam in the servlet session "
+"between requests. Seam implements configurable <emphasis>conversation "
+"timeout</emphasis>, automatically destroying inactive conversations, and "
+"thus ensuring that the state held by a single user login session does not "
+"grow without bound if the user abandons conversations."
msgstr ""
#. Tag: para
#: Concepts.xml:142
#, no-c-format
-msgid "Seam serializes processing of concurrent requests that take place in the same long-running conversation context, in the same process."
+msgid ""
+"Seam serializes processing of concurrent requests that take place in the "
+"same long-running conversation context, in the same process."
msgstr ""
#. Tag: para
#: Concepts.xml:146
#, no-c-format
-msgid "Alternatively, Seam may be configured to keep conversational state in the client browser."
+msgid ""
+"Alternatively, Seam may be configured to keep conversational state in the "
+"client browser."
msgstr ""
#. Tag: title
@@ -219,13 +292,19 @@
#. Tag: para
#: Concepts.xml:153
#, no-c-format
-msgid "A session context holds state associated with the user login session. While there are some cases where it is useful to share state between several conversations, we generally frown on the use of session context for holding components other than global information about the logged in user."
+msgid ""
+"A session context holds state associated with the user login session. While "
+"there are some cases where it is useful to share state between several "
+"conversations, we generally frown on the use of session context for holding "
+"components other than global information about the logged in user."
msgstr ""
#. Tag: para
#: Concepts.xml:158
#, no-c-format
-msgid "In a JSR-168 portal environment, the session context represents the portlet session."
+msgid ""
+"In a JSR-168 portal environment, the session context represents the portlet "
+"session."
msgstr ""
#. Tag: title
@@ -237,7 +316,15 @@
#. Tag: para
#: Concepts.xml:165
#, no-c-format
-msgid "The business process context holds state associated with the long running business process. This state is managed and made persistent by the BPM engine (JBoss jBPM). The business process spans multiple interactions with multiple users, so this state is shared between multiple users, but in a well-defined manner. The current task determines the current business process instance, and the lifecycle of the business process is defined externally using a <emphasis>process definition language</emphasis>, so there are no special annotations for business process demarcation."
+msgid ""
+"The business process context holds state associated with the long running "
+"business process. This state is managed and made persistent by the BPM "
+"engine (JBoss jBPM). The business process spans multiple interactions with "
+"multiple users, so this state is shared between multiple users, but in a "
+"well-defined manner. The current task determines the current business "
+"process instance, and the lifecycle of the business process is defined "
+"externally using a <emphasis>process definition language</emphasis>, so "
+"there are no special annotations for business process demarcation."
msgstr ""
#. Tag: title
@@ -249,7 +336,11 @@
#. Tag: para
#: Concepts.xml:177
#, no-c-format
-msgid "The application context is the familiar servlet context from the servlet spec. Application context is mainly useful for holding static information such as configuration data, reference data or metamodels. For example, Seam stores its own configuration and metamodel in the application context."
+msgid ""
+"The application context is the familiar servlet context from the servlet "
+"spec. Application context is mainly useful for holding static information "
+"such as configuration data, reference data or metamodels. For example, Seam "
+"stores its own configuration and metamodel in the application context."
msgstr ""
#. Tag: title
@@ -261,20 +352,32 @@
#. Tag: para
#: Concepts.xml:186
#, no-c-format
-msgid "A context defines a namespace, a set of <emphasis>context variables</emphasis>. These work much the same as session or request attributes in the servlet spec. You may bind any value you like to a context variable, but usually we bind Seam component instances to context variables."
+msgid ""
+"A context defines a namespace, a set of <emphasis>context variables</"
+"emphasis>. These work much the same as session or request attributes in the "
+"servlet spec. You may bind any value you like to a context variable, but "
+"usually we bind Seam component instances to context variables."
msgstr ""
#. Tag: para
#: Concepts.xml:192
#, no-c-format
-msgid "So, within a context, a component instance is identified by the context variable name (this is usually, but not always, the same as the component name). You may programatically access a named component instance in a particular scope via the <literal>Contexts</literal> class, which provides access to several thread-bound instances of the <literal>Context</literal> interface:"
+msgid ""
+"So, within a context, a component instance is identified by the context "
+"variable name (this is usually, but not always, the same as the component "
+"name). You may programatically access a named component instance in a "
+"particular scope via the <literal>Contexts</literal> class, which provides "
+"access to several thread-bound instances of the <literal>Context</literal> "
+"interface:"
msgstr ""
#. Tag: programlisting
#: Concepts.xml:199
#, no-c-format
-msgid "<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>"
-msgstr "<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>"
+msgid ""
+"<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>"
+msgstr ""
+"<![CDATA[User user = (User) Contexts.getSessionContext().get(\"user\");]]>"
#. Tag: para
#: Concepts.xml:201
@@ -291,7 +394,9 @@
#. Tag: para
#: Concepts.xml:207
#, no-c-format
-msgid "Usually, however, we obtain components from a context via injection, and put component instances into a context via outjection."
+msgid ""
+"Usually, however, we obtain components from a context via injection, and put "
+"component instances into a context via outjection."
msgstr ""
#. Tag: title
@@ -303,7 +408,10 @@
#. Tag: para
#: Concepts.xml:215
#, no-c-format
-msgid "Sometimes, as above, component instances are obtained from a particular known scope. Other times, all stateful scopes are searched, in <emphasis>priority order</emphasis>. The order is as follows:"
+msgid ""
+"Sometimes, as above, component instances are obtained from a particular "
+"known scope. Other times, all stateful scopes are searched, in "
+"<emphasis>priority order</emphasis>. The order is as follows:"
msgstr ""
#. Tag: para
@@ -315,7 +423,10 @@
#. Tag: para
#: Concepts.xml:241
#, no-c-format
-msgid "You can perform a priority search by calling <literal>Contexts.lookupInStatefulContexts()</literal>. Whenever you access a component by name from a JSF page, a priority search occurs."
+msgid ""
+"You can perform a priority search by calling <literal>Contexts."
+"lookupInStatefulContexts()</literal>. Whenever you access a component by "
+"name from a JSF page, a priority search occurs."
msgstr ""
#. Tag: title
@@ -327,31 +438,65 @@
#. Tag: para
#: Concepts.xml:250
#, no-c-format
-msgid "Neither the servlet nor EJB specifications define any facilities for managing concurrent requests originating from the same client. The servlet container simply lets all threads run concurrently and leaves enforcing threadsafeness to application code. The EJB container allows stateless components to be accessed concurrently, and throws an exception if multiple threads access a stateful session bean."
+msgid ""
+"Neither the servlet nor EJB specifications define any facilities for "
+"managing concurrent requests originating from the same client. The servlet "
+"container simply lets all threads run concurrently and leaves enforcing "
+"threadsafeness to application code. The EJB container allows stateless "
+"components to be accessed concurrently, and throws an exception if multiple "
+"threads access a stateful session bean."
msgstr ""
#. Tag: para
#: Concepts.xml:256
#, no-c-format
-msgid "This behavior might have been okay in old-style web applications which were based around fine-grained, synchronous requests. But for modern applications which make heavy use of many fine-grained, asynchronous (AJAX) requests, concurrency is a fact of life, and must be supported by the programming model. Seam weaves a concurrency management layer into its context model."
+msgid ""
+"This behavior might have been okay in old-style web applications which were "
+"based around fine-grained, synchronous requests. But for modern applications "
+"which make heavy use of many fine-grained, asynchronous (AJAX) requests, "
+"concurrency is a fact of life, and must be supported by the programming "
+"model. Seam weaves a concurrency management layer into its context model."
msgstr ""
#. Tag: para
#: Concepts.xml:262
#, no-c-format
-msgid "The Seam session and application contexts are multithreaded. Seam will allow concurrent requests in a context to be processed concurrently. The event and page contexts are by nature single threaded. The business process context is strictly speaking multi-threaded, but in practice concurrency is sufficiently rare that this fact may be disregarded most of the time. Finally, Seam enforces a <emphasis>single thread per conversation per process</emphasis> model for the conversation context by serializing concurrent requests in the same long-running conversation context."
+msgid ""
+"The Seam session and application contexts are multithreaded. Seam will allow "
+"concurrent requests in a context to be processed concurrently. The event and "
+"page contexts are by nature single threaded. The business process context is "
+"strictly speaking multi-threaded, but in practice concurrency is "
+"sufficiently rare that this fact may be disregarded most of the time. "
+"Finally, Seam enforces a <emphasis>single thread per conversation per "
+"process</emphasis> model for the conversation context by serializing "
+"concurrent requests in the same long-running conversation context."
msgstr ""
#. Tag: para
#: Concepts.xml:270
#, no-c-format
-msgid "Since the session context is multithreaded, and often contains volatile state, session scope components are always protected by Seam from concurrent access so long as the Seam interceptors are not disabled for that component. If interceptors are disabled, then any thread-safety that is required must be implemented by the component itself. Seam serializes requests to session scope session beans and JavaBeans by default (and detects and breaks any deadlocks that occur). This is not the default behaviour for application scoped components however, since application scoped components do not usually hold volatile state and because synchronization at the global level is <emphasis>extremely</emphasis> expensive. However, you can force a serialized threading model on any session bean or JavaBean component by adding the <literal>@Synchronized</literal> annotation."
+msgid ""
+"Since the session context is multithreaded, and often contains volatile "
+"state, session scope components are always protected by Seam from concurrent "
+"access so long as the Seam interceptors are not disabled for that component. "
+"If interceptors are disabled, then any thread-safety that is required must "
+"be implemented by the component itself. Seam serializes requests to session "
+"scope session beans and JavaBeans by default (and detects and breaks any "
+"deadlocks that occur). This is not the default behaviour for application "
+"scoped components however, since application scoped components do not "
+"usually hold volatile state and because synchronization at the global level "
+"is <emphasis>extremely</emphasis> expensive. However, you can force a "
+"serialized threading model on any session bean or JavaBean component by "
+"adding the <literal>@Synchronized</literal> annotation."
msgstr ""
#. Tag: para
#: Concepts.xml:281
#, no-c-format
-msgid "This concurrency model means that AJAX clients can safely use volatile session and conversational state, without the need for any special work on the part of the developer."
+msgid ""
+"This concurrency model means that AJAX clients can safely use volatile "
+"session and conversational state, without the need for any special work on "
+"the part of the developer."
msgstr ""
#. Tag: title
@@ -363,7 +508,13 @@
#. Tag: para
#: Concepts.xml:291
#, no-c-format
-msgid "Seam components are POJOs (Plain Old Java Objects). In particular, they are JavaBeans or EJB 3.0 enterprise beans. While Seam does not require that components be EJBs and can even be used without an EJB 3.0 compliant container, Seam was designed with EJB 3.0 in mind and includes deep integration with EJB 3.0. Seam supports the following <emphasis>component types</emphasis>."
+msgid ""
+"Seam components are POJOs (Plain Old Java Objects). In particular, they are "
+"JavaBeans or EJB 3.0 enterprise beans. While Seam does not require that "
+"components be EJBs and can even be used without an EJB 3.0 compliant "
+"container, Seam was designed with EJB 3.0 in mind and includes deep "
+"integration with EJB 3.0. Seam supports the following <emphasis>component "
+"types</emphasis>."
msgstr ""
#. Tag: para
@@ -411,7 +562,12 @@
#. Tag: para
#: Concepts.xml:321
#, no-c-format
-msgid "Stateless session bean components are not able to hold state across multiple invocations. Therefore, they usually work by operating upon the state of other components in the various Seam contexts. They may be used as JSF action listeners, but cannot provide properties to JSF components for display."
+msgid ""
+"Stateless session bean components are not able to hold state across multiple "
+"invocations. Therefore, they usually work by operating upon the state of "
+"other components in the various Seam contexts. They may be used as JSF "
+"action listeners, but cannot provide properties to JSF components for "
+"display."
msgstr ""
#. Tag: para
@@ -423,19 +579,29 @@
#. Tag: para
#: Concepts.xml:329
#, no-c-format
-msgid "Stateless session beans can be accessed concurrently as a new instance is used for each request. Assigning the instance to the request is the responsibility of the EJB3 container (normally instances will be allocated from a reusable pool meaning that you may find any instance variables contain data from previous uses of the bean)."
+msgid ""
+"Stateless session beans can be accessed concurrently as a new instance is "
+"used for each request. Assigning the instance to the request is the "
+"responsibility of the EJB3 container (normally instances will be allocated "
+"from a reusable pool meaning that you may find any instance variables "
+"contain data from previous uses of the bean)."
msgstr ""
#. Tag: para
#: Concepts.xml:335
#, no-c-format
-msgid "Stateless session beans are the least interesting kind of Seam component."
+msgid ""
+"Stateless session beans are the least interesting kind of Seam component."
msgstr ""
#. Tag: para
#: Concepts.xml:338
#, no-c-format
-msgid "Seam stateless session bean components may be instantiated using <literal>Component.getInstance()</literal> or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup or the <literal>new</literal> operator."
+msgid ""
+"Seam stateless session bean components may be instantiated using "
+"<literal>Component.getInstance()</literal> or <literal>@In(create=true)</"
+"literal>. They should not be directly instantiated via JNDI lookup or the "
+"<literal>new</literal> operator."
msgstr ""
#. Tag: title
@@ -447,31 +613,53 @@
#. Tag: para
#: Concepts.xml:347
#, no-c-format
-msgid "Stateful session bean components are able to hold state not only across multiple invocations of the bean, but also across multiple requests. Application state that does not belong in the database should usually be held by stateful session beans. This is a major difference between Seam and many other web application frameworks. Instead of sticking information about the current conversation directly in the <literal>HttpSession</literal>, you should keep it in instance variables of a stateful session bean that is bound to the conversation context. This allows Seam to manage the lifecycle of this state for you, and ensure that there are no collisions between state relating to different concurrent conversations."
+msgid ""
+"Stateful session bean components are able to hold state not only across "
+"multiple invocations of the bean, but also across multiple requests. "
+"Application state that does not belong in the database should usually be "
+"held by stateful session beans. This is a major difference between Seam and "
+"many other web application frameworks. Instead of sticking information about "
+"the current conversation directly in the <literal>HttpSession</literal>, you "
+"should keep it in instance variables of a stateful session bean that is "
+"bound to the conversation context. This allows Seam to manage the lifecycle "
+"of this state for you, and ensure that there are no collisions between state "
+"relating to different concurrent conversations."
msgstr ""
#. Tag: para
#: Concepts.xml:357
#, no-c-format
-msgid "Stateful session beans are often used as JSF action listener, and as backing beans that provide properties to JSF components for display or form submission."
+msgid ""
+"Stateful session beans are often used as JSF action listener, and as backing "
+"beans that provide properties to JSF components for display or form "
+"submission."
msgstr ""
#. Tag: para
#: Concepts.xml:361
#, no-c-format
-msgid "By default, stateful session beans are bound to the conversation context. They may never be bound to the page or stateless contexts."
+msgid ""
+"By default, stateful session beans are bound to the conversation context. "
+"They may never be bound to the page or stateless contexts."
msgstr ""
#. Tag: para
#: Concepts.xml:365
#, no-c-format
-msgid "Concurrent requests to session-scoped stateful session beans are always serialized by Seam as long as the Seam interceptors are not disabled for the bean."
+msgid ""
+"Concurrent requests to session-scoped stateful session beans are always "
+"serialized by Seam as long as the Seam interceptors are not disabled for the "
+"bean."
msgstr ""
#. Tag: para
#: Concepts.xml:370
#, no-c-format
-msgid "Seam stateful session bean components may be instantiated using <literal>Component.getInstance()</literal> or <literal>@In(create=true)</literal>. They should not be directly instantiated via JNDI lookup or the <literal>new</literal> operator."
+msgid ""
+"Seam stateful session bean components may be instantiated using "
+"<literal>Component.getInstance()</literal> or <literal>@In(create=true)</"
+"literal>. They should not be directly instantiated via JNDI lookup or the "
+"<literal>new</literal> operator."
msgstr ""
#. Tag: title
@@ -483,37 +671,58 @@
#. Tag: para
#: Concepts.xml:379
#, no-c-format
-msgid "Entity beans may be bound to a context variable and function as a seam component. Because entities have a persistent identity in addition to their contextual identity, entity instances are usually bound explicitly in Java code, rather than being instantiated implicitly by Seam."
+msgid ""
+"Entity beans may be bound to a context variable and function as a seam "
+"component. Because entities have a persistent identity in addition to their "
+"contextual identity, entity instances are usually bound explicitly in Java "
+"code, rather than being instantiated implicitly by Seam."
msgstr ""
#. Tag: para
#: Concepts.xml:384
#, no-c-format
-msgid "Entity bean components do not support bijection or context demarcation. Nor does invocation of an entity bean trigger validation."
+msgid ""
+"Entity bean components do not support bijection or context demarcation. Nor "
+"does invocation of an entity bean trigger validation."
msgstr ""
#. Tag: para
#: Concepts.xml:388
#, no-c-format
-msgid "Entity beans are not usually used as JSF action listeners, but do often function as backing beans that provide properties to JSF components for display or form submission. In particular, it is common to use an entity as a backing bean, together with a stateless session bean action listener to implement create/update/delete type functionality."
+msgid ""
+"Entity beans are not usually used as JSF action listeners, but do often "
+"function as backing beans that provide properties to JSF components for "
+"display or form submission. In particular, it is common to use an entity as "
+"a backing bean, together with a stateless session bean action listener to "
+"implement create/update/delete type functionality."
msgstr ""
#. Tag: para
#: Concepts.xml:394
#, no-c-format
-msgid "By default, entity beans are bound to the conversation context. They may never be bound to the stateless context."
+msgid ""
+"By default, entity beans are bound to the conversation context. They may "
+"never be bound to the stateless context."
msgstr ""
#. Tag: para
#: Concepts.xml:398
#, no-c-format
-msgid "Note that it in a clustered environment is somewhat less efficient to bind an entity bean directly to a conversation or session scoped Seam context variable than it would be to hold a reference to the entity bean in a stateful session bean. For this reason, not all Seam applications define entity beans to be Seam components."
+msgid ""
+"Note that it in a clustered environment is somewhat less efficient to bind "
+"an entity bean directly to a conversation or session scoped Seam context "
+"variable than it would be to hold a reference to the entity bean in a "
+"stateful session bean. For this reason, not all Seam applications define "
+"entity beans to be Seam components."
msgstr ""
#. Tag: para
#: Concepts.xml:404
#, no-c-format
-msgid "Seam entity bean components may be instantiated using <literal>Component.getInstance()</literal>, <literal>@In(create=true)</literal> or directly using the <literal>new</literal> operator."
+msgid ""
+"Seam entity bean components may be instantiated using <literal>Component."
+"getInstance()</literal>, <literal>@In(create=true)</literal> or directly "
+"using the <literal>new</literal> operator."
msgstr ""
#. Tag: title
@@ -525,13 +734,22 @@
#. Tag: para
#: Concepts.xml:412
#, no-c-format
-msgid "Javabeans may be used just like a stateless or stateful session bean. However, they do not provide the functionality of a session bean (declarative transaction demarcation, declarative security, efficient clustered state replication, EJB 3.0 persistence, timeout methods, etc)."
+msgid ""
+"Javabeans may be used just like a stateless or stateful session bean. "
+"However, they do not provide the functionality of a session bean "
+"(declarative transaction demarcation, declarative security, efficient "
+"clustered state replication, EJB 3.0 persistence, timeout methods, etc)."
msgstr ""
#. Tag: para
#: Concepts.xml:417
#, no-c-format
-msgid "In a later chapter, we show you how to use Seam and Hibernate without an EJB container. In this use case, components are JavaBeans instead of session beans. Note, however, that in many application servers it is somewhat less efficient to cluster conversation or session scoped Seam JavaBean components than it is to cluster stateful session bean components."
+msgid ""
+"In a later chapter, we show you how to use Seam and Hibernate without an EJB "
+"container. In this use case, components are JavaBeans instead of session "
+"beans. Note, however, that in many application servers it is somewhat less "
+"efficient to cluster conversation or session scoped Seam JavaBean components "
+"than it is to cluster stateful session bean components."
msgstr ""
#. Tag: para
@@ -543,13 +761,18 @@
#. Tag: para
#: Concepts.xml:426
#, no-c-format
-msgid "Concurrent requests to session-scoped JavaBeans are always serialized by Seam."
+msgid ""
+"Concurrent requests to session-scoped JavaBeans are always serialized by "
+"Seam."
msgstr ""
#. Tag: para
#: Concepts.xml:429
#, no-c-format
-msgid "Seam JavaBean components may be instantiated using <literal>Component.getInstance()</literal> or <literal>@In(create=true)</literal>. They should not be directly instantiated using the <literal>new</literal> operator."
+msgid ""
+"Seam JavaBean components may be instantiated using <literal>Component."
+"getInstance()</literal> or <literal>@In(create=true)</literal>. They should "
+"not be directly instantiated using the <literal>new</literal> operator."
msgstr ""
#. Tag: title
@@ -561,19 +784,28 @@
#. Tag: para
#: Concepts.xml:438
#, no-c-format
-msgid "Message-driven beans may function as a seam component. However, message-driven beans are called quite differently to other Seam components - instead of invoking them via the context variable, they listen for messages sent to a JMS queue or topic."
+msgid ""
+"Message-driven beans may function as a seam component. However, message-"
+"driven beans are called quite differently to other Seam components - instead "
+"of invoking them via the context variable, they listen for messages sent to "
+"a JMS queue or topic."
msgstr ""
#. Tag: para
#: Concepts.xml:443
#, no-c-format
-msgid "Message-driven beans may not be bound to a Seam context. Nor do they have access to the session or conversation state of their \"caller\". However, they do support bijection and some other Seam functionality."
+msgid ""
+"Message-driven beans may not be bound to a Seam context. Nor do they have "
+"access to the session or conversation state of their \"caller\". However, "
+"they do support bijection and some other Seam functionality."
msgstr ""
#. Tag: para
#: Concepts.xml:448
#, no-c-format
-msgid "Message-driven beans are never instantiated by the application. They are instantiated by the EJB container when a message is received."
+msgid ""
+"Message-driven beans are never instantiated by the application. They are "
+"instantiated by the EJB container when a message is received."
msgstr ""
#. Tag: title
@@ -585,7 +817,14 @@
#. Tag: para
#: Concepts.xml:456
#, no-c-format
-msgid "In order to perform its magic (bijection, context demarcation, validation, etc), Seam must intercept component invocations. For JavaBeans, Seam is in full control of instantiation of the component, and no special configuration is needed. For entity beans, interception is not required since bijection and context demarcation are not defined. For session beans, we must register an EJB interceptor for the session bean component. We could use an annotation, as follows:"
+msgid ""
+"In order to perform its magic (bijection, context demarcation, validation, "
+"etc), Seam must intercept component invocations. For JavaBeans, Seam is in "
+"full control of instantiation of the component, and no special configuration "
+"is needed. For entity beans, interception is not required since bijection "
+"and context demarcation are not defined. For session beans, we must register "
+"an EJB interceptor for the session bean component. We could use an "
+"annotation, as follows:"
msgstr ""
#. Tag: programlisting
@@ -607,7 +846,9 @@
#. Tag: para
#: Concepts.xml:466
#, no-c-format
-msgid "But a much better way is to define the interceptor in <literal>ejb-jar.xml</literal>."
+msgid ""
+"But a much better way is to define the interceptor in <literal>ejb-jar.xml</"
+"literal>."
msgstr ""
#. Tag: programlisting
@@ -616,27 +857,31 @@
msgid ""
"<![CDATA[<interceptors>\n"
" <interceptor>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
+"class>\n"
" </interceptor>\n"
"</interceptors>\n"
" \n"
"<assembly-descriptor>\n"
" <interceptor-binding>\n"
" <ejb-name>*</ejb-name>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
+"class>\n"
" </interceptor-binding>\n"
"</assembly-descriptor>]]>"
msgstr ""
"<![CDATA[<interceptors>\n"
" <interceptor>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
+"class>\n"
" </interceptor>\n"
"</interceptors>\n"
" \n"
"<assembly-descriptor>\n"
" <interceptor-binding>\n"
" <ejb-name>*</ejb-name>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
+"class>\n"
" </interceptor-binding>\n"
"</assembly-descriptor>]]>"
@@ -649,7 +894,9 @@
#. Tag: para
#: Concepts.xml:476
#, no-c-format
-msgid "All seam components need a name. We can assign a name to a component using the <literal>@Name</literal> annotation:"
+msgid ""
+"All seam components need a name. We can assign a name to a component using "
+"the <literal>@Name</literal> annotation:"
msgstr ""
#. Tag: programlisting
@@ -671,25 +918,47 @@
#. Tag: para
#: Concepts.xml:483
#, no-c-format
-msgid "This name is the <emphasis>seam component name</emphasis> and is not related to any other name defined by the EJB specification. However, seam component names work just like JSF managed bean names and you can think of the two concepts as identical."
+msgid ""
+"This name is the <emphasis>seam component name</emphasis> and is not related "
+"to any other name defined by the EJB specification. However, seam component "
+"names work just like JSF managed bean names and you can think of the two "
+"concepts as identical."
msgstr ""
#. Tag: para
#: Concepts.xml:489
#, no-c-format
-msgid "<literal>@Name</literal> is not the only way to define a component name, but we always need to specify the name <emphasis>somewhere</emphasis>. If we don't, then none of the other Seam annotations will function."
+msgid ""
+"<literal>@Name</literal> is not the only way to define a component name, but "
+"we always need to specify the name <emphasis>somewhere</emphasis>. If we "
+"don't, then none of the other Seam annotations will function."
msgstr ""
#. Tag: para
#: Concepts.xml:495
#, no-c-format
-msgid "Whenever Seam instantiates a component, it binds the new instance to a variable in the scope configured for the component that matches the component name. This behavior is identical to how JSF managed beans work, except that Seam allows you to configure this mapping using annotations rather than XML. You can also programmatically bind a component to a context variable. This is useful if a particular component serves more than one role in the system. For example, the currently logged in <literal>User</literal> might be bound to the <literal>currentUser</literal> session context variable, while a <literal>User</literal> that is the subject of some administration functionality might be bound to the <literal>user</literal> conversation context variable. Be careful, though, because through a programmatic assignment, it's possible to overwrite a context variable that has a reference to a Seam component, potentially confusing matters."
+msgid ""
+"Whenever Seam instantiates a component, it binds the new instance to a "
+"variable in the scope configured for the component that matches the "
+"component name. This behavior is identical to how JSF managed beans work, "
+"except that Seam allows you to configure this mapping using annotations "
+"rather than XML. You can also programmatically bind a component to a context "
+"variable. This is useful if a particular component serves more than one role "
+"in the system. For example, the currently logged in <literal>User</literal> "
+"might be bound to the <literal>currentUser</literal> session context "
+"variable, while a <literal>User</literal> that is the subject of some "
+"administration functionality might be bound to the <literal>user</literal> "
+"conversation context variable. Be careful, though, because through a "
+"programmatic assignment, it's possible to overwrite a context variable that "
+"has a reference to a Seam component, potentially confusing matters."
msgstr ""
#. Tag: para
#: Concepts.xml:506
#, no-c-format
-msgid "For very large applications, and for built-in seam components, qualified component names are often used to avoid naming conflicts."
+msgid ""
+"For very large applications, and for built-in seam components, qualified "
+"component names are often used to avoid naming conflicts."
msgstr ""
#. Tag: programlisting
@@ -711,7 +980,9 @@
#. Tag: para
#: Concepts.xml:513
#, no-c-format
-msgid "We may use the qualified component name both in Java code and in JSF's expression language:"
+msgid ""
+"We may use the qualified component name both in Java code and in JSF's "
+"expression language:"
msgstr ""
#. Tag: programlisting
@@ -727,26 +998,38 @@
#. Tag: para
#: Concepts.xml:519
#, no-c-format
-msgid "Since this is noisy, Seam also provides a means of aliasing a qualified name to a simple name. Add a line like this to the <literal>components.xml</literal> file:"
+msgid ""
+"Since this is noisy, Seam also provides a means of aliasing a qualified name "
+"to a simple name. Add a line like this to the <literal>components.xml</"
+"literal> file:"
msgstr ""
#. Tag: programlisting
#: Concepts.xml:524
#, no-c-format
-msgid "<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com.jboss.myapp.loginAction}\"/>]]>"
-msgstr "<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com.jboss.myapp.loginAction}\"/>]]>"
+msgid ""
+"<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com."
+"jboss.myapp.loginAction}\"/>]]>"
+msgstr ""
+"<![CDATA[<factory name=\"loginAction\" scope=\"STATELESS\" value=\"#{com."
+"jboss.myapp.loginAction}\"/>]]>"
#. Tag: para
#: Concepts.xml:526
#, no-c-format
-msgid "All of the built-in Seam components have qualified names but can be accessed through their unqualified names due to the namespace import feature of Seam. The <literal>components.xml</literal> file included in the Seam JAR defines the following namespaces."
+msgid ""
+"All of the built-in Seam components have qualified names but can be accessed "
+"through their unqualified names due to the namespace import feature of Seam. "
+"The <literal>components.xml</literal> file included in the Seam JAR defines "
+"the following namespaces."
msgstr ""
#. Tag: programlisting
#: Concepts.xml:533
#, no-c-format
msgid ""
-"<components xmlns="http://jboss.com/products/seam/components">\n"
+"<components xmlns="http://jboss.com/products/seam/components""
+">\n"
" \n"
" <import>org.jboss.seam.core</import>\n"
" <import>org.jboss.seam.cache</import>\n"
@@ -772,7 +1055,11 @@
#. Tag: para
#: Concepts.xml:535
#, no-c-format
-msgid "When attempting to resolve an unqualified name, Seam will check each of those namespaces, in order. You can include additional namespaces in your application's <literal>components.xml</literal> file for application-specific namespaces."
+msgid ""
+"When attempting to resolve an unqualified name, Seam will check each of "
+"those namespaces, in order. You can include additional namespaces in your "
+"application's <literal>components.xml</literal> file for application-"
+"specific namespaces."
msgstr ""
#. Tag: title
@@ -784,7 +1071,10 @@
#. Tag: para
#: Concepts.xml:544
#, no-c-format
-msgid "We can override the default scope (context) of a component using the <literal>@Scope</literal> annotation. This lets us define what context a component instance is bound to, when it is instantiated by Seam."
+msgid ""
+"We can override the default scope (context) of a component using the "
+"<literal>@Scope</literal> annotation. This lets us define what context a "
+"component instance is bound to, when it is instantiated by Seam."
msgstr ""
#. Tag: programlisting
@@ -808,7 +1098,9 @@
#. Tag: para
#: Concepts.xml:552
#, no-c-format
-msgid "<literal>org.jboss.seam.ScopeType</literal> defines an enumeration of possible scopes."
+msgid ""
+"<literal>org.jboss.seam.ScopeType</literal> defines an enumeration of "
+"possible scopes."
msgstr ""
#. Tag: title
@@ -820,7 +1112,17 @@
#. Tag: para
#: Concepts.xml:560
#, no-c-format
-msgid "Some Seam component classes can fulfill more than one role in the system. For example, we often have a <literal>User</literal> class which is usually used as a session-scoped component representing the current user but is used in user administration screens as a conversation-scoped component. The <literal>@Role</literal> annotation lets us define an additional named role for a component, with a different scope—it lets us bind the same component class to different context variables. (Any Seam component <emphasis>instance</emphasis> may be bound to multiple context variables, but this lets us do it at the class level, and take advantage of auto-instantiation.)"
+msgid ""
+"Some Seam component classes can fulfill more than one role in the system. "
+"For example, we often have a <literal>User</literal> class which is usually "
+"used as a session-scoped component representing the current user but is used "
+"in user administration screens as a conversation-scoped component. The "
+"<literal>@Role</literal> annotation lets us define an additional named role "
+"for a component, with a different scope — it lets us bind the same "
+"component class to different context variables. (Any Seam component "
+"<emphasis>instance</emphasis> may be bound to multiple context variables, "
+"but this lets us do it at the class level, and take advantage of auto-"
+"instantiation.)"
msgstr ""
#. Tag: programlisting
@@ -846,7 +1148,9 @@
#. Tag: para
#: Concepts.xml:572
#, no-c-format
-msgid "The <literal>@Roles</literal> annotation lets us specify as many additional roles as we like."
+msgid ""
+"The <literal>@Roles</literal> annotation lets us specify as many additional "
+"roles as we like."
msgstr ""
#. Tag: programlisting
@@ -880,20 +1184,31 @@
#. Tag: para
#: Concepts.xml:582
#, no-c-format
-msgid "Like many good frameworks, Seam eats its own dogfood and is implemented mostly as a set of built-in Seam interceptors (see later) and Seam components. This makes it easy for applications to interact with built-in components at runtime or even customize the basic functionality of Seam by replacing the built-in components with custom implementations. The built-in components are defined in the Seam namespace <literal>org.jboss.seam.core</literal> and the Java package of the same name."
+msgid ""
+"Like many good frameworks, Seam eats its own dogfood and is implemented "
+"mostly as a set of built-in Seam interceptors (see later) and Seam "
+"components. This makes it easy for applications to interact with built-in "
+"components at runtime or even customize the basic functionality of Seam by "
+"replacing the built-in components with custom implementations. The built-in "
+"components are defined in the Seam namespace <literal>org.jboss.seam.core</"
+"literal> and the Java package of the same name."
msgstr ""
#. Tag: para
#: Concepts.xml:589
#, no-c-format
-msgid "The built-in components may be injected, just like any Seam components, but they also provide convenient static <literal>instance()</literal> methods:"
+msgid ""
+"The built-in components may be injected, just like any Seam components, but "
+"they also provide convenient static <literal>instance()</literal> methods:"
msgstr ""
#. Tag: programlisting
#: Concepts.xml:593
#, no-c-format
-msgid "<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>"
-msgstr "<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>"
+msgid ""
+"<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>"
+msgstr ""
+"<![CDATA[FacesMessages.instance().add(\"Welcome back, #{user.name}!\");]]>"
#. Tag: title
#: Concepts.xml:599
@@ -904,37 +1219,67 @@
#. Tag: para
#: Concepts.xml:600
#, no-c-format
-msgid "<emphasis>Dependency injection</emphasis> or <emphasis>inversion of control</emphasis> is by now a familiar concept to most Java developers. Dependency injection allows a component to obtain a reference to another component by having the container \"inject\" the other component to a setter method or instance variable. In all dependency injection implementations that we have seen, injection occurs when the component is constructed, and the reference does not subsequently change for the lifetime of the component instance. For stateless components, this is reasonable. From the point of view of a client, all instances of a particular stateless component are interchangeable. On the other hand, Seam emphasizes the use of stateful components. So traditional dependency injection is no longer a very useful construct. Seam introduces the notion of <emphasis>bijection</emphasis> as a generalization of injection. In contrast to injection, bijection is:"
+msgid ""
+"<emphasis>Dependency injection</emphasis> or <emphasis>inversion of control</"
+"emphasis> is by now a familiar concept to most Java developers. Dependency "
+"injection allows a component to obtain a reference to another component by "
+"having the container \"inject\" the other component to a setter method or "
+"instance variable. In all dependency injection implementations that we have "
+"seen, injection occurs when the component is constructed, and the reference "
+"does not subsequently change for the lifetime of the component instance. For "
+"stateless components, this is reasonable. From the point of view of a "
+"client, all instances of a particular stateless component are "
+"interchangeable. On the other hand, Seam emphasizes the use of stateful "
+"components. So traditional dependency injection is no longer a very useful "
+"construct. Seam introduces the notion of <emphasis>bijection</emphasis> as a "
+"generalization of injection. In contrast to injection, bijection is:"
msgstr ""
#. Tag: para
#: Concepts.xml:614
#, no-c-format
-msgid "<emphasis>contextual</emphasis> - bijection is used to assemble stateful components from various different contexts (a component from a \"wider\" context may even have a reference to a component from a \"narrower\" context)"
+msgid ""
+"<emphasis>contextual</emphasis> - bijection is used to assemble stateful "
+"components from various different contexts (a component from a \"wider\" "
+"context may even have a reference to a component from a \"narrower\" context)"
msgstr ""
#. Tag: para
#: Concepts.xml:621
#, no-c-format
-msgid "<emphasis>bidirectional</emphasis> - values are injected from context variables into attributes of the component being invoked, and also <emphasis>outjected</emphasis> from the component attributes back out to the context, allowing the component being invoked to manipulate the values of contextual variables simply by setting its own instance variables"
+msgid ""
+"<emphasis>bidirectional</emphasis> - values are injected from context "
+"variables into attributes of the component being invoked, and also "
+"<emphasis>outjected</emphasis> from the component attributes back out to the "
+"context, allowing the component being invoked to manipulate the values of "
+"contextual variables simply by setting its own instance variables"
msgstr ""
#. Tag: para
#: Concepts.xml:629
#, no-c-format
-msgid "<emphasis>dynamic</emphasis> - since the value of contextual variables changes over time, and since Seam components are stateful, bijection takes place every time a component is invoked"
+msgid ""
+"<emphasis>dynamic</emphasis> - since the value of contextual variables "
+"changes over time, and since Seam components are stateful, bijection takes "
+"place every time a component is invoked"
msgstr ""
#. Tag: para
#: Concepts.xml:636
#, no-c-format
-msgid "In essence, bijection lets you alias a context variable to a component instance variable, by specifying that the value of the instance variable is injected, outjected, or both. Of course, we use annotations to enable bijection."
+msgid ""
+"In essence, bijection lets you alias a context variable to a component "
+"instance variable, by specifying that the value of the instance variable is "
+"injected, outjected, or both. Of course, we use annotations to enable "
+"bijection."
msgstr ""
#. Tag: para
#: Concepts.xml:642
#, no-c-format
-msgid "The <literal>@In</literal> annotation specifies that a value should be injected, either into an instance variable:"
+msgid ""
+"The <literal>@In</literal> annotation specifies that a value should be "
+"injected, either into an instance variable:"
msgstr ""
#. Tag: programlisting
@@ -994,19 +1339,32 @@
#. Tag: para
#: Concepts.xml:656
#, no-c-format
-msgid "By default, Seam will do a priority search of all contexts, using the name of the property or instance variable that is being injected. You may wish to specify the context variable name explicitly, using, for example, <literal>@In(\"currentUser\")</literal>."
+msgid ""
+"By default, Seam will do a priority search of all contexts, using the name "
+"of the property or instance variable that is being injected. You may wish to "
+"specify the context variable name explicitly, using, for example, "
+"<literal>@In(\"currentUser\")</literal>."
msgstr ""
#. Tag: para
#: Concepts.xml:662
#, no-c-format
-msgid "If you want Seam to create an instance of the component when there is no existing component instance bound to the named context variable, you should specify <literal>@In(create=true)</literal>. If the value is optional (it can be null), specify <literal>@In(required=false)</literal>."
+msgid ""
+"If you want Seam to create an instance of the component when there is no "
+"existing component instance bound to the named context variable, you should "
+"specify <literal>@In(create=true)</literal>. If the value is optional (it "
+"can be null), specify <literal>@In(required=false)</literal>."
msgstr ""
#. Tag: para
#: Concepts.xml:668
#, no-c-format
-msgid "For some components, it can be repetitive to have to specify <literal>@In(create=true)</literal> everywhere they are used. In such cases, you can annotate the component <literal>@AutoCreate</literal>, and then it will always be created, whenever needed, even without the explicit use of <literal>create=true</literal>."
+msgid ""
+"For some components, it can be repetitive to have to specify <literal>@In"
+"(create=true)</literal> everywhere they are used. In such cases, you can "
+"annotate the component <literal>@AutoCreate</literal>, and then it will "
+"always be created, whenever needed, even without the explicit use of "
+"<literal>create=true</literal>."
msgstr ""
#. Tag: para
@@ -1036,19 +1394,25 @@
#. Tag: para
#: Concepts.xml:680
#, no-c-format
-msgid "Injected values are disinjected (i.e., set to <literal>null</literal>) immediately after method completion and outjection."
+msgid ""
+"Injected values are disinjected (i.e., set to <literal>null</literal>) "
+"immediately after method completion and outjection."
msgstr ""
#. Tag: para
#: Concepts.xml:685
#, no-c-format
-msgid "(There is much more information about component lifecycle and injection in the next chapter.)"
+msgid ""
+"(There is much more information about component lifecycle and injection in "
+"the next chapter.)"
msgstr ""
#. Tag: para
#: Concepts.xml:689
#, no-c-format
-msgid "The <literal>@Out</literal> annotation specifies that an attribute should be outjected, either from an instance variable:"
+msgid ""
+"The <literal>@Out</literal> annotation specifies that an attribute should be "
+"outjected, either from an instance variable:"
msgstr ""
#. Tag: programlisting
@@ -1184,31 +1548,53 @@
#. Tag: para
#: Concepts.xml:719
#, no-c-format
-msgid "Session bean and entity bean Seam components support all the usual EJB 3.0 lifecycle callback (<literal>@PostConstruct</literal>, <literal>@PreDestroy</literal>, etc). But Seam also supports the use of any of these callbacks with JavaBean components. However, since these annotations are not available in a J2EE environment, Seam defines two additional component lifecycle callbacks, equivalent to <literal>@PostConstruct</literal> and <literal>@PreDestroy</literal>."
+msgid ""
+"Session bean and entity bean Seam components support all the usual EJB 3.0 "
+"lifecycle callback (<literal>@PostConstruct</literal>, <literal>@PreDestroy</"
+"literal>, etc). But Seam also supports the use of any of these callbacks "
+"with JavaBean components. However, since these annotations are not available "
+"in a J2EE environment, Seam defines two additional component lifecycle "
+"callbacks, equivalent to <literal>@PostConstruct</literal> and "
+"<literal>@PreDestroy</literal>."
msgstr ""
#. Tag: para
#: Concepts.xml:727
#, no-c-format
-msgid "The <literal>@Create</literal> method is called after Seam instantiates a component. Components may define only one <literal>@Create</literal> method."
+msgid ""
+"The <literal>@Create</literal> method is called after Seam instantiates a "
+"component. Components may define only one <literal>@Create</literal> method."
msgstr ""
#. Tag: para
#: Concepts.xml:732
#, no-c-format
-msgid "The <literal>@Destroy</literal> method is called when the context that the Seam component is bound to ends. Components may define only one <literal>@Destroy</literal> method."
+msgid ""
+"The <literal>@Destroy</literal> method is called when the context that the "
+"Seam component is bound to ends. Components may define only one "
+"<literal>@Destroy</literal> method."
msgstr ""
#. Tag: para
#: Concepts.xml:737
#, no-c-format
-msgid "In addition, stateful session bean components <emphasis>must</emphasis> define a method with no parameters annotated <literal>@Remove</literal>. This method is called by Seam when the context ends."
+msgid ""
+"In addition, stateful session bean components <emphasis>must</emphasis> "
+"define a method with no parameters annotated <literal>@Remove</literal>. "
+"This method is called by Seam when the context ends."
msgstr ""
#. Tag: para
#: Concepts.xml:742
#, no-c-format
-msgid "Finally, a related annotation is the <literal>@Startup</literal> annotation, which may be applied to any application or session scoped component. The <literal>@Startup</literal> annotation tells Seam to instantiate the component immediately, when the context begins, instead of waiting until it is first referenced by a client. It is possible to control the order of instantiation of startup components by specifying <literal>@Startup(depends={....})</literal>."
+msgid ""
+"Finally, a related annotation is the <literal>@Startup</literal> annotation, "
+"which may be applied to any application or session scoped component. The "
+"<literal>@Startup</literal> annotation tells Seam to instantiate the "
+"component immediately, when the context begins, instead of waiting until it "
+"is first referenced by a client. It is possible to control the order of "
+"instantiation of startup components by specifying <literal>@Startup(depends="
+"{....})</literal>."
msgstr ""
#. Tag: title
@@ -1220,7 +1606,10 @@
#. Tag: para
#: Concepts.xml:755
#, no-c-format
-msgid "The <literal>@Install</literal> annotation lets you control conditional installation of components that are required in some deployment scenarios and not in others. This is useful if:"
+msgid ""
+"The <literal>@Install</literal> annotation lets you control conditional "
+"installation of components that are required in some deployment scenarios "
+"and not in others. This is useful if:"
msgstr ""
#. Tag: para
@@ -1232,49 +1621,69 @@
#. Tag: para
#: Concepts.xml:767
#, no-c-format
-msgid "You want change the implementation of a component in certain deployment scenarios."
+msgid ""
+"You want change the implementation of a component in certain deployment "
+"scenarios."
msgstr ""
#. Tag: para
#: Concepts.xml:773
#, no-c-format
-msgid "You want to install some components only if their dependencies are available (useful for framework authors)."
+msgid ""
+"You want to install some components only if their dependencies are available "
+"(useful for framework authors)."
msgstr ""
#. Tag: para
#: Concepts.xml:780
#, no-c-format
-msgid "<literal>@Install</literal> works by letting you specify <emphasis>precedence</emphasis> and <emphasis>dependencies</emphasis>."
+msgid ""
+"<literal>@Install</literal> works by letting you specify "
+"<emphasis>precedence</emphasis> and <emphasis>dependencies</emphasis>."
msgstr ""
#. Tag: para
#: Concepts.xml:785
#, no-c-format
-msgid "The precedence of a component is a number that Seam uses to decide which component to install when there are multiple classes with the same component name in the classpath. Seam will choose the component with the higher precendence. There are some predefined precedence values (in ascending order):"
+msgid ""
+"The precedence of a component is a number that Seam uses to decide which "
+"component to install when there are multiple classes with the same component "
+"name in the classpath. Seam will choose the component with the higher "
+"precendence. There are some predefined precedence values (in ascending "
+"order):"
msgstr ""
#. Tag: para
#: Concepts.xml:794
#, no-c-format
-msgid "<literal>BUILT_IN</literal> — the lowest precedece components are the components built in to Seam."
+msgid ""
+"<literal>BUILT_IN</literal> — the lowest precedece components are the "
+"components built in to Seam."
msgstr ""
#. Tag: para
#: Concepts.xml:800
#, no-c-format
-msgid "<literal>FRAMEWORK</literal> — components defined by third-party frameworks may override built-in components, but are overridden by application components."
+msgid ""
+"<literal>FRAMEWORK</literal> — components defined by third-party "
+"frameworks may override built-in components, but are overridden by "
+"application components."
msgstr ""
#. Tag: para
#: Concepts.xml:807
#, no-c-format
-msgid "<literal>APPLICATION</literal> — the default precedence. This is appropriate for most application components."
+msgid ""
+"<literal>APPLICATION</literal> — the default precedence. This is "
+"appropriate for most application components."
msgstr ""
#. Tag: para
#: Concepts.xml:813
#, no-c-format
-msgid "<literal>DEPLOYMENT</literal> — for application components which are deployment-specific."
+msgid ""
+"<literal>DEPLOYMENT</literal> — for application components which are "
+"deployment-specific."
msgstr ""
#. Tag: para
@@ -1286,7 +1695,9 @@
#. Tag: para
#: Concepts.xml:825
#, no-c-format
-msgid "Suppose we have a component named <literal>messageSender</literal> that talks to a JMS queue."
+msgid ""
+"Suppose we have a component named <literal>messageSender</literal> that "
+"talks to a JMS queue."
msgstr ""
#. Tag: programlisting
@@ -1310,7 +1721,11 @@
#. Tag: para
#: Concepts.xml:832
#, no-c-format
-msgid "In our unit tests, we don't have a JMS queue available, so we would like to stub out this method. We'll create a <emphasis>mock</emphasis> component that exists in the classpath when unit tests are running, but is never deployed with the application:"
+msgid ""
+"In our unit tests, we don't have a JMS queue available, so we would like to "
+"stub out this method. We'll create a <emphasis>mock</emphasis> component "
+"that exists in the classpath when unit tests are running, but is never "
+"deployed with the application:"
msgstr ""
#. Tag: programlisting
@@ -1336,13 +1751,24 @@
#. Tag: para
#: Concepts.xml:841
#, no-c-format
-msgid "The <literal>precedence</literal> helps Seam decide which version to use when it finds both components in the classpath."
+msgid ""
+"The <literal>precedence</literal> helps Seam decide which version to use "
+"when it finds both components in the classpath."
msgstr ""
#. Tag: para
#: Concepts.xml:846
#, no-c-format
-msgid "This is nice if we are able to control exactly which classes are in the classpath. But if I'm writing a reusable framework with many dependecies, I don't want to have to break that framework across many jars. I want to be able to decide which components to install depending upon what other components are installed, and upon what classes are available in the classpath. The <literal>@Install</literal> annotation also controls this functionality. Seam uses this mechanism internally to enable conditional installation of many of the built-in components. However, you probably won't need to use it in your application."
+msgid ""
+"This is nice if we are able to control exactly which classes are in the "
+"classpath. But if I'm writing a reusable framework with many dependecies, I "
+"don't want to have to break that framework across many jars. I want to be "
+"able to decide which components to install depending upon what other "
+"components are installed, and upon what classes are available in the "
+"classpath. The <literal>@Install</literal> annotation also controls this "
+"functionality. Seam uses this mechanism internally to enable conditional "
+"installation of many of the built-in components. However, you probably won't "
+"need to use it in your application."
msgstr ""
#. Tag: title
@@ -1361,7 +1787,8 @@
#: Concepts.xml:866
#, no-c-format
msgid ""
-"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction.class);\n"
+"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction."
+"class);\n"
" \n"
"public Order createOrder(User user, Product product, int quantity) {\n"
" if ( log.isDebugEnabled() ) {\n"
@@ -1372,7 +1799,8 @@
" return new Order(user, product, quantity);\n"
"}]]>"
msgstr ""
-"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction.class);\n"
+"<![CDATA[private static final Log log = LogFactory.getLog(CreateOrderAction."
+"class);\n"
" \n"
"public Order createOrder(User user, Product product, int quantity) {\n"
" if ( log.isDebugEnabled() ) {\n"
@@ -1386,7 +1814,11 @@
#. Tag: para
#: Concepts.xml:868
#, no-c-format
-msgid "It is difficult to imagine how the code for a simple log message could possibly be more verbose. There is more lines of code tied up in logging than in the actual business logic! I remain totally astonished that the Java community has not come up with anything better in 10 years."
+msgid ""
+"It is difficult to imagine how the code for a simple log message could "
+"possibly be more verbose. There is more lines of code tied up in logging "
+"than in the actual business logic! I remain totally astonished that the Java "
+"community has not come up with anything better in 10 years."
msgstr ""
#. Tag: para
@@ -1402,33 +1834,45 @@
"<![CDATA[@Logger private Log log;\n"
" \n"
"public Order createOrder(User user, Product product, int quantity) {\n"
-" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", user.username(), product.name(), quantity);\n"
+" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", "
+"user.username(), product.name(), quantity);\n"
" return new Order(user, product, quantity);\n"
"}]]>"
msgstr ""
"<![CDATA[@Logger private Log log;\n"
" \n"
"public Order createOrder(User user, Product product, int quantity) {\n"
-" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", user.username(), product.name(), quantity);\n"
+" log.debug(\"Creating new order for user: #0 product: #1 quantity: #2\", "
+"user.username(), product.name(), quantity);\n"
" return new Order(user, product, quantity);\n"
"}]]>"
#. Tag: para
#: Concepts.xml:880
#, no-c-format
-msgid "It doesn't matter if you declare the <literal>log</literal> variable static or not—it will work either way, except for entity bean components which require the <literal>log</literal> variable to be static."
+msgid ""
+"It doesn't matter if you declare the <literal>log</literal> variable static "
+"or not — it will work either way, except for entity bean components "
+"which require the <literal>log</literal> variable to be static."
msgstr ""
#. Tag: para
#: Concepts.xml:886
#, no-c-format
-msgid "Note that we don't need the noisy <literal>if ( log.isDebugEnabled() )</literal> guard, since string concatenation happens <emphasis>inside</emphasis> the <literal>debug()</literal> method. Note also that we don't usually need to specify the log category explicitly, since Seam knows what component it is injecting the <literal>Log</literal> into."
+msgid ""
+"Note that we don't need the noisy <literal>if ( log.isDebugEnabled() )</"
+"literal> guard, since string concatenation happens <emphasis>inside</"
+"emphasis> the <literal>debug()</literal> method. Note also that we don't "
+"usually need to specify the log category explicitly, since Seam knows what "
+"component it is injecting the <literal>Log</literal> into."
msgstr ""
#. Tag: para
#: Concepts.xml:901
#, no-c-format
-msgid "If <literal>User</literal> and <literal>Product</literal> are Seam components available in the current contexts, it gets even better:"
+msgid ""
+"If <literal>User</literal> and <literal>Product</literal> are Seam "
+"components available in the current contexts, it gets even better:"
msgstr ""
#. Tag: programlisting
@@ -1438,45 +1882,74 @@
"<![CDATA[@Logger private Log log;\n"
" \n"
"public Order createOrder(User user, Product product, int quantity) {\n"
-" log.debug(\"Creating new order for user: #{user.username} product: #{product.name} quantity: #0\", quantity);\n"
+" log.debug(\"Creating new order for user: #{user.username} product: #"
+"{product.name} quantity: #0\", quantity);\n"
" return new Order(user, product, quantity);\n"
"}]]>"
msgstr ""
"<![CDATA[@Logger private Log log;\n"
" \n"
"public Order createOrder(User user, Product product, int quantity) {\n"
-" log.debug(\"Creating new order for user: #{user.username} product: #{product.name} quantity: #0\", quantity);\n"
+" log.debug(\"Creating new order for user: #{user.username} product: #"
+"{product.name} quantity: #0\", quantity);\n"
" return new Order(user, product, quantity);\n"
"}]]>"
#. Tag: para
#: Concepts.xml:908
#, no-c-format
-msgid "Seam logging automagically chooses whether to send output to log4j or JDK logging. If log4j is in the classpath, Seam with use it. If it is not, Seam will use JDK logging."
+msgid ""
+"Seam logging automagically chooses whether to send output to log4j or JDK "
+"logging. If log4j is in the classpath, Seam with use it. If it is not, Seam "
+"will use JDK logging."
msgstr ""
#. Tag: title
#: Concepts.xml:916
#, no-c-format
-msgid "The <literal>Mutable</literal> interface and <literal>@ReadOnly</literal>"
+msgid ""
+"The <literal>Mutable</literal> interface and <literal>@ReadOnly</literal>"
msgstr ""
#. Tag: para
#: Concepts.xml:917
#, no-c-format
-msgid "Many application servers feature an amazingly broken implementation of <literal>HttpSession</literal> clustering, where changes to the state of mutable objects bound to the session are only replicated when the application calls <literal>setAttribute()</literal> explicitly. This is a source of bugs that can not effectively be tested for at development time, since they will only manifest when failover occurs. Furthermore, the actual replication message contains the entire serialized object graph bound to the session attribute, which is inefficient."
+msgid ""
+"Many application servers feature an amazingly broken implementation of "
+"<literal>HttpSession</literal> clustering, where changes to the state of "
+"mutable objects bound to the session are only replicated when the "
+"application calls <literal>setAttribute()</literal> explicitly. This is a "
+"source of bugs that can not effectively be tested for at development time, "
+"since they will only manifest when failover occurs. Furthermore, the actual "
+"replication message contains the entire serialized object graph bound to the "
+"session attribute, which is inefficient."
msgstr ""
#. Tag: para
#: Concepts.xml:926
#, no-c-format
-msgid "Of course, EJB stateful session beans must perform automatic dirty checking and replication of mutable state and a sophisticated EJB container can introduce optimizations such as attribute-level replication. Unfortunately, not all Seam users have the good fortune to be working in an environment that supports EJB 3.0. So, for session and conversation scoped JavaBean and entity bean components, Seam provides an extra layer of cluster-safe state management over the top of the web container session clustering."
+msgid ""
+"Of course, EJB stateful session beans must perform automatic dirty checking "
+"and replication of mutable state and a sophisticated EJB container can "
+"introduce optimizations such as attribute-level replication. Unfortunately, "
+"not all Seam users have the good fortune to be working in an environment "
+"that supports EJB 3.0. So, for session and conversation scoped JavaBean and "
+"entity bean components, Seam provides an extra layer of cluster-safe state "
+"management over the top of the web container session clustering."
msgstr ""
#. Tag: para
#: Concepts.xml:934
#, no-c-format
-msgid "For session or conversation scoped JavaBean components, Seam automatically forces replication to occur by calling <literal>setAttribute()</literal> once in every request that the component was invoked by the application. Of course, this strategy is inefficient for read-mostly components. You can control this behavior by implementing the <literal>org.jboss.seam.core.Mutable</literal> interface, or by extending <literal>org.jboss.seam.core.AbstractMutable</literal>, and writing your own dirty-checking logic inside the component. For example,"
+msgid ""
+"For session or conversation scoped JavaBean components, Seam automatically "
+"forces replication to occur by calling <literal>setAttribute()</literal> "
+"once in every request that the component was invoked by the application. Of "
+"course, this strategy is inefficient for read-mostly components. You can "
+"control this behavior by implementing the <literal>org.jboss.seam.core."
+"Mutable</literal> interface, or by extending <literal>org.jboss.seam.core."
+"AbstractMutable</literal>, and writing your own dirty-checking logic inside "
+"the component. For example,"
msgstr ""
#. Tag: programlisting
@@ -1526,7 +1999,9 @@
#. Tag: para
#: Concepts.xml:945
#, no-c-format
-msgid "Or, you can use the <literal>@ReadOnly</literal> annotation to achieve a similar effect:"
+msgid ""
+"Or, you can use the <literal>@ReadOnly</literal> annotation to achieve a "
+"similar effect:"
msgstr ""
#. Tag: programlisting
@@ -1576,7 +2051,15 @@
#. Tag: para
#: Concepts.xml:951
#, no-c-format
-msgid "For session or conversation scoped entity bean components, Seam automatically forces replication to occur by calling <literal>setAttribute()</literal> once in every request, <emphasis>unless the (conversation-scoped) entity is currently associated with a Seam-managed persistence context, in which case no replication is needed</emphasis>. This strategy is not necessarily efficient, so session or conversation scope entity beans should be used with care. You can always write a stateful session bean or JavaBean component to \"manage\" the entity bean instance. For example,"
+msgid ""
+"For session or conversation scoped entity bean components, Seam "
+"automatically forces replication to occur by calling <literal>setAttribute()"
+"</literal> once in every request, <emphasis>unless the (conversation-scoped) "
+"entity is currently associated with a Seam-managed persistence context, in "
+"which case no replication is needed</emphasis>. This strategy is not "
+"necessarily efficient, so session or conversation scope entity beans should "
+"be used with care. You can always write a stateful session bean or JavaBean "
+"component to \"manage\" the entity bean instance. For example,"
msgstr ""
#. Tag: programlisting
@@ -1618,7 +2101,10 @@
#. Tag: para
#: Concepts.xml:962
#, no-c-format
-msgid "Note that the <literal>EntityHome</literal> class in the Seam Application Framework provides a great example of managing an entity bean instance using a Seam component."
+msgid ""
+"Note that the <literal>EntityHome</literal> class in the Seam Application "
+"Framework provides a great example of managing an entity bean instance using "
+"a Seam component."
msgstr ""
#. Tag: title
@@ -1630,13 +2116,29 @@
#. Tag: para
#: Concepts.xml:971
#, no-c-format
-msgid "We often need to work with objects that are not Seam components. But we still want to be able to inject them into our components using <literal>@In</literal> and use them in value and method binding expressions, etc. Sometimes, we even need to tie them into the Seam context lifecycle (<literal>@Destroy</literal>, for example). So the Seam contexts can contain objects which are not Seam components, and Seam provides a couple of nice features that make it easier to work with non-component objects bound to contexts."
+msgid ""
+"We often need to work with objects that are not Seam components. But we "
+"still want to be able to inject them into our components using <literal>@In</"
+"literal> and use them in value and method binding expressions, etc. "
+"Sometimes, we even need to tie them into the Seam context lifecycle "
+"(<literal>@Destroy</literal>, for example). So the Seam contexts can contain "
+"objects which are not Seam components, and Seam provides a couple of nice "
+"features that make it easier to work with non-component objects bound to "
+"contexts."
msgstr ""
#. Tag: para
#: Concepts.xml:979
#, no-c-format
-msgid "The <emphasis>factory component pattern</emphasis> lets a Seam component act as the instantiator for a non-component object. A <emphasis>factory method</emphasis> will be called when a context variable is referenced but has no value bound to it. We define factory methods using the <literal>@Factory</literal> annotation. The factory method binds a value to the context variable, and determines the scope of the bound value. There are two styles of factory method. The first style returns a value, which is bound to the context by Seam:"
+msgid ""
+"The <emphasis>factory component pattern</emphasis> lets a Seam component act "
+"as the instantiator for a non-component object. A <emphasis>factory method</"
+"emphasis> will be called when a context variable is referenced but has no "
+"value bound to it. We define factory methods using the <literal>@Factory</"
+"literal> annotation. The factory method binds a value to the context "
+"variable, and determines the scope of the bound value. There are two styles "
+"of factory method. The first style returns a value, which is bound to the "
+"context by Seam:"
msgstr ""
#. Tag: programlisting
@@ -1656,7 +2158,9 @@
#. Tag: para
#: Concepts.xml:990
#, no-c-format
-msgid "The second style is a method of type <literal>void</literal> which binds the value to the context variable itself:"
+msgid ""
+"The second style is a method of type <literal>void</literal> which binds the "
+"value to the context variable itself:"
msgstr ""
#. Tag: programlisting
@@ -1680,13 +2184,23 @@
#. Tag: para
#: Concepts.xml:997
#, no-c-format
-msgid "In both cases, the factory method is called when we reference the <literal>customerList</literal> context variable and its value is null, and then has no further part to play in the lifecycle of the value. An even more powerful pattern is the <emphasis>manager component pattern</emphasis>. In this case, we have a Seam component that is bound to a context variable, that manages the value of the context variable, while remaining invisible to clients."
+msgid ""
+"In both cases, the factory method is called when we reference the "
+"<literal>customerList</literal> context variable and its value is null, and "
+"then has no further part to play in the lifecycle of the value. An even more "
+"powerful pattern is the <emphasis>manager component pattern</emphasis>. In "
+"this case, we have a Seam component that is bound to a context variable, "
+"that manages the value of the context variable, while remaining invisible to "
+"clients."
msgstr ""
#. Tag: para
#: Concepts.xml:1005
#, no-c-format
-msgid "A manager component is any component with an <literal>@Unwrap</literal> method. This method returns the value that will be visable to clients, and is called <emphasis>every time</emphasis> a context variable is referenced."
+msgid ""
+"A manager component is any component with an <literal>@Unwrap</literal> "
+"method. This method returns the value that will be visable to clients, and "
+"is called <emphasis>every time</emphasis> a context variable is referenced."
msgstr ""
#. Tag: programlisting
@@ -1720,7 +2234,13 @@
#. Tag: para
#: Concepts.xml:1015
#, no-c-format
-msgid "The manager component pattern is especially useful if we have an object where you need more control over the lifecycle of the component. For example, if you have a heavyweight object that needs a cleanup operation when the context ends you could <literal>@Unwrap</literal> the object, and perform cleanup in the <literal>@Destroy</literal> method of the manager component."
+msgid ""
+"The manager component pattern is especially useful if we have an object "
+"where you need more control over the lifecycle of the component. For "
+"example, if you have a heavyweight object that needs a cleanup operation "
+"when the context ends you could <literal>@Unwrap</literal> the object, and "
+"perform cleanup in the <literal>@Destroy</literal> method of the manager "
+"component."
msgstr ""
#. Tag: programlisting
@@ -1806,6 +2326,8 @@
#. Tag: para
#: Concepts.xml:1024
#, no-c-format
-msgid "Here the managed component observes many events which change the underlying object. The component manages these actions itself, and because the object is unwrapped on every access, a consistent view is provided."
+msgid ""
+"Here the managed component observes many events which change the underlying "
+"object. The component manages these actions itself, and because the object "
+"is unwrapped on every access, a consistent view is provided."
msgstr ""
-
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Configuration.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,7 +5,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-12-04 00:58+0000\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
"PO-Revision-Date: 2008-12-31 16:43+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
@@ -22,8 +22,20 @@
#. Tag: para
#: Configuration.xml:6
#, no-c-format
-msgid "Configuration is a very boring topic and an extremely tedious pastime. Unfortunately, several lines of XML are required to integrate Seam into your JSF implementation and servlet container. There's no need to be too put off by the following sections; you'll never need to type any of this stuff yourself, since you can just use seam-gen to start your application or you can copy and paste from the example applications!"
-msgstr "La configurazione è un argomento molto noioso ed un passatempo estremamente tedioso. Sfortunatamente sono richieste parecchie linee di XML per integrare Seam con l'implementazione JSF ed il servlet container. Non c'è alcun bisogno di soffermarsi sulle seguenti sezioni; non si dovrà mai scrivere queste cose a mano, poiché basta usare seam-gen per iniziare l'applicazione oppure basta copiare ed incollare il codice dagli esempi di applicazione!"
+msgid ""
+"Configuration is a very boring topic and an extremely tedious pastime. "
+"Unfortunately, several lines of XML are required to integrate Seam into your "
+"JSF implementation and servlet container. There's no need to be too put off "
+"by the following sections; you'll never need to type any of this stuff "
+"yourself, since you can just use seam-gen to start your application or you "
+"can copy and paste from the example applications!"
+msgstr ""
+"La configurazione è un argomento molto noioso ed un passatempo estremamente "
+"tedioso. Sfortunatamente sono richieste parecchie linee di XML per integrare "
+"Seam con l'implementazione JSF ed il servlet container. Non c'è alcun "
+"bisogno di soffermarsi sulle seguenti sezioni; non si dovrà mai scrivere "
+"queste cose a mano, poiché basta usare seam-gen per iniziare l'applicazione "
+"oppure basta copiare ed incollare il codice dagli esempi di applicazione!"
#. Tag: title
#: Configuration.xml:12
@@ -34,7 +46,9 @@
#. Tag: para
#: Configuration.xml:14
#, no-c-format
-msgid "First, let's look at the basic configuration that is needed whenever we use Seam with JSF."
+msgid ""
+"First, let's look at the basic configuration that is needed whenever we use "
+"Seam with JSF."
msgstr ""
#. Tag: title
@@ -84,7 +98,9 @@
#. Tag: para
#: Configuration.xml:25
#, no-c-format
-msgid "In addition, Seam requires the following entry in your <literal>web.xml</literal> file:"
+msgid ""
+"In addition, Seam requires the following entry in your <literal>web.xml</"
+"literal> file:"
msgstr ""
#. Tag: programlisting
@@ -102,13 +118,20 @@
#. Tag: para
#: Configuration.xml:29
#, no-c-format
-msgid "This listener is responsible for bootstrapping Seam, and for destroying session and application contexts."
+msgid ""
+"This listener is responsible for bootstrapping Seam, and for destroying "
+"session and application contexts."
msgstr ""
#. Tag: para
#: Configuration.xml:32
#, no-c-format
-msgid "Some JSF implementations have a broken implementation of server-side state saving that interferes with Seam's conversation propagation. If you have problems with conversation propagation during form submissions, try switching to client-side state saving. You'll need this in <literal>web.xml</literal>:"
+msgid ""
+"Some JSF implementations have a broken implementation of server-side state "
+"saving that interferes with Seam's conversation propagation. If you have "
+"problems with conversation propagation during form submissions, try "
+"switching to client-side state saving. You'll need this in <literal>web.xml</"
+"literal>:"
msgstr ""
#. Tag: programlisting
@@ -128,7 +151,18 @@
#. Tag: para
#: Configuration.xml:38
#, no-c-format
-msgid "There is a minor gray area in the JSF specification regarding the mutability of view state values. Since Seam uses the JSF view state to back its PAGE scope this can become an issue in some cases. If you're using server side state saving with the JSF-RI and you want a PAGE scoped bean to keep its exact value for a given view of a page you will need to specify the following context-param. Otherwise if a user uses the \"back\" button a PAGE scoped component will have the latest value if it has changed not the value of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This setting is not enabled by default because of the performance hit of serializing the JSF view with every request."
+msgid ""
+"There is a minor gray area in the JSF specification regarding the mutability "
+"of view state values. Since Seam uses the JSF view state to back its PAGE "
+"scope this can become an issue in some cases. If you're using server side "
+"state saving with the JSF-RI and you want a PAGE scoped bean to keep its "
+"exact value for a given view of a page you will need to specify the "
+"following context-param. Otherwise if a user uses the \"back\" button a PAGE "
+"scoped component will have the latest value if it has changed not the value "
+"of the \"back\" page. (see <ulink url=\"https://javaserverfaces-spec-public."
+"dev.java.net/issues/show_bug.cgi?id=295\"> Spec Issue </ulink> ). This "
+"setting is not enabled by default because of the performance hit of "
+"serializing the JSF view with every request."
msgstr ""
#. Tag: programlisting
@@ -154,7 +188,9 @@
#. Tag: para
#: Configuration.xml:58
#, no-c-format
-msgid "If you want follow our advice and use Facelets instead of JSP, add the following lines to <literal>faces-config.xml</literal>:"
+msgid ""
+"If you want follow our advice and use Facelets instead of JSP, add the "
+"following lines to <literal>faces-config.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -192,7 +228,16 @@
#. Tag: para
#: Configuration.xml:67
#, no-c-format
-msgid "If you are using facelets in JBoss AS, you'll find that Facelets logging is broken (the log messages don't make it to the server log). Seam provides a bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/lib</literal> of your application. The Facelets logging catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/nonav/docs/dev/docbook.html#config-logging\">Facelets Developer Documentation</ulink>."
+msgid ""
+"If you are using facelets in JBoss AS, you'll find that Facelets logging is "
+"broken (the log messages don't make it to the server log). Seam provides a "
+"bridge to fix this, to use it copy <literal>lib/interop/jboss-seam-jul.jar</"
+"literal> to <literal>$JBOSS_HOME/server/default/deploy/jboss-web.deployer/"
+"jsf-libs/</literal> and include the <literal>jboss-seam-ui.jar</literal> in "
+"the <literal>WEB-INF/lib</literal> of your application. The Facelets logging "
+"catagories are itemized in the <ulink url=\"https://facelets.dev.java.net/"
+"nonav/docs/dev/docbook.html#config-logging\">Facelets Developer "
+"Documentation</ulink>."
msgstr ""
#. Tag: title
@@ -204,7 +249,10 @@
#. Tag: para
#: Configuration.xml:83
#, no-c-format
-msgid "The Seam Resource Servlet provides resources used by Seam Remoting, captchas (see the security chapter) and some JSF UI controls. Configuring the Seam Resource Servlet requires the following entry in <literal>web.xml</literal>:"
+msgid ""
+"The Seam Resource Servlet provides resources used by Seam Remoting, captchas "
+"(see the security chapter) and some JSF UI controls. Configuring the Seam "
+"Resource Servlet requires the following entry in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -240,7 +288,12 @@
#. Tag: para
#: Configuration.xml:93
#, no-c-format
-msgid "Seam doesn't need any servlet filters for basic operation. However, there are several features which depend upon the use of filters. To make things easier, Seam lets you add and configure servlet filters just like you would configure other built-in Seam components. To take advantage of this feature, we must first install a master filter in <literal>web.xml</literal>:"
+msgid ""
+"Seam doesn't need any servlet filters for basic operation. However, there "
+"are several features which depend upon the use of filters. To make things "
+"easier, Seam lets you add and configure servlet filters just like you would "
+"configure other built-in Seam components. To take advantage of this feature, "
+"we must first install a master filter in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -270,25 +323,36 @@
#. Tag: para
#: Configuration.xml:100
#, no-c-format
-msgid "The Seam master filter <emphasis>must</emphasis> be the first filter specified in <literal>web.xml</literal>. This ensures it is run first."
+msgid ""
+"The Seam master filter <emphasis>must</emphasis> be the first filter "
+"specified in <literal>web.xml</literal>. This ensures it is run first."
msgstr ""
#. Tag: para
#: Configuration.xml:103
#, no-c-format
-msgid "The Seam filters share a number of common attributes, you can set these in <literal>components.xml</literal> in addition to any parameters discussed below:"
+msgid ""
+"The Seam filters share a number of common attributes, you can set these in "
+"<literal>components.xml</literal> in addition to any parameters discussed "
+"below:"
msgstr ""
#. Tag: para
#: Configuration.xml:111
#, no-c-format
-msgid "<literal>url-pattern</literal> — Used to specify which requests are filtered, the default is all requests. <literal>url-pattern</literal> is a Tomcat style pattern which allows a wildcard suffix."
+msgid ""
+"<literal>url-pattern</literal> — Used to specify which requests are "
+"filtered, the default is all requests. <literal>url-pattern</literal> is a "
+"Tomcat style pattern which allows a wildcard suffix."
msgstr ""
#. Tag: para
#: Configuration.xml:118
#, no-c-format
-msgid "<literal>regex-url-pattern</literal> — Used to specify which requests are filtered, the default is all requests. <literal>regex-url-pattern</literal> is a true regular expression match for request path."
+msgid ""
+"<literal>regex-url-pattern</literal> — Used to specify which requests "
+"are filtered, the default is all requests. <literal>regex-url-pattern</"
+"literal> is a true regular expression match for request path."
msgstr ""
#. Tag: para
@@ -300,7 +364,10 @@
#. Tag: para
#: Configuration.xml:131
#, no-c-format
-msgid "Note that the patterns are matched against the URI path of the request (see <literal>HttpServletRequest.getURIPath()</literal>) and that the name of the servlet context is removed before matching."
+msgid ""
+"Note that the patterns are matched against the URI path of the request (see "
+"<literal>HttpServletRequest.getURIPath()</literal>) and that the name of the "
+"servlet context is removed before matching."
msgstr ""
#. Tag: para
@@ -318,13 +385,24 @@
#. Tag: para
#: Configuration.xml:141
#, no-c-format
-msgid "This filter provides the exception mapping functionality in <literal>pages.xml</literal> (almost all applications will need this). It also takes care of rolling back uncommitted transactions when uncaught exceptions occur. (According to the Java EE specification, the web container should do this automatically, but we've found that this behavior cannot be relied upon in all application servers. And it is certainly not required of plain servlet engines like Tomcat.)"
+msgid ""
+"This filter provides the exception mapping functionality in <literal>pages."
+"xml</literal> (almost all applications will need this). It also takes care "
+"of rolling back uncommitted transactions when uncaught exceptions occur. "
+"(According to the Java EE specification, the web container should do this "
+"automatically, but we've found that this behavior cannot be relied upon in "
+"all application servers. And it is certainly not required of plain servlet "
+"engines like Tomcat.)"
msgstr ""
#. Tag: para
#: Configuration.xml:147
#, no-c-format
-msgid "By default, the exception handling filter will process all requests, however this behavior may be adjusted by adding a <literal><web:exception-filter></literal> entry to <literal>components.xml</literal>, as shown in this example:"
+msgid ""
+"By default, the exception handling filter will process all requests, however "
+"this behavior may be adjusted by adding a <literal><web:exception-"
+"filter></literal> entry to <literal>components.xml</literal>, as shown in "
+"this example:"
msgstr ""
#. Tag: programlisting
@@ -354,13 +432,18 @@
#. Tag: para
#: Configuration.xml:158
#, no-c-format
-msgid "This filter allows Seam to propagate the conversation context across browser redirects. It intercepts any browser redirects and adds a request parameter that specifies the Seam conversation identifier."
+msgid ""
+"This filter allows Seam to propagate the conversation context across browser "
+"redirects. It intercepts any browser redirects and adds a request parameter "
+"that specifies the Seam conversation identifier."
msgstr ""
#. Tag: para
#: Configuration.xml:162
#, no-c-format
-msgid "The redirect filter will process all requests by default, but this behavior can also be adjusted in <literal>components.xml</literal>:"
+msgid ""
+"The redirect filter will process all requests by default, but this behavior "
+"can also be adjusted in <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -378,7 +461,11 @@
#. Tag: para
#: Configuration.xml:171
#, no-c-format
-msgid "This filter allows Seam to apply URL rewriting for views based on configuration in the <literal>pages.xml</literal> file. This filter is not activate by default, but can be activated by adding the configuration to <literal>components.xml</literal>:"
+msgid ""
+"This filter allows Seam to apply URL rewriting for views based on "
+"configuration in the <literal>pages.xml</literal> file. This filter is not "
+"activate by default, but can be activated by adding the configuration to "
+"<literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -390,7 +477,10 @@
#. Tag: para
#: Configuration.xml:179
#, no-c-format
-msgid "The <literal>view-mapping</literal> parameter must match the servlet mapping defined for the Faces Servlet in the <literal>web.xml</literal> file. If ommitted, the rewrite filter assumes the pattern <literal>*.seam</literal>."
+msgid ""
+"The <literal>view-mapping</literal> parameter must match the servlet mapping "
+"defined for the Faces Servlet in the <literal>web.xml</literal> file. If "
+"ommitted, the rewrite filter assumes the pattern <literal>*.seam</literal>."
msgstr ""
#. Tag: title
@@ -402,7 +492,11 @@
#. Tag: para
#: Configuration.xml:187
#, no-c-format
-msgid "This feature is necessary when using the Seam file upload JSF control. It detects multipart form requests and processes them according to the multipart/form-data specification (RFC-2388). To override the default settings, add the following entry to <literal>components.xml</literal>:"
+msgid ""
+"This feature is necessary when using the Seam file upload JSF control. It "
+"detects multipart form requests and processes them according to the "
+"multipart/form-data specification (RFC-2388). To override the default "
+"settings, add the following entry to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -420,13 +514,21 @@
#. Tag: para
#: Configuration.xml:195
#, no-c-format
-msgid "<literal>create-temp-files</literal> — If set to <literal>true</literal>, uploaded files are written to a temporary file (instead of held in memory). This may be an important consideration if large file uploads are expected. The default setting is <literal>false</literal>."
+msgid ""
+"<literal>create-temp-files</literal> — If set to <literal>true</"
+"literal>, uploaded files are written to a temporary file (instead of held in "
+"memory). This may be an important consideration if large file uploads are "
+"expected. The default setting is <literal>false</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:202
#, no-c-format
-msgid "<literal>max-request-size</literal> — If the size of a file upload request (determined by reading the <literal>Content-Length</literal> header in the request) exceeds this value, the request will be aborted. The default setting is 0 (no size limit)."
+msgid ""
+"<literal>max-request-size</literal> — If the size of a file upload "
+"request (determined by reading the <literal>Content-Length</literal> header "
+"in the request) exceeds this value, the request will be aborted. The default "
+"setting is 0 (no size limit)."
msgstr ""
#. Tag: title
@@ -442,10 +544,11 @@
msgstr ""
#. Tag: para
-#: Configuration.xml:214
-#: Configuration.xml:309
+#: Configuration.xml:214 Configuration.xml:309
#, no-c-format
-msgid "This filter is not installed by default and requires an entry in <literal>components.xml</literal> to enable it:"
+msgid ""
+"This filter is not installed by default and requires an entry in "
+"<literal>components.xml</literal> to enable it:"
msgstr ""
#. Tag: programlisting
@@ -469,7 +572,13 @@
#. Tag: para
#: Configuration.xml:225
#, no-c-format
-msgid "<literal>override-client</literal> — If this is set to <literal>true</literal>, the request encoding will be set to whatever is specified by <literal>encoding</literal> no matter whether the request already specifies an encoding or not. If set to <literal>false</literal>, the request encoding will only be set if the request doesn't already specify an encoding. The default setting is <literal>false</literal>."
+msgid ""
+"<literal>override-client</literal> — If this is set to <literal>true</"
+"literal>, the request encoding will be set to whatever is specified by "
+"<literal>encoding</literal> no matter whether the request already specifies "
+"an encoding or not. If set to <literal>false</literal>, the request encoding "
+"will only be set if the request doesn't already specify an encoding. The "
+"default setting is <literal>false</literal>."
msgstr ""
#. Tag: title
@@ -481,19 +590,28 @@
#. Tag: para
#: Configuration.xml:238
#, no-c-format
-msgid "If RichFaces is used in your project, Seam will install the RichFaces Ajax filter for you, making sure to install it before all other built-in filters. You don't need to install the RichFaces Ajax filter in <literal>web.xml</literal> yourself."
+msgid ""
+"If RichFaces is used in your project, Seam will install the RichFaces Ajax "
+"filter for you, making sure to install it before all other built-in filters. "
+"You don't need to install the RichFaces Ajax filter in <literal>web.xml</"
+"literal> yourself."
msgstr ""
#. Tag: para
#: Configuration.xml:246
#, no-c-format
-msgid "The RichFaces Ajax filter is only installed if the RichFaces jars are present in your project."
+msgid ""
+"The RichFaces Ajax filter is only installed if the RichFaces jars are "
+"present in your project."
msgstr ""
#. Tag: para
#: Configuration.xml:251
#, no-c-format
-msgid "To override the default settings, add the following entry to <literal>components.xml</literal>. The options are the same as those specified in the RichFaces Developer Guide:"
+msgid ""
+"To override the default settings, add the following entry to "
+"<literal>components.xml</literal>. The options are the same as those "
+"specified in the RichFaces Developer Guide:"
msgstr ""
#. Tag: programlisting
@@ -513,19 +631,31 @@
#. Tag: para
#: Configuration.xml:257
#, no-c-format
-msgid "<literal>force-parser</literal> — forces all JSF pages to be validated by Richfaces's XML syntax checker. If <literal>false</literal>, only AJAX responses are validated and converted to well-formed XML. Setting <literal>force-parser</literal> to <literal>false</literal> improves performance, but can provide visual artifacts on AJAX updates."
+msgid ""
+"<literal>force-parser</literal> — forces all JSF pages to be validated "
+"by Richfaces's XML syntax checker. If <literal>false</literal>, only AJAX "
+"responses are validated and converted to well-formed XML. Setting "
+"<literal>force-parser</literal> to <literal>false</literal> improves "
+"performance, but can provide visual artifacts on AJAX updates."
msgstr ""
#. Tag: para
#: Configuration.xml:265
#, no-c-format
-msgid "<literal>enable-cache</literal> — enables caching of framework-generated resources (e.g. javascript, CSS, images, etc). When developing custom javascript or CSS, setting to true prevents the browser from caching the resource."
+msgid ""
+"<literal>enable-cache</literal> — enables caching of framework-"
+"generated resources (e.g. javascript, CSS, images, etc). When developing "
+"custom javascript or CSS, setting to true prevents the browser from caching "
+"the resource."
msgstr ""
#. Tag: para
#: Configuration.xml:271
#, no-c-format
-msgid "<literal>log4j-init-file</literal> — is used to setup per-application logging. A path, relative to web application context, to the log4j.xml configuration file should be provided."
+msgid ""
+"<literal>log4j-init-file</literal> — is used to setup per-application "
+"logging. A path, relative to web application context, to the log4j.xml "
+"configuration file should be provided."
msgstr ""
#. Tag: title
@@ -537,13 +667,20 @@
#. Tag: para
#: Configuration.xml:283
#, no-c-format
-msgid "This filter adds the authenticated user name to the log4j mapped diagnostic context so that it can be included in formatted log output if desired, by adding %X{username} to the pattern."
+msgid ""
+"This filter adds the authenticated user name to the log4j mapped diagnostic "
+"context so that it can be included in formatted log output if desired, by "
+"adding %X{username} to the pattern."
msgstr ""
#. Tag: para
#: Configuration.xml:289
#, no-c-format
-msgid "By default, the logging filter will process all requests, however this behavior may be adjusted by adding a <literal><web:logging-filter></literal> entry to <literal>components.xml</literal>, as shown in this example:"
+msgid ""
+"By default, the logging filter will process all requests, however this "
+"behavior may be adjusted by adding a <literal><web:logging-filter></"
+"literal> entry to <literal>components.xml</literal>, as shown in this "
+"example:"
msgstr ""
#. Tag: programlisting
@@ -569,13 +706,22 @@
#. Tag: para
#: Configuration.xml:299
#, no-c-format
-msgid "Requests sent direct to some servlet other than the JSF servlet are not processed through the JSF lifecycle, so Seam provides a servlet filter that can be applied to any other servlet that needs access to Seam components."
+msgid ""
+"Requests sent direct to some servlet other than the JSF servlet are not "
+"processed through the JSF lifecycle, so Seam provides a servlet filter that "
+"can be applied to any other servlet that needs access to Seam components."
msgstr ""
#. Tag: para
#: Configuration.xml:303
#, no-c-format
-msgid "This filter allows custom servlets to interact with the Seam contexts. It sets up the Seam contexts at the beginning of each request, and tears them down at the end of the request. You should make sure that this filter is <emphasis>never</emphasis> applied to the JSF <literal>FacesServlet</literal>. Seam uses the phase listener for context management in a JSF request."
+msgid ""
+"This filter allows custom servlets to interact with the Seam contexts. It "
+"sets up the Seam contexts at the beginning of each request, and tears them "
+"down at the end of the request. You should make sure that this filter is "
+"<emphasis>never</emphasis> applied to the JSF <literal>FacesServlet</"
+"literal>. Seam uses the phase listener for context management in a JSF "
+"request."
msgstr ""
#. Tag: programlisting
@@ -587,13 +733,19 @@
#. Tag: para
#: Configuration.xml:314
#, no-c-format
-msgid "The context filter expects to find the conversation id of any conversation context in a request parameter named <literal>conversationId</literal>. You are responsible for ensuring that it gets sent in the request."
+msgid ""
+"The context filter expects to find the conversation id of any conversation "
+"context in a request parameter named <literal>conversationId</literal>. You "
+"are responsible for ensuring that it gets sent in the request."
msgstr ""
#. Tag: para
#: Configuration.xml:318
#, no-c-format
-msgid "You are also responsible for ensuring propagation of any new conversation id back to the client. Seam exposes the conversation id as a property of the built in component <literal>conversation</literal>."
+msgid ""
+"You are also responsible for ensuring propagation of any new conversation id "
+"back to the client. Seam exposes the conversation id as a property of the "
+"built in component <literal>conversation</literal>."
msgstr ""
#. Tag: title
@@ -605,7 +757,13 @@
#. Tag: para
#: Configuration.xml:327
#, no-c-format
-msgid "Seam can install your filters for you, allowing you to specify <emphasis>where</emphasis> in the chain your filter is placed (the servlet specification doesn't provide a well defined order if you specify your filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</literal> annotation to your Seam component (which must implement <literal>javax.servlet.Filter</literal>):"
+msgid ""
+"Seam can install your filters for you, allowing you to specify "
+"<emphasis>where</emphasis> in the chain your filter is placed (the servlet "
+"specification doesn't provide a well defined order if you specify your "
+"filters in a <literal>web.xml</literal>). Just add the <literal>@Filter</"
+"literal> annotation to your Seam component (which must implement "
+"<literal>javax.servlet.Filter</literal>):"
msgstr ""
#. Tag: programlisting
@@ -629,7 +787,12 @@
#. Tag: para
#: Configuration.xml:334
#, no-c-format
-msgid "Adding the <literal>@Startup</literal> annotation means thar the component is available during Seam startup; bijection isn't available here (<literal>@BypassInterceptors</literal>); and the filter should be further down the chain than the RichFaces filter (<literal>@Filter(within=\"org.jboss.seam.web.ajax4jsfFilter\")</literal>)."
+msgid ""
+"Adding the <literal>@Startup</literal> annotation means thar the component "
+"is available during Seam startup; bijection isn't available here "
+"(<literal>@BypassInterceptors</literal>); and the filter should be further "
+"down the chain than the RichFaces filter (<literal>@Filter(within=\"org."
+"jboss.seam.web.ajax4jsfFilter\")</literal>)."
msgstr ""
#. Tag: title
@@ -641,13 +804,24 @@
#. Tag: para
#: Configuration.xml:345
#, no-c-format
-msgid "In a Seam application, EJB components have a certain duality, as they are managed by both the EJB container and Seam. Actually, it's more that Seam resolves EJB component references, manages the lifetime of stateful session bean components, and also participates in each method call via interceptors. Let's start with the configuration of the Seam interceptor chain."
+msgid ""
+"In a Seam application, EJB components have a certain duality, as they are "
+"managed by both the EJB container and Seam. Actually, it's more that Seam "
+"resolves EJB component references, manages the lifetime of stateful session "
+"bean components, and also participates in each method call via interceptors. "
+"Let's start with the configuration of the Seam interceptor chain."
msgstr ""
#. Tag: para
#: Configuration.xml:350
#, no-c-format
-msgid "We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB components. This interceptor delegates to a set of built-in server-side interceptors that handle such concerns as bijection, conversation demarcation, and business process signals. The simplest way to do this across an entire application is to add the following interceptor configuration in <literal>ejb-jar.xml</literal>:"
+msgid ""
+"We need to apply the <literal>SeamInterceptor</literal> to our Seam EJB "
+"components. This interceptor delegates to a set of built-in server-side "
+"interceptors that handle such concerns as bijection, conversation "
+"demarcation, and business process signals. The simplest way to do this "
+"across an entire application is to add the following interceptor "
+"configuration in <literal>ejb-jar.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -656,28 +830,32 @@
msgid ""
"<![CDATA[<interceptors>\n"
" <interceptor>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
+"class>\n"
" </interceptor>\n"
"</interceptors>\n"
" \n"
"<assembly-descriptor>\n"
" <interceptor-binding>\n"
" <ejb-name>*</ejb-name>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-"
+"class>\n"
" </interceptor-binding>\n"
"</assembly-descriptor>\n"
"]]>"
msgstr ""
"<![CDATA[<interceptors>\n"
" <interceptor>\n"
-" <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>\n"
+" <interceptor-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"
"]]>"
@@ -685,7 +863,15 @@
#. Tag: para
#: Configuration.xml:357
#, no-c-format
-msgid "Seam needs to know where to go to find session beans in JNDI. One way to do this is specify the <literal>@JndiName</literal> annotation on every session bean Seam component. However, this is quite tedious. A better approach is to specify a pattern that Seam can use to calculate the JNDI name from the EJB name. Unfortunately, there is no standard mapping to global JNDI defined in the EJB3 specification, so this mapping is vendor-specific (and may depend on your own naming conventions as well). We usually specify this option in <literal>components.xml</literal>."
+msgid ""
+"Seam needs to know where to go to find session beans in JNDI. One way to do "
+"this is specify the <literal>@JndiName</literal> annotation on every session "
+"bean Seam component. However, this is quite tedious. A better approach is to "
+"specify a pattern that Seam can use to calculate the JNDI name from the EJB "
+"name. Unfortunately, there is no standard mapping to global JNDI defined in "
+"the EJB3 specification, so this mapping is vendor-specific (and may depend "
+"on your own naming conventions as well). We usually specify this option in "
+"<literal>components.xml</literal>."
msgstr ""
#. Tag: para
@@ -703,13 +889,20 @@
#. Tag: para
#: Configuration.xml:368
#, no-c-format
-msgid "In this case, <literal>earName</literal> is the name of the EAR in which the bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name of the EJB, and the final segment represents the type of interface (local or remote)."
+msgid ""
+"In this case, <literal>earName</literal> is the name of the EAR in which the "
+"bean is deployed, Seam replaces <literal>#{ejbName}</literal> with the name "
+"of the EJB, and the final segment represents the type of interface (local or "
+"remote)."
msgstr ""
#. Tag: para
#: Configuration.xml:372
#, no-c-format
-msgid "Outside the context of an EAR (when using the JBoss Embeddable EJB3 container), the first segment is dropped since there is no EAR, leaving us with the following pattern:"
+msgid ""
+"Outside the context of an EAR (when using the JBoss Embeddable EJB3 "
+"container), the first segment is dropped since there is no EAR, leaving us "
+"with the following pattern:"
msgstr ""
#. Tag: programlisting
@@ -721,25 +914,36 @@
#. Tag: para
#: Configuration.xml:377
#, no-c-format
-msgid "How these JNDI names are resolved and somehow locate an EJB component might appear a bit like black magic at this point, so let's dig into the details. First, let's talk about how the EJB components get into JNDI."
+msgid ""
+"How these JNDI names are resolved and somehow locate an EJB component might "
+"appear a bit like black magic at this point, so let's dig into the details. "
+"First, let's talk about how the EJB components get into JNDI."
msgstr ""
#. Tag: para
#: Configuration.xml:381
#, no-c-format
-msgid "The folks at JBoss don't care much for XML, if you can't tell. So when they designed JBoss AS, they decided that EJB components would get assigned a global JNDI name automatically, using the pattern just described (i.e., EAR name/EJB name/interface type). The EJB name is the first non-empty value from the following list:"
+msgid ""
+"The folks at JBoss don't care much for XML, if you can't tell. So when they "
+"designed JBoss AS, they decided that EJB components would get assigned a "
+"global JNDI name automatically, using the pattern just described (i.e., EAR "
+"name/EJB name/interface type). The EJB name is the first non-empty value "
+"from the following list:"
msgstr ""
#. Tag: para
#: Configuration.xml:387
#, no-c-format
-msgid "The value of the <literal><ejb-name></literal> element in ejb-jar.xml"
+msgid ""
+"The value of the <literal><ejb-name></literal> element in ejb-jar.xml"
msgstr ""
#. Tag: para
#: Configuration.xml:390
#, no-c-format
-msgid "The value of the <literal>name</literal> attribute in the @Stateless or @Stateful annotation"
+msgid ""
+"The value of the <literal>name</literal> attribute in the @Stateless or "
+"@Stateful annotation"
msgstr ""
#. Tag: para
@@ -751,7 +955,9 @@
#. Tag: para
#: Configuration.xml:397
#, no-c-format
-msgid "Let's look at an example. Assume that you have the following EJB bean and interface defined."
+msgid ""
+"Let's look at an example. Assume that you have the following EJB bean and "
+"interface defined."
msgstr ""
#. Tag: programlisting
@@ -805,19 +1011,36 @@
#. Tag: para
#: Configuration.xml:401
#, no-c-format
-msgid "Assuming your EJB bean class is deployed in an EAR named myapp, the global JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. As you learned, you can reference this EJB component as a Seam component with the name <literal>authenticator</literal> and Seam will take care of finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</literal> annotation)."
+msgid ""
+"Assuming your EJB bean class is deployed in an EAR named myapp, the global "
+"JNDI name myapp/AuthenticatorBean/local will be assigned to it on JBoss AS. "
+"As you learned, you can reference this EJB component as a Seam component "
+"with the name <literal>authenticator</literal> and Seam will take care of "
+"finding it in JNDI according to the JNDI pattern (or <literal>@JndiName</"
+"literal> annotation)."
msgstr ""
#. Tag: para
#: Configuration.xml:407
#, no-c-format
-msgid "So what about the rest of the application servers? Well, according to the Java EE spec, which most vendors try to adhere to religiously, you have to declare an EJB reference for your EJB in order for it to be assigned a JNDI name. That requires some XML. It also means that it is up to you to establish a JNDI naming convention so that you can leverage the Seam JNDI pattern. You might find the JBoss convention a good one to follow."
+msgid ""
+"So what about the rest of the application servers? Well, according to the "
+"Java EE spec, which most vendors try to adhere to religiously, you have to "
+"declare an EJB reference for your EJB in order for it to be assigned a JNDI "
+"name. That requires some XML. It also means that it is up to you to "
+"establish a JNDI naming convention so that you can leverage the Seam JNDI "
+"pattern. You might find the JBoss convention a good one to follow."
msgstr ""
#. Tag: para
#: Configuration.xml:413
#, no-c-format
-msgid "There are two places you have to define the EJB reference when using Seam on non-JBoss application servers. If you are going to be looking up the Seam EJB component through JSF (in a JSF view or as a JSF action listener) or a Seam JavaBean component, then you must declare the EJB reference in web.xml. Here is the EJB reference for the example component just shown:"
+msgid ""
+"There are two places you have to define the EJB reference when using Seam on "
+"non-JBoss application servers. If you are going to be looking up the Seam "
+"EJB component through JSF (in a JSF view or as a JSF action listener) or a "
+"Seam JavaBean component, then you must declare the EJB reference in web.xml. "
+"Here is the EJB reference for the example component just shown:"
msgstr ""
#. Tag: programlisting
@@ -841,19 +1064,36 @@
#. Tag: para
#: Configuration.xml:420
#, no-c-format
-msgid "This reference will cover most uses of the component in a Seam application. However, if you want to be able to inject a Seam EJB component into another Seam EJB component using <literal>@In</literal>, you need to define this EJB reference in another location. This time, it must be defined in ejb-jar.xml, and it's a bit tricker."
+msgid ""
+"This reference will cover most uses of the component in a Seam application. "
+"However, if you want to be able to inject a Seam EJB component into another "
+"Seam EJB component using <literal>@In</literal>, you need to define this EJB "
+"reference in another location. This time, it must be defined in ejb-jar.xml, "
+"and it's a bit tricker."
msgstr ""
#. Tag: para
#: Configuration.xml:425
#, no-c-format
-msgid "Within the context of an EJB method call, you have to deal with a somewhat sheltered JNDI context. When Seam attempts to find another Seam EJB component to satisfy an injection point defined using <literal>@In</literal>, it isn't going to be successful looking up the component in JNDI. You cannot simply resolve JNDI names as you please. You have to define those references explicitly. Unlike with the web context, however, you cannot declare EJB references globally for all EJB components. Instead, you have to specify the JNDI resources for a given EJB component one-by-one (this applies to JBoss AS 5 in addition to non-JBoss application servers)."
+msgid ""
+"Within the context of an EJB method call, you have to deal with a somewhat "
+"sheltered JNDI context. When Seam attempts to find another Seam EJB "
+"component to satisfy an injection point defined using <literal>@In</"
+"literal>, it isn't going to be successful looking up the component in JNDI. "
+"You cannot simply resolve JNDI names as you please. You have to define those "
+"references explicitly. Unlike with the web context, however, you cannot "
+"declare EJB references globally for all EJB components. Instead, you have to "
+"specify the JNDI resources for a given EJB component one-by-one (this "
+"applies to JBoss AS 5 in addition to non-JBoss application servers)."
msgstr ""
#. Tag: para
#: Configuration.xml:433
#, no-c-format
-msgid "Let's assume that we have an EJB named RegisterAction (the name is resolved using the three steps mentioned previously). That EJB has the following Seam injection:"
+msgid ""
+"Let's assume that we have an EJB named RegisterAction (the name is resolved "
+"using the three steps mentioned previously). That EJB has the following Seam "
+"injection:"
msgstr ""
#. Tag: programlisting
@@ -871,7 +1111,9 @@
#. Tag: para
#: Configuration.xml:438
#, no-c-format
-msgid "In order for this injection to work, the link must be established in the ejb-jar.xml file as follows:"
+msgid ""
+"In order for this injection to work, the link must be established in the ejb-"
+"jar.xml file as follows:"
msgstr ""
#. Tag: programlisting
@@ -883,7 +1125,8 @@
" <session>\n"
" <ejb-name>RegisterAction</ejb-name>\n"
" <ejb-local-ref>\n"
-" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n"
+" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-"
+"name>\n"
" <ejb-ref-type>Session</ejb-ref-type>\n"
" <local>com.example.myapp.Authenticator</local>\n"
" </ejb-local-ref>\n"
@@ -900,7 +1143,8 @@
" <session>\n"
" <ejb-name>RegisterAction</ejb-name>\n"
" <ejb-local-ref>\n"
-" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-name>\n"
+" <ejb-ref-name>myapp/AuthenticatorAction/local</ejb-ref-"
+"name>\n"
" <ejb-ref-type>Session</ejb-ref-type>\n"
" <local>com.example.myapp.Authenticator</local>\n"
" </ejb-local-ref>\n"
@@ -915,31 +1159,66 @@
#. Tag: para
#: Configuration.xml:442
#, no-c-format
-msgid "Notice that the contents of the <literal><ejb-local-ref></literal> are identical to what we defined in web.xml. What we are doing is bringing the reference into the EJB context where it can be used by the RegisterAction bean. You will need to add one of these references for any injection of a Seam EJB compoenent into another Seam EJB component using <literal>@In</literal>. (You can see an example of this setup in the jee5/booking example)."
+msgid ""
+"Notice that the contents of the <literal><ejb-local-ref></literal> are "
+"identical to what we defined in web.xml. What we are doing is bringing the "
+"reference into the EJB context where it can be used by the RegisterAction "
+"bean. You will need to add one of these references for any injection of a "
+"Seam EJB compoenent into another Seam EJB component using <literal>@In</"
+"literal>. (You can see an example of this setup in the jee5/booking example)."
msgstr ""
#. Tag: para
#: Configuration.xml:448
#, no-c-format
-msgid "But what about <literal>@EJB</literal>? It's true that you can inject one EJB into another using <literal>@EJB</literal>. However, by doing so, you are injecting the actual EJB reference rather than the Seam EJB component instance. In this case, some Seam features will work, while others won't. That's because Seam's interceptor is invoked on any method call to an EJB component. But that only invokes Seam's server-side interceptor chain. What you lose is Seam's state management and Seam's client-side interceptor chain. Client-side interceptors handle concerns such as security and concurrency. Also, when injecting a SFSB, there is no guarantee that you will get the SFSB bound to the active session or conversation, whatever the case may be. Thus, you definitely want to inject the Seam EJB component using <literal>@In</literal>."
+msgid ""
+"But what about <literal>@EJB</literal>? It's true that you can inject one "
+"EJB into another using <literal>@EJB</literal>. However, by doing so, you "
+"are injecting the actual EJB reference rather than the Seam EJB component "
+"instance. In this case, some Seam features will work, while others won't. "
+"That's because Seam's interceptor is invoked on any method call to an EJB "
+"component. But that only invokes Seam's server-side interceptor chain. What "
+"you lose is Seam's state management and Seam's client-side interceptor "
+"chain. Client-side interceptors handle concerns such as security and "
+"concurrency. Also, when injecting a SFSB, there is no guarantee that you "
+"will get the SFSB bound to the active session or conversation, whatever the "
+"case may be. Thus, you definitely want to inject the Seam EJB component "
+"using <literal>@In</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:458
#, no-c-format
-msgid "That covers how JNDI names are defined and used. The lesson is that with some application servers, such as GlassFish, you are going to have to specify JNDI names for all EJB components explicitly, and sometimes twice! And even if you are following the same naming convention as JBoss AS, the JNDI pattern in Seam may need to be altered. For instance, the global JNDI names are automatically prefixed with java:comp/env on GlassFish, so you need to define the JNDI pattern as follows:"
+msgid ""
+"That covers how JNDI names are defined and used. The lesson is that with "
+"some application servers, such as GlassFish, you are going to have to "
+"specify JNDI names for all EJB components explicitly, and sometimes twice! "
+"And even if you are following the same naming convention as JBoss AS, the "
+"JNDI pattern in Seam may need to be altered. For instance, the global JNDI "
+"names are automatically prefixed with java:comp/env on GlassFish, so you "
+"need to define the JNDI pattern as follows:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:464
#, no-c-format
-msgid "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>"
-msgstr "<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]>"
+msgid ""
+"<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]"
+">"
+msgstr ""
+"<![CDATA[<core:init jndi-name=\"java:comp/env/earName/#{ejbName}/local\" />]]"
+">"
#. Tag: para
#: Configuration.xml:466
#, no-c-format
-msgid "Finally, let's talk about transactions. In an EJB3 environment, we recommend the use of a special built-in component for transaction management, that is fully aware of container transactions, and can correctly process transaction success events registered with the <literal>Events</literal> component. If you don't add this line to your <literal>components.xml</literal> file, Seam won't know when container-managed transactions end:"
+msgid ""
+"Finally, let's talk about transactions. In an EJB3 environment, we recommend "
+"the use of a special built-in component for transaction management, that is "
+"fully aware of container transactions, and can correctly process transaction "
+"success events registered with the <literal>Events</literal> component. If "
+"you don't add this line to your <literal>components.xml</literal> file, Seam "
+"won't know when container-managed transactions end:"
msgstr ""
#. Tag: programlisting
@@ -957,25 +1236,43 @@
#. Tag: para
#: Configuration.xml:480
#, no-c-format
-msgid "There is one final item you need to know about. You must place a <literal>seam.properties</literal>, <literal>META-INF/seam.properties</literal> or <literal>META-INF/components.xml</literal> file in any archive in which your Seam components are deployed (even an empty properties file will do). At startup, Seam will scan any archives with <literal>seam.properties</literal> files for seam components."
+msgid ""
+"There is one final item you need to know about. You must place a "
+"<literal>seam.properties</literal>, <literal>META-INF/seam.properties</"
+"literal> or <literal>META-INF/components.xml</literal> file in any archive "
+"in which your Seam components are deployed (even an empty properties file "
+"will do). At startup, Seam will scan any archives with <literal>seam."
+"properties</literal> files for seam components."
msgstr ""
#. Tag: para
#: Configuration.xml:485
#, no-c-format
-msgid "In a web archive (WAR) file, you must place a <literal>seam.properties</literal> file in the <literal>WEB-INF/classes</literal> directory if you have any Seam components included here."
+msgid ""
+"In a web archive (WAR) file, you must place a <literal>seam.properties</"
+"literal> file in the <literal>WEB-INF/classes</literal> directory if you "
+"have any Seam components included here."
msgstr ""
#. Tag: para
#: Configuration.xml:488
#, no-c-format
-msgid "That's why all the Seam examples have an empty <literal>seam.properties</literal> file. You can't just delete this file and expect everything to still work!"
+msgid ""
+"That's why all the Seam examples have an empty <literal>seam.properties</"
+"literal> file. You can't just delete this file and expect everything to "
+"still work!"
msgstr ""
#. Tag: para
#: Configuration.xml:491
#, no-c-format
-msgid "You might think this is silly and what kind of idiot framework designers would make an empty file affect the behavior of their software?? Well, this is a workaround for a limitation of the JVM—if we didn't use this mechanism, our next best option would be to force you to list every component explicitly in <literal>components.xml</literal>, just like some other competing frameworks do! I think you'll like our way better."
+msgid ""
+"You might think this is silly and what kind of idiot framework designers "
+"would make an empty file affect the behavior of their software?? Well, this "
+"is a workaround for a limitation of the JVM — if we didn't use this "
+"mechanism, our next best option would be to force you to list every "
+"component explicitly in <literal>components.xml</literal>, just like some "
+"other competing frameworks do! I think you'll like our way better."
msgstr ""
#. Tag: title
@@ -987,7 +1284,10 @@
#. Tag: para
#: Configuration.xml:504
#, no-c-format
-msgid "Seam comes packaged and configured with Hibernate as the default JPA provider. If you require using a different JPA provider you must tell <literal>seam</literal> about it."
+msgid ""
+"Seam comes packaged and configured with Hibernate as the default JPA "
+"provider. If you require using a different JPA provider you must tell "
+"<literal>seam</literal> about it."
msgstr ""
#. Tag: title
@@ -999,31 +1299,41 @@
#. Tag: para
#: Configuration.xml:511
#, no-c-format
-msgid "Configuration of the JPA provider will be easier in the future and will not require configuration changes, unless you are adding a custom persistence provider implementation."
+msgid ""
+"Configuration of the JPA provider will be easier in the future and will not "
+"require configuration changes, unless you are adding a custom persistence "
+"provider implementation."
msgstr ""
#. Tag: para
#: Configuration.xml:518
#, no-c-format
-msgid "Telling seam about a different JPA provider can be be done in one of two ways:"
+msgid ""
+"Telling seam about a different JPA provider can be be done in one of two "
+"ways:"
msgstr ""
#. Tag: para
#: Configuration.xml:519
#, no-c-format
-msgid "Update your application's <literal>components.xml</literal> so that the generic <literal>PersistenceProvider</literal> takes precedence over the hibernate version. Simply add the following to the file:"
+msgid ""
+"Update your application's <literal>components.xml</literal> so that the "
+"generic <literal>PersistenceProvider</literal> takes precedence over the "
+"hibernate version. Simply add the following to the file:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:524
#, no-c-format
msgid ""
-"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
+"\" \n"
" class=\"org.jboss.seam.persistence.PersistenceProvider\"\n"
" scope=\"stateless\">\n"
"</component>]]>"
msgstr ""
-"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
+"\" \n"
" class=\"org.jboss.seam.persistence.PersistenceProvider\"\n"
" scope=\"stateless\">\n"
"</component>]]>"
@@ -1031,25 +1341,37 @@
#. Tag: para
#: Configuration.xml:525
#, no-c-format
-msgid "If you want to take advantage of your JPA provider's non-standard features you will need to write you own implementation of the <literal>PersistenceProvider</literal>. Use <literal>HibernatePersistenceProvider</literal> as a starting point (don't forget to give back to the community :). Then you will need to tell <literal>seam</literal> to use it as before."
+msgid ""
+"If you want to take advantage of your JPA provider's non-standard features "
+"you will need to write you own implementation of the "
+"<literal>PersistenceProvider</literal>. Use "
+"<literal>HibernatePersistenceProvider</literal> as a starting point (don't "
+"forget to give back to the community :). Then you will need to tell "
+"<literal>seam</literal> to use it as before."
msgstr ""
#. Tag: programlisting
#: Configuration.xml:532
#, no-c-format
msgid ""
-"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
+"\" \n"
" class=\"org.your.package.YourPersistenceProvider\">\n"
"</component>]]>"
msgstr ""
-"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider\" \n"
+"<![CDATA[<component name=\"org.jboss.seam.persistence.persistenceProvider"
+"\" \n"
" class=\"org.your.package.YourPersistenceProvider\">\n"
"</component>]]>"
#. Tag: para
#: Configuration.xml:533
#, no-c-format
-msgid "All that is left is updating the <literal>persistence.xml</literal> file with the correct provider class, and what ever properties your provider needs. Don't forget to package your new provider's jar files in the application if they are needed."
+msgid ""
+"All that is left is updating the <literal>persistence.xml</literal> file "
+"with the correct provider class, and what ever properties your provider "
+"needs. Don't forget to package your new provider's jar files in the "
+"application if they are needed."
msgstr ""
#. Tag: title
@@ -1061,14 +1383,14 @@
#. Tag: para
#: Configuration.xml:552
#, no-c-format
-msgid "If you're running in a Java EE 5 environment, this is all the configuration required to start using Seam!"
+msgid ""
+"If you're running in a Java EE 5 environment, this is all the configuration "
+"required to start using Seam!"
msgstr ""
# come tradurre?
#. Tag: title
-#: Configuration.xml:555
-#: Configuration.xml:650
-#: Configuration.xml:788
+#: Configuration.xml:555 Configuration.xml:650 Configuration.xml:788
#: Configuration.xml:821
#, no-c-format
msgid "Packaging"
@@ -1077,7 +1399,9 @@
#. Tag: para
#: Configuration.xml:557
#, no-c-format
-msgid "Once you've packaged all this stuff together into an EAR, the archive structure will look something like this:"
+msgid ""
+"Once you've packaged all this stuff together into an EAR, the archive "
+"structure will look something like this:"
msgstr ""
#. Tag: programlisting
@@ -1157,43 +1481,65 @@
#. Tag: para
#: Configuration.xml:562
#, no-c-format
-msgid "You should declare <literal>jboss-seam.jar</literal> as an ejb module in <literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> should be placed in the EAR's lib directory (putting it in the EAR classpath."
+msgid ""
+"You should declare <literal>jboss-seam.jar</literal> as an ejb module in "
+"<literal>META-INF/application.xml</literal>; <literal>jboss-el.jar</literal> "
+"should be placed in the EAR's lib directory (putting it in the EAR classpath."
msgstr ""
#. Tag: para
#: Configuration.xml:567
#, no-c-format
-msgid "If you want to use jBPM or Drools, you must include the needed jars in the EAR's lib directory."
+msgid ""
+"If you want to use jBPM or Drools, you must include the needed jars in the "
+"EAR's lib directory."
msgstr ""
#. Tag: para
#: Configuration.xml:569
#, no-c-format
-msgid "If you want to use facelets (our recommendation), you must include <literal>jsf-facelets.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR."
+msgid ""
+"If you want to use facelets (our recommendation), you must include "
+"<literal>jsf-facelets.jar</literal> in the <literal>WEB-INF/lib</literal> "
+"directory of the WAR."
msgstr ""
#. Tag: para
#: Configuration.xml:572
#, no-c-format
-msgid "If you want to use the Seam tag library (most Seam applications do), you must include <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR. If you want to use the PDF or email tag libraries, you need to put <literal>jboss-seam-pdf.jar</literal> or <literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
+msgid ""
+"If you want to use the Seam tag library (most Seam applications do), you "
+"must include <literal>jboss-seam-ui.jar</literal> in the <literal>WEB-INF/"
+"lib</literal> directory of the WAR. If you want to use the PDF or email tag "
+"libraries, you need to put <literal>jboss-seam-pdf.jar</literal> or "
+"<literal>jboss-seam-mail.jar</literal> in <literal>WEB-INF/lib</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:577
#, no-c-format
-msgid "If you want to use the Seam debug page (only works for applications using facelets), you must include <literal>jboss-seam-debug.jar</literal> in the <literal>WEB-INF/lib</literal> directory of the WAR."
+msgid ""
+"If you want to use the Seam debug page (only works for applications using "
+"facelets), you must include <literal>jboss-seam-debug.jar</literal> in the "
+"<literal>WEB-INF/lib</literal> directory of the WAR."
msgstr ""
#. Tag: para
#: Configuration.xml:580
#, no-c-format
-msgid "Seam ships with several example applications that are deployable in any Java EE container that supports EJB 3.0."
+msgid ""
+"Seam ships with several example applications that are deployable in any Java "
+"EE container that supports EJB 3.0."
msgstr ""
#. Tag: para
#: Configuration.xml:583
#, no-c-format
-msgid "I really wish that was all there was to say on the topic of configuration but unfortunately we're only about a third of the way there. If you're too overwhelmed by all this tedious configuration stuff, feel free to skip over the rest of this section and come back to it later."
+msgid ""
+"I really wish that was all there was to say on the topic of configuration "
+"but unfortunately we're only about a third of the way there. If you're too "
+"overwhelmed by all this tedious configuration stuff, feel free to skip over "
+"the rest of this section and come back to it later."
msgstr ""
#. Tag: title
@@ -1205,19 +1551,35 @@
#. Tag: para
#: Configuration.xml:594
#, no-c-format
-msgid "Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. In this case you would use Hibernate3 or JPA instead of EJB 3.0 persistence, and plain JavaBeans instead of session beans. You'll miss out on some of the nice features of session beans but it will be very easy to migrate to EJB 3.0 when you're ready and, in the meantime, you'll be able to take advantage of Seam's unique declarative state management architecture."
+msgid ""
+"Seam is useful even if you're not yet ready to take the plunge into EJB 3.0. "
+"In this case you would use Hibernate3 or JPA instead of EJB 3.0 persistence, "
+"and plain JavaBeans instead of session beans. You'll miss out on some of the "
+"nice features of session beans but it will be very easy to migrate to EJB "
+"3.0 when you're ready and, in the meantime, you'll be able to take advantage "
+"of Seam's unique declarative state management architecture."
msgstr ""
#. Tag: para
#: Configuration.xml:609
#, no-c-format
-msgid "Seam JavaBean components do not provide declarative transaction demarcation like session beans do. You <emphasis>could</emphasis> manage your transactions manually using the JTA <literal>UserTransaction</literal> or declaratively using Seam's <literal>@Transactional</literal> annotation. But most applications will just use Seam managed transactions when using Hibernate with JavaBeans."
+msgid ""
+"Seam JavaBean components do not provide declarative transaction demarcation "
+"like session beans do. You <emphasis>could</emphasis> manage your "
+"transactions manually using the JTA <literal>UserTransaction</literal> or "
+"declaratively using Seam's <literal>@Transactional</literal> annotation. But "
+"most applications will just use Seam managed transactions when using "
+"Hibernate with JavaBeans."
msgstr ""
#. Tag: para
#: Configuration.xml:615
#, no-c-format
-msgid "The Seam distribution includes a version of the booking example application that uses Hibernate3 and JavaBeans instead of EJB3, and another version that uses JPA and JavaBeans. These example applications are ready to deploy into any J2EE application server."
+msgid ""
+"The Seam distribution includes a version of the booking example application "
+"that uses Hibernate3 and JavaBeans instead of EJB3, and another version that "
+"uses JPA and JavaBeans. These example applications are ready to deploy into "
+"any J2EE application server."
msgstr ""
#. Tag: title
@@ -1229,19 +1591,29 @@
#. Tag: para
#: Configuration.xml:622
#, no-c-format
-msgid "Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your <literal>hibernate.cfg.xml</literal> file if you install a built-in component:"
+msgid ""
+"Seam will bootstrap a Hibernate <literal>SessionFactory</literal> from your "
+"<literal>hibernate.cfg.xml</literal> file if you install a built-in "
+"component:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:625
#, no-c-format
-msgid "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
-msgstr "<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>]]>"
+msgid ""
+"<![CDATA[<persistence:hibernate-session-factory name="
+"\"hibernateSessionFactory\"/>]]>"
+msgstr ""
+"<![CDATA[<persistence:hibernate-session-factory name="
+"\"hibernateSessionFactory\"/>]]>"
#. Tag: para
#: Configuration.xml:627
#, no-c-format
-msgid "You will also need to configure a <emphasis>managed session</emphasis> if you want a Seam managed Hibernate <literal>Session</literal> to be available via injection."
+msgid ""
+"You will also need to configure a <emphasis>managed session</emphasis> if "
+"you want a Seam managed Hibernate <literal>Session</literal> to be available "
+"via injection."
msgstr ""
#. Tag: programlisting
@@ -1249,10 +1621,12 @@
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n"
-" session-factory=\"#{hibernateSessionFactory}\"/>]]>"
+" session-factory=\"#{hibernateSessionFactory}\"/"
+">]]>"
msgstr ""
"<![CDATA[<persistence:managed-hibernate-session name=\"hibernateSession\"\n"
-" session-factory=\"#{hibernateSessionFactory}\"/>]]>"
+" session-factory=\"#{hibernateSessionFactory}\"/"
+">]]>"
#. Tag: title
#: Configuration.xml:635
@@ -1263,19 +1637,29 @@
#. Tag: para
#: Configuration.xml:637
#, no-c-format
-msgid "Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your <literal>persistence.xml</literal> file if you install this built-in component:"
+msgid ""
+"Seam will bootstrap a JPA <literal>EntityManagerFactory</literal> from your "
+"<literal>persistence.xml</literal> file if you install this built-in "
+"component:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:640
#, no-c-format
-msgid "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
-msgstr "<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/>]]>"
+msgid ""
+"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/"
+">]]>"
+msgstr ""
+"<![CDATA[<persistence:entity-manager-factory name=\"entityManagerFactory\"/"
+">]]>"
#. Tag: para
#: Configuration.xml:642
#, no-c-format
-msgid "You will also need to configure a <emphasis>managed persistence context</emphasis> if you want a Seam managed JPA <literal>EntityManager</literal> to be available via injection."
+msgid ""
+"You will also need to configure a <emphasis>managed persistence context</"
+"emphasis> if you want a Seam managed JPA <literal>EntityManager</literal> to "
+"be available via injection."
msgstr ""
#. Tag: programlisting
@@ -1283,10 +1667,12 @@
#, no-c-format
msgid ""
"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
-" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
+" entity-manager-factory=\"#{entityManagerFactory}"
+"\"/>]]>"
msgstr ""
"<![CDATA[<persistence:managed-persistence-context name=\"entityManager\"\n"
-" entity-manager-factory=\"#{entityManagerFactory}\"/>]]>"
+" entity-manager-factory=\"#{entityManagerFactory}"
+"\"/>]]>"
#. Tag: para
#: Configuration.xml:652
@@ -1365,7 +1751,9 @@
#. Tag: para
#: Configuration.xml:656
#, no-c-format
-msgid "If we want to deploy Hibernate in a non-EE environment like Tomcat or TestNG, we need to do a little bit more work."
+msgid ""
+"If we want to deploy Hibernate in a non-EE environment like Tomcat or "
+"TestNG, we need to do a little bit more work."
msgstr ""
#. Tag: title
@@ -1377,26 +1765,37 @@
#. Tag: para
#: Configuration.xml:665
#, no-c-format
-msgid "It is possible to use Seam completely outside of an EE environment. In this case, you need to tell Seam how to manage transactions, since there will be no JTA available. If you're using JPA, you can tell Seam to use JPA resource-local transactions, ie. <literal>EntityTransaction</literal>, like so:"
+msgid ""
+"It is possible to use Seam completely outside of an EE environment. In this "
+"case, you need to tell Seam how to manage transactions, since there will be "
+"no JTA available. If you're using JPA, you can tell Seam to use JPA resource-"
+"local transactions, ie. <literal>EntityTransaction</literal>, like so:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:669
#, no-c-format
-msgid "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
-msgstr "<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/>]]>"
+msgid ""
+"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/"
+">]]>"
+msgstr ""
+"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/"
+">]]>"
#. Tag: para
#: Configuration.xml:671
#, no-c-format
-msgid "If you're using Hibernate, you can tell Seam to use the Hibernate transaction API like this:"
+msgid ""
+"If you're using Hibernate, you can tell Seam to use the Hibernate "
+"transaction API like this:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:673
#, no-c-format
msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
-msgstr "<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
+msgstr ""
+"<![CDATA[<transaction:hibernate-transaction session=\"#{session}\"/>]]>"
#. Tag: para
#: Configuration.xml:675
@@ -1407,7 +1806,8 @@
#. Tag: para
#: Configuration.xml:677
#, no-c-format
-msgid "A better alternative is to use JBoss Embedded to get access to the EE APIs."
+msgid ""
+"A better alternative is to use JBoss Embedded to get access to the EE APIs."
msgstr ""
#. Tag: title
@@ -1419,13 +1819,18 @@
#. Tag: para
#: Configuration.xml:684
#, no-c-format
-msgid "JBoss Embedded lets you run EJB3 components outside the context of the Java EE 5 application server. This is especially, but not only, useful for testing."
+msgid ""
+"JBoss Embedded lets you run EJB3 components outside the context of the Java "
+"EE 5 application server. This is especially, but not only, useful for "
+"testing."
msgstr ""
#. Tag: para
#: Configuration.xml:687
#, no-c-format
-msgid "The Seam booking example application includes a TestNG integration test suite that runs on JBoss Embedded via <literal>SeamTest</literal>."
+msgid ""
+"The Seam booking example application includes a TestNG integration test "
+"suite that runs on JBoss Embedded via <literal>SeamTest</literal>."
msgstr ""
#. Tag: para
@@ -1443,31 +1848,49 @@
#. Tag: para
#: Configuration.xml:714
#, no-c-format
-msgid "Embedded JBoss must by installed into Tomcat for Seam applications to run correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend=\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=228977\">here</ulink>. The process for installing Embedded JBoss into Tomcat 6 is quite simple. First, you should copy the Embedded JBoss JARs and configuration files into Tomcat."
+msgid ""
+"Embedded JBoss must by installed into Tomcat for Seam applications to run "
+"correctly on it. Embedded JBoss runs with JDK 5 or JDK 6 ( see <xref linkend="
+"\"jdk_dependencies\"/> for details on using JDK 6). Embedded JBoss can be "
+"downloaded <ulink url=\"http://sourceforge.net/project/showfiles.php?"
+"group_id=22866&package_id=228977\">here</ulink>. The process for "
+"installing Embedded JBoss into Tomcat 6 is quite simple. First, you should "
+"copy the Embedded JBoss JARs and configuration files into Tomcat."
msgstr ""
#. Tag: para
#: Configuration.xml:728
#, no-c-format
-msgid "Copy all files and directories under the Embedded JBoss <literal>bootstrap</literal> and <literal>lib</literal> directories, except for the <literal>jndi.properties</literal> file, into the Tomcat <literal>lib</literal> directory."
+msgid ""
+"Copy all files and directories under the Embedded JBoss <literal>bootstrap</"
+"literal> and <literal>lib</literal> directories, except for the "
+"<literal>jndi.properties</literal> file, into the Tomcat <literal>lib</"
+"literal> directory."
msgstr ""
#. Tag: para
#: Configuration.xml:735
#, no-c-format
-msgid "Remove the <literal>annotations-api.jar</literal> file from the Tomcat <literal>lib</literal> directory."
+msgid ""
+"Remove the <literal>annotations-api.jar</literal> file from the Tomcat "
+"<literal>lib</literal> directory."
msgstr ""
#. Tag: para
#: Configuration.xml:741
#, no-c-format
-msgid "Next, two configuration files need to be updated to add Embedded JBoss-specific functionality."
+msgid ""
+"Next, two configuration files need to be updated to add Embedded JBoss-"
+"specific functionality."
msgstr ""
#. Tag: para
#: Configuration.xml:747
#, no-c-format
-msgid "Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</literal> to <literal>conf/server.xml</literal>. It must appear after all other listeners in the file:"
+msgid ""
+"Add the Embedded JBoss listener <literal>EmbeddedJBossBootstrapListener</"
+"literal> to <literal>conf/server.xml</literal>. It must appear after all "
+"other listeners in the file:"
msgstr ""
#. Tag: programlisting
@@ -1476,36 +1899,48 @@
msgid ""
"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
"\n"
-" <!-- Comment these entries out to disable JMX MBeans support used for the \n"
+" <!-- Comment these entries out to disable JMX MBeans support used for "
+"the \n"
" administration web application -->\n"
" <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>"
+" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener"
+"\" />\n"
+" <Listener className=\"org.apache.catalina.mbeans."
+"GlobalResourcesLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.storeconfig."
+"StoreConfigLifecycleListener\" />]]>"
msgstr ""
"<![CDATA[<Server port=\"8005\" shutdown=\"SHUTDOWN\">\n"
"\n"
-" <!-- Comment these entries out to disable JMX MBeans support used for the \n"
+" <!-- Comment these entries out to disable JMX MBeans support used for "
+"the \n"
" administration web application -->\n"
" <Listener className=\"org.apache.catalina.core.AprLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.mbeans.GlobalResourcesLifecycleListener\" />\n"
-" <Listener className=\"org.apache.catalina.storeconfig.StoreConfigLifecycleListener\" />]]>"
+" <Listener className=\"org.apache.catalina.mbeans.ServerLifecycleListener"
+"\" />\n"
+" <Listener className=\"org.apache.catalina.mbeans."
+"GlobalResourcesLifecycleListener\" />\n"
+" <Listener className=\"org.apache.catalina.storeconfig."
+"StoreConfigLifecycleListener\" />]]>"
#. Tag: programlisting
#: Configuration.xml:751
#, no-c-format
msgid ""
"<![CDATA[ <!-- Add this listener -->\n"
-" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>"
+" <Listener className=\"org.jboss.embedded.tomcat."
+"EmbeddedJBossBootstrapListener\" />]]>"
msgstr ""
"<![CDATA[ <!-- Add this listener -->\n"
-" <Listener className=\"org.jboss.embedded.tomcat.EmbeddedJBossBootstrapListener\" />]]>"
+" <Listener className=\"org.jboss.embedded.tomcat."
+"EmbeddedJBossBootstrapListener\" />]]>"
#. Tag: para
#: Configuration.xml:755
#, no-c-format
-msgid "WAR file scanning should be enabled by adding the <literal>WebinfScanner</literal> listener to <literal>conf/context.xml</literal>:"
+msgid ""
+"WAR file scanning should be enabled by adding the <literal>WebinfScanner</"
+"literal> listener to <literal>conf/context.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1516,7 +1951,8 @@
" <!-- Default set of monitored resources -->\n"
" <WatchedResource>WEB-INF/web.xml</WatchedResource>\n"
" \n"
-" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n"
+" <!-- Uncomment this to disable session persistence across Tomcat "
+"restarts -->\n"
" <!--\n"
" <Manager pathname=\"\" />\n"
" -->]]>"
@@ -1525,7 +1961,8 @@
" <!-- Default set of monitored resources -->\n"
" <WatchedResource>WEB-INF/web.xml</WatchedResource>\n"
" \n"
-" <!-- Uncomment this to disable session persistence across Tomcat restarts -->\n"
+" <!-- Uncomment this to disable session persistence across Tomcat "
+"restarts -->\n"
" <!--\n"
" <Manager pathname=\"\" />\n"
" -->]]>"
@@ -1549,20 +1986,32 @@
#. Tag: para
#: Configuration.xml:764
#, no-c-format
-msgid "If you are using Sun JDK 6, you need to set the Java option <literal>sun.lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in the JAVA_OPTS environment variable used by the Catalina startup script (catalina.bat on Windows or catalina.sh on Unix)."
+msgid ""
+"If you are using Sun JDK 6, you need to set the Java option <literal>sun."
+"lang.ClassLoader.allowArraySyntax</literal> to <literal>true</literal> in "
+"the JAVA_OPTS environment variable used by the Catalina startup script "
+"(catalina.bat on Windows or catalina.sh on Unix)."
msgstr ""
#. Tag: para
#: Configuration.xml:769
#, no-c-format
-msgid "Open the script appropriate for your operating system in a text editor. Add a new line immediately below the comments at the top of the file where you will define the JAVA_OPTS environment variable. On Windows, use the following syntax:"
+msgid ""
+"Open the script appropriate for your operating system in a text editor. Add "
+"a new line immediately below the comments at the top of the file where you "
+"will define the JAVA_OPTS environment variable. On Windows, use the "
+"following syntax:"
msgstr ""
#. Tag: programlisting
#: Configuration.xml:773
#, no-c-format
-msgid "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>"
-msgstr "<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader.allowArraySyntax=true]]>"
+msgid ""
+"<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader."
+"allowArraySyntax=true]]>"
+msgstr ""
+"<![CDATA[set JAVA_OPTS=%JAVA_OPTS% -Dsun.lang.ClassLoader."
+"allowArraySyntax=true]]>"
#. Tag: para
#: Configuration.xml:775
@@ -1573,19 +2022,28 @@
#. Tag: programlisting
#: Configuration.xml:777
#, no-c-format
-msgid "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>"
-msgstr "<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true\"]]>"
+msgid ""
+"<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true"
+"\"]]>"
+msgstr ""
+"<![CDATA[JAVA_OPTS=\"$JAVA_OPTS -Dsun.lang.ClassLoader.allowArraySyntax=true"
+"\"]]>"
#. Tag: para
#: Configuration.xml:782
#, no-c-format
-msgid "For more configuration options, please see the Embedded JBoss Tomcat integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddedAndTomcat\">wiki entry</ulink>."
+msgid ""
+"For more configuration options, please see the Embedded JBoss Tomcat "
+"integration <ulink url=\"http://wiki.jboss.org/wiki/Wiki.jsp?"
+"page=EmbeddedAndTomcat\">wiki entry</ulink>."
msgstr ""
#. Tag: para
#: Configuration.xml:790
#, no-c-format
-msgid "The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something like this:"
+msgid ""
+"The archive structure of a WAR-based deployment on an servlet engine like "
+"Tomcat will look something like this:"
msgstr ""
#. Tag: programlisting
@@ -1661,7 +2119,9 @@
#. Tag: para
#: Configuration.xml:795
#, no-c-format
-msgid "Most of the Seam example applications may be deployed to Tomcat by running <literal>ant deploy.tomcat</literal>."
+msgid ""
+"Most of the Seam example applications may be deployed to Tomcat by running "
+"<literal>ant deploy.tomcat</literal>."
msgstr ""
#. Tag: title
@@ -1673,7 +2133,11 @@
#. Tag: para
#: Configuration.xml:804
#, no-c-format
-msgid "Seam's jBPM integration is not installed by default, so you'll need to enable jBPM by installing a built-in component. You'll also need to explicitly list your process and pageflow definitions. In <literal>components.xml</literal>:"
+msgid ""
+"Seam's jBPM integration is not installed by default, so you'll need to "
+"enable jBPM by installing a built-in component. You'll also need to "
+"explicitly list your process and pageflow definitions. In "
+"<literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1705,7 +2169,12 @@
#. Tag: para
#: Configuration.xml:810
#, no-c-format
-msgid "No further special configuration is needed if you only have pageflows. If you do have business process definitions, you need to provide a jBPM configuration, and a Hibernate configuration for jBPM. The Seam DVD Store demo includes example <literal>jbpm.cfg.xml</literal> and <literal>hibernate.cfg.xml</literal> files that will work with Seam:"
+msgid ""
+"No further special configuration is needed if you only have pageflows. If "
+"you do have business process definitions, you need to provide a jBPM "
+"configuration, and a Hibernate configuration for jBPM. The Seam DVD Store "
+"demo includes example <literal>jbpm.cfg.xml</literal> and <literal>hibernate."
+"cfg.xml</literal> files that will work with Seam:"
msgstr ""
#. Tag: programlisting
@@ -1717,17 +2186,22 @@
" <jbpm-context>\n"
" <service name=\"persistence\">\n"
" <factory>\n"
-" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory\">\n"
+" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory"
+"\">\n"
" <field name=\"isTransactionEnabled\"><false/></field>\n"
" </bean>\n"
" </factory>\n"
" </service>\n"
" <service name=\"tx\" factory=\"org.jbpm.tx.TxServiceFactory\" />\n"
-" <service name=\"message\" factory=\"org.jbpm.msg.db.DbMessageServiceFactory\" />\n"
-" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db.DbSchedulerServiceFactory\" />\n"
-" <service name=\"logging\" factory=\"org.jbpm.logging.db.DbLoggingServiceFactory\" />\n"
+" <service name=\"message\" factory=\"org.jbpm.msg.db."
+"DbMessageServiceFactory\" />\n"
+" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db."
+"DbSchedulerServiceFactory\" />\n"
+" <service name=\"logging\" factory=\"org.jbpm.logging.db."
+"DbLoggingServiceFactory\" />\n"
" <service name=\"authentication\" \n"
-" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n"
+" factory=\"org.jbpm.security.authentication."
+"DefaultAuthenticationServiceFactory\" />\n"
" </jbpm-context>\n"
"\n"
"</jbpm-configuration>]]>"
@@ -1737,17 +2211,22 @@
" <jbpm-context>\n"
" <service name=\"persistence\">\n"
" <factory>\n"
-" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory\">\n"
+" <bean class=\"org.jbpm.persistence.db.DbPersistenceServiceFactory"
+"\">\n"
" <field name=\"isTransactionEnabled\"><false/></field>\n"
" </bean>\n"
" </factory>\n"
" </service>\n"
" <service name=\"tx\" factory=\"org.jbpm.tx.TxServiceFactory\" />\n"
-" <service name=\"message\" factory=\"org.jbpm.msg.db.DbMessageServiceFactory\" />\n"
-" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db.DbSchedulerServiceFactory\" />\n"
-" <service name=\"logging\" factory=\"org.jbpm.logging.db.DbLoggingServiceFactory\" />\n"
+" <service name=\"message\" factory=\"org.jbpm.msg.db."
+"DbMessageServiceFactory\" />\n"
+" <service name=\"scheduler\" factory=\"org.jbpm.scheduler.db."
+"DbSchedulerServiceFactory\" />\n"
+" <service name=\"logging\" factory=\"org.jbpm.logging.db."
+"DbLoggingServiceFactory\" />\n"
" <service name=\"authentication\" \n"
-" factory=\"org.jbpm.security.authentication.DefaultAuthenticationServiceFactory\" />\n"
+" factory=\"org.jbpm.security.authentication."
+"DefaultAuthenticationServiceFactory\" />\n"
" </jbpm-context>\n"
"\n"
"</jbpm-configuration>]]>"
@@ -1755,13 +2234,20 @@
#. Tag: para
#: Configuration.xml:817
#, no-c-format
-msgid "The most important thing to notice here is that jBPM transaction control is disabled. Seam or EJB3 should control the JTA transactions."
+msgid ""
+"The most important thing to notice here is that jBPM transaction control is "
+"disabled. Seam or EJB3 should control the JTA transactions."
msgstr ""
#. Tag: para
#: Configuration.xml:823
#, no-c-format
-msgid "There is not yet any well-defined packaging format for jBPM configuration and process/pageflow definition files. In the Seam examples we've decided to simply package all these files into the root of the EAR. In future, we will probably design some other standard packaging format. So the EAR looks something like this:"
+msgid ""
+"There is not yet any well-defined packaging format for jBPM configuration "
+"and process/pageflow definition files. In the Seam examples we've decided to "
+"simply package all these files into the root of the EAR. In future, we will "
+"probably design some other standard packaging format. So the EAR looks "
+"something like this:"
msgstr ""
#. Tag: programlisting
@@ -1861,13 +2347,22 @@
#. Tag: para
#: Configuration.xml:837
#, no-c-format
-msgid "It is very important that the timeout for Stateful Session Beans is set higher than the timeout for HTTP Sessions, otherwise SFSB's may time out before the user's HTTP session has ended. JBoss Application Server has a default session bean timeout of 30 minutes, which is configured in <literal>server/default/conf/standardjboss.xml</literal> (replace <emphasis>default</emphasis> with your own configuration)."
+msgid ""
+"It is very important that the timeout for Stateful Session Beans is set "
+"higher than the timeout for HTTP Sessions, otherwise SFSB's may time out "
+"before the user's HTTP session has ended. JBoss Application Server has a "
+"default session bean timeout of 30 minutes, which is configured in "
+"<literal>server/default/conf/standardjboss.xml</literal> (replace "
+"<emphasis>default</emphasis> with your own configuration)."
msgstr ""
#. Tag: para
#: Configuration.xml:843
#, no-c-format
-msgid "The default SFSB timeout can be adjusted by modifying the value of <literal>max-bean-life</literal> in the <literal>LRUStatefulContextCachePolicy</literal> cache configuration:"
+msgid ""
+"The default SFSB timeout can be adjusted by modifying the value of "
+"<literal>max-bean-life</literal> in the "
+"<literal>LRUStatefulContextCachePolicy</literal> cache configuration:"
msgstr ""
#. Tag: programlisting
@@ -1875,7 +2370,8 @@
#, no-c-format
msgid ""
"<![CDATA[<container-cache-conf>\n"
-" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>\n"
+" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-"
+"policy>\n"
" <cache-policy-conf>\n"
" <min-capacity>50</min-capacity>\n"
" <max-capacity>1000000</max-capacity>\n"
@@ -1894,7 +2390,8 @@
"</container-cache-conf>]]>"
msgstr ""
"<![CDATA[<container-cache-conf>\n"
-" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-policy>\n"
+" <cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-"
+"policy>\n"
" <cache-policy-conf>\n"
" <min-capacity>50</min-capacity>\n"
" <max-capacity>1000000</max-capacity>\n"
@@ -1915,7 +2412,12 @@
#. Tag: para
#: Configuration.xml:848
#, no-c-format
-msgid "The default HTTP session timeout can be modified in <literal>server/default/deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in <literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for JBoss 4.2.x. The following entry in this file controls the default session timeout for all web applications:"
+msgid ""
+"The default HTTP session timeout can be modified in <literal>server/default/"
+"deploy/jbossweb-tomcat55.sar/conf/web.xml</literal> for JBoss 4.0.x, or in "
+"<literal>server/default/deploy/jboss-web.deployer/conf/web.xml</literal> for "
+"JBoss 4.2.x. The following entry in this file controls the default session "
+"timeout for all web applications:"
msgstr ""
#. Tag: programlisting
@@ -1935,7 +2437,9 @@
#. Tag: para
#: Configuration.xml:855
#, no-c-format
-msgid "To override this value for your own application, simply include this entry in your application's own <literal>web.xml</literal>."
+msgid ""
+"To override this value for your own application, simply include this entry "
+"in your application's own <literal>web.xml</literal>."
msgstr ""
#. Tag: title
@@ -1947,7 +2451,12 @@
#. Tag: para
#: Configuration.xml:863
#, no-c-format
-msgid "If you want to run your Seam application in a portlet, take a look at the JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> for more."
+msgid ""
+"If you want to run your Seam application in a portlet, take a look at the "
+"JBoss Portlet Bridge, an implementation of JSR-301 that supports JSF within "
+"a portlet, with extensions for Seam and RichFaces. See <ulink url=\"http://"
+"labs.jboss.com/portletbridge\">http://labs.jboss.com/portletbridge</ulink> "
+"for more."
msgstr ""
#. Tag: title
@@ -1959,13 +2468,22 @@
#. Tag: para
#: Configuration.xml:876
#, no-c-format
-msgid "Seam scans all jars containing <literal>/seam.properties</literal>, <literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam.properties</literal> on startup for resources. For example, all classes annotated with <literal>@Name</literal> are registered with Seam as Seam components."
+msgid ""
+"Seam scans all jars containing <literal>/seam.properties</literal>, "
+"<literal>/META-INF/components.xml</literal> or <literal>/META-INF/seam."
+"properties</literal> on startup for resources. For example, all classes "
+"annotated with <literal>@Name</literal> are registered with Seam as Seam "
+"components."
msgstr ""
#. Tag: para
#: Configuration.xml:883
#, no-c-format
-msgid "You may also want Seam to handle custom resources. A common use case is to handle a specific annotation and Seam provides specific support for this. First, tell Seam which annotations to handle in <literal>/META-INF/seam-deployment.properties</literal>:"
+msgid ""
+"You may also want Seam to handle custom resources. A common use case is to "
+"handle a specific annotation and Seam provides specific support for this. "
+"First, tell Seam which annotations to handle in <literal>/META-INF/seam-"
+"deployment.properties</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1981,7 +2499,9 @@
#. Tag: para
#: Configuration.xml:892
#, no-c-format
-msgid "Then, during application startup you can get hold of all classes annotated with <literal>@Foo</literal>:"
+msgid ""
+"Then, during application startup you can get hold of all classes annotated "
+"with <literal>@Foo</literal>:"
msgstr ""
#. Tag: programlisting
@@ -2037,7 +2557,10 @@
#. Tag: para
#: Configuration.xml:899
#, no-c-format
-msgid "You can also handle <emphasis>any</emphasis> resource. For example, you process any files with the extension <literal>.foo.xml</literal>. To do this, we need to write a custom deployment handler:"
+msgid ""
+"You can also handle <emphasis>any</emphasis> resource. For example, you "
+"process any files with the extension <literal>.foo.xml</literal>. To do "
+"this, we need to write a custom deployment handler:"
msgstr ""
#. Tag: programlisting
@@ -2085,13 +2608,17 @@
#. Tag: para
#: Configuration.xml:907
#, no-c-format
-msgid "Here we are just building a list of any files with the suffix <literal>.foo.xml</literal>."
+msgid ""
+"Here we are just building a list of any files with the suffix <literal>.foo."
+"xml</literal>."
msgstr ""
#. Tag: para
#: Configuration.xml:912
#, no-c-format
-msgid "Then, we need to register the deployment handler with Seam. In <literal>/META-INF/seam-deployment.properties</literal>:"
+msgid ""
+"Then, we need to register the deployment handler with Seam. In <literal>/"
+"META-INF/seam-deployment.properties</literal>:"
msgstr ""
#. Tag: programlisting
@@ -2101,23 +2628,31 @@
"<![CDATA[# For standard deployment\n"
"org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n"
"# For hot deployment\n"
-"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
+"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme."
+"FooDeploymentHandler]]>"
msgstr ""
"<![CDATA[# For standard deployment\n"
"org.jboss.seam.deployment.deploymentHandlers=com.acme.FooDeploymentHandler\n"
"# For hot deployment\n"
-"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme.FooDeploymentHandler]]>"
+"org.jboss.seam.deployment.hotDeploymentHandlers=com.acme."
+"FooDeploymentHandler]]>"
#. Tag: para
#: Configuration.xml:919
#, no-c-format
-msgid "You can register multiple deployment handler using a comma separated list."
+msgid ""
+"You can register multiple deployment handler using a comma separated list."
msgstr ""
#. Tag: para
#: Configuration.xml:924
#, no-c-format
-msgid "Seam uses deployment handlers internally to install components and namespaces, therefore the <literal>handle()</literal> is called too early in inside Seam bootstrap to normally be useful. However, you can easily access the deployment handler during an <literal>APPLICATION</literal> scoped component's startup:"
+msgid ""
+"Seam uses deployment handlers internally to install components and "
+"namespaces, therefore the <literal>handle()</literal> is called too early in "
+"inside Seam bootstrap to normally be useful. However, you can easily access "
+"the deployment handler during an <literal>APPLICATION</literal> scoped "
+"component's startup:"
msgstr ""
#. Tag: programlisting
@@ -2169,4 +2704,3 @@
" }\n"
"\n"
"}]]>"
-
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Conversations.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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: 2009-01-17 21:02+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:13+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -108,8 +108,8 @@
#. Tag: para
#: Conversations.xml:111
#, no-c-format
-msgid "If the JSF request lifecycle is foreshortened by a redirect, Seam transparently stores and restores the current conversation context—unless the conversation was already ended via <literal>@End(beforeRedirect=true)</literal>."
-msgstr "Se il ciclo di vita della richiesta JSF viene accorciato da un redirect, Seam memorizza e ripristina in modo trasparente il contesto dell'attuale conversazione—amenoché la conversazione sia già stata terminata tramite <literal>@End(beforeRedirect=true)</literal>."
+msgid "If the JSF request lifecycle is foreshortened by a redirect, Seam transparently stores and restores the current conversation context — unless the conversation was already ended via <literal>@End(beforeRedirect=true)</literal>."
+msgstr "Se il ciclo di vita della richiesta JSF viene accorciato da un redirect, Seam memorizza e ripristina in modo trasparente il contesto dell'attuale conversazione — amenoché la conversazione sia già stata terminata tramite <literal>@End(beforeRedirect=true)</literal>."
#. Tag: para
#: Conversations.xml:120
@@ -525,8 +525,8 @@
#. Tag: para
#: Conversations.xml:428
#, no-c-format
-msgid "Seam provides the notion of a <emphasis>page action</emphasis> to help solve the first problem, but this does nothing to help us with the second problem. We <emphasis>could</emphasis> work around this by using the RESTful approach of passing a request parameter and requerying for the selected object on the server side. In some cases—such as the Seam blog example application—this is indeed the best approach. The RESTful style supports bookmarking, since it does not require server-side state. In other cases, where we don't care about bookmarks, the use of <literal>@DataModel</literal> and <literal>@DataModelSelection</literal> is just so convenient and transparent!"
-msgstr "Seam fornisce la nozione di <emphasis>pagina d'azione</emphasis> per aiutare a risolvere il primo problema, ma questo non aiuta per niente il secondo problema. Si <emphasis>può</emphasis> aggirare questo usando l'approccio RESTful di passare un parametro di richiesta e di riottenere l'oggetto selezionato lato server. In alcuni casi—come nell'esempio Seam del Blog—questo è il migliore approccio. Lo stile RESTful supporta i segnalibri, poiché non richiede uno stato lato server. In altri casi, dove non interessanno i segnalibri, l'uso di un <literal>@DataModel</literal> e di <literal>@DataModelSelection</literal> è conveniente e trasparente!"
+msgid "Seam provides the notion of a <emphasis>page action</emphasis> to help solve the first problem, but this does nothing to help us with the second problem. We <emphasis>could</emphasis> work around this by using the RESTful approach of passing a request parameter and requerying for the selected object on the server side. In some cases — such as the Seam blog example application — this is indeed the best approach. The RESTful style supports bookmarking, since it does not require server-side state. In other cases, where we don't care about bookmarks, the use of <literal>@DataModel</literal> and <literal>@DataModelSelection</literal> is just so convenient and transparent!"
+msgstr "Seam fornisce la nozione di <emphasis>pagina d'azione</emphasis> per aiutare a risolvere il primo problema, ma questo non aiuta per niente il secondo problema. Si <emphasis>può</emphasis> aggirare questo usando l'approccio RESTful di passare un parametro di richiesta e di riottenere l'oggetto selezionato lato server. In alcuni casi — come nell'esempio Seam del Blog — questo è il migliore approccio. Lo stile RESTful supporta i segnalibri, poiché non richiede uno stato lato server. In altri casi, dove non interessanno i segnalibri, l'uso di un <literal>@DataModel</literal> e di <literal>@DataModelSelection</literal> è conveniente e trasparente!"
#. Tag: para
#: Conversations.xml:441
@@ -757,7 +757,7 @@
#. Tag: para
#: Conversations.xml:576
#, no-c-format
-msgid "With a natural conversation its really easy to have the user rejoin the existing conversation, and pick up where they left off - just have them to rejoin the payForItem conversation with the itemId as the conversation id."
+msgid "With a natural conversation it's really easy to have the user rejoin the existing conversation, and pick up where they left off - just have them to rejoin the payForItem conversation with the itemId as the conversation id."
msgstr "Con una conversazione naturale è molto facile riunire l'utente alla conversazione esistente, e riprendere dove aveva lasciato - riunirsi alla conversazione pagaOggetto con l'idOggetto come id di conversazione."
#. Tag: emphasis
@@ -775,7 +775,7 @@
#. Tag: para
#: Conversations.xml:595
#, no-c-format
-msgid "With a natural conversations, when you are building your hotel booking system (or, of course, whatever your app is) you can generate a URL like <literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> (of course, whatever parameter <literal>hotel</literal> maps to on your domain model must be unique) and with URLRewrite easily transform this to http://seam-hotels/book/BestWesternAntwerpen."
+msgid "With a natural conversation, when you are building your hotel booking system (or, of course, whatever your app is) you can generate a URL like <literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> (of course, whatever parameter <literal>hotel</literal> maps to on your domain model must be unique) and with URLRewrite easily transform this to http://seam-hotels/book/BestWesternAntwerpen."
msgstr "Con una conversazione naturale, quando si costruisce un sistema di prenotazione hotel (od una qualsiasi applicazione) si può generare un URL del tipo <literal>http://seam-hotels/book.seam?hotel=BestWesternAntwerpen</literal> (sicuramente un qualsiasi parametro <literal>hotel</literal>, che mappi sul modello di dominio, deve essere univoco) e con URLRewrite si può facilmente trasformare questo in http://seam-hotels/book/BestWesternAntwerpen."
#. Tag: para
@@ -908,7 +908,7 @@
#: Conversations.xml:674
#, no-c-format
msgid "When named conversations are specified in the <literal><page/></literal> element, redirection to the named conversation occurs as part of navigation rules, after the action method has already been invoked. This is a problem when redirecting to an existing conversation, as redirection needs to be occur before the action method is invoked. Therefore it is necessary to specify the conversation name when the action is invoked. One way of doing this is by using the <literal>s:conversationName</literal> tag:"
-msgstr ""
+msgstr "Quando le conversazioni con nome vengono specificate nell'elemento <literal><page/></literal>, la redirezione alla conversazione con nome avviene come parte delle regole, dopo che il metodo d'azione è già stato invocato. Questo è un problema quando ci si redirige ad una conversazione esistente, poiché la redirezione deve avvenire prima che sia invocato il metodo d'azione. Quindi è necessario specificare il nome della conversazione quando si invoca l'azione. Un metodo per fare questo è usare il tag <literal>s:conversationName</literal>:"
#. Tag: programlisting
#: Conversations.xml:684
@@ -926,7 +926,7 @@
#: Conversations.xml:686
#, no-c-format
msgid "Another alternative is to specify the <literal>conversationName</literal> attribute when using either <literal>s:link</literal> or <literal>s:button</literal>:"
-msgstr ""
+msgstr "Un'altra alternativa è specificare l'attributo <literal>conversationName</literal> quando si usano o <literal>s:link</literal> o <literal>s:button</literal>:"
#. Tag: programlisting
#: Conversations.xml:691
@@ -944,31 +944,31 @@
#: Conversations.xml:699
#, no-c-format
msgid "Workspace management is the ability to \"switch\" conversations in a single window. Seam makes workspace management completely transparent at the level of the Java code. To enable workspace management, all you need to do is:"
-msgstr ""
+msgstr "La gestione del workspace è la capacità di \"cambiare\" le conversazioni all'interno di una singola finestra. Seam rende la gestione del workspace completamente trasparente a livello di codice Java. Per abilitare la gestione del workspace, occorre fare questo:"
#. Tag: para
#: Conversations.xml:708
#, no-c-format
msgid "Provide <emphasis>description</emphasis> text for each view id (when using JSF or Seam navigation rules) or page node (when using jPDL pageflows). This description text is displayed to the user by the workspace switchers."
-msgstr ""
+msgstr "Fornire un testo di <emphasis>descrizione</emphasis> ad ogni id di vista (quando si usa JSF o le regole di navigazione JSF) od il nodo della pagina (quando si usano i pageflow jPDL). Questo testo di descrizione viene mostrato all'utente attraverso lo switcher di workspace."
#. Tag: para
#: Conversations.xml:716
#, no-c-format
msgid "Include one or more of the standard workspace switcher JSP or facelets fragments in your pages. The standard fragments support workspace management via a drop down menu, a list of conversations, or breadcrumbs."
-msgstr ""
+msgstr "Includere uno o più switcher JSP standard di workspace oppure frammenti facelets nelle proprie pagine. I frammenti standard supportano la gestione del workspace attraverso un menu dropdown, una lista di conversazioni, oppure breadcrumb."
#. Tag: title
#: Conversations.xml:726
#, no-c-format
msgid "Workspace management and JSF navigation"
-msgstr ""
+msgstr "Gestione del workspace e navigazione JSF"
#. Tag: para
#: Conversations.xml:727
#, no-c-format
msgid "When you use JSF or Seam navigation rules, Seam switches to a conversation by restoring the current <literal>view-id</literal> for that conversation. The descriptive text for the workspace is defined in a file called <literal>pages.xml</literal> that Seam expects to find in the <literal>WEB-INF</literal> directory, right next to <literal>faces-config.xml</literal>:"
-msgstr ""
+msgstr "Quando si usano JSF o le regole di navigazione di Seam, Seam cambia la conversazione ripristinando l'attuale <literal>view-id</literal> per quella conversazione. Il testo descrittivo per il workspace viene definito in un file chiamato <literal>pages.xml</literal> che Seam si aspetta di trovare nella directory <literal>WEB-INF</literal>, giusto dove si trova <literal>faces-config.xml</literal>:"
#. Tag: programlisting
#: Conversations.xml:736
@@ -1008,19 +1008,19 @@
#: Conversations.xml:738
#, no-c-format
msgid "Note that if this file is missing, the Seam application will continue to work perfectly! The only missing functionality will be the ability to switch workspaces."
-msgstr ""
+msgstr "Si noti che se questo file manca, l'applicazione Seam continuerà a funzionare perfettamente! La sola cosa che mancherà sarà la possibilità di cambiare workspace."
#. Tag: title
#: Conversations.xml:747
#, no-c-format
msgid "Workspace management and jPDL pageflow"
-msgstr ""
+msgstr "Gestione del workspace e pageflow jPDL"
#. Tag: para
#: Conversations.xml:748
#, no-c-format
msgid "When you use a jPDL pageflow definition, Seam switches to a conversation by restoring the current jBPM process state. This is a more flexible model since it allows the same <literal>view-id</literal> to have different descriptions depending upon the current <literal><page></literal> node. The description text is defined by the <literal><page></literal> node:"
-msgstr ""
+msgstr "Quando si usa una definizione di pageflow jPDL, Seam cambia la conversazione ripristinando il corrente stato del processo jBPM. Questo è un modello più flessibile poiché consente allo stesso <literal>view-id</literal> di avere descrizioni differenti a seconda del nodo corrente <literal><page></literal>. Il testo di descrizione è definito dal nodo <literal><page></literal>:"
#. Tag: programlisting
#: Conversations.xml:759
@@ -1084,7 +1084,7 @@
#: Conversations.xml:766
#, no-c-format
msgid "Include the following fragment in your JSP or facelets page to get a drop-down menu that lets you switch to any current conversation, or to any other page of the application:"
-msgstr ""
+msgstr "Includere il seguente frammento nella pagina JSP o facelets per ottenere un menu dropdown che consenta di cambiare la conversazione, o la pagina dell'applicazione:"
#. Tag: programlisting
#: Conversations.xml:772
@@ -1108,13 +1108,13 @@
#: Conversations.xml:774
#, no-c-format
msgid "In this example, we have a menu that includes an item for each conversation, together with two additional items that let the user begin a new conversation."
-msgstr ""
+msgstr "In quest'esempio si ha un menu che include un item per ogni conversazione, assieme a due item aggiuntivi che consentono all'utente di iniziare una nuova conversazione."
#. Tag: para
#: Conversations.xml:780
#, no-c-format
msgid "Only conversations with a description (specified in <literal>pages.xml</literal>) will be included in the drop-down menu."
-msgstr ""
+msgstr "Solo le conversazioni con una descrizione (specificata in <literal>pages.xml</literal>) verranno incluse nel menu dropdown."
#. Tag: title
#: Conversations.xml:798
@@ -1190,13 +1190,13 @@
#: Conversations.xml:820
#, no-c-format
msgid "Only conversations with a description will be included in the list."
-msgstr ""
+msgstr "Solo le conversazioni con una descrizione verranno incluse nella lista."
#. Tag: para
#: Conversations.xml:825
#, no-c-format
msgid "Notice that the conversation list lets the user destroy workspaces."
-msgstr ""
+msgstr "Si noti che la lista delle conversazioni consente all'utente di distruggere i workspace."
#. Tag: title
#: Conversations.xml:832
@@ -1228,19 +1228,19 @@
#: Conversations.xml:855
#, no-c-format
msgid "Conversational components and JSF component bindings"
-msgstr ""
+msgstr "Componenti conversazionali ed associazione ai componenti JSF"
#. Tag: para
#: Conversations.xml:857
#, no-c-format
msgid "Conversational components have one minor limitation: they cannot be used to hold bindings to JSF components. (We generally prefer not to use this feature of JSF unless absolutely necessary, since it creates a hard dependency from application logic to the view.) On a postback request, component bindings are updated during the Restore View phase, before the Seam conversation context has been restored."
-msgstr ""
+msgstr "I componenti conversazionali hanno una piccola limitazione: non possono essere usati per mantenere un riferimento ai componenti JSF. (In generali si preferisce non usare questa funzionalità di JSF amenoché sia assolutamente necessario, poiché questo crea una dipendenza stretta della logica dell'applicazione con la vista.) Sulle richieste postback, i binding dei componenti vengono aggiornati durante la fase restore view, prima che il contesto della conversazione di Seam venga ripristinato."
#. Tag: para
#: Conversations.xml:865
#, no-c-format
msgid "To work around this use an event scoped component to store the component bindings and inject it into the conversation scoped component that requires it."
-msgstr ""
+msgstr "Per aggirare questo si usa un componente con scope evento per memorizzare i binding dei componenti ed per iniettarlo nel componente a scope conversazione che lo richiede."
#. Tag: programlisting
#: Conversations.xml:870
@@ -1294,13 +1294,13 @@
#: Conversations.xml:875
#, no-c-format
msgid "Also, you can't inject a conversation scoped component into an event scoped component which you bind a JSF control to. This includes Seam built in components like <literal>facesMessages</literal>."
-msgstr ""
+msgstr "Inoltre non si può iniettare un componente con scope conversazione in un componente con scope evento a cui associare il controllo JSF. Questo include i componenti predefiniti Seam come <literal>facesMessages</literal>."
#. Tag: para
#: Conversations.xml:881
#, no-c-format
-msgid "Alternatively, you can access the JSF component tree through the implicit <literal>uiComponent</literal> handle. The following example accesses <literal>getRowIndex()</literal>of the <literal>UIData</literal> component which backs the data table during iteration, it prints the current row number:"
-msgstr ""
+msgid "Alternatively, you can access the JSF component tree through the implicit <literal>uiComponent</literal> handle. The following example accesses <literal>getRowIndex()</literal> of the <literal>UIData</literal> component which backs the data table during iteration, it prints the current row number:"
+msgstr "In alternativa si può accedere all'albero del componente JSF attraverso l'handle implicito <literal>uiComponent</literal>. Il seguente esempio accede a <literal>getRowIndex()</literal> del componente <literal>UIData</literal> che è retrostante alla tabella dei dati durante l'interazione, e stampa il numero della riga corrente:"
#. Tag: programlisting
#: Conversations.xml:888
@@ -1326,7 +1326,7 @@
#: Conversations.xml:890
#, no-c-format
msgid "JSF UI components are available with their client identifier in this map."
-msgstr ""
+msgstr "I componenti JSF UI sono disponibili in questa mappa con il loro identificatore di client."
#. Tag: title
#: Conversations.xml:897
@@ -1338,25 +1338,25 @@
#: Conversations.xml:899
#, no-c-format
msgid "A general discussion of concurrent calls to Seam components can be found in <xref linkend=\"concurrency\"/>. Here we will discuss the most common situation in which you will encounter concurrency — accessing conversational components from AJAX requests. We're going to discuss the options that a Ajax client library should provide to control events originating at the client — and we'll look at the options RichFaces gives you."
-msgstr ""
+msgstr "Una discussione generale sulle chiamate concorrenti ai componenti Seam può essere trovata in <xref linkend=\"concurrency\"/>. Qua si discuterà la situazione più comune in cui si troverà la concorrenza — accedendo a componenti conversazionali da richieste AJAX. Si dicuteranno le opzioni che la libreria client Ajax dovrebbe fornire per controllare gli eventi originati nel client — e si vedranno le opzioni che fornisce RichFaces."
#. Tag: para
#: Conversations.xml:909
#, no-c-format
msgid "Conversational components don't allow real concurrent access therefore Seam queues each request to process them serially. This allows each request to be executed in a deterministic fashion. However, a simple queue isn't that great — firstly, if a method is, for some reason, taking a very long time to complete, running it over and over again whenever the client generates a request is bad idea (potential for Denial of Service attacks), and, secondly, AJAX is often to used to provide a quick status update to the user, so continuing to run the action after a long time isn't useful."
-msgstr ""
+msgstr "I componenti conversazionali non consentono una vero accesso concorrente, e quindi Seam accoda ogna richiesta per poi processarla in modo seriale. Questo consente ad ogni richiesta di venir eseguita in un modo deterministico. Comunque, una semplice cosa non è cosa ottima — in primo luogo, se un metodo per qualche ragione impiega molto tempo a terminare, eseguirlo più volte quando il client genera una richiesta, è una cattiva idea (potenziale per attacchi di tipo Denial of Service), ed in secondo luogo, AJAX spesso viene usato per fornire un veloce aggiornamento dello stato all'utente, e così continuare ad eseguire l'azione per lungo tempo non è utile."
#. Tag: para
#: Conversations.xml:921
#, no-c-format
msgid "Therefore, when you are working inside a long running conversation, Seam queues the action event for a period of time (the concurrent request timeout); if it can't process the event in time, it creates a temporary conversation and prints out a message to the user to let them know what's going on. It's therefore very important not to flood the server with AJAX events!"
-msgstr ""
+msgstr "Quindi quando si lavora all'interno di una conversazione long-running, Seam accoda l'evento azione per un periodo di tempo (il timeout della richiesta concorrente); se non si può processare l'evento in tempo, si crea una conversazione temporanea e si stampa un messaggio all'utente per rendergli noto cosa sta succedendo. E' quindi molto importante non inondare il server con eventi AJAX!"
#. Tag: para
#: Conversations.xml:930
#, no-c-format
msgid "We can set a sensible default for the concurrent request timeout (in ms) in components.xml:"
-msgstr ""
+msgstr "Si può impostare un valore di default sensibile per il timeout delle richieste concorrenti (in ms) dentro il file components.xml:"
#. Tag: programlisting
#: Conversations.xml:935
@@ -1368,7 +1368,7 @@
#: Conversations.xml:937
#, no-c-format
msgid "We can also fine tune the concurrent request timeout on a page-by-page basis:"
-msgstr ""
+msgstr "Si può anche perfezionare questo timeout a livello di ogni singola pagina:"
#. Tag: programlisting
#: Conversations.xml:942
@@ -1388,43 +1388,43 @@
#: Conversations.xml:944
#, no-c-format
msgid "So far we've discussed AJAX requests which appear serial to the user - the client tells the server that an event has occur, and then rerenders part of the page based on the result. This approach is great when the AJAX request is lightweight (the methods called are simple e.g. calculating the sum of a column of numbers). But what if we need to do a complex computation thats going to take a minute?"
-msgstr ""
+msgstr "Finora si è discusso delle richieste AJAX che appaiono in serie all'utente - il client dice al server quale evento avviene, e quindi rigenera parte della pagina a seconda del risultato. Questo approccio è ottimo quando la richiesta AJAX è leggera (i metodi chiamati sono semplici, per esempio il calcolo della somma di una colonna di numeri): Ma cosa succede se occorre un calcolo più complesso che dura diversi minuti?"
#. Tag: para
#: Conversations.xml:953
#, no-c-format
msgid "For heavy computation we should use a poll based approach — the client sends an AJAX request to the server, which causes action to be executed asynchronously on the server (the response to the client is immediate) and the client then polls the server for updates. This is good approach when you have a long-running action for which it is important that every action executes (you don't want some to timeout)."
-msgstr ""
+msgstr "Per una computazione pesante occorre usare un approccio basato sull'interrogazione — il client spedisce una richiesta AJAX al server, che causa un'azione asincrona sul server (la risposta al client è immediata) ed il client quindi interroga il server per gli aggiornamenti. Questo è un buon approccio quando si ha un'azione long-running per la quale è importante che ciascuna azione venga eseguita (non si vuole che qualcuna vada in timeout)."
#. Tag: title
#: Conversations.xml:963
#, no-c-format
msgid "How should we design our conversational AJAX application?"
-msgstr ""
+msgstr "Come si può progettare la nostra applicazione AJAX conversazionale?"
#. Tag: para
#: Conversations.xml:965
#, no-c-format
msgid "Well first, you need to decide whether you want to use the simpler \"serial\" request or whether you want to use a polling approach."
-msgstr ""
+msgstr "In primo luogo occorre decidere se si vuole usare una richiesta semplice \"seriale\" e se si vuole l'approccio con interrogazione."
#. Tag: para
#: Conversations.xml:970
#, no-c-format
msgid "If you go for a \"serial\" requests, then you need to estimate how long your request will take to complete - is it much shorter than the concurrent request timeout? If not, you probably want to alter the concurrent request timeout for this page (as discussed above). You probably want a queue on the client side to prevent flooding the server with requests. If the event occurs often (e.g. a keypress, onblur of input fields) and immediate update of the client is not a priority you should set a request delay on the client side. When working out your request delay, factor in that the event may also be queued on the server side."
-msgstr ""
+msgstr "Nel caso di richiesta \"seriale\" occorre stimare quando tempo occorrerà alle richieste per completarsi - è più breve del timeout della richiesta concorrente? Altrimenti si potrebbe volere probabilmente modificare il timeout per questa pagina (come discusso sopra). Si vuole che la coda lato client prevenga l'inondazione di richiesta al server. Se l'evento si verifica spesso (es. keypress, onblur di un campo d'input) e l'aggiornamento immediato del client non è una priorità si deve ritardare la richiesta lato client. Quando si lavora sul ritardo delle richieste, si tenga presente che l'evento può venire accodato anche lato server."
#. Tag: para
#: Conversations.xml:983
#, no-c-format
msgid "Finally, the client library may provide an option to abort unfinished duplicate requests in favor of the most recent."
-msgstr ""
+msgstr "Infine la libreria del client può fornire un'opzione su come abbandonare le richieste duplicate non terminate a favore di quelle più recenti."
#. Tag: para
#: Conversations.xml:988
#, no-c-format
msgid "Using a poll-style design requires less fine-tuning. You just mark your action method <literal>@Asynchronous</literal> and decide on a polling interval:"
-msgstr ""
+msgstr "Usando un design di tipo interrogazione richiede un minor fine-tuning. Basta marcare il metodo d'azione con <literal>@Asynchronous</literal> e decidere l'intervallo di interrogazione:"
#. Tag: programlisting
#: Conversations.xml:994
@@ -1470,7 +1470,7 @@
#: Conversations.xml:1000
#, no-c-format
msgid "However carefully you design your application to queue concurrent requests to your conversational component, there is a risk that the server will become overloaded and be unable to process all the requests before the request will have to wait longer than the <literal>concurrent-request-timeout</literal>. In this case Seam will throw a <literal>ConcurrentRequestTimeoutException</literal> which can be handled in <literal>pages.xml</literal>. We recommend sending an HTTP 503 error:"
-msgstr ""
+msgstr "Comunque per quanto in modo attento si progetti la propria applicazione in modo che accodi le richieste concorrenti nel componente conversazionale, c'è il rischio che il server venga sovraccaricato e sia incapace di processare tutte le richieste prima che la richiesta debba aspettare più a lungo del <literal>concurrent-request-timeout</literal>. In questo caso Seam lancerà una <literal>ConcurrentRequestTimeoutException</literal> che potrà venir gestita in <literal>pages.xml</literal>. Si raccomanda di inviare un errore HTTP 503:"
#. Tag: programlisting
#: Conversations.xml:1011
@@ -1494,7 +1494,7 @@
#: Conversations.xml:1016
#, no-c-format
msgid "The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay."
-msgstr ""
+msgstr "Il server è incapace di gestire la richiesta a causa di un temporaneo sovraccarico o di una manutenzione al server. L'implicazione è che questa è una condizione temporanea che verrà risolta dopo un qualche ritardo."
#. Tag: para
#: Conversations.xml:1024
@@ -1523,8 +1523,8 @@
#. Tag: para
#: Conversations.xml:1030
#, no-c-format
-msgid "ICEfaces, RichFaces Ajax and Seam Remoting can all handle HTTP error codes. Seam Remoting will pop up a dialog box showing the HTTP error and ICEfaces will indicate the error in it's connection status component. RichFaces Ajax provides the most complete support for handling HTTP errors by providing a user definable callback. For example, to show the error message to the user:"
-msgstr ""
+msgid "ICEfaces, RichFaces Ajax and Seam Remoting can all handle HTTP error codes. Seam Remoting will pop up a dialog box showing the HTTP error and ICEfaces will indicate the error in its connection status component. RichFaces Ajax provides the most complete support for handling HTTP errors by providing a user definable callback. For example, to show the error message to the user:"
+msgstr "ICEfaces, RichFaces Ajax e Seam Remoting possono tutti gestire i codici d'errore HTTP. Seam Remoting mostrerà una finestra di dialogo con l'errore HTTP e ICEfaces indicherà l'errore nel suo componente di stato. RichFaces Ajax fornisce il supporto più completo per la gestione degli errori HTTP e chiamate callback definibili dall'utente. Per esempio, per mostrare il messaggio d'errore all'utente:"
#. Tag: programlisting
#: Conversations.xml:1039
@@ -1552,37 +1552,37 @@
#: Conversations.xml:1046
#, no-c-format
msgid "RichFaces Ajax is the AJAX library most commonly used with Seam, and provides all the controls discussed above:"
-msgstr ""
+msgstr "RichFaces Ajax è la libreria AJAX più usata in Seam e fornisce tutti i controlli discussi sopra:"
#. Tag: para
#: Conversations.xml:1053
#, no-c-format
-msgid "<literal>eventsQueue</literal> — provide a queue in which events are placed. All events are queued and requests are sent to the server serially. This is useful if the request can to the server can take some time to execute (e.g. heavy computation, retrieving information from a slow source) as the server isn't flooded."
-msgstr ""
+msgid "<literal>eventsQueue</literal> — provides a queue in which events are placed. All events are queued and requests are sent to the server serially. This is useful if the request to the server can take some time to execute (e.g. heavy computation, retrieving information from a slow source) as the server isn't flooded."
+msgstr "<literal>eventsQueue</literal> — fornisce una coda in cui vengono messi gli eventi. Tutti gli eventi vengono accodati e le richieste vengono inviate al server in modo seriale. Questo è utile se la richiesta al server può prendersi un pò di tempo per essere eseguita (es. computazione pesante, recupero di informazioni da una sorgente lenta) ed il server non viene inondato."
#. Tag: para
#: Conversations.xml:1063
#, no-c-format
-msgid "<literal>ignoreDupResponses</literal> — ignore the response produced by the request if a more recent 'similar' request is already in the queue. ignoreDupResponses=\"true\" does <emphasis>not cancel</emphasis> the the processing of the request on the server side — just prevents unnecessary updates on the client side."
-msgstr ""
+msgid "<literal>ignoreDupResponses</literal> — ignores the response produced by the request if a more recent 'similar' request is already in the queue. ignoreDupResponses=\"true\" does <emphasis>not cancel</emphasis> the processing of the request on the server side — just prevents unnecessary updates on the client side."
+msgstr "<literal>ignoreDupResponses</literal> — ignora la risposta prodotta dalla richiesta se una recente richiesta simile è già in coda. ignoreDupResponses=\"true\" <emphasis>non cancella</emphasis> l'elaborazione della richiesta lato server — previene solamente aggiornamenti non necessari lato client."
#. Tag: para
#: Conversations.xml:1070
#, no-c-format
msgid "This option should be used with care with Seam's conversations as it allows multiple concurrent requests to be made."
-msgstr ""
+msgstr "Quest'opzione dovrebbe essere usata con cautela nelle conversazioni Seam poiché consente di eseguire richeste concorrenti multiple."
#. Tag: para
#: Conversations.xml:1076
#, no-c-format
msgid "<literal>requestDelay</literal> — defines the time (in ms.) that the request will be remain on the queue. If the request has not been processed by after this time the request will be sent (regardless of whether a response has been received) or discarded (if there is a more recent similar event on the queue)."
-msgstr ""
+msgstr "<literal>requestDelay</literal> — definisce il tempo (in ms) in cui la richiesta rimane in coda. Se la richiesta non è stata processata dopo questo tempo, la richiesta verrà inviata (anche se la risposta è stata ricevuta) o scartata (se c'è in coda una richiesta recente simile)."
#. Tag: para
#: Conversations.xml:1083
#, no-c-format
msgid "This option should be used with care with Seam's conversations as it allows multiple concurrent requests to be made. You need to be sure that the delay you set (in combination with the concurrent request timeout) is longer than the action will take to execute."
-msgstr ""
+msgstr "Quest'opzione dovrebbe essere usata con cautela nelle conversazioni Seam poiché consente richieste concorrenti multiple- Occorre accertarsi che il ritardo impostato (in combinazione con il timeout delle richieste concorrenti) sia più lungo dell'azione da eseguire."
#. Tag: para
#: Conversations.xml:1091
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Drools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Drools.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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-25 15:04+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:13+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -208,8 +208,8 @@
#. Tag: para
#: Drools.xml:90
#, no-c-format
-msgid "You can even allow a rule base to act as a jBPM action handler, decision handler, or assignment handler—in either a pageflow or business process definition."
-msgstr "Si può anche consentire alla base di regole di agire come action handler di jBPM, decision handler, o assignment handler— sia in una definizione di pageflow sia in un processo di business."
+msgid "You can even allow a rule base to act as a jBPM action handler, decision handler, or assignment handler — in either a pageflow or business process definition."
+msgstr "Si può anche consentire alla base di regole di agire come action handler di jBPM, decision handler, o assignment handler — sia in una definizione di pageflow sia in un processo di business."
#. Tag: programlisting
#: Drools.xml:96
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Events.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Events.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Events.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,7 +5,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-12-04 00:58+0000\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
"PO-Revision-Date: 2008-12-15 18:36+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
@@ -22,7 +22,13 @@
#. Tag: para
#: Events.xml:7
#, no-c-format
-msgid "Complementing the contextual component model, there are two further basic concepts that facilitate the extreme loose-coupling that is the distinctive feature of Seam applications. The first is a strong event model where events may be mapped to event listeners via JSF-like method binding expressions. The second is the pervasive use of annotations and interceptors to apply cross-cutting concerns to components which implement business logic."
+msgid ""
+"Complementing the contextual component model, there are two further basic "
+"concepts that facilitate the extreme loose-coupling that is the distinctive "
+"feature of Seam applications. The first is a strong event model where events "
+"may be mapped to event listeners via JSF-like method binding expressions. "
+"The second is the pervasive use of annotations and interceptors to apply "
+"cross-cutting concerns to components which implement business logic."
msgstr ""
#. Tag: title
@@ -34,7 +40,11 @@
#. Tag: para
#: Events.xml:18
#, no-c-format
-msgid "The Seam component model was developed for use with <emphasis>event-driven applications</emphasis>, specifically to enable the development of fine-grained, loosely-coupled components in a fine-grained eventing model. Events in Seam come in several types, most of which we have already seen:"
+msgid ""
+"The Seam component model was developed for use with <emphasis>event-driven "
+"applications</emphasis>, specifically to enable the development of fine-"
+"grained, loosely-coupled components in a fine-grained eventing model. Events "
+"in Seam come in several types, most of which we have already seen:"
msgstr ""
#. Tag: para
@@ -70,19 +80,28 @@
#. Tag: para
#: Events.xml:43
#, no-c-format
-msgid "All of these various kinds of events are mapped to Seam components via JSF EL method binding expressions. For a JSF event, this is defined in the JSF template:"
+msgid ""
+"All of these various kinds of events are mapped to Seam components via JSF "
+"EL method binding expressions. For a JSF event, this is defined in the JSF "
+"template:"
msgstr ""
#. Tag: programlisting
#: Events.xml:48
#, no-c-format
-msgid "<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}\"/>]]>"
-msgstr "<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}\"/>]]>"
+msgid ""
+"<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}"
+"\"/>]]>"
+msgstr ""
+"<![CDATA[<h:commandButton value=\"Click me!\" action=\"#{helloWorld.sayHello}"
+"\"/>]]>"
#. Tag: para
#: Events.xml:52
#, no-c-format
-msgid "For a jBPM transition event, it is specified in the jBPM process definition or pageflow definition:"
+msgid ""
+"For a jBPM transition event, it is specified in the jBPM process definition "
+"or pageflow definition:"
msgstr ""
#. Tag: programlisting
@@ -104,7 +123,10 @@
#. Tag: para
#: Events.xml:59
#, no-c-format
-msgid "You can find out more information about JSF events and jBPM events elsewhere. Let's concentrate for now upon the two additional kinds of events defined by Seam."
+msgid ""
+"You can find out more information about JSF events and jBPM events "
+"elsewhere. Let's concentrate for now upon the two additional kinds of events "
+"defined by Seam."
msgstr ""
#. Tag: title
@@ -116,7 +138,10 @@
#. Tag: para
#: Events.xml:68
#, no-c-format
-msgid "A Seam page action is an event that occurs just before we render a page. We declare page actions in <literal>WEB-INF/pages.xml</literal>. We can define a page action for either a particular JSF view id:"
+msgid ""
+"A Seam page action is an event that occurs just before we render a page. We "
+"declare page actions in <literal>WEB-INF/pages.xml</literal>. We can define "
+"a page action for either a particular JSF view id:"
msgstr ""
#. Tag: programlisting
@@ -134,7 +159,10 @@
#. Tag: para
#: Events.xml:76
#, no-c-format
-msgid "Or we can use a <literal>*</literal> wildcard as a suffix to the <literal>view-id</literal> to specify an action that applies to all view ids that match the pattern:"
+msgid ""
+"Or we can use a <literal>*</literal> wildcard as a suffix to the "
+"<literal>view-id</literal> to specify an action that applies to all view ids "
+"that match the pattern:"
msgstr ""
#. Tag: programlisting
@@ -152,19 +180,27 @@
#. Tag: para
#: Events.xml:84
#, no-c-format
-msgid "If multiple wildcarded page actions match the current view-id, Seam will call all the actions, in order of least-specific to most-specific."
+msgid ""
+"If multiple wildcarded page actions match the current view-id, Seam will "
+"call all the actions, in order of least-specific to most-specific."
msgstr ""
#. Tag: para
#: Events.xml:89
#, no-c-format
-msgid "The page action method can return a JSF outcome. If the outcome is non-null, Seam will use the defined navigation rules to navigate to a view."
+msgid ""
+"The page action method can return a JSF outcome. If the outcome is non-null, "
+"Seam will use the defined navigation rules to navigate to a view."
msgstr ""
#. Tag: para
#: Events.xml:94
#, no-c-format
-msgid "Furthermore, the view id mentioned in the <literal><page></literal> element need not correspond to a real JSP or Facelets page! So, we can reproduce the functionality of a traditional action-oriented framework like Struts or WebWork using page actions. For example:"
+msgid ""
+"Furthermore, the view id mentioned in the <literal><page></literal> "
+"element need not correspond to a real JSP or Facelets page! So, we can "
+"reproduce the functionality of a traditional action-oriented framework like "
+"Struts or WebWork using page actions. For example:"
msgstr ""
#. Tag: programlisting
@@ -176,13 +212,17 @@
#. Tag: para
#: Events.xml:104
#, no-c-format
-msgid "This is quite useful if you want to do complex things in response to non-faces requests (for example, HTTP GET requests)."
+msgid ""
+"This is quite useful if you want to do complex things in response to non-"
+"faces requests (for example, HTTP GET requests)."
msgstr ""
#. Tag: para
#: Events.xml:109
#, no-c-format
-msgid "Multiple or conditional page actions my be specified using the <literal><action></literal> tag:"
+msgid ""
+"Multiple or conditional page actions my be specified using the <literal><"
+"action></literal> tag:"
msgstr ""
#. Tag: programlisting
@@ -191,14 +231,16 @@
msgid ""
"<![CDATA[<pages>\n"
" <page view-id=\"/hello.jsp\">\n"
-" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation.failed}\"/>\n"
+" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation."
+"failed}\"/>\n"
" <action execute=\"#{hitCount.increment}\"/>\n"
" </page>\n"
"</pages>]]>"
msgstr ""
"<![CDATA[<pages>\n"
" <page view-id=\"/hello.jsp\">\n"
-" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation.failed}\"/>\n"
+" <action execute=\"#{helloWorld.sayHello}\" if=\"#{not validation."
+"failed}\"/>\n"
" <action execute=\"#{hitCount.increment}\"/>\n"
" </page>\n"
"</pages>]]>"
@@ -212,13 +254,19 @@
#. Tag: para
#: Events.xml:122
#, no-c-format
-msgid "A JSF faces request (a form submission) encapsulates both an \"action\" (a method binding) and \"parameters\" (input value bindings). A page action might also needs parameters!"
+msgid ""
+"A JSF faces request (a form submission) encapsulates both an \"action\" (a "
+"method binding) and \"parameters\" (input value bindings). A page action "
+"might also needs parameters!"
msgstr ""
#. Tag: para
#: Events.xml:128
#, no-c-format
-msgid "Since GET requests are bookmarkable, page parameters are passed as human-readable request parameters. (Unlike JSF form inputs, which are anything but!)"
+msgid ""
+"Since GET requests are bookmarkable, page parameters are passed as human-"
+"readable request parameters. (Unlike JSF form inputs, which are anything "
+"but!)"
msgstr ""
#. Tag: para
@@ -236,7 +284,9 @@
#. Tag: para
#: Events.xml:141
#, no-c-format
-msgid "Seam lets us provide a value binding that maps a named request parameter to an attribute of a model object."
+msgid ""
+"Seam lets us provide a value binding that maps a named request parameter to "
+"an attribute of a model object."
msgstr ""
#. Tag: programlisting
@@ -260,37 +310,58 @@
#. Tag: para
#: Events.xml:148
#, no-c-format
-msgid "The <literal><param></literal> declaration is bidirectional, just like a value binding for a JSF input:"
+msgid ""
+"The <literal><param></literal> declaration is bidirectional, just like "
+"a value binding for a JSF input:"
msgstr ""
#. Tag: para
#: Events.xml:155
#, no-c-format
-msgid "When a non-faces (GET) request for the view id occurs, Seam sets the value of the named request parameter onto the model object, after performing appropriate type conversions."
+msgid ""
+"When a non-faces (GET) request for the view id occurs, Seam sets the value "
+"of the named request parameter onto the model object, after performing "
+"appropriate type conversions."
msgstr ""
#. Tag: para
#: Events.xml:162
#, no-c-format
-msgid "Any <literal><s:link></literal> or <literal><s:button></literal> transparently includes the request parameter. The value of the parameter is determined by evaluating the value binding during the render phase (when the <literal><s:link></literal> is rendered)."
+msgid ""
+"Any <literal><s:link></literal> or <literal><s:button></literal> "
+"transparently includes the request parameter. The value of the parameter is "
+"determined by evaluating the value binding during the render phase (when the "
+"<literal><s:link></literal> is rendered)."
msgstr ""
#. Tag: para
#: Events.xml:170
#, no-c-format
-msgid "Any navigation rule with a <literal><redirect/></literal> to the view id transparently includes the request parameter. The value of the parameter is determined by evaluating the value binding at the end of the invoke application phase."
+msgid ""
+"Any navigation rule with a <literal><redirect/></literal> to the view "
+"id transparently includes the request parameter. The value of the parameter "
+"is determined by evaluating the value binding at the end of the invoke "
+"application phase."
msgstr ""
#. Tag: para
#: Events.xml:178
#, no-c-format
-msgid "The value is transparently propagated with any JSF form submission for the page with the given view id. This means that view parameters behave like <literal>PAGE</literal>-scoped context variables for faces requests."
+msgid ""
+"The value is transparently propagated with any JSF form submission for the "
+"page with the given view id. This means that view parameters behave like "
+"<literal>PAGE</literal>-scoped context variables for faces requests."
msgstr ""
#. Tag: para
#: Events.xml:187
#, no-c-format
-msgid "The essential idea behind all this is that <emphasis>however</emphasis> we get from any other page to <literal>/hello.jsp</literal> (or from <literal>/hello.jsp</literal> back to <literal>/hello.jsp</literal>), the value of the model attribute referred to in the value binding is \"remembered\", without the need for a conversation (or other server-side state)."
+msgid ""
+"The essential idea behind all this is that <emphasis>however</emphasis> we "
+"get from any other page to <literal>/hello.jsp</literal> (or from <literal>/"
+"hello.jsp</literal> back to <literal>/hello.jsp</literal>), the value of the "
+"model attribute referred to in the value binding is \"remembered\", without "
+"the need for a conversation (or other server-side state)."
msgstr ""
#. Tag: title
@@ -302,7 +373,10 @@
#. Tag: para
#: Events.xml:202
#, no-c-format
-msgid "If just the <literal>name</literal> attribute is specified then the request parameter is propagated using the <literal>PAGE</literal> context (it isn't mapped to model property)."
+msgid ""
+"If just the <literal>name</literal> attribute is specified then the request "
+"parameter is propagated using the <literal>PAGE</literal> context (it isn't "
+"mapped to model property)."
msgstr ""
#. Tag: programlisting
@@ -326,25 +400,44 @@
#. Tag: para
#: Events.xml:211
#, no-c-format
-msgid "Propagation of page parameters is especially useful if you want to build multi-layer master-detail CRUD pages. You can use it to \"remember\" which view you were previously on (e.g. when pressing the Save button), and which entity you were editing."
+msgid ""
+"Propagation of page parameters is especially useful if you want to build "
+"multi-layer master-detail CRUD pages. You can use it to \"remember\" which "
+"view you were previously on (e.g. when pressing the Save button), and which "
+"entity you were editing."
msgstr ""
#. Tag: para
#: Events.xml:218
#, no-c-format
-msgid "Any <literal><s:link></literal> or <literal><s:button></literal> transparently propagates the request parameter if that parameter is listed as a page parameter for the view."
+msgid ""
+"Any <literal><s:link></literal> or <literal><s:button></literal> "
+"transparently propagates the request parameter if that parameter is listed "
+"as a page parameter for the view."
msgstr ""
#. Tag: para
#: Events.xml:225
#, no-c-format
-msgid "The value is transparently propagated with any JSF form submission for the page with the given view id. (This means that view parameters behave like <literal>PAGE</literal>-scoped context variables for faces requests."
+msgid ""
+"The value is transparently propagated with any JSF form submission for the "
+"page with the given view id. (This means that view parameters behave like "
+"<literal>PAGE</literal>-scoped context variables for faces requests."
msgstr ""
#. Tag: para
#: Events.xml:234
#, no-c-format
-msgid "This all sounds pretty complex, and you're probably wondering if such an exotic construct is really worth the effort. Actually, the idea is very natural once you \"get it\". It is definitely worth taking the time to understand this stuff. Page parameters are the most elegant way to propagate state across a non-faces request. They are especially cool for problems like search screens with bookmarkable results pages, where we would like to be able to write our application code to handle both POST and GET requests with the same code. Page parameters eliminate repetitive listing of request parameters in the view definition and make redirects much easier to code."
+msgid ""
+"This all sounds pretty complex, and you're probably wondering if such an "
+"exotic construct is really worth the effort. Actually, the idea is very "
+"natural once you \"get it\". It is definitely worth taking the time to "
+"understand this stuff. Page parameters are the most elegant way to propagate "
+"state across a non-faces request. They are especially cool for problems like "
+"search screens with bookmarkable results pages, where we would like to be "
+"able to write our application code to handle both POST and GET requests with "
+"the same code. Page parameters eliminate repetitive listing of request "
+"parameters in the view definition and make redirects much easier to code."
msgstr ""
#. Tag: title
@@ -356,7 +449,10 @@
#. Tag: para
#: Events.xml:251
#, no-c-format
-msgid "Rewriting occurs based on rewrite patterns found for views in <literal>pages.xml</literal>. Seam URL rewriting does both incoming and outgoing URL rewriting based on the same pattern. Here's a simple pattern:"
+msgid ""
+"Rewriting occurs based on rewrite patterns found for views in <literal>pages."
+"xml</literal>. Seam URL rewriting does both incoming and outgoing URL "
+"rewriting based on the same pattern. Here's a simple pattern:"
msgstr ""
#. Tag: programlisting
@@ -378,13 +474,22 @@
#. Tag: para
#: Events.xml:260
#, no-c-format
-msgid "In this case, any incoming request for <literal>/home</literal> will be sent to <literal>/home.xhtml</literal>. More interestingly, any link generated that would normally point to <literal>/home.seam</literal> will instead be rewritten as <literal>/home</literal>. Rewrite patterns only match the portion of the URL before the query parameters. So, <literal>/home.seam?conversationId=13</literal> and <literal>/home.seam?color=red</literal> will both be matched by this rewrite rule."
+msgid ""
+"In this case, any incoming request for <literal>/home</literal> will be sent "
+"to <literal>/home.xhtml</literal>. More interestingly, any link generated "
+"that would normally point to <literal>/home.seam</literal> will instead be "
+"rewritten as <literal>/home</literal>. Rewrite patterns only match the "
+"portion of the URL before the query parameters. So, <literal>/home.seam?"
+"conversationId=13</literal> and <literal>/home.seam?color=red</literal> will "
+"both be matched by this rewrite rule."
msgstr ""
#. Tag: para
#: Events.xml:270
#, no-c-format
-msgid "Rewrite rules can take these query paramters into consideration, as shown with the following rules."
+msgid ""
+"Rewrite rules can take these query paramters into consideration, as shown "
+"with the following rules."
msgstr ""
#. Tag: programlisting
@@ -408,13 +513,23 @@
#. Tag: para
#: Events.xml:275
#, no-c-format
-msgid "In this case, an incoming request for <literal>/home/red</literal> will be served as if it were a request for <literal>/home.seam?color=red</literal>. Similarly, if color is a page parameter an outgoing URL that would normally show as <literal>/home.seam?color=blue</literal> would instead be output as <literal>/home/blue</literal>. Rules are processed in order, so it is important to list more specific rules before more general rules."
+msgid ""
+"In this case, an incoming request for <literal>/home/red</literal> will be "
+"served as if it were a request for <literal>/home.seam?color=red</literal>. "
+"Similarly, if color is a page parameter an outgoing URL that would normally "
+"show as <literal>/home.seam?color=blue</literal> would instead be output as "
+"<literal>/home/blue</literal>. Rules are processed in order, so it is "
+"important to list more specific rules before more general rules."
msgstr ""
#. Tag: para
#: Events.xml:285
#, no-c-format
-msgid "Default Seam query parameters can also be mapped using URL rewriting, allowing for another option for hiding Seam's fingerprints. In the following example, <literal>/search.seam?conversationId=13</literal> would be written as <literal>/search-13</literal>."
+msgid ""
+"Default Seam query parameters can also be mapped using URL rewriting, "
+"allowing for another option for hiding Seam's fingerprints. In the following "
+"example, <literal>/search.seam?conversationId=13</literal> would be written "
+"as <literal>/search-13</literal>."
msgstr ""
#. Tag: programlisting
@@ -438,13 +553,20 @@
#. Tag: para
#: Events.xml:292
#, no-c-format
-msgid "Seam URL rewriting provides simple, bidirectional rewriting on a per-view basis. For more complex rewriting rules that cover non-seam components, Seam applications can continue to use the <literal>org.tuckey URLRewriteFilter </literal>or apply rewriting rules at the web server."
+msgid ""
+"Seam URL rewriting provides simple, bidirectional rewriting on a per-view "
+"basis. For more complex rewriting rules that cover non-seam components, Seam "
+"applications can continue to use the <literal>org.tuckey URLRewriteFilter </"
+"literal>or apply rewriting rules at the web server."
msgstr ""
#. Tag: para
#: Events.xml:298
#, no-c-format
-msgid "URL rewriting requires the Seam rewrite filter to be enable. Rewrite filter configuration is discussed in <xref linkend=\"configuration.filters.rewrite\"/>."
+msgid ""
+"URL rewriting requires the Seam rewrite filter to be enable. Rewrite filter "
+"configuration is discussed in <xref linkend=\"configuration.filters.rewrite"
+"\"/>."
msgstr ""
#. Tag: title
@@ -467,7 +589,8 @@
" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" "
+"value=\"#{calculator.op}\"/>\n"
" </page>\n"
"</pages>]]>"
msgstr ""
@@ -475,13 +598,13 @@
" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converterId=\"com.my.calculator.OperatorConverter\" "
+"value=\"#{calculator.op}\"/>\n"
" </page>\n"
"</pages>]]>"
#. Tag: para
-#: Events.xml:314
-#: Events.xml:327
+#: Events.xml:314 Events.xml:327
#, no-c-format
msgid "Alternatively:"
msgstr ""
@@ -494,7 +617,8 @@
" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#"
+"{calculator.op}\"/>\n"
" </page>\n"
"</pages>]]>"
msgstr ""
@@ -502,14 +626,16 @@
" <page view-id=\"/calculator.jsp\" action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#"
+"{calculator.op}\"/>\n"
" </page>\n"
"</pages>]]>"
#. Tag: para
#: Events.xml:321
#, no-c-format
-msgid "JSF validators, and <literal>required=\"true\"</literal> may also be used:"
+msgid ""
+"JSF validators, and <literal>required=\"true\"</literal> may also be used:"
msgstr ""
#. Tag: programlisting
@@ -559,13 +685,17 @@
#. Tag: para
#: Events.xml:333
#, no-c-format
-msgid "Even better, model-based Hibernate validator annotations are automatically recognized and validated."
+msgid ""
+"Even better, model-based Hibernate validator annotations are automatically "
+"recognized and validated."
msgstr ""
#. Tag: para
#: Events.xml:338
#, no-c-format
-msgid "When type conversion or validation fails, a global <literal>FacesMessage</literal> is added to the <literal>FacesContext</literal>."
+msgid ""
+"When type conversion or validation fails, a global <literal>FacesMessage</"
+"literal> is added to the <literal>FacesContext</literal>."
msgstr ""
#. Tag: title
@@ -577,13 +707,17 @@
#. Tag: para
#: Events.xml:348
#, no-c-format
-msgid "You can use standard JSF navigation rules defined in <literal>faces-config.xml</literal> in a Seam application. However, JSF navigation rules have a number of annoying limitations:"
+msgid ""
+"You can use standard JSF navigation rules defined in <literal>faces-config."
+"xml</literal> in a Seam application. However, JSF navigation rules have a "
+"number of annoying limitations:"
msgstr ""
#. Tag: para
#: Events.xml:356
#, no-c-format
-msgid "It is not possible to specify request parameters to be used when redirecting."
+msgid ""
+"It is not possible to specify request parameters to be used when redirecting."
msgstr ""
#. Tag: para
@@ -595,13 +729,18 @@
#. Tag: para
#: Events.xml:366
#, no-c-format
-msgid "Rules work by evaluating the return value of the action method; it is not possible to evaluate an arbitrary EL expression."
+msgid ""
+"Rules work by evaluating the return value of the action method; it is not "
+"possible to evaluate an arbitrary EL expression."
msgstr ""
#. Tag: para
#: Events.xml:373
#, no-c-format
-msgid "A further problem is that \"orchestration\" logic gets scattered between <literal>pages.xml</literal> and <literal>faces-config.xml</literal>. It's better to unify this logic into <literal>pages.xml</literal>."
+msgid ""
+"A further problem is that \"orchestration\" logic gets scattered between "
+"<literal>pages.xml</literal> and <literal>faces-config.xml</literal>. It's "
+"better to unify this logic into <literal>pages.xml</literal>."
msgstr ""
#. Tag: para
@@ -671,7 +810,10 @@
#. Tag: para
#: Events.xml:390
#, no-c-format
-msgid "But it would be even nicer if we didn't have to pollute our <literal>DocumentEditor</literal> component with string-valued return values (the JSF outcomes). So Seam lets us write:"
+msgid ""
+"But it would be even nicer if we didn't have to pollute our "
+"<literal>DocumentEditor</literal> component with string-valued return values "
+"(the JSF outcomes). So Seam lets us write:"
msgstr ""
#. Tag: programlisting
@@ -733,13 +875,18 @@
#. Tag: para
#: Events.xml:403
#, no-c-format
-msgid "The first form evaluates a value binding to determine the outcome value to be used by the subsequent rules. The second approach ignores the outcome and evaluates a value binding for each possible rule."
+msgid ""
+"The first form evaluates a value binding to determine the outcome value to "
+"be used by the subsequent rules. The second approach ignores the outcome and "
+"evaluates a value binding for each possible rule."
msgstr ""
#. Tag: para
#: Events.xml:410
#, no-c-format
-msgid "Of course, when an update succeeds, we probably want to end the current conversation. We can do that like this:"
+msgid ""
+"Of course, when an update succeeds, we probably want to end the current "
+"conversation. We can do that like this:"
msgstr ""
#. Tag: programlisting
@@ -771,7 +918,10 @@
#. Tag: para
#: Events.xml:417
#, no-c-format
-msgid "As we've ended conversation any subsequent requests won't know which document we are interested in. We can pass the document id as a request parameter which also makes the view bookmarkable:"
+msgid ""
+"As we've ended conversation any subsequent requests won't know which "
+"document we are interested in. We can pass the document id as a request "
+"parameter which also makes the view bookmarkable:"
msgstr ""
#. Tag: programlisting
@@ -784,7 +934,8 @@
" <rule if=\"#{documentEditor.errors.empty}\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/viewDocument.xhtml\">\n"
-" <param name=\"documentId\" value=\"#{documentEditor.documentId}\"/>\n"
+" <param name=\"documentId\" value=\"#{documentEditor."
+"documentId}\"/>\n"
" </redirect>\n"
" </rule>\n"
" </navigation>\n"
@@ -797,7 +948,8 @@
" <rule if=\"#{documentEditor.errors.empty}\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/viewDocument.xhtml\">\n"
-" <param name=\"documentId\" value=\"#{documentEditor.documentId}\"/>\n"
+" <param name=\"documentId\" value=\"#{documentEditor."
+"documentId}\"/>\n"
" </redirect>\n"
" </rule>\n"
" </navigation>\n"
@@ -807,7 +959,10 @@
#. Tag: para
#: Events.xml:425
#, no-c-format
-msgid "Null outcomes are a special case in JSF. The null outcome is interpreted to mean \"redisplay the page\". The following navigation rule matches any non-null outcome, but <emphasis>not</emphasis> the null outcome:"
+msgid ""
+"Null outcomes are a special case in JSF. The null outcome is interpreted to "
+"mean \"redisplay the page\". The following navigation rule matches any non-"
+"null outcome, but <emphasis>not</emphasis> the null outcome:"
msgstr ""
#. Tag: programlisting
@@ -837,7 +992,9 @@
#. Tag: para
#: Events.xml:433
#, no-c-format
-msgid "If you want to perform navigation when a null outcome occurs, use the following form instead:"
+msgid ""
+"If you want to perform navigation when a null outcome occurs, use the "
+"following form instead:"
msgstr ""
#. Tag: programlisting
@@ -893,13 +1050,21 @@
#. Tag: title
#: Events.xml:449
#, no-c-format
-msgid "Fine-grained files for definition of navigation, page actions and parameters"
+msgid ""
+"Fine-grained files for definition of navigation, page actions and parameters"
msgstr ""
#. Tag: para
#: Events.xml:451
#, no-c-format
-msgid "If you have a lot of different page actions and page parameters, or even just a lot of navigation rules, you will almost certainly want to split the declarations up over multiple files. You can define actions and parameters for a page with the view id <literal>/calc/calculator.jsp</literal> in a resource named <literal>calc/calculator.page.xml</literal>. The root element in this case is the <literal><page></literal> element, and the view id is implied:"
+msgid ""
+"If you have a lot of different page actions and page parameters, or even "
+"just a lot of navigation rules, you will almost certainly want to split the "
+"declarations up over multiple files. You can define actions and parameters "
+"for a page with the view id <literal>/calc/calculator.jsp</literal> in a "
+"resource named <literal>calc/calculator.page.xml</literal>. The root element "
+"in this case is the <literal><page></literal> element, and the view id "
+"is implied:"
msgstr ""
#. Tag: programlisting
@@ -909,13 +1074,15 @@
"<![CDATA[<page action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#"
+"{calculator.op}\"/>\n"
"</page>]]>"
msgstr ""
"<![CDATA[<page action=\"#{calculator.calculate}\">\n"
" <param name=\"x\" value=\"#{calculator.lhs}\"/>\n"
" <param name=\"y\" value=\"#{calculator.rhs}\"/>\n"
-" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#{calculator.op}\"/>\n"
+" <param name=\"op\" converter=\"#{operatorConverter}\" value=\"#"
+"{calculator.op}\"/>\n"
"</page>]]>"
#. Tag: title
@@ -927,13 +1094,19 @@
#. Tag: para
#: Events.xml:471
#, no-c-format
-msgid "Seam components can interact by simply calling each others methods. Stateful components may even implement the observer/observable pattern. But to enable components to interact in a more loosely-coupled fashion than is possible when the components call each others methods directly, Seam provides <emphasis>component-driven events</emphasis>."
+msgid ""
+"Seam components can interact by simply calling each others methods. Stateful "
+"components may even implement the observer/observable pattern. But to enable "
+"components to interact in a more loosely-coupled fashion than is possible "
+"when the components call each others methods directly, Seam provides "
+"<emphasis>component-driven events</emphasis>."
msgstr ""
#. Tag: para
#: Events.xml:479
#, no-c-format
-msgid "We specify event listeners (observers) in <literal>components.xml</literal>."
+msgid ""
+"We specify event listeners (observers) in <literal>components.xml</literal>."
msgstr ""
#. Tag: programlisting
@@ -963,7 +1136,10 @@
#. Tag: para
#: Events.xml:489
#, no-c-format
-msgid "When an event occurs, the actions registered for that event will be called in the order they appear in <literal>components.xml</literal>. How does a component raise an event? Seam provides a built-in component for this."
+msgid ""
+"When an event occurs, the actions registered for that event will be called "
+"in the order they appear in <literal>components.xml</literal>. How does a "
+"component raise an event? Seam provides a built-in component for this."
msgstr ""
#. Tag: programlisting
@@ -1015,7 +1191,10 @@
#. Tag: para
#: Events.xml:503
#, no-c-format
-msgid "Notice that this event producer has no dependency upon event consumers. The event listener may now be implemented with absolutely no dependency upon the producer:"
+msgid ""
+"Notice that this event producer has no dependency upon event consumers. The "
+"event listener may now be implemented with absolutely no dependency upon the "
+"producer:"
msgstr ""
#. Tag: programlisting
@@ -1039,7 +1218,11 @@
#. Tag: para
#: Events.xml:511
#, no-c-format
-msgid "The method binding defined in <literal>components.xml</literal> above takes care of mapping the event to the consumer. If you don't like futzing about in the <literal>components.xml</literal> file, you can use an annotation instead:"
+msgid ""
+"The method binding defined in <literal>components.xml</literal> above takes "
+"care of mapping the event to the consumer. If you don't like futzing about "
+"in the <literal>components.xml</literal> file, you can use an annotation "
+"instead:"
msgstr ""
#. Tag: programlisting
@@ -1065,7 +1248,12 @@
#. Tag: para
#: Events.xml:520
#, no-c-format
-msgid "You might wonder why I've not mentioned anything about event objects in this discussion. In Seam, there is no need for an event object to propagate state between event producer and listener. State is held in the Seam contexts, and is shared between components. However, if you really want to pass an event object, you can:"
+msgid ""
+"You might wonder why I've not mentioned anything about event objects in this "
+"discussion. In Seam, there is no need for an event object to propagate state "
+"between event producer and listener. State is held in the Seam contexts, and "
+"is shared between components. However, if you really want to pass an event "
+"object, you can:"
msgstr ""
#. Tag: programlisting
@@ -1076,7 +1264,8 @@
"public class HelloWorld {\n"
" private String name;\n"
" public void sayHello() {\n"
-" FacesMessages.instance().add(\"Hello World, my name is #0.\", name);\n"
+" FacesMessages.instance().add(\"Hello World, my name is #0.\", "
+"name);\n"
" Events.instance().raiseEvent(\"hello\", name);\n"
" }\n"
"}]]>"
@@ -1085,7 +1274,8 @@
"public class HelloWorld {\n"
" private String name;\n"
" public void sayHello() {\n"
-" FacesMessages.instance().add(\"Hello World, my name is #0.\", name);\n"
+" FacesMessages.instance().add(\"Hello World, my name is #0.\", "
+"name);\n"
" Events.instance().raiseEvent(\"hello\", name);\n"
" }\n"
"}]]>"
@@ -1119,229 +1309,306 @@
#. Tag: para
#: Events.xml:536
#, no-c-format
-msgid "Seam defines a number of built-in events that the application can use to perform special kinds of framework integration. The events are:"
+msgid ""
+"Seam defines a number of built-in events that the application can use to "
+"perform special kinds of framework integration. The events are:"
msgstr ""
#. Tag: para
#: Events.xml:542
#, no-c-format
-msgid "<literal>org.jboss.seam.validationFailed</literal> — called when JSF validation fails"
+msgid ""
+"<literal>org.jboss.seam.validationFailed</literal> — called when JSF "
+"validation fails"
msgstr ""
#. Tag: para
#: Events.xml:543
#, no-c-format
-msgid "<literal>org.jboss.seam.noConversation</literal> — called when there is no long running conversation and a long running conversation is required"
+msgid ""
+"<literal>org.jboss.seam.noConversation</literal> — called when there "
+"is no long running conversation and a long running conversation is required"
msgstr ""
#. Tag: para
#: Events.xml:544
#, no-c-format
-msgid "<literal>org.jboss.seam.preSetVariable.<name></literal> — called when the context variable <name> is set"
+msgid ""
+"<literal>org.jboss.seam.preSetVariable.<name></literal> — called "
+"when the context variable <name> is set"
msgstr ""
#. Tag: para
#: Events.xml:545
#, no-c-format
-msgid "<literal>org.jboss.seam.postSetVariable.<name></literal> — called when the context variable <name> is set"
+msgid ""
+"<literal>org.jboss.seam.postSetVariable.<name></literal> — "
+"called when the context variable <name> is set"
msgstr ""
#. Tag: para
#: Events.xml:546
#, no-c-format
-msgid "<literal>org.jboss.seam.preRemoveVariable.<name></literal> — called when the context variable <name> is unset"
+msgid ""
+"<literal>org.jboss.seam.preRemoveVariable.<name></literal> — "
+"called when the context variable <name> is unset"
msgstr ""
#. Tag: para
#: Events.xml:547
#, no-c-format
-msgid "<literal>org.jboss.seam.postRemoveVariable.<name></literal> — called when the context variable <name> is unset"
+msgid ""
+"<literal>org.jboss.seam.postRemoveVariable.<name></literal> — "
+"called when the context variable <name> is unset"
msgstr ""
#. Tag: para
#: Events.xml:548
#, no-c-format
-msgid "<literal>org.jboss.seam.preDestroyContext.<SCOPE></literal> — called before the <SCOPE> context is destroyed"
+msgid ""
+"<literal>org.jboss.seam.preDestroyContext.<SCOPE></literal> — "
+"called before the <SCOPE> context is destroyed"
msgstr ""
#. Tag: para
#: Events.xml:549
#, no-c-format
-msgid "<literal>org.jboss.seam.postDestroyContext.<SCOPE></literal> — called after the <SCOPE> context is destroyed"
+msgid ""
+"<literal>org.jboss.seam.postDestroyContext.<SCOPE></literal> — "
+"called after the <SCOPE> context is destroyed"
msgstr ""
#. Tag: para
#: Events.xml:550
#, no-c-format
-msgid "<literal>org.jboss.seam.beginConversation </literal>— called whenever a long-running conversation begins"
+msgid ""
+"<literal>org.jboss.seam.beginConversation </literal> — called whenever "
+"a long-running conversation begins"
msgstr ""
#. Tag: para
#: Events.xml:551
#, no-c-format
-msgid "<literal>org.jboss.seam.endConversation </literal>— called whenever a long-running conversation ends"
+msgid ""
+"<literal>org.jboss.seam.endConversation </literal> — called whenever a "
+"long-running conversation ends"
msgstr ""
#. Tag: para
#: Events.xml:552
#, no-c-format
-msgid "<literal>org.jboss.seam.conversationTimeout</literal>— called when a conversation timeout occurs. The conversation id is passed as a parameter."
+msgid ""
+"<literal>org.jboss.seam.conversationTimeout</literal> — called when a "
+"conversation timeout occurs. The conversation id is passed as a parameter."
msgstr ""
#. Tag: para
#: Events.xml:553
#, no-c-format
-msgid "<literal>org.jboss.seam.beginPageflow </literal>— called when a pageflow begins"
+msgid ""
+"<literal>org.jboss.seam.beginPageflow </literal> — called when a "
+"pageflow begins"
msgstr ""
#. Tag: para
#: Events.xml:554
#, no-c-format
-msgid "<literal>org.jboss.seam.beginPageflow.<name> </literal>— called when the pageflow <name> begins"
+msgid ""
+"<literal>org.jboss.seam.beginPageflow.<name> </literal> — called "
+"when the pageflow <name> begins"
msgstr ""
#. Tag: para
#: Events.xml:555
#, no-c-format
-msgid "<literal>org.jboss.seam.endPageflow </literal>— called when a pageflow ends"
+msgid ""
+"<literal>org.jboss.seam.endPageflow </literal> — called when a "
+"pageflow ends"
msgstr ""
#. Tag: para
#: Events.xml:556
#, no-c-format
-msgid "<literal>org.jboss.seam.endPageflow.<name> </literal>— called when the pageflow <name> ends"
+msgid ""
+"<literal>org.jboss.seam.endPageflow.<name> </literal> — called "
+"when the pageflow <name> ends"
msgstr ""
#. Tag: para
#: Events.xml:557
#, no-c-format
-msgid "<literal>org.jboss.seam.createProcess.<name> </literal>— called when the process <name> is created"
+msgid ""
+"<literal>org.jboss.seam.createProcess.<name> </literal> — called "
+"when the process <name> is created"
msgstr ""
#. Tag: para
#: Events.xml:558
#, no-c-format
-msgid "<literal>org.jboss.seam.endProcess.<name> </literal>— called when the process <name> ends"
+msgid ""
+"<literal>org.jboss.seam.endProcess.<name> </literal> — called "
+"when the process <name> ends"
msgstr ""
#. Tag: para
#: Events.xml:559
#, no-c-format
-msgid "<literal>org.jboss.seam.initProcess.<name> </literal>— called when the process <name> is associated with the conversation"
+msgid ""
+"<literal>org.jboss.seam.initProcess.<name> </literal> — called "
+"when the process <name> is associated with the conversation"
msgstr ""
#. Tag: para
#: Events.xml:560
#, no-c-format
-msgid "<literal>org.jboss.seam.initTask.<name> </literal>— called when the task <name> is associated with the conversation"
+msgid ""
+"<literal>org.jboss.seam.initTask.<name> </literal> — called when "
+"the task <name> is associated with the conversation"
msgstr ""
#. Tag: para
#: Events.xml:561
#, no-c-format
-msgid "<literal>org.jboss.seam.startTask.<name> </literal>— called when the task <name> is started"
+msgid ""
+"<literal>org.jboss.seam.startTask.<name> </literal> — called "
+"when the task <name> is started"
msgstr ""
#. Tag: para
#: Events.xml:562
#, no-c-format
-msgid "<literal>org.jboss.seam.endTask.<name> </literal>— called when the task <name> is ended"
+msgid ""
+"<literal>org.jboss.seam.endTask.<name> </literal> — called when "
+"the task <name> is ended"
msgstr ""
#. Tag: para
#: Events.xml:563
#, no-c-format
-msgid "<literal>org.jboss.seam.postCreate.<name> </literal>— called when the component <name> is created"
+msgid ""
+"<literal>org.jboss.seam.postCreate.<name> </literal> — called "
+"when the component <name> is created"
msgstr ""
#. Tag: para
#: Events.xml:564
#, no-c-format
-msgid "<literal>org.jboss.seam.preDestroy.<name> </literal>— called when the component <name> is destroyed"
+msgid ""
+"<literal>org.jboss.seam.preDestroy.<name> </literal> — called "
+"when the component <name> is destroyed"
msgstr ""
#. Tag: para
#: Events.xml:565
#, no-c-format
-msgid "<literal>org.jboss.seam.beforePhase </literal>— called before the start of a JSF phase"
+msgid ""
+"<literal>org.jboss.seam.beforePhase </literal> — called before the "
+"start of a JSF phase"
msgstr ""
#. Tag: para
#: Events.xml:566
#, no-c-format
-msgid "<literal>org.jboss.seam.afterPhase </literal>— called after the end of a JSF phase"
+msgid ""
+"<literal>org.jboss.seam.afterPhase </literal> — called after the end "
+"of a JSF phase"
msgstr ""
#. Tag: para
#: Events.xml:567
#, no-c-format
-msgid "<literal>org.jboss.seam.postInitialization </literal>— called when Seam has initialized and started up all components"
+msgid ""
+"<literal>org.jboss.seam.postInitialization </literal> — called when "
+"Seam has initialized and started up all components"
msgstr ""
#. Tag: para
#: Events.xml:568
#, no-c-format
-msgid "<literal>org.jboss.seam.postReInitialization </literal>— called when Seam has re-initialized and started up all components after a redeploy"
+msgid ""
+"<literal>org.jboss.seam.postReInitialization </literal> — called when "
+"Seam has re-initialized and started up all components after a redeploy"
msgstr ""
#. Tag: para
#: Events.xml:569
#, no-c-format
-msgid "<literal>org.jboss.seam.postAuthenticate.<name> </literal>— called after a user is authenticated"
+msgid ""
+"<literal>org.jboss.seam.postAuthenticate.<name> </literal> — "
+"called after a user is authenticated"
msgstr ""
#. Tag: para
#: Events.xml:570
#, no-c-format
-msgid "<literal>org.jboss.seam.preAuthenticate.<name> </literal>— called before attempting to authenticate a user"
+msgid ""
+"<literal>org.jboss.seam.preAuthenticate.<name> </literal> — "
+"called before attempting to authenticate a user"
msgstr ""
#. Tag: para
#: Events.xml:571
#, no-c-format
-msgid "<literal>org.jboss.seam.notLoggedIn</literal> — called there is no authenticated user and authentication is required"
+msgid ""
+"<literal>org.jboss.seam.notLoggedIn</literal> — called there is no "
+"authenticated user and authentication is required"
msgstr ""
#. Tag: para
#: Events.xml:572
#, no-c-format
-msgid "<literal>org.jboss.seam.rememberMe</literal> — occurs when Seam security detects the username in a cookie"
+msgid ""
+"<literal>org.jboss.seam.rememberMe</literal> — occurs when Seam "
+"security detects the username in a cookie"
msgstr ""
#. Tag: para
#: Events.xml:573
#, no-c-format
-msgid "<literal>org.jboss.seam.exceptionHandled.<type></literal> — called when an uncaught exception is handled by Seam"
+msgid ""
+"<literal>org.jboss.seam.exceptionHandled.<type></literal> — "
+"called when an uncaught exception is handled by Seam"
msgstr ""
#. Tag: para
#: Events.xml:574
#, no-c-format
-msgid "<literal>org.jboss.seam.exceptionHandled</literal> — called when an uncaught exception is handled by Seam"
+msgid ""
+"<literal>org.jboss.seam.exceptionHandled</literal> — called when an "
+"uncaught exception is handled by Seam"
msgstr ""
#. Tag: para
#: Events.xml:575
#, no-c-format
-msgid "<literal>org.jboss.seam.exceptionNotHandled</literal> — called when there was no handler for an uncaught exception"
+msgid ""
+"<literal>org.jboss.seam.exceptionNotHandled</literal> — called when "
+"there was no handler for an uncaught exception"
msgstr ""
#. Tag: para
#: Events.xml:576
#, no-c-format
-msgid "<literal>org.jboss.seam.afterTransactionSuccess</literal> — called when a transaction succeeds in the Seam Application Framework"
+msgid ""
+"<literal>org.jboss.seam.afterTransactionSuccess</literal> — called "
+"when a transaction succeeds in the Seam Application Framework"
msgstr ""
#. Tag: para
#: Events.xml:577
#, no-c-format
-msgid "<literal>org.jboss.seam.afterTransactionSuccess.<name></literal> — called when a transaction succeeds in the Seam Application Framework which manages an entity called <literal><name></literal>"
+msgid ""
+"<literal>org.jboss.seam.afterTransactionSuccess.<name></literal> "
+"— called when a transaction succeeds in the Seam Application Framework "
+"which manages an entity called <literal><name></literal>"
msgstr ""
#. Tag: para
#: Events.xml:580
#, no-c-format
-msgid "Seam components may observe any of these events in just the same way they observe any other component-driven events."
+msgid ""
+"Seam components may observe any of these events in just the same way they "
+"observe any other component-driven events."
msgstr ""
#. Tag: title
@@ -1353,7 +1620,13 @@
#. Tag: para
#: Events.xml:591
#, no-c-format
-msgid "EJB 3.0 introduced a standard interceptor model for session bean components. To add an interceptor to a bean, you need to write a class with a method annotated <literal>@AroundInvoke</literal> and annotate the bean with an <literal>@Interceptors</literal> annotation that specifies the name of the interceptor class. For example, the following interceptor checks that the user is logged in before allowing invoking an action listener method:"
+msgid ""
+"EJB 3.0 introduced a standard interceptor model for session bean components. "
+"To add an interceptor to a bean, you need to write a class with a method "
+"annotated <literal>@AroundInvoke</literal> and annotate the bean with an "
+"<literal>@Interceptors</literal> annotation that specifies the name of the "
+"interceptor class. For example, the following interceptor checks that the "
+"user is logged in before allowing invoking an action listener method:"
msgstr ""
#. Tag: programlisting
@@ -1363,9 +1636,11 @@
"<![CDATA[public class LoggedInInterceptor {\n"
"\n"
" @AroundInvoke\n"
-" public Object checkLoggedIn(InvocationContext invocation) throws Exception {\n"
+" public Object checkLoggedIn(InvocationContext invocation) throws "
+"Exception {\n"
" \n"
-" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!=null;\n"
+" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!"
+"=null;\n"
" if (isLoggedIn) {\n"
" //the user is already logged in\n"
" return invocation.proceed();\n"
@@ -1381,9 +1656,11 @@
"<![CDATA[public class LoggedInInterceptor {\n"
"\n"
" @AroundInvoke\n"
-" public Object checkLoggedIn(InvocationContext invocation) throws Exception {\n"
+" public Object checkLoggedIn(InvocationContext invocation) throws "
+"Exception {\n"
" \n"
-" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!=null;\n"
+" boolean isLoggedIn = Contexts.getSessionContext().get(\"loggedIn\")!"
+"=null;\n"
" if (isLoggedIn) {\n"
" //the user is already logged in\n"
" return invocation.proceed();\n"
@@ -1399,7 +1676,15 @@
#. Tag: para
#: Events.xml:602
#, no-c-format
-msgid "To apply this interceptor to a session bean which acts as an action listener, we must annotate the session bean <literal>@Interceptors(LoggedInInterceptor.class)</literal>. This is a somewhat ugly annotation. Seam builds upon the interceptor framework in EJB3 by allowing you to use <literal>@Interceptors</literal> as a meta-annotation for class level interceptors (those annotated <literal>@Target(TYPE)</literal>). In our example, we would create an <literal>@LoggedIn</literal> annotation, as follows:"
+msgid ""
+"To apply this interceptor to a session bean which acts as an action "
+"listener, we must annotate the session bean <literal>@Interceptors"
+"(LoggedInInterceptor.class)</literal>. This is a somewhat ugly annotation. "
+"Seam builds upon the interceptor framework in EJB3 by allowing you to use "
+"<literal>@Interceptors</literal> as a meta-annotation for class level "
+"interceptors (those annotated <literal>@Target(TYPE)</literal>). In our "
+"example, we would create an <literal>@LoggedIn</literal> annotation, as "
+"follows:"
msgstr ""
#. Tag: programlisting
@@ -1419,7 +1704,9 @@
#. Tag: para
#: Events.xml:613
#, no-c-format
-msgid "We can now simply annotate our action listener bean with <literal>@LoggedIn</literal> to apply the interceptor."
+msgid ""
+"We can now simply annotate our action listener bean with <literal>@LoggedIn</"
+"literal> to apply the interceptor."
msgstr ""
#. Tag: programlisting
@@ -1453,7 +1740,10 @@
#. Tag: para
#: Events.xml:620
#, no-c-format
-msgid "If interceptor ordering is important (it usually is), you can add <literal>@Interceptor</literal> annotations to your interceptor classes to specify a partial order of interceptors."
+msgid ""
+"If interceptor ordering is important (it usually is), you can add "
+"<literal>@Interceptor</literal> annotations to your interceptor classes to "
+"specify a partial order of interceptors."
msgstr ""
#. Tag: programlisting
@@ -1481,7 +1771,9 @@
#. Tag: para
#: Events.xml:628
#, no-c-format
-msgid "You can even have a \"client-side\" interceptor, that runs around any of the built-in functionality of EJB3:"
+msgid ""
+"You can even have a \"client-side\" interceptor, that runs around any of the "
+"built-in functionality of EJB3:"
msgstr ""
#. Tag: programlisting
@@ -1503,25 +1795,43 @@
#. Tag: para
#: Events.xml:635
#, no-c-format
-msgid "EJB interceptors are stateful, with a lifecycle that is the same as the component they intercept. For interceptors which do not need to maintain state, Seam lets you get a performance optimization by specifying <literal>@Interceptor(stateless=true)</literal>."
+msgid ""
+"EJB interceptors are stateful, with a lifecycle that is the same as the "
+"component they intercept. For interceptors which do not need to maintain "
+"state, Seam lets you get a performance optimization by specifying "
+"<literal>@Interceptor(stateless=true)</literal>."
msgstr ""
#. Tag: para
#: Events.xml:642
#, no-c-format
-msgid "Much of the functionality of Seam is implemented as a set of built-in Seam interceptors, including the interceptors named in the previous example. You don't have to explicitly specify these interceptors by annotating your components; they exist for all interceptable Seam components."
+msgid ""
+"Much of the functionality of Seam is implemented as a set of built-in Seam "
+"interceptors, including the interceptors named in the previous example. You "
+"don't have to explicitly specify these interceptors by annotating your "
+"components; they exist for all interceptable Seam components."
msgstr ""
#. Tag: para
#: Events.xml:649
#, no-c-format
-msgid "You can even use Seam interceptors with JavaBean components, not just EJB3 beans!"
+msgid ""
+"You can even use Seam interceptors with JavaBean components, not just EJB3 "
+"beans!"
msgstr ""
#. Tag: para
#: Events.xml:653
#, no-c-format
-msgid "EJB defines interception not only for business methods (using <literal>@AroundInvoke</literal>), but also for the lifecycle methods <literal>@PostConstruct</literal>, <literal>@PreDestroy</literal>, <literal>@PrePassivate</literal> and <literal>@PostActive</literal>. Seam supports all these lifecycle methods on both component and interceptor not only for EJB3 beans, but also for JavaBean components (except <literal>@PreDestroy</literal> which is not meaningful for JavaBean components)."
+msgid ""
+"EJB defines interception not only for business methods (using "
+"<literal>@AroundInvoke</literal>), but also for the lifecycle methods "
+"<literal>@PostConstruct</literal>, <literal>@PreDestroy</literal>, "
+"<literal>@PrePassivate</literal> and <literal>@PostActive</literal>. Seam "
+"supports all these lifecycle methods on both component and interceptor not "
+"only for EJB3 beans, but also for JavaBean components (except "
+"<literal>@PreDestroy</literal> which is not meaningful for JavaBean "
+"components)."
msgstr ""
#. Tag: title
@@ -1533,7 +1843,14 @@
#. Tag: para
#: Events.xml:667
#, no-c-format
-msgid "JSF is surprisingly limited when it comes to exception handling. As a partial workaround for this problem, Seam lets you define how a particular class of exception is to be treated by annotating the exception class, or declaring the exception class in an XML file. This facility is meant to be combined with the EJB 3.0-standard <literal>@ApplicationException</literal> annotation which specifies whether the exception should cause a transaction rollback."
+msgid ""
+"JSF is surprisingly limited when it comes to exception handling. As a "
+"partial workaround for this problem, Seam lets you define how a particular "
+"class of exception is to be treated by annotating the exception class, or "
+"declaring the exception class in an XML file. This facility is meant to be "
+"combined with the EJB 3.0-standard <literal>@ApplicationException</literal> "
+"annotation which specifies whether the exception should cause a transaction "
+"rollback."
msgstr ""
#. Tag: title
@@ -1545,25 +1862,46 @@
#. Tag: para
#: Events.xml:679
#, no-c-format
-msgid "EJB specifies well-defined rules that let us control whether an exception immediately marks the current transaction for rollback when it is thrown by a business method of the bean: <emphasis>system exceptions</emphasis> always cause a transaction rollback, <emphasis>application exceptions</emphasis> do not cause a rollback by default, but they do if <literal>@ApplicationException(rollback=true)</literal> is specified. (An application exception is any checked exception, or any unchecked exception annotated <literal>@ApplicationException</literal>. A system exception is any unchecked exception without an <literal>@ApplicationException</literal> annotation.)"
+msgid ""
+"EJB specifies well-defined rules that let us control whether an exception "
+"immediately marks the current transaction for rollback when it is thrown by "
+"a business method of the bean: <emphasis>system exceptions</emphasis> always "
+"cause a transaction rollback, <emphasis>application exceptions</emphasis> do "
+"not cause a rollback by default, but they do if "
+"<literal>@ApplicationException(rollback=true)</literal> is specified. (An "
+"application exception is any checked exception, or any unchecked exception "
+"annotated <literal>@ApplicationException</literal>. A system exception is "
+"any unchecked exception without an <literal>@ApplicationException</literal> "
+"annotation.)"
msgstr ""
#. Tag: para
#: Events.xml:692
#, no-c-format
-msgid "Note that there is a difference between marking a transaction for rollback, and actually rolling it back. The exception rules say that the transaction should be marked rollback only, but it may still be active after the exception is thrown."
+msgid ""
+"Note that there is a difference between marking a transaction for rollback, "
+"and actually rolling it back. The exception rules say that the transaction "
+"should be marked rollback only, but it may still be active after the "
+"exception is thrown."
msgstr ""
#. Tag: para
#: Events.xml:699
#, no-c-format
-msgid "Seam applies the EJB 3.0 exception rollback rules also to Seam JavaBean components."
+msgid ""
+"Seam applies the EJB 3.0 exception rollback rules also to Seam JavaBean "
+"components."
msgstr ""
#. Tag: para
#: Events.xml:704
#, no-c-format
-msgid "But these rules only apply in the Seam component layer. What about an exception that is uncaught and propagates out of the Seam component layer, and out of the JSF layer? Well, it is always wrong to leave a dangling transaction open, so Seam rolls back any active transaction when an exception occurs and is uncaught in the Seam component layer."
+msgid ""
+"But these rules only apply in the Seam component layer. What about an "
+"exception that is uncaught and propagates out of the Seam component layer, "
+"and out of the JSF layer? Well, it is always wrong to leave a dangling "
+"transaction open, so Seam rolls back any active transaction when an "
+"exception occurs and is uncaught in the Seam component layer."
msgstr ""
#. Tag: title
@@ -1575,7 +1913,9 @@
#. Tag: para
#: Events.xml:716
#, no-c-format
-msgid "To enable Seam's exception handling, we need to make sure we have the master servlet filter declared in <literal>web.xml</literal>:"
+msgid ""
+"To enable Seam's exception handling, we need to make sure we have the master "
+"servlet filter declared in <literal>web.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -1605,7 +1945,10 @@
#. Tag: para
#: Events.xml:723
#, no-c-format
-msgid "You need to disable Facelets development mode in <literal>web.xml</literal> and Seam debug mode in <literal>components.xml</literal> if you want your exception handlers to fire."
+msgid ""
+"You need to disable Facelets development mode in <literal>web.xml</literal> "
+"and Seam debug mode in <literal>components.xml</literal> if you want your "
+"exception handlers to fire."
msgstr ""
#. Tag: title
@@ -1617,7 +1960,11 @@
#. Tag: para
#: Events.xml:734
#, no-c-format
-msgid "The following exception results in a HTTP 404 error whenever it propagates out of the Seam component layer. It does not roll back the current transaction immediately when thrown, but the transaction will be rolled back if it the exception is not caught by another Seam component."
+msgid ""
+"The following exception results in a HTTP 404 error whenever it propagates "
+"out of the Seam component layer. It does not roll back the current "
+"transaction immediately when thrown, but the transaction will be rolled back "
+"if it the exception is not caught by another Seam component."
msgstr ""
#. Tag: programlisting
@@ -1633,7 +1980,10 @@
#. Tag: para
#: Events.xml:743
#, no-c-format
-msgid "This exception results in a browser redirect whenever it propagates out of the Seam component layer. It also ends the current conversation. It causes an immediate rollback of the current transaction."
+msgid ""
+"This exception results in a browser redirect whenever it propagates out of "
+"the Seam component layer. It also ends the current conversation. It causes "
+"an immediate rollback of the current transaction."
msgstr ""
#. Tag: programlisting
@@ -1642,28 +1992,37 @@
msgid ""
"<![CDATA[@Redirect(viewId=\"/failure.xhtml\", end=true)\n"
"@ApplicationException(rollback=true)\n"
-"public class UnrecoverableApplicationException extends RuntimeException { ... }]]>"
+"public class UnrecoverableApplicationException extends RuntimeException "
+"{ ... }]]>"
msgstr ""
"<![CDATA[@Redirect(viewId=\"/failure.xhtml\", end=true)\n"
"@ApplicationException(rollback=true)\n"
-"public class UnrecoverableApplicationException extends RuntimeException { ... }]]>"
+"public class UnrecoverableApplicationException extends RuntimeException "
+"{ ... }]]>"
#. Tag: note
#: Events.xml:751
#, no-c-format
-msgid "It is important to note that Seam cannot handle exceptions that occur during JSF's RENDER_RESPONSE phase, as it is not possible to perform a redirect once the response has started being written to."
+msgid ""
+"It is important to note that Seam cannot handle exceptions that occur during "
+"JSF's RENDER_RESPONSE phase, as it is not possible to perform a redirect "
+"once the response has started being written to."
msgstr ""
#. Tag: para
#: Events.xml:757
#, no-c-format
-msgid "You can also use EL to specify the <literal>viewId</literal> to redirect to."
+msgid ""
+"You can also use EL to specify the <literal>viewId</literal> to redirect to."
msgstr ""
#. Tag: para
#: Events.xml:761
#, no-c-format
-msgid "This exception results in a redirect, along with a message to the user, when it propagates out of the Seam component layer. It also immediately rolls back the current transaction."
+msgid ""
+"This exception results in a redirect, along with a message to the user, when "
+"it propagates out of the Seam component layer. It also immediately rolls "
+"back the current transaction."
msgstr ""
#. Tag: programlisting
@@ -1685,7 +2044,10 @@
#. Tag: para
#: Events.xml:774
#, no-c-format
-msgid "Since we can't add annotations to all the exception classes we are interested in, Seam also lets us specify this functionality in <literal>pages.xml</literal>."
+msgid ""
+"Since we can't add annotations to all the exception classes we are "
+"interested in, Seam also lets us specify this functionality in "
+"<literal>pages.xml</literal>."
msgstr ""
#. Tag: programlisting
@@ -1739,19 +2101,25 @@
#. Tag: para
#: Events.xml:781
#, no-c-format
-msgid "The last <literal><exception></literal> declaration does not specify a class, and is a catch-all for any exception for which handling is not otherwise specified via annotations or in <literal>pages.xml</literal>."
+msgid ""
+"The last <literal><exception></literal> declaration does not specify a "
+"class, and is a catch-all for any exception for which handling is not "
+"otherwise specified via annotations or in <literal>pages.xml</literal>."
msgstr ""
#. Tag: para
#: Events.xml:787
#, no-c-format
-msgid "You can also use EL to specify the <literal>view-id</literal> to redirect to."
+msgid ""
+"You can also use EL to specify the <literal>view-id</literal> to redirect to."
msgstr ""
#. Tag: para
#: Events.xml:791
#, no-c-format
-msgid "You can also access the handled exception instance through EL, Seam places it in the conversation context, e.g. to access the message of the exception:"
+msgid ""
+"You can also access the handled exception instance through EL, Seam places "
+"it in the conversation context, e.g. to access the message of the exception:"
msgstr ""
#. Tag: programlisting
@@ -1766,7 +2134,8 @@
" <exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message severity=\"WARN\">#{org.jboss.seam.handledException.message}</message>\n"
+" <message severity=\"WARN\">#{org.jboss.seam.handledException."
+"message}</message>\n"
" </redirect>\n"
" </exception>\n"
"\n"
@@ -1780,7 +2149,8 @@
" <exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message severity=\"WARN\">#{org.jboss.seam.handledException.message}</message>\n"
+" <message severity=\"WARN\">#{org.jboss.seam.handledException."
+"message}</message>\n"
" </redirect>\n"
" </exception>\n"
"\n"
@@ -1789,7 +2159,11 @@
#. Tag: para
#: Events.xml:798
#, no-c-format
-msgid "<literal>org.jboss.seam.handledException</literal> holds the nested exception that was actually handled by an exception handler. The outermost (wrapper) exception is also available, as <literal>org.jboss.seam.caughtException</literal>."
+msgid ""
+"<literal>org.jboss.seam.handledException</literal> holds the nested "
+"exception that was actually handled by an exception handler. The outermost "
+"(wrapper) exception is also available, as <literal>org.jboss.seam."
+"caughtException</literal>."
msgstr ""
#. Tag: title
@@ -1801,51 +2175,74 @@
#. Tag: para
#: Events.xml:807
#, no-c-format
-msgid "For the exception handlers defined in <literal>pages.xml</literal>, it is possible to declare the logging level at which the exception will be logged, or to even suppress the exception being logged altogether. The attributes <literal>log</literal> and <literal>logLevel</literal> can be used to control exception logging. By setting <literal>log=\"false\"</literal> as per the following example, then no log message will be generated when the specified exception occurs:"
+msgid ""
+"For the exception handlers defined in <literal>pages.xml</literal>, it is "
+"possible to declare the logging level at which the exception will be logged, "
+"or to even suppress the exception being logged altogether. The attributes "
+"<literal>log</literal> and <literal>logLevel</literal> can be used to "
+"control exception logging. By setting <literal>log=\"false\"</literal> as "
+"per the following example, then no log message will be generated when the "
+"specified exception occurs:"
msgstr ""
#. Tag: programlisting
#: Events.xml:816
#, no-c-format
msgid ""
-"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" log=\"false\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException"
+"\" log=\"false\">\n"
" <redirect view-id=\"/register.xhtml\">\n"
-" <message severity=\"warn\">You must be a member to use this feature</message>\n"
+" <message severity=\"warn\">You must be a member to use this "
+"feature</message>\n"
" </redirect>\n"
" </exception>]]>"
msgstr ""
-"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" log=\"false\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException"
+"\" log=\"false\">\n"
" <redirect view-id=\"/register.xhtml\">\n"
-" <message severity=\"warn\">You must be a member to use this feature</message>\n"
+" <message severity=\"warn\">You must be a member to use this "
+"feature</message>\n"
" </redirect>\n"
" </exception>]]>"
#. Tag: para
#: Events.xml:818
#, no-c-format
-msgid "If the <literal>log</literal> attribute is not specified, then it defaults to <literal>true</literal> (i.e. the exception will be logged). Alternatively, you can specify the <literal>logLevel</literal> to control at which log level the exception will be logged:"
+msgid ""
+"If the <literal>log</literal> attribute is not specified, then it defaults "
+"to <literal>true</literal> (i.e. the exception will be logged). "
+"Alternatively, you can specify the <literal>logLevel</literal> to control at "
+"which log level the exception will be logged:"
msgstr ""
#. Tag: programlisting
#: Events.xml:824
#, no-c-format
msgid ""
-"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" logLevel=\"info\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException"
+"\" logLevel=\"info\">\n"
" <redirect view-id=\"/register.xhtml\">\n"
-" <message severity=\"warn\">You must be a member to use this feature</message>\n"
+" <message severity=\"warn\">You must be a member to use this "
+"feature</message>\n"
" </redirect>\n"
" </exception>]]>"
msgstr ""
-"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException\" logLevel=\"info\">\n"
+"<![CDATA[ <exception class=\"org.jboss.seam.security.NotLoggedInException"
+"\" logLevel=\"info\">\n"
" <redirect view-id=\"/register.xhtml\">\n"
-" <message severity=\"warn\">You must be a member to use this feature</message>\n"
+" <message severity=\"warn\">You must be a member to use this "
+"feature</message>\n"
" </redirect>\n"
" </exception>]]>"
#. Tag: para
#: Events.xml:826
#, no-c-format
-msgid "The acceptable values for <literal>logLevel</literal> are: <literal>fatal, error, warn, info, debug</literal> or <literal>trace</literal>. If the <literal>logLevel</literal> is not specified, or if an invalid value is configured, then it will default to <literal>error</literal>."
+msgid ""
+"The acceptable values for <literal>logLevel</literal> are: <literal>fatal, "
+"error, warn, info, debug</literal> or <literal>trace</literal>. If the "
+"<literal>logLevel</literal> is not specified, or if an invalid value is "
+"configured, then it will default to <literal>error</literal>."
msgstr ""
#. Tag: title
@@ -1873,7 +2270,8 @@
"<exception class=\"javax.persistence.OptimisticLockException\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message>Another user changed the same data, please try again</message>\n"
+" <message>Another user changed the same data, please try again</"
+"message>\n"
" </redirect>\n"
"</exception>]]>"
msgstr ""
@@ -1886,7 +2284,8 @@
"<exception class=\"javax.persistence.OptimisticLockException\">\n"
" <end-conversation/>\n"
" <redirect view-id=\"/error.xhtml\">\n"
-" <message>Another user changed the same data, please try again</message>\n"
+" <message>Another user changed the same data, please try again</"
+"message>\n"
" </redirect>\n"
"</exception>]]>"
@@ -1900,13 +2299,15 @@
#: Events.xml:849
#, no-c-format
msgid ""
-"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException"
+"\">\n"
" <redirect view-id=\"/error.xhtml\">\n"
" <message>Not found</message>\n"
" </redirect>\n"
"</exception>]]>"
msgstr ""
-"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.framework.EntityNotFoundException"
+"\">\n"
" <redirect view-id=\"/error.xhtml\">\n"
" <message>Not found</message>\n"
" </redirect>\n"
@@ -1922,7 +2323,8 @@
#: Events.xml:855
#, no-c-format
msgid ""
-"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException"
+"\">\n"
" <redirect>\n"
" <message>You don't have permission to do this</message>\n"
" </redirect>\n"
@@ -1934,7 +2336,8 @@
" </redirect>\n"
"</exception>]]>"
msgstr ""
-"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException\">\n"
+"<![CDATA[<exception class=\"org.jboss.seam.security.AuthorizationException"
+"\">\n"
" <redirect>\n"
" <message>You don't have permission to do this</message>\n"
" </redirect>\n"
@@ -1971,7 +2374,11 @@
#. Tag: para
#: Events.xml:863
#, no-c-format
-msgid "A <literal>ViewExpiredException</literal> occurs if the user posts back to a page once their session has expired. <literal>no-conversation-view-id</literal> and <literal>conversation-required</literal> give you finer grained control over session expiration if you are inside a conversation."
+msgid ""
+"A <literal>ViewExpiredException</literal> occurs if the user posts back to a "
+"page once their session has expired. <literal>no-conversation-view-id</"
+"literal> and <literal>conversation-required</literal> give you finer grained "
+"control over session expiration if you are inside a conversation."
msgstr ""
#. Tag: title
@@ -1983,12 +2390,20 @@
#. Tag: para
#: Events.xml:875
#, no-c-format
-msgid "When specified as the attribute of a <literal>page</literal> element in <literal>pages.xml</literal>, this setting controls whether a page requires an active long-running or nested conversation before being rendered. If there is not an active long-running or nested conversation when trying to access the page, you will be redirected to the <literal>no-conversation-view-id</literal> view (which is specified in the root <literal>pages</literal> element) instead."
+msgid ""
+"When specified as the attribute of a <literal>page</literal> element in "
+"<literal>pages.xml</literal>, this setting controls whether a page requires "
+"an active long-running or nested conversation before being rendered. If "
+"there is not an active long-running or nested conversation when trying to "
+"access the page, you will be redirected to the <literal>no-conversation-view-"
+"id</literal> view (which is specified in the root <literal>pages</literal> "
+"element) instead."
msgstr ""
#. Tag: programlisting
#: Events.xml:883
#, no-c-format
-msgid "<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
-msgstr "<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
-
+msgid ""
+"<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
+msgstr ""
+"<![CDATA[ <page view-id=\"/foo.xhtml\" conversation-required=\"true\"/>]]>"
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Excel.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Excel.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Excel.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: Seam_Reference_Guide\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-12-04 00:58+0000\n"
-"PO-Revision-Date: 2009-01-16 19:43+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:17+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -220,145 +220,145 @@
#. Tag: para
#: Excel.xml:117
#, no-c-format
-msgid "<literal>type</literal> —Defines which export module to be used. The value is a string and can be either \"jxl\" or \"csv\". The default is \"jxl\"."
+msgid "<literal>type</literal> — Defines which export module to be used. The value is a string and can be either \"jxl\" or \"csv\". The default is \"jxl\"."
msgstr ""
#. Tag: para
#: Excel.xml:125
#, no-c-format
-msgid "<literal>templateURI</literal> —A template that should be used as a basis for the workbook. The value is a string (URI)."
-msgstr ""
+msgid "<literal>templateURI</literal> — A template that should be used as a basis for the workbook. The value is a string (URI)."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:132
#, no-c-format
-msgid "<literal>arrayGrowSize</literal> —The amount of memory by which to increase the amount of memory allocated to storing the workbook data. For processeses reading many small workbooks inside a WAS it might be necessary to reduce the default size Default value is 1 megabyte. The value is a number (bytes)."
+msgid "<literal>arrayGrowSize</literal> — The amount of memory by which to increase the amount of memory allocated to storing the workbook data. For processeses reading many small workbooks inside a WAS it might be necessary to reduce the default size Default value is 1 megabyte. The value is a number (bytes)."
msgstr ""
#. Tag: para
#: Excel.xml:143
#, no-c-format
-msgid "<literal>autoFilterDisabled</literal> —Should autofiltering be disabled?. The value is a boolean."
-msgstr ""
+msgid "<literal>autoFilterDisabled</literal> — Should autofiltering be disabled?. The value is a boolean."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:150
#, no-c-format
-msgid "<literal>cellValidationDisabled</literal> —Shoule cell validation be ignored? The value is a boolean."
-msgstr ""
+msgid "<literal>cellValidationDisabled</literal> — Should cell validation be ignored? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:157
#, no-c-format
-msgid "<literal>characterSet</literal> —The character set. This is only used when the spreadsheet is read, and has no effect when the spreadsheet is written. The value is a string (character set encoding)."
+msgid "<literal>characterSet</literal> — The character set. This is only used when the spreadsheet is read, and has no effect when the spreadsheet is written. The value is a string (character set encoding)."
msgstr ""
#. Tag: para
#: Excel.xml:166
#, no-c-format
-msgid "<literal>drawingsDisabled</literal> —Should drawings be disabled? The value is a boolean."
-msgstr ""
+msgid "<literal>drawingsDisabled</literal> — Should drawings be disabled? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:173
#, no-c-format
-msgid "<literal>excelDisplayLanguage</literal> —The language in which the generated file will display. The value is a string (two character ISO 3166 country code)."
+msgid "<literal>excelDisplayLanguage</literal> — The language in which the generated file will display. The value is a string (two character ISO 3166 country code)."
msgstr ""
#. Tag: para
#: Excel.xml:181
#, no-c-format
-msgid "<literal>excelRegionalSettings</literal> —The regional settings for the generated excel file. The value is a string (two character ISO 3166 country code)."
-msgstr ""
+msgid "<literal>excelRegionalSettings</literal> — The regional settings for the generated excel file. The value is a string (two character ISO 3166 country code)."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:189
#, no-c-format
-msgid "<literal>formulaAdjust</literal> —Should formulas be adjusted? The value is a boolean."
-msgstr ""
+msgid "<literal>formulaAdjust</literal> — Should formulas be adjusted? The value is a boolean."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:196
#, no-c-format
-msgid "<literal>gcDisabled</literal> —Should garbage collection be disabled? The value is a boolean."
-msgstr ""
+msgid "<literal>gcDisabled</literal> — Should garbage collection be disabled? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:203
#, no-c-format
-msgid "<literal>ignoreBlanks</literal> —Should blanks be ignored? The value is a boolean."
-msgstr ""
+msgid "<literal>ignoreBlanks</literal> — Should blanks be ignored? The value is a boolean."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:210
#, no-c-format
-msgid "<literal>initialFileSize</literal> —The initial amount of memory allocated to store the workbook data when reading a worksheet. For processeses reading many small workbooks inside a WAS it might be necessary to reduce the default size Default value is 5 megabytes. The value is a number (bytes)."
+msgid "<literal>initialFileSize</literal> — The initial amount of memory allocated to store the workbook data when reading a worksheet. For processeses reading many small workbooks inside a WAS it might be necessary to reduce the default size Default value is 5 megabytes. The value is a number (bytes)."
msgstr ""
#. Tag: para
#: Excel.xml:221
#, no-c-format
-msgid "<literal>locale</literal> —The locale used by JExcelApi to generate the spreadsheet. Setting this value has no effect on the language or region of the generated excel file. The value is a string."
+msgid "<literal>locale</literal> — The locale used by JExcelApi to generate the spreadsheet. Setting this value has no effect on the language or region of the generated excel file. The value is a string."
msgstr ""
#. Tag: para
#: Excel.xml:230
#, no-c-format
-msgid "<literal>mergedCellCheckingDisabled</literal> —Should merged cell checking be disabled? The value is a boolean."
+msgid "<literal>mergedCellCheckingDisabled</literal> — Should merged cell checking be disabled? The value is a boolean."
msgstr ""
#. Tag: para
#: Excel.xml:237
#, no-c-format
-msgid "<literal>namesDisabled</literal> —Should handling of names be disabled? The value is a boolean."
-msgstr ""
+msgid "<literal>namesDisabled</literal> — Should handling of names be disabled? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:244
#, no-c-format
-msgid "<literal>propertySets</literal> —Should any property sets be enabled (such as macros) to be copied along with the workbook? Leaving this feature enabled will result in the JXL process using more memory. The value is a boolean."
+msgid "<literal>propertySets</literal> — Should any property sets be enabled (such as macros) to be copied along with the workbook? Leaving this feature enabled will result in the JXL process using more memory. The value is a boolean."
msgstr ""
#. Tag: para
#: Excel.xml:254
#, no-c-format
-msgid "<literal>rationalization</literal> —Should the cell formats be rationalized before writing out the sheet? The value is a boolean. Default is true."
+msgid "<literal>rationalization</literal> — Should the cell formats be rationalized before writing out the sheet? The value is a boolean. Default is true."
msgstr ""
#. Tag: para
#: Excel.xml:262
#, no-c-format
-msgid "<literal>supressWarnings</literal> —Should warnings be suppressed?. Due to the change in logging in version 2.4, this will now set the warning behaviour across the JVM (depending on the type of logger used). The value is a boolean."
+msgid "<literal>supressWarnings</literal> — Should warnings be suppressed?. Due to the change in logging in version 2.4, this will now set the warning behaviour across the JVM (depending on the type of logger used). The value is a boolean."
msgstr ""
#. Tag: para
#: Excel.xml:272
#, no-c-format
-msgid "<literal> temporaryFileDuringWriteDirectory </literal> —Used in conjunction with the <literal>useTemporaryFileDuringWrite</literal> setting to set the target directory for the temporary files. This value can be NULL, in which case the normal system default temporary directory is used instead. The value is a string (the directory to which temporary files should be written)."
+msgid "<literal> temporaryFileDuringWriteDirectory </literal> — Used in conjunction with the <literal>useTemporaryFileDuringWrite</literal> setting to set the target directory for the temporary files. This value can be NULL, in which case the normal system default temporary directory is used instead. The value is a string (the directory to which temporary files should be written)."
msgstr ""
#. Tag: para
#: Excel.xml:287
#, no-c-format
-msgid "<literal>useTemporaryFileDuringWrite</literal> —Should a temporary file is used during the generation of the workbook. If not set, the workbook will take place entirely in memory. Setting this flag involves an assessment of the trade-offs between memory usage and performance. The value is a boolean."
+msgid "<literal>useTemporaryFileDuringWrite</literal> — Should a temporary file is used during the generation of the workbook. If not set, the workbook will take place entirely in memory. Setting this flag involves an assessment of the trade-offs between memory usage and performance. The value is a boolean."
msgstr ""
#. Tag: para
#: Excel.xml:298
#, no-c-format
-msgid "<literal>workbookProtected</literal> —Should the workbook be protected? The value is a boolean."
-msgstr ""
+msgid "<literal>workbookProtected</literal> — Should the workbook be protected? The value is a boolean."
+msgstr "<literal>bottomMargin</literal> — Il margine inferiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:305
#, no-c-format
-msgid "<literal>filename</literal> —The filename to use for the download. The value is a string. Please not that if you map the DocumentServlet to some pattern, this file extension must also match."
+msgid "<literal>filename</literal> — The filename to use for the download. The value is a string. Please not that if you map the DocumentServlet to some pattern, this file extension must also match."
msgstr ""
#. Tag: para
#: Excel.xml:313
#, no-c-format
-msgid "<literal>exportKey</literal> —A key under which to store the resulting data in a DocumentData object under the event scope. If used, there is no redirection."
+msgid "<literal>exportKey</literal> — A key under which to store the resulting data in a DocumentData object under the event scope. If used, there is no redirection."
msgstr ""
#. Tag: emphasis
@@ -383,13 +383,13 @@
#. Tag: para
#: Excel.xml:326
#, no-c-format
-msgid "<literal><e:link/></literal> —Zero or more stylesheet links (see <xref linkend=\"excel.fontsandlayout.link\"/> )."
+msgid "<literal><e:link/></literal> — Zero or more stylesheet links (see <xref linkend=\"excel.fontsandlayout.link\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:334
#, no-c-format
-msgid "<literal><e:worksheet/></literal> —Zero or more worksheets (see <xref linkend=\"excel.worksheet\"/> )."
+msgid "<literal><e:worksheet/></literal> — Zero or more worksheets (see <xref linkend=\"excel.worksheet\"/> )."
msgstr ""
#. Tag: emphasis
@@ -498,271 +498,271 @@
#. Tag: para
#: Excel.xml:383
#, no-c-format
-msgid "<literal>value</literal> —An EL-expression to the backing data. The value is a string. The target of this expression is examined for an Iterable. Note that if the target is a Map, the iteration is done over the Map.Entry entrySet(), so you should use a .key or .value to target in your references."
+msgid "<literal>value</literal> — An EL-expression to the backing data. The value is a string. The target of this expression is examined for an Iterable. Note that if the target is a Map, the iteration is done over the Map.Entry entrySet(), so you should use a .key or .value to target in your references."
msgstr ""
#. Tag: para
#: Excel.xml:393
#, no-c-format
-msgid "<literal>var</literal> —The current row iterator variable name that can later be referenced in cell value attributes. The value is a string"
+msgid "<literal>var</literal> — The current row iterator variable name that can later be referenced in cell value attributes. The value is a string"
msgstr ""
#. Tag: para
#: Excel.xml:401
#, no-c-format
-msgid "<literal>name</literal> —The name of the worksheet. The valus is a string. Defaults to Sheet# where # is the worksheet index. If the given worksheet name exists, that sheet is selected. This can be used for merging several data sets into a single worksheet, just define the same name for them (using <literal>startRow</literal> and <literal>startCol</literal> to make sure that they don't occupy the same space)."
+msgid "<literal>name</literal> — The name of the worksheet. The valus is a string. Defaults to Sheet# where # is the worksheet index. If the given worksheet name exists, that sheet is selected. This can be used for merging several data sets into a single worksheet, just define the same name for them (using <literal>startRow</literal> and <literal>startCol</literal> to make sure that they don't occupy the same space)."
msgstr ""
#. Tag: para
#: Excel.xml:418
#, no-c-format
-msgid "<literal>startRow</literal> —Defines the starting row for the data. The value is a number. Used for placing the data in other places than the upper-left corner (especially useful if having multiple data sets for a single worksheet). The defaults is 0."
+msgid "<literal>startRow</literal> — Defines the starting row for the data. The value is a number. Used for placing the data in other places than the upper-left corner (especially useful if having multiple data sets for a single worksheet). The defaults is 0."
msgstr ""
#. Tag: para
#: Excel.xml:428
#, no-c-format
-msgid "<literal>startColumn</literal> —Defines the starting column for the data. The value is a number. Used for placing the data in other places than the upper-left corner (especially useful if having multiple data sets for a single worksheet). The default is 0."
+msgid "<literal>startColumn</literal> — Defines the starting column for the data. The value is a number. Used for placing the data in other places than the upper-left corner (especially useful if having multiple data sets for a single worksheet). The default is 0."
msgstr ""
#. Tag: para
#: Excel.xml:438
#, no-c-format
-msgid "<literal>automaticFormulaCalculation</literal> —Should formulas be automatically calculated? The value is a boolean."
+msgid "<literal>automaticFormulaCalculation</literal> — Should formulas be automatically calculated? The value is a boolean."
msgstr ""
#. Tag: para
#: Excel.xml:445
#, no-c-format
-msgid "<literal>bottomMargin</literal> —The bottom margin. The value is a number (inches)"
-msgstr "<literal>bottomMargin</literal> —Il margine inferiore. Il valore è un numero (pollici)."
+msgid "<literal>bottomMargin</literal> — The bottom margin. The value is a number (inches)"
+msgstr "<literal>bottomMargin</literal> — Il margine inferiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:452
#, no-c-format
-msgid "<literal>copies</literal> —The number of copies. The value is a number."
-msgstr ""
+msgid "<literal>copies</literal> — The number of copies. The value is a number."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:459
#, no-c-format
-msgid "<literal>defaultColumnWidth</literal> —The default column width. The value is a number (characters * 256)."
-msgstr ""
+msgid "<literal>defaultColumnWidth</literal> — The default column width. The value is a number (characters * 256)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:466
#, no-c-format
-msgid "<literal>defaultRowHeight</literal> —The default row height. The value is a number (1/20ths of a point)."
-msgstr ""
+msgid "<literal>defaultRowHeight</literal> — The default row height. The value is a number (1/20ths of a point)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:473
#, no-c-format
-msgid "<literal>displayZeroValues</literal> —Should zero-values be displayed? The value is a boolean."
-msgstr ""
+msgid "<literal>displayZeroValues</literal> — Should zero-values be displayed? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:480
#, no-c-format
-msgid "<literal>fitHeight</literal> —The number of pages vertically that this sheet will be printed into. The value is a number."
-msgstr ""
+msgid "<literal>fitHeight</literal> — The number of pages vertically that this sheet will be printed into. The value is a number."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:487
#, no-c-format
-msgid "<literal>fitToPages</literal> —Should printing be fit to pages? The value is a boolean."
-msgstr ""
+msgid "<literal>fitToPages</literal> — Should printing be fit to pages? The value is a boolean."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:494
#, no-c-format
-msgid "<literal>fitWidth</literal> —The number of pages widthwise which this sheet should be printed into. The value is a number."
-msgstr ""
+msgid "<literal>fitWidth</literal> — The number of pages widthwise which this sheet should be printed into. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:502
#, no-c-format
-msgid "<literal>footerMargin</literal> —The margin for any page footer. The value is a number (inches)."
-msgstr ""
+msgid "<literal>footerMargin</literal> — The margin for any page footer. The value is a number (inches)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:509
#, no-c-format
-msgid "<literal>headerMargin</literal> —The margin for any page headers. The value is a number (inches)."
-msgstr ""
+msgid "<literal>headerMargin</literal> — The margin for any page headers. The value is a number (inches)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:516
#, no-c-format
-msgid "<literal>hidden</literal> —Should the worksheet be hidden? The value is a boolean."
-msgstr ""
+msgid "<literal>hidden</literal> — Should the worksheet be hidden? The value is a boolean."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:523
#, no-c-format
-msgid "<literal>horizontalCentre</literal> —Should the worksheet be centered horizontally? The value is a boolean."
-msgstr ""
+msgid "<literal>horizontalCentre</literal> — Should the worksheet be centered horizontally? The value is a boolean."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:530
#, no-c-format
-msgid "<literal>horizontalFreeze</literal> —The row at which the pane is frozen vertically. The value is a number."
-msgstr ""
+msgid "<literal>horizontalFreeze</literal> — The row at which the pane is frozen vertically. The value is a number."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:537
#, no-c-format
-msgid "<literal>horizontalPrintResolution</literal> —The horizontal print resolution. The value is a number."
-msgstr ""
+msgid "<literal>horizontalPrintResolution</literal> — The horizontal print resolution. The value is a number."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:544
#, no-c-format
-msgid "<literal>leftMargin</literal> —The left margin. The value is a number (inches)."
-msgstr "<literal>leftMargin</literal> —Il margine sinistro. Il valore è un numero (pollici)."
+msgid "<literal>leftMargin</literal> — The left margin. The value is a number (inches)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:551
#, no-c-format
-msgid "<literal>normalMagnification</literal> —The normal magnificaton factor (not zoom or scale factor). The value is a number (percentage)."
-msgstr ""
+msgid "<literal>normalMagnification</literal> — The normal magnificaton factor (not zoom or scale factor). The value is a number (percentage)."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:558
#, no-c-format
-msgid "<literal>orientation</literal> —The paper orientation for printing this sheet. The value is a string that can be either \"landscape\" or \"portrait\"."
-msgstr ""
+msgid "<literal>orientation</literal> — The paper orientation for printing this sheet. The value is a string that can be either \"landscape\" or \"portrait\"."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:566
#, no-c-format
-msgid "<literal>pageBreakPreviewMagnification</literal> —The page break preview magnificaton factor (not zoom or scale factors). the value is a number (percentage)."
+msgid "<literal>pageBreakPreviewMagnification</literal> — The page break preview magnificaton factor (not zoom or scale factors). the value is a number (percentage)."
msgstr ""
#. Tag: para
#: Excel.xml:574
#, no-c-format
-msgid "<literal>pageBreakPreviewMode</literal> —Show page in preview mode? The value is a boolean."
-msgstr ""
+msgid "<literal>pageBreakPreviewMode</literal> — Show page in preview mode? The value is a boolean."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:581
#, no-c-format
-msgid "<literal>pageStart</literal> —The page number at which to commence printing. The value is a number."
-msgstr ""
+msgid "<literal>pageStart</literal> — The page number at which to commence printing. The value is a number."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:588
#, no-c-format
-msgid "<literal>paperSize</literal> —The paper size to be used when printing this sheet. The value is a string that can be one of \"a4\", \"a3\", \"letter\", \"legal\" etc (see <ulink url=\"http://jexcelapi.sourceforge.net/resources/javadocs/current/docs/jxl/format/PaperSize.html\"> jxl.format.PaperSize </ulink> )."
+msgid "<literal>paperSize</literal> — The paper size to be used when printing this sheet. The value is a string that can be one of \"a4\", \"a3\", \"letter\", \"legal\" etc (see <ulink url=\"http://jexcelapi.sourceforge.net/resources/javadocs/current/docs/jxl/format/PaperSize.html\"> jxl.format.PaperSize </ulink> )."
msgstr ""
#. Tag: para
#: Excel.xml:601
#, no-c-format
-msgid "<literal>password</literal> —The password for this sheet. The value is a string."
-msgstr ""
+msgid "<literal>password</literal> — The password for this sheet. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:608
#, no-c-format
-msgid "<literal>passwordHash</literal> —The password hash - used only when copying sheets. The value is a string."
-msgstr ""
+msgid "<literal>passwordHash</literal> — The password hash - used only when copying sheets. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:615
#, no-c-format
-msgid "<literal>printGridLines</literal> —Should grid lines be printed? The value is a boolean."
-msgstr ""
+msgid "<literal>printGridLines</literal> — Should grid lines be printed? The value is a boolean."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:622
#, no-c-format
-msgid "<literal>printHeaders</literal> —Should headers be printed? The value is a boolean."
-msgstr ""
+msgid "<literal>printHeaders</literal> — Should headers be printed? The value is a boolean."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:629
#, no-c-format
-msgid "<literal>sheetProtected</literal> —Should the sheet be protected (read-only)? The value is a boolean."
-msgstr ""
+msgid "<literal>sheetProtected</literal> — Should the sheet be protected (read-only)? The value is a boolean."
+msgstr "<literal>bottomMargin</literal> — Il margine inferiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:636
#, no-c-format
-msgid "<literal>recalculateFormulasBeforeSave</literal> —Should the formulas be re-calculated when the sheet is saved? The value is a boolean. false"
+msgid "<literal>recalculateFormulasBeforeSave</literal> — Should the formulas be re-calculated when the sheet is saved? The value is a boolean. false"
msgstr ""
#. Tag: para
#: Excel.xml:643
#, no-c-format
-msgid "<literal>rightMargin</literal> —The right margin. The value is a number (inches)."
-msgstr "<literal>rightMargin</literal> —Il margine destro. Il valore è un numero (pollici)."
+msgid "<literal>rightMargin</literal> — The right margin. The value is a number (inches)."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:650
#, no-c-format
-msgid "<literal>scaleFactor</literal> —The scale factor for this sheet to be used when printing. The value is a number (percent)."
-msgstr ""
+msgid "<literal>scaleFactor</literal> — The scale factor for this sheet to be used when printing. The value is a number (percent)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:657
#, no-c-format
-msgid "<literal>selected</literal> —Should the sheet be selected when the workbook opens? The value is a boolean."
-msgstr ""
+msgid "<literal>selected</literal> — Should the sheet be selected when the workbook opens? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:664
#, no-c-format
-msgid "<literal>showGridLines</literal> —Should gridlines be shown? The value is a boolean."
-msgstr ""
+msgid "<literal>showGridLines</literal> — Should gridlines be shown? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:671
#, no-c-format
-msgid "<literal>topMargin</literal> —The top margin. The value is a number (inches)."
-msgstr "<literal>topMargin</literal> —Il margine superiore. Il valore è un numero (pollici)."
+msgid "<literal>topMargin</literal> — The top margin. The value is a number (inches)."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:678
#, no-c-format
-msgid "<literal>verticalCentre</literal> —Center verically? The value is a boolean."
-msgstr ""
+msgid "<literal>verticalCentre</literal> — Center verically? The value is a boolean."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:684
#, no-c-format
-msgid "<literal>verticalFreeze</literal> —The row at which the pane is frozen vertically. The value is a number."
-msgstr ""
+msgid "<literal>verticalFreeze</literal> — The row at which the pane is frozen vertically. The value is a number."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:691
#, no-c-format
-msgid "<literal>verticalPrintResolution</literal> —The vertical print resolution. The value is a number."
-msgstr ""
+msgid "<literal>verticalPrintResolution</literal> — The vertical print resolution. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:698
#, no-c-format
-msgid "<literal>zoomFactor</literal> —T zoom factor. Do not confuse zoom factor (which relates to the on screen view) with scale factor (which refers to the scale factor when printing). The value is a number (percentage."
+msgid "<literal>zoomFactor</literal> — T zoom factor. Do not confuse zoom factor (which relates to the on screen view) with scale factor (which refers to the scale factor when printing). The value is a number (percentage."
msgstr ""
#. Tag: para
#: Excel.xml:712
#, no-c-format
-msgid "<literal><e:printArea/></literal> —Zero or more print area definitions (see <xref linkend=\"excel.printareatitles\"/> )."
+msgid "<literal><e:printArea/></literal> — Zero or more print area definitions (see <xref linkend=\"excel.printareatitles\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:720
#, no-c-format
-msgid "<literal><e:printTitle/></literal> —Zero or more print title definitions (see <xref linkend=\"excel.printareatitles\"/> )."
+msgid "<literal><e:printTitle/></literal> — Zero or more print title definitions (see <xref linkend=\"excel.printareatitles\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:728
#, no-c-format
-msgid "<literal><e:headerFooter/></literal> —Zero or more header/footer definitions ((see <xref linkend=\"excel.headersfooters\"/> ))."
+msgid "<literal><e:headerFooter/></literal> — Zero or more header/footer definitions ((see <xref linkend=\"excel.headersfooters\"/> ))."
msgstr ""
#. Tag: para
@@ -774,13 +774,13 @@
#. Tag: para
#: Excel.xml:749
#, no-c-format
-msgid "<literal>header</literal>—Contents that will be placed at the top of the data block, above the column headers (if any)"
+msgid "<literal>header</literal>— Contents that will be placed at the top of the data block, above the column headers (if any)"
msgstr ""
#. Tag: para
#: Excel.xml:756
#, no-c-format
-msgid "<literal>footer</literal>—Contents that will be placed at the bottom of the data block, below the column footers (if any)"
+msgid "<literal>footer</literal>— Contents that will be placed at the bottom of the data block, below the column footers (if any)"
msgstr ""
#. Tag: programlisting
@@ -840,37 +840,37 @@
#. Tag: para
#: Excel.xml:806
#, no-c-format
-msgid "<literal><e:cell/></literal> —Zero or more cells (see <xref linkend=\"excel.cells\"/> )."
+msgid "<literal><e:cell/></literal> — Zero or more cells (see <xref linkend=\"excel.cells\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:814
#, no-c-format
-msgid "<literal><e:formula/></literal> —Zero or more formulas (see <xref linkend=\"excel.formulas\"/> )."
+msgid "<literal><e:formula/></literal> — Zero or more formulas (see <xref linkend=\"excel.formulas\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:822
#, no-c-format
-msgid "<literal><e:image/></literal> —Zero or more images (see <xref linkend=\"excel.images\"/> )."
+msgid "<literal><e:image/></literal> — Zero or more images (see <xref linkend=\"excel.images\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:830
#, no-c-format
-msgid "<literal><e:hyperLink/></literal> —Zero or more hyperlinks (see <xref linkend=\"excel.hyperlinks\"/> )."
+msgid "<literal><e:hyperLink/></literal> — Zero or more hyperlinks (see <xref linkend=\"excel.hyperlinks\"/> )."
msgstr ""
#. Tag: para
#: Excel.xml:843
#, no-c-format
-msgid "<literal>header</literal> —This facet can/will contain one <literal><e:cell></literal> , <literal><e:formula></literal> , <literal><e:image></literal> or <literal><e:hyperLink></literal> that will be used as header for the column."
+msgid "<literal>header</literal> — This facet can/will contain one <literal><e:cell></literal> , <literal><e:formula></literal> , <literal><e:image></literal> or <literal><e:hyperLink></literal> that will be used as header for the column."
msgstr ""
#. Tag: para
#: Excel.xml:857
#, no-c-format
-msgid "<literal>footer</literal> —This facet can/will contain one <literal><e:cell></literal> , <literal><e:formula></literal> , <literal><e:image></literal> or <literal><e:hyperLink></literal> that will be used as footer for the column."
+msgid "<literal>footer</literal> — This facet can/will contain one <literal><e:cell></literal> , <literal><e:formula></literal> , <literal><e:image></literal> or <literal><e:hyperLink></literal> that will be used as footer for the column."
msgstr ""
#. Tag: programlisting
@@ -931,38 +931,38 @@
#. Tag: para
#: Excel.xml:907
#, no-c-format
-msgid "<literal>column</literal> —The column where to place the cell. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>column</literal> — The column where to place the cell. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:915
#, no-c-format
-msgid "<literal>row</literal> —The row where to place the cell. The default is the internal counter. The value is number. Note that the value is 0-based."
+msgid "<literal>row</literal> — The row where to place the cell. The default is the internal counter. The value is number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:923
#, no-c-format
-msgid "<literal>value</literal> —The value to display. Usually an EL-expression referencing the var-attribute of the containing datatable. The value is a string."
+msgid "<literal>value</literal> — The value to display. Usually an EL-expression referencing the var-attribute of the containing datatable. The value is a string."
msgstr ""
#. Tag: para
#: Excel.xml:931
#, no-c-format
-msgid "<literal>comment</literal> —A comment to add to the cell. The value is a string."
-msgstr ""
+msgid "<literal>comment</literal> — A comment to add to the cell. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:938
#, no-c-format
-msgid "<literal>commentHeight</literal> —The height of the comment. The value is a number (in pixels)."
-msgstr ""
+msgid "<literal>commentHeight</literal> — The height of the comment. The value is a number (in pixels)."
+msgstr "<literal>rightMargin</literal> — Il margine destro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:945
#, no-c-format
-msgid "<literal>commentWidth</literal> —A width of the comment. The value is a number (in pixels)."
-msgstr ""
+msgid "<literal>commentWidth</literal> — A width of the comment. The value is a number (in pixels)."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:958
@@ -1021,20 +1021,20 @@
#. Tag: para
#: Excel.xml:1005
#, no-c-format
-msgid "<literal>value</literal> —The limit (or lower limit where applicable) of the validation. The value is a number."
-msgstr ""
+msgid "<literal>value</literal> — The limit (or lower limit where applicable) of the validation. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1013
#, no-c-format
-msgid "<literal>value2</literal> —The upper limit (where applicable) of the validation. The value is a number."
-msgstr ""
+msgid "<literal>value2</literal> — The upper limit (where applicable) of the validation. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1020
#, no-c-format
-msgid "<literal>condition</literal> —The validation condition. The value is a string."
-msgstr ""
+msgid "<literal>condition</literal> — The validation condition. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1026
@@ -1123,26 +1123,26 @@
#. Tag: para
#: Excel.xml:1127
#, no-c-format
-msgid "<literal>startColumn</literal> —The starting column of the range of values to validate against. The value is a number."
-msgstr ""
+msgid "<literal>startColumn</literal> — The starting column of the range of values to validate against. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1135
#, no-c-format
-msgid "<literal>startRow</literal> —The starting row of the range of values to validate against. The value is a number."
-msgstr ""
+msgid "<literal>startRow</literal> — The starting row of the range of values to validate against. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1142
#, no-c-format
-msgid "<literal>endColumn</literal> —The ending column of the range of values to validate against. The value is a number."
-msgstr ""
+msgid "<literal>endColumn</literal> — The ending column of the range of values to validate against. The value is a number."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1149
#, no-c-format
-msgid "<literal>endRow</literal> —The ending row of the range of values to validate against. The value is a number."
-msgstr ""
+msgid "<literal>endRow</literal> — The ending row of the range of values to validate against. The value is a number."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: programlisting
#: Excel.xml:1181
@@ -1207,8 +1207,8 @@
#. Tag: para
#: Excel.xml:1256
#, no-c-format
-msgid "<literal>value</literal> —A values to validate against."
-msgstr "<literal>value</literal> —Un valore da validare."
+msgid "<literal>value</literal> — A values to validate against."
+msgstr "<literal>value</literal> — Un valore da validare."
#. Tag: programlisting
#: Excel.xml:1287
@@ -1385,32 +1385,32 @@
#. Tag: para
#: Excel.xml:1397
#, no-c-format
-msgid "<literal>startColumn</literal> —The starting column of the image. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>startColumn</literal> — The starting column of the image. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1405
#, no-c-format
-msgid "<literal>startRow</literal> —The starting row of the image. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>startRow</literal> — The starting row of the image. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1413
#, no-c-format
-msgid "<literal>columnSpan</literal> —The column span of the image. The default is one resulting in the default width of the image. The value is a float."
+msgid "<literal>columnSpan</literal> — The column span of the image. The default is one resulting in the default width of the image. The value is a float."
msgstr ""
#. Tag: para
#: Excel.xml:1421
#, no-c-format
-msgid "<literal>rowSpan</literal> —The row span of the image. The default is the one resulting in the default height of the image. The value is a float."
+msgid "<literal>rowSpan</literal> — The row span of the image. The default is the one resulting in the default height of the image. The value is a float."
msgstr ""
#. Tag: para
#: Excel.xml:1429
#, no-c-format
-msgid "<literal>URI</literal> —The URI to the image. The value is a string."
-msgstr ""
+msgid "<literal>URI</literal> — The URI to the image. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: programlisting
#: Excel.xml:1461
@@ -1461,38 +1461,38 @@
#. Tag: para
#: Excel.xml:1491
#, no-c-format
-msgid "<literal>startColumn</literal> —The starting column of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>startColumn</literal> — The starting column of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1499
#, no-c-format
-msgid "<literal>startRow</literal> —The starting row of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>startRow</literal> — The starting row of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1507
#, no-c-format
-msgid "<literal>endColumn</literal> —The ending column of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>endColumn</literal> — The ending column of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1515
#, no-c-format
-msgid "<literal>endRow</literal> —The ending row of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
+msgid "<literal>endRow</literal> — The ending row of the hyperlink. The default is the internal counter. The value is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1523
#, no-c-format
-msgid "<literal>URL</literal> —The URL to link. The value is a string."
-msgstr ""
+msgid "<literal>URL</literal> — The URL to link. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: para
#: Excel.xml:1529
#, no-c-format
-msgid "<literal>description</literal> —The description of the link. The value is a string."
-msgstr "<literal>description</literal> —La descrizione del link. Il valore è una stringa."
+msgid "<literal>description</literal> — The description of the link. The value is a string."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: programlisting
#: Excel.xml:1561
@@ -1546,21 +1546,21 @@
#: Excel.xml:1609
#: Excel.xml:1672
#, no-c-format
-msgid "<literal>left</literal> —The contents of the left header/footer part."
-msgstr "<literal>left</literal> — i contenuti della parte sinistra di intestazione/pié di pagina."
+msgid "<literal>left</literal> — The contents of the left header/footer part."
+msgstr "<literal>left</literal> — I contenuti della parte sinistra di intestazione/pié di pagina."
#. Tag: para
#: Excel.xml:1616
#: Excel.xml:1679
#, no-c-format
-msgid "<literal>center</literal> —The contents of the center header/footer part."
+msgid "<literal>center</literal> — The contents of the center header/footer part."
msgstr "<literal>center</literal> — i contenuti della parte centrale di intestazione/pié di pagina."
#. Tag: para
#: Excel.xml:1623
#: Excel.xml:1686
#, no-c-format
-msgid "<literal>right</literal> —The contents of the right header/footer part."
+msgid "<literal>right</literal> — The contents of the right header/footer part."
msgstr "<literal>right</literal> — i contenuti della parte destra di intestazione/pié di pagina."
#. Tag: literal
@@ -1843,25 +1843,25 @@
#. Tag: para
#: Excel.xml:1902
#, no-c-format
-msgid "<literal>firstColumn</literal> —The column of the top-left corner of the area. The parameter is a number. Note that the value is 0-based."
+msgid "<literal>firstColumn</literal> — The column of the top-left corner of the area. The parameter is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1910
#, no-c-format
-msgid "<literal>firstRow</literal> —The row of the top-left corner of the area. The parameter is a number. Note that the value is 0-based."
+msgid "<literal>firstRow</literal> — The row of the top-left corner of the area. The parameter is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1918
#, no-c-format
-msgid "<literal>lastColumn</literal> —The column of the bottom-right corner of the area. The parameter is a number. Note that the value is 0-based."
+msgid "<literal>lastColumn</literal> — The column of the bottom-right corner of the area. The parameter is a number. Note that the value is 0-based."
msgstr ""
#. Tag: para
#: Excel.xml:1926
#, no-c-format
-msgid "<literal>lastRow</literal> —The row of the bottom-right corner of the area. The parameter is a number. Note that the value is 0-based."
+msgid "<literal>lastRow</literal> — The row of the bottom-right corner of the area. The parameter is a number. Note that the value is 0-based."
msgstr ""
#. Tag: programlisting
@@ -1930,21 +1930,21 @@
#. Tag: para
#: Excel.xml:1990
#, no-c-format
-msgid "<literal>startRow</literal> —The row to start the grouping at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>startRow</literal> — The row to start the grouping at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:1998
#, no-c-format
-msgid "<literal>endRow</literal> —The row to end the grouping at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>endRow</literal> — The row to end the grouping at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:2006
#: Excel.xml:2071
#, no-c-format
-msgid "<literal>collapse</literal> —Should the grouping be collapsed initially? The value is a boolean."
-msgstr ""
+msgid "<literal>collapse</literal> — Should the grouping be collapsed initially? The value is a boolean."
+msgstr "<literal>description</literal> — La descrizione del link. Il valore è una stringa."
#. Tag: emphasis
#: Excel.xml:2014
@@ -1964,14 +1964,14 @@
#. Tag: para
#: Excel.xml:2055
#, no-c-format
-msgid "<literal>startColumn</literal> —The column to start the grouping at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>startColumn</literal> — The column to start the grouping at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:2063
#, no-c-format
-msgid "<literal>endColumn</literal> —The column to end the grouping at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>endColumn</literal> — The column to end the grouping at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: programlisting
#: Excel.xml:2104
@@ -2022,8 +2022,8 @@
#. Tag: para
#: Excel.xml:2131
#, no-c-format
-msgid "<literal>row</literal> —The row to break at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>row</literal> — The row to break at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: programlisting
#: Excel.xml:2163
@@ -2072,26 +2072,26 @@
#. Tag: para
#: Excel.xml:2186
#, no-c-format
-msgid "<literal>startRow</literal> —The row to start the merging from. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>startRow</literal> — The row to start the merging from. The value is a number. Note that the value is 0-based."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:2194
#, no-c-format
-msgid "<literal>startColumn</literal> —The column to start the merging from. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>startColumn</literal> — The column to start the merging from. The value is a number. Note that the value is 0-based."
+msgstr "<literal>topMargin</literal> — Il margine superiore. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:2202
#, no-c-format
-msgid "<literal>endRow</literal> —The row to end the merging at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>endRow</literal> — The row to end the merging at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: para
#: Excel.xml:2209
#, no-c-format
-msgid "<literal>endColumn</literal> —The column to end the merging at. The value is a number. Note that the value is 0-based."
-msgstr ""
+msgid "<literal>endColumn</literal> — The column to end the merging at. The value is a number. Note that the value is 0-based."
+msgstr "<literal>leftMargin</literal> — Il margine sinistro. Il valore è un numero (pollici)."
#. Tag: programlisting
#: Excel.xml:2242
@@ -2228,8 +2228,8 @@
#. Tag: para
#: Excel.xml:2311
#, no-c-format
-msgid "<literal>URL</literal> —The URL to the stylesheet"
-msgstr "<literal>URL</literal> —l'URL al foglio di stile"
+msgid "<literal>URL</literal> — The URL to the stylesheet"
+msgstr "<literal>URL</literal> — l'URL al foglio di stile"
#. Tag: programlisting
#: Excel.xml:2342
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Framework.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Framework.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Framework.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,7 +5,7 @@
msgstr ""
"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"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
"PO-Revision-Date: 2008-12-20 16:14+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
@@ -22,19 +22,32 @@
#. Tag: para
#: Framework.xml:8
#, no-c-format
-msgid "Seam makes it really easy to create applications by writing plain Java classes with annotations, which don't need to extend any special interfaces or superclasses. But we can simplify some common programming tasks even further, by providing a set of pre-built components which can be re-used either by configuration in <literal>components.xml</literal> (for very simple cases) or extension."
+msgid ""
+"Seam makes it really easy to create applications by writing plain Java "
+"classes with annotations, which don't need to extend any special interfaces "
+"or superclasses. But we can simplify some common programming tasks even "
+"further, by providing a set of pre-built components which can be re-used "
+"either by configuration in <literal>components.xml</literal> (for very "
+"simple cases) or extension."
msgstr ""
#. Tag: para
#: Framework.xml:18
#, no-c-format
-msgid "The <emphasis>Seam Application Framework</emphasis> can reduce the amount of code you need to write when doing basic database access in a web application, using either Hibernate or JPA."
+msgid ""
+"The <emphasis>Seam Application Framework</emphasis> can reduce the amount of "
+"code you need to write when doing basic database access in a web "
+"application, using either Hibernate or JPA."
msgstr ""
#. Tag: para
#: Framework.xml:24
#, no-c-format
-msgid "We should emphasize that the framework is extremely simple, just a handful of simple classes that are easy to understand and extend. The \"magic\" is in Seam itself—the same magic you use when creating any Seam application even without using this framework."
+msgid ""
+"We should emphasize that the framework is extremely simple, just a handful "
+"of simple classes that are easy to understand and extend. The \"magic\" is "
+"in Seam itself — the same magic you use when creating any Seam "
+"application even without using this framework."
msgstr ""
#. Tag: title
@@ -46,7 +59,14 @@
#. Tag: para
#: Framework.xml:35
#, no-c-format
-msgid "The components provided by the Seam application framework may be used in one of two different approaches. The first way is to install and configure an instance of the component in <literal>components.xml</literal>, just like we have done with other kinds of built-in Seam components. For example, the following fragment from <literal>components.xml</literal> installs a component which can perform basic CRUD operations for a <literal>Person</literal> entity:"
+msgid ""
+"The components provided by the Seam application framework may be used in one "
+"of two different approaches. The first way is to install and configure an "
+"instance of the component in <literal>components.xml</literal>, just like we "
+"have done with other kinds of built-in Seam components. For example, the "
+"following fragment from <literal>components.xml</literal> installs a "
+"component which can perform basic CRUD operations for a <literal>Person</"
+"literal> entity:"
msgstr ""
#. Tag: programlisting
@@ -68,7 +88,9 @@
#. Tag: para
#: Framework.xml:49
#, no-c-format
-msgid "If that looks a bit too much like \"programming in XML\" for your taste, you can use extension instead:"
+msgid ""
+"If that looks a bit too much like \"programming in XML\" for your taste, you "
+"can use extension instead:"
msgstr ""
#. Tag: programlisting
@@ -100,13 +122,19 @@
#. Tag: para
#: Framework.xml:56
#, no-c-format
-msgid "The second approach has one huge advantage: you can easily add extra functionality, and override the built-in functionality (the framework classes were carefully designed for extension and customization)."
+msgid ""
+"The second approach has one huge advantage: you can easily add extra "
+"functionality, and override the built-in functionality (the framework "
+"classes were carefully designed for extension and customization)."
msgstr ""
#. Tag: para
#: Framework.xml:63
#, no-c-format
-msgid "A second advantage is that your classes may be EJB stateful session beans, if you like. (They do not have to be, they can be plain JavaBean components if you prefer.) If you are using JBoss AS, you'll need 4.2.2.GA or later:"
+msgid ""
+"A second advantage is that your classes may be EJB stateful session beans, "
+"if you like. (They do not have to be, they can be plain JavaBean components "
+"if you prefer.) If you are using JBoss AS, you'll need 4.2.2.GA or later:"
msgstr ""
#. Tag: programlisting
@@ -115,20 +143,25 @@
msgid ""
"<![CDATA[@Stateful\n"
"@Name(\"personHome\")\n"
-"public class PersonHome extends EntityHome<Person> implements LocalPersonHome {\n"
+"public class PersonHome extends EntityHome<Person> implements "
+"LocalPersonHome {\n"
" \n"
"}]]>"
msgstr ""
"<![CDATA[@Stateful\n"
"@Name(\"personHome\")\n"
-"public class PersonHome extends EntityHome<Person> implements LocalPersonHome {\n"
+"public class PersonHome extends EntityHome<Person> implements "
+"LocalPersonHome {\n"
" \n"
"}]]>"
#. Tag: para
#: Framework.xml:72
#, no-c-format
-msgid "You can also make your classes stateless session beans. In this case you <emphasis>must</emphasis> use injection to provide the persistence context, even if it is called <literal>entityManager</literal>:"
+msgid ""
+"You can also make your classes stateless session beans. In this case you "
+"<emphasis>must</emphasis> use injection to provide the persistence context, "
+"even if it is called <literal>entityManager</literal>:"
msgstr ""
#. Tag: programlisting
@@ -137,7 +170,8 @@
msgid ""
"<![CDATA[@Stateless\n"
"@Name(\"personHome\")\n"
-"public class PersonHome extends EntityHome<Person> implements LocalPersonHome {\n"
+"public class PersonHome extends EntityHome<Person> implements "
+"LocalPersonHome {\n"
" \n"
" @In EntityManager entityManager;\n"
" \n"
@@ -149,7 +183,8 @@
msgstr ""
"<![CDATA[@Stateless\n"
"@Name(\"personHome\")\n"
-"public class PersonHome extends EntityHome<Person> implements LocalPersonHome {\n"
+"public class PersonHome extends EntityHome<Person> implements "
+"LocalPersonHome {\n"
" \n"
" @In EntityManager entityManager;\n"
" \n"
@@ -162,19 +197,29 @@
#. Tag: para
#: Framework.xml:81
#, no-c-format
-msgid "At this time, the Seam Application Framework provides four main built-in components: <literal>EntityHome</literal> and <literal>HibernateEntityHome</literal> for CRUD, along with <literal>EntityQuery</literal> and <literal>HibernateEntityQuery</literal> for queries."
+msgid ""
+"At this time, the Seam Application Framework provides four main built-in "
+"components: <literal>EntityHome</literal> and <literal>HibernateEntityHome</"
+"literal> for CRUD, along with <literal>EntityQuery</literal> and "
+"<literal>HibernateEntityQuery</literal> for queries."
msgstr ""
#. Tag: para
#: Framework.xml:89
#, no-c-format
-msgid "The Home and Query components are written so that they can function with a scope of session, event or conversation. Which scope you use depends upon the state model you wish to use in your application."
+msgid ""
+"The Home and Query components are written so that they can function with a "
+"scope of session, event or conversation. Which scope you use depends upon "
+"the state model you wish to use in your application."
msgstr ""
#. Tag: para
#: Framework.xml:95
#, no-c-format
-msgid "The Seam Application Framework only works with Seam-managed persistence contexts. By default, the components will look for a persistence context named <literal>entityManager</literal>."
+msgid ""
+"The Seam Application Framework only works with Seam-managed persistence "
+"contexts. By default, the components will look for a persistence context "
+"named <literal>entityManager</literal>."
msgstr ""
#. Tag: title
@@ -186,7 +231,9 @@
#. Tag: para
#: Framework.xml:106
#, no-c-format
-msgid "A Home object provides persistence operations for a particular entity class. Suppose we have our trusty <literal>Person</literal> class:"
+msgid ""
+"A Home object provides persistence operations for a particular entity class. "
+"Suppose we have our trusty <literal>Person</literal> class:"
msgstr ""
#. Tag: programlisting
@@ -216,14 +263,20 @@
#. Tag: para
#: Framework.xml:113
#, no-c-format
-msgid "We can define a <literal>personHome</literal> component either via configuration:"
+msgid ""
+"We can define a <literal>personHome</literal> component either via "
+"configuration:"
msgstr ""
#. Tag: programlisting
#: Framework.xml:118
#, no-c-format
-msgid "<![CDATA[<framework:entity-home name=\"personHome\" entity-class=\"eg.Person\" />]]>"
-msgstr "<![CDATA[<framework:entity-home name=\"personHome\" entity-class=\"eg.Person\" />]]>"
+msgid ""
+"<![CDATA[<framework:entity-home name=\"personHome\" entity-class=\"eg.Person"
+"\" />]]>"
+msgstr ""
+"<![CDATA[<framework:entity-home name=\"personHome\" entity-class=\"eg.Person"
+"\" />]]>"
#. Tag: para
#: Framework.xml:120
@@ -244,7 +297,13 @@
#. Tag: para
#: Framework.xml:126
#, no-c-format
-msgid "A Home object provides the following operations: <literal>persist()</literal>, <literal>remove()</literal>, <literal>update()</literal> and <literal>getInstance()</literal>. Before you can call the <literal>remove()</literal>, or <literal>update()</literal> operations, you must first set the identifier of the object you are interested in, using the <literal>setId()</literal> method."
+msgid ""
+"A Home object provides the following operations: <literal>persist()</"
+"literal>, <literal>remove()</literal>, <literal>update()</literal> and "
+"<literal>getInstance()</literal>. Before you can call the <literal>remove()</"
+"literal>, or <literal>update()</literal> operations, you must first set the "
+"identifier of the object you are interested in, using the <literal>setId()</"
+"literal> method."
msgstr ""
#. Tag: para
@@ -259,26 +318,35 @@
msgid ""
"<![CDATA[<h1>Create Person</h1>\n"
"<h:form>\n"
-" <div>First name: <h:inputText value=\"#{personHome.instance.firstName}\"/></div>\n"
-" <div>Last name: <h:inputText value=\"#{personHome.instance.lastName}\"/></div>\n"
+" <div>First name: <h:inputText value=\"#{personHome.instance.firstName}\"/"
+"></div>\n"
+" <div>Last name: <h:inputText value=\"#{personHome.instance.lastName}\"/"
+"></div>\n"
" <div>\n"
-" <h:commandButton value=\"Create Person\" action=\"#{personHome.persist}\"/>\n"
+" <h:commandButton value=\"Create Person\" action=\"#{personHome."
+"persist}\"/>\n"
" </div>\n"
"</h:form>]]>"
msgstr ""
"<![CDATA[<h1>Create Person</h1>\n"
"<h:form>\n"
-" <div>First name: <h:inputText value=\"#{personHome.instance.firstName}\"/></div>\n"
-" <div>Last name: <h:inputText value=\"#{personHome.instance.lastName}\"/></div>\n"
+" <div>First name: <h:inputText value=\"#{personHome.instance.firstName}\"/"
+"></div>\n"
+" <div>Last name: <h:inputText value=\"#{personHome.instance.lastName}\"/"
+"></div>\n"
" <div>\n"
-" <h:commandButton value=\"Create Person\" action=\"#{personHome.persist}\"/>\n"
+" <h:commandButton value=\"Create Person\" action=\"#{personHome."
+"persist}\"/>\n"
" </div>\n"
"</h:form>]]>"
#. Tag: para
#: Framework.xml:141
#, no-c-format
-msgid "Usually, it is much nicer to be able to refer to the <literal>Person</literal> merely as <literal>person</literal>, so let's make that possible by adding a line to <literal>components.xml</literal>:"
+msgid ""
+"Usually, it is much nicer to be able to refer to the <literal>Person</"
+"literal> merely as <literal>person</literal>, so let's make that possible by "
+"adding a line to <literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -300,7 +368,9 @@
#. Tag: para
#: Framework.xml:149
#, no-c-format
-msgid "(If we are using configuration.) Or by adding a <literal>@Factory</literal> method to <literal>PersonHome</literal>:"
+msgid ""
+"(If we are using configuration.) Or by adding a <literal>@Factory</literal> "
+"method to <literal>PersonHome</literal>:"
msgstr ""
#. Tag: programlisting
@@ -326,7 +396,9 @@
#. Tag: para
#: Framework.xml:156
#, no-c-format
-msgid "(If we are using extension.) This change simplifies our JSF page to the following:"
+msgid ""
+"(If we are using extension.) This change simplifies our JSF page to the "
+"following:"
msgstr ""
#. Tag: programlisting
@@ -338,7 +410,8 @@
" <div>First name: <h:inputText value=\"#{person.firstName}\"/></div>\n"
" <div>Last name: <h:inputText value=\"#{person.lastName}\"/></div>\n"
" <div>\n"
-" <h:commandButton value=\"Create Person\" action=\"#{personHome.persist}\"/>\n"
+" <h:commandButton value=\"Create Person\" action=\"#{personHome."
+"persist}\"/>\n"
" </div>\n"
"</h:form>]]>"
msgstr ""
@@ -347,14 +420,20 @@
" <div>First name: <h:inputText value=\"#{person.firstName}\"/></div>\n"
" <div>Last name: <h:inputText value=\"#{person.lastName}\"/></div>\n"
" <div>\n"
-" <h:commandButton value=\"Create Person\" action=\"#{personHome.persist}\"/>\n"
+" <h:commandButton value=\"Create Person\" action=\"#{personHome."
+"persist}\"/>\n"
" </div>\n"
"</h:form>]]>"
#. Tag: para
#: Framework.xml:163
#, no-c-format
-msgid "Well, that lets us create new <literal>Person</literal> entries. Yes, that is all the code that is required! Now, if we want to be able to display, update and delete pre-existing <literal>Person</literal> entries in the database, we need to be able to pass the entry identifier to the <literal>PersonHome</literal>. Page parameters are a great way to do that:"
+msgid ""
+"Well, that lets us create new <literal>Person</literal> entries. Yes, that "
+"is all the code that is required! Now, if we want to be able to display, "
+"update and delete pre-existing <literal>Person</literal> entries in the "
+"database, we need to be able to pass the entry identifier to the "
+"<literal>PersonHome</literal>. Page parameters are a great way to do that:"
msgstr ""
#. Tag: programlisting
@@ -384,43 +463,59 @@
#, no-c-format
msgid ""
"<![CDATA[<h1>\n"
-" <h:outputText rendered=\"#{!personHome.managed}\" value=\"Create Person\"/>\n"
-" <h:outputText rendered=\"#{personHome.managed}\" value=\"Edit Person\"/>\n"
+" <h:outputText rendered=\"#{!personHome.managed}\" value=\"Create Person"
+"\"/>\n"
+" <h:outputText rendered=\"#{personHome.managed}\" value=\"Edit Person\"/"
+">\n"
"</h1>\n"
"<h:form>\n"
" <div>First name: <h:inputText value=\"#{person.firstName}\"/></div>\n"
" <div>Last name: <h:inputText value=\"#{person.lastName}\"/></div>\n"
" <div>\n"
-" <h:commandButton value=\"Create Person\" action=\"#{personHome.persist}\" rendered=\"#{!personHome.managed}\"/>\n"
-" <h:commandButton value=\"Update Person\" action=\"#{personHome.update}\" rendered=\"#{personHome.managed}\"/>\n"
-" <h:commandButton value=\"Delete Person\" action=\"#{personHome.remove}\" rendered=\"#{personHome.managed}\"/>\n"
+" <h:commandButton value=\"Create Person\" action=\"#{personHome."
+"persist}\" rendered=\"#{!personHome.managed}\"/>\n"
+" <h:commandButton value=\"Update Person\" action=\"#{personHome."
+"update}\" rendered=\"#{personHome.managed}\"/>\n"
+" <h:commandButton value=\"Delete Person\" action=\"#{personHome."
+"remove}\" rendered=\"#{personHome.managed}\"/>\n"
" </div>\n"
"</h:form>]]>"
msgstr ""
"<![CDATA[<h1>\n"
-" <h:outputText rendered=\"#{!personHome.managed}\" value=\"Create Person\"/>\n"
-" <h:outputText rendered=\"#{personHome.managed}\" value=\"Edit Person\"/>\n"
+" <h:outputText rendered=\"#{!personHome.managed}\" value=\"Create Person"
+"\"/>\n"
+" <h:outputText rendered=\"#{personHome.managed}\" value=\"Edit Person\"/"
+">\n"
"</h1>\n"
"<h:form>\n"
" <div>First name: <h:inputText value=\"#{person.firstName}\"/></div>\n"
" <div>Last name: <h:inputText value=\"#{person.lastName}\"/></div>\n"
" <div>\n"
-" <h:commandButton value=\"Create Person\" action=\"#{personHome.persist}\" rendered=\"#{!personHome.managed}\"/>\n"
-" <h:commandButton value=\"Update Person\" action=\"#{personHome.update}\" rendered=\"#{personHome.managed}\"/>\n"
-" <h:commandButton value=\"Delete Person\" action=\"#{personHome.remove}\" rendered=\"#{personHome.managed}\"/>\n"
+" <h:commandButton value=\"Create Person\" action=\"#{personHome."
+"persist}\" rendered=\"#{!personHome.managed}\"/>\n"
+" <h:commandButton value=\"Update Person\" action=\"#{personHome."
+"update}\" rendered=\"#{personHome.managed}\"/>\n"
+" <h:commandButton value=\"Delete Person\" action=\"#{personHome."
+"remove}\" rendered=\"#{personHome.managed}\"/>\n"
" </div>\n"
"</h:form>]]>"
#. Tag: para
#: Framework.xml:180
#, no-c-format
-msgid "When we link to the page with no request parameters, the page will be displayed as a \"Create Person\" page. When we provide a value for the <literal>personId</literal> request parameter, it will be an \"Edit Person\" page."
+msgid ""
+"When we link to the page with no request parameters, the page will be "
+"displayed as a \"Create Person\" page. When we provide a value for the "
+"<literal>personId</literal> request parameter, it will be an \"Edit Person\" "
+"page."
msgstr ""
#. Tag: para
#: Framework.xml:187
#, no-c-format
-msgid "Suppose we need to create <literal>Person</literal> entries with their nationality initialized. We can do that easily, via configuration:"
+msgid ""
+"Suppose we need to create <literal>Person</literal> entries with their "
+"nationality initialized. We can do that easily, via configuration:"
msgstr ""
#. Tag: programlisting
@@ -492,13 +587,17 @@
#. Tag: para
#: Framework.xml:200
#, no-c-format
-msgid "Of course, the <literal>Country</literal> could be an object managed by another Home object, for example, <literal>CountryHome</literal>."
+msgid ""
+"Of course, the <literal>Country</literal> could be an object managed by "
+"another Home object, for example, <literal>CountryHome</literal>."
msgstr ""
#. Tag: para
#: Framework.xml:205
#, no-c-format
-msgid "To add more sophisticated operations (association management, etc), we can just add methods to <literal>PersonHome</literal>."
+msgid ""
+"To add more sophisticated operations (association management, etc), we can "
+"just add methods to <literal>PersonHome</literal>."
msgstr ""
#. Tag: programlisting
@@ -548,13 +647,23 @@
#. Tag: para
#: Framework.xml:212
#, no-c-format
-msgid "The Home object raises an <literal>org.jboss.seam.afterTransactionSuccess</literal> event when a transaction succeeds (a call to <literal>persist()</literal>, <literal>update()</literal> or <literal>remove()</literal> succeeds). By observing this event we can refresh our queries when the underlying entities are changed. If we only want to refresh certain queries when a particular entity is persited, updated or removed we can observe the <literal>org.jboss.seam.afterTransactionSuccess.<name></literal> event (where <literal><name></literal> is the name of the entity)."
+msgid ""
+"The Home object raises an <literal>org.jboss.seam.afterTransactionSuccess</"
+"literal> event when a transaction succeeds (a call to <literal>persist()</"
+"literal>, <literal>update()</literal> or <literal>remove()</literal> "
+"succeeds). By observing this event we can refresh our queries when the "
+"underlying entities are changed. If we only want to refresh certain queries "
+"when a particular entity is persited, updated or removed we can observe the "
+"<literal>org.jboss.seam.afterTransactionSuccess.<name></literal> event "
+"(where <literal><name></literal> is the name of the entity)."
msgstr ""
#. Tag: para
#: Framework.xml:223
#, no-c-format
-msgid "The Home object automatically displays faces messages when an operation is successful. To customize these messages we can, again, use configuration:"
+msgid ""
+"The Home object automatically displays faces messages when an operation is "
+"successful. To customize these messages we can, again, use configuration:"
msgstr ""
#. Tag: programlisting
@@ -567,9 +676,12 @@
"<framework:entity-home name=\"personHome\"\n"
" entity-class=\"eg.Person\"\n"
" new-instance=\"#{newPerson}\">\n"
-" <framework:created-message>New person #{person.firstName} #{person.lastName} created</framework:created-message>\n"
-" <framework:deleted-message>Person #{person.firstName} #{person.lastName} deleted</framework:deleted-message>\n"
-" <framework:updated-message>Person #{person.firstName} #{person.lastName} updated</framework:updated-message>\n"
+" <framework:created-message>New person #{person.firstName} #{person."
+"lastName} created</framework:created-message>\n"
+" <framework:deleted-message>Person #{person.firstName} #{person.lastName} "
+"deleted</framework:deleted-message>\n"
+" <framework:updated-message>Person #{person.firstName} #{person.lastName} "
+"updated</framework:updated-message>\n"
"</framework:entity-home>\n"
"\n"
"<component name=\"newPerson\" \n"
@@ -583,9 +695,12 @@
"<framework:entity-home name=\"personHome\"\n"
" entity-class=\"eg.Person\"\n"
" new-instance=\"#{newPerson}\">\n"
-" <framework:created-message>New person #{person.firstName} #{person.lastName} created</framework:created-message>\n"
-" <framework:deleted-message>Person #{person.firstName} #{person.lastName} deleted</framework:deleted-message>\n"
-" <framework:updated-message>Person #{person.firstName} #{person.lastName} updated</framework:updated-message>\n"
+" <framework:created-message>New person #{person.firstName} #{person."
+"lastName} created</framework:created-message>\n"
+" <framework:deleted-message>Person #{person.firstName} #{person.lastName} "
+"deleted</framework:deleted-message>\n"
+" <framework:updated-message>Person #{person.firstName} #{person.lastName} "
+"updated</framework:updated-message>\n"
"</framework:entity-home>\n"
"\n"
"<component name=\"newPerson\" \n"
@@ -615,9 +730,12 @@
" return new Person(country);\n"
" }\n"
" \n"
-" protected String getCreatedMessage() { return createValueExpression(\"New person #{person.firstName} #{person.lastName} created\"); }\n"
-" protected String getUpdatedMessage() { return createValueExpression(\"Person #{person.firstName} #{person.lastName} updated\"); }\n"
-" protected String getDeletedMessage() { return createValueExpression(\"Person #{person.firstName} #{person.lastName} deleted\"); }\n"
+" protected String getCreatedMessage() { return createValueExpression"
+"(\"New person #{person.firstName} #{person.lastName} created\"); }\n"
+" protected String getUpdatedMessage() { return createValueExpression"
+"(\"Person #{person.firstName} #{person.lastName} updated\"); }\n"
+" protected String getDeletedMessage() { return createValueExpression"
+"(\"Person #{person.firstName} #{person.lastName} deleted\"); }\n"
" \n"
"}]]>"
msgstr ""
@@ -633,40 +751,52 @@
" return new Person(country);\n"
" }\n"
" \n"
-" protected String getCreatedMessage() { return createValueExpression(\"New person #{person.firstName} #{person.lastName} created\"); }\n"
-" protected String getUpdatedMessage() { return createValueExpression(\"Person #{person.firstName} #{person.lastName} updated\"); }\n"
-" protected String getDeletedMessage() { return createValueExpression(\"Person #{person.firstName} #{person.lastName} deleted\"); }\n"
+" protected String getCreatedMessage() { return createValueExpression"
+"(\"New person #{person.firstName} #{person.lastName} created\"); }\n"
+" protected String getUpdatedMessage() { return createValueExpression"
+"(\"Person #{person.firstName} #{person.lastName} updated\"); }\n"
+" protected String getDeletedMessage() { return createValueExpression"
+"(\"Person #{person.firstName} #{person.lastName} deleted\"); }\n"
" \n"
"}]]>"
#. Tag: para
#: Framework.xml:236
#, no-c-format
-msgid "But the best way to specify the messages is to put them in a resource bundle known to Seam (the bundle named <literal>messages</literal>, by default)."
+msgid ""
+"But the best way to specify the messages is to put them in a resource bundle "
+"known to Seam (the bundle named <literal>messages</literal>, by default)."
msgstr ""
#. Tag: programlisting
#: Framework.xml:242
#, no-c-format
msgid ""
-"<![CDATA[Person_created=New person #{person.firstName} #{person.lastName} created\n"
+"<![CDATA[Person_created=New person #{person.firstName} #{person.lastName} "
+"created\n"
"Person_deleted=Person #{person.firstName} #{person.lastName} deleted\n"
"Person_updated=Person #{person.firstName} #{person.lastName} updated]]>"
msgstr ""
-"<![CDATA[Person_created=New person #{person.firstName} #{person.lastName} created\n"
+"<![CDATA[Person_created=New person #{person.firstName} #{person.lastName} "
+"created\n"
"Person_deleted=Person #{person.firstName} #{person.lastName} deleted\n"
"Person_updated=Person #{person.firstName} #{person.lastName} updated]]>"
#. Tag: para
#: Framework.xml:244
#, no-c-format
-msgid "This enables internationalization, and keeps your code and configuration clean of presentation concerns."
+msgid ""
+"This enables internationalization, and keeps your code and configuration "
+"clean of presentation concerns."
msgstr ""
#. Tag: para
#: Framework.xml:249
#, no-c-format
-msgid "The final step is to add validation functionality to the page, using <literal><s:validateAll></literal> and <literal><s:decorate></literal>, but I'll leave that for you to figure out."
+msgid ""
+"The final step is to add validation functionality to the page, using "
+"<literal><s:validateAll></literal> and <literal><s:decorate></"
+"literal>, but I'll leave that for you to figure out."
msgstr ""
#. Tag: title
@@ -678,7 +808,9 @@
#. Tag: para
#: Framework.xml:260
#, no-c-format
-msgid "If we need a list of all <literal>Person</literal> instance in the database, we can use a Query object. For example:"
+msgid ""
+"If we need a list of all <literal>Person</literal> instance in the database, "
+"we can use a Query object. For example:"
msgstr ""
#. Tag: programlisting
@@ -704,7 +836,8 @@
"<![CDATA[<h1>List of people</h1>\n"
"<h:dataTable value=\"#{people.resultList}\" var=\"person\">\n"
" <h:column>\n"
-" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #{person.lastName}\">\n"
+" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #"
+"{person.lastName}\">\n"
" <f:param name=\"personId\" value=\"#{person.id}\"/>\n"
" </s:link>\n"
" </h:column>\n"
@@ -713,7 +846,8 @@
"<![CDATA[<h1>List of people</h1>\n"
"<h:dataTable value=\"#{people.resultList}\" var=\"person\">\n"
" <h:column>\n"
-" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #{person.lastName}\">\n"
+" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #"
+"{person.lastName}\">\n"
" <f:param name=\"personId\" value=\"#{person.id}\"/>\n"
" </s:link>\n"
" </h:column>\n"
@@ -774,57 +908,70 @@
"<![CDATA[<h1>Search for people</h1>\n"
"<h:dataTable value=\"#{people.resultList}\" var=\"person\">\n"
" <h:column>\n"
-" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #{person.lastName}\">\n"
+" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #"
+"{person.lastName}\">\n"
" <f:param name=\"personId\" value=\"#{person.id}\"/>\n"
" </s:link>\n"
" </h:column>\n"
"</h:dataTable>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value=\"First Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value="
+"\"First Page\">\n"
" <f:param name=\"firstResult\" value=\"0\"/>\n"
"</s:link>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value=\"Previous Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value="
+"\"Previous Page\">\n"
" <f:param name=\"firstResult\" value=\"#{people.previousFirstResult}\"/>\n"
"</s:link>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value=\"Next Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value="
+"\"Next Page\">\n"
" <f:param name=\"firstResult\" value=\"#{people.nextFirstResult}\"/>\n"
"</s:link>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value=\"Last Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value="
+"\"Last Page\">\n"
" <f:param name=\"firstResult\" value=\"#{people.lastFirstResult}\"/>\n"
"</s:link>]]>"
msgstr ""
"<![CDATA[<h1>Search for people</h1>\n"
"<h:dataTable value=\"#{people.resultList}\" var=\"person\">\n"
" <h:column>\n"
-" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #{person.lastName}\">\n"
+" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #"
+"{person.lastName}\">\n"
" <f:param name=\"personId\" value=\"#{person.id}\"/>\n"
" </s:link>\n"
" </h:column>\n"
"</h:dataTable>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value=\"First Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value="
+"\"First Page\">\n"
" <f:param name=\"firstResult\" value=\"0\"/>\n"
"</s:link>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value=\"Previous Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.previousExists}\" value="
+"\"Previous Page\">\n"
" <f:param name=\"firstResult\" value=\"#{people.previousFirstResult}\"/>\n"
"</s:link>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value=\"Next Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value="
+"\"Next Page\">\n"
" <f:param name=\"firstResult\" value=\"#{people.nextFirstResult}\"/>\n"
"</s:link>\n"
"\n"
-"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value=\"Last Page\">\n"
+"<s:link view=\"/search.xhtml\" rendered=\"#{people.nextExists}\" value="
+"\"Last Page\">\n"
" <f:param name=\"firstResult\" value=\"#{people.lastFirstResult}\"/>\n"
"</s:link>]]>"
#. Tag: para
#: Framework.xml:292
#, no-c-format
-msgid "Real search screens let the user enter a bunch of optional search criteria to narrow the list of results returned. The Query object lets you specify optional \"restrictions\" to support this important usecase:"
+msgid ""
+"Real search screens let the user enter a bunch of optional search criteria "
+"to narrow the list of results returned. The Query object lets you specify "
+"optional \"restrictions\" to support this important usecase:"
msgstr ""
#. Tag: programlisting
@@ -838,8 +985,10 @@
" order=\"lastName\" \n"
" max-results=\"20\">\n"
" <framework:restrictions>\n"
-" <value>lower(firstName) like lower( concat(#{examplePerson.firstName},'%') )</value>\n"
-" <value>lower(lastName) like lower( concat(#{examplePerson.lastName},'%') )</value>\n"
+" <value>lower(firstName) like lower( concat(#{examplePerson."
+"firstName},'%') )</value>\n"
+" <value>lower(lastName) like lower( concat(#{examplePerson."
+"lastName},'%') )</value>\n"
" </framework:restrictions>\n"
"</framework:entity-query>]]>"
msgstr ""
@@ -850,8 +999,10 @@
" order=\"lastName\" \n"
" max-results=\"20\">\n"
" <framework:restrictions>\n"
-" <value>lower(firstName) like lower( concat(#{examplePerson.firstName},'%') )</value>\n"
-" <value>lower(lastName) like lower( concat(#{examplePerson.lastName},'%') )</value>\n"
+" <value>lower(firstName) like lower( concat(#{examplePerson."
+"firstName},'%') )</value>\n"
+" <value>lower(lastName) like lower( concat(#{examplePerson."
+"lastName},'%') )</value>\n"
" </framework:restrictions>\n"
"</framework:entity-query>]]>"
@@ -867,14 +1018,17 @@
msgid ""
"<![CDATA[<h1>Search for people</h1>\n"
"<h:form>\n"
-" <div>First name: <h:inputText value=\"#{examplePerson.firstName}\"/></div>\n"
-" <div>Last name: <h:inputText value=\"#{examplePerson.lastName}\"/></div>\n"
+" <div>First name: <h:inputText value=\"#{examplePerson.firstName}\"/></"
+"div>\n"
+" <div>Last name: <h:inputText value=\"#{examplePerson.lastName}\"/></"
+"div>\n"
" <div><h:commandButton value=\"Search\" action=\"/search.jsp\"/></div>\n"
"</h:form>\n"
"\n"
"<h:dataTable value=\"#{people.resultList}\" var=\"person\">\n"
" <h:column>\n"
-" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #{person.lastName}\">\n"
+" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #"
+"{person.lastName}\">\n"
" <f:param name=\"personId\" value=\"#{person.id}\"/>\n"
" </s:link>\n"
" </h:column>\n"
@@ -882,14 +1036,17 @@
msgstr ""
"<![CDATA[<h1>Search for people</h1>\n"
"<h:form>\n"
-" <div>First name: <h:inputText value=\"#{examplePerson.firstName}\"/></div>\n"
-" <div>Last name: <h:inputText value=\"#{examplePerson.lastName}\"/></div>\n"
+" <div>First name: <h:inputText value=\"#{examplePerson.firstName}\"/></"
+"div>\n"
+" <div>Last name: <h:inputText value=\"#{examplePerson.lastName}\"/></"
+"div>\n"
" <div><h:commandButton value=\"Search\" action=\"/search.jsp\"/></div>\n"
"</h:form>\n"
"\n"
"<h:dataTable value=\"#{people.resultList}\" var=\"person\">\n"
" <h:column>\n"
-" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #{person.lastName}\">\n"
+" <s:link view=\"/editPerson.jsp\" value=\"#{person.firstName} #"
+"{person.lastName}\">\n"
" <f:param name=\"personId\" value=\"#{person.id}\"/>\n"
" </s:link>\n"
" </h:column>\n"
@@ -898,7 +1055,9 @@
#. Tag: para
#: Framework.xml:306
#, no-c-format
-msgid "To refresh the query when the underlying entities change we observe the <literal>org.jboss.seam.afterTransactionSuccess</literal> event:"
+msgid ""
+"To refresh the query when the underlying entities change we observe the "
+"<literal>org.jboss.seam.afterTransactionSuccess</literal> event:"
msgstr ""
#. Tag: programlisting
@@ -916,7 +1075,9 @@
#. Tag: para
#: Framework.xml:313
#, no-c-format
-msgid "Or, to just refresh the query when the person entity is persisted, updated or removed through <literal>PersonHome</literal>:"
+msgid ""
+"Or, to just refresh the query when the person entity is persisted, updated "
+"or removed through <literal>PersonHome</literal>:"
msgstr ""
#. Tag: programlisting
@@ -934,13 +1095,19 @@
#. Tag: para
#: Framework.xml:320
#, no-c-format
-msgid "Unfortunately Query objects don't work well with <emphasis>join fetch</emphasis> queries - the use of pagination with these queries is not recomended, and you'll have to implement your own method of calculating the total number of results (by overriding <literal>getCountEjbql()</literal>."
+msgid ""
+"Unfortunately Query objects don't work well with <emphasis>join fetch</"
+"emphasis> queries - the use of pagination with these queries is not "
+"recomended, and you'll have to implement your own method of calculating the "
+"total number of results (by overriding <literal>getCountEjbql()</literal>."
msgstr ""
#. Tag: para
#: Framework.xml:328
#, no-c-format
-msgid "The examples in this section have all shown reuse by configuration. However, reuse by extension is equally possible for Query objects."
+msgid ""
+"The examples in this section have all shown reuse by configuration. However, "
+"reuse by extension is equally possible for Query objects."
msgstr ""
#. Tag: title
@@ -952,13 +1119,23 @@
#. Tag: para
#: Framework.xml:337
#, no-c-format
-msgid "A totally optional part of the Seam Application Framework is the class <literal>Controller</literal> and its subclasses <literal>EntityController</literal> <literal>HibernateEntityController</literal> and <literal>BusinessProcessController</literal>. These classes provide nothing more than some convenience methods for access to commonly used built-in components and methods of built-in components. They help save a few keystrokes (characters can add up!) and provide a great launchpad for new users to explore the rich functionality built in to Seam."
+msgid ""
+"A totally optional part of the Seam Application Framework is the class "
+"<literal>Controller</literal> and its subclasses <literal>EntityController</"
+"literal> <literal>HibernateEntityController</literal> and "
+"<literal>BusinessProcessController</literal>. These classes provide nothing "
+"more than some convenience methods for access to commonly used built-in "
+"components and methods of built-in components. They help save a few "
+"keystrokes (characters can add up!) and provide a great launchpad for new "
+"users to explore the rich functionality built in to Seam."
msgstr ""
#. Tag: para
#: Framework.xml:349
#, no-c-format
-msgid "For example, here is what <literal>RegisterAction</literal> from the Seam registration example would look like:"
+msgid ""
+"For example, here is what <literal>RegisterAction</literal> from the Seam "
+"registration example would look like:"
msgstr ""
#. Tag: programlisting
@@ -974,7 +1151,8 @@
" \n"
" public String register()\n"
" {\n"
-" List existing = createQuery(\"select u.username from User u where u.username=:username\")\n"
+" List existing = createQuery(\"select u.username from User u where u."
+"username=:username\")\n"
" .setParameter(\"username\", user.getUsername())\n"
" .getResultList();\n"
" \n"
@@ -1002,7 +1180,8 @@
" \n"
" public String register()\n"
" {\n"
-" List existing = createQuery(\"select u.username from User u where u.username=:username\")\n"
+" List existing = createQuery(\"select u.username from User u where u."
+"username=:username\")\n"
" .setParameter(\"username\", user.getUsername())\n"
" .getResultList();\n"
" \n"
@@ -1026,4 +1205,3 @@
#, no-c-format
msgid "As you can see, its not an earthshattering improvement..."
msgstr ""
-
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Getting_Started_With_JBoss_Tools.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,7 +5,7 @@
msgstr ""
"Project-Id-Version: seam 2_0\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-05-03 11:34+0000\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
"PO-Revision-Date: 2008-12-27 12:52+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
@@ -22,7 +22,12 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:7
#, no-c-format
-msgid "JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project creation wizard for Seam, Content Assist for the Unified Expression Language (EL) in both facelets and Java code, a graphical editor for jPDL, a graphical editor for Seam configuration files, support for running Seam integration tests from within Eclipse, and much more."
+msgid ""
+"JBoss Tools is a collection of Eclipse plugins. JBoss Tools a project "
+"creation wizard for Seam, Content Assist for the Unified Expression Language "
+"(EL) in both facelets and Java code, a graphical editor for jPDL, a "
+"graphical editor for Seam configuration files, support for running Seam "
+"integration tests from within Eclipse, and much more."
msgstr ""
#. Tag: para
@@ -34,7 +39,11 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:19
#, no-c-format
-msgid "JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible with a few tweaks to get your app running on other application servers. The changes are much like those described for seam-gen later in this reference manual."
+msgid ""
+"JBoss Tools, as with seam-gen, works best with JBoss AS, but it's possible "
+"with a few tweaks to get your app running on other application servers. The "
+"changes are much like those described for seam-gen later in this reference "
+"manual."
msgstr ""
#. Tag: title
@@ -46,7 +55,10 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:29
#, no-c-format
-msgid "Make sure you have JDK 5, JBoss AS 4.2, Eclipse 3.3, the JBoss Tools plugins (at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) and the TestNG plugin for Eclipse correctly installed before starting."
+msgid ""
+"Make sure you have JDK 5, JBoss AS 4.2, Eclipse 3.3, the JBoss Tools plugins "
+"(at least Seam Tools, the Visual Page Editor, jBPM Tools and JBoss AS Tools) "
+"and the TestNG plugin for Eclipse correctly installed before starting."
msgstr ""
#. Tag: para
@@ -70,19 +82,26 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:47
#, no-c-format
-msgid "Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> <emphasis>Seam Web Project</emphasis>."
+msgid ""
+"Go to <emphasis>File</emphasis> -> <emphasis>New</emphasis> -> "
+"<emphasis>Seam Web Project</emphasis>."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:63
#, no-c-format
-msgid "First, enter a name for your new project. For this tutorial, we're going to use <literal>helloworld</literal> ."
+msgid ""
+"First, enter a name for your new project. For this tutorial, we're going to "
+"use <literal>helloworld</literal> ."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:71
#, no-c-format
-msgid "Now, we need to tell JBoss Tools about JBoss AS. This is a two stage process, first we need to define a runtime, make sure you select JBoss AS 4.2:"
+msgid ""
+"Now, we need to tell JBoss Tools about JBoss AS. This is a two stage "
+"process, first we need to define a runtime, make sure you select JBoss AS "
+"4.2:"
msgstr ""
#. Tag: para
@@ -94,43 +113,69 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:103
#, no-c-format
-msgid "Next, we need to define a server JBoss Tools can deploy the project to. Make sure to again select JBoss AS 4.2, and also the runtime you just defined:"
+msgid ""
+"Next, we need to define a server JBoss Tools can deploy the project to. Make "
+"sure to again select JBoss AS 4.2, and also the runtime you just defined:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:118
#, no-c-format
-msgid "On the next screen give the server a name, and hit <emphasis>Finish</emphasis>:"
+msgid ""
+"On the next screen give the server a name, and hit <emphasis>Finish</"
+"emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:134
#, no-c-format
-msgid "Make sure the runtime and server you just created are selected, select <emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> and hit <emphasis>Next</emphasis>:"
+msgid ""
+"Make sure the runtime and server you just created are selected, select "
+"<emphasis>Dynamic Web Project with Seam 2.0 (technology preview)</emphasis> "
+"and hit <emphasis>Next</emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:151
#, no-c-format
-msgid "The next 3 screens allow you to further customize your new project, but for us the defaults are fine. So just hit <empahsis>Next</empahsis> until you reach the final screen."
+msgid ""
+"The next 3 screens allow you to further customize your new project, but for "
+"us the defaults are fine. So just hit <emphasis>Next</emphasis> until you "
+"reach the final screen."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:157
#, no-c-format
-msgid "The first step here is to tell JBoss Tools about the Seam download you want to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - make sure to give it a name, and select <emphasis>2.0</emphasis> as the version:"
+msgid ""
+"The first step here is to tell JBoss Tools about the Seam download you want "
+"to use. <emphasis>Add</emphasis> a new <emphasis>Seam Runtime</emphasis> - "
+"make sure to give it a name, and select <emphasis>2.0</emphasis> as the "
+"version:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:175
#, 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 <emphasis>EAR</emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that you've chosen a WAR deployment for the rest of the tutorial, but you can follow exactly the same steps for a EAR 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 <emphasis>EAR</"
+"emphasis>. Otherwise, choose <emphasis>WAR</emphasis>. We'll assume that "
+"you've chosen a WAR deployment for the rest of the tutorial, but you can "
+"follow exactly the same steps for a EAR deployment."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:187
#, no-c-format
-msgid "Next, select your database type. We'll assume you have MySQL installed, with an existing schema. You'll need to tell JBoss Tools about the database, select <emphasis>MySQL</emphasis> as the database, and create a new connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:"
+msgid ""
+"Next, select your database type. We'll assume you have MySQL installed, with "
+"an existing schema. You'll need to tell JBoss Tools about the database, "
+"select <emphasis>MySQL</emphasis> as the database, and create a new "
+"connection profile. Select <emphasis>Generic JDBC Connection</emphasis>:"
msgstr ""
#. Tag: para
@@ -142,7 +187,10 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:221
#, no-c-format
-msgid "JBoss Tools doesn't come with drivers for any databases, so you need to tell JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by clicking <emphasis>...</emphasis>."
+msgid ""
+"JBoss Tools doesn't come with drivers for any databases, so you need to tell "
+"JBoss Tools where the MySQL JDBC driver is. Tell it about the driver by "
+"clicking <emphasis>...</emphasis>."
msgstr ""
#. Tag: para
@@ -160,13 +208,17 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:257
#, no-c-format
-msgid "Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</emphasis>:"
+msgid ""
+"Locate the jar on your computer by choosing <emphasis>Edit Jar/Zip</"
+"emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:273
#, no-c-format
-msgid "Review the username and password used to connect, and if correct, hit <emphasis>Ok</emphasis>."
+msgid ""
+"Review the username and password used to connect, and if correct, hit "
+"<emphasis>Ok</emphasis>."
msgstr ""
#. Tag: para
@@ -178,25 +230,37 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:293
#, no-c-format
-msgid "If you are working with an existing data model, make sure you tell JBoss Tools that the tables already exist in the database."
+msgid ""
+"If you are working with an existing data model, make sure you tell JBoss "
+"Tools that the tables already exist in the database."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:298
#, no-c-format
-msgid "Review the username and password used to connect, test the connection using the <emphasis>Test Connection</emphasis> button, and if it works, hit <emphasis>Finish</emphasis>:"
+msgid ""
+"Review the username and password used to connect, test the connection using "
+"the <emphasis>Test Connection</emphasis> button, and if it works, hit "
+"<emphasis>Finish</emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:304
#, no-c-format
-msgid "Finally, review the package names for your generated beans, and if you are happy, click <emphasis>Finish</emphasis>:"
+msgid ""
+"Finally, review the package names for your generated beans, and if you are "
+"happy, click <emphasis>Finish</emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:320
#, 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. 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. We suggest the following values:"
msgstr ""
#. Tag: programlisting
@@ -208,7 +272,9 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:331
#, 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
@@ -220,7 +286,9 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:338
#, no-c-format
-msgid "Locate the server in the <emphasis>JBoss Server View</emphasis>, right click on the server and select <emphasis>Edit Launch Configuration</emphasis>:"
+msgid ""
+"Locate the server in the <emphasis>JBoss Server View</emphasis>, right click "
+"on the server and select <emphasis>Edit Launch Configuration</emphasis>:"
msgstr ""
#. Tag: para
@@ -232,19 +300,28 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:370
#, 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: para
#: Getting_Started_With_JBoss_Tools.xml:376
#, no-c-format
-msgid "To start JBoss, and deploy the project, just right click on the server you created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</emphasis> to start in debug mode):"
+msgid ""
+"To start JBoss, and deploy the project, just right click on the server you "
+"created, and click <emphasis>Start</emphasis>, (or <emphasis>Debug</"
+"emphasis> to start in debug mode):"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:393
#, 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."
+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."
msgstr ""
#. Tag: title
@@ -256,20 +333,26 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:405
#, 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."
+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."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:411
#, no-c-format
-msgid "First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:"
+msgid ""
+"First, select <emphasis>New</emphasis> -> <emphasis>Seam Action</emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:426
#: Getting_Started_With_JBoss_Tools.xml:492
#, no-c-format
-msgid "Now, enter the name of the Seam component. JBoss Tools selects sensible defaults for other fields:"
+msgid ""
+"Now, enter the name of the Seam component. JBoss Tools selects sensible "
+"defaults for other fields:"
msgstr ""
#. Tag: para
@@ -281,13 +364,20 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:446
#, 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
#: Getting_Started_With_JBoss_Tools.xml:454
#, no-c-format
-msgid "Finally, open the <literal>helloworld-test</literal> project, locate <literal>PingTest</literal> class, right click on it, and choose <emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:"
+msgid ""
+"Finally, open the <literal>helloworld-test</literal> project, locate "
+"<literal>PingTest</literal> class, right click on it, and choose "
+"<emphasis>Run As</emphasis> -> <emphasis>TestNG Test</emphasis>:"
msgstr ""
#. Tag: title
@@ -299,13 +389,21 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:476
#, no-c-format
-msgid "The first step is to create a form. Select <emphasis>New</emphasis> -> <emphasis>Seam Form</emphasis>:"
+msgid ""
+"The first step is to create a form. Select <emphasis>New</emphasis> -> "
+"<emphasis>Seam Form</emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:508
#, no-c-format
-msgid "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 (note, you don't need to restart the app server each time you change the code in <literal>src/action</literal> as Seam hot reloads the component for you <xref linkend=\"gettingstartedwithjbosstools.hotdeployment\"/>)."
+msgid ""
+"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 (note, you don't need to restart the app "
+"server each time you change the code in <literal>src/action</literal> as "
+"Seam hot reloads the component for you <xref linkend="
+"\"gettingstartedwithjbosstools.hotdeployment\"/>)."
msgstr ""
#. Tag: title
@@ -317,13 +415,21 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:521
#, no-c-format
-msgid "Manually create some tables in your database. (If you need to switch to a different database, create a new project, and select the correct database). Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</emphasis>:"
+msgid ""
+"Manually create some tables in your database. (If you need to switch to a "
+"different database, create a new project, and select the correct database). "
+"Then, select <emphasis>New</emphasis> -> <emphasis>Seam Generate Entities</"
+"emphasis>:"
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:539
#, no-c-format
-msgid "JBoss Tools gives you the option to either reverse engineer entities, components and views from a database schema or to reverse engineer components and views from existing JPA entities. We're going to do <emphasis>Reverse engieneer from database</emphasis>."
+msgid ""
+"JBoss Tools gives you the option to either reverse engineer entities, "
+"components and views from a database schema or to reverse engineer "
+"components and views from existing JPA entities. We're going to do "
+"<emphasis>Reverse engieneer from database</emphasis>."
msgstr ""
#. Tag: para
@@ -335,7 +441,12 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:561
#, no-c-format
-msgid "Then 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 reverse engineering."
+msgid ""
+"Then 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 reverse engineering."
msgstr ""
#. Tag: title
@@ -371,13 +482,20 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:594
#, no-c-format
-msgid "But if we want to change any Java code, we still need to do a full restart of the application by doing a <emphasis>Full Publish</emphasis>."
+msgid ""
+"But if we want to change any Java code, we still need to do a full restart "
+"of the application by doing a <emphasis>Full Publish</emphasis>."
msgstr ""
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:600
#, 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
@@ -389,7 +507,9 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:613
#, 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
@@ -401,19 +521,25 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:626
#, 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
#: Getting_Started_With_JBoss_Tools.xml:633
#, 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
#: Getting_Started_With_JBoss_Tools.xml:640
#, 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
@@ -425,12 +551,17 @@
#. Tag: para
#: Getting_Started_With_JBoss_Tools.xml:654
#, 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
#: Getting_Started_With_JBoss_Tools.xml:662
#, no-c-format
-msgid "If you create a WAR project using JBoss Tools, incremental hot deployment is available out of the box for classes in the <literal>src/action</literal> source directory. However, JBoss Tools does not support incremental hot deployment for EAR projects."
+msgid ""
+"If you create a WAR project using JBoss Tools, incremental hot deployment is "
+"available out of the box for classes in the <literal>src/action</literal> "
+"source directory. However, JBoss Tools does not support incremental hot "
+"deployment for EAR projects."
msgstr ""
-
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Itext.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Itext.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Itext.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-12-04 00:58+0000\n"
-"PO-Revision-Date: 2009-01-17 21:00+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:21+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -22,8 +22,8 @@
#. Tag: para
#: Itext.xml:3
#, no-c-format
-msgid "Seam now includes a component set for generating documents using iText. The primary focus of Seam's iText document support is for the generation of PDF doucuments, but Seam also offers basic support for RTF document generation."
-msgstr "Seam adesso include un componente per la generazione di documenti usando iText. "
+msgid "Seam now includes a component set for generating documents using iText. The primary focus of Seam's iText document support is for the generation of PDF documents, but Seam also offers basic support for RTF document generation."
+msgstr "Seam adesso include un componente per la generazione di documenti usando iText. Il primo focus del supporto di Seam ai documenti iText è per la generazione dei documenti PDF, ma Seam offre anche un supporto base per la generazione di documenti RTF."
#. Tag: title
#: Itext.xml:8
@@ -1359,21 +1359,18 @@
#. Tag: para
#: Itext.xml:1388
-#: Itext.xml:1584
#, no-c-format
msgid "<literal>legendItemPaint</literal>— The default color of the text labels in the legend."
msgstr ""
#. Tag: para
#: Itext.xml:1394
-#: Itext.xml:1590
#, no-c-format
msgid "<literal>legendItemBackgoundPaint</literal>— The background color for the legend, if different from the chart background color."
msgstr ""
#. Tag: para
#: Itext.xml:1400
-#: Itext.xml:1596
#, no-c-format
msgid "<literal>legendOutlinePaint</literal>— The color of the border around the legend."
msgstr ""
@@ -1387,28 +1384,24 @@
#. Tag: para
#: Itext.xml:1412
-#: Itext.xml:1608
#, no-c-format
msgid "<literal>plotBackgroundPaint</literal>— The color of the plot background."
msgstr ""
#. Tag: para
#: Itext.xml:1418
-#: Itext.xml:1614
#, no-c-format
msgid "<literal>plotBackgroundAlpha</literal>— The alpha (transparency) level of the plot background. It should be a number between 0 (completely transparent) and 1 (completely opaque)."
msgstr ""
#. Tag: para
#: Itext.xml:1425
-#: Itext.xml:1621
#, no-c-format
msgid "<literal>plotForegroundAlpha</literal>— The alpha (transparency) level of the plot. It should be a number between 0 (completely transparent) and 1 (completely opaque)."
msgstr ""
#. Tag: para
#: Itext.xml:1432
-#: Itext.xml:1628
#, no-c-format
msgid "<literal>plotOutlinePaint</literal>— The color of the range gridlines, if visible."
msgstr ""
@@ -1436,14 +1429,12 @@
#. Tag: para
#: Itext.xml:1454
-#: Itext.xml:1650
#, no-c-format
msgid "<literal>rangeGridlinesVisible</literal>— Controls whether or not gridlines for the range axis are shown on the chart."
msgstr ""
#. Tag: para
#: Itext.xml:1459
-#: Itext.xml:1655
#, no-c-format
msgid "<literal>rangeGridlinePaint</literal>— The color of the range gridlines, if visible."
msgstr ""
@@ -1458,20 +1449,19 @@
#. Tag: para
#: Itext.xml:1470
#: Itext.xml:1666
+#: Itext.xml:1710
#, no-c-format
msgid "<literal>title</literal> — The chart title text."
msgstr ""
#. Tag: para
#: Itext.xml:1474
-#: Itext.xml:1670
#, no-c-format
msgid "<literal>titlePaint</literal>— The color of the chart title text."
msgstr ""
#. Tag: para
#: Itext.xml:1479
-#: Itext.xml:1675
#, no-c-format
msgid "<literal>titleBackgroundPaint</literal>— The background color around the chart title."
msgstr ""
@@ -1514,6 +1504,72 @@
msgid "Displays a line chart."
msgstr ""
+#. Tag: para
+#: Itext.xml:1584
+#, no-c-format
+msgid "<literal>legendItemPaint</literal> — The default color of the text labels in the legend."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
+
+#. Tag: para
+#: Itext.xml:1590
+#, no-c-format
+msgid "<literal>legendItemBackgoundPaint</literal> — The background color for the legend, if different from the chart background color."
+msgstr ""
+
+#. Tag: para
+#: Itext.xml:1596
+#, no-c-format
+msgid "<literal>legendOutlinePaint</literal> — The color of the border around the legend."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
+
+#. Tag: para
+#: Itext.xml:1608
+#, no-c-format
+msgid "<literal>plotBackgroundPaint</literal> — The color of the plot background."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
+
+#. Tag: para
+#: Itext.xml:1614
+#, no-c-format
+msgid "<literal>plotBackgroundAlpha</literal> — The alpha (transparency) level of the plot background. It should be a number between 0 (completely transparent) and 1 (completely opaque)."
+msgstr ""
+
+#. Tag: para
+#: Itext.xml:1621
+#, no-c-format
+msgid "<literal>plotForegroundAlpha</literal> — The alpha (transparency) level of the plot. It should be a number between 0 (completely transparent) and 1 (completely opaque)."
+msgstr ""
+
+#. Tag: para
+#: Itext.xml:1628
+#, no-c-format
+msgid "<literal>plotOutlinePaint</literal> — The color of the range gridlines, if visible."
+msgstr ""
+
+#. Tag: para
+#: Itext.xml:1650
+#, no-c-format
+msgid "<literal>rangeGridlinesVisible</literal> — Controls whether or not gridlines for the range axis are shown on the chart."
+msgstr ""
+
+#. Tag: para
+#: Itext.xml:1655
+#, no-c-format
+msgid "<literal>rangeGridlinePaint</literal> — The color of the range gridlines, if visible."
+msgstr ""
+
+#. Tag: para
+#: Itext.xml:1670
+#, no-c-format
+msgid "<literal>titlePaint</literal> — The color of the chart title text."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
+
+#. Tag: para
+#: Itext.xml:1675
+#, no-c-format
+msgid "<literal>titleBackgroundPaint</literal> — The background color around the chart title."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
+
#. Tag: programlisting
#: Itext.xml:1688
#, no-c-format
@@ -1553,142 +1609,136 @@
msgstr ""
#. Tag: para
-#: Itext.xml:1710
-#, no-c-format
-msgid "<literal>title</literal>— The chart title text."
-msgstr ""
-
-#. Tag: para
#: Itext.xml:1714
#, no-c-format
-msgid "<literal>label</literal>— The default label text for pie sections."
-msgstr ""
+msgid "<literal>label</literal> — The default label text for pie sections."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1719
#, no-c-format
-msgid "<literal>legend</literal>— A boolean value indicating whether or not the chart should include a legend. Default value is true"
+msgid "<literal>legend</literal> — A boolean value indicating whether or not the chart should include a legend. Default value is true"
msgstr ""
#. Tag: para
#: Itext.xml:1724
#, no-c-format
-msgid "<literal>is3D</literal>—A boolean value indicating that the chart should be rendered in 3D instead of 2D."
+msgid "<literal>is3D</literal> —A boolean value indicating that the chart should be rendered in 3D instead of 2D."
msgstr ""
#. Tag: para
#: Itext.xml:1729
#, no-c-format
-msgid "<literal>labelLinkMargin</literal>— The link margin for labels."
+msgid "<literal>labelLinkMargin</literal> — The link margin for labels."
msgstr ""
#. Tag: para
#: Itext.xml:1734
#, no-c-format
-msgid "<literal>labelLinkPaint</literal>— The paint used for the label linking lines."
+msgid "<literal>labelLinkPaint</literal> — The paint used for the label linking lines."
msgstr ""
#. Tag: para
#: Itext.xml:1739
#, no-c-format
-msgid "<literal>labelLinkStroke</literal>— he stroke used for the label linking lines."
-msgstr ""
+msgid "<literal>labelLinkStroke</literal> — he stroke used for the label linking lines."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1745
#, no-c-format
-msgid "<literal>labelLinksVisible</literal>— A flag that controls whether or not the label links are drawn."
+msgid "<literal>labelLinksVisible</literal> — A flag that controls whether or not the label links are drawn."
msgstr ""
#. Tag: para
#: Itext.xml:1750
#, no-c-format
-msgid "<literal>labelOutlinePaint</literal>— The paint used to draw the outline of the section labels."
-msgstr ""
+msgid "<literal>labelOutlinePaint</literal> — The paint used to draw the outline of the section labels."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1755
#, no-c-format
-msgid "<literal>labelOutlineStroke</literal>— The stroke used to draw the outline of the section labels."
-msgstr ""
+msgid "<literal>labelOutlineStroke</literal> — The stroke used to draw the outline of the section labels."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1760
#, no-c-format
-msgid "<literal>labelShadowPaint</literal>— The paint used to draw the shadow for the section labels."
-msgstr ""
+msgid "<literal>labelShadowPaint</literal> — The paint used to draw the shadow for the section labels."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1765
#, no-c-format
-msgid "<literal>labelPaint</literal>— The color used to draw the section labels"
-msgstr ""
+msgid "<literal>labelPaint</literal> — The color used to draw the section labels"
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1770
#, no-c-format
-msgid "<literal>labelGap</literal>— The gap between the labels and the plot as a percentage of the plot width."
+msgid "<literal>labelGap</literal> — The gap between the labels and the plot as a percentage of the plot width."
msgstr ""
#. Tag: para
#: Itext.xml:1775
#, no-c-format
-msgid "<literal>labelBackgroundPaint</literal>— The color used to draw the background of the section labels. If this is null, the background is not filled."
+msgid "<literal>labelBackgroundPaint</literal> — The color used to draw the background of the section labels. If this is null, the background is not filled."
msgstr ""
#. Tag: para
#: Itext.xml:1782
#, no-c-format
-msgid "<literal>startAngle</literal>— The starting angle of the first section."
-msgstr ""
+msgid "<literal>startAngle</literal> — The starting angle of the first section."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1787
#, no-c-format
-msgid "<literal>circular</literal>— A boolean value indicating that the chart should be drawn as a circle. If false, the chart is drawn as an ellipse. The default is true."
+msgid "<literal>circular</literal> — A boolean value indicating that the chart should be drawn as a circle. If false, the chart is drawn as an ellipse. The default is true."
msgstr ""
#. Tag: para
#: Itext.xml:1793
#, no-c-format
-msgid "<literal>direction</literal>— The direction the pie section are drawn. One of: <literal>clockwise</literal> or <literal>anticlockwise</literal>. The default is <literal>clockwise</literal>."
+msgid "<literal>direction</literal> — The direction the pie section are drawn. One of: <literal>clockwise</literal> or <literal>anticlockwise</literal>. The default is <literal>clockwise</literal>."
msgstr ""
#. Tag: para
#: Itext.xml:1799
#, no-c-format
-msgid "<literal>sectionOutlinePaint</literal>— The outline paint for all sections."
-msgstr ""
+msgid "<literal>sectionOutlinePaint</literal> — The outline paint for all sections."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1804
#, no-c-format
-msgid "<literal>sectionOutlineStroke</literal>— The outline stroke for all sections"
-msgstr ""
+msgid "<literal>sectionOutlineStroke</literal> — The outline stroke for all sections"
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1809
#, no-c-format
-msgid "<literal>sectionOutlinesVisible</literal>— Indicates whether an outline is drawn for each section in the plot."
+msgid "<literal>sectionOutlinesVisible</literal> — Indicates whether an outline is drawn for each section in the plot."
msgstr ""
#. Tag: para
#: Itext.xml:1814
#, no-c-format
-msgid "<literal>baseSectionOutlinePaint</literal>— The base section outline paint."
-msgstr ""
+msgid "<literal>baseSectionOutlinePaint</literal> — The base section outline paint."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1819
#, no-c-format
-msgid "<literal>baseSectionPaint</literal>— The base section paint."
-msgstr ""
+msgid "<literal>baseSectionPaint</literal> — The base section paint."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:1823
#, no-c-format
-msgid "<literal>baseSectionOutlineStroke</literal>— The base section outline stroke."
-msgstr ""
+msgid "<literal>baseSectionOutlineStroke</literal> — The base section outline stroke."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: programlisting
#: Itext.xml:1831
@@ -1985,20 +2035,20 @@
#. Tag: para
#: Itext.xml:2123
#, no-c-format
-msgid "<literal>code</literal>— The value to be encoded by the barcode."
-msgstr "<literal>code</literal>— Il valore da codificare nel barcode."
+msgid "<literal>code</literal> — The value to be encoded by the barcode."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:2128
#, no-c-format
-msgid "<literal>xpos</literal>— For PDFs, the absolute y position of the barcode on the page."
-msgstr ""
+msgid "<literal>xpos</literal> — For PDFs, the absolute y position of the barcode on the page."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:2133
#, no-c-format
-msgid "<literal>ypos</literal>— For PDFs, the absolute y position of the barcode on the page."
-msgstr ""
+msgid "<literal>ypos</literal> — For PDFs, the absolute y position of the barcode on the page."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:2138
@@ -2191,8 +2241,8 @@
#. Tag: para
#: Itext.xml:2339
#, no-c-format
-msgid "<literal>height</literal> — ..The height of the component to be rendered."
-msgstr ""
+msgid "<literal>height</literal> — The height of the component to be rendered."
+msgstr "<literal>code</literal> — Il valore da codificare nel barcode."
#. Tag: para
#: Itext.xml:2343
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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: 2009-01-03 12:17+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:21+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -534,8 +534,8 @@
#. Tag: para
#: Jbpm.xml:312
#, no-c-format
-msgid "If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal> phase—during a <literal>@Factory</literal> or <literal>@Create</literal> method, for example—we consider ourselves to be already at the page being rendered, and use a <literal><start-page></literal> node as the first node in the pageflow, as in the example above."
-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."
+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 "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
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Jms.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Jms.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Jms.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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: 2009-01-11 18:45+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:22+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -22,14 +22,14 @@
#. Tag: para
#: Jms.xml:3
#, no-c-format
-msgid "Seam makes it very easy to perform work asynchronously from a web request. When most people think of asynchronicity in Java EE, they think of using JMS. This is certainly one way to approach the problem in Seam, and is the right way when you have strict and well-defined quality of service requirements. Seam makes it easy to send and recieve JMS messages using Seam components."
+msgid "Seam makes it very easy to perform work asynchronously from a web request. When most people think of asynchronicity in Java EE, they think of using JMS. This is certainly one way to approach the problem in Seam, and is the right way when you have strict and well-defined quality of service requirements. Seam makes it easy to send and receive JMS messages using Seam components."
msgstr "Seam semplifica molto l'esecuzione di lavori asincroni da richiesta web. Quando la maggior parte delle persone pensa all'asincronicità in Java EE, pensano all'uso di JMS. Questo è certamente un modo per approcciare il problema in Seam, ed è quello giusto quando si hanno dei requisiti di qualità di servizio molto stringenti e ben definiti. Seam semplifica l'invio e la ricezione di messaggi JMS usando i componenti Seam."
# rivedere la frase.
#. Tag: para
#: Jms.xml:11
#, no-c-format
-msgid "But for many usecases, JMS is overkill. Seam layers a simple asynchronous method and event facility over your choice of <emphasis>dispatchers</emphasis>:"
+msgid "But for many use cases, JMS is overkill. Seam layers a simple asynchronous method and event facility over your choice of <emphasis>dispatchers</emphasis>:"
msgstr "Ma per molti casi d'uso, JMS è eccessivo. Seam aggiunge come nuovo layer un semplice metodo asincrono ed un meccanismo d'eventi sulla scelta del <emphasis>dispatcher</emphasis>:"
#. Tag: para
@@ -715,8 +715,8 @@
#. Tag: para
#: Jms.xml:210
#, no-c-format
-msgid "Here, for example, using <literal>java.util.concurrent</literal> dispatcher, we inject it's control object and cancel all future invocations when an exception is encountered"
-msgstr "Per esempio, usando il dispatcher <literal>java.util.concurrent</literal>, viene iniettato il suo oggetto di controllo e vengono cancellate tutte le future invocazioni quando si incontra un'eccezione "
+msgid "Here, for example, using <literal>java.util.concurrent</literal> dispatcher, we inject its control object and cancel all future invocations when an exception is encountered"
+msgstr "Per esempio, usando il dispatcher <literal>java.util.concurrent</literal>, viene iniettato il suo oggetto di controllo e vengono cancellate tutte le future invocazioni quando si incontra un'eccezione."
#. Tag: para
#: Jms.xml:216
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Persistence.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Persistence.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Persistence.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,7 +5,7 @@
msgstr ""
"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"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
"PO-Revision-Date: 2008-12-30 12:24+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
@@ -22,7 +22,11 @@
#. Tag: para
#: Persistence.xml:4
#, no-c-format
-msgid "Seam provides extensive support for the two most popular persistence architectures for Java: Hibernate3, and the Java Persistence API introduced with EJB 3.0. Seam's unique state-management architecture allows the most sophisticated ORM integration of any web application framework."
+msgid ""
+"Seam provides extensive support for the two most popular persistence "
+"architectures for Java: Hibernate3, and the Java Persistence API introduced "
+"with EJB 3.0. Seam's unique state-management architecture allows the most "
+"sophisticated ORM integration of any web application framework."
msgstr ""
#. Tag: title
@@ -34,37 +38,75 @@
#. Tag: para
#: Persistence.xml:15
#, no-c-format
-msgid "Seam grew out of the frustration of the Hibernate team with the statelessness typical of the previous generation of Java application architectures. The state management architecture of Seam was originally designed to solve problems relating to persistence—in particular problems associated with <emphasis>optimistic transaction processing</emphasis>. Scalable online applications always use optimistic transactions. An atomic (database/JTA) level transaction should not span a user interaction unless the application is designed to support only a very small number of concurrent clients. But almost all interesting work involves first displaying data to a user, and then, slightly later, updating the same data. So Hibernate was designed to support the idea of a persistence context which spanned an optimistic transaction."
+msgid ""
+"Seam grew out of the frustration of the Hibernate team with the "
+"statelessness typical of the previous generation of Java application "
+"architectures. The state management architecture of Seam was originally "
+"designed to solve problems relating to persistence — in particular "
+"problems associated with <emphasis>optimistic transaction processing</"
+"emphasis>. Scalable online applications always use optimistic transactions. "
+"An atomic (database/JTA) level transaction should not span a user "
+"interaction unless the application is designed to support only a very small "
+"number of concurrent clients. But almost all interesting work involves first "
+"displaying data to a user, and then, slightly later, updating the same data. "
+"So Hibernate was designed to support the idea of a persistence context which "
+"spanned an optimistic transaction."
msgstr ""
#. Tag: para
#: Persistence.xml:30
#, no-c-format
-msgid "Unfortunately, the so-called \"stateless\" architectures that preceded Seam and EJB 3.0 had no construct for representing an optimistic transaction. So, instead, these architectures provided persistence contexts scoped to the atomic transaction. Of course, this resulted in many problems for users, and is the cause of the number one user complaint about Hibernate: the dreaded <literal>LazyInitializationException</literal>. What we need is a construct for representing an optimistic transaction in the application tier."
+msgid ""
+"Unfortunately, the so-called \"stateless\" architectures that preceded Seam "
+"and EJB 3.0 had no construct for representing an optimistic transaction. So, "
+"instead, these architectures provided persistence contexts scoped to the "
+"atomic transaction. Of course, this resulted in many problems for users, and "
+"is the cause of the number one user complaint about Hibernate: the dreaded "
+"<literal>LazyInitializationException</literal>. What we need is a construct "
+"for representing an optimistic transaction in the application tier."
msgstr ""
#. Tag: para
#: Persistence.xml:40
#, no-c-format
-msgid "EJB 3.0 recognizes this problem, and introduces the idea of a stateful component (a stateful session bean) with an <emphasis>extended persistence context</emphasis> scoped to the lifetime of the component. This is a partial solution to the problem (and is a useful construct in and of itself) however there are two problems:"
+msgid ""
+"EJB 3.0 recognizes this problem, and introduces the idea of a stateful "
+"component (a stateful session bean) with an <emphasis>extended persistence "
+"context</emphasis> scoped to the lifetime of the component. This is a "
+"partial solution to the problem (and is a useful construct in and of itself) "
+"however there are two problems:"
msgstr ""
#. Tag: para
#: Persistence.xml:50
#, no-c-format
-msgid "The lifecycle of the stateful session bean must be managed manually via code in the web tier (it turns out that this is a subtle problem and much more difficult in practice than it sounds)."
+msgid ""
+"The lifecycle of the stateful session bean must be managed manually via code "
+"in the web tier (it turns out that this is a subtle problem and much more "
+"difficult in practice than it sounds)."
msgstr ""
#. Tag: para
#: Persistence.xml:57
#, no-c-format
-msgid "Propagation of the persistence context between stateful components in the same optimistic transaction is possible, but tricky."
+msgid ""
+"Propagation of the persistence context between stateful components in the "
+"same optimistic transaction is possible, but tricky."
msgstr ""
#. Tag: para
#: Persistence.xml:64
#, no-c-format
-msgid "Seam solves the first problem by providing conversations, and stateful session bean components scoped to the conversation. (Most conversations actually represent optimistic transactions in the data layer.) This is sufficient for many simple applications (such as the Seam booking demo) where persistence context propagation is not needed. For more complex applications, with many loosly-interacting components in each conversation, propagation of the persistence context across components becomes an important issue. So Seam extends the persistence context management model of EJB 3.0, to provide conversation-scoped extended persistence contexts."
+msgid ""
+"Seam solves the first problem by providing conversations, and stateful "
+"session bean components scoped to the conversation. (Most conversations "
+"actually represent optimistic transactions in the data layer.) This is "
+"sufficient for many simple applications (such as the Seam booking demo) "
+"where persistence context propagation is not needed. For more complex "
+"applications, with many loosly-interacting components in each conversation, "
+"propagation of the persistence context across components becomes an "
+"important issue. So Seam extends the persistence context management model of "
+"EJB 3.0, to provide conversation-scoped extended persistence contexts."
msgstr ""
#. Tag: title
@@ -76,19 +118,33 @@
#. Tag: para
#: Persistence.xml:81
#, no-c-format
-msgid "EJB session beans feature declarative transaction management. The EJB container is able to start a transaction transparently when the bean is invoked, and end it when the invocation ends. If we write a session bean method that acts as a JSF action listener, we can do all the work associated with that action in one transaction, and be sure that it is committed or rolled back when we finish processing the action. This is a great feature, and all that is needed by some Seam applications."
+msgid ""
+"EJB session beans feature declarative transaction management. The EJB "
+"container is able to start a transaction transparently when the bean is "
+"invoked, and end it when the invocation ends. If we write a session bean "
+"method that acts as a JSF action listener, we can do all the work associated "
+"with that action in one transaction, and be sure that it is committed or "
+"rolled back when we finish processing the action. This is a great feature, "
+"and all that is needed by some Seam applications."
msgstr ""
#. Tag: para
#: Persistence.xml:90
#, no-c-format
-msgid "However, there is a problem with this approach. A Seam application may not perform all data access for a request from a single method call to a session bean."
+msgid ""
+"However, there is a problem with this approach. A Seam application may not "
+"perform all data access for a request from a single method call to a session "
+"bean."
msgstr ""
#. Tag: para
#: Persistence.xml:97
#, no-c-format
-msgid "The request might require processing by several loosly-coupled components, each of which is called independently from the web layer. It is common to see several or even many calls per request from the web layer to EJB components in Seam."
+msgid ""
+"The request might require processing by several loosly-coupled components, "
+"each of which is called independently from the web layer. It is common to "
+"see several or even many calls per request from the web layer to EJB "
+"components in Seam."
msgstr ""
#. Tag: para
@@ -100,49 +156,86 @@
#. Tag: para
#: Persistence.xml:110
#, no-c-format
-msgid "The more transactions per request, the more likely we are to encounter atomicity and isolation problems when our application is processing many concurrent requests. Certainly, all write operations should occur in the same transaction!"
+msgid ""
+"The more transactions per request, the more likely we are to encounter "
+"atomicity and isolation problems when our application is processing many "
+"concurrent requests. Certainly, all write operations should occur in the "
+"same transaction!"
msgstr ""
#. Tag: para
#: Persistence.xml:116
#, no-c-format
-msgid "Hibernate users developed the <emphasis>\"open session in view\"</emphasis> pattern to work around this problem. In the Hibernate community, \"open session in view\" was historically even more important because frameworks like Spring use transaction-scoped persistence contexts. So rendering the view would cause <literal>LazyInitializationException</literal>s when unfetched associations were accessed."
+msgid ""
+"Hibernate users developed the <emphasis>\"open session in view\"</emphasis> "
+"pattern to work around this problem. In the Hibernate community, \"open "
+"session in view\" was historically even more important because frameworks "
+"like Spring use transaction-scoped persistence contexts. So rendering the "
+"view would cause <literal>LazyInitializationException</literal>s when "
+"unfetched associations were accessed."
msgstr ""
#. Tag: para
#: Persistence.xml:124
#, no-c-format
-msgid "This pattern is usually implemented as a single transaction which spans the entire request. There are several problems with this implementation, the most serious being that we can never be sure that a transaction is successful until we commit it—but by the time the \"open session in view\" transaction is committed, the view is fully rendered, and the rendered response may already have been flushed to the client. How can we notify the user that their transaction was unsuccessful?"
+msgid ""
+"This pattern is usually implemented as a single transaction which spans the "
+"entire request. There are several problems with this implementation, the "
+"most serious being that we can never be sure that a transaction is "
+"successful until we commit it — but by the time the \"open session in "
+"view\" transaction is committed, the view is fully rendered, and the "
+"rendered response may already have been flushed to the client. How can we "
+"notify the user that their transaction was unsuccessful?"
msgstr ""
#. Tag: para
#: Persistence.xml:133
#, no-c-format
-msgid "Seam solves both the transaction isolation problem and the association fetching problem, while working around the problems with \"open session in view\". The solution comes in two parts:"
+msgid ""
+"Seam solves both the transaction isolation problem and the association "
+"fetching problem, while working around the problems with \"open session in "
+"view\". The solution comes in two parts:"
msgstr ""
#. Tag: para
#: Persistence.xml:141
#, no-c-format
-msgid "use an extended persistence context that is scoped to the conversation, instead of to the transaction"
+msgid ""
+"use an extended persistence context that is scoped to the conversation, "
+"instead of to the transaction"
msgstr ""
#. Tag: para
#: Persistence.xml:147
#, no-c-format
-msgid "use two transactions per request; the first spans the beginning of the restore view phase (some transaction managers begin the transaction later at the beginning of the apply request vaues phase) until the end of the invoke application phase; the second spans the render response phase"
+msgid ""
+"use two transactions per request; the first spans the beginning of the "
+"restore view phase (some transaction managers begin the transaction later at "
+"the beginning of the apply request vaues phase) until the end of the invoke "
+"application phase; the second spans the render response phase"
msgstr ""
#. Tag: para
#: Persistence.xml:156
#, no-c-format
-msgid "In the next section, we'll tell you how to set up a conversation-scope persistence context. But first we need to tell you how to enable Seam transaction management. Note that you can use conversation-scoped persistence contexts without Seam transaction management, and there are good reasons to use Seam transaction management even when you're not using Seam-managed persistence contexts. However, the two facilities were designed to work together, and work best when used together."
+msgid ""
+"In the next section, we'll tell you how to set up a conversation-scope "
+"persistence context. But first we need to tell you how to enable Seam "
+"transaction management. Note that you can use conversation-scoped "
+"persistence contexts without Seam transaction management, and there are good "
+"reasons to use Seam transaction management even when you're not using Seam-"
+"managed persistence contexts. However, the two facilities were designed to "
+"work together, and work best when used together."
msgstr ""
#. Tag: para
#: Persistence.xml:165
#, no-c-format
-msgid "Seam transaction management is useful even if you're using EJB 3.0 container-managed persistence contexts. But it is especially useful if you use Seam outside a Java EE 5 environment, or in any other case where you would use a Seam-managed persistence context."
+msgid ""
+"Seam transaction management is useful even if you're using EJB 3.0 container-"
+"managed persistence contexts. But it is especially useful if you use Seam "
+"outside a Java EE 5 environment, or in any other case where you would use a "
+"Seam-managed persistence context."
msgstr ""
#. Tag: title
@@ -154,7 +247,10 @@
#. Tag: para
#: Persistence.xml:175
#, no-c-format
-msgid "Seam transaction management is enabled by default for all JSF requests. If you want to <emphasis>disable</emphasis> this feature, you can do it in <literal>components.xml</literal>:"
+msgid ""
+"Seam transaction management is enabled by default for all JSF requests. If "
+"you want to <emphasis>disable</emphasis> this feature, you can do it in "
+"<literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -178,7 +274,13 @@
#. Tag: para
#: Persistence.xml:188
#, no-c-format
-msgid "Seam provides a transaction management abstraction for beginning, committing, rolling back, and synchronizing with a transaction. By default Seam uses a JTA transaction component that integrates with Container Managed and programmatic EJB transactions. If you are working in a Java EE 5 environment, you should install the EJB synchronization component in <literal>components.xml</literal>:"
+msgid ""
+"Seam provides a transaction management abstraction for beginning, "
+"committing, rolling back, and synchronizing with a transaction. By default "
+"Seam uses a JTA transaction component that integrates with Container Managed "
+"and programmatic EJB transactions. If you are working in a Java EE 5 "
+"environment, you should install the EJB synchronization component in "
+"<literal>components.xml</literal>:"
msgstr ""
#. Tag: programlisting
@@ -190,25 +292,40 @@
#. Tag: para
#: Persistence.xml:197
#, no-c-format
-msgid "However, if you are working in a non EE 5 container, Seam will try auto detect the transaction synchronization mechanism to use. However, if Seam is unable to detect the correct transaction synchronization to use, you may find you need configure one of the following:"
+msgid ""
+"However, if you are working in a non EE 5 container, Seam will try auto "
+"detect the transaction synchronization mechanism to use. However, if Seam is "
+"unable to detect the correct transaction synchronization to use, you may "
+"find you need configure one of the following:"
msgstr ""
#. Tag: para
#: Persistence.xml:204
#, no-c-format
-msgid "JPA RESOURCE_LOCAL transactions with the <literal>javax.persistence.EntityTransaction</literal> interface. <literal>EntityTransaction</literal> begins the transaction at the beginning of the apply request values phase."
+msgid ""
+"JPA RESOURCE_LOCAL transactions with the <literal>javax.persistence."
+"EntityTransaction</literal> interface. <literal>EntityTransaction</literal> "
+"begins the transaction at the beginning of the apply request values phase."
msgstr ""
#. Tag: para
#: Persistence.xml:212
#, no-c-format
-msgid "Hibernate managed transactions with the <literal>org.hibernate.Transaction</literal> interface. <literal>HibernateTransaction</literal> begins the transaction at the beginning of the apply request values phase."
+msgid ""
+"Hibernate managed transactions with the <literal>org.hibernate.Transaction</"
+"literal> interface. <literal>HibernateTransaction</literal> begins the "
+"transaction at the beginning of the apply request values phase."
msgstr ""
#. Tag: para
#: Persistence.xml:220
#, no-c-format
-msgid "Spring managed transactions with the <literal>org.springframework.transaction.PlatformTransactionManager</literal> interface. The Spring <literal>PlatformTransactionManagement</literal> manager may begin the transaction at the beginning of the apply request values phase if the <literal>userConversationContext</literal> attribute is set."
+msgid ""
+"Spring managed transactions with the <literal>org.springframework."
+"transaction.PlatformTransactionManager</literal> interface. The Spring "
+"<literal>PlatformTransactionManagement</literal> manager may begin the "
+"transaction at the beginning of the apply request values phase if the "
+"<literal>userConversationContext</literal> attribute is set."
msgstr ""
#. Tag: para
@@ -220,7 +337,14 @@
#. Tag: para
#: Persistence.xml:234
#, no-c-format
-msgid "Configure JPA RESOURCE_LOCAL transaction management by adding the following to your components.xml where <literal>#{em}</literal> is the name of the <literal>persistence:managed-persistence-context</literal> component. If your managed persistence context is named <literal>entityManager</literal>, you can opt to leave out the <literal>entity-manager</literal> attribute. (see <link linkend=\"persistence.seam-managed-persistence-contexts\">Seam-managed persistence contexts</link> )"
+msgid ""
+"Configure JPA RESOURCE_LOCAL transaction management by adding the following "
+"to your components.xml where <literal>#{em}</literal> is the name of the "
+"<literal>persistence:managed-persistence-context</literal> component. If "
+"your managed persistence context is named <literal>entityManager</literal>, "
+"you can opt to leave out the <literal>entity-manager</literal> attribute. "
+"(see <link linkend=\"persistence.seam-managed-persistence-contexts\">Seam-"
+"managed persistence contexts</link> )"
msgstr ""
#. Tag: programlisting
@@ -232,19 +356,32 @@
#. Tag: para
#: Persistence.xml:245
#, no-c-format
-msgid "To configure Hibernate managed transactions declare the following in your components.xml where <literal>#{hibernateSession}</literal> is the name of the project's <literal>persistence:managed-hibernate-session</literal> component. If your managed hibernate session is named <literal>session</literal>, you can opt to leave out the <literal>session</literal> attribute. (see <link linkend=\"persistence.seam-managed-persistence-contexts\">Seam-managed persistence contexts</link> )"
+msgid ""
+"To configure Hibernate managed transactions declare the following in your "
+"components.xml where <literal>#{hibernateSession}</literal> is the name of "
+"the project's <literal>persistence:managed-hibernate-session</literal> "
+"component. If your managed hibernate session is named <literal>session</"
+"literal>, you can opt to leave out the <literal>session</literal> attribute. "
+"(see <link linkend=\"persistence.seam-managed-persistence-contexts\">Seam-"
+"managed persistence contexts</link> )"
msgstr ""
#. Tag: programlisting
#: Persistence.xml:255
#, no-c-format
-msgid "<![CDATA[<transaction:hibernate-transaction session=\"#{hibernateSession}\"/>]]>"
-msgstr "<![CDATA[<transaction:hibernate-transaction session=\"#{hibernateSession}\"/>]]>"
+msgid ""
+"<![CDATA[<transaction:hibernate-transaction session=\"#{hibernateSession}\"/"
+">]]>"
+msgstr ""
+"<![CDATA[<transaction:hibernate-transaction session=\"#{hibernateSession}\"/"
+">]]>"
#. Tag: para
#: Persistence.xml:256
#, no-c-format
-msgid "To explicitly disable Seam managed transactions declare the following in your components.xml:"
+msgid ""
+"To explicitly disable Seam managed transactions declare the following in "
+"your components.xml:"
msgstr ""
#. Tag: programlisting
@@ -256,7 +393,9 @@
#. Tag: para
#: Persistence.xml:260
#, no-c-format
-msgid "For configuring Spring managed transactions see <link linkend=\"spring-transactions\">using Spring PlatformTransactionManagement</link> ."
+msgid ""
+"For configuring Spring managed transactions see <link linkend=\"spring-"
+"transactions\">using Spring PlatformTransactionManagement</link> ."
msgstr ""
#. Tag: title
@@ -268,7 +407,17 @@
#. Tag: para
#: Persistence.xml:269
#, no-c-format
-msgid "Transaction synchronization provides callbacks for transaction related events such as <literal>beforeCompletion()</literal> and <literal>afterCompletion()</literal>. By default, Seam uses it's own transaction synchronization component which requires explicit use of the Seam transaction component when committing a transaction to ensure synchronization callbacks are correctly executed. If in a Java EE 5 environment the <literal><transaction:ejb-transaction/></literal> component should be be declared in <literal>components.xml</literal> to ensure that Seam synchronization callbacks are correctly called if the container commits a transaction outside of Seam's knowledge."
+msgid ""
+"Transaction synchronization provides callbacks for transaction related "
+"events such as <literal>beforeCompletion()</literal> and "
+"<literal>afterCompletion()</literal>. By default, Seam uses it's own "
+"transaction synchronization component which requires explicit use of the "
+"Seam transaction component when committing a transaction to ensure "
+"synchronization callbacks are correctly executed. If in a Java EE 5 "
+"environment the <literal><transaction:ejb-transaction/></literal> "
+"component should be be declared in <literal>components.xml</literal> to "
+"ensure that Seam synchronization callbacks are correctly called if the "
+"container commits a transaction outside of Seam's knowledge."
msgstr ""
#. Tag: title
@@ -280,19 +429,38 @@
#. Tag: para
#: Persistence.xml:285
#, no-c-format
-msgid "If you're using Seam outside of a Java EE 5 environment, you can't rely upon the container to manage the persistence context lifecycle for you. Even if you are in an EE 5 environment, you might have a complex application with many loosly coupled components that collaborate together in the scope of a single conversation, and in this case you might find that propagation of the persistence context between component is tricky and error-prone."
+msgid ""
+"If you're using Seam outside of a Java EE 5 environment, you can't rely upon "
+"the container to manage the persistence context lifecycle for you. Even if "
+"you are in an EE 5 environment, you might have a complex application with "
+"many loosly coupled components that collaborate together in the scope of a "
+"single conversation, and in this case you might find that propagation of the "
+"persistence context between component is tricky and error-prone."
msgstr ""
#. Tag: para
#: Persistence.xml:294
#, no-c-format
-msgid "In either case, you'll need to use a <emphasis>managed persistence context</emphasis> (for JPA) or a <emphasis>managed session</emphasis> (for Hibernate) in your components. A Seam-managed persistence context is just a built-in Seam component that manages an instance of <literal>EntityManager</literal> or <literal>Session</literal> in the conversation context. You can inject it with <literal>@In</literal>."
+msgid ""
+"In either case, you'll need to use a <emphasis>managed persistence context</"
+"emphasis> (for JPA) or a <emphasis>managed session</emphasis> (for "
+"Hibernate) in your components. A Seam-managed persistence context is just a "
+"built-in Seam component that manages an instance of <literal>EntityManager</"
+"literal> or <literal>Session</literal> in the conversation context. You can "
+"inject it with <literal>@In</literal>."
msgstr ""
#. Tag: para
#: Persistence.xml:302
#, no-c-format
-msgid "Seam-managed persistence contexts are extremely efficient in a clustered environment. Seam is able to perform an optimization that EJB 3.0 specification does not allow containers to use for container-managed extended persistence contexts. Seam supports transparent failover of extended persisence contexts, without the need to replicate any persistence context state between nodes. (We hope to fix this oversight in the next revision of the EJB spec.)"
+msgid ""
+"Seam-managed persistence contexts are extremely efficient in a clustered "
+"environment. Seam is able to perform an optimization that EJB 3.0 "
+"specification does not allow containers to use for container-managed "
+"extended persistence contexts. Seam supports transparent failover of "
+"extended persisence contexts, without the need to replicate any persistence "
+"context state between nodes. (We hope to fix this oversight in the next "
+"revision of the EJB spec.)"
msgstr ""
#. Tag: title
@@ -304,7 +472,9 @@
#. Tag: para
#: Persistence.xml:314
#, no-c-format
-msgid "Configuring a managed persistence context is easy. In <literal>components.xml</literal>, we can write:"
+msgid ""
+"Configuring a managed persistence context is easy. In <literal>components."
+"xml</literal>, we can write:"
msgstr ""
#. Tag: programlisting
@@ -313,22 +483,33 @@
msgid ""
"<![CDATA[<persistence:managed-persistence-context name=\"bookingDatabase\" \n"
" auto-create=\"true\"\n"
-" persistence-unit-jndi-name=\"java:/EntityManagerFactories/bookingData\"/>]]>"
+" persistence-unit-jndi-name=\"java:/EntityManagerFactories/"
+"bookingData\"/>]]>"
msgstr ""
"<![CDATA[<persistence:managed-persistence-context name=\"bookingDatabase\" \n"
" auto-create=\"true\"\n"
-" persistence-unit-jndi-name=\"java:/EntityManagerFactories/bookingData\"/>]]>"
+" persistence-unit-jndi-name=\"java:/EntityManagerFactories/"
+"bookingData\"/>]]>"
#. Tag: para
#: Persistence.xml:321
#, no-c-format
-msgid "This configuration creates a conversation-scoped Seam component named <literal>bookingDatabase</literal> that manages the lifecycle of <literal>EntityManager</literal> instances for the persistence unit (<literal>EntityManagerFactory</literal> instance) with JNDI name <literal>java:/EntityManagerFactories/bookingData</literal>."
+msgid ""
+"This configuration creates a conversation-scoped Seam component named "
+"<literal>bookingDatabase</literal> that manages the lifecycle of "
+"<literal>EntityManager</literal> instances for the persistence unit "
+"(<literal>EntityManagerFactory</literal> instance) with JNDI name "
+"<literal>java:/EntityManagerFactories/bookingData</literal>."
msgstr ""
#. Tag: para
#: Persistence.xml:328
#, no-c-format
-msgid "Of course, you need to make sure that you have bound the <literal>EntityManagerFactory</literal> into JNDI. In JBoss, you can do this by adding the following property setting to <literal>persistence.xml</literal>."
+msgid ""
+"Of course, you need to make sure that you have bound the "
+"<literal>EntityManagerFactory</literal> into JNDI. In JBoss, you can do this "
+"by adding the following property setting to <literal>persistence.xml</"
+"literal>."
msgstr ""
#. Tag: programlisting
@@ -356,7 +537,15 @@
#. Tag: para
#: Persistence.xml:342
#, no-c-format
-msgid "If you are using EJB3 and mark your class or method <literal>@TransactionAttribute(REQUIRES_NEW)</literal> then the transaction and persistence context shouldn't be propagated to method calls on this object. However as the Seam-managed persistence context is propagated to any component within the conversation, it will be propagated to methods marked <literal>REQUIRES_NEW</literal>. Therefore, if you mark a method <literal>REQUIRES_NEW</literal> then you should access the entity manager using @PersistenceContext."
+msgid ""
+"If you are using EJB3 and mark your class or method "
+"<literal>@TransactionAttribute(REQUIRES_NEW)</literal> then the transaction "
+"and persistence context shouldn't be propagated to method calls on this "
+"object. However as the Seam-managed persistence context is propagated to any "
+"component within the conversation, it will be propagated to methods marked "
+"<literal>REQUIRES_NEW</literal>. Therefore, if you mark a method "
+"<literal>REQUIRES_NEW</literal> then you should access the entity manager "
+"using @PersistenceContext."
msgstr ""
#. Tag: title
@@ -368,29 +557,37 @@
#. Tag: para
#: Persistence.xml:358
#, no-c-format
-msgid "Seam-managed Hibernate sessions are similar. In <literal>components.xml</literal>:"
+msgid ""
+"Seam-managed Hibernate sessions are similar. In <literal>components.xml</"
+"literal>:"
msgstr ""
#. Tag: programlisting
#: Persistence.xml:362
#, no-c-format
msgid ""
-"<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>\n"
+"<![CDATA[<persistence:hibernate-session-factory name="
+"\"hibernateSessionFactory\"/>\n"
"\n"
"<persistence:managed-hibernate-session name=\"bookingDatabase\" \n"
" auto-create=\"true\"\n"
-" session-factory-jndi-name=\"java:/bookingSessionFactory\"/>]]>"
+" session-factory-jndi-name=\"java:/bookingSessionFactory\"/"
+">]]>"
msgstr ""
-"<![CDATA[<persistence:hibernate-session-factory name=\"hibernateSessionFactory\"/>\n"
+"<![CDATA[<persistence:hibernate-session-factory name="
+"\"hibernateSessionFactory\"/>\n"
"\n"
"<persistence:managed-hibernate-session name=\"bookingDatabase\" \n"
" auto-create=\"true\"\n"
-" session-factory-jndi-name=\"java:/bookingSessionFactory\"/>]]>"
+" session-factory-jndi-name=\"java:/bookingSessionFactory\"/"
+">]]>"
#. Tag: para
#: Persistence.xml:364
#, no-c-format
-msgid "Where <literal>java:/bookingSessionFactory</literal> is the name of the session factory specified in <literal>hibernate.cfg.xml</literal>."
+msgid ""
+"Where <literal>java:/bookingSessionFactory</literal> is the name of the "
+"session factory specified in <literal>hibernate.cfg.xml</literal>."
msgstr ""
#. Tag: programlisting
@@ -400,31 +597,42 @@
"<![CDATA[<session-factory name=\"java:/bookingSessionFactory\">\n"
" <property name=\"transaction.flush_before_completion\">true</property>\n"
" <property name=\"connection.release_mode\">after_statement</property>\n"
-" <property name=\"transaction.manager_lookup_class\">org.hibernate.transaction.JBossTransactionManagerLookup</property>\n"
-" <property name=\"transaction.factory_class\">org.hibernate.transaction.JTATransactionFactory</property>\n"
-" <property name=\"connection.datasource\">java:/bookingDatasource</property>\n"
+" <property name=\"transaction.manager_lookup_class\">org.hibernate."
+"transaction.JBossTransactionManagerLookup</property>\n"
+" <property name=\"transaction.factory_class\">org.hibernate.transaction."
+"JTATransactionFactory</property>\n"
+" <property name=\"connection.datasource\">java:/bookingDatasource</"
+"property>\n"
" ...\n"
"</session-factory>]]>"
msgstr ""
"<![CDATA[<session-factory name=\"java:/bookingSessionFactory\">\n"
" <property name=\"transaction.flush_before_completion\">true</property>\n"
" <property name=\"connection.release_mode\">after_statement</property>\n"
-" <property name=\"transaction.manager_lookup_class\">org.hibernate.transaction.JBossTransactionManagerLookup</property>\n"
-" <property name=\"transaction.factory_class\">org.hibernate.transaction.JTATransactionFactory</property>\n"
-" <property name=\"connection.datasource\">java:/bookingDatasource</property>\n"
+" <property name=\"transaction.manager_lookup_class\">org.hibernate."
+"transaction.JBossTransactionManagerLookup</property>\n"
+" <property name=\"transaction.factory_class\">org.hibernate.transaction."
+"JTATransactionFactory</property>\n"
+" <property name=\"connection.datasource\">java:/bookingDatasource</"
+"property>\n"
" ...\n"
"</session-factory>]]>"
#. Tag: para
#: Persistence.xml:371
#, no-c-format
-msgid "Note that Seam does not flush the session, so you should always enable <literal>hibernate.transaction.flush_before_completion</literal> to ensure that the session is automatically flushed before the JTA transaction commits."
+msgid ""
+"Note that Seam does not flush the session, so you should always enable "
+"<literal>hibernate.transaction.flush_before_completion</literal> to ensure "
+"that the session is automatically flushed before the JTA transaction commits."
msgstr ""
#. Tag: para
#: Persistence.xml:378
#, no-c-format
-msgid "We can now have a managed Hibernate <literal>Session</literal> injected into our JavaBean components using the following code:"
+msgid ""
+"We can now have a managed Hibernate <literal>Session</literal> injected into "
+"our JavaBean components using the following code:"
msgstr ""
#. Tag: programlisting
@@ -442,25 +650,51 @@
#. Tag: para
#: Persistence.xml:389
#, no-c-format
-msgid "Persistence contexts scoped to the conversation allows you to program optimistic transactions that span multiple requests to the server without the need to use the <literal>merge()</literal> operation , without the need to re-load data at the beginning of each request, and without the need to wrestle with the <literal>LazyInitializationException</literal> or <literal>NonUniqueObjectException</literal>."
+msgid ""
+"Persistence contexts scoped to the conversation allows you to program "
+"optimistic transactions that span multiple requests to the server without "
+"the need to use the <literal>merge()</literal> operation , without the need "
+"to re-load data at the beginning of each request, and without the need to "
+"wrestle with the <literal>LazyInitializationException</literal> or "
+"<literal>NonUniqueObjectException</literal>."
msgstr ""
#. Tag: para
#: Persistence.xml:398
#, no-c-format
-msgid "As with any optimistic transaction management, transaction isolation and consistency can be achieved via use of optimistic locking. Fortunately, both Hibernate and EJB 3.0 make it very easy to use optimistic locking, by providing the <literal>@Version</literal> annotation."
+msgid ""
+"As with any optimistic transaction management, transaction isolation and "
+"consistency can be achieved via use of optimistic locking. Fortunately, both "
+"Hibernate and EJB 3.0 make it very easy to use optimistic locking, by "
+"providing the <literal>@Version</literal> annotation."
msgstr ""
#. Tag: para
#: Persistence.xml:405
#, no-c-format
-msgid "By default, the persistence context is flushed (synchronized with the database) at the end of each transaction. This is sometimes the desired behavior. But very often, we would prefer that all changes are held in memory and only written to the database when the conversation ends successfully. This allows for truly atomic conversations. As the result of a truly stupid and shortsighted decision by certain non-JBoss, non-Sun and non-Sybase members of the EJB 3.0 expert group, there is currently no simple, usable and portable way to implement atomic conversations using EJB 3.0 persistence. However, Hibernate provides this feature as a vendor extension to the <literal>FlushModeType</literal>s defined by the specification, and it is our expectation that other vendors will soon provide a similar extension."
+msgid ""
+"By default, the persistence context is flushed (synchronized with the "
+"database) at the end of each transaction. This is sometimes the desired "
+"behavior. But very often, we would prefer that all changes are held in "
+"memory and only written to the database when the conversation ends "
+"successfully. This allows for truly atomic conversations. As the result of a "
+"truly stupid and shortsighted decision by certain non-JBoss, non-Sun and non-"
+"Sybase members of the EJB 3.0 expert group, there is currently no simple, "
+"usable and portable way to implement atomic conversations using EJB 3.0 "
+"persistence. However, Hibernate provides this feature as a vendor extension "
+"to the <literal>FlushModeType</literal>s defined by the specification, and "
+"it is our expectation that other vendors will soon provide a similar "
+"extension."
msgstr ""
#. Tag: para
#: Persistence.xml:419
#, no-c-format
-msgid "Seam lets you specify <literal>FlushModeType.MANUAL</literal> when beginning a conversation. Currently, this works only when Hibernate is the underlying persistence provider, but we plan to support other equivalent vendor extensions."
+msgid ""
+"Seam lets you specify <literal>FlushModeType.MANUAL</literal> when beginning "
+"a conversation. Currently, this works only when Hibernate is the underlying "
+"persistence provider, but we plan to support other equivalent vendor "
+"extensions."
msgstr ""
#. Tag: programlisting
@@ -484,7 +718,9 @@
#. Tag: para
#: Persistence.xml:427
#, no-c-format
-msgid "Now, the <literal>claim</literal> object remains managed by the persistence context for the rest ot the conversation. We can make changes to the claim:"
+msgid ""
+"Now, the <literal>claim</literal> object remains managed by the persistence "
+"context for the rest ot the conversation. We can make changes to the claim:"
msgstr ""
#. Tag: programlisting
@@ -504,7 +740,9 @@
#. Tag: para
#: Persistence.xml:434
#, no-c-format
-msgid "But these changes will not be flushed to the database until we explicitly force the flush to occur:"
+msgid ""
+"But these changes will not be flushed to the database until we explicitly "
+"force the flush to occur:"
msgstr ""
#. Tag: programlisting
@@ -524,7 +762,9 @@
#. Tag: para
#: Persistence.xml:441
#, no-c-format
-msgid "Of course, you could set the <literal>flushMode</literal> to <literal>MANUAL</literal> from pages.xml, for example in a navigation rule:"
+msgid ""
+"Of course, you could set the <literal>flushMode</literal> to "
+"<literal>MANUAL</literal> from pages.xml, for example in a navigation rule:"
msgstr ""
#. Tag: programlisting
@@ -536,7 +776,8 @@
#. Tag: para
#: Persistence.xml:448
#, no-c-format
-msgid "You can set any Seam Managed Persistence Context to use manual flush mode:"
+msgid ""
+"You can set any Seam Managed Persistence Context to use manual flush mode:"
msgstr ""
#. Tag: programlisting
@@ -545,12 +786,14 @@
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
" xmlns:core=\"http://jboss.com/products/seam/core\">\n"
-" <core:manager conversation-timeout=\"120000\" default-flush-mode=\"manual\" />\n"
+" <core:manager conversation-timeout=\"120000\" default-flush-mode=\"manual"
+"\" />\n"
"</components>]]>"
msgstr ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
" xmlns:core=\"http://jboss.com/products/seam/core\">\n"
-" <core:manager conversation-timeout=\"120000\" default-flush-mode=\"manual\" />\n"
+" <core:manager conversation-timeout=\"120000\" default-flush-mode=\"manual"
+"\" />\n"
"</components>]]>"
#. Tag: title
@@ -562,13 +805,24 @@
#. Tag: para
#: Persistence.xml:462
#, no-c-format
-msgid "The <literal>EntityManager</literal> interface lets you access a vendor-specific API via the <literal>getDelegate()</literal> method. Naturally, the most interesting vendor is Hibernate, and the most powerful delegate interface is <literal>org.hibernate.Session</literal>. You'd be nuts to use anything else. Trust me, I'm not biased at all. If you must use a different JPA provider see <link linkend=\"alt-jpa-providers\">Using Alternate JPA Providers</link>."
+msgid ""
+"The <literal>EntityManager</literal> interface lets you access a vendor-"
+"specific API via the <literal>getDelegate()</literal> method. Naturally, the "
+"most interesting vendor is Hibernate, and the most powerful delegate "
+"interface is <literal>org.hibernate.Session</literal>. You'd be nuts to use "
+"anything else. Trust me, I'm not biased at all. If you must use a different "
+"JPA provider see <link linkend=\"alt-jpa-providers\">Using Alternate JPA "
+"Providers</link>."
msgstr ""
#. Tag: para
#: Persistence.xml:471
#, no-c-format
-msgid "But regardless of whether you're using Hibernate (genius!) or something else (masochist, or just not very bright), you'll almost certainly want to use the delegate in your Seam components from time to time. One approach would be the following:"
+msgid ""
+"But regardless of whether you're using Hibernate (genius!) or something else "
+"(masochist, or just not very bright), you'll almost certainly want to use "
+"the delegate in your Seam components from time to time. One approach would "
+"be the following:"
msgstr ""
#. Tag: programlisting
@@ -579,20 +833,26 @@
"\n"
"@Create\n"
"public void init() {\n"
-" ( (Session) entityManager.getDelegate() ).enableFilter(\"currentVersions\");\n"
+" ( (Session) entityManager.getDelegate() ).enableFilter(\"currentVersions"
+"\");\n"
"}]]>"
msgstr ""
"<![CDATA[@In EntityManager entityManager;\n"
"\n"
"@Create\n"
"public void init() {\n"
-" ( (Session) entityManager.getDelegate() ).enableFilter(\"currentVersions\");\n"
+" ( (Session) entityManager.getDelegate() ).enableFilter(\"currentVersions"
+"\");\n"
"}]]>"
#. Tag: para
#: Persistence.xml:480
#, no-c-format
-msgid "But typecasts are unquestionably the ugliest syntax in the Java language, so most people avoid them whenever possible. Here's a different way to get at the delegate. First, add the following line to <literal>components.xml</literal>:"
+msgid ""
+"But typecasts are unquestionably the ugliest syntax in the Java language, so "
+"most people avoid them whenever possible. Here's a different way to get at "
+"the delegate. First, add the following line to <literal>components.xml</"
+"literal>:"
msgstr ""
#. Tag: programlisting
@@ -642,17 +902,24 @@
#. Tag: para
#: Persistence.xml:498
#, no-c-format
-msgid "Seam proxies the <literal>EntityManager</literal> or <literal>Session</literal> object whenever you use a Seam-managed persistence context or inject a container managed persistence context using <literal>@PersistenceContext</literal>. This lets you use EL expressions in your query strings, safely and efficiently. For example, this:"
+msgid ""
+"Seam proxies the <literal>EntityManager</literal> or <literal>Session</"
+"literal> object whenever you use a Seam-managed persistence context or "
+"inject a container managed persistence context using "
+"<literal>@PersistenceContext</literal>. This lets you use EL expressions in "
+"your query strings, safely and efficiently. For example, this:"
msgstr ""
#. Tag: programlisting
#: Persistence.xml:506
#, no-c-format
msgid ""
-"<![CDATA[User user = em.createQuery(\"from User where username=#{user.username}\")\n"
+"<![CDATA[User user = em.createQuery(\"from User where username=#{user."
+"username}\")\n"
" .getSingleResult();]]>"
msgstr ""
-"<![CDATA[User user = em.createQuery(\"from User where username=#{user.username}\")\n"
+"<![CDATA[User user = em.createQuery(\"from User where username=#{user."
+"username}\")\n"
" .getSingleResult();]]>"
#. Tag: para
@@ -683,10 +950,12 @@
#: Persistence.xml:516
#, no-c-format
msgid ""
-"<![CDATA[User user = em.createQuery(\"from User where username=\" + user.getUsername()) //BAD!\n"
+"<![CDATA[User user = em.createQuery(\"from User where username=\" + user."
+"getUsername()) //BAD!\n"
" .getSingleResult();]]>"
msgstr ""
-"<![CDATA[User user = em.createQuery(\"from User where username=\" + user.getUsername()) //BAD!\n"
+"<![CDATA[User user = em.createQuery(\"from User where username=\" + user."
+"getUsername()) //BAD!\n"
" .getSingleResult();]]>"
#. Tag: para
@@ -704,13 +973,23 @@
#. Tag: para
#: Persistence.xml:527
#, no-c-format
-msgid "The coolest, and most unique, feature of Hibernate is <emphasis>filters</emphasis>. Filters let you provide a restricted view of the data in the database. You can find out more about filters in the Hibernate documentation. But we thought we'd mention an easy way to incorporate filters into a Seam application, one that works especially well with the Seam Application Framework."
+msgid ""
+"The coolest, and most unique, feature of Hibernate is <emphasis>filters</"
+"emphasis>. Filters let you provide a restricted view of the data in the "
+"database. You can find out more about filters in the Hibernate "
+"documentation. But we thought we'd mention an easy way to incorporate "
+"filters into a Seam application, one that works especially well with the "
+"Seam Application Framework."
msgstr ""
#. Tag: para
#: Persistence.xml:535
#, no-c-format
-msgid "Seam-managed persistence contexts may have a list of filters defined, which will be enabled whenever an <literal>EntityManager</literal> or Hibernate <literal>Session</literal> is first created. (Of course, they may only be used when Hibernate is the underlying persistence provider.)"
+msgid ""
+"Seam-managed persistence contexts may have a list of filters defined, which "
+"will be enabled whenever an <literal>EntityManager</literal> or Hibernate "
+"<literal>Session</literal> is first created. (Of course, they may only be "
+"used when Hibernate is the underlying persistence provider.)"
msgstr ""
#. Tag: programlisting
@@ -734,7 +1013,8 @@
"</persistence:filter>\n"
"\n"
"<persistence:managed-persistence-context name=\"personDatabase\"\n"
-" persistence-unit-jndi-name=\"java:/EntityManagerFactories/personDatabase\">\n"
+" persistence-unit-jndi-name=\"java:/EntityManagerFactories/personDatabase"
+"\">\n"
" <persistence:filters>\n"
" <value>#{regionFilter}</value>\n"
" <value>#{currentFilter}</value>\n"
@@ -758,10 +1038,10 @@
"</persistence:filter>\n"
"\n"
"<persistence:managed-persistence-context name=\"personDatabase\"\n"
-" persistence-unit-jndi-name=\"java:/EntityManagerFactories/personDatabase\">\n"
+" persistence-unit-jndi-name=\"java:/EntityManagerFactories/personDatabase"
+"\">\n"
" <persistence:filters>\n"
" <value>#{regionFilter}</value>\n"
" <value>#{currentFilter}</value>\n"
" </persistence:filters>\n"
"</persistence:managed-persistence-context>]]>"
-
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Preface.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Preface.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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-27 14:49+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:22+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -46,8 +46,8 @@
#. Tag: para
#: Preface.xml:32
#, no-c-format
-msgid "Unlike plain Java EE or J2EE components, Seam components may <emphasis>simultaneously</emphasis> access state associated with the web request and state held in transactional resources (without the need to propagate web request state manually via method parameters). You might object that the application layering imposed upon you by the old J2EE platform was a Good Thing. Well, nothing stops you creating an equivalent layered architecture using Seam—the difference is that <emphasis>you</emphasis> get to architect your own application and decide what the layers are and how they work together."
-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 imposta dalla vecchia piattaforma J2EE fosse una Cosa Buona. Bene, niente vieta di creare un'architettura a strati equivalente usando Seam— la differenza è che <emphasis>tu</emphasis> decidi l'architettura dell'applicazione e decidi quali sono i layer e come lavorano assieme"
+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 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 imposta dalla vecchia piattaforma J2EE fosse una Cosa Buona. Bene, niente vieta di creare un'architettura a strati equivalente usando Seam — la differenza è che <emphasis>tu</emphasis> decidi l'architettura dell'applicazione e decidi quali sono i layer e come lavorano assieme"
#. Tag: emphasis
#: Preface.xml:45
@@ -70,8 +70,8 @@
#. Tag: para
#: Preface.xml:61
#, no-c-format
-msgid "It is possible to write Seam applications where \"everything\" is an EJB. This may come as a surprise if you're used to thinking of EJBs as coarse-grained, so-called \"heavyweight\" objects. However, version 3.0 has completely changed the nature of EJB from the point of view of the developer. An EJB is a fine-grained object—nothing more complex than an annotated JavaBean. Seam even encourages you to use session beans as JSF action listeners!"
-msgstr "E' possibile scrivere applicazioni Seam dove \"qualsiasi cosa\" sia un EJB. Questo potrebbe essere sorprendente, se si è abituati 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 incoraggia ad usare i session bean come action listener JSF! "
+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 sorprendente, se si è abituati 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 incoraggia ad usare i session bean come action listener JSF! "
#. Tag: para
#: Preface.xml:69
@@ -143,8 +143,8 @@
#. Tag: para
#: Preface.xml:136
#, no-c-format
-msgid "Declarative application state management is made possible by the richness of the <emphasis>context model</emphasis> defined by Seam. Seam extends the context model defined by the servlet spec—request, session, application—with two new contexts—conversation and business process—that are more meaningful from the point of view of the business logic."
-msgstr "La gestione dichiarativa dello stato dell''applicazione è resa possibile grazie alla ricchezza del <emphasis>modello di contesto</emphasis> definito da Seam. Seam estende il modello di contesto definito dalla specifica servlet—richiesta, sessione, applicazione—con due nuovi contesti—conversazione e processo di business—che sono più significatici dal punto di vista della logica di business."
+msgid "Declarative application state management is made possible by the richness of the <emphasis>context model</emphasis> defined by Seam. Seam extends the context model defined by the servlet spec — request, session, application — with two new contexts — conversation and business process — that are more meaningful from the point of view of the business logic."
+msgstr "La gestione dichiarativa dello stato dell''applicazione è resa possibile grazie alla ricchezza del <emphasis>modello di contesto</emphasis> definito da Seam. Seam estende il modello di contesto definito dalla specifica servlet — richiesta, sessione, applicazione — con due nuovi contesti — conversazione e processo di business — che sono più significatici dal punto di vista della logica di business."
#. Tag: para
#: Preface.xml:143
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Rss.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Rss.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Rss.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: Seam_Reference_Guide\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-10-14 13:15+0000\n"
-"PO-Revision-Date: 2008-12-18 10:14+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:23+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: Italian <kde-i18n-it at lists.kde.org>\n"
"MIME-Version: 1.0\n"
@@ -144,38 +144,38 @@
#. Tag: para
#: Rss.xml:64
#, no-c-format
-msgid "<literal>uid</literal> —An optional unique feed id. The value is a string."
-msgstr "<literal>uid</literal> —Un identificativo unico opzionale. Il valore è una stringa."
+msgid "<literal>uid</literal> — An optional unique feed id. The value is a string."
+msgstr "<literal>uid</literal> — Un identificativo unico opzionale. Il valore è una stringa."
#. Tag: para
#: Rss.xml:70
#, no-c-format
-msgid "<literal>title</literal> —The title of the feed. The value is a string."
-msgstr "<literal>title</literal> —Il titolo del feed. Il valore è una stringa."
+msgid "<literal>title</literal> — The title of the feed. The value is a string."
+msgstr "<literal>title</literal> — Il titolo del feed. Il valore è una stringa."
#. Tag: para
#: Rss.xml:76
#, no-c-format
-msgid "<literal>subtitle</literal> —The subtitle of the feed. The value is a string."
-msgstr "<literal>subtitle</literal> —Il sottotitolo del feed. Il valore è una stringa."
+msgid "<literal>subtitle</literal> — The subtitle of the feed. The value is a string."
+msgstr "<literal>subtitle</literal> — Il sottotitolo del feed. Il valore è una stringa."
#. Tag: para
#: Rss.xml:82
#, no-c-format
-msgid "<literal>updated</literal> —When was the feed updated? The value is a date."
-msgstr "<literal>updated</literal> —Quando è stato aggiornato il feed? Il valore è una data."
+msgid "<literal>updated</literal> — When was the feed updated? The value is a date."
+msgstr "<literal>updated</literal> — Quando è stato aggiornato il feed? Il valore è una data."
#. Tag: para
#: Rss.xml:88
#, no-c-format
-msgid "<literal>link</literal> —The link to the source of the information. The value is a string."
-msgstr "<literal>link</literal> —Il link alla fonte dell'informazione. Il valore è una stringa."
+msgid "<literal>link</literal> — The link to the source of the information. The value is a string."
+msgstr "<literal>link</literal> — Il link alla fonte dell'informazione. Il valore è una stringa."
#. Tag: para
#: Rss.xml:95
#, no-c-format
-msgid "<literal>feedFormat</literal> —The feed format. The value is a string and defaults to ATOM1. Valid values are RSS10, RSS20, ATOM03 and ATOM10."
-msgstr "<literal>feedFormat</literal> —Il formato del feed. Il valore è una stringa con default ATOM1. I valori ammessi sono RSS10, RSS20, ATOM03 e ATOM10."
+msgid "<literal>feedFormat</literal> — The feed format. The value is a string and defaults to ATOM1. Valid values are RSS10, RSS20, ATOM03 and ATOM10."
+msgstr "<literal>feedFormat</literal> — Il formato del feed. Il valore è una stringa con default ATOM1. I valori ammessi sono RSS10, RSS20, ATOM03 e ATOM10."
#. Tag: emphasis
#: Rss.xml:103
@@ -220,50 +220,50 @@
#. Tag: para
#: Rss.xml:151
#, no-c-format
-msgid "<literal>uid</literal> —An optional unique entry id. The value is a string."
-msgstr "<literal>uid</literal> —Un identificativo unico opzionale. Il valore è una stringa."
+msgid "<literal>uid</literal> — An optional unique entry id. The value is a string."
+msgstr "<literal>uid</literal> — Un identificativo unico opzionale. Il valore è una stringa."
#. Tag: para
#: Rss.xml:157
#, no-c-format
-msgid "<literal>title</literal> —The title of the entry. The value is a string."
-msgstr "<literal>title</literal> —Il titolo dell'elemento. Il valore è una stringa."
+msgid "<literal>title</literal> — The title of the entry. The value is a string."
+msgstr "<literal>title</literal> — Il titolo dell'elemento. Il valore è una stringa."
#. Tag: para
#: Rss.xml:163
#, no-c-format
-msgid "<literal>link</literal> —A link to the item. The value is a string."
-msgstr "<literal>link</literal> —Un link all'articolo. Il valore è una stringa."
+msgid "<literal>link</literal> — A link to the item. The value is a string."
+msgstr "<literal>link</literal> — Un link all'articolo. Il valore è una stringa."
#. Tag: para
#: Rss.xml:169
#, no-c-format
-msgid "<literal>author</literal> —The author of the story. The value is a string."
-msgstr "<literal>author</literal> —L'autore dell'articolo. Il valore è una stringa."
+msgid "<literal>author</literal> — The author of the story. The value is a string."
+msgstr "<literal>author</literal> — L'autore dell'articolo. Il valore è una stringa."
#. Tag: para
#: Rss.xml:175
#, no-c-format
-msgid "<literal>summary</literal> —The body of the story. The value is a string."
-msgstr "<literal>summary</literal> —Il corpo dell'articolo. Il valore è una stringa."
+msgid "<literal>summary</literal> — The body of the story. The value is a string."
+msgstr "<literal>summary</literal> — Il corpo dell'articolo. Il valore è una stringa."
#. Tag: para
#: Rss.xml:181
#, no-c-format
-msgid "<literal>textFormat</literal> —The format of the body and title of the story. The value is a string and valid values are \"text\" and \"html\". Defaults to \"html\"."
-msgstr "<literal>textFormat</literal> —Il formato del corpo e del titolo dell'articolo. Il valore è una stringa e i valori ammessi sono \"text\" e \"html\". Il valore di default è \"html\"."
+msgid "<literal>textFormat</literal> — The format of the body and title of the story. The value is a string and valid values are \"text\" and \"html\". Defaults to \"html\"."
+msgstr "<literal>textFormat</literal> — Il formato del corpo e del titolo dell'articolo. Il valore è una stringa e i valori ammessi sono \"text\" e \"html\". Il valore di default è \"html\"."
#. Tag: para
#: Rss.xml:189
#, no-c-format
-msgid "<literal>published</literal> —When was the story first published? The value is a date."
-msgstr "<literal>published</literal> —Quando è stato pubblicato l'articolo? Il valore è una data."
+msgid "<literal>published</literal> — When was the story first published? The value is a date."
+msgstr "<literal>published</literal> — Quando è stato pubblicato l'articolo? Il valore è una data."
#. Tag: para
#: Rss.xml:195
#, no-c-format
-msgid "<literal>updated</literal> —When was the story updated? The value is a date."
-msgstr "<literal>updated</literal> —Quando è stato aggiornato l'articolo? Il valore è una data."
+msgid "<literal>updated</literal> — When was the story updated? The value is a date."
+msgstr "<literal>updated</literal> — Quando è stato aggiornato l'articolo? Il valore è una data."
#. Tag: title
#: Rss.xml:229
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Tutorial.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-01-05 00:19+0000\n"
-"PO-Revision-Date: 2009-01-11 20:26+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:25+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -1383,8 +1383,8 @@
#. 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."
-msgstr "Ma <literal>MessageManagerBean</literal> è anche responsabile per il recupero della lista dei messaggi la prima volta che si naviga nella pagina della lista messaggi. Ci sono vari modi in cui l'utente può navigare nella pagina, e non tutti sono preceduti da un'azione JSF—l'utente può avere un memorizzato la pagina, per esempio. Quindi il compito di recuperare la lista messaggi avviene in un <emphasis>metodo factory</emphasis> di Seam, invece che in un metodo action listener."
+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 "Ma <literal>MessageManagerBean</literal> è anche responsabile per il recupero della lista dei messaggi la prima volta che si naviga nella pagina della lista messaggi. Ci sono vari modi in cui l'utente può navigare nella pagina, e non tutti sono preceduti da un'azione JSF — l'utente può avere un memorizzato la pagina, per esempio. Quindi il compito di recuperare la lista messaggi avviene in un <emphasis>metodo factory</emphasis> di Seam, invece che in un metodo action listener."
#. Tag: para
#: Tutorial.xml:564
@@ -3110,7 +3110,7 @@
#. 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> transition, 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 "L'esempio indovina-numero contiene anche i pulsanti Giveup (abbandona) e Cheat (imbroglia). Si dovrebbe essere facilmente in grado di tracciare lo stato pageflow per le relative azioni. Si presti attenzione alla transizione <literal>cheat</literal>, che carica un sotto-processo per gestire tale flusso. Sebbene sia superfluo per quest'applicazione, questo dimostra come pageflow complessi possano venire spezzati in parti più piccole per renderle più facili da capire."
#. Tag: title
@@ -4180,7 +4180,7 @@
#. 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 association."
msgstr "L'istanza <varname>hotel</varname> viene iniettata dal contesto conversazione. L'hotel viene caricato tramite un <emphasis>contesto di persistenza esteso</emphasis> cosicché l'entity rimanga gestito lungo la conversazione. Questo consente di caricare in modo lazy la <varname>availableRooms</varname> tramite il metodo <varname>@Factory</varname> semplicemente seguendo l'associazione."
#. Tag: para
@@ -4544,7 +4544,7 @@
#. 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, its 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 "Annotare un'azione con <link linkend=\"end-annotation\"> <varname>@End(root=true)</varname> </link> termina la conversazione radice che distrugge effettivamente tutto lo stack delle conversazioni. Quando una conversazione termina, terminano anche le sue conversazioni innestate. Poiché la conversazione radice è quella che inizia tutto, questo è un modo semplice per distruggere e rilasciare tutto lo stato associato al workspace una volta confermata la prenotazione."
#. Tag: para
@@ -4700,8 +4700,8 @@
#. 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."
-msgstr "Se si arriva in quaste pagina da un segnalibro, come viene inizializzato <literal>#{blog.recentBlogEntries}</literal> usato da <literal><h:dataTable></literal>? <literal>Blog</literal> viene recuperato in modo lazy—\"tirato\"—quando serve, da un componente Seam chiamato <literal>blog</literal>. Questo è il flusso di controllo opposto a quello usato nei tradizionali framework web basati sull'azione, come ad esempio 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 "Se si arriva in quaste pagina da un segnalibro, come viene inizializzato <literal>#{blog.recentBlogEntries}</literal> usato da <literal><h:dataTable></literal>? <literal>Blog</literal> viene recuperato in modo lazy — \"tirato\" — quando serve, da un componente Seam chiamato <literal>blog</literal>. Questo è il flusso di controllo opposto a quello usato nei tradizionali framework web basati sull'azione, come ad esempio Struts."
#. Tag: programlisting
#: Tutorial.xml:1772
@@ -4752,8 +4752,8 @@
#. 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>."
-msgstr "L'annotazione <literal>@Unwrap</literal> impone a Seam di restituire il valore di ritorno del metodo—<literal>Blog</literal>—invece dell'attuale componente <literal>BlogService</literal> ai client. Questo è il <emphasis>manager component pattern</emphasis> di Seam."
+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 "L'annotazione <literal>@Unwrap</literal> impone a Seam di restituire il valore di ritorno del metodo — <literal>Blog</literal> — invece dell'attuale componente <literal>BlogService</literal> ai client. Questo è il <emphasis>manager component pattern</emphasis> di Seam."
#. Tag: para
#: Tutorial.xml:1792
@@ -4845,11 +4845,11 @@
#. 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 to 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 "Ma quando viene fatto il redirect, occorre includere i valori sottomessi con la form dentro l'URL per ottenere un URL memorizzabile come ad esempio <literal>http://localhost:8080/seam-blog/search/</literal>. JSF non fornisce un modo semplice per farlo, ma Seam sì. Per ottenere questo si usano due funzionalità di Seam: <emphasis>i parametri di pagina</emphasis> e <emphasis>la riscrittura dell'URL</emphasis>. Entrambi sono definiti in <literal>WEB-INF/pages.xml</literal>:"
#. Tag: programlisting
-#: Tutorial.xml:1830
+#: Tutorial.xml:1829
#, no-c-format
msgid ""
"<![CDATA[<pages>\n"
@@ -4875,37 +4875,37 @@
"</pages>]]>"
#. Tag: para
-#: Tutorial.xml:1833
+#: Tutorial.xml:1832
#, 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."
msgstr "Il parametro di pagina istruisce Seam a fare collegare il parametro di richiesta chiamato <literal>searchPattern</literal> al valore di <literal>#{searchService.searchPattern}</literal>, sia quando arriava una richiesta per la pagina di ricerca, sia quando viene generato un link alla pagina di ricerca. Seam si prende la responsabilità di mantenere il link tra lo stato dell'URL e lo stato dell'applicazione, mentre voi, come sviluppatori, non dovete preoccuparvene."
#. Tag: para
-#: Tutorial.xml:1840
+#: Tutorial.xml:1839
#, 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 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 "Senza riscrittura, l'URL di una ricerca di un termine <literal>book</literal> sarebbe <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal>. Questo può andare bene, ma Seam può semplificare l'URL usando una regola di riscrittura. La prima regola, per il pattern <literal>/search/{searchPattern}</literal>, dice che in ogni volta che si ha un URL per search.xhtml con un parametro di richiesta searchPattern, si può semplificare quest'URL. E quindi l'URL visto prima, <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal> viene riscritto come <literal>http://localhost:8080/seam-blog/search/book</literal>."
#. Tag: para
-#: Tutorial.xml:1850
+#: Tutorial.xml:1849
#, 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>."
msgstr "Come per i parametri di pagina, la riscrittura dell'URL è bidirezionale. Questo significa che Sean inoltra le richieste di URL più semplici alla giusta vista e genera automaticamente la vista più semplice per voi. Non serve preoccuparsi della costruzione dell'URL. Viene tutto gestito in modo trasparente dietro. L'unico requisito è che per usare la riscrittura dell'URL, occorre abilitare il filtro di riscrittura in <literal>components.xml</literal>."
#. Tag: programlisting
-#: Tutorial.xml:1858
+#: Tutorial.xml:1857
#, no-c-format
msgid "<web:rewrite-filter view-mapping="/seam/*" />"
msgstr "<web:rewrite-filter view-mapping="/seam/*" />"
#. Tag: para
-#: Tutorial.xml:1860
+#: Tutorial.xml:1859
#, no-c-format
msgid "The redirect takes us to the <literal>search.xhtml</literal> page:"
msgstr "Il redirect di porta alla pagina <literal>search.xhtml</literal>:"
#. Tag: programlisting
-#: Tutorial.xml:1862
+#: Tutorial.xml:1861
#, no-c-format
msgid ""
"<![CDATA[<h:dataTable value=\"#{searchResults}\" var=\"blogEntry\">\n"
@@ -4937,13 +4937,13 @@
"</h:dataTable>]]>"
#. Tag: para
-#: Tutorial.xml:1865
+#: Tutorial.xml:1864
#, no-c-format
msgid "Which again uses \"pull\"-style MVC to retrieve the actual search results using Hibernate Search."
msgstr "Il quale usa ancora MVC di tipo \"pull\" per recuperare i risultati di ricerca usando hibernate Search."
#. Tag: programlisting
-#: Tutorial.xml:1868
+#: Tutorial.xml:1867
#, no-c-format
msgid ""
"<![CDATA[@Name(\"searchService\")\n"
@@ -5053,25 +5053,25 @@
"]]>"
#. Tag: title
-#: Tutorial.xml:1874
+#: Tutorial.xml:1873
#, no-c-format
msgid "Using \"push\"-style MVC in a RESTful application"
msgstr "Uso di MVC push in un'applicazione RESTful"
#. Tag: para
-#: Tutorial.xml:1876
+#: Tutorial.xml:1875
#, 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."
msgstr "Alcune volte ha più senso usare MVC push-style per processare pagine RESTful, e quindi Seam fornisce la nozione di <emphasis>azione di pagina</emphasis>. L'esempio di Blog utilizza l'azione di pagina per pagina di entry del blog, <literal>entry.xhtml</literal>. Notare che questo è un pò forzato, sarebbe stato più facile usare anche qua lo stile MVC pull-style."
#. Tag: para
-#: Tutorial.xml:1881
+#: Tutorial.xml:1880
#, 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 "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
+#: Tutorial.xml:1883
#, no-c-format
msgid ""
"<![CDATA[@Name(\"entryAction\")\n"
@@ -5107,13 +5107,13 @@
"}]]>"
#. Tag: para
-#: Tutorial.xml:1887
+#: Tutorial.xml:1886
#, no-c-format
msgid "Page actions are also declared in <literal>pages.xml</literal>:"
msgstr "Le azione nella pagina vengono anche dichiarate in <literal>pages.xml</literal>:"
#. Tag: programlisting
-#: Tutorial.xml:1889
+#: Tutorial.xml:1888
#, no-c-format
msgid ""
"<![CDATA[<pages>\n"
@@ -5183,19 +5183,19 @@
"</pages>]]>"
#. Tag: para
-#: Tutorial.xml:1892
+#: Tutorial.xml:1891
#, 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."
msgstr "Notare che l'esempio utilizza azioni di pagina per la validazione e per il conteggio delle pagine visitate. Si noti anche l'uso di un parametro nel binding di metodo all'interno della azione di pagina. Questa non è una caratteristiva standard di JSF EL, ma Seam consente di usarla, non solo per le azioni di pagina, ma anche nei binding di metodo JSF."
#. Tag: para
-#: Tutorial.xml:1897
+#: Tutorial.xml:1896
#, 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:"
-msgstr "Quando la pagina <literal>entry.xhtml</literal> viene richiesta, Seam innanzitutto lega il parametro della pagina <literal>blogEntryId</literal> al modello. Si tenga presente che a causa della riscrittura dell'URL, il nome del parametro blogEntryId non verrà mostrato nell'URL. Seam quindi esegue l'azione, che recupera i dati necessari—<literal>blogEntry</literal>—e li colloca nel contesto di evento di Seam. Infine, viene generato il seguente:"
+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 "Quando la pagina <literal>entry.xhtml</literal> viene richiesta, Seam innanzitutto lega il parametro della pagina <literal>blogEntryId</literal> al modello. Si tenga presente che a causa della riscrittura dell'URL, il nome del parametro blogEntryId non verrà mostrato nell'URL. Seam quindi esegue l'azione, che recupera i dati necessari — <literal>blogEntry</literal> — e li colloca nel contesto di evento di Seam. Infine, viene generato il seguente:"
#. Tag: programlisting
-#: Tutorial.xml:1904
+#: Tutorial.xml:1903
#, no-c-format
msgid ""
"<![CDATA[<div class=\"blogEntry\">\n"
@@ -5225,13 +5225,13 @@
"</div>]]>"
#. Tag: para
-#: Tutorial.xml:1907
+#: Tutorial.xml:1906
#, 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>. 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
+#: Tutorial.xml:1910
#, no-c-format
msgid ""
"<![CDATA[@ApplicationException(rollback=true)\n"
@@ -5255,13 +5255,13 @@
"}]]>"
#. Tag: para
-#: Tutorial.xml:1914
+#: Tutorial.xml:1913
#, no-c-format
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
+#: Tutorial.xml:1915
#, no-c-format
msgid ""
"<![CDATA[@Name(\"entryAction\")\n"
@@ -5299,7 +5299,7 @@
"}]]>"
#. Tag: programlisting
-#: Tutorial.xml:1918
+#: Tutorial.xml:1917
#, no-c-format
msgid ""
"<![CDATA[<pages>\n"
@@ -5323,14 +5323,14 @@
"</pages>]]>"
#. Tag: para
-#: Tutorial.xml:1921
+#: Tutorial.xml:1920
#, no-c-format
msgid "It is a matter of taste which implementation you prefer."
msgstr "E' una questione di gusti su quale implementazione tu preferisca."
# fragment caching = ?
#. Tag: para
-#: Tutorial.xml:1924
+#: Tutorial.xml:1923
#, 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."
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Validation.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Validation.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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-25 14:52+0100\n"
+"POT-Creation-Date: 2009-01-18 15:00+0000\n"
+"PO-Revision-Date: 2009-01-18 16:25+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -220,8 +220,8 @@
#. 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 "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."
+msgid "This approach <emphasis>defines</emphasis> constraints on the model, and <emphasis>presents</emphasis> constraint violations in the view — a significantly better design."
+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
Modified: trunk/doc/Seam_Reference_Guide/it-IT/Xml.po
===================================================================
--- trunk/doc/Seam_Reference_Guide/it-IT/Xml.po 2009-01-18 15:23:57 UTC (rev 9947)
+++ trunk/doc/Seam_Reference_Guide/it-IT/Xml.po 2009-01-18 15:27:22 UTC (rev 9948)
@@ -5,8 +5,8 @@
msgstr ""
"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: 2009-01-11 12:45+0100\n"
+"POT-Creation-Date: 2009-01-18 15:01+0000\n"
+"PO-Revision-Date: 2009-01-18 16:26+0100\n"
"Last-Translator: Nicola Benaglia <nico.benaz at gmail.com>\n"
"Language-Team: none\n"
"MIME-Version: 1.0\n"
@@ -34,95 +34,95 @@
#. 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, via system properties, or via a properties file named <literal>seam.properties</literal> in the root of the classpath."
msgstr "I componenti Seam possono essere accompagnati da proprietà di configurazioni o via parametri di contesto servlet oppure tramite un file di proprietà chiamato <literal>seam.properties</literal> collocato nella radice del classpath."
#. 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, a system property named <literal>org.jboss.seam.properties.com.jboss.myapp.settings.locale</literal> via -D at startup, or as a servlet context parameter, and Seam will set the value of the <literal>locale</literal> attribute whenever it instantiates the component."
msgstr "Il componente Seam configurabile deve esporre metodi setter di stile JavaBeans per gli attributi configurabili. Se un componente Seam chiamato <literal>com.jboss.myapp.settings</literal> ha un metodo setter chiamato <literal>setLocale()</literal>, si può scrivere una proprietà chiamata <literal>com.jboss.myapp.settings.locale</literal> nel file <literal>seam.properties</literal> o come parametro di contesto servlet, e Seam imposterà il valore dell'attributo <literal>locale</literal> quando istanzia il componente."
#. Tag: para
-#: Xml.xml:31
+#: Xml.xml:32
#, 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>, <literal>seam.properties</literal>, or via a system property prefixed with <literal>org.jboss.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 "Lo stesso meccanismo viene usato per configurare lo stesso Seam. Per esempio, per impostare il timeout della conversazione, si fornisce un valore a <literal>org.jboss.seam.core.manager.conversationTimeout</literal> in <literal>web.xml</literal> oppure in <literal>seam.properties</literal>. (C'è un componente Seam predefinito chiamato <literal>org.jboss.seam.core.manager</literal> con metodo setter chiamato <literal>setConversationTimeout()</literal>.)"
#. Tag: title
-#: Xml.xml:41
+#: Xml.xml:43
#, no-c-format
msgid "Configuring components via <literal>components.xml</literal>"
msgstr "Configurazione dei componenti tramite <literal>components.xml</literal>"
#. Tag: para
-#: Xml.xml:43
+#: Xml.xml:45
#, no-c-format
msgid "The <literal>components.xml</literal> file is a bit more powerful than property settings. It lets you:"
msgstr "Il file <literal>components.xml</literal> è un poco più potente delle impostazioni di proprietà. Esso consente di:"
#. Tag: para
-#: Xml.xml:50
+#: Xml.xml:52
#, 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."
-msgstr "Configurare i componenti installati automaticamente—inclusi entrambi i componenti predefiniti ed i componenti di applicazione che sono stati annotati con l'annotazione <literal>@Name</literal> e rilevati dallo scanner di deploy di Seam."
+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 "Configurare i componenti installati automaticamente — inclusi entrambi i componenti predefiniti ed i componenti di applicazione che sono stati annotati con l'annotazione <literal>@Name</literal> e rilevati dallo scanner di deploy di Seam."
#. Tag: para
-#: Xml.xml:55
+#: Xml.xml:57
#, 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)."
-msgstr "Installare le classi senza annotazione <literal>@Name</literal> come componenti Seam—questo è ancora più utile per alcuni tipi di componenti infrastrutturali che possono essere installati diverse volte con diversi nomi (per esempio i contesti di persistenza gestiti da Seam)."
+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 with different names (for example Seam-managed persistence contexts)."
+msgstr "Installare le classi senza annotazione <literal>@Name</literal> come componenti Seam — questo è ancora più utile per alcuni tipi di componenti infrastrutturali che possono essere installati diverse volte con diversi nomi (per esempio i contesti di persistenza gestiti da Seam)."
#. Tag: para
-#: Xml.xml:60
+#: Xml.xml:62
#, 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."
msgstr "Installare componenti che <emphasis>hanno</emphasis> un'annotazione <literal>@Name</literal>, ma non vengono installati di default poiché una annotazione <literal>@Install</literal> indica che non devono essere installati."
#. Tag: para
-#: Xml.xml:65
+#: Xml.xml:67
#, no-c-format
msgid "Override the scope of a component."
msgstr "Override dello scope di un componente"
#. Tag: para
-#: Xml.xml:69
+#: Xml.xml:71
#, no-c-format
msgid "A <literal>components.xml</literal> file may appear in one of three different places:"
msgstr "Un file <literal>components.xml</literal> può apparire in una delle tre seguenti posizioni:"
#. Tag: para
-#: Xml.xml:75
+#: Xml.xml:77
#, no-c-format
msgid "The <literal>WEB-INF</literal> directory of a <literal>war</literal>."
msgstr "Nella directory <literal>WEB-INF</literal> di un file <literal>war</literal>."
#. Tag: para
-#: Xml.xml:78
+#: Xml.xml:80
#, no-c-format
msgid "The <literal>META-INF</literal> directory of a <literal>jar</literal>."
msgstr "Nella directory <literal>META-INF</literal> di un file <literal>jar</literal>."
#. Tag: para
-#: Xml.xml:81
+#: Xml.xml:83
#, no-c-format
msgid "Any directory of a <literal>jar</literal> that contains classes with an <literal>@Name</literal> annotation."
msgstr "In una qualsiasi directory di un file <literal>jar</literal> che contenga classi con annotazione <literal>@Name</literal>."
#. Tag: para
-#: Xml.xml:88
+#: Xml.xml:90
#, 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."
msgstr "Solitamente i componenti Seam vengono installati quando lo scanner di deploy scopre una classe con una annotazione <literal>@Name</literal> collocata in un archivio con un file <literal>seam.properties</literal> o un file <literal>META-INF/components.xml</literal>. (Amenoché il componente abbia una annotazione <literal>@Install</literal> che indichi che non debba essere installato di default). Il file <literal>components.xml</literal> consente di gestire i casi speciali in cui occorra fare override delle annotazioni."
#. Tag: para
-#: Xml.xml:97
+#: Xml.xml:99
#, no-c-format
msgid "For example, the following <literal>components.xml</literal> file installs jBPM:"
msgstr "Per esempio, il seguente file <literal>components.xml</literal> installa jBPM:"
#. Tag: programlisting
-#: Xml.xml:101
+#: Xml.xml:103
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
@@ -138,13 +138,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:103
+#: Xml.xml:105
#, no-c-format
msgid "This example does the same thing:"
msgstr "Questo esempio fa la stessa cosa:"
#. Tag: programlisting
-#: Xml.xml:107
+#: Xml.xml:109
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -156,13 +156,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:109
+#: Xml.xml:111
#, no-c-format
msgid "This one installs and configures two different Seam-managed persistence contexts:"
msgstr "Questo installa e configura due differenti contesti di persistenza gestiti da Seam:"
#. Tag: programlisting
-#: Xml.xml:113
+#: Xml.xml:115
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
@@ -188,13 +188,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:115
+#: Xml.xml:117
#, no-c-format
msgid "As does this one:"
msgstr "Ed anche questo fa lo stesso:"
#. Tag: programlisting
-#: Xml.xml:119
+#: Xml.xml:121
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -222,13 +222,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:121
+#: Xml.xml:123
#, no-c-format
msgid "This example creates a session-scoped Seam-managed persistence context (this is not recommended in practice):"
msgstr "Questo esempio crea un contesto di persistenza gestito da Seam con scope di sessione (questa non è una pratica raccomandata):"
#. Tag: programlisting
-#: Xml.xml:126
+#: Xml.xml:128
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
@@ -250,7 +250,7 @@
"</components>]]>"
#. Tag: programlisting
-#: Xml.xml:128
+#: Xml.xml:130
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -274,13 +274,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:130
+#: Xml.xml:132
#, 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."
msgstr "E' comune utilizzare l'opzione <literal>auto-create</literal> per gli oggetti infrastrutturali quali i contesti di persistenza, che risparmia dal dovere specificare esplicitamente <literal>create=true</literal> quando si usa l'annotazione <literal>@In</literal>."
#. Tag: programlisting
-#: Xml.xml:137
+#: Xml.xml:139
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\" \n"
@@ -302,7 +302,7 @@
"</components>]]>"
#. Tag: programlisting
-#: Xml.xml:139
+#: Xml.xml:141
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -326,13 +326,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:141
+#: Xml.xml:143
#, 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."
msgstr "La dichiarazione <literal><factory></literal> consente di specificare un valore o un'espressione di method binding che verrà valutata per inizializzare il valore di una variabile di contesto quando viene referenziata la prima volta."
#. Tag: programlisting
-#: Xml.xml:147
+#: Xml.xml:149
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -348,13 +348,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:149
+#: Xml.xml:151
#, no-c-format
msgid "You can create an \"alias\" (a second name) for a Seam component like so:"
msgstr "Si può creare un \"alias\" (un secondo nome) per un componente Seam in questo modo:"
#. Tag: programlisting
-#: Xml.xml:153
+#: Xml.xml:155
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -370,13 +370,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:155
+#: Xml.xml:157
#, no-c-format
msgid "You can even create an \"alias\" for a commonly used expression:"
msgstr "Si può anche creare un \"alias\" per un'espressione comunemente usata:"
#. Tag: programlisting
-#: Xml.xml:159
+#: Xml.xml:161
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -392,13 +392,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:161
+#: Xml.xml:163
#, no-c-format
msgid "It is especially common to see the use of <literal>auto-create=\"true\"</literal> with the <literal><factory></literal> declaration:"
msgstr "E' comune vedere usato <literal>auto-create=\"true\"</literal> con la dichiarazione <literal><factory></literal>:"
#. Tag: programlisting
-#: Xml.xml:166
+#: Xml.xml:168
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -414,31 +414,31 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:168
+#: Xml.xml:170
#, 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."
msgstr "A volte si vuole riutilizzare lo stesso file <literal>components.xml</literal> con piccoli cambiamenti durante il deploy ed il testing. Seam consente di mettere dei wildcard della forma <literal>@wildcard@</literal> nel file <literal>components.xml</literal> che può essere rimpiazzato o dallo script Ant (a deployment time) o fornendo un file chiamato <literal>components.properties</literal> nel classpath (a development time). Si vedrà usato quest'ultimo approccio negli esempi di Seam."
#. Tag: title
-#: Xml.xml:179
+#: Xml.xml:181
#, no-c-format
msgid "Fine-grained configuration files"
msgstr "File di configurazione a grana fine"
#. Tag: para
-#: Xml.xml:180
+#: Xml.xml:182
#, 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."
msgstr "Qualora si abbia un grande numero di componenti che devono essere configurati in XML, è più sensato suddividere l'informazione di <literal>components.xml</literal> in numerosi piccoli file. Seam consente di mettere la configurazione per una classe non anonima, per esempio, <literal>com.helloworld.Hello</literal> in una risorsa chiamata <literal>com/helloworld/Hello.component.xml</literal>. (Potresti essere familiare a questo pattern, poiché è lo stesso usato da Hibernate.) L'elemento radice del file può essere o un elemento <literal><components></literal> oppure <literal><component></literal>."
#. Tag: para
-#: Xml.xml:189
+#: Xml.xml:191
#, no-c-format
msgid "The first option lets you define multiple components in the file:"
msgstr "La prima opzione lascia definire nel file componenti multipli:"
#. Tag: programlisting
-#: Xml.xml:193
+#: Xml.xml:195
#, no-c-format
msgid ""
"<![CDATA[<components>\n"
@@ -456,13 +456,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:195
+#: Xml.xml:197
#, no-c-format
msgid "The second option only lets you define or configure one component, but is less noisy:"
msgstr "La seconda opzione lascia definire o configurare un solo componente, ma è meno rumorosa:"
#. Tag: programlisting
-#: Xml.xml:199
+#: Xml.xml:201
#, no-c-format
msgid ""
"<![CDATA[<component name=\"hello\">\n"
@@ -474,43 +474,43 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:201
+#: Xml.xml:203
#, no-c-format
msgid "In the second option, the class name is implied by the file in which the component definition appears."
msgstr "Nella seconda opzione, il nome della classe è implicato nel file in cui appare la definizione del componente."
#. Tag: para
-#: Xml.xml:206
+#: Xml.xml:208
#, 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>."
msgstr "In alternativa, si può mettere una configurazione per tutte le classi nel pacchetto <literal>com.helloworld</literal> in <literal>com/helloworld/components.xml</literal>."
#. Tag: title
-#: Xml.xml:213
+#: Xml.xml:215
#, no-c-format
msgid "Configurable property types"
msgstr "Tipi di proprietà configurabili"
#. Tag: para
-#: Xml.xml:214
+#: Xml.xml:216
#, no-c-format
msgid "Properties of string, primitive or primitive wrapper type may be configured just as you would expect:"
msgstr "Le proprietà dei tipi stringa, primitivi o wrapper primitivi possono essere configurati solo come atteso:"
#. Tag: programlisting
-#: Xml.xml:218
+#: Xml.xml:220
#, no-c-format
msgid "<![CDATA[org.jboss.seam.core.manager.conversationTimeout 60000]]>"
msgstr "<![CDATA[org.jboss.seam.core.manager.conversationTimeout 60000]]>"
#. Tag: programlisting
-#: Xml.xml:220
+#: Xml.xml:222
#, no-c-format
msgid "<![CDATA[<core:manager conversation-timeout=\"60000\"/>]]>"
msgstr "<![CDATA[<core:manager conversation-timeout=\"60000\"/>]]>"
#. Tag: programlisting
-#: Xml.xml:222
+#: Xml.xml:224
#, no-c-format
msgid ""
"<![CDATA[<component name=\"org.jboss.seam.core.manager\">\n"
@@ -522,19 +522,19 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:224
+#: Xml.xml:226
#, no-c-format
msgid "Arrays, sets and lists of strings or primitives are also supported:"
msgstr "Anche array, set e liste di stringhe o primitivi sono supportati:"
#. Tag: programlisting
-#: Xml.xml:228
+#: Xml.xml:230
#, no-c-format
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
+#: Xml.xml:232
#, no-c-format
msgid ""
"<![CDATA[<bpm:jbpm>\n"
@@ -554,7 +554,7 @@
"</bpm:jbpm>]]>"
#. Tag: programlisting
-#: Xml.xml:232
+#: Xml.xml:234
#, no-c-format
msgid ""
"<![CDATA[<component name=\"org.jboss.seam.bpm.jbpm\">\n"
@@ -574,13 +574,13 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:234
+#: Xml.xml:236
#, no-c-format
msgid "Even maps with String-valued keys and string or primitive values are supported:"
msgstr "Anche le mappe con chiavi associate a stringhe oppure valori stringa o primitivi sono supportati:"
#. Tag: programlisting
-#: Xml.xml:238
+#: Xml.xml:240
#, no-c-format
msgid ""
"<![CDATA[<component name=\"issueEditor\">\n"
@@ -600,19 +600,19 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:240
+#: Xml.xml:242
#, 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 "Quando si configurano le proprietò multi valore, di default Seam preserverà l'ordine in cui vengono messi gli attributi in <literal>components.xml</literal> (amenoché venga usato <literal>SortedSet</literal>/<literal>SortedMap</literal> allora Seam userà <literal>TreeMap</literal>/<literal>TreeSet</literal>). Se la proprietò ha un tipo concreto (per esempio <literal>LinkedList</literal>) Seam userà quel tipo."
#. Tag: para
-#: Xml.xml:246
+#: Xml.xml:248
#, no-c-format
msgid "You can also override the type by specifying a fully qualified class name:"
msgstr "Si può anche fare l'override del tipo specificando un nome di classe pienamente qualificato:"
#. Tag: programlisting
-#: Xml.xml:250
+#: Xml.xml:252
#, no-c-format
msgid ""
"<![CDATA[<component name=\"issueEditor\">\n"
@@ -632,13 +632,13 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:252
+#: Xml.xml:254
#, 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."
msgstr "Infine si può unire assieme i componenti usando un'espressione value-binding. Si noti che è diverso dall'usare l'iniezione con <literal>@In</literal>, poiché avviene al momento dell'istanziamento del componente invece che al momento dell'invocazione. E' quindi molto più simile alle strutture con dependency injection offerte dai tradizionali IoC container come JSF o Spring."
#. Tag: programlisting
-#: Xml.xml:260
+#: Xml.xml:262
#, no-c-format
msgid ""
"<![CDATA[<drools:managed-working-memory name=\"policyPricingWorkingMemory\"\n"
@@ -648,7 +648,7 @@
" rule-base=\"#{policyPricingRules}\"/>]]>"
#. Tag: programlisting
-#: Xml.xml:262
+#: Xml.xml:264
#, no-c-format
msgid ""
"<![CDATA[<component name=\"policyPricingWorkingMemory\"\n"
@@ -662,13 +662,13 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:264
+#: Xml.xml:266
#, 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."
msgstr "Seam risolve anche un'espressione stringa EL prima di assegnare il valore iniziale alla proprietà del bean del componente. Quindi si possono iniettare alcuni dati di contesto nei componenti."
#. Tag: programlisting
-#: Xml.xml:269
+#: Xml.xml:271
#, no-c-format
msgid ""
"<![CDATA[<component name=\"greeter\" class=\"com.example.action.Greeter\">\n"
@@ -680,13 +680,13 @@
"</component>]]>"
#. Tag: para
-#: Xml.xml:271
+#: Xml.xml:273
#, 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."
msgstr "C'è un'importante eccezione. Se un tipo di proprietà a cui il valore iniziale assegnato è o una <literal>ValueExpression</literal> di Seam o una <literal>MethodExpression</literal>, allora la valutazione di EL è rimandata. Invece il wrapper dell'espressione appropriata viene creato e assegnato alla proprietà. I modelli di messaggi nel componente Home dell'Applicazione Framework di Seam servono da esempio."
#. Tag: programlisting
-#: Xml.xml:279
+#: Xml.xml:281
#, no-c-format
msgid ""
"<![CDATA[<framework:entity-home name=\"myEntityHome\"\n"
@@ -698,25 +698,25 @@
" created-message=\"'#{myEntityHome.instance.name}' has been successfully added.\"/>]]>"
#. Tag: para
-#: Xml.xml:281
+#: Xml.xml:283
#, 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."
msgstr "Dentro il componente sipuò accedere all'espressione di stringa chiamando <literal>getExpressionString()</literal> sulla <literal>ValueExpression</literal> o <literal>MethodExpression</literal>. Se la proprietà è una <literal>ValueExpression</literal>, si può risolvere il valore usando <literal>getValue()</literal> e se la proprietà è un <literal>MethodExpression</literal>, si può invocare il metodo usando <literal>invoke(Object args...)</literal>. Ovviamente per assegnare un valore alla proprietà <literal>MethodExpression</literal>, l'intero valore iniziale deve essere una singola espressione EL."
#. Tag: title
-#: Xml.xml:294
+#: Xml.xml:296
#, no-c-format
msgid "Using XML Namespaces"
msgstr "Uso dei namespace XML"
#. Tag: para
-#: Xml.xml:295
+#: Xml.xml:297
#, 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:"
msgstr "Attraverso gli esempi ci sono stati due modi per dichiarare i componenti: con e senza l'uso di namespace XML. Il seguente mostra un tipico file <literal>components.xml</literal> senza namespace:"
#. Tag: programlisting
-#: Xml.xml:301
+#: Xml.xml:303
#, no-c-format
msgid ""
"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
@@ -742,19 +742,19 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:303
+#: Xml.xml:305
#, 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."
msgstr "Come si può vedere, è abbastanza prolisso. Ancor peggio, i nomi del componente e dell'attributo non possono essere validati a development time."
#. Tag: para
-#: Xml.xml:308
+#: Xml.xml:310
#, no-c-format
msgid "The namespaced version looks like this:"
msgstr "La versione con namespace appare come:"
#. Tag: programlisting
-#: Xml.xml:310
+#: Xml.xml:312
#, no-c-format
msgid ""
"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
@@ -782,25 +782,25 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:312
+#: Xml.xml:314
#, 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."
msgstr "Anche se le dichiarazioni di schema sono lunghe, il contenuto vero di XML è piatto e facile da capire. Gli schemi forniscono informazioni dettagliate su ogni componente e sugli attributi disponibili, consentendo agli editor XML di offrire un autocompletamento intelligente. L'uso di elementi con namespace semplifica molto la generazione ed il mantenimento in uno stato corretto dei file <literal>components.xml</literal>."
#. Tag: para
-#: Xml.xml:319
+#: Xml.xml:321
#, 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."
msgstr "Questo funziona bene per i componenti predefiniti di Seam, ma per i componenti creati dall'utente? Ci sono due opzioni. La prima, Seam supporta un misto dei due modelli, consentendo l'uso delle dichiarazioni generiche <literal><component></literal> for i componenti utente, assieme alle dichiarazioni con namespace dei componenti predefiniti. Ma ancor meglio, Seam consente di dichiarare in modo veloce i namespace per i propri componenti."
#. Tag: para
-#: Xml.xml:326
+#: Xml.xml:328
#, 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:"
msgstr "Qualsiasi pacchetto Java può essere associato ad un namespace XML annotando il pacchetto con l'annotazione <literal>@Namespace</literal>. (Le annotazioni a livello pacchetto vengono dichiarate in un file chiamato <literal>package-info.java</literal> nella directory del pacchetto.) Ecco un esempio tratto dalla demo seampay:"
#. Tag: programlisting
-#: Xml.xml:332
+#: Xml.xml:334
#, no-c-format
msgid ""
"@Namespace(value=\"http://jboss.com/products/seam/examples/seampay\")\n"
@@ -814,13 +814,13 @@
"import org.jboss.seam.annotations.Namespace;"
#. Tag: para
-#: Xml.xml:334
+#: Xml.xml:336
#, 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:"
msgstr "Questo è tutto ciò che bisogna fare per utilizzare lo stile namespace in <literal>components.xml</literal>! Adesso si può scrivere:"
#. Tag: programlisting
-#: Xml.xml:339
+#: Xml.xml:341
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
@@ -854,13 +854,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:341
+#: Xml.xml:343
#, no-c-format
msgid "<para>Or:</para>"
msgstr "<para>Oppure:</para>"
#. Tag: programlisting
-#: Xml.xml:343
+#: Xml.xml:345
#, no-c-format
msgid ""
"<![CDATA[<components xmlns=\"http://jboss.com/products/seam/components\"\n"
@@ -900,13 +900,13 @@
"</components>]]>"
#. Tag: para
-#: Xml.xml:345
+#: Xml.xml:347
#, 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:"
msgstr "Questi esempi illustrano i due usi modi d'uso di un elemento con namespace. Nella prima dichiarazione, <literal><pay:payment-home></literal> referenzia il componente <literal>paymentHome</literal>:"
#. Tag: programlisting
-#: Xml.xml:351
+#: Xml.xml:353
#, no-c-format
msgid ""
"<![CDATA[package org.jboss.seam.example.seampay;\n"
@@ -929,19 +929,19 @@
# hyphenated = ?
#. Tag: para
-#: Xml.xml:353
+#: Xml.xml:355
#, 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."
msgstr "Il nome dell'elemento è una forma con trattino d'unione del nome del componente. Gli attributi dell'elemento sono la forma con trattino dei nomi delle proprietà. "
#. Tag: para
-#: Xml.xml:358
+#: Xml.xml:360
#, 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:"
msgstr "Nella seconda dichiarazione, l'elemento <literal><pay:payment></literal> fa riferimento alla classe <literal>Payment</literal> nel pacchetto <literal>org.jboss.seam.example.seampay</literal>. In questo caso <literal>Payment</literal> è un entity dichiarato come componente Seam:"
#. Tag: programlisting
-#: Xml.xml:364
+#: Xml.xml:366
#, no-c-format
msgid ""
"<![CDATA[package org.jboss.seam.example.seampay;\n"
@@ -963,85 +963,85 @@
"}]]>"
#. Tag: para
-#: Xml.xml:366
+#: Xml.xml:368
#, 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."
msgstr "Se si vuole far funzionare la validazione e l'autocompletamento per i componenti definiti dall'utente, occorre uno schema. Seam non fornisce ancora un meccanismo per generare automaticamente uno schema per un set di componenti, così è necessario generarne uno manualmente. Come guida d'esempio si possono usare le definizioni di schema dei pacchetti standard di Seam."
#. Tag: para
-#: Xml.xml:373
+#: Xml.xml:375
#, no-c-format
msgid "The following are the the namespaces used by Seam:"
msgstr "Seam utilizza i seguenti namespace:"
#. Tag: para
-#: Xml.xml:377
+#: Xml.xml:379
#, no-c-format
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
+#: Xml.xml:382
#, no-c-format
msgid "core — <literal>http://jboss.com/products/seam/core</literal>"
msgstr "core — <literal>http://jboss.com/products/seam/core</literal>"
#. Tag: para
-#: Xml.xml:383
+#: Xml.xml:385
#, no-c-format
msgid "drools — <literal>http://jboss.com/products/seam/drools</literal>"
msgstr "drools — <literal>http://jboss.com/products/seam/drools</literal>"
#. Tag: para
-#: Xml.xml:386
+#: Xml.xml:388
#, no-c-format
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
+#: Xml.xml:391
#, no-c-format
msgid "jms — <literal>http://jboss.com/products/seam/jms</literal>"
msgstr "jms — <literal>http://jboss.com/products/seam/jms</literal>"
#. Tag: para
-#: Xml.xml:392
+#: Xml.xml:394
#, no-c-format
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
+#: Xml.xml:397
#, no-c-format
msgid "theme — <literal>http://jboss.com/products/seam/theme</literal>"
msgstr "theme — <literal>http://jboss.com/products/seam/theme</literal>"
#. Tag: para
-#: Xml.xml:398
+#: Xml.xml:400
#, no-c-format
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
+#: Xml.xml:403
#, no-c-format
msgid "mail — <literal>http://jboss.com/products/seam/mail</literal>"
msgstr "mail — <literal>http://jboss.com/products/seam/mail</literal>"
#. Tag: para
-#: Xml.xml:404
+#: Xml.xml:406
#, no-c-format
msgid "web — <literal>http://jboss.com/products/seam/web</literal>"
msgstr "web — <literal>http://jboss.com/products/seam/web</literal>"
#. Tag: para
-#: Xml.xml:407
+#: Xml.xml:409
#, no-c-format
msgid "pdf — <literal>http://jboss.com/products/seam/pdf</literal>"
msgstr "pdf — <literal>http://jboss.com/products/seam/pdf</literal>"
#. Tag: para
-#: Xml.xml:410
+#: Xml.xml:412
#, no-c-format
msgid "spring — <literal>http://jboss.com/products/seam/spring</literal>"
msgstr "spring — <literal>http://jboss.com/products/seam/spring</literal>"
More information about the seam-commits
mailing list