seam-commits June 2009

seam-commits@lists.jboss.org

1 participants
156 discussions

Seam SVN: r11068 - in tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide: bn-IN and 23 other directories.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2009-06-02 14:37:36 -0400 (Tue, 02 Jun 2009) New Revision: 11068 Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Annotations.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Author_Group.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Book_Info.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Cache.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Components.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Concepts.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Configuration.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Controls.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Conversations.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Dependencies.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Drools.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Elenhancements.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Events.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Excel.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Feedback.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Framework.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gettingstarted.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Glassfish.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Groovy.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Guice.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gwt.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Hsearch.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/I18n.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Itext.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jbpm.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jms.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Mail.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Performance.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Persistence.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Preface.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Remoting.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Revision_History.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Rss.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Security.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Spring.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Testing.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Text.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tools.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tutorial.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Validation.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Weblogic.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Webservices.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Websphere.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Wicket.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Xml.pot tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po Log: merge docs to 11066 Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" -"PO-Revision-Date: 2009-05-30 15:23+0100\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" +"PO-Revision-Date: 2009-06-01 20:52+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -58,8 +58,8 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:46 #, no-c-format -msgid "But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and Hibernate entities) don't become detatched during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter." -msgstr "Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei componenti JavaBean, Seam assicura che le istanze entity gestite (cioè entity JPA e Hibernate) non divengano detached durante la replica. Seam mantiene un record di entity che sono caricati e li carica automaticamente nel nodo secondario. Occorre comunque usare un contesto di persistenza gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate informazioni su questa funzionalità vengono fornite nella seconda parte del capitolo." +msgid "But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and Hibernate entities) don't become detached during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter." +msgstr "Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei componenti JavaBean, Seam assicura che le istanze entity gestite (cioè entity JPA e Hibernate) non divengano detached durante la replica. Seam mantiene un record di entity caricati e li carica automaticamente nel nodo secondario. Occorre comunque usare un contesto di persistenza gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate informazioni su questa funzionalità vengono fornite nella seconda parte del capitolo." #. Tag: para #: ClusteringAndEJBPassivation.xml:55 @@ -76,8 +76,8 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:62 #, no-c-format -msgid "Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered environment must implement the <literal>Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the session attribute on every change of the object." -msgstr "Un componente JavaBean mutabile con scope sessione o conversazione che verrà usato in un ambiente clustered deve implementare l'interfaccia <literal>Mutable</literal> dell'API Seam. Come parte del contratto, il contratto deve mantenere un dirty flag che viene segnato e resettato dal metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per determinare se è necessario replicare il componente. Questo evita di dover usare la più problematica API dei Servlet per aggiungere e rimuovere l'attributo sessione ad ogni cambiamento dell'oggetto." +msgid "Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered environment must implement the <literal>org.jboss.seam.core.Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the session attribute on every change of the object." +msgstr "Un componente JavaBean mutabile con scope sessione o conversazione che verrà usato in un ambiente clustered deve implementare l'interfaccia <literal>org.jboss.seam.core.Mutable</literal> dell'API Seam. Come parte del contratto, il contratto deve mantenere un dirty flag che viene segnato e resettato dal metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per determinare se è necessario replicare il componente. Questo evita di dover usare la più problematica API dei Servlet per aggiungere e rimuovere l'attributo sessione ad ogni cambiamento dell'oggetto." #. Tag: para #: ClusteringAndEJBPassivation.xml:70 @@ -94,7 +94,7 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:84 #, no-c-format -msgid "Please note that clustering does not work with hot deployable compoennts. But then again, you shouldn't be using hot deployable components in a non-development environment anyway." +msgid "Please note that clustering does not work with hot deployable components. But then again, you shouldn't be using hot deployable components in a non-development environment anyway." msgstr "Si noti che il clustering non funziona con componenti hot deployable. Ma comunque non si dovrebbero usare i componenti hot deployable in un ambiente non di sviluppo." #. Tag: title @@ -364,7 +364,7 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:260 #, no-c-format -msgid "The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not become detatched prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees)." +msgid "The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not become detached prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees)." msgstr "MEI serve per due scenari distinti (passivazione EJB e passivazione della sessione HTTP), sebbene raggiunge lo stesso obiettivo generale. Assicura che lungo la vita di una conversazione con l'uso di almeno un contesto di persistenza esteso, le istanze dell'entity caricate dal contesto di persistenza rimangano gestite (non divengano detached in modo prematuro da un evento passivation). In breve, assicura l'integrità del contesto di persistenza esteso (e quindi delle sue garanzie)." #. Tag: para @@ -424,7 +424,7 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:329 #, no-c-format -msgid "Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a compliment to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB." +msgid "Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a complement to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB." msgstr "Le conversazioni sono state inizialmente progettate avendo in mente gli stateful session bean (SFSB), in primo luogo poiché la specifica EJB3 indica gli SFSB come host del contesto di persistenza esteso. Seam introduce un complemento al contesto di persistenza esteso, conosciuto col nome di contesto di persistenza gestito da Seam, il quale risolve un certo numero di limitazioni presenti nella specifica (le regole complesse di propagazione e la mancanza di flush manuale). Entrambi possono essere usati con i SFSB." #. Tag: para @@ -436,7 +436,7 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:347 #, no-c-format -msgid "With all of that said, the Java EE container can passivate a SFSB, which means it will serialize the object to an area of storage external to the JVM. When this happens depends on the settings of the individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the guarnatees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this references at the beginning of the next invocation. Of course, Seam is! already storing the persistence manager in the conversation. Thus, when the SFSB passivates and later activates, it has absolutely no averse affect on the application." +msgid "With all of that said, the Java EE container can passivate a SFSB, which means it will serialize the object to an area of storage external to the JVM. When this happens depends on the settings of the individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the guarantees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this references at the beginning of the next invocation. Of course, Seam is! already storing the persistence manager in the conversation. Thus, when the SFSB passivates and later activates, it has absolutely no averse affect on the application." msgstr "Con tutto ciò detto, il container Java EE può passivare un SFSB, il che significa che verrà serializzato l'oggetto in un area di memorizzazione esterna alla JVM. Quando questo avviene dipende dalle impostazione del singolo SFSB. Questo processo può anche essere disabilitato. Comunque il contesto di persistenza non è serializzato (questo è vero solo per SMPC?). Infatti cosa succede dipende fortemente dal container Java EE. La specifica non è molto chiara in proposito. Molti vendor dicono di non fare avvenire questo se servono le garanzie del contesto di persistenza esteso. L'approccio di Seam più conservativo. Seam non si fida del SFSB con il contesto di persistenza o delle istanze entity. Dopo ogni invocazione del SFSB, Seam sposta il riferimento all'istanza entity mantenuta dal SFSB dentro l'attuale conversazione (e quindi nella sessione HTTP). mettendo a null questi campi nel SFSB. Poi ripristina questi riferimenri all'inizio di ogni invocazione. Certament! e Seam sta già memorizzando il gestore della persistenza nella conversazione. Perciò quando il SFSB passiva e poi si riattiva, non c'è alcun effetto negativo sull'applicazione." #. Tag: para Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Annotations.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Annotations.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Annotations.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Author_Group.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Author_Group.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Author_Group.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Book_Info.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Book_Info.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Book_Info.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Cache.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Cache.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Cache.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" @@ -95,7 +95,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -121,9 +121,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -159,7 +159,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -518,7 +518,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -628,7 +628,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -661,7 +661,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Components.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Components.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Components.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Concepts.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Concepts.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Concepts.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Configuration.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Configuration.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Configuration.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Controls.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Controls.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Controls.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Conversations.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Conversations.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Conversations.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Dependencies.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Dependencies.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Dependencies.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Drools.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Drools.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Drools.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Elenhancements.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Elenhancements.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Elenhancements.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Events.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Events.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Events.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Excel.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Excel.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Excel.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Feedback.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Feedback.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Feedback.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Framework.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Framework.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Framework.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gettingstarted.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gettingstarted.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gettingstarted.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Glassfish.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Glassfish.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Glassfish.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Groovy.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Groovy.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Groovy.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Guice.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Guice.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Guice.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gwt.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gwt.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Gwt.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Hsearch.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Hsearch.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Hsearch.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/I18n.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/I18n.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/I18n.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Itext.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Itext.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Itext.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jbpm.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jbpm.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jbpm.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jms.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jms.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Jms.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Mail.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Mail.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Mail.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Performance.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Performance.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Performance.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Persistence.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Persistence.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Persistence.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Preface.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Preface.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Preface.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Remoting.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Remoting.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Remoting.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Revision_History.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Revision_History.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Revision_History.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Rss.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Rss.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Rss.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Security.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Security.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Security.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Spring.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Spring.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Spring.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Testing.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Testing.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Testing.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Text.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Text.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Text.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tools.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tools.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tools.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tutorial.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tutorial.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Tutorial.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Validation.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Validation.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Validation.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Weblogic.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Weblogic.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Weblogic.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Webservices.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Webservices.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Webservices.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Websphere.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Websphere.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Websphere.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Wicket.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Wicket.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Wicket.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Xml.pot =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Xml.pot 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pot/Xml.pot 2009-06-02 18:37:36 UTC (rev 11068) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po 2009-06-02 13:00:58 UTC (rev 11067) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po 2009-06-02 18:37:36 UTC (rev 11068) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current "

15 years, 7 months

1
0
0 / 0

Seam SVN: r11067 - branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US.

by seam-commits＠lists.jboss.org

Author: manaRH Date: 2009-06-02 09:00:58 -0400 (Tue, 02 Jun 2009) New Revision: 11067 Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Components.xml Log: JBPAPP-2051 Modified: branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Components.xml =================================================================== --- branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Components.xml 2009-06-01 18:53:15 UTC (rev 11066) +++ branches/enterprise/JBPAPP_4_3_FP01/doc/Seam_Reference_Guide/en-US/Components.xml 2009-06-02 13:00:58 UTC (rev 11067) @@ -1023,15 +1023,15 @@ errors if the system is placed under any load and debug is enabled. </para> </listitem> + + + + + + + <listitem> <para> - <literal>org.jboss.seam.core.init.clientSideConversations</literal> — - if set to <literal>true</literal>, Seam will save conversation context - variables in the client instead of in the <literal>HttpSession</literal>. - </para> - </listitem> - <listitem> - <para> <literal>org.jboss.seam.core.init.userTransactionName</literal> — the JNDI name to use when looking up the JTA <literal>UserTransaction</literal> object. </para>

15 years, 7 months

1
0
0 / 0

Seam SVN: r11066 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT.

by seam-commits＠lists.jboss.org

Author: nico.ben Date: 2009-06-01 14:53:15 -0400 (Mon, 01 Jun 2009) New Revision: 11066 Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po Log: JBSEAM-3767: Italian translation of Seam guide Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-01 18:53:15 UTC (rev 11066) @@ -6,7 +6,7 @@ "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-06-01 18:34+0000\n" -"PO-Revision-Date: 2009-05-30 15:23+0100\n" +"PO-Revision-Date: 2009-06-01 20:52+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -23,45 +23,19 @@ #: ClusteringAndEJBPassivation.xml:7 #, no-c-format msgid "Please note that this chapter is still being reviewed. Tread carefully." -msgstr "" -"Si noti che questo capitolo è ancora sotto revisione. Maneggiare con cura." +msgstr "Si noti che questo capitolo è ancora sotto revisione. Maneggiare con cura." #. Tag: para #: ClusteringAndEJBPassivation.xml:10 #, no-c-format -msgid "" -"This chapter covers two distinct topics that happen share a common solution " -"in Seam, (web) clustering and EJB passivation. Therefore, they are addressed " -"together in this reference manual. Although performance tends to be grouped " -"in this category as well, it's kept separate because the focus of this " -"chapter is on the programming model and how it's affected by the use of the " -"aforementioned features." -msgstr "" -"Questo capitolo copre due distinti argomenti che condividono un soluzione " -"comune in Seam, (web) clustering e passivazione EJB. Quindi, sono trattati " -"assieme in questo manuale. Sebbene anche la performance tende ad essere " -"raggruppata in questa categoria, essa viene mantenuta separata poiché il " -"focus di questo capitolo è sul modello di programmazione e su come questo è " -"influenzato dall'uso delle funzionalità sopracitate." +msgid "This chapter covers two distinct topics that happen share a common solution in Seam, (web) clustering and EJB passivation. Therefore, they are addressed together in this reference manual. Although performance tends to be grouped in this category as well, it's kept separate because the focus of this chapter is on the programming model and how it's affected by the use of the aforementioned features." +msgstr "Questo capitolo copre due distinti argomenti che condividono un soluzione comune in Seam, (web) clustering e passivazione EJB. Quindi, sono trattati assieme in questo manuale. Sebbene anche la performance tende ad essere raggruppata in questa categoria, essa viene mantenuta separata poiché il focus di questo capitolo è sul modello di programmazione e su come questo è influenzato dall'uso delle funzionalità sopracitate." #. Tag: para #: ClusteringAndEJBPassivation.xml:17 #, no-c-format -msgid "" -"In this chapter you will learn how Seam manages the passivation of Seam " -"components and entity instances, how to activate this feature, and how this " -"feature is related to clustering. You will also learn how to deploy a Seam " -"application into a cluster and verify that HTTP session replication is " -"working properly. Let's start with a little background on clustering and see " -"an example of how you deploy a Seam application to a JBoss AS cluster." -msgstr "" -"In questo capitolo si apprenderà come Seam gestisce la passivazione dei " -"componenti Seam e degli entity, come attivare questa funzionalità e come " -"questa funzionalità è collegata al clustering. Inoltre si apprenderà come " -"eseguire il deploy di un'applicazione Seam in un cluster e verificare che la " -"replica della sessione HTTP funzioni correttamente. Iniziamo con un pò di " -"background sul clustering e vediamo come fare il deploy di un'applicazione " -"Seam in un cluster JBoss AS." +msgid "In this chapter you will learn how Seam manages the passivation of Seam components and entity instances, how to activate this feature, and how this feature is related to clustering. You will also learn how to deploy a Seam application into a cluster and verify that HTTP session replication is working properly. Let's start with a little background on clustering and see an example of how you deploy a Seam application to a JBoss AS cluster." +msgstr "In questo capitolo si apprenderà come Seam gestisce la passivazione dei componenti Seam e degli entity, come attivare questa funzionalità e come questa funzionalità è collegata al clustering. Inoltre si apprenderà come eseguire il deploy di un'applicazione Seam in un cluster e verificare che la replica della sessione HTTP funzioni correttamente. Iniziamo con un pò di background sul clustering e vediamo come fare il deploy di un'applicazione Seam in un cluster JBoss AS." #. Tag: title #: ClusteringAndEJBPassivation.xml:25 @@ -72,87 +46,26 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:27 #, no-c-format -msgid "" -"Clustering (more formally web clustering) allows an application to run on " -"two or more parallel servers (i.e., nodes) while providing a uniform view of " -"the application to clients. Load is distributed across the servers in such a " -"way that if one or more of the servers fails, the application is still " -"accessible via any of the surviving nodes. This topology is crucial for " -"building scalable enterprise applications as performance and availability " -"can be improved simply by adding nodes. But it brings up an important " -"question. <emphasis>What happens to the state that was on the server that " -"failed?</emphasis>" -msgstr "" -"Il clustering (più formalmente web clustering) consente ad un'applicazione " -"di girare su due o più server paralleli (cioè, nodi) mentre viene fornita ai " -"client una vista uniforme dell'applicazione. Il carico è distribuito sui " -"server in modo tale che se uno o più server fallisce, l'applicazione " -"continua ad essere accessibile tramite gli altri nodi. Questa tipologia è " -"cruciale per la costruzione di applicazioni enterprise scalabili in " -"performance e la disponibilità può essere migliorata semplicemente " -"aggiungendo nodi. Ma si giunge ad una domanda importante. <emphasis>Cosa " -"succede allo stato presente su un server che ha fallito?</emphasis>" +msgid "Clustering (more formally web clustering) allows an application to run on two or more parallel servers (i.e., nodes) while providing a uniform view of the application to clients. Load is distributed across the servers in such a way that if one or more of the servers fails, the application is still accessible via any of the surviving nodes. This topology is crucial for building scalable enterprise applications as performance and availability can be improved simply by adding nodes. But it brings up an important question. <emphasis>What happens to the state that was on the server that failed?</emphasis>" +msgstr "Il clustering (più formalmente web clustering) consente ad un'applicazione di girare su due o più server paralleli (cioè, nodi) mentre viene fornita ai client una vista uniforme dell'applicazione. Il carico è distribuito sui server in modo tale che se uno o più server fallisce, l'applicazione continua ad essere accessibile tramite gli altri nodi. Questa tipologia è cruciale per la costruzione di applicazioni enterprise scalabili in performance e la disponibilità può essere migliorata semplicemente aggiungendo nodi. Ma si giunge ad una domanda importante. <emphasis>Cosa succede allo stato presente su un server che ha fallito?</emphasis>" #. Tag: para #: ClusteringAndEJBPassivation.xml:36 #, no-c-format -msgid "" -"Since day one, Seam has always provided support for stateful applications " -"running in a cluster. Up to this point, you have learned that Seam provides " -"state management in the form of additional scopes and by governing the life " -"cycle of stateful (scoped) components. But state management in Seam goes " -"beyond creating, storing and destroying instances. Seam tracks changes to " -"JavaBean components and stores the changes at strategic points during the " -"request so that the changes can be restored when the request shifts to a " -"secondary node in the cluster. Fortunately, monitoring and replication of " -"stateful EJB components is already handled by the EJB server, so this " -"feature of Seam is intended to put stateful JavaBeans on par with their EJB " -"cohorts." -msgstr "" -"Sin dal primo giorno Seam ha sempre fornito il supporto alle applicazioni " -"stateful in azione dentro un cluster. Fino ad ora si è appreso che Seam " -"fornisce la gestione dello stato aggiungendo degli scope e governando il " -"ciclo di vita dei componenti stateful (con scope). Ma la gestione dello " -"stato in Seam va oltre alla creazione, memorizzazione e distruzione di " -"istanze. Seam traccia i cambiamenti ai componenti JavaBean e memorizza i " -"cambiamenti in punti strategici durante la richiesta, affinché i cambiamenti " -"vengano ripristinati quando la richiesta passa su un nodo secondario del " -"cluster. Fortunatamente il monitoraggio e la replica di componenti EJB " -"stateful viene già gestita dal server EJB, quindi tale funzionalità di Seam " -"serve per mettere i JavaBean a fianco dei suoi compagni EJB." +msgid "Since day one, Seam has always provided support for stateful applications running in a cluster. Up to this point, you have learned that Seam provides state management in the form of additional scopes and by governing the life cycle of stateful (scoped) components. But state management in Seam goes beyond creating, storing and destroying instances. Seam tracks changes to JavaBean components and stores the changes at strategic points during the request so that the changes can be restored when the request shifts to a secondary node in the cluster. Fortunately, monitoring and replication of stateful EJB components is already handled by the EJB server, so this feature of Seam is intended to put stateful JavaBeans on par with their EJB cohorts." +msgstr "Sin dal primo giorno Seam ha sempre fornito il supporto alle applicazioni stateful in azione dentro un cluster. Fino ad ora si è appreso che Seam fornisce la gestione dello stato aggiungendo degli scope e governando il ciclo di vita dei componenti stateful (con scope). Ma la gestione dello stato in Seam va oltre alla creazione, memorizzazione e distruzione di istanze. Seam traccia i cambiamenti ai componenti JavaBean e memorizza i cambiamenti in punti strategici durante la richiesta, affinché i cambiamenti vengano ripristinati quando la richiesta passa su un nodo secondario del cluster. Fortunatamente il monitoraggio e la replica di componenti EJB stateful viene già gestita dal server EJB, quindi tale funzionalità di Seam serve per mettere i JavaBean a fianco dei suoi compagni EJB." #. Tag: para #: ClusteringAndEJBPassivation.xml:46 -#, fuzzy, no-c-format -msgid "" -"But wait, there's more! Seam also offers an incredibly unique feature for " -"clustered applications. In addition to monitoring JavaBean components, Seam " -"ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detached during replication. Seam keeps a record of the " -"entities that are loaded and automatically loads them on the secondary node. " -"You must, however, be using a Seam-managed persistence context to get this " -"feature. More in depth information about this feature is provided in the " -"second half of this chapter." -msgstr "" -"Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica " -"caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei " -"componenti JavaBean, Seam assicura che le istanze entity gestite (cioè " -"entity JPA e Hibernate) non divengano detached durante la replica. Seam " -"mantiene un record di entity che sono caricati e li carica automaticamente " -"nel nodo secondario. Occorre comunque usare un contesto di persistenza " -"gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate " -"informazioni su questa funzionalità vengono fornite nella seconda parte del " -"capitolo." +#, no-c-format +msgid "But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and Hibernate entities) don't become detached during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter." +msgstr "Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei componenti JavaBean, Seam assicura che le istanze entity gestite (cioè entity JPA e Hibernate) non divengano detached durante la replica. Seam mantiene un record di entity caricati e li carica automaticamente nel nodo secondario. Occorre comunque usare un contesto di persistenza gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate informazioni su questa funzionalità vengono fornite nella seconda parte del capitolo." #. Tag: para #: ClusteringAndEJBPassivation.xml:55 #, no-c-format -msgid "" -"Now that you understand what features Seam offers to support a clustered " -"environment, let's look at how you program for clustering." -msgstr "" -"Ora che si è capito quali funzionalità offre Seam per supportare l'ambiente " -"clustered, guardiamo come si programma un cluster." +msgid "Now that you understand what features Seam offers to support a clustered environment, let's look at how you program for clustering." +msgstr "Ora che si è capito quali funzionalità offre Seam per supportare l'ambiente clustered, guardiamo come si programma un cluster." #. Tag: title #: ClusteringAndEJBPassivation.xml:61 @@ -162,137 +75,57 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:62 -#, fuzzy, no-c-format -msgid "" -"Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>org.jboss.seam." -"core.Mutable</literal> interface from the Seam API. As part of the contract, " -"the component must maintain a dirty flag that is reported and reset by the " -"<literal>clearDirty()</literal> method. Seam calls this method to determine " -"if it is necessary to replicate the component. This avoids having to use the " -"more cumbersome Servlet API to add and remove the session attribute on every " -"change of the object." -msgstr "" -"Un componente JavaBean mutabile con scope sessione o conversazione che verrà " -"usato in un ambiente clustered deve implementare l'interfaccia " -"<literal>Mutable</literal> dell'API Seam. Come parte del contratto, il " -"contratto deve mantenere un dirty flag che viene segnato e resettato dal " -"metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per " -"determinare se è necessario replicare il componente. Questo evita di dover " -"usare la più problematica API dei Servlet per aggiungere e rimuovere " -"l'attributo sessione ad ogni cambiamento dell'oggetto." +#, no-c-format +msgid "Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered environment must implement the <literal>org.jboss.seam.core.Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the session attribute on every change of the object." +msgstr "Un componente JavaBean mutabile con scope sessione o conversazione che verrà usato in un ambiente clustered deve implementare l'interfaccia <literal>org.jboss.seam.core.Mutable</literal> dell'API Seam. Come parte del contratto, il contratto deve mantenere un dirty flag che viene segnato e resettato dal metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per determinare se è necessario replicare il componente. Questo evita di dover usare la più problematica API dei Servlet per aggiungere e rimuovere l'attributo sessione ad ogni cambiamento dell'oggetto." #. Tag: para #: ClusteringAndEJBPassivation.xml:70 #, no-c-format -msgid "" -"You also must ensure that all session- and conversation-scoped JavaBean " -"components are Serializable. Additional, all fields of a stateful component " -"(EJB or JavaBean) must Serializable unless the field is marked transient or " -"set to null in a <literal>@PrePassivate</literal> method. You can restore " -"the value of a transient or nullified field in a <literal>@PostActivate</" -"literal> method." -msgstr "" -"Bisogna assicurarsi che tutti i componenti JavaBean con scope sessione e " -"conversazione siano Serializable. Inoltre tutti i campi di un componente " -"stateful (EJB o JavaBean) devono essere Serializable amenoché siano marcati " -"come transient o impostati a null in un metodo <literal>@PrePassivate</" -"literal>. Si può ripristinare il valore di un campo transient o null in un " -"metodo <literal>@PostActivate</literal>." +msgid "You also must ensure that all session- and conversation-scoped JavaBean components are Serializable. Additional, all fields of a stateful component (EJB or JavaBean) must Serializable unless the field is marked transient or set to null in a <literal>@PrePassivate</literal> method. You can restore the value of a transient or nullified field in a <literal>@PostActivate</literal> method." +msgstr "Bisogna assicurarsi che tutti i componenti JavaBean con scope sessione e conversazione siano Serializable. Inoltre tutti i campi di un componente stateful (EJB o JavaBean) devono essere Serializable amenoché siano marcati come transient o impostati a null in un metodo <literal>@PrePassivate</literal>. Si può ripristinare il valore di un campo transient o null in un metodo <literal>@PostActivate</literal>." #. Tag: para #: ClusteringAndEJBPassivation.xml:76 #, no-c-format -msgid "" -"One area where people often get bitten is by using <literal>List.subList</" -"literal> to create a list. The resulting list is not Serializable. So watch " -"out for situations like that. If hit a <literal>java.io." -"NotSerializableException</literal> and cannot locate the culprit at first " -"glance, you can put a breakpoint on this exception, run the application " -"server in debug mode and attach a debugger (such as Eclipse) to see what " -"deserialization is choking on." -msgstr "" -"Un'area in cui spesso le persone hanno problemi è con l'uso di <literal>List." -"subList</literal> per creare una lista. La lista risultante non è " -"Serializable. Quindi attenzione a queste situazioni. Se ci si imbatte in una " -"<literal>java.io.NotSerializableException</literal> e non si riescead " -"individuare subito il colpevole, si può mettere un breakpoint su " -"quest'eccezione, avviare l'application server in modalità debug ed attaccare " -"il debugger (come in Eclipse) per vedere quale deserializzazione causa il " -"problema." +msgid "One area where people often get bitten is by using <literal>List.subList</literal> to create a list. The resulting list is not Serializable. So watch out for situations like that. If hit a <literal>java.io.NotSerializableException</literal> and cannot locate the culprit at first glance, you can put a breakpoint on this exception, run the application server in debug mode and attach a debugger (such as Eclipse) to see what deserialization is choking on." +msgstr "Un'area in cui spesso le persone hanno problemi è con l'uso di <literal>List.subList</literal> per creare una lista. La lista risultante non è Serializable. Quindi attenzione a queste situazioni. Se ci si imbatte in una <literal>java.io.NotSerializableException</literal> e non si riescead individuare subito il colpevole, si può mettere un breakpoint su quest'eccezione, avviare l'application server in modalità debug ed attaccare il debugger (come in Eclipse) per vedere quale deserializzazione causa il problema." #. Tag: para #: ClusteringAndEJBPassivation.xml:84 -#, fuzzy, no-c-format -msgid "" -"Please note that clustering does not work with hot deployable components. " -"But then again, you shouldn't be using hot deployable components in a non-" -"development environment anyway." -msgstr "" -"Si noti che il clustering non funziona con componenti hot deployable. Ma " -"comunque non si dovrebbero usare i componenti hot deployable in un ambiente " -"non di sviluppo." +#, no-c-format +msgid "Please note that clustering does not work with hot deployable components. But then again, you shouldn't be using hot deployable components in a non-development environment anyway." +msgstr "Si noti che il clustering non funziona con componenti hot deployable. Ma comunque non si dovrebbero usare i componenti hot deployable in un ambiente non di sviluppo." #. Tag: title #: ClusteringAndEJBPassivation.xml:92 #, no-c-format -msgid "" -"Deploying a Seam application to a JBoss AS cluster with session replication" -msgstr "" -"Deploy di un'applicazione Seam in un cluster JBoss AS con replica di sessione" +msgid "Deploying a Seam application to a JBoss AS cluster with session replication" +msgstr "Deploy di un'applicazione Seam in un cluster JBoss AS con replica di sessione" #. Tag: para #: ClusteringAndEJBPassivation.xml:94 #, no-c-format -msgid "" -"The procedure outlined in this tutorial has been validated with an seam-gen " -"application and the Seam booking example." -msgstr "" -"Questa procedura descritta nel tutorial è stata validata con un'applicazione " -"seam-gen e nell'esempio Prenotazione." +msgid "The procedure outlined in this tutorial has been validated with an seam-gen application and the Seam booking example." +msgstr "Questa procedura descritta nel tutorial è stata validata con un'applicazione seam-gen e nell'esempio Prenotazione." #. Tag: para #: ClusteringAndEJBPassivation.xml:99 #, no-c-format -msgid "" -"In the tutorial, I assume that the IP addresses of the master and slave " -"servers are 192.168.1.2 and 192.168.1.3, respectively. I am intentionally " -"not using the mod_jk load balancer so that it's easier to validate that both " -"nodes are responding to requests and can share sessions." -msgstr "" -"In questo tutorial si assume che gli indirizzi IP dei server master e slave " -"siano rispettivamente 192.168.1.2 e 192.168.1.3. Intenzionalmente non viene " -"usato il bilanciatore di carico mod_jk, quindi è più facile validate che " -"entrambi i nodi stiano rispondendo alle richieste e possano condividere le " -"sessioni." +msgid "In the tutorial, I assume that the IP addresses of the master and slave servers are 192.168.1.2 and 192.168.1.3, respectively. I am intentionally not using the mod_jk load balancer so that it's easier to validate that both nodes are responding to requests and can share sessions." +msgstr "In questo tutorial si assume che gli indirizzi IP dei server master e slave siano rispettivamente 192.168.1.2 e 192.168.1.3. Intenzionalmente non viene usato il bilanciatore di carico mod_jk, quindi è più facile validate che entrambi i nodi stiano rispondendo alle richieste e possano condividere le sessioni." #. Tag: para #: ClusteringAndEJBPassivation.xml:105 #, no-c-format -msgid "" -"I'm using the farm deployment method in these instructions, though you could " -"also deploy the application normally and allow the two servers to negotiate " -"a master/slave relationship based on startup order." -msgstr "" -"In queste istruzioni si sta usando il metodo di sviluppo farm, sebbene si " -"possa fare normalmente il deploy dell'applicazione e consentire ai due " -"server di negoziare una relazione master/slave basata sull'ordine di avvio." +msgid "I'm using the farm deployment method in these instructions, though you could also deploy the application normally and allow the two servers to negotiate a master/slave relationship based on startup order." +msgstr "In queste istruzioni si sta usando il metodo di sviluppo farm, sebbene si possa fare normalmente il deploy dell'applicazione e consentire ai due server di negoziare una relazione master/slave basata sull'ordine di avvio." #. Tag: para #: ClusteringAndEJBPassivation.xml:111 #, no-c-format -msgid "" -"JBoss AS clustering relies on UDP multicasting provided by jGroups. The " -"SELinux configuration that ships with RHEL/Fedora blocks these packets by " -"default. You can allow them to pass by modifying the iptables rules (as " -"root). The following commands apply to an IP address that matches 192.168.1." -"x." -msgstr "" -"JBoss AS clustering si basa sul multicasting UDP fornito da jGroups. La " -"configurazione SELinux che è inclusa in RHEL/Fedora di default blocca questi " -"pacchetti. Si può consentire di lasciarli passare modificando le regole " -"iptables (come root). I seguenti comandi si applicano ad un indirizzo IP che " -"corrisponde a 192.168.1.x." +msgid "JBoss AS clustering relies on UDP multicasting provided by jGroups. The SELinux configuration that ships with RHEL/Fedora blocks these packets by default. You can allow them to pass by modifying the iptables rules (as root). The following commands apply to an IP address that matches 192.168.1.x." +msgstr "JBoss AS clustering si basa sul multicasting UDP fornito da jGroups. La configurazione SELinux che è inclusa in RHEL/Fedora di default blocca questi pacchetti. Si può consentire di lasciarli passare modificando le regole iptables (come root). I seguenti comandi si applicano ad un indirizzo IP che corrisponde a 192.168.1.x." #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:116 @@ -311,12 +144,8 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:117 #, no-c-format -msgid "" -"Detailed information can be found on <ulink url=\"http://www.jboss.org/" -"community/docs/DOC-11935\">this page</ulink> on the JBoss Wiki." -msgstr "" -"Maggiori dettagli possono essere trovati nella <ulink url=\"http://www.jboss." -"org/community/docs/DOC-11935\">pagina</ulink> del JBoss Wiki." +msgid "Detailed information can be found on <ulink url=\"http://www.jboss.org/community/docs/DOC-11935\">this page</ulink> on the JBoss Wiki." +msgstr "Maggiori dettagli possono essere trovati nella <ulink url=\"http://www.jboss.org/community/docs/DOC-11935\">pagina</ulink> del JBoss Wiki." #. Tag: para #: ClusteringAndEJBPassivation.xml:122 @@ -327,47 +156,26 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:125 #, no-c-format -msgid "" -"Deploy the JDBC driver to server/all/lib/ on both instances if not using " -"HSQLDB" -msgstr "" -"Fare il deploy del driver JDBC in server/all/lib/ su entrambe le istanze se " -"non si usa HSQLDB" +msgid "Deploy the JDBC driver to server/all/lib/ on both instances if not using HSQLDB" +msgstr "Fare il deploy del driver JDBC in server/all/lib/ su entrambe le istanze se non si usa HSQLDB" #. Tag: para #: ClusteringAndEJBPassivation.xml:128 #, no-c-format -msgid "" -"Add <literal><distributable/></literal> as the first child element in WEB-" -"INF/web.xml" -msgstr "" -"Aggiungere <literal><distributable/></literal> come primo elemento figlio " -"in WEB-INF/web.xml" +msgid "Add <literal><distributable/></literal> as the first child element in WEB-INF/web.xml" +msgstr "Aggiungere <literal><distributable/></literal> come primo elemento figlio in WEB-INF/web.xml" #. Tag: para #: ClusteringAndEJBPassivation.xml:131 #, no-c-format -msgid "" -"Set the <literal>distributable</literal> property on <literal>org.jboss.seam." -"core.init</literal> to true to enable the ManagedEntityInterceptor (i.e., " -"<literal><![CDATA[<core:init distributable=\"true\"/>]]></literal>)" -msgstr "" -"Impostare la proprietà <literal>distributable</literal> su <literal>org." -"jboss.seam.core.init</literal> a true per abilitare il " -"ManagedEntityInterceptor (cioè, <literal><![CDATA[<core:init distributable=" -"\"true\"/>]]></literal>)" +msgid "Set the <literal>distributable</literal> property on <literal>org.jboss.seam.core.init</literal> to true to enable the ManagedEntityInterceptor (i.e., <literal><![CDATA[<core:init distributable=\"true\"/>]]></literal>)" +msgstr "Impostare la proprietà <literal>distributable</literal> su <literal>org.jboss.seam.core.init</literal> a true per abilitare il ManagedEntityInterceptor (cioè, <literal><![CDATA[<core:init distributable=\"true\"/>]]></literal>)" #. Tag: para #: ClusteringAndEJBPassivation.xml:136 #, no-c-format -msgid "" -"Ensure you have two IP addresses available (two computers, two network " -"cards, or two IP addressses bound to the same interface). I'll assume the " -"two IP address are 192.168.1.2 and 192.168.1.3" -msgstr "" -"Assicurarsi di avere disponibili due indirizzi IP (due computer, due schede " -"di rete oppure due indirizzi IP sulla stessa interfaccia). Si assume che i " -"due indirizzi IP siano 192.168.1.2 e 192.168.1.3" +msgid "Ensure you have two IP addresses available (two computers, two network cards, or two IP addressses bound to the same interface). I'll assume the two IP address are 192.168.1.2 and 192.168.1.3" +msgstr "Assicurarsi di avere disponibili due indirizzi IP (due computer, due schede di rete oppure due indirizzi IP sulla stessa interfaccia). Si assume che i due indirizzi IP siano 192.168.1.2 e 192.168.1.3" #. Tag: para #: ClusteringAndEJBPassivation.xml:141 @@ -384,19 +192,14 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:143 #, no-c-format -msgid "" -"The log should report that there are 1 cluster members and 0 other members." +msgid "The log should report that there are 1 cluster members and 0 other members." msgstr "Il log dovrebbe riportare che c'è 1 membro cluster e 0 altri membri." #. Tag: para #: ClusteringAndEJBPassivation.xml:146 #, no-c-format -msgid "" -"Verify that the server/all/farm directory is empty in the slave JBoss AS " -"instance" -msgstr "" -"Verificare che la directory server/all/farm sia vuota nell'istanza slave di " -"JBoss AS" +msgid "Verify that the server/all/farm directory is empty in the slave JBoss AS instance" +msgstr "Verificare che la directory server/all/farm sia vuota nell'istanza slave di JBoss AS" #. Tag: para #: ClusteringAndEJBPassivation.xml:149 @@ -413,12 +216,8 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:151 #, no-c-format -msgid "" -"The log should report that there are 2 cluster members and 1 other members. " -"It should also show the state being retrieved from the master." -msgstr "" -"Il log dovrebbe riportare che ci sono 2 membri cluster e 1 altro membro. " -"Dovrebbe anche mostrare che lo stato viene recuperato dal master." +msgid "The log should report that there are 2 cluster members and 1 other members. It should also show the state being retrieved from the master." +msgstr "Il log dovrebbe riportare che ci sono 2 membri cluster e 1 altro membro. Dovrebbe anche mostrare che lo stato viene recuperato dal master." #. Tag: para #: ClusteringAndEJBPassivation.xml:155 @@ -429,14 +228,8 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:156 #, no-c-format -msgid "" -"In the log of the master you should see acknowledgement of the deployment. " -"In the log of the slave you should see a corresponding message acknowledging " -"the deployment to the slave." -msgstr "" -"Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log " -"dello slave si dovrebbe vedere il corrispondente messaggio di " -"acknowledgement del deploy per lo slave." +msgid "In the log of the master you should see acknowledgement of the deployment. In the log of the slave you should see a corresponding message acknowledging the deployment to the slave." +msgstr "Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log dello slave si dovrebbe vedere il corrispondente messaggio di acknowledgement del deploy per lo slave." #. Tag: para #: ClusteringAndEJBPassivation.xml:160 @@ -447,63 +240,32 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:161 #, no-c-format -msgid "" -"In the log of the master you should see acknowledgement of the deployment. " -"In the log of the slave you should see a corresponding message acknowledging " -"the deployment to the slave. Note that you may have to wait up to 3 minutes " -"for the deployed archive to be transfered." -msgstr "" -"Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log " -"dello slave si dovrebbe vedere il corrispondente messaggio di " -"acknowledgement del deploy per lo slave. Si noti che si potrebbe dover " -"attendere fino a 3 minuti perché venga trasferito l'archivio deployato." +msgid "In the log of the master you should see acknowledgement of the deployment. In the log of the slave you should see a corresponding message acknowledging the deployment to the slave. Note that you may have to wait up to 3 minutes for the deployed archive to be transfered." +msgstr "Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log dello slave si dovrebbe vedere il corrispondente messaggio di acknowledgement del deploy per lo slave. Si noti che si potrebbe dover attendere fino a 3 minuti perché venga trasferito l'archivio deployato." #. Tag: para #: ClusteringAndEJBPassivation.xml:166 #, no-c-format -msgid "" -"You're application is now running in a cluster with HTTP session " -"replication! But, of course, you are going to want to validate that the " -"clustering actually works." -msgstr "" -"La vostra applicazione sta girando in un cluster con replica della sessione " -"HTTP! Ma certamente si vuole validate il fatto che il clustering sta " -"funzionando." +msgid "You're application is now running in a cluster with HTTP session replication! But, of course, you are going to want to validate that the clustering actually works." +msgstr "La vostra applicazione sta girando in un cluster con replica della sessione HTTP! Ma certamente si vuole validate il fatto che il clustering sta funzionando." #. Tag: title #: ClusteringAndEJBPassivation.xml:172 #, no-c-format -msgid "" -"Validating the distributable services of an application running in a JBoss " -"AS cluster" -msgstr "" -"Validazione dei servizi distribuiti di un'applicazione su un cluster JBoss AS" +msgid "Validating the distributable services of an application running in a JBoss AS cluster" +msgstr "Validazione dei servizi distribuiti di un'applicazione su un cluster JBoss AS" #. Tag: para #: ClusteringAndEJBPassivation.xml:173 #, no-c-format -msgid "" -"It's all well and fine to see the application start successfully on two " -"different JBoss AS servers, but seeing is believing. You likely want to " -"validate that the two instances are exchanging HTTP sessions to allow the " -"slave to take over when the master instance is stopped." -msgstr "" -"E' sempre bello vedere che l'applicazione si avvia con successo su due " -"diversi server JBoss AS, ma vedere è credere! Probabilmente si vuole " -"validare che le due istanze si stiano scambiando le sessioni HTTP per " -"consentire allo slave di entrare in azione quando l'istanza master si ferma." +msgid "It's all well and fine to see the application start successfully on two different JBoss AS servers, but seeing is believing. You likely want to validate that the two instances are exchanging HTTP sessions to allow the slave to take over when the master instance is stopped." +msgstr "E' sempre bello vedere che l'applicazione si avvia con successo su due diversi server JBoss AS, ma vedere è credere! Probabilmente si vuole validare che le due istanze si stiano scambiando le sessioni HTTP per consentire allo slave di entrare in azione quando l'istanza master si ferma." #. Tag: para #: ClusteringAndEJBPassivation.xml:179 #, no-c-format -msgid "" -"Start off by visiting the application running on the master instance in your " -"browser. That will produce the first HTTP session. Now, open up the JBoss AS " -"JMX console on that instance and navigate to the following MBean:" -msgstr "" -"Avviare e visitare sul browser l'applicazione che gira sull'istanza master. " -"Questo produrrà la prima sessione HTTP. Ora si apra la console JMX di JBoss " -"AS su tale istanza e si vada al seguente MBean:" +msgid "Start off by visiting the application running on the master instance in your browser. That will produce the first HTTP session. Now, open up the JBoss AS JMX console on that instance and navigate to the following MBean:" +msgstr "Avviare e visitare sul browser l'applicazione che gira sull'istanza master. Questo produrrà la prima sessione HTTP. Ora si apra la console JMX di JBoss AS su tale istanza e si vada al seguente MBean:" #. Tag: para #: ClusteringAndEJBPassivation.xml:187 @@ -526,76 +288,32 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:197 #, no-c-format -msgid "" -"Invoke the printDetails() method. You will see a tree of active HTTP " -"sessions. Verify that the session your browser is using corresponds to one " -"of the sessions in this tree." -msgstr "" -"Invocare il metodo printDetails(). Si vedrà un albero con le sessioni HTTP " -"attive. Verificare che la sessione del browser in uso corrisponda ad una " -"delle sessioni in questo albero." +msgid "Invoke the printDetails() method. You will see a tree of active HTTP sessions. Verify that the session your browser is using corresponds to one of the sessions in this tree." +msgstr "Invocare il metodo printDetails(). Si vedrà un albero con le sessioni HTTP attive. Verificare che la sessione del browser in uso corrisponda ad una delle sessioni in questo albero." #. Tag: para #: ClusteringAndEJBPassivation.xml:202 #, no-c-format -msgid "" -"Now switch over to the slave instance and invoke the same method in the JMX " -"console. You should see an identical list (at least underneath this " -"application's context path)." -msgstr "" -"Ora si passi all'istanza slave e si invochi lo stesso metodo nella console " -"JMX. Si dovrebbe vedere la stessa lista (almeno sotto il context path " -"dell'applicazione)" +msgid "Now switch over to the slave instance and invoke the same method in the JMX console. You should see an identical list (at least underneath this application's context path)." +msgstr "Ora si passi all'istanza slave e si invochi lo stesso metodo nella console JMX. Si dovrebbe vedere la stessa lista (almeno sotto il context path dell'applicazione)" #. Tag: para #: ClusteringAndEJBPassivation.xml:207 #, no-c-format -msgid "" -"So you can see that at least both servers claim to have identical sessions. " -"Now, time to test that the data is serializing and unserializing properly." -msgstr "" -"Quindi si può vedere che entrambi i server hanno le stesse identiche " -"sessioni. Ora occorre testare che i dati vengano serializzati e " -"deserializzati correttamente." +msgid "So you can see that at least both servers claim to have identical sessions. Now, time to test that the data is serializing and unserializing properly." +msgstr "Quindi si può vedere che entrambi i server hanno le stesse identiche sessioni. Ora occorre testare che i dati vengano serializzati e deserializzati correttamente." #. Tag: para #: ClusteringAndEJBPassivation.xml:212 #, no-c-format -msgid "" -"Sign in using using the URL of the master instance. Then, construct a URL " -"for the second instance by putting the ;jsessionid=XXXX immediately after " -"the servlet path and changing the IP address. You should see that the " -"session has carried over to the other instance. Now kill the master instance " -"and see that you can continue to use the application from the slave " -"instance. Remove the deployments from the server/all/farm directory and " -"start the instance again. Switch the IP in the URL back to that of the " -"master instance and visit the URL. You'll see that the original session is " -"still being used." -msgstr "" -"Fare il login usando l'URL dell'istanza master. Poi scrivere l'URL per la " -"seconda istanza mettendo ;jsessionid=XXXX immediatamente dopo il path del " -"servlet e cambiando l'indirizzo IP. Si dovrebbe vedere che la sessione viene " -"trasportata nell'altra istanza. Ora uccidere il processo dell'istanza master " -"e verificare che si possa continuare ad usare l'applicazione dall'istanza " -"slave. Rimuovere i deploy dalla directory server/all/farm ed avviare di " -"nuovo l'istanza. Cambiare nell'URL l'IP a quello dell'istanza master e " -"visitare l'URL. Si vedrà che viene usata ancora la sessione originale." +msgid "Sign in using using the URL of the master instance. Then, construct a URL for the second instance by putting the ;jsessionid=XXXX immediately after the servlet path and changing the IP address. You should see that the session has carried over to the other instance. Now kill the master instance and see that you can continue to use the application from the slave instance. Remove the deployments from the server/all/farm directory and start the instance again. Switch the IP in the URL back to that of the master instance and visit the URL. You'll see that the original session is still being used." +msgstr "Fare il login usando l'URL dell'istanza master. Poi scrivere l'URL per la seconda istanza mettendo ;jsessionid=XXXX immediatamente dopo il path del servlet e cambiando l'indirizzo IP. Si dovrebbe vedere che la sessione viene trasportata nell'altra istanza. Ora uccidere il processo dell'istanza master e verificare che si possa continuare ad usare l'applicazione dall'istanza slave. Rimuovere i deploy dalla directory server/all/farm ed avviare di nuovo l'istanza. Cambiare nell'URL l'IP a quello dell'istanza master e visitare l'URL. Si vedrà che viene usata ancora la sessione originale." #. Tag: para #: ClusteringAndEJBPassivation.xml:221 #, no-c-format -msgid "" -"One way to watch objects passivate and activate is to create a session- or " -"conversation-scoped Seam component and implement the appropriate life-cycle " -"methods. You can either use methods from the HttpSessionActivationListener " -"interface (Seam automatically registers this interface on all non-EJB " -"components):" -msgstr "" -"Un modo per vedere passivare ed attivare gli oggetti è create un componente " -"Seam con scope conversazione o sessione ed implementare i metodi del ciclo " -"di vita in modo appropriato. Si possono usare i metodi dell'interfaccia " -"HttpSessionActivationListener (Seam automaticamente registra " -"quest'interfaccia per tutti i componenti non-EJB):" +msgid "One way to watch objects passivate and activate is to create a session- or conversation-scoped Seam component and implement the appropriate life-cycle methods. You can either use methods from the HttpSessionActivationListener interface (Seam automatically registers this interface on all non-EJB components):" +msgstr "Un modo per vedere passivare ed attivare gli oggetti è create un componente Seam con scope conversazione o sessione ed implementare i metodi del ciclo di vita in modo appropriato. Si possono usare i metodi dell'interfaccia HttpSessionActivationListener (Seam automaticamente registra quest'interfaccia per tutti i componenti non-EJB):" #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:228 @@ -610,28 +328,14 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:230 #, no-c-format -msgid "" -"Or you can simply mark two no-argument public void methods with " -"<literal>@PrePassivate</literal> and <literal>@PostActivate</literal>, " -"respectively. Note that the passivation step occurs at the end of every " -"request, while the activation step occurs when a node is called upon." -msgstr "" -"O semplicemente si possono marcare due metodi senza argomenti public void " -"rispettivamente con <literal>@PrePassivate</literal> e " -"<literal>@PostActivate</literal>. Si noti che il passo di passivazione " -"avviene alla fine di ogni richiesta, mentre quello di attivazione avviene " -"quando viene chiamato un nodo." +msgid "Or you can simply mark two no-argument public void methods with <literal>@PrePassivate</literal> and <literal>@PostActivate</literal>, respectively. Note that the passivation step occurs at the end of every request, while the activation step occurs when a node is called upon." +msgstr "O semplicemente si possono marcare due metodi senza argomenti public void rispettivamente con <literal>@PrePassivate</literal> e <literal>@PostActivate</literal>. Si noti che il passo di passivazione avviene alla fine di ogni richiesta, mentre quello di attivazione avviene quando viene chiamato un nodo." #. Tag: para #: ClusteringAndEJBPassivation.xml:237 #, no-c-format -msgid "" -"Now that you understand the big picture of running Seam in a cluster, it's " -"time to address Seam's most mysterious, yet remarkable agent, the " -"ManagedEntityInterceptor." -msgstr "" -"Ora che si ha il quadro generale del funzionamento di un cluster con Seam, è " -"tempo di indirizzarsi verso il misterioso ManagedEntityInterceptor." +msgid "Now that you understand the big picture of running Seam in a cluster, it's time to address Seam's most mysterious, yet remarkable agent, the ManagedEntityInterceptor." +msgstr "Ora che si ha il quadro generale del funzionamento di un cluster con Seam, è tempo di indirizzarsi verso il misterioso ManagedEntityInterceptor." #. Tag: title #: ClusteringAndEJBPassivation.xml:244 @@ -642,19 +346,8 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:246 #, no-c-format -msgid "" -"The ManagedEntityInterceptor (MEI) is an optional interceptor in Seam that " -"gets applied to conversation-scoped components when enabled. Enabling it is " -"simple. You just set the distributable property on the org.jboss.seam.init." -"core component to true. More simply put, you add (or update) the following " -"component declaration in the component descriptor (i.e., components.xml)." -msgstr "" -"Il ManagedEntityInterceptor (MEI) è un interceptor opzionale di Seam che " -"viene applicato, se abilitato, ai componenti con scope conversazione. " -"L'abilitazione è semplice. Occorre impostare a true la proprietà " -"distributable nel componente org.jboss.seam.init.core. Più semplicemente " -"aggiungere (o aggiornare) la seguente dichiarazione di componente in " -"components.xml:" +msgid "The ManagedEntityInterceptor (MEI) is an optional interceptor in Seam that gets applied to conversation-scoped components when enabled. Enabling it is simple. You just set the distributable property on the org.jboss.seam.init.core component to true. More simply put, you add (or update) the following component declaration in the component descriptor (i.e., components.xml)." +msgstr "Il ManagedEntityInterceptor (MEI) è un interceptor opzionale di Seam che viene applicato, se abilitato, ai componenti con scope conversazione. L'abilitazione è semplice. Occorre impostare a true la proprietà distributable nel componente org.jboss.seam.init.core. Più semplicemente aggiungere (o aggiornare) la seguente dichiarazione di componente in components.xml:" #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:253 @@ -665,62 +358,26 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:255 #, no-c-format -msgid "" -"Note that this doesn't enable replication of HTTP sessions, but it does " -"prepare Seam to be able to deal with passivation of either EJB components or " -"components in the HTTP session." -msgstr "" -"Si noti che questo non abilita la replica delle sessioni HTTP, ma prepara " -"Seam a poter gestire la passivazione dei componenti EJB o dei componenti " -"nelle sessioni HTTP." +msgid "Note that this doesn't enable replication of HTTP sessions, but it does prepare Seam to be able to deal with passivation of either EJB components or components in the HTTP session." +msgstr "Si noti che questo non abilita la replica delle sessioni HTTP, ma prepara Seam a poter gestire la passivazione dei componenti EJB o dei componenti nelle sessioni HTTP." #. Tag: para #: ClusteringAndEJBPassivation.xml:260 -#, fuzzy, no-c-format -msgid "" -"The MEI serves two distinct scenarios (EJB passivation and HTTP session " -"passivation), although to accomplish the same overall goal. It ensures that " -"throughout the life of a conversation using at least one extended " -"persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detached prematurally by a " -"passivation event). In short, it ensures the integrity of the extended " -"persistence context (and therefore its guarantees)." -msgstr "" -"MEI serve per due scenari distinti (passivazione EJB e passivazione della " -"sessione HTTP), sebbene raggiunge lo stesso obiettivo generale. Assicura che " -"lungo la vita di una conversazione con l'uso di almeno un contesto di " -"persistenza esteso, le istanze dell'entity caricate dal contesto di " -"persistenza rimangano gestite (non divengano detached in modo prematuro da " -"un evento passivation). In breve, assicura l'integrità del contesto di " -"persistenza esteso (e quindi delle sue garanzie)." +#, no-c-format +msgid "The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not become detached prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees)." +msgstr "MEI serve per due scenari distinti (passivazione EJB e passivazione della sessione HTTP), sebbene raggiunge lo stesso obiettivo generale. Assicura che lungo la vita di una conversazione con l'uso di almeno un contesto di persistenza esteso, le istanze dell'entity caricate dal contesto di persistenza rimangano gestite (non divengano detached in modo prematuro da un evento passivation). In breve, assicura l'integrità del contesto di persistenza esteso (e quindi delle sue garanzie)." #. Tag: para #: ClusteringAndEJBPassivation.xml:268 #, no-c-format -msgid "" -"The previous statement implies that there is a challenge that threatens this " -"contract. In fact, there are two. One case is when a stateful session bean " -"(SFSB) that hosts an extended persistence context is passivated (to save " -"memory or to migrate it to another node in the cluster) and the second is " -"when the HTTP session is passivated (to prepare it to be migrated to another " -"node in the cluster)." -msgstr "" -"La precedente affermazione implica che ci sia una minaccia al contratto. " -"Infatti ce ne sono due. Un caso è quando lo stateful session bean (SFSB) che " -"ospita un contesto di persistenza esteso viene passivato (per risparmiare " -"memoria o migrarlo in un altro nodo del cluster) ed il secondo quando la " -"sessione HTTP viene passivata (per prepararla alla migrazione in un altro " -"nodo del cluster)." +msgid "The previous statement implies that there is a challenge that threatens this contract. In fact, there are two. One case is when a stateful session bean (SFSB) that hosts an extended persistence context is passivated (to save memory or to migrate it to another node in the cluster) and the second is when the HTTP session is passivated (to prepare it to be migrated to another node in the cluster)." +msgstr "La precedente affermazione implica che ci sia una minaccia al contratto. Infatti ce ne sono due. Un caso è quando lo stateful session bean (SFSB) che ospita un contesto di persistenza esteso viene passivato (per risparmiare memoria o migrarlo in un altro nodo del cluster) ed il secondo quando la sessione HTTP viene passivata (per prepararla alla migrazione in un altro nodo del cluster)." #. Tag: para #: ClusteringAndEJBPassivation.xml:275 #, no-c-format -msgid "" -"I first want to discuss the general problem of passivation and then look at " -"the two challenges cited individually." -msgstr "" -"Vogliamo discutere per primo il problema generale della passivazione e poi " -"guardare singolarmente le due minacce." +msgid "I first want to discuss the general problem of passivation and then look at the two challenges cited individually." +msgstr "Vogliamo discutere per primo il problema generale della passivazione e poi guardare singolarmente le due minacce." #. Tag: title #: ClusteringAndEJBPassivation.xml:281 @@ -731,107 +388,32 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:283 #, no-c-format -msgid "" -"The persistence context is where the persistence manager (i.e., JPA " -"EntityManager or Hibernate Session) stores entity instances (i.e., objects) " -"it has loaded from the database (via the object-relational mappings). Within " -"a persistence context, there is no more than one object per unique database " -"record. The persistence context is often referred to as the first-level " -"cache because if the application asks for a record by its unique identifier " -"that has already been loaded into the persistence context, a call to the " -"database is avoided. But it's about more than just caching." -msgstr "" -"Il contesto di persistenza è il posto in cui il gestore di persistenza (cioè " -"EntityManager JPA o Hibernate Session) memorizza le istanze degli entity " -"(cioè gli oggetti) che ha caricato dal database (tramite mappature " -"relazionali degli oggetti). Dentro un contesto di persistenza, c'è alpiù un " -"oggetto per record di database. Il contesto di persistenza è spesso " -"considerato il primo livello di cache, poiché se l'applicazione chiede un " -"record attraverso il suo identificatore unico che è già stato caricato nel " -"contesto di persistenza, viene evitata una chiamata al database. Ma questo è " -"più che una cache." +msgid "The persistence context is where the persistence manager (i.e., JPA EntityManager or Hibernate Session) stores entity instances (i.e., objects) it has loaded from the database (via the object-relational mappings). Within a persistence context, there is no more than one object per unique database record. The persistence context is often referred to as the first-level cache because if the application asks for a record by its unique identifier that has already been loaded into the persistence context, a call to the database is avoided. But it's about more than just caching." +msgstr "Il contesto di persistenza è il posto in cui il gestore di persistenza (cioè EntityManager JPA o Hibernate Session) memorizza le istanze degli entity (cioè gli oggetti) che ha caricato dal database (tramite mappature relazionali degli oggetti). Dentro un contesto di persistenza, c'è alpiù un oggetto per record di database. Il contesto di persistenza è spesso considerato il primo livello di cache, poiché se l'applicazione chiede un record attraverso il suo identificatore unico che è già stato caricato nel contesto di persistenza, viene evitata una chiamata al database. Ma questo è più che una cache." #. Tag: para #: ClusteringAndEJBPassivation.xml:292 #, no-c-format -msgid "" -"Objects held in the persistence context can be modified, which the " -"persistence manager tracks. When an object is modified, it's considered " -"\"dirty\". The persistence manager will migrate these changes to the " -"database using a technique known as write-behind (which basically means only " -"when necessary). Thus, the persistence context maintains a set of pending " -"changes to the database." -msgstr "" -"Gli oggetti mantenuti nel contesto di persistenza possono essere modificati, " -"cosa di cui il gestore di persistenza tiene traccia. Quando un oggetto viene " -"modificato, viene considerato \"dirty\". Il gestore di persistenza migrerà " -"questi cambiamenti al database usando una tecnica conosciuta come write-" -"behind (che significa solo quando necessario). Quindi il contesto di " -"persistenza mantiene un set di cambiamenti pendenti sul database." +msgid "Objects held in the persistence context can be modified, which the persistence manager tracks. When an object is modified, it's considered \"dirty\". The persistence manager will migrate these changes to the database using a technique known as write-behind (which basically means only when necessary). Thus, the persistence context maintains a set of pending changes to the database." +msgstr "Gli oggetti mantenuti nel contesto di persistenza possono essere modificati, cosa di cui il gestore di persistenza tiene traccia. Quando un oggetto viene modificato, viene considerato \"dirty\". Il gestore di persistenza migrerà questi cambiamenti al database usando una tecnica conosciuta come write-behind (che significa solo quando necessario). Quindi il contesto di persistenza mantiene un set di cambiamenti pendenti sul database." #. Tag: para #: ClusteringAndEJBPassivation.xml:299 #, no-c-format -msgid "" -"Database-oriented applications do much more than just read from and write to " -"the database. They capture transactional bits of information that need to be " -"tranfered into the database atomically (at once). It's not always possible " -"to capture this information all on one screen. Additionally, the user might " -"need to make a judgement call about whether to approve or reject the pending " -"changes." -msgstr "" -"Le applicazioni orientate ai database fanno molto di più che leggere e " -"scrivere nel database. Esse catturano bit transazionali di informazione che " -"devono essere trasferiti nel database in modo atomico (in una solo volta). " -"Non è sempre possibile catturare queste informazioni in una sola volta. In " -"aggiunta l'utente potrebbe decidere se approvare o disapprovare le modifiche " -"pendenti." +msgid "Database-oriented applications do much more than just read from and write to the database. They capture transactional bits of information that need to be tranfered into the database atomically (at once). It's not always possible to capture this information all on one screen. Additionally, the user might need to make a judgement call about whether to approve or reject the pending changes." +msgstr "Le applicazioni orientate ai database fanno molto di più che leggere e scrivere nel database. Esse catturano bit transazionali di informazione che devono essere trasferiti nel database in modo atomico (in una solo volta). Non è sempre possibile catturare queste informazioni in una sola volta. In aggiunta l'utente potrebbe decidere se approvare o disapprovare le modifiche pendenti." #. Tag: para #: ClusteringAndEJBPassivation.xml:306 #, no-c-format -msgid "" -"What we are getting at here is that the idea of a transaction from the " -"user's perspective needs to be extended. And that is why the extended " -"persistence context fits so perfectly with this requirement. It can hold " -"such changes for as long as the application can keep it open and then use " -"the built-in capabilities of the persistence manager to push these pending " -"changes to the database without requiring the application developer to worry " -"about the low-level details (a simple call to <literal>EntityManager#flush()" -"</literal> does the trick)." -msgstr "" -"Ciò che vogliamo dire è che l'idea di transazione dal punto di vista " -"dell'utente deve essere estesa. E questo è il motivo per cui il contesto di " -"persistenza esteso risponde perfettamente a questo requisito. Può mantenere " -"i cambiamenti tanto a lungo quanto viene mantenuta aperta l'applicazione e " -"poi usare le capacità predefinite del gestore di persistenza per apportare " -"nel database questi cambiamenti senza richiedere allo sviluppatore di " -"preoccuparsi dei dettagli di basso livello (una semplice chiamata a " -"<literal>EntityManager#flush()</literal> fa tutto il lavoro)." +msgid "What we are getting at here is that the idea of a transaction from the user's perspective needs to be extended. And that is why the extended persistence context fits so perfectly with this requirement. It can hold such changes for as long as the application can keep it open and then use the built-in capabilities of the persistence manager to push these pending changes to the database without requiring the application developer to worry about the low-level details (a simple call to <literal>EntityManager#flush()</literal> does the trick)." +msgstr "Ciò che vogliamo dire è che l'idea di transazione dal punto di vista dell'utente deve essere estesa. E questo è il motivo per cui il contesto di persistenza esteso risponde perfettamente a questo requisito. Può mantenere i cambiamenti tanto a lungo quanto viene mantenuta aperta l'applicazione e poi usare le capacità predefinite del gestore di persistenza per apportare nel database questi cambiamenti senza richiedere allo sviluppatore di preoccuparsi dei dettagli di basso livello (una semplice chiamata a <literal>EntityManager#flush()</literal> fa tutto il lavoro)." #. Tag: para #: ClusteringAndEJBPassivation.xml:315 #, no-c-format -msgid "" -"The link between the persistence manager and the entity instances is " -"maintained using object references. The entity instances are serializable, " -"but the persistence manager (and in turn its persistence context) is not. " -"Therefore, the process of serialization works against this design. " -"Serialization can occur either when a SFSB or the HTTP session is " -"passivated. In order to sustain the activity in the application, the " -"persistence manager and the entity instances it manages must weather " -"serialization without losing their relationship. That's the aid that the MEI " -"provides." -msgstr "" -"Il collegamento tra il gestore della persistenza e le istanze degli entity " -"viene mantenuto usando i riferimenti oggetto. Le istanze entity sono " -"serializzabili, ma il gestore della persistenza non lo è (e quindi il suo " -"contesto di persistenza). Quindi il processo di serializzazione funziona " -"contro questo design. La serializzazione avviene anche quando un SFSB o " -"sessione HTTP sono passivati. Per sostenere l'attività nell'applicazione, il " -"gestore della persistenza e le istanze entity che gestisce devono esporre la " -"serializzazione senza perdere la loro relazione. E' questo l'aiuto che viene " -"fornito da MEI." +msgid "The link between the persistence manager and the entity instances is maintained using object references. The entity instances are serializable, but the persistence manager (and in turn its persistence context) is not. Therefore, the process of serialization works against this design. Serialization can occur either when a SFSB or the HTTP session is passivated. In order to sustain the activity in the application, the persistence manager and the entity instances it manages must weather serialization without losing their relationship. That's the aid that the MEI provides." +msgstr "Il collegamento tra il gestore della persistenza e le istanze degli entity viene mantenuto usando i riferimenti oggetto. Le istanze entity sono serializzabili, ma il gestore della persistenza non lo è (e quindi il suo contesto di persistenza). Quindi il processo di serializzazione funziona contro questo design. La serializzazione avviene anche quando un SFSB o sessione HTTP sono passivati. Per sostenere l'attività nell'applicazione, il gestore della persistenza e le istanze entity che gestisce devono esporre la serializzazione senza perdere la loro relazione. E' questo l'aiuto che viene fornito da MEI." #. Tag: title #: ClusteringAndEJBPassivation.xml:327 @@ -841,114 +423,33 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:329 -#, fuzzy, no-c-format -msgid "" -"Conversations were initially designed with stateful session beans (SFSBs) in " -"mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a complement to the " -"extended persistence context, known as a Seam-managed persistence context, " -"which works around a number of limitations in the specification (complex " -"propagation rules and lack of manual flushing). Both can be used with a SFSB." -msgstr "" -"Le conversazioni sono state inizialmente progettate avendo in mente gli " -"stateful session bean (SFSB), in primo luogo poiché la specifica EJB3 indica " -"gli SFSB come host del contesto di persistenza esteso. Seam introduce un " -"complemento al contesto di persistenza esteso, conosciuto col nome di " -"contesto di persistenza gestito da Seam, il quale risolve un certo numero di " -"limitazioni presenti nella specifica (le regole complesse di propagazione e " -"la mancanza di flush manuale). Entrambi possono essere usati con i SFSB." +#, no-c-format +msgid "Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a complement to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB." +msgstr "Le conversazioni sono state inizialmente progettate avendo in mente gli stateful session bean (SFSB), in primo luogo poiché la specifica EJB3 indica gli SFSB come host del contesto di persistenza esteso. Seam introduce un complemento al contesto di persistenza esteso, conosciuto col nome di contesto di persistenza gestito da Seam, il quale risolve un certo numero di limitazioni presenti nella specifica (le regole complesse di propagazione e la mancanza di flush manuale). Entrambi possono essere usati con i SFSB." #. Tag: para #: ClusteringAndEJBPassivation.xml:337 #, no-c-format -msgid "" -"A SFSB relies on a client to hold a reference to it in order to keep it " -"active. Seam has provided an ideal place for this reference in the " -"conversation context. Thus, for as long as the conversation context is " -"active, the SFSB is active. If an EntityManager is injected into that SFSB " -"using the annotation @PersistenceContext(EXTENDED), then that EntityManager " -"will be bound to the SFSB and remain open throughout its lifetime, the " -"lifetime of the conversation. If an EntityManager is injected using @In, " -"then that EntityManager is maintained by Seam and stored directly in the " -"conversation context, thus living for the lifetime of the conversation " -"independent of the lifetime of the SFSB." -msgstr "" -"Un SFSB si affida al client per mantenere un riferimento ad esso e per " -"mantenerlo attivo. Seam ha fornito un posto ideal per questo riferimento al " -"contesto di conversazione. Quindi fintantoché il contesto di conversazione " -"rimane attivo, il SFSB è attivo. Se un EntityManager viene iniettato in " -"questo SFSB usando l'annotazione @PersistenceContext(EXTENDED), allora tale " -"EntityManager verrà associato al SFSB e rimarrà aperto lungo tutto il ciclo " -"di vita della conversazione. Se un EntityManager viene iniettato usano @In, " -"allora tale EntityManager verrà mantenuto da Seam e memorizzato direttamente " -"nel contesto conversazione, quindi vivrà per tutto il ciclo di vita della " -"conversazione indipendente dal ciclo di vita del SFSB." +msgid "A SFSB relies on a client to hold a reference to it in order to keep it active. Seam has provided an ideal place for this reference in the conversation context. Thus, for as long as the conversation context is active, the SFSB is active. If an EntityManager is injected into that SFSB using the annotation @PersistenceContext(EXTENDED), then that EntityManager will be bound to the SFSB and remain open throughout its lifetime, the lifetime of the conversation. If an EntityManager is injected using @In, then that EntityManager is maintained by Seam and stored directly in the conversation context, thus living for the lifetime of the conversation independent of the lifetime of the SFSB." +msgstr "Un SFSB si affida al client per mantenere un riferimento ad esso e per mantenerlo attivo. Seam ha fornito un posto ideal per questo riferimento al contesto di conversazione. Quindi fintantoché il contesto di conversazione rimane attivo, il SFSB è attivo. Se un EntityManager viene iniettato in questo SFSB usando l'annotazione @PersistenceContext(EXTENDED), allora tale EntityManager verrà associato al SFSB e rimarrà aperto lungo tutto il ciclo di vita della conversazione. Se un EntityManager viene iniettato usano @In, allora tale EntityManager verrà mantenuto da Seam e memorizzato direttamente nel contesto conversazione, quindi vivrà per tutto il ciclo di vita della conversazione indipendente dal ciclo di vita del SFSB." #. Tag: para #: ClusteringAndEJBPassivation.xml:347 -#, fuzzy, no-c-format -msgid "" -"With all of that said, the Java EE container can passivate a SFSB, which " -"means it will serialize the object to an area of storage external to the " -"JVM. When this happens depends on the settings of the individual SFSB. This " -"process can even be disabled. However, the persistence context is not " -"serialized (is this only true of SMPC?). In fact, what happens depends " -"highly on the Java EE container. The spec is not very clear about this " -"situation. Many vendors just tell you not to let it happen if you need the " -"guarantees of the extended persistence context. Seam's approach is more " -"conservative. Seam basically doesn't trust the SFSB with the persistence " -"context or the entity instances. After each invocation of the SFSB, Seam " -"moves the reference to entity instance held by the SFSB into the current " -"conversation (and therefore into the HTTP session), nullifying those fields " -"on the SFSB. It then restores this references at the beginning of the next " -"invocation. Of course, Seam is already storing the persistence manager in " -"the conversation. Thus, when the SFSB passivates and later activates, it has " -"absolutely no averse affect on the application." -msgstr "" -"Con tutto ciò detto, il container Java EE può passivare un SFSB, il che " -"significa che verrà serializzato l'oggetto in un area di memorizzazione " -"esterna alla JVM. Quando questo avviene dipende dalle impostazione del " -"singolo SFSB. Questo processo può anche essere disabilitato. Comunque il " -"contesto di persistenza non è serializzato (questo è vero solo per SMPC?). " -"Infatti cosa succede dipende fortemente dal container Java EE. La specifica " -"non è molto chiara in proposito. Molti vendor dicono di non fare avvenire " -"questo se servono le garanzie del contesto di persistenza esteso. " -"L'approccio di Seam più conservativo. Seam non si fida del SFSB con il " -"contesto di persistenza o delle istanze entity. Dopo ogni invocazione del " -"SFSB, Seam sposta il riferimento all'istanza entity mantenuta dal SFSB " -"dentro l'attuale conversazione (e quindi nella sessione HTTP). mettendo a " -"null questi campi nel SFSB. Poi ripristina questi riferimenri all'inizio di " -"ogni invocazione. Certamente Seam sta già memorizzando il gestore della " -"persistenza nella conversazione. Perciò quando il SFSB passiva e poi si " -"riattiva, non c'è alcun effetto negativo sull'applicazione." +#, no-c-format +msgid "With all of that said, the Java EE container can passivate a SFSB, which means it will serialize the object to an area of storage external to the JVM. When this happens depends on the settings of the individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the guarantees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this references at the beginning of the next invocation. Of course, Seam is! already storing the persistence manager in the conversation. Thus, when the SFSB passivates and later activates, it has absolutely no averse affect on the application." +msgstr "Con tutto ciò detto, il container Java EE può passivare un SFSB, il che significa che verrà serializzato l'oggetto in un area di memorizzazione esterna alla JVM. Quando questo avviene dipende dalle impostazione del singolo SFSB. Questo processo può anche essere disabilitato. Comunque il contesto di persistenza non è serializzato (questo è vero solo per SMPC?). Infatti cosa succede dipende fortemente dal container Java EE. La specifica non è molto chiara in proposito. Molti vendor dicono di non fare avvenire questo se servono le garanzie del contesto di persistenza esteso. L'approccio di Seam più conservativo. Seam non si fida del SFSB con il contesto di persistenza o delle istanze entity. Dopo ogni invocazione del SFSB, Seam sposta il riferimento all'istanza entity mantenuta dal SFSB dentro l'attuale conversazione (e quindi nella sessione HTTP). mettendo a null questi campi nel SFSB. Poi ripristina questi riferimenri all'inizio di ogni invocazione. Certament! e Seam sta già memorizzando il gestore della persistenza nella conversazione. Perciò quando il SFSB passiva e poi si riattiva, non c'è alcun effetto negativo sull'applicazione." #. Tag: para #: ClusteringAndEJBPassivation.xml:363 #, no-c-format -msgid "" -"If you are using SFSBs in your application that hold references to extended " -"persistence contexts, and those SFSBs can passivate, then you must use the " -"MEI. This requirement holds even if you are using a single instance (not a " -"cluster). However, if you are using clustered SFSB, then this requirement " -"also applies." -msgstr "" -"Se si stanno usando degl SFSB che mantengono riferimenti a contesti di " -"persistenza estesi, e questi SFSB possono essere passivati, allora occorre " -"usare un MEI. Questo requisisto esiste anche se si adopera una singola " -"istanza (non un cluster). Comunque se si usa un SFSB clustered, questo " -"requisito permane comunque." +msgid "If you are using SFSBs in your application that hold references to extended persistence contexts, and those SFSBs can passivate, then you must use the MEI. This requirement holds even if you are using a single instance (not a cluster). However, if you are using clustered SFSB, then this requirement also applies." +msgstr "Se si stanno usando degl SFSB che mantengono riferimenti a contesti di persistenza estesi, e questi SFSB possono essere passivati, allora occorre usare un MEI. Questo requisisto esiste anche se si adopera una singola istanza (non un cluster). Comunque se si usa un SFSB clustered, questo requisito permane comunque." #. Tag: para #: ClusteringAndEJBPassivation.xml:371 #, no-c-format -msgid "" -"It is possible to disable passivation on a SFSB. See the <ulink url=\"http://" -"www.jboss.org/community/docs/DOC-9656\">Ejb3DisableSfsbPassivation</ulink> " -"page on the JBoss Wiki for details." -msgstr "" -"E' possibile disabilitare la passivazione su un SFSB. Si veda la pagina " -"<ulink url=\"http://www.jboss.org/community/docs/DOC-9656" -"\">Ejb3DisableSfsbPassivation</ulink> su JBoss Wiki." +msgid "It is possible to disable passivation on a SFSB. See the <ulink url=\"http://www.jboss.org/community/docs/DOC-9656\">Ejb3DisableSfsbPassivation</ulink> page on the JBoss Wiki for details." +msgstr "E' possibile disabilitare la passivazione su un SFSB. Si veda la pagina <ulink url=\"http://www.jboss.org/community/docs/DOC-9656\">Ejb3DisableSfsbPassivation</ulink> su JBoss Wiki." #. Tag: title #: ClusteringAndEJBPassivation.xml:379 @@ -959,51 +460,14 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:381 #, no-c-format -msgid "" -"Dealing with passivation of a SFSB works by leveraging the HTTP session. But " -"what happens when the HTTP session passivates? This happens in a clustered " -"environment with session replication enabled. This case is much tricker to " -"deal with and is where a bulk of the MEI infrastructure comes into play. In " -"thise case, the persistence manager is going to be destroyed because it " -"cannot be serialized. Seam handles this deconstruction (hence ensuring that " -"the HTTP session serializes properly). But what happens on the other end. " -"Well, when the MEI sticks an entity instance into the conversation, it " -"embeds the instance in a wrapper that provides information on how to " -"reassociate the instance with a persistence manager post-serialization. So " -"when the application jumps to another node in the cluster (presumably " -"because the target node went down) the MEI infrastruture essentially " -"reconstructs the persistence context. The huge drawback here is that since " -"the persistence context is being reconstructed (from the database), pending " -"changes are dropped. However, what Seam does do is ensure that if the entity " -"instance is versioned, that the guarantees of optimistic locking are upheld. " -"(why isn't the dirty state transfered?)" -msgstr "" -"La passivazione di un SFSB funziona facendo leva sulla sessione HTTP. Ma " -"cosa succede quando la sessione HTTP passiva? Questo capita in un ambiente " -"clusteres cone la replica della sessioneattivata. Questo caso è più " -"problematico da gestire ed avviene quando entra in gioco una parte " -"dell'infrastruttura MEI. In questo caso il gestore della persistenza sta per " -"essere distrutto, poiché non può essere serializzato. Seam gestisce questa " -"decostruzione (che assicura che la sessione HTTP serializzi in modo " -"corretto). Ma cosa avviene dall'altro lato? Quando MEI colloca un'istanza " -"entity in un conversazione, incorpora l'istanza in un wrapper che fornisce " -"informazioni su come riassociare l'istanza col gestore di persistenza dopo " -"la serializzazione. Perciò quando l'applicazione passa su un altro nodo del " -"cluster (presumibilmente poiché il nodo target è sceso) l'infrastruttura MEI " -"verrà ricostruita (dal database), i cambiamenti pendenti verranno " -"abbandonati. Comunque quello che Seam fa è assicurare che se l'istanza " -"entity viene versionata, le garanzie di lock ottimistico vengono mantenute. " -"(Perche lo stato dirty non viene trasferito?)" +msgid "Dealing with passivation of a SFSB works by leveraging the HTTP session. But what happens when the HTTP session passivates? This happens in a clustered environment with session replication enabled. This case is much tricker to deal with and is where a bulk of the MEI infrastructure comes into play. In thise case, the persistence manager is going to be destroyed because it cannot be serialized. Seam handles this deconstruction (hence ensuring that the HTTP session serializes properly). But what happens on the other end. Well, when the MEI sticks an entity instance into the conversation, it embeds the instance in a wrapper that provides information on how to reassociate the instance with a persistence manager post-serialization. So when the application jumps to another node in the cluster (presumably because the target node went down) the MEI infrastruture essentially reconstructs the persistence context. The huge drawback here is that since the persistence context is ! being reconstructed (from the database), pending changes are dropped. However, what Seam does do is ensure that if the entity instance is versioned, that the guarantees of optimistic locking are upheld. (why isn't the dirty state transfered?)" +msgstr "La passivazione di un SFSB funziona facendo leva sulla sessione HTTP. Ma cosa succede quando la sessione HTTP passiva? Questo capita in un ambiente clusteres cone la replica della sessioneattivata. Questo caso è più problematico da gestire ed avviene quando entra in gioco una parte dell'infrastruttura MEI. In questo caso il gestore della persistenza sta per essere distrutto, poiché non può essere serializzato. Seam gestisce questa decostruzione (che assicura che la sessione HTTP serializzi in modo corretto). Ma cosa avviene dall'altro lato? Quando MEI colloca un'istanza entity in un conversazione, incorpora l'istanza in un wrapper che fornisce informazioni su come riassociare l'istanza col gestore di persistenza dopo la serializzazione. Perciò quando l'applicazione passa su un altro nodo del cluster (presumibilmente poiché il nodo target è sceso) l'infrastruttura MEI verrà ricostruita (dal database), i cambiamenti pendenti verranno abbandonati. Comunque quel! lo che Seam fa è assicurare che se l'istanza entity viene versionata, le garanzie di lock ottimistico vengono mantenute. (Perche lo stato dirty non viene trasferito?)" #. Tag: para #: ClusteringAndEJBPassivation.xml:397 #, no-c-format -msgid "" -"If you are deploying your application in a cluster and using HTTP session " -"replication, you must use the MEI." -msgstr "" -"Se si esegue il deploy dell'applicazione in un cluster e si usa la replica " -"della sessione HTTP, occorre usare MEI." +msgid "If you are deploying your application in a cluster and using HTTP session replication, you must use the MEI." +msgstr "Se si esegue il deploy dell'applicazione in un cluster e si usa la replica della sessione HTTP, occorre usare MEI." #. Tag: title #: ClusteringAndEJBPassivation.xml:404 @@ -1014,16 +478,6 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:406 #, no-c-format -msgid "" -"The important point of this section is that the MEI is there for a reason. " -"It's there to ensure that the extended persistence context can retain intact " -"in the face of passivation (of either a SFSB or the HTTP session). This " -"matters because the natural design of Seam applications (and conversational " -"state in general) revolve around the state of this resource." -msgstr "" -"Il punto importante di questa sezione è che il MEI esiste per una ragione. " -"Per assicurare che il contesto di persistenza esteso possa rimanenre integro " -"anche con la passivazione (sia di un SFSB sia di una sessione HTTP). Questo " -"è importante poiché il progetto originale delle applicazione Seam (ed in " -"generale dello stato conversazione) ruota attorno allo stato di questa " -"risorsa." +msgid "The important point of this section is that the MEI is there for a reason. It's there to ensure that the extended persistence context can retain intact in the face of passivation (of either a SFSB or the HTTP session). This matters because the natural design of Seam applications (and conversational state in general) revolve around the state of this resource." +msgstr "Il punto importante di questa sezione è che il MEI esiste per una ragione. Per assicurare che il contesto di persistenza esteso possa rimanenre integro anche con la passivazione (sia di un SFSB sia di una sessione HTTP). Questo è importante poiché il progetto originale delle applicazione Seam (ed in generale dello stato conversazione) ruota attorno allo stato di questa risorsa." +

15 years, 7 months

1
0
0 / 0

Seam SVN: r11065 - in branches/community/Seam_2_1/doc/Seam_Reference_Guide: bn-IN and 23 other directories.

by seam-commits＠lists.jboss.org

Author: nico.ben Date: 2009-06-01 14:46:43 -0400 (Mon, 01 Jun 2009) New Revision: 11065 Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Annotations.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Author_Group.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Book_Info.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Cache.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Components.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Concepts.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Configuration.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Controls.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Conversations.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Dependencies.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Drools.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Elenhancements.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Events.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Excel.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Feedback.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Framework.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gettingstarted.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Glassfish.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Groovy.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Guice.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gwt.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Hsearch.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/I18n.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Itext.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jbpm.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jms.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Mail.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Performance.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Persistence.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Preface.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Remoting.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Revision_History.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Rss.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Security.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Spring.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Testing.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Text.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tools.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tutorial.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Validation.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Weblogic.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Webservices.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Websphere.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Wicket.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Xml.pot branches/community/Seam_2_1/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po Log: Regenerated POT and updated all POs Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/as-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/bn-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/de-DE/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-ES/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/es-MX/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/fr-FR/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/gu-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/hi-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-30 15:23+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" @@ -23,19 +23,45 @@ #: ClusteringAndEJBPassivation.xml:7 #, no-c-format msgid "Please note that this chapter is still being reviewed. Tread carefully." -msgstr "Si noti che questo capitolo è ancora sotto revisione. Maneggiare con cura." +msgstr "" +"Si noti che questo capitolo è ancora sotto revisione. Maneggiare con cura." #. Tag: para #: ClusteringAndEJBPassivation.xml:10 #, no-c-format -msgid "This chapter covers two distinct topics that happen share a common solution in Seam, (web) clustering and EJB passivation. Therefore, they are addressed together in this reference manual. Although performance tends to be grouped in this category as well, it's kept separate because the focus of this chapter is on the programming model and how it's affected by the use of the aforementioned features." -msgstr "Questo capitolo copre due distinti argomenti che condividono un soluzione comune in Seam, (web) clustering e passivazione EJB. Quindi, sono trattati assieme in questo manuale. Sebbene anche la performance tende ad essere raggruppata in questa categoria, essa viene mantenuta separata poiché il focus di questo capitolo è sul modello di programmazione e su come questo è influenzato dall'uso delle funzionalità sopracitate." +msgid "" +"This chapter covers two distinct topics that happen share a common solution " +"in Seam, (web) clustering and EJB passivation. Therefore, they are addressed " +"together in this reference manual. Although performance tends to be grouped " +"in this category as well, it's kept separate because the focus of this " +"chapter is on the programming model and how it's affected by the use of the " +"aforementioned features." +msgstr "" +"Questo capitolo copre due distinti argomenti che condividono un soluzione " +"comune in Seam, (web) clustering e passivazione EJB. Quindi, sono trattati " +"assieme in questo manuale. Sebbene anche la performance tende ad essere " +"raggruppata in questa categoria, essa viene mantenuta separata poiché il " +"focus di questo capitolo è sul modello di programmazione e su come questo è " +"influenzato dall'uso delle funzionalità sopracitate." #. Tag: para #: ClusteringAndEJBPassivation.xml:17 #, no-c-format -msgid "In this chapter you will learn how Seam manages the passivation of Seam components and entity instances, how to activate this feature, and how this feature is related to clustering. You will also learn how to deploy a Seam application into a cluster and verify that HTTP session replication is working properly. Let's start with a little background on clustering and see an example of how you deploy a Seam application to a JBoss AS cluster." -msgstr "In questo capitolo si apprenderà come Seam gestisce la passivazione dei componenti Seam e degli entity, come attivare questa funzionalità e come questa funzionalità è collegata al clustering. Inoltre si apprenderà come eseguire il deploy di un'applicazione Seam in un cluster e verificare che la replica della sessione HTTP funzioni correttamente. Iniziamo con un pò di background sul clustering e vediamo come fare il deploy di un'applicazione Seam in un cluster JBoss AS." +msgid "" +"In this chapter you will learn how Seam manages the passivation of Seam " +"components and entity instances, how to activate this feature, and how this " +"feature is related to clustering. You will also learn how to deploy a Seam " +"application into a cluster and verify that HTTP session replication is " +"working properly. Let's start with a little background on clustering and see " +"an example of how you deploy a Seam application to a JBoss AS cluster." +msgstr "" +"In questo capitolo si apprenderà come Seam gestisce la passivazione dei " +"componenti Seam e degli entity, come attivare questa funzionalità e come " +"questa funzionalità è collegata al clustering. Inoltre si apprenderà come " +"eseguire il deploy di un'applicazione Seam in un cluster e verificare che la " +"replica della sessione HTTP funzioni correttamente. Iniziamo con un pò di " +"background sul clustering e vediamo come fare il deploy di un'applicazione " +"Seam in un cluster JBoss AS." #. Tag: title #: ClusteringAndEJBPassivation.xml:25 @@ -46,26 +72,87 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:27 #, no-c-format -msgid "Clustering (more formally web clustering) allows an application to run on two or more parallel servers (i.e., nodes) while providing a uniform view of the application to clients. Load is distributed across the servers in such a way that if one or more of the servers fails, the application is still accessible via any of the surviving nodes. This topology is crucial for building scalable enterprise applications as performance and availability can be improved simply by adding nodes. But it brings up an important question. <emphasis>What happens to the state that was on the server that failed?</emphasis>" -msgstr "Il clustering (più formalmente web clustering) consente ad un'applicazione di girare su due o più server paralleli (cioè, nodi) mentre viene fornita ai client una vista uniforme dell'applicazione. Il carico è distribuito sui server in modo tale che se uno o più server fallisce, l'applicazione continua ad essere accessibile tramite gli altri nodi. Questa tipologia è cruciale per la costruzione di applicazioni enterprise scalabili in performance e la disponibilità può essere migliorata semplicemente aggiungendo nodi. Ma si giunge ad una domanda importante. <emphasis>Cosa succede allo stato presente su un server che ha fallito?</emphasis>" +msgid "" +"Clustering (more formally web clustering) allows an application to run on " +"two or more parallel servers (i.e., nodes) while providing a uniform view of " +"the application to clients. Load is distributed across the servers in such a " +"way that if one or more of the servers fails, the application is still " +"accessible via any of the surviving nodes. This topology is crucial for " +"building scalable enterprise applications as performance and availability " +"can be improved simply by adding nodes. But it brings up an important " +"question. <emphasis>What happens to the state that was on the server that " +"failed?</emphasis>" +msgstr "" +"Il clustering (più formalmente web clustering) consente ad un'applicazione " +"di girare su due o più server paralleli (cioè, nodi) mentre viene fornita ai " +"client una vista uniforme dell'applicazione. Il carico è distribuito sui " +"server in modo tale che se uno o più server fallisce, l'applicazione " +"continua ad essere accessibile tramite gli altri nodi. Questa tipologia è " +"cruciale per la costruzione di applicazioni enterprise scalabili in " +"performance e la disponibilità può essere migliorata semplicemente " +"aggiungendo nodi. Ma si giunge ad una domanda importante. <emphasis>Cosa " +"succede allo stato presente su un server che ha fallito?</emphasis>" #. Tag: para #: ClusteringAndEJBPassivation.xml:36 #, no-c-format -msgid "Since day one, Seam has always provided support for stateful applications running in a cluster. Up to this point, you have learned that Seam provides state management in the form of additional scopes and by governing the life cycle of stateful (scoped) components. But state management in Seam goes beyond creating, storing and destroying instances. Seam tracks changes to JavaBean components and stores the changes at strategic points during the request so that the changes can be restored when the request shifts to a secondary node in the cluster. Fortunately, monitoring and replication of stateful EJB components is already handled by the EJB server, so this feature of Seam is intended to put stateful JavaBeans on par with their EJB cohorts." -msgstr "Sin dal primo giorno Seam ha sempre fornito il supporto alle applicazioni stateful in azione dentro un cluster. Fino ad ora si è appreso che Seam fornisce la gestione dello stato aggiungendo degli scope e governando il ciclo di vita dei componenti stateful (con scope). Ma la gestione dello stato in Seam va oltre alla creazione, memorizzazione e distruzione di istanze. Seam traccia i cambiamenti ai componenti JavaBean e memorizza i cambiamenti in punti strategici durante la richiesta, affinché i cambiamenti vengano ripristinati quando la richiesta passa su un nodo secondario del cluster. Fortunatamente il monitoraggio e la replica di componenti EJB stateful viene già gestita dal server EJB, quindi tale funzionalità di Seam serve per mettere i JavaBean a fianco dei suoi compagni EJB." +msgid "" +"Since day one, Seam has always provided support for stateful applications " +"running in a cluster. Up to this point, you have learned that Seam provides " +"state management in the form of additional scopes and by governing the life " +"cycle of stateful (scoped) components. But state management in Seam goes " +"beyond creating, storing and destroying instances. Seam tracks changes to " +"JavaBean components and stores the changes at strategic points during the " +"request so that the changes can be restored when the request shifts to a " +"secondary node in the cluster. Fortunately, monitoring and replication of " +"stateful EJB components is already handled by the EJB server, so this " +"feature of Seam is intended to put stateful JavaBeans on par with their EJB " +"cohorts." +msgstr "" +"Sin dal primo giorno Seam ha sempre fornito il supporto alle applicazioni " +"stateful in azione dentro un cluster. Fino ad ora si è appreso che Seam " +"fornisce la gestione dello stato aggiungendo degli scope e governando il " +"ciclo di vita dei componenti stateful (con scope). Ma la gestione dello " +"stato in Seam va oltre alla creazione, memorizzazione e distruzione di " +"istanze. Seam traccia i cambiamenti ai componenti JavaBean e memorizza i " +"cambiamenti in punti strategici durante la richiesta, affinché i cambiamenti " +"vengano ripristinati quando la richiesta passa su un nodo secondario del " +"cluster. Fortunatamente il monitoraggio e la replica di componenti EJB " +"stateful viene già gestita dal server EJB, quindi tale funzionalità di Seam " +"serve per mettere i JavaBean a fianco dei suoi compagni EJB." #. Tag: para #: ClusteringAndEJBPassivation.xml:46 -#, no-c-format -msgid "But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and Hibernate entities) don't become detatched during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter." -msgstr "Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei componenti JavaBean, Seam assicura che le istanze entity gestite (cioè entity JPA e Hibernate) non divengano detached durante la replica. Seam mantiene un record di entity che sono caricati e li carica automaticamente nel nodo secondario. Occorre comunque usare un contesto di persistenza gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate informazioni su questa funzionalità vengono fornite nella seconda parte del capitolo." +#, fuzzy, no-c-format +msgid "" +"But wait, there's more! Seam also offers an incredibly unique feature for " +"clustered applications. In addition to monitoring JavaBean components, Seam " +"ensures that managed entity instances (i.e. JPA and Hibernate entities) " +"don't become detached during replication. Seam keeps a record of the " +"entities that are loaded and automatically loads them on the secondary node. " +"You must, however, be using a Seam-managed persistence context to get this " +"feature. More in depth information about this feature is provided in the " +"second half of this chapter." +msgstr "" +"Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica " +"caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei " +"componenti JavaBean, Seam assicura che le istanze entity gestite (cioè " +"entity JPA e Hibernate) non divengano detached durante la replica. Seam " +"mantiene un record di entity che sono caricati e li carica automaticamente " +"nel nodo secondario. Occorre comunque usare un contesto di persistenza " +"gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate " +"informazioni su questa funzionalità vengono fornite nella seconda parte del " +"capitolo." #. Tag: para #: ClusteringAndEJBPassivation.xml:55 #, no-c-format -msgid "Now that you understand what features Seam offers to support a clustered environment, let's look at how you program for clustering." -msgstr "Ora che si è capito quali funzionalità offre Seam per supportare l'ambiente clustered, guardiamo come si programma un cluster." +msgid "" +"Now that you understand what features Seam offers to support a clustered " +"environment, let's look at how you program for clustering." +msgstr "" +"Ora che si è capito quali funzionalità offre Seam per supportare l'ambiente " +"clustered, guardiamo come si programma un cluster." #. Tag: title #: ClusteringAndEJBPassivation.xml:61 @@ -75,57 +162,137 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:62 -#, no-c-format -msgid "Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered environment must implement the <literal>Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the session attribute on every change of the object." -msgstr "Un componente JavaBean mutabile con scope sessione o conversazione che verrà usato in un ambiente clustered deve implementare l'interfaccia <literal>Mutable</literal> dell'API Seam. Come parte del contratto, il contratto deve mantenere un dirty flag che viene segnato e resettato dal metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per determinare se è necessario replicare il componente. Questo evita di dover usare la più problematica API dei Servlet per aggiungere e rimuovere l'attributo sessione ad ogni cambiamento dell'oggetto." +#, fuzzy, no-c-format +msgid "" +"Any session- or conversation-scoped mutable JavaBean component that will be " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " +"<literal>clearDirty()</literal> method. Seam calls this method to determine " +"if it is necessary to replicate the component. This avoids having to use the " +"more cumbersome Servlet API to add and remove the session attribute on every " +"change of the object." +msgstr "" +"Un componente JavaBean mutabile con scope sessione o conversazione che verrà " +"usato in un ambiente clustered deve implementare l'interfaccia " +"<literal>Mutable</literal> dell'API Seam. Come parte del contratto, il " +"contratto deve mantenere un dirty flag che viene segnato e resettato dal " +"metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per " +"determinare se è necessario replicare il componente. Questo evita di dover " +"usare la più problematica API dei Servlet per aggiungere e rimuovere " +"l'attributo sessione ad ogni cambiamento dell'oggetto." #. Tag: para #: ClusteringAndEJBPassivation.xml:70 #, no-c-format -msgid "You also must ensure that all session- and conversation-scoped JavaBean components are Serializable. Additional, all fields of a stateful component (EJB or JavaBean) must Serializable unless the field is marked transient or set to null in a <literal>@PrePassivate</literal> method. You can restore the value of a transient or nullified field in a <literal>@PostActivate</literal> method." -msgstr "Bisogna assicurarsi che tutti i componenti JavaBean con scope sessione e conversazione siano Serializable. Inoltre tutti i campi di un componente stateful (EJB o JavaBean) devono essere Serializable amenoché siano marcati come transient o impostati a null in un metodo <literal>@PrePassivate</literal>. Si può ripristinare il valore di un campo transient o null in un metodo <literal>@PostActivate</literal>." +msgid "" +"You also must ensure that all session- and conversation-scoped JavaBean " +"components are Serializable. Additional, all fields of a stateful component " +"(EJB or JavaBean) must Serializable unless the field is marked transient or " +"set to null in a <literal>@PrePassivate</literal> method. You can restore " +"the value of a transient or nullified field in a <literal>@PostActivate</" +"literal> method." +msgstr "" +"Bisogna assicurarsi che tutti i componenti JavaBean con scope sessione e " +"conversazione siano Serializable. Inoltre tutti i campi di un componente " +"stateful (EJB o JavaBean) devono essere Serializable amenoché siano marcati " +"come transient o impostati a null in un metodo <literal>@PrePassivate</" +"literal>. Si può ripristinare il valore di un campo transient o null in un " +"metodo <literal>@PostActivate</literal>." #. Tag: para #: ClusteringAndEJBPassivation.xml:76 #, no-c-format -msgid "One area where people often get bitten is by using <literal>List.subList</literal> to create a list. The resulting list is not Serializable. So watch out for situations like that. If hit a <literal>java.io.NotSerializableException</literal> and cannot locate the culprit at first glance, you can put a breakpoint on this exception, run the application server in debug mode and attach a debugger (such as Eclipse) to see what deserialization is choking on." -msgstr "Un'area in cui spesso le persone hanno problemi è con l'uso di <literal>List.subList</literal> per creare una lista. La lista risultante non è Serializable. Quindi attenzione a queste situazioni. Se ci si imbatte in una <literal>java.io.NotSerializableException</literal> e non si riescead individuare subito il colpevole, si può mettere un breakpoint su quest'eccezione, avviare l'application server in modalità debug ed attaccare il debugger (come in Eclipse) per vedere quale deserializzazione causa il problema." +msgid "" +"One area where people often get bitten is by using <literal>List.subList</" +"literal> to create a list. The resulting list is not Serializable. So watch " +"out for situations like that. If hit a <literal>java.io." +"NotSerializableException</literal> and cannot locate the culprit at first " +"glance, you can put a breakpoint on this exception, run the application " +"server in debug mode and attach a debugger (such as Eclipse) to see what " +"deserialization is choking on." +msgstr "" +"Un'area in cui spesso le persone hanno problemi è con l'uso di <literal>List." +"subList</literal> per creare una lista. La lista risultante non è " +"Serializable. Quindi attenzione a queste situazioni. Se ci si imbatte in una " +"<literal>java.io.NotSerializableException</literal> e non si riescead " +"individuare subito il colpevole, si può mettere un breakpoint su " +"quest'eccezione, avviare l'application server in modalità debug ed attaccare " +"il debugger (come in Eclipse) per vedere quale deserializzazione causa il " +"problema." #. Tag: para #: ClusteringAndEJBPassivation.xml:84 -#, no-c-format -msgid "Please note that clustering does not work with hot deployable compoennts. But then again, you shouldn't be using hot deployable components in a non-development environment anyway." -msgstr "Si noti che il clustering non funziona con componenti hot deployable. Ma comunque non si dovrebbero usare i componenti hot deployable in un ambiente non di sviluppo." +#, fuzzy, no-c-format +msgid "" +"Please note that clustering does not work with hot deployable components. " +"But then again, you shouldn't be using hot deployable components in a non-" +"development environment anyway." +msgstr "" +"Si noti che il clustering non funziona con componenti hot deployable. Ma " +"comunque non si dovrebbero usare i componenti hot deployable in un ambiente " +"non di sviluppo." #. Tag: title #: ClusteringAndEJBPassivation.xml:92 #, no-c-format -msgid "Deploying a Seam application to a JBoss AS cluster with session replication" -msgstr "Deploy di un'applicazione Seam in un cluster JBoss AS con replica di sessione" +msgid "" +"Deploying a Seam application to a JBoss AS cluster with session replication" +msgstr "" +"Deploy di un'applicazione Seam in un cluster JBoss AS con replica di sessione" #. Tag: para #: ClusteringAndEJBPassivation.xml:94 #, no-c-format -msgid "The procedure outlined in this tutorial has been validated with an seam-gen application and the Seam booking example." -msgstr "Questa procedura descritta nel tutorial è stata validata con un'applicazione seam-gen e nell'esempio Prenotazione." +msgid "" +"The procedure outlined in this tutorial has been validated with an seam-gen " +"application and the Seam booking example." +msgstr "" +"Questa procedura descritta nel tutorial è stata validata con un'applicazione " +"seam-gen e nell'esempio Prenotazione." #. Tag: para #: ClusteringAndEJBPassivation.xml:99 #, no-c-format -msgid "In the tutorial, I assume that the IP addresses of the master and slave servers are 192.168.1.2 and 192.168.1.3, respectively. I am intentionally not using the mod_jk load balancer so that it's easier to validate that both nodes are responding to requests and can share sessions." -msgstr "In questo tutorial si assume che gli indirizzi IP dei server master e slave siano rispettivamente 192.168.1.2 e 192.168.1.3. Intenzionalmente non viene usato il bilanciatore di carico mod_jk, quindi è più facile validate che entrambi i nodi stiano rispondendo alle richieste e possano condividere le sessioni." +msgid "" +"In the tutorial, I assume that the IP addresses of the master and slave " +"servers are 192.168.1.2 and 192.168.1.3, respectively. I am intentionally " +"not using the mod_jk load balancer so that it's easier to validate that both " +"nodes are responding to requests and can share sessions." +msgstr "" +"In questo tutorial si assume che gli indirizzi IP dei server master e slave " +"siano rispettivamente 192.168.1.2 e 192.168.1.3. Intenzionalmente non viene " +"usato il bilanciatore di carico mod_jk, quindi è più facile validate che " +"entrambi i nodi stiano rispondendo alle richieste e possano condividere le " +"sessioni." #. Tag: para #: ClusteringAndEJBPassivation.xml:105 #, no-c-format -msgid "I'm using the farm deployment method in these instructions, though you could also deploy the application normally and allow the two servers to negotiate a master/slave relationship based on startup order." -msgstr "In queste istruzioni si sta usando il metodo di sviluppo farm, sebbene si possa fare normalmente il deploy dell'applicazione e consentire ai due server di negoziare una relazione master/slave basata sull'ordine di avvio." +msgid "" +"I'm using the farm deployment method in these instructions, though you could " +"also deploy the application normally and allow the two servers to negotiate " +"a master/slave relationship based on startup order." +msgstr "" +"In queste istruzioni si sta usando il metodo di sviluppo farm, sebbene si " +"possa fare normalmente il deploy dell'applicazione e consentire ai due " +"server di negoziare una relazione master/slave basata sull'ordine di avvio." #. Tag: para #: ClusteringAndEJBPassivation.xml:111 #, no-c-format -msgid "JBoss AS clustering relies on UDP multicasting provided by jGroups. The SELinux configuration that ships with RHEL/Fedora blocks these packets by default. You can allow them to pass by modifying the iptables rules (as root). The following commands apply to an IP address that matches 192.168.1.x." -msgstr "JBoss AS clustering si basa sul multicasting UDP fornito da jGroups. La configurazione SELinux che è inclusa in RHEL/Fedora di default blocca questi pacchetti. Si può consentire di lasciarli passare modificando le regole iptables (come root). I seguenti comandi si applicano ad un indirizzo IP che corrisponde a 192.168.1.x." +msgid "" +"JBoss AS clustering relies on UDP multicasting provided by jGroups. The " +"SELinux configuration that ships with RHEL/Fedora blocks these packets by " +"default. You can allow them to pass by modifying the iptables rules (as " +"root). The following commands apply to an IP address that matches 192.168.1." +"x." +msgstr "" +"JBoss AS clustering si basa sul multicasting UDP fornito da jGroups. La " +"configurazione SELinux che è inclusa in RHEL/Fedora di default blocca questi " +"pacchetti. Si può consentire di lasciarli passare modificando le regole " +"iptables (come root). I seguenti comandi si applicano ad un indirizzo IP che " +"corrisponde a 192.168.1.x." #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:116 @@ -144,8 +311,12 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:117 #, no-c-format -msgid "Detailed information can be found on <ulink url=\"http://www.jboss.org/community/docs/DOC-11935\">this page</ulink> on the JBoss Wiki." -msgstr "Maggiori dettagli possono essere trovati nella <ulink url=\"http://www.jboss.org/community/docs/DOC-11935\">pagina</ulink> del JBoss Wiki." +msgid "" +"Detailed information can be found on <ulink url=\"http://www.jboss.org/" +"community/docs/DOC-11935\">this page</ulink> on the JBoss Wiki." +msgstr "" +"Maggiori dettagli possono essere trovati nella <ulink url=\"http://www.jboss." +"org/community/docs/DOC-11935\">pagina</ulink> del JBoss Wiki." #. Tag: para #: ClusteringAndEJBPassivation.xml:122 @@ -156,26 +327,47 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:125 #, no-c-format -msgid "Deploy the JDBC driver to server/all/lib/ on both instances if not using HSQLDB" -msgstr "Fare il deploy del driver JDBC in server/all/lib/ su entrambe le istanze se non si usa HSQLDB" +msgid "" +"Deploy the JDBC driver to server/all/lib/ on both instances if not using " +"HSQLDB" +msgstr "" +"Fare il deploy del driver JDBC in server/all/lib/ su entrambe le istanze se " +"non si usa HSQLDB" #. Tag: para #: ClusteringAndEJBPassivation.xml:128 #, no-c-format -msgid "Add <literal><distributable/></literal> as the first child element in WEB-INF/web.xml" -msgstr "Aggiungere <literal><distributable/></literal> come primo elemento figlio in WEB-INF/web.xml" +msgid "" +"Add <literal><distributable/></literal> as the first child element in WEB-" +"INF/web.xml" +msgstr "" +"Aggiungere <literal><distributable/></literal> come primo elemento figlio " +"in WEB-INF/web.xml" #. Tag: para #: ClusteringAndEJBPassivation.xml:131 #, no-c-format -msgid "Set the <literal>distributable</literal> property on <literal>org.jboss.seam.core.init</literal> to true to enable the ManagedEntityInterceptor (i.e., <literal><![CDATA[<core:init distributable=\"true\"/>]]></literal>)" -msgstr "Impostare la proprietà <literal>distributable</literal> su <literal>org.jboss.seam.core.init</literal> a true per abilitare il ManagedEntityInterceptor (cioè, <literal><![CDATA[<core:init distributable=\"true\"/>]]></literal>)" +msgid "" +"Set the <literal>distributable</literal> property on <literal>org.jboss.seam." +"core.init</literal> to true to enable the ManagedEntityInterceptor (i.e., " +"<literal><![CDATA[<core:init distributable=\"true\"/>]]></literal>)" +msgstr "" +"Impostare la proprietà <literal>distributable</literal> su <literal>org." +"jboss.seam.core.init</literal> a true per abilitare il " +"ManagedEntityInterceptor (cioè, <literal><![CDATA[<core:init distributable=" +"\"true\"/>]]></literal>)" #. Tag: para #: ClusteringAndEJBPassivation.xml:136 #, no-c-format -msgid "Ensure you have two IP addresses available (two computers, two network cards, or two IP addressses bound to the same interface). I'll assume the two IP address are 192.168.1.2 and 192.168.1.3" -msgstr "Assicurarsi di avere disponibili due indirizzi IP (due computer, due schede di rete oppure due indirizzi IP sulla stessa interfaccia). Si assume che i due indirizzi IP siano 192.168.1.2 e 192.168.1.3" +msgid "" +"Ensure you have two IP addresses available (two computers, two network " +"cards, or two IP addressses bound to the same interface). I'll assume the " +"two IP address are 192.168.1.2 and 192.168.1.3" +msgstr "" +"Assicurarsi di avere disponibili due indirizzi IP (due computer, due schede " +"di rete oppure due indirizzi IP sulla stessa interfaccia). Si assume che i " +"due indirizzi IP siano 192.168.1.2 e 192.168.1.3" #. Tag: para #: ClusteringAndEJBPassivation.xml:141 @@ -192,14 +384,19 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:143 #, no-c-format -msgid "The log should report that there are 1 cluster members and 0 other members." +msgid "" +"The log should report that there are 1 cluster members and 0 other members." msgstr "Il log dovrebbe riportare che c'è 1 membro cluster e 0 altri membri." #. Tag: para #: ClusteringAndEJBPassivation.xml:146 #, no-c-format -msgid "Verify that the server/all/farm directory is empty in the slave JBoss AS instance" -msgstr "Verificare che la directory server/all/farm sia vuota nell'istanza slave di JBoss AS" +msgid "" +"Verify that the server/all/farm directory is empty in the slave JBoss AS " +"instance" +msgstr "" +"Verificare che la directory server/all/farm sia vuota nell'istanza slave di " +"JBoss AS" #. Tag: para #: ClusteringAndEJBPassivation.xml:149 @@ -216,8 +413,12 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:151 #, no-c-format -msgid "The log should report that there are 2 cluster members and 1 other members. It should also show the state being retrieved from the master." -msgstr "Il log dovrebbe riportare che ci sono 2 membri cluster e 1 altro membro. Dovrebbe anche mostrare che lo stato viene recuperato dal master." +msgid "" +"The log should report that there are 2 cluster members and 1 other members. " +"It should also show the state being retrieved from the master." +msgstr "" +"Il log dovrebbe riportare che ci sono 2 membri cluster e 1 altro membro. " +"Dovrebbe anche mostrare che lo stato viene recuperato dal master." #. Tag: para #: ClusteringAndEJBPassivation.xml:155 @@ -228,8 +429,14 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:156 #, no-c-format -msgid "In the log of the master you should see acknowledgement of the deployment. In the log of the slave you should see a corresponding message acknowledging the deployment to the slave." -msgstr "Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log dello slave si dovrebbe vedere il corrispondente messaggio di acknowledgement del deploy per lo slave." +msgid "" +"In the log of the master you should see acknowledgement of the deployment. " +"In the log of the slave you should see a corresponding message acknowledging " +"the deployment to the slave." +msgstr "" +"Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log " +"dello slave si dovrebbe vedere il corrispondente messaggio di " +"acknowledgement del deploy per lo slave." #. Tag: para #: ClusteringAndEJBPassivation.xml:160 @@ -240,32 +447,63 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:161 #, no-c-format -msgid "In the log of the master you should see acknowledgement of the deployment. In the log of the slave you should see a corresponding message acknowledging the deployment to the slave. Note that you may have to wait up to 3 minutes for the deployed archive to be transfered." -msgstr "Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log dello slave si dovrebbe vedere il corrispondente messaggio di acknowledgement del deploy per lo slave. Si noti che si potrebbe dover attendere fino a 3 minuti perché venga trasferito l'archivio deployato." +msgid "" +"In the log of the master you should see acknowledgement of the deployment. " +"In the log of the slave you should see a corresponding message acknowledging " +"the deployment to the slave. Note that you may have to wait up to 3 minutes " +"for the deployed archive to be transfered." +msgstr "" +"Nel log del master si dovrebbe vedere l'acknowledgement del deploy. Nel log " +"dello slave si dovrebbe vedere il corrispondente messaggio di " +"acknowledgement del deploy per lo slave. Si noti che si potrebbe dover " +"attendere fino a 3 minuti perché venga trasferito l'archivio deployato." #. Tag: para #: ClusteringAndEJBPassivation.xml:166 #, no-c-format -msgid "You're application is now running in a cluster with HTTP session replication! But, of course, you are going to want to validate that the clustering actually works." -msgstr "La vostra applicazione sta girando in un cluster con replica della sessione HTTP! Ma certamente si vuole validate il fatto che il clustering sta funzionando." +msgid "" +"You're application is now running in a cluster with HTTP session " +"replication! But, of course, you are going to want to validate that the " +"clustering actually works." +msgstr "" +"La vostra applicazione sta girando in un cluster con replica della sessione " +"HTTP! Ma certamente si vuole validate il fatto che il clustering sta " +"funzionando." #. Tag: title #: ClusteringAndEJBPassivation.xml:172 #, no-c-format -msgid "Validating the distributable services of an application running in a JBoss AS cluster" -msgstr "Validazione dei servizi distribuiti di un'applicazione su un cluster JBoss AS" +msgid "" +"Validating the distributable services of an application running in a JBoss " +"AS cluster" +msgstr "" +"Validazione dei servizi distribuiti di un'applicazione su un cluster JBoss AS" #. Tag: para #: ClusteringAndEJBPassivation.xml:173 #, no-c-format -msgid "It's all well and fine to see the application start successfully on two different JBoss AS servers, but seeing is believing. You likely want to validate that the two instances are exchanging HTTP sessions to allow the slave to take over when the master instance is stopped." -msgstr "E' sempre bello vedere che l'applicazione si avvia con successo su due diversi server JBoss AS, ma vedere è credere! Probabilmente si vuole validare che le due istanze si stiano scambiando le sessioni HTTP per consentire allo slave di entrare in azione quando l'istanza master si ferma." +msgid "" +"It's all well and fine to see the application start successfully on two " +"different JBoss AS servers, but seeing is believing. You likely want to " +"validate that the two instances are exchanging HTTP sessions to allow the " +"slave to take over when the master instance is stopped." +msgstr "" +"E' sempre bello vedere che l'applicazione si avvia con successo su due " +"diversi server JBoss AS, ma vedere è credere! Probabilmente si vuole " +"validare che le due istanze si stiano scambiando le sessioni HTTP per " +"consentire allo slave di entrare in azione quando l'istanza master si ferma." #. Tag: para #: ClusteringAndEJBPassivation.xml:179 #, no-c-format -msgid "Start off by visiting the application running on the master instance in your browser. That will produce the first HTTP session. Now, open up the JBoss AS JMX console on that instance and navigate to the following MBean:" -msgstr "Avviare e visitare sul browser l'applicazione che gira sull'istanza master. Questo produrrà la prima sessione HTTP. Ora si apra la console JMX di JBoss AS su tale istanza e si vada al seguente MBean:" +msgid "" +"Start off by visiting the application running on the master instance in your " +"browser. That will produce the first HTTP session. Now, open up the JBoss AS " +"JMX console on that instance and navigate to the following MBean:" +msgstr "" +"Avviare e visitare sul browser l'applicazione che gira sull'istanza master. " +"Questo produrrà la prima sessione HTTP. Ora si apra la console JMX di JBoss " +"AS su tale istanza e si vada al seguente MBean:" #. Tag: para #: ClusteringAndEJBPassivation.xml:187 @@ -288,32 +526,76 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:197 #, no-c-format -msgid "Invoke the printDetails() method. You will see a tree of active HTTP sessions. Verify that the session your browser is using corresponds to one of the sessions in this tree." -msgstr "Invocare il metodo printDetails(). Si vedrà un albero con le sessioni HTTP attive. Verificare che la sessione del browser in uso corrisponda ad una delle sessioni in questo albero." +msgid "" +"Invoke the printDetails() method. You will see a tree of active HTTP " +"sessions. Verify that the session your browser is using corresponds to one " +"of the sessions in this tree." +msgstr "" +"Invocare il metodo printDetails(). Si vedrà un albero con le sessioni HTTP " +"attive. Verificare che la sessione del browser in uso corrisponda ad una " +"delle sessioni in questo albero." #. Tag: para #: ClusteringAndEJBPassivation.xml:202 #, no-c-format -msgid "Now switch over to the slave instance and invoke the same method in the JMX console. You should see an identical list (at least underneath this application's context path)." -msgstr "Ora si passi all'istanza slave e si invochi lo stesso metodo nella console JMX. Si dovrebbe vedere la stessa lista (almeno sotto il context path dell'applicazione)" +msgid "" +"Now switch over to the slave instance and invoke the same method in the JMX " +"console. You should see an identical list (at least underneath this " +"application's context path)." +msgstr "" +"Ora si passi all'istanza slave e si invochi lo stesso metodo nella console " +"JMX. Si dovrebbe vedere la stessa lista (almeno sotto il context path " +"dell'applicazione)" #. Tag: para #: ClusteringAndEJBPassivation.xml:207 #, no-c-format -msgid "So you can see that at least both servers claim to have identical sessions. Now, time to test that the data is serializing and unserializing properly." -msgstr "Quindi si può vedere che entrambi i server hanno le stesse identiche sessioni. Ora occorre testare che i dati vengano serializzati e deserializzati correttamente." +msgid "" +"So you can see that at least both servers claim to have identical sessions. " +"Now, time to test that the data is serializing and unserializing properly." +msgstr "" +"Quindi si può vedere che entrambi i server hanno le stesse identiche " +"sessioni. Ora occorre testare che i dati vengano serializzati e " +"deserializzati correttamente." #. Tag: para #: ClusteringAndEJBPassivation.xml:212 #, no-c-format -msgid "Sign in using using the URL of the master instance. Then, construct a URL for the second instance by putting the ;jsessionid=XXXX immediately after the servlet path and changing the IP address. You should see that the session has carried over to the other instance. Now kill the master instance and see that you can continue to use the application from the slave instance. Remove the deployments from the server/all/farm directory and start the instance again. Switch the IP in the URL back to that of the master instance and visit the URL. You'll see that the original session is still being used." -msgstr "Fare il login usando l'URL dell'istanza master. Poi scrivere l'URL per la seconda istanza mettendo ;jsessionid=XXXX immediatamente dopo il path del servlet e cambiando l'indirizzo IP. Si dovrebbe vedere che la sessione viene trasportata nell'altra istanza. Ora uccidere il processo dell'istanza master e verificare che si possa continuare ad usare l'applicazione dall'istanza slave. Rimuovere i deploy dalla directory server/all/farm ed avviare di nuovo l'istanza. Cambiare nell'URL l'IP a quello dell'istanza master e visitare l'URL. Si vedrà che viene usata ancora la sessione originale." +msgid "" +"Sign in using using the URL of the master instance. Then, construct a URL " +"for the second instance by putting the ;jsessionid=XXXX immediately after " +"the servlet path and changing the IP address. You should see that the " +"session has carried over to the other instance. Now kill the master instance " +"and see that you can continue to use the application from the slave " +"instance. Remove the deployments from the server/all/farm directory and " +"start the instance again. Switch the IP in the URL back to that of the " +"master instance and visit the URL. You'll see that the original session is " +"still being used." +msgstr "" +"Fare il login usando l'URL dell'istanza master. Poi scrivere l'URL per la " +"seconda istanza mettendo ;jsessionid=XXXX immediatamente dopo il path del " +"servlet e cambiando l'indirizzo IP. Si dovrebbe vedere che la sessione viene " +"trasportata nell'altra istanza. Ora uccidere il processo dell'istanza master " +"e verificare che si possa continuare ad usare l'applicazione dall'istanza " +"slave. Rimuovere i deploy dalla directory server/all/farm ed avviare di " +"nuovo l'istanza. Cambiare nell'URL l'IP a quello dell'istanza master e " +"visitare l'URL. Si vedrà che viene usata ancora la sessione originale." #. Tag: para #: ClusteringAndEJBPassivation.xml:221 #, no-c-format -msgid "One way to watch objects passivate and activate is to create a session- or conversation-scoped Seam component and implement the appropriate life-cycle methods. You can either use methods from the HttpSessionActivationListener interface (Seam automatically registers this interface on all non-EJB components):" -msgstr "Un modo per vedere passivare ed attivare gli oggetti è create un componente Seam con scope conversazione o sessione ed implementare i metodi del ciclo di vita in modo appropriato. Si possono usare i metodi dell'interfaccia HttpSessionActivationListener (Seam automaticamente registra quest'interfaccia per tutti i componenti non-EJB):" +msgid "" +"One way to watch objects passivate and activate is to create a session- or " +"conversation-scoped Seam component and implement the appropriate life-cycle " +"methods. You can either use methods from the HttpSessionActivationListener " +"interface (Seam automatically registers this interface on all non-EJB " +"components):" +msgstr "" +"Un modo per vedere passivare ed attivare gli oggetti è create un componente " +"Seam con scope conversazione o sessione ed implementare i metodi del ciclo " +"di vita in modo appropriato. Si possono usare i metodi dell'interfaccia " +"HttpSessionActivationListener (Seam automaticamente registra " +"quest'interfaccia per tutti i componenti non-EJB):" #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:228 @@ -328,14 +610,28 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:230 #, no-c-format -msgid "Or you can simply mark two no-argument public void methods with <literal>@PrePassivate</literal> and <literal>@PostActivate</literal>, respectively. Note that the passivation step occurs at the end of every request, while the activation step occurs when a node is called upon." -msgstr "O semplicemente si possono marcare due metodi senza argomenti public void rispettivamente con <literal>@PrePassivate</literal> e <literal>@PostActivate</literal>. Si noti che il passo di passivazione avviene alla fine di ogni richiesta, mentre quello di attivazione avviene quando viene chiamato un nodo." +msgid "" +"Or you can simply mark two no-argument public void methods with " +"<literal>@PrePassivate</literal> and <literal>@PostActivate</literal>, " +"respectively. Note that the passivation step occurs at the end of every " +"request, while the activation step occurs when a node is called upon." +msgstr "" +"O semplicemente si possono marcare due metodi senza argomenti public void " +"rispettivamente con <literal>@PrePassivate</literal> e " +"<literal>@PostActivate</literal>. Si noti che il passo di passivazione " +"avviene alla fine di ogni richiesta, mentre quello di attivazione avviene " +"quando viene chiamato un nodo." #. Tag: para #: ClusteringAndEJBPassivation.xml:237 #, no-c-format -msgid "Now that you understand the big picture of running Seam in a cluster, it's time to address Seam's most mysterious, yet remarkable agent, the ManagedEntityInterceptor." -msgstr "Ora che si ha il quadro generale del funzionamento di un cluster con Seam, è tempo di indirizzarsi verso il misterioso ManagedEntityInterceptor." +msgid "" +"Now that you understand the big picture of running Seam in a cluster, it's " +"time to address Seam's most mysterious, yet remarkable agent, the " +"ManagedEntityInterceptor." +msgstr "" +"Ora che si ha il quadro generale del funzionamento di un cluster con Seam, è " +"tempo di indirizzarsi verso il misterioso ManagedEntityInterceptor." #. Tag: title #: ClusteringAndEJBPassivation.xml:244 @@ -346,8 +642,19 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:246 #, no-c-format -msgid "The ManagedEntityInterceptor (MEI) is an optional interceptor in Seam that gets applied to conversation-scoped components when enabled. Enabling it is simple. You just set the distributable property on the org.jboss.seam.init.core component to true. More simply put, you add (or update) the following component declaration in the component descriptor (i.e., components.xml)." -msgstr "Il ManagedEntityInterceptor (MEI) è un interceptor opzionale di Seam che viene applicato, se abilitato, ai componenti con scope conversazione. L'abilitazione è semplice. Occorre impostare a true la proprietà distributable nel componente org.jboss.seam.init.core. Più semplicemente aggiungere (o aggiornare) la seguente dichiarazione di componente in components.xml:" +msgid "" +"The ManagedEntityInterceptor (MEI) is an optional interceptor in Seam that " +"gets applied to conversation-scoped components when enabled. Enabling it is " +"simple. You just set the distributable property on the org.jboss.seam.init." +"core component to true. More simply put, you add (or update) the following " +"component declaration in the component descriptor (i.e., components.xml)." +msgstr "" +"Il ManagedEntityInterceptor (MEI) è un interceptor opzionale di Seam che " +"viene applicato, se abilitato, ai componenti con scope conversazione. " +"L'abilitazione è semplice. Occorre impostare a true la proprietà " +"distributable nel componente org.jboss.seam.init.core. Più semplicemente " +"aggiungere (o aggiornare) la seguente dichiarazione di componente in " +"components.xml:" #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:253 @@ -358,26 +665,62 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:255 #, no-c-format -msgid "Note that this doesn't enable replication of HTTP sessions, but it does prepare Seam to be able to deal with passivation of either EJB components or components in the HTTP session." -msgstr "Si noti che questo non abilita la replica delle sessioni HTTP, ma prepara Seam a poter gestire la passivazione dei componenti EJB o dei componenti nelle sessioni HTTP." +msgid "" +"Note that this doesn't enable replication of HTTP sessions, but it does " +"prepare Seam to be able to deal with passivation of either EJB components or " +"components in the HTTP session." +msgstr "" +"Si noti che questo non abilita la replica delle sessioni HTTP, ma prepara " +"Seam a poter gestire la passivazione dei componenti EJB o dei componenti " +"nelle sessioni HTTP." #. Tag: para #: ClusteringAndEJBPassivation.xml:260 -#, no-c-format -msgid "The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not become detatched prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees)." -msgstr "MEI serve per due scenari distinti (passivazione EJB e passivazione della sessione HTTP), sebbene raggiunge lo stesso obiettivo generale. Assicura che lungo la vita di una conversazione con l'uso di almeno un contesto di persistenza esteso, le istanze dell'entity caricate dal contesto di persistenza rimangano gestite (non divengano detached in modo prematuro da un evento passivation). In breve, assicura l'integrità del contesto di persistenza esteso (e quindi delle sue garanzie)." +#, fuzzy, no-c-format +msgid "" +"The MEI serves two distinct scenarios (EJB passivation and HTTP session " +"passivation), although to accomplish the same overall goal. It ensures that " +"throughout the life of a conversation using at least one extended " +"persistence context, the entity instances loaded by the persistence context" +"(s) remain managed (they do not become detached prematurally by a " +"passivation event). In short, it ensures the integrity of the extended " +"persistence context (and therefore its guarantees)." +msgstr "" +"MEI serve per due scenari distinti (passivazione EJB e passivazione della " +"sessione HTTP), sebbene raggiunge lo stesso obiettivo generale. Assicura che " +"lungo la vita di una conversazione con l'uso di almeno un contesto di " +"persistenza esteso, le istanze dell'entity caricate dal contesto di " +"persistenza rimangano gestite (non divengano detached in modo prematuro da " +"un evento passivation). In breve, assicura l'integrità del contesto di " +"persistenza esteso (e quindi delle sue garanzie)." #. Tag: para #: ClusteringAndEJBPassivation.xml:268 #, no-c-format -msgid "The previous statement implies that there is a challenge that threatens this contract. In fact, there are two. One case is when a stateful session bean (SFSB) that hosts an extended persistence context is passivated (to save memory or to migrate it to another node in the cluster) and the second is when the HTTP session is passivated (to prepare it to be migrated to another node in the cluster)." -msgstr "La precedente affermazione implica che ci sia una minaccia al contratto. Infatti ce ne sono due. Un caso è quando lo stateful session bean (SFSB) che ospita un contesto di persistenza esteso viene passivato (per risparmiare memoria o migrarlo in un altro nodo del cluster) ed il secondo quando la sessione HTTP viene passivata (per prepararla alla migrazione in un altro nodo del cluster)." +msgid "" +"The previous statement implies that there is a challenge that threatens this " +"contract. In fact, there are two. One case is when a stateful session bean " +"(SFSB) that hosts an extended persistence context is passivated (to save " +"memory or to migrate it to another node in the cluster) and the second is " +"when the HTTP session is passivated (to prepare it to be migrated to another " +"node in the cluster)." +msgstr "" +"La precedente affermazione implica che ci sia una minaccia al contratto. " +"Infatti ce ne sono due. Un caso è quando lo stateful session bean (SFSB) che " +"ospita un contesto di persistenza esteso viene passivato (per risparmiare " +"memoria o migrarlo in un altro nodo del cluster) ed il secondo quando la " +"sessione HTTP viene passivata (per prepararla alla migrazione in un altro " +"nodo del cluster)." #. Tag: para #: ClusteringAndEJBPassivation.xml:275 #, no-c-format -msgid "I first want to discuss the general problem of passivation and then look at the two challenges cited individually." -msgstr "Vogliamo discutere per primo il problema generale della passivazione e poi guardare singolarmente le due minacce." +msgid "" +"I first want to discuss the general problem of passivation and then look at " +"the two challenges cited individually." +msgstr "" +"Vogliamo discutere per primo il problema generale della passivazione e poi " +"guardare singolarmente le due minacce." #. Tag: title #: ClusteringAndEJBPassivation.xml:281 @@ -388,32 +731,107 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:283 #, no-c-format -msgid "The persistence context is where the persistence manager (i.e., JPA EntityManager or Hibernate Session) stores entity instances (i.e., objects) it has loaded from the database (via the object-relational mappings). Within a persistence context, there is no more than one object per unique database record. The persistence context is often referred to as the first-level cache because if the application asks for a record by its unique identifier that has already been loaded into the persistence context, a call to the database is avoided. But it's about more than just caching." -msgstr "Il contesto di persistenza è il posto in cui il gestore di persistenza (cioè EntityManager JPA o Hibernate Session) memorizza le istanze degli entity (cioè gli oggetti) che ha caricato dal database (tramite mappature relazionali degli oggetti). Dentro un contesto di persistenza, c'è alpiù un oggetto per record di database. Il contesto di persistenza è spesso considerato il primo livello di cache, poiché se l'applicazione chiede un record attraverso il suo identificatore unico che è già stato caricato nel contesto di persistenza, viene evitata una chiamata al database. Ma questo è più che una cache." +msgid "" +"The persistence context is where the persistence manager (i.e., JPA " +"EntityManager or Hibernate Session) stores entity instances (i.e., objects) " +"it has loaded from the database (via the object-relational mappings). Within " +"a persistence context, there is no more than one object per unique database " +"record. The persistence context is often referred to as the first-level " +"cache because if the application asks for a record by its unique identifier " +"that has already been loaded into the persistence context, a call to the " +"database is avoided. But it's about more than just caching." +msgstr "" +"Il contesto di persistenza è il posto in cui il gestore di persistenza (cioè " +"EntityManager JPA o Hibernate Session) memorizza le istanze degli entity " +"(cioè gli oggetti) che ha caricato dal database (tramite mappature " +"relazionali degli oggetti). Dentro un contesto di persistenza, c'è alpiù un " +"oggetto per record di database. Il contesto di persistenza è spesso " +"considerato il primo livello di cache, poiché se l'applicazione chiede un " +"record attraverso il suo identificatore unico che è già stato caricato nel " +"contesto di persistenza, viene evitata una chiamata al database. Ma questo è " +"più che una cache." #. Tag: para #: ClusteringAndEJBPassivation.xml:292 #, no-c-format -msgid "Objects held in the persistence context can be modified, which the persistence manager tracks. When an object is modified, it's considered \"dirty\". The persistence manager will migrate these changes to the database using a technique known as write-behind (which basically means only when necessary). Thus, the persistence context maintains a set of pending changes to the database." -msgstr "Gli oggetti mantenuti nel contesto di persistenza possono essere modificati, cosa di cui il gestore di persistenza tiene traccia. Quando un oggetto viene modificato, viene considerato \"dirty\". Il gestore di persistenza migrerà questi cambiamenti al database usando una tecnica conosciuta come write-behind (che significa solo quando necessario). Quindi il contesto di persistenza mantiene un set di cambiamenti pendenti sul database." +msgid "" +"Objects held in the persistence context can be modified, which the " +"persistence manager tracks. When an object is modified, it's considered " +"\"dirty\". The persistence manager will migrate these changes to the " +"database using a technique known as write-behind (which basically means only " +"when necessary). Thus, the persistence context maintains a set of pending " +"changes to the database." +msgstr "" +"Gli oggetti mantenuti nel contesto di persistenza possono essere modificati, " +"cosa di cui il gestore di persistenza tiene traccia. Quando un oggetto viene " +"modificato, viene considerato \"dirty\". Il gestore di persistenza migrerà " +"questi cambiamenti al database usando una tecnica conosciuta come write-" +"behind (che significa solo quando necessario). Quindi il contesto di " +"persistenza mantiene un set di cambiamenti pendenti sul database." #. Tag: para #: ClusteringAndEJBPassivation.xml:299 #, no-c-format -msgid "Database-oriented applications do much more than just read from and write to the database. They capture transactional bits of information that need to be tranfered into the database atomically (at once). It's not always possible to capture this information all on one screen. Additionally, the user might need to make a judgement call about whether to approve or reject the pending changes." -msgstr "Le applicazioni orientate ai database fanno molto di più che leggere e scrivere nel database. Esse catturano bit transazionali di informazione che devono essere trasferiti nel database in modo atomico (in una solo volta). Non è sempre possibile catturare queste informazioni in una sola volta. In aggiunta l'utente potrebbe decidere se approvare o disapprovare le modifiche pendenti." +msgid "" +"Database-oriented applications do much more than just read from and write to " +"the database. They capture transactional bits of information that need to be " +"tranfered into the database atomically (at once). It's not always possible " +"to capture this information all on one screen. Additionally, the user might " +"need to make a judgement call about whether to approve or reject the pending " +"changes." +msgstr "" +"Le applicazioni orientate ai database fanno molto di più che leggere e " +"scrivere nel database. Esse catturano bit transazionali di informazione che " +"devono essere trasferiti nel database in modo atomico (in una solo volta). " +"Non è sempre possibile catturare queste informazioni in una sola volta. In " +"aggiunta l'utente potrebbe decidere se approvare o disapprovare le modifiche " +"pendenti." #. Tag: para #: ClusteringAndEJBPassivation.xml:306 #, no-c-format -msgid "What we are getting at here is that the idea of a transaction from the user's perspective needs to be extended. And that is why the extended persistence context fits so perfectly with this requirement. It can hold such changes for as long as the application can keep it open and then use the built-in capabilities of the persistence manager to push these pending changes to the database without requiring the application developer to worry about the low-level details (a simple call to <literal>EntityManager#flush()</literal> does the trick)." -msgstr "Ciò che vogliamo dire è che l'idea di transazione dal punto di vista dell'utente deve essere estesa. E questo è il motivo per cui il contesto di persistenza esteso risponde perfettamente a questo requisito. Può mantenere i cambiamenti tanto a lungo quanto viene mantenuta aperta l'applicazione e poi usare le capacità predefinite del gestore di persistenza per apportare nel database questi cambiamenti senza richiedere allo sviluppatore di preoccuparsi dei dettagli di basso livello (una semplice chiamata a <literal>EntityManager#flush()</literal> fa tutto il lavoro)." +msgid "" +"What we are getting at here is that the idea of a transaction from the " +"user's perspective needs to be extended. And that is why the extended " +"persistence context fits so perfectly with this requirement. It can hold " +"such changes for as long as the application can keep it open and then use " +"the built-in capabilities of the persistence manager to push these pending " +"changes to the database without requiring the application developer to worry " +"about the low-level details (a simple call to <literal>EntityManager#flush()" +"</literal> does the trick)." +msgstr "" +"Ciò che vogliamo dire è che l'idea di transazione dal punto di vista " +"dell'utente deve essere estesa. E questo è il motivo per cui il contesto di " +"persistenza esteso risponde perfettamente a questo requisito. Può mantenere " +"i cambiamenti tanto a lungo quanto viene mantenuta aperta l'applicazione e " +"poi usare le capacità predefinite del gestore di persistenza per apportare " +"nel database questi cambiamenti senza richiedere allo sviluppatore di " +"preoccuparsi dei dettagli di basso livello (una semplice chiamata a " +"<literal>EntityManager#flush()</literal> fa tutto il lavoro)." #. Tag: para #: ClusteringAndEJBPassivation.xml:315 #, no-c-format -msgid "The link between the persistence manager and the entity instances is maintained using object references. The entity instances are serializable, but the persistence manager (and in turn its persistence context) is not. Therefore, the process of serialization works against this design. Serialization can occur either when a SFSB or the HTTP session is passivated. In order to sustain the activity in the application, the persistence manager and the entity instances it manages must weather serialization without losing their relationship. That's the aid that the MEI provides." -msgstr "Il collegamento tra il gestore della persistenza e le istanze degli entity viene mantenuto usando i riferimenti oggetto. Le istanze entity sono serializzabili, ma il gestore della persistenza non lo è (e quindi il suo contesto di persistenza). Quindi il processo di serializzazione funziona contro questo design. La serializzazione avviene anche quando un SFSB o sessione HTTP sono passivati. Per sostenere l'attività nell'applicazione, il gestore della persistenza e le istanze entity che gestisce devono esporre la serializzazione senza perdere la loro relazione. E' questo l'aiuto che viene fornito da MEI." +msgid "" +"The link between the persistence manager and the entity instances is " +"maintained using object references. The entity instances are serializable, " +"but the persistence manager (and in turn its persistence context) is not. " +"Therefore, the process of serialization works against this design. " +"Serialization can occur either when a SFSB or the HTTP session is " +"passivated. In order to sustain the activity in the application, the " +"persistence manager and the entity instances it manages must weather " +"serialization without losing their relationship. That's the aid that the MEI " +"provides." +msgstr "" +"Il collegamento tra il gestore della persistenza e le istanze degli entity " +"viene mantenuto usando i riferimenti oggetto. Le istanze entity sono " +"serializzabili, ma il gestore della persistenza non lo è (e quindi il suo " +"contesto di persistenza). Quindi il processo di serializzazione funziona " +"contro questo design. La serializzazione avviene anche quando un SFSB o " +"sessione HTTP sono passivati. Per sostenere l'attività nell'applicazione, il " +"gestore della persistenza e le istanze entity che gestisce devono esporre la " +"serializzazione senza perdere la loro relazione. E' questo l'aiuto che viene " +"fornito da MEI." #. Tag: title #: ClusteringAndEJBPassivation.xml:327 @@ -423,33 +841,114 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:329 -#, no-c-format -msgid "Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a compliment to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB." -msgstr "Le conversazioni sono state inizialmente progettate avendo in mente gli stateful session bean (SFSB), in primo luogo poiché la specifica EJB3 indica gli SFSB come host del contesto di persistenza esteso. Seam introduce un complemento al contesto di persistenza esteso, conosciuto col nome di contesto di persistenza gestito da Seam, il quale risolve un certo numero di limitazioni presenti nella specifica (le regole complesse di propagazione e la mancanza di flush manuale). Entrambi possono essere usati con i SFSB." +#, fuzzy, no-c-format +msgid "" +"Conversations were initially designed with stateful session beans (SFSBs) in " +"mind, primarily because the EJB 3 specification designates SFSBs as hosts of " +"the extended persistence context. Seam introduces a complement to the " +"extended persistence context, known as a Seam-managed persistence context, " +"which works around a number of limitations in the specification (complex " +"propagation rules and lack of manual flushing). Both can be used with a SFSB." +msgstr "" +"Le conversazioni sono state inizialmente progettate avendo in mente gli " +"stateful session bean (SFSB), in primo luogo poiché la specifica EJB3 indica " +"gli SFSB come host del contesto di persistenza esteso. Seam introduce un " +"complemento al contesto di persistenza esteso, conosciuto col nome di " +"contesto di persistenza gestito da Seam, il quale risolve un certo numero di " +"limitazioni presenti nella specifica (le regole complesse di propagazione e " +"la mancanza di flush manuale). Entrambi possono essere usati con i SFSB." #. Tag: para #: ClusteringAndEJBPassivation.xml:337 #, no-c-format -msgid "A SFSB relies on a client to hold a reference to it in order to keep it active. Seam has provided an ideal place for this reference in the conversation context. Thus, for as long as the conversation context is active, the SFSB is active. If an EntityManager is injected into that SFSB using the annotation @PersistenceContext(EXTENDED), then that EntityManager will be bound to the SFSB and remain open throughout its lifetime, the lifetime of the conversation. If an EntityManager is injected using @In, then that EntityManager is maintained by Seam and stored directly in the conversation context, thus living for the lifetime of the conversation independent of the lifetime of the SFSB." -msgstr "Un SFSB si affida al client per mantenere un riferimento ad esso e per mantenerlo attivo. Seam ha fornito un posto ideal per questo riferimento al contesto di conversazione. Quindi fintantoché il contesto di conversazione rimane attivo, il SFSB è attivo. Se un EntityManager viene iniettato in questo SFSB usando l'annotazione @PersistenceContext(EXTENDED), allora tale EntityManager verrà associato al SFSB e rimarrà aperto lungo tutto il ciclo di vita della conversazione. Se un EntityManager viene iniettato usano @In, allora tale EntityManager verrà mantenuto da Seam e memorizzato direttamente nel contesto conversazione, quindi vivrà per tutto il ciclo di vita della conversazione indipendente dal ciclo di vita del SFSB." +msgid "" +"A SFSB relies on a client to hold a reference to it in order to keep it " +"active. Seam has provided an ideal place for this reference in the " +"conversation context. Thus, for as long as the conversation context is " +"active, the SFSB is active. If an EntityManager is injected into that SFSB " +"using the annotation @PersistenceContext(EXTENDED), then that EntityManager " +"will be bound to the SFSB and remain open throughout its lifetime, the " +"lifetime of the conversation. If an EntityManager is injected using @In, " +"then that EntityManager is maintained by Seam and stored directly in the " +"conversation context, thus living for the lifetime of the conversation " +"independent of the lifetime of the SFSB." +msgstr "" +"Un SFSB si affida al client per mantenere un riferimento ad esso e per " +"mantenerlo attivo. Seam ha fornito un posto ideal per questo riferimento al " +"contesto di conversazione. Quindi fintantoché il contesto di conversazione " +"rimane attivo, il SFSB è attivo. Se un EntityManager viene iniettato in " +"questo SFSB usando l'annotazione @PersistenceContext(EXTENDED), allora tale " +"EntityManager verrà associato al SFSB e rimarrà aperto lungo tutto il ciclo " +"di vita della conversazione. Se un EntityManager viene iniettato usano @In, " +"allora tale EntityManager verrà mantenuto da Seam e memorizzato direttamente " +"nel contesto conversazione, quindi vivrà per tutto il ciclo di vita della " +"conversazione indipendente dal ciclo di vita del SFSB." #. Tag: para #: ClusteringAndEJBPassivation.xml:347 -#, no-c-format -msgid "With all of that said, the Java EE container can passivate a SFSB, which means it will serialize the object to an area of storage external to the JVM. When this happens depends on the settings of the individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the guarnatees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this references at the beginning of the next invocation. Of course, Seam is! already storing the persistence manager in the conversation. Thus, when the SFSB passivates and later activates, it has absolutely no averse affect on the application." -msgstr "Con tutto ciò detto, il container Java EE può passivare un SFSB, il che significa che verrà serializzato l'oggetto in un area di memorizzazione esterna alla JVM. Quando questo avviene dipende dalle impostazione del singolo SFSB. Questo processo può anche essere disabilitato. Comunque il contesto di persistenza non è serializzato (questo è vero solo per SMPC?). Infatti cosa succede dipende fortemente dal container Java EE. La specifica non è molto chiara in proposito. Molti vendor dicono di non fare avvenire questo se servono le garanzie del contesto di persistenza esteso. L'approccio di Seam più conservativo. Seam non si fida del SFSB con il contesto di persistenza o delle istanze entity. Dopo ogni invocazione del SFSB, Seam sposta il riferimento all'istanza entity mantenuta dal SFSB dentro l'attuale conversazione (e quindi nella sessione HTTP). mettendo a null questi campi nel SFSB. Poi ripristina questi riferimenri all'inizio di ogni invocazione. Certament! e Seam sta già memorizzando il gestore della persistenza nella conversazione. Perciò quando il SFSB passiva e poi si riattiva, non c'è alcun effetto negativo sull'applicazione." +#, fuzzy, no-c-format +msgid "" +"With all of that said, the Java EE container can passivate a SFSB, which " +"means it will serialize the object to an area of storage external to the " +"JVM. When this happens depends on the settings of the individual SFSB. This " +"process can even be disabled. However, the persistence context is not " +"serialized (is this only true of SMPC?). In fact, what happens depends " +"highly on the Java EE container. The spec is not very clear about this " +"situation. Many vendors just tell you not to let it happen if you need the " +"guarantees of the extended persistence context. Seam's approach is more " +"conservative. Seam basically doesn't trust the SFSB with the persistence " +"context or the entity instances. After each invocation of the SFSB, Seam " +"moves the reference to entity instance held by the SFSB into the current " +"conversation (and therefore into the HTTP session), nullifying those fields " +"on the SFSB. It then restores this references at the beginning of the next " +"invocation. Of course, Seam is already storing the persistence manager in " +"the conversation. Thus, when the SFSB passivates and later activates, it has " +"absolutely no averse affect on the application." +msgstr "" +"Con tutto ciò detto, il container Java EE può passivare un SFSB, il che " +"significa che verrà serializzato l'oggetto in un area di memorizzazione " +"esterna alla JVM. Quando questo avviene dipende dalle impostazione del " +"singolo SFSB. Questo processo può anche essere disabilitato. Comunque il " +"contesto di persistenza non è serializzato (questo è vero solo per SMPC?). " +"Infatti cosa succede dipende fortemente dal container Java EE. La specifica " +"non è molto chiara in proposito. Molti vendor dicono di non fare avvenire " +"questo se servono le garanzie del contesto di persistenza esteso. " +"L'approccio di Seam più conservativo. Seam non si fida del SFSB con il " +"contesto di persistenza o delle istanze entity. Dopo ogni invocazione del " +"SFSB, Seam sposta il riferimento all'istanza entity mantenuta dal SFSB " +"dentro l'attuale conversazione (e quindi nella sessione HTTP). mettendo a " +"null questi campi nel SFSB. Poi ripristina questi riferimenri all'inizio di " +"ogni invocazione. Certamente Seam sta già memorizzando il gestore della " +"persistenza nella conversazione. Perciò quando il SFSB passiva e poi si " +"riattiva, non c'è alcun effetto negativo sull'applicazione." #. Tag: para #: ClusteringAndEJBPassivation.xml:363 #, no-c-format -msgid "If you are using SFSBs in your application that hold references to extended persistence contexts, and those SFSBs can passivate, then you must use the MEI. This requirement holds even if you are using a single instance (not a cluster). However, if you are using clustered SFSB, then this requirement also applies." -msgstr "Se si stanno usando degl SFSB che mantengono riferimenti a contesti di persistenza estesi, e questi SFSB possono essere passivati, allora occorre usare un MEI. Questo requisisto esiste anche se si adopera una singola istanza (non un cluster). Comunque se si usa un SFSB clustered, questo requisito permane comunque." +msgid "" +"If you are using SFSBs in your application that hold references to extended " +"persistence contexts, and those SFSBs can passivate, then you must use the " +"MEI. This requirement holds even if you are using a single instance (not a " +"cluster). However, if you are using clustered SFSB, then this requirement " +"also applies." +msgstr "" +"Se si stanno usando degl SFSB che mantengono riferimenti a contesti di " +"persistenza estesi, e questi SFSB possono essere passivati, allora occorre " +"usare un MEI. Questo requisisto esiste anche se si adopera una singola " +"istanza (non un cluster). Comunque se si usa un SFSB clustered, questo " +"requisito permane comunque." #. Tag: para #: ClusteringAndEJBPassivation.xml:371 #, no-c-format -msgid "It is possible to disable passivation on a SFSB. See the <ulink url=\"http://www.jboss.org/community/docs/DOC-9656\">Ejb3DisableSfsbPassivation</ulink> page on the JBoss Wiki for details." -msgstr "E' possibile disabilitare la passivazione su un SFSB. Si veda la pagina <ulink url=\"http://www.jboss.org/community/docs/DOC-9656\">Ejb3DisableSfsbPassivation</ulink> su JBoss Wiki." +msgid "" +"It is possible to disable passivation on a SFSB. See the <ulink url=\"http://" +"www.jboss.org/community/docs/DOC-9656\">Ejb3DisableSfsbPassivation</ulink> " +"page on the JBoss Wiki for details." +msgstr "" +"E' possibile disabilitare la passivazione su un SFSB. Si veda la pagina " +"<ulink url=\"http://www.jboss.org/community/docs/DOC-9656" +"\">Ejb3DisableSfsbPassivation</ulink> su JBoss Wiki." #. Tag: title #: ClusteringAndEJBPassivation.xml:379 @@ -460,14 +959,51 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:381 #, no-c-format -msgid "Dealing with passivation of a SFSB works by leveraging the HTTP session. But what happens when the HTTP session passivates? This happens in a clustered environment with session replication enabled. This case is much tricker to deal with and is where a bulk of the MEI infrastructure comes into play. In thise case, the persistence manager is going to be destroyed because it cannot be serialized. Seam handles this deconstruction (hence ensuring that the HTTP session serializes properly). But what happens on the other end. Well, when the MEI sticks an entity instance into the conversation, it embeds the instance in a wrapper that provides information on how to reassociate the instance with a persistence manager post-serialization. So when the application jumps to another node in the cluster (presumably because the target node went down) the MEI infrastruture essentially reconstructs the persistence context. The huge drawback here is that since the persistence context is ! being reconstructed (from the database), pending changes are dropped. However, what Seam does do is ensure that if the entity instance is versioned, that the guarantees of optimistic locking are upheld. (why isn't the dirty state transfered?)" -msgstr "La passivazione di un SFSB funziona facendo leva sulla sessione HTTP. Ma cosa succede quando la sessione HTTP passiva? Questo capita in un ambiente clusteres cone la replica della sessioneattivata. Questo caso è più problematico da gestire ed avviene quando entra in gioco una parte dell'infrastruttura MEI. In questo caso il gestore della persistenza sta per essere distrutto, poiché non può essere serializzato. Seam gestisce questa decostruzione (che assicura che la sessione HTTP serializzi in modo corretto). Ma cosa avviene dall'altro lato? Quando MEI colloca un'istanza entity in un conversazione, incorpora l'istanza in un wrapper che fornisce informazioni su come riassociare l'istanza col gestore di persistenza dopo la serializzazione. Perciò quando l'applicazione passa su un altro nodo del cluster (presumibilmente poiché il nodo target è sceso) l'infrastruttura MEI verrà ricostruita (dal database), i cambiamenti pendenti verranno abbandonati. Comunque quel! lo che Seam fa è assicurare che se l'istanza entity viene versionata, le garanzie di lock ottimistico vengono mantenute. (Perche lo stato dirty non viene trasferito?)" +msgid "" +"Dealing with passivation of a SFSB works by leveraging the HTTP session. But " +"what happens when the HTTP session passivates? This happens in a clustered " +"environment with session replication enabled. This case is much tricker to " +"deal with and is where a bulk of the MEI infrastructure comes into play. In " +"thise case, the persistence manager is going to be destroyed because it " +"cannot be serialized. Seam handles this deconstruction (hence ensuring that " +"the HTTP session serializes properly). But what happens on the other end. " +"Well, when the MEI sticks an entity instance into the conversation, it " +"embeds the instance in a wrapper that provides information on how to " +"reassociate the instance with a persistence manager post-serialization. So " +"when the application jumps to another node in the cluster (presumably " +"because the target node went down) the MEI infrastruture essentially " +"reconstructs the persistence context. The huge drawback here is that since " +"the persistence context is being reconstructed (from the database), pending " +"changes are dropped. However, what Seam does do is ensure that if the entity " +"instance is versioned, that the guarantees of optimistic locking are upheld. " +"(why isn't the dirty state transfered?)" +msgstr "" +"La passivazione di un SFSB funziona facendo leva sulla sessione HTTP. Ma " +"cosa succede quando la sessione HTTP passiva? Questo capita in un ambiente " +"clusteres cone la replica della sessioneattivata. Questo caso è più " +"problematico da gestire ed avviene quando entra in gioco una parte " +"dell'infrastruttura MEI. In questo caso il gestore della persistenza sta per " +"essere distrutto, poiché non può essere serializzato. Seam gestisce questa " +"decostruzione (che assicura che la sessione HTTP serializzi in modo " +"corretto). Ma cosa avviene dall'altro lato? Quando MEI colloca un'istanza " +"entity in un conversazione, incorpora l'istanza in un wrapper che fornisce " +"informazioni su come riassociare l'istanza col gestore di persistenza dopo " +"la serializzazione. Perciò quando l'applicazione passa su un altro nodo del " +"cluster (presumibilmente poiché il nodo target è sceso) l'infrastruttura MEI " +"verrà ricostruita (dal database), i cambiamenti pendenti verranno " +"abbandonati. Comunque quello che Seam fa è assicurare che se l'istanza " +"entity viene versionata, le garanzie di lock ottimistico vengono mantenute. " +"(Perche lo stato dirty non viene trasferito?)" #. Tag: para #: ClusteringAndEJBPassivation.xml:397 #, no-c-format -msgid "If you are deploying your application in a cluster and using HTTP session replication, you must use the MEI." -msgstr "Se si esegue il deploy dell'applicazione in un cluster e si usa la replica della sessione HTTP, occorre usare MEI." +msgid "" +"If you are deploying your application in a cluster and using HTTP session " +"replication, you must use the MEI." +msgstr "" +"Se si esegue il deploy dell'applicazione in un cluster e si usa la replica " +"della sessione HTTP, occorre usare MEI." #. Tag: title #: ClusteringAndEJBPassivation.xml:404 @@ -478,6 +1014,16 @@ #. Tag: para #: ClusteringAndEJBPassivation.xml:406 #, no-c-format -msgid "The important point of this section is that the MEI is there for a reason. It's there to ensure that the extended persistence context can retain intact in the face of passivation (of either a SFSB or the HTTP session). This matters because the natural design of Seam applications (and conversational state in general) revolve around the state of this resource." -msgstr "Il punto importante di questa sezione è che il MEI esiste per una ragione. Per assicurare che il contesto di persistenza esteso possa rimanenre integro anche con la passivazione (sia di un SFSB sia di una sessione HTTP). Questo è importante poiché il progetto originale delle applicazione Seam (ed in generale dello stato conversazione) ruota attorno allo stato di questa risorsa." - +msgid "" +"The important point of this section is that the MEI is there for a reason. " +"It's there to ensure that the extended persistence context can retain intact " +"in the face of passivation (of either a SFSB or the HTTP session). This " +"matters because the natural design of Seam applications (and conversational " +"state in general) revolve around the state of this resource." +msgstr "" +"Il punto importante di questa sezione è che il MEI esiste per una ragione. " +"Per assicurare che il contesto di persistenza esteso possa rimanenre integro " +"anche con la passivazione (sia di un SFSB sia di una sessione HTTP). Questo " +"è importante poiché il progetto originale delle applicazione Seam (ed in " +"generale dello stato conversazione) ruota attorno allo stato di questa " +"risorsa." Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/ja-JP/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/kn-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/ko-KR/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/ml-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/mr-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/or-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pa-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Annotations.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Annotations.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Annotations.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Author_Group.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Author_Group.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Author_Group.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Book_Info.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Book_Info.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Book_Info.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Cache.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Cache.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Cache.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/ClusteringAndEJBPassivation.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" @@ -95,7 +95,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -121,9 +121,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -159,7 +159,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -518,7 +518,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -628,7 +628,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -661,7 +661,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Components.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Components.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Components.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Concepts.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Concepts.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Concepts.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Configuration.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Configuration.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Configuration.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Controls.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Controls.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Controls.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Conversations.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Conversations.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Conversations.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Dependencies.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Dependencies.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Dependencies.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Drools.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Drools.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Drools.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Elenhancements.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Elenhancements.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Elenhancements.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Events.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Events.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Events.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Excel.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Excel.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Excel.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Feedback.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Feedback.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Feedback.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Framework.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Framework.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Framework.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Getting_Started_With_JBoss_Tools.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gettingstarted.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gettingstarted.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gettingstarted.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Glassfish.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Glassfish.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Glassfish.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Groovy.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Groovy.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Groovy.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Guice.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Guice.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Guice.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gwt.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gwt.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Gwt.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Hsearch.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Hsearch.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Hsearch.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/I18n.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/I18n.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/I18n.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Itext.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Itext.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Itext.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jbpm.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jbpm.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jbpm.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jms.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jms.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Jms.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Mail.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Mail.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Mail.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Performance.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Performance.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Performance.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Persistence.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Persistence.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Persistence.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Preface.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Preface.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Preface.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Remoting.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Remoting.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Remoting.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Revision_History.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Revision_History.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Revision_History.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Rss.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Rss.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Rss.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Security.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Security.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Security.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Spring.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Spring.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Spring.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Testing.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Testing.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Testing.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Text.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Text.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Text.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tools.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tools.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tools.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tutorial.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tutorial.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Tutorial.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Validation.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Validation.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Validation.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Weblogic.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Weblogic.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Weblogic.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Webservices.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Webservices.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Webservices.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Websphere.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Websphere.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Websphere.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Wicket.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Wicket.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Wicket.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Xml.pot =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Xml.pot 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pot/Xml.pot 2009-06-01 18:46:43 UTC (rev 11065) @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <kde-i18n-doc(a)kde.org>\n" Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/pt-BR/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/ru-RU/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/si-LK/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/sl-SL/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/ta-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/te-IN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-CN/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current " Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/zh-TW/ClusteringAndEJBPassivation.po 2009-06-01 18:46:43 UTC (rev 11065) @@ -5,7 +5,7 @@ msgstr "" "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"POT-Creation-Date: 2009-06-01 18:34+0000\n" "PO-Revision-Date: 2009-05-29 06:39+0000\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -94,7 +94,7 @@ "But wait, there's more! Seam also offers an incredibly unique feature for " "clustered applications. In addition to monitoring JavaBean components, Seam " "ensures that managed entity instances (i.e. JPA and Hibernate entities) " -"don't become detatched during replication. Seam keeps a record of the " +"don't become detached during replication. Seam keeps a record of the " "entities that are loaded and automatically loads them on the secondary node. " "You must, however, be using a Seam-managed persistence context to get this " "feature. More in depth information about this feature is provided in the " @@ -120,9 +120,9 @@ #, no-c-format msgid "" "Any session- or conversation-scoped mutable JavaBean component that will be " -"used in a clustered environment must implement the <literal>Mutable</" -"literal> interface from the Seam API. As part of the contract, the component " -"must maintain a dirty flag that is reported and reset by the " +"used in a clustered environment must implement the <literal>org.jboss.seam." +"core.Mutable</literal> interface from the Seam API. As part of the contract, " +"the component must maintain a dirty flag that is reported and reset by the " "<literal>clearDirty()</literal> method. Seam calls this method to determine " "if it is necessary to replicate the component. This avoids having to use the " "more cumbersome Servlet API to add and remove the session attribute on every " @@ -158,7 +158,7 @@ #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "" -"Please note that clustering does not work with hot deployable compoennts. " +"Please note that clustering does not work with hot deployable components. " "But then again, you shouldn't be using hot deployable components in a non-" "development environment anyway." msgstr "" @@ -517,7 +517,7 @@ "passivation), although to accomplish the same overall goal. It ensures that " "throughout the life of a conversation using at least one extended " "persistence context, the entity instances loaded by the persistence context" -"(s) remain managed (they do not become detatched prematurally by a " +"(s) remain managed (they do not become detached prematurally by a " "passivation event). In short, it ensures the integrity of the extended " "persistence context (and therefore its guarantees)." msgstr "" @@ -627,7 +627,7 @@ msgid "" "Conversations were initially designed with stateful session beans (SFSBs) in " "mind, primarily because the EJB 3 specification designates SFSBs as hosts of " -"the extended persistence context. Seam introduces a compliment to the " +"the extended persistence context. Seam introduces a complement to the " "extended persistence context, known as a Seam-managed persistence context, " "which works around a number of limitations in the specification (complex " "propagation rules and lack of manual flushing). Both can be used with a SFSB." @@ -660,7 +660,7 @@ "serialized (is this only true of SMPC?). In fact, what happens depends " "highly on the Java EE container. The spec is not very clear about this " "situation. Many vendors just tell you not to let it happen if you need the " -"guarnatees of the extended persistence context. Seam's approach is more " +"guarantees of the extended persistence context. Seam's approach is more " "conservative. Seam basically doesn't trust the SFSB with the persistence " "context or the entity instances. After each invocation of the SFSB, Seam " "moves the reference to entity instance held by the SFSB into the current "

15 years, 7 months

1
0
0 / 0

Seam SVN: r11064 - in tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide: it-IT and 1 other directory.

by seam-commits＠lists.jboss.org

Author: norman.richards(a)jboss.com Date: 2009-06-01 13:17:12 -0400 (Mon, 01 Jun 2009) New Revision: 11064 Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Jbpm.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Weblogic.po tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Websphere.po Log: merge docs to 11063 Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml 2009-06-01 11:24:41 UTC (rev 11063) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml 2009-06-01 17:17:12 UTC (rev 11064) @@ -46,7 +46,7 @@ <para> But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and - Hibernate entities) don't become detatched during replication. Seam keeps a record of the entities that are + Hibernate entities) don't become detached during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter. @@ -61,7 +61,7 @@ <title>Programming for clustering</title> <para> Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered - environment must implement the <literal>Mutable</literal> interface from the Seam API. As part of the + environment must implement the <literal>org.jboss.seam.core.Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the @@ -82,7 +82,7 @@ </para> <note> <para> - Please note that clustering does not work with hot deployable compoennts. But then again, you shouldn't + Please note that clustering does not work with hot deployable components. But then again, you shouldn't be using hot deployable components in a non-development environment anyway. </para> </note> @@ -265,7 +265,7 @@ The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not - become detatched prematurally by a passivation event). In short, it ensures the integrity of the extended + become detached prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees). </para> @@ -333,7 +333,7 @@ <para> Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a - compliment to the extended persistence context, known as a Seam-managed persistence context, which works + complement to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB. </para> @@ -354,7 +354,7 @@ individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the - guarnatees of the extended persistence context. Seam's approach is more conservative. Seam basically + guarantees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-01 11:24:41 UTC (rev 11063) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/ClusteringAndEJBPassivation.po 2009-06-01 17:17:12 UTC (rev 11064) @@ -6,7 +6,7 @@ "Project-Id-Version: Seam_-_Contextual_Components VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-05-29 06:39+0000\n" -"PO-Revision-Date: 2009-05-29 15:50+0100\n" +"PO-Revision-Date: 2009-05-30 15:23+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -59,13 +59,13 @@ #: ClusteringAndEJBPassivation.xml:46 #, no-c-format msgid "But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and Hibernate entities) don't become detatched during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter." -msgstr "" +msgstr "Ma attenzione, c'è di più! Seam offre anche un'incredibile ed unica caratteristica per le applicazioni cluster. In aggiunta al monitoraggio dei componenti JavaBean, Seam assicura che le istanze entity gestite (cioè entity JPA e Hibernate) non divengano detached durante la replica. Seam mantiene un record di entity che sono caricati e li carica automaticamente nel nodo secondario. Occorre comunque usare un contesto di persistenza gestito da Seam per avere questa funzionalità. Maggiori e più dettagliate informazioni su questa funzionalità vengono fornite nella seconda parte del capitolo." #. Tag: para #: ClusteringAndEJBPassivation.xml:55 #, no-c-format msgid "Now that you understand what features Seam offers to support a clustered environment, let's look at how you program for clustering." -msgstr "" +msgstr "Ora che si è capito quali funzionalità offre Seam per supportare l'ambiente clustered, guardiamo come si programma un cluster." #. Tag: title #: ClusteringAndEJBPassivation.xml:61 @@ -77,25 +77,25 @@ #: ClusteringAndEJBPassivation.xml:62 #, no-c-format msgid "Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered environment must implement the <literal>Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the session attribute on every change of the object." -msgstr "" +msgstr "Un componente JavaBean mutabile con scope sessione o conversazione che verrà usato in un ambiente clustered deve implementare l'interfaccia <literal>Mutable</literal> dell'API Seam. Come parte del contratto, il contratto deve mantenere un dirty flag che viene segnato e resettato dal metodo <literal>clearDirty()</literal>. Seam chiama questo metodo per determinare se è necessario replicare il componente. Questo evita di dover usare la più problematica API dei Servlet per aggiungere e rimuovere l'attributo sessione ad ogni cambiamento dell'oggetto." #. Tag: para #: ClusteringAndEJBPassivation.xml:70 #, no-c-format msgid "You also must ensure that all session- and conversation-scoped JavaBean components are Serializable. Additional, all fields of a stateful component (EJB or JavaBean) must Serializable unless the field is marked transient or set to null in a <literal>@PrePassivate</literal> method. You can restore the value of a transient or nullified field in a <literal>@PostActivate</literal> method." -msgstr "" +msgstr "Bisogna assicurarsi che tutti i componenti JavaBean con scope sessione e conversazione siano Serializable. Inoltre tutti i campi di un componente stateful (EJB o JavaBean) devono essere Serializable amenoché siano marcati come transient o impostati a null in un metodo <literal>@PrePassivate</literal>. Si può ripristinare il valore di un campo transient o null in un metodo <literal>@PostActivate</literal>." #. Tag: para #: ClusteringAndEJBPassivation.xml:76 #, no-c-format msgid "One area where people often get bitten is by using <literal>List.subList</literal> to create a list. The resulting list is not Serializable. So watch out for situations like that. If hit a <literal>java.io.NotSerializableException</literal> and cannot locate the culprit at first glance, you can put a breakpoint on this exception, run the application server in debug mode and attach a debugger (such as Eclipse) to see what deserialization is choking on." -msgstr "" +msgstr "Un'area in cui spesso le persone hanno problemi è con l'uso di <literal>List.subList</literal> per creare una lista. La lista risultante non è Serializable. Quindi attenzione a queste situazioni. Se ci si imbatte in una <literal>java.io.NotSerializableException</literal> e non si riescead individuare subito il colpevole, si può mettere un breakpoint su quest'eccezione, avviare l'application server in modalità debug ed attaccare il debugger (come in Eclipse) per vedere quale deserializzazione causa il problema." #. Tag: para #: ClusteringAndEJBPassivation.xml:84 #, no-c-format msgid "Please note that clustering does not work with hot deployable compoennts. But then again, you shouldn't be using hot deployable components in a non-development environment anyway." -msgstr "" +msgstr "Si noti che il clustering non funziona con componenti hot deployable. Ma comunque non si dovrebbero usare i componenti hot deployable in un ambiente non di sviluppo." #. Tag: title #: ClusteringAndEJBPassivation.xml:92 @@ -107,25 +107,25 @@ #: ClusteringAndEJBPassivation.xml:94 #, no-c-format msgid "The procedure outlined in this tutorial has been validated with an seam-gen application and the Seam booking example." -msgstr "" +msgstr "Questa procedura descritta nel tutorial è stata validata con un'applicazione seam-gen e nell'esempio Prenotazione." #. Tag: para #: ClusteringAndEJBPassivation.xml:99 #, no-c-format msgid "In the tutorial, I assume that the IP addresses of the master and slave servers are 192.168.1.2 and 192.168.1.3, respectively. I am intentionally not using the mod_jk load balancer so that it's easier to validate that both nodes are responding to requests and can share sessions." -msgstr "" +msgstr "In questo tutorial si assume che gli indirizzi IP dei server master e slave siano rispettivamente 192.168.1.2 e 192.168.1.3. Intenzionalmente non viene usato il bilanciatore di carico mod_jk, quindi è più facile validate che entrambi i nodi stiano rispondendo alle richieste e possano condividere le sessioni." #. Tag: para #: ClusteringAndEJBPassivation.xml:105 #, no-c-format msgid "I'm using the farm deployment method in these instructions, though you could also deploy the application normally and allow the two servers to negotiate a master/slave relationship based on startup order." -msgstr "" +msgstr "In queste istruzioni si sta usando il metodo di sviluppo farm, sebbene si possa fare normalmente il deploy dell'applicazione e consentire ai due server di negoziare una relazione master/slave basata sull'ordine di avvio." #. Tag: para #: ClusteringAndEJBPassivation.xml:111 #, no-c-format msgid "JBoss AS clustering relies on UDP multicasting provided by jGroups. The SELinux configuration that ships with RHEL/Fedora blocks these packets by default. You can allow them to pass by modifying the iptables rules (as root). The following commands apply to an IP address that matches 192.168.1.x." -msgstr "" +msgstr "JBoss AS clustering si basa sul multicasting UDP fornito da jGroups. La configurazione SELinux che è inclusa in RHEL/Fedora di default blocca questi pacchetti. Si può consentire di lasciarli passare modificando le regole iptables (come root). I seguenti comandi si applicano ad un indirizzo IP che corrisponde a 192.168.1.x." #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:116 @@ -175,7 +175,7 @@ #: ClusteringAndEJBPassivation.xml:136 #, no-c-format msgid "Ensure you have two IP addresses available (two computers, two network cards, or two IP addressses bound to the same interface). I'll assume the two IP address are 192.168.1.2 and 192.168.1.3" -msgstr "" +msgstr "Assicurarsi di avere disponibili due indirizzi IP (due computer, due schede di rete oppure due indirizzi IP sulla stessa interfaccia). Si assume che i due indirizzi IP siano 192.168.1.2 e 192.168.1.3" #. Tag: para #: ClusteringAndEJBPassivation.xml:141 @@ -193,7 +193,7 @@ #: ClusteringAndEJBPassivation.xml:143 #, no-c-format msgid "The log should report that there are 1 cluster members and 0 other members." -msgstr "Il log dovrebbe riportare che c'è 1 membri cluster e 0 altri membri." +msgstr "Il log dovrebbe riportare che c'è 1 membro cluster e 0 altri membri." #. Tag: para #: ClusteringAndEJBPassivation.xml:146 @@ -217,7 +217,7 @@ #: ClusteringAndEJBPassivation.xml:151 #, no-c-format msgid "The log should report that there are 2 cluster members and 1 other members. It should also show the state being retrieved from the master." -msgstr "Il log dovrebbe riportare che ci sono 2 membri cluster e 1 altri membri. Dovrebbe anche mostrare che lo stato viene recuperato dal master." +msgstr "Il log dovrebbe riportare che ci sono 2 membri cluster e 1 altro membro. Dovrebbe anche mostrare che lo stato viene recuperato dal master." #. Tag: para #: ClusteringAndEJBPassivation.xml:155 @@ -259,13 +259,13 @@ #: ClusteringAndEJBPassivation.xml:173 #, no-c-format msgid "It's all well and fine to see the application start successfully on two different JBoss AS servers, but seeing is believing. You likely want to validate that the two instances are exchanging HTTP sessions to allow the slave to take over when the master instance is stopped." -msgstr "" +msgstr "E' sempre bello vedere che l'applicazione si avvia con successo su due diversi server JBoss AS, ma vedere è credere! Probabilmente si vuole validare che le due istanze si stiano scambiando le sessioni HTTP per consentire allo slave di entrare in azione quando l'istanza master si ferma." #. Tag: para #: ClusteringAndEJBPassivation.xml:179 #, no-c-format msgid "Start off by visiting the application running on the master instance in your browser. That will produce the first HTTP session. Now, open up the JBoss AS JMX console on that instance and navigate to the following MBean:" -msgstr "" +msgstr "Avviare e visitare sul browser l'applicazione che gira sull'istanza master. Questo produrrà la prima sessione HTTP. Ora si apra la console JMX di JBoss AS su tale istanza e si vada al seguente MBean:" #. Tag: para #: ClusteringAndEJBPassivation.xml:187 @@ -289,31 +289,31 @@ #: ClusteringAndEJBPassivation.xml:197 #, no-c-format msgid "Invoke the printDetails() method. You will see a tree of active HTTP sessions. Verify that the session your browser is using corresponds to one of the sessions in this tree." -msgstr "" +msgstr "Invocare il metodo printDetails(). Si vedrà un albero con le sessioni HTTP attive. Verificare che la sessione del browser in uso corrisponda ad una delle sessioni in questo albero." #. Tag: para #: ClusteringAndEJBPassivation.xml:202 #, no-c-format msgid "Now switch over to the slave instance and invoke the same method in the JMX console. You should see an identical list (at least underneath this application's context path)." -msgstr "" +msgstr "Ora si passi all'istanza slave e si invochi lo stesso metodo nella console JMX. Si dovrebbe vedere la stessa lista (almeno sotto il context path dell'applicazione)" #. Tag: para #: ClusteringAndEJBPassivation.xml:207 #, no-c-format msgid "So you can see that at least both servers claim to have identical sessions. Now, time to test that the data is serializing and unserializing properly." -msgstr "" +msgstr "Quindi si può vedere che entrambi i server hanno le stesse identiche sessioni. Ora occorre testare che i dati vengano serializzati e deserializzati correttamente." #. Tag: para #: ClusteringAndEJBPassivation.xml:212 #, no-c-format msgid "Sign in using using the URL of the master instance. Then, construct a URL for the second instance by putting the ;jsessionid=XXXX immediately after the servlet path and changing the IP address. You should see that the session has carried over to the other instance. Now kill the master instance and see that you can continue to use the application from the slave instance. Remove the deployments from the server/all/farm directory and start the instance again. Switch the IP in the URL back to that of the master instance and visit the URL. You'll see that the original session is still being used." -msgstr "" +msgstr "Fare il login usando l'URL dell'istanza master. Poi scrivere l'URL per la seconda istanza mettendo ;jsessionid=XXXX immediatamente dopo il path del servlet e cambiando l'indirizzo IP. Si dovrebbe vedere che la sessione viene trasportata nell'altra istanza. Ora uccidere il processo dell'istanza master e verificare che si possa continuare ad usare l'applicazione dall'istanza slave. Rimuovere i deploy dalla directory server/all/farm ed avviare di nuovo l'istanza. Cambiare nell'URL l'IP a quello dell'istanza master e visitare l'URL. Si vedrà che viene usata ancora la sessione originale." #. Tag: para #: ClusteringAndEJBPassivation.xml:221 #, no-c-format msgid "One way to watch objects passivate and activate is to create a session- or conversation-scoped Seam component and implement the appropriate life-cycle methods. You can either use methods from the HttpSessionActivationListener interface (Seam automatically registers this interface on all non-EJB components):" -msgstr "" +msgstr "Un modo per vedere passivare ed attivare gli oggetti è create un componente Seam con scope conversazione o sessione ed implementare i metodi del ciclo di vita in modo appropriato. Si possono usare i metodi dell'interfaccia HttpSessionActivationListener (Seam automaticamente registra quest'interfaccia per tutti i componenti non-EJB):" #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:228 @@ -329,13 +329,13 @@ #: ClusteringAndEJBPassivation.xml:230 #, no-c-format msgid "Or you can simply mark two no-argument public void methods with <literal>@PrePassivate</literal> and <literal>@PostActivate</literal>, respectively. Note that the passivation step occurs at the end of every request, while the activation step occurs when a node is called upon." -msgstr "" +msgstr "O semplicemente si possono marcare due metodi senza argomenti public void rispettivamente con <literal>@PrePassivate</literal> e <literal>@PostActivate</literal>. Si noti che il passo di passivazione avviene alla fine di ogni richiesta, mentre quello di attivazione avviene quando viene chiamato un nodo." #. Tag: para #: ClusteringAndEJBPassivation.xml:237 #, no-c-format msgid "Now that you understand the big picture of running Seam in a cluster, it's time to address Seam's most mysterious, yet remarkable agent, the ManagedEntityInterceptor." -msgstr "" +msgstr "Ora che si ha il quadro generale del funzionamento di un cluster con Seam, è tempo di indirizzarsi verso il misterioso ManagedEntityInterceptor." #. Tag: title #: ClusteringAndEJBPassivation.xml:244 @@ -347,7 +347,7 @@ #: ClusteringAndEJBPassivation.xml:246 #, no-c-format msgid "The ManagedEntityInterceptor (MEI) is an optional interceptor in Seam that gets applied to conversation-scoped components when enabled. Enabling it is simple. You just set the distributable property on the org.jboss.seam.init.core component to true. More simply put, you add (or update) the following component declaration in the component descriptor (i.e., components.xml)." -msgstr "" +msgstr "Il ManagedEntityInterceptor (MEI) è un interceptor opzionale di Seam che viene applicato, se abilitato, ai componenti con scope conversazione. L'abilitazione è semplice. Occorre impostare a true la proprietà distributable nel componente org.jboss.seam.init.core. Più semplicemente aggiungere (o aggiornare) la seguente dichiarazione di componente in components.xml:" #. Tag: programlisting #: ClusteringAndEJBPassivation.xml:253 @@ -359,25 +359,25 @@ #: ClusteringAndEJBPassivation.xml:255 #, no-c-format msgid "Note that this doesn't enable replication of HTTP sessions, but it does prepare Seam to be able to deal with passivation of either EJB components or components in the HTTP session." -msgstr "" +msgstr "Si noti che questo non abilita la replica delle sessioni HTTP, ma prepara Seam a poter gestire la passivazione dei componenti EJB o dei componenti nelle sessioni HTTP." #. Tag: para #: ClusteringAndEJBPassivation.xml:260 #, no-c-format msgid "The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not become detatched prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees)." -msgstr "" +msgstr "MEI serve per due scenari distinti (passivazione EJB e passivazione della sessione HTTP), sebbene raggiunge lo stesso obiettivo generale. Assicura che lungo la vita di una conversazione con l'uso di almeno un contesto di persistenza esteso, le istanze dell'entity caricate dal contesto di persistenza rimangano gestite (non divengano detached in modo prematuro da un evento passivation). In breve, assicura l'integrità del contesto di persistenza esteso (e quindi delle sue garanzie)." #. Tag: para #: ClusteringAndEJBPassivation.xml:268 #, no-c-format msgid "The previous statement implies that there is a challenge that threatens this contract. In fact, there are two. One case is when a stateful session bean (SFSB) that hosts an extended persistence context is passivated (to save memory or to migrate it to another node in the cluster) and the second is when the HTTP session is passivated (to prepare it to be migrated to another node in the cluster)." -msgstr "" +msgstr "La precedente affermazione implica che ci sia una minaccia al contratto. Infatti ce ne sono due. Un caso è quando lo stateful session bean (SFSB) che ospita un contesto di persistenza esteso viene passivato (per risparmiare memoria o migrarlo in un altro nodo del cluster) ed il secondo quando la sessione HTTP viene passivata (per prepararla alla migrazione in un altro nodo del cluster)." #. Tag: para #: ClusteringAndEJBPassivation.xml:275 #, no-c-format msgid "I first want to discuss the general problem of passivation and then look at the two challenges cited individually." -msgstr "" +msgstr "Vogliamo discutere per primo il problema generale della passivazione e poi guardare singolarmente le due minacce." #. Tag: title #: ClusteringAndEJBPassivation.xml:281 @@ -389,25 +389,25 @@ #: ClusteringAndEJBPassivation.xml:283 #, no-c-format msgid "The persistence context is where the persistence manager (i.e., JPA EntityManager or Hibernate Session) stores entity instances (i.e., objects) it has loaded from the database (via the object-relational mappings). Within a persistence context, there is no more than one object per unique database record. The persistence context is often referred to as the first-level cache because if the application asks for a record by its unique identifier that has already been loaded into the persistence context, a call to the database is avoided. But it's about more than just caching." -msgstr "" +msgstr "Il contesto di persistenza è il posto in cui il gestore di persistenza (cioè EntityManager JPA o Hibernate Session) memorizza le istanze degli entity (cioè gli oggetti) che ha caricato dal database (tramite mappature relazionali degli oggetti). Dentro un contesto di persistenza, c'è alpiù un oggetto per record di database. Il contesto di persistenza è spesso considerato il primo livello di cache, poiché se l'applicazione chiede un record attraverso il suo identificatore unico che è già stato caricato nel contesto di persistenza, viene evitata una chiamata al database. Ma questo è più che una cache." #. Tag: para #: ClusteringAndEJBPassivation.xml:292 #, no-c-format msgid "Objects held in the persistence context can be modified, which the persistence manager tracks. When an object is modified, it's considered \"dirty\". The persistence manager will migrate these changes to the database using a technique known as write-behind (which basically means only when necessary). Thus, the persistence context maintains a set of pending changes to the database." -msgstr "" +msgstr "Gli oggetti mantenuti nel contesto di persistenza possono essere modificati, cosa di cui il gestore di persistenza tiene traccia. Quando un oggetto viene modificato, viene considerato \"dirty\". Il gestore di persistenza migrerà questi cambiamenti al database usando una tecnica conosciuta come write-behind (che significa solo quando necessario). Quindi il contesto di persistenza mantiene un set di cambiamenti pendenti sul database." #. Tag: para #: ClusteringAndEJBPassivation.xml:299 #, no-c-format msgid "Database-oriented applications do much more than just read from and write to the database. They capture transactional bits of information that need to be tranfered into the database atomically (at once). It's not always possible to capture this information all on one screen. Additionally, the user might need to make a judgement call about whether to approve or reject the pending changes." -msgstr "" +msgstr "Le applicazioni orientate ai database fanno molto di più che leggere e scrivere nel database. Esse catturano bit transazionali di informazione che devono essere trasferiti nel database in modo atomico (in una solo volta). Non è sempre possibile catturare queste informazioni in una sola volta. In aggiunta l'utente potrebbe decidere se approvare o disapprovare le modifiche pendenti." #. Tag: para #: ClusteringAndEJBPassivation.xml:306 #, no-c-format msgid "What we are getting at here is that the idea of a transaction from the user's perspective needs to be extended. And that is why the extended persistence context fits so perfectly with this requirement. It can hold such changes for as long as the application can keep it open and then use the built-in capabilities of the persistence manager to push these pending changes to the database without requiring the application developer to worry about the low-level details (a simple call to <literal>EntityManager#flush()</literal> does the trick)." -msgstr "" +msgstr "Ciò che vogliamo dire è che l'idea di transazione dal punto di vista dell'utente deve essere estesa. E questo è il motivo per cui il contesto di persistenza esteso risponde perfettamente a questo requisito. Può mantenere i cambiamenti tanto a lungo quanto viene mantenuta aperta l'applicazione e poi usare le capacità predefinite del gestore di persistenza per apportare nel database questi cambiamenti senza richiedere allo sviluppatore di preoccuparsi dei dettagli di basso livello (una semplice chiamata a <literal>EntityManager#flush()</literal> fa tutto il lavoro)." #. Tag: para #: ClusteringAndEJBPassivation.xml:315 @@ -425,25 +425,25 @@ #: ClusteringAndEJBPassivation.xml:329 #, no-c-format msgid "Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a compliment to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB." -msgstr "" +msgstr "Le conversazioni sono state inizialmente progettate avendo in mente gli stateful session bean (SFSB), in primo luogo poiché la specifica EJB3 indica gli SFSB come host del contesto di persistenza esteso. Seam introduce un complemento al contesto di persistenza esteso, conosciuto col nome di contesto di persistenza gestito da Seam, il quale risolve un certo numero di limitazioni presenti nella specifica (le regole complesse di propagazione e la mancanza di flush manuale). Entrambi possono essere usati con i SFSB." #. Tag: para #: ClusteringAndEJBPassivation.xml:337 #, no-c-format msgid "A SFSB relies on a client to hold a reference to it in order to keep it active. Seam has provided an ideal place for this reference in the conversation context. Thus, for as long as the conversation context is active, the SFSB is active. If an EntityManager is injected into that SFSB using the annotation @PersistenceContext(EXTENDED), then that EntityManager will be bound to the SFSB and remain open throughout its lifetime, the lifetime of the conversation. If an EntityManager is injected using @In, then that EntityManager is maintained by Seam and stored directly in the conversation context, thus living for the lifetime of the conversation independent of the lifetime of the SFSB." -msgstr "" +msgstr "Un SFSB si affida al client per mantenere un riferimento ad esso e per mantenerlo attivo. Seam ha fornito un posto ideal per questo riferimento al contesto di conversazione. Quindi fintantoché il contesto di conversazione rimane attivo, il SFSB è attivo. Se un EntityManager viene iniettato in questo SFSB usando l'annotazione @PersistenceContext(EXTENDED), allora tale EntityManager verrà associato al SFSB e rimarrà aperto lungo tutto il ciclo di vita della conversazione. Se un EntityManager viene iniettato usano @In, allora tale EntityManager verrà mantenuto da Seam e memorizzato direttamente nel contesto conversazione, quindi vivrà per tutto il ciclo di vita della conversazione indipendente dal ciclo di vita del SFSB." #. Tag: para #: ClusteringAndEJBPassivation.xml:347 #, no-c-format msgid "With all of that said, the Java EE container can passivate a SFSB, which means it will serialize the object to an area of storage external to the JVM. When this happens depends on the settings of the individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the guarnatees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this references at the beginning of the next invocation. Of course, Seam is! already storing the persistence manager in the conversation. Thus, when the SFSB passivates and later activates, it has absolutely no averse affect on the application." -msgstr "" +msgstr "Con tutto ciò detto, il container Java EE può passivare un SFSB, il che significa che verrà serializzato l'oggetto in un area di memorizzazione esterna alla JVM. Quando questo avviene dipende dalle impostazione del singolo SFSB. Questo processo può anche essere disabilitato. Comunque il contesto di persistenza non è serializzato (questo è vero solo per SMPC?). Infatti cosa succede dipende fortemente dal container Java EE. La specifica non è molto chiara in proposito. Molti vendor dicono di non fare avvenire questo se servono le garanzie del contesto di persistenza esteso. L'approccio di Seam più conservativo. Seam non si fida del SFSB con il contesto di persistenza o delle istanze entity. Dopo ogni invocazione del SFSB, Seam sposta il riferimento all'istanza entity mantenuta dal SFSB dentro l'attuale conversazione (e quindi nella sessione HTTP). mettendo a null questi campi nel SFSB. Poi ripristina questi riferimenri all'inizio di ogni invocazione. Certament! e Seam sta già memorizzando il gestore della persistenza nella conversazione. Perciò quando il SFSB passiva e poi si riattiva, non c'è alcun effetto negativo sull'applicazione." #. Tag: para #: ClusteringAndEJBPassivation.xml:363 #, no-c-format msgid "If you are using SFSBs in your application that hold references to extended persistence contexts, and those SFSBs can passivate, then you must use the MEI. This requirement holds even if you are using a single instance (not a cluster). However, if you are using clustered SFSB, then this requirement also applies." -msgstr "" +msgstr "Se si stanno usando degl SFSB che mantengono riferimenti a contesti di persistenza estesi, e questi SFSB possono essere passivati, allora occorre usare un MEI. Questo requisisto esiste anche se si adopera una singola istanza (non un cluster). Comunque se si usa un SFSB clustered, questo requisito permane comunque." #. Tag: para #: ClusteringAndEJBPassivation.xml:371 @@ -461,7 +461,7 @@ #: ClusteringAndEJBPassivation.xml:381 #, no-c-format msgid "Dealing with passivation of a SFSB works by leveraging the HTTP session. But what happens when the HTTP session passivates? This happens in a clustered environment with session replication enabled. This case is much tricker to deal with and is where a bulk of the MEI infrastructure comes into play. In thise case, the persistence manager is going to be destroyed because it cannot be serialized. Seam handles this deconstruction (hence ensuring that the HTTP session serializes properly). But what happens on the other end. Well, when the MEI sticks an entity instance into the conversation, it embeds the instance in a wrapper that provides information on how to reassociate the instance with a persistence manager post-serialization. So when the application jumps to another node in the cluster (presumably because the target node went down) the MEI infrastruture essentially reconstructs the persistence context. The huge drawback here is that since the persistence context is ! being reconstructed (from the database), pending changes are dropped. However, what Seam does do is ensure that if the entity instance is versioned, that the guarantees of optimistic locking are upheld. (why isn't the dirty state transfered?)" -msgstr "" +msgstr "La passivazione di un SFSB funziona facendo leva sulla sessione HTTP. Ma cosa succede quando la sessione HTTP passiva? Questo capita in un ambiente clusteres cone la replica della sessioneattivata. Questo caso è più problematico da gestire ed avviene quando entra in gioco una parte dell'infrastruttura MEI. In questo caso il gestore della persistenza sta per essere distrutto, poiché non può essere serializzato. Seam gestisce questa decostruzione (che assicura che la sessione HTTP serializzi in modo corretto). Ma cosa avviene dall'altro lato? Quando MEI colloca un'istanza entity in un conversazione, incorpora l'istanza in un wrapper che fornisce informazioni su come riassociare l'istanza col gestore di persistenza dopo la serializzazione. Perciò quando l'applicazione passa su un altro nodo del cluster (presumibilmente poiché il nodo target è sceso) l'infrastruttura MEI verrà ricostruita (dal database), i cambiamenti pendenti verranno abbandonati. Comunque quel! lo che Seam fa è assicurare che se l'istanza entity viene versionata, le garanzie di lock ottimistico vengono mantenute. (Perche lo stato dirty non viene trasferito?)" #. Tag: para #: ClusteringAndEJBPassivation.xml:397 @@ -479,5 +479,5 @@ #: ClusteringAndEJBPassivation.xml:406 #, no-c-format msgid "The important point of this section is that the MEI is there for a reason. It's there to ensure that the extended persistence context can retain intact in the face of passivation (of either a SFSB or the HTTP session). This matters because the natural design of Seam applications (and conversational state in general) revolve around the state of this resource." -msgstr "" +msgstr "Il punto importante di questa sezione è che il MEI esiste per una ragione. Per assicurare che il contesto di persistenza esteso possa rimanenre integro anche con la passivazione (sia di un SFSB sia di una sessione HTTP). Questo è importante poiché il progetto originale delle applicazione Seam (ed in generale dello stato conversazione) ruota attorno allo stato di questa risorsa." Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Jbpm.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2009-06-01 11:24:41 UTC (rev 11063) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Jbpm.po 2009-06-01 17:17:12 UTC (rev 11064) @@ -17,7 +17,7 @@ #: Jbpm.xml:2 #, no-c-format msgid "Pageflows and business processes" -msgstr "Pageflows e processi di business" +msgstr "Pageflow e processi di business" #. Tag: para #: Jbpm.xml:4 Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Weblogic.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Weblogic.po 2009-06-01 11:24:41 UTC (rev 11063) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Weblogic.po 2009-06-01 17:17:12 UTC (rev 11064) @@ -5,8 +5,8 @@ msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2009-05-26 13:23+0000\n" -"PO-Revision-Date: 2009-05-29 15:20+0100\n" +"POT-Creation-Date: 2009-05-29 06:39+0000\n" +"PO-Revision-Date: 2009-05-31 12:14+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -22,14 +22,34 @@ #. Tag: para #: Weblogic.xml:4 #, no-c-format -msgid "Weblogic 10.3 is BEA's latest stable JEE5 server offering. Seam applications can be deployed and developed on Weblogic servers, and this chapter will show you how. There are some known issues with the Weblogic servers that will need to be worked around, and configuration changes that are needed specific to Weblogic." -msgstr "Weblogic 10.3 è l'ultimo server JEE5 stabile proposto da BEA. Le applicazioni Seam possono essere sviluppate e installate sui server Weblogic, e questo capitolo vi mostrerà in che modo. Ci sono alcuni problemi noti da aggirare relativi ai server Weblogic e alcune modifiche alle configurazioni che sono specifiche di Weblogic." +msgid "" +"Weblogic 10.3 is BEA's latest stable JEE5 server offering. Seam applications " +"can be deployed and developed on Weblogic servers, and this chapter will " +"show you how. There are some known issues with the Weblogic servers that " +"will need to be worked around, and configuration changes that are needed " +"specific to Weblogic." +msgstr "" +"Weblogic 10.3 è l'ultimo server JEE5 stabile proposto da BEA. Le " +"applicazioni Seam possono essere sviluppate e installate sui server " +"Weblogic, e questo capitolo vi mostrerà in che modo. Ci sono alcuni problemi " +"noti da aggirare relativi ai server Weblogic e alcune modifiche alle " +"configurazioni che sono specifiche di Weblogic." #. Tag: para #: Weblogic.xml:10 #, no-c-format -msgid "First step is to get Weblogic downloaded, installed and running. Then we'll talk about Seam's JEE5 example and the hurdles to getting it running. After that, the JPA example will be deployed to the server. Then finally we will create a <literal>seam-gen</literal> application and get it up and running to provide a jump start to your own application." -msgstr "Innanzitutto bisogna scaricare Weblogic, installarlo e avviarlo. Quindi passeremo a parlare dell'esempio JEE5 di Seam e deigli ostacoli da superare per farlo funzionare. Dopo di ché, installeremo l'esempio JPA. Infine creeremo un'applicazione <literal>seam-gen</literal> e la faremo girare per fornire un punto di partenza alla vostra applicazione." +msgid "" +"First step is to get Weblogic downloaded, installed and running. Then we'll " +"talk about Seam's JEE5 example and the hurdles to getting it running. After " +"that, the JPA example will be deployed to the server. Then finally we will " +"create a <literal>seam-gen</literal> application and get it up and running " +"to provide a jump start to your own application." +msgstr "" +"Innanzitutto bisogna scaricare Weblogic, installarlo e avviarlo. Quindi " +"passeremo a parlare dell'esempio JEE5 di Seam e deigli ostacoli da superare " +"per farlo funzionare. Dopo di ché, installeremo l'esempio JPA. Infine " +"creeremo un'applicazione <literal>seam-gen</literal> e la faremo girare per " +"fornire un punto di partenza alla vostra applicazione." # operatività? # messa in opera? @@ -42,46 +62,99 @@ #. Tag: para #: Weblogic.xml:19 #, no-c-format -msgid "First things first we need to get the server installed. There are some outstanding issues that were not addressed in 10.3, but it does solve some of the issues discussed below without the need for BEA patches. The previous release 10.0.MP1 is also available, but requires some BEA patches to function correctly." -msgstr "Prima di tutto bisogna installare il server. Ci sono alcuni problemi non trascurabili che non sono stati affrontati nella 10.3, che tuttavia risolve alcuni di quelli discussi sotto senza dover installare le patch di BEA. E' disponibile anche il precedente rilascio, 10.0.MP1, che, tuttavia, richiede le patch di BEA per funzionare correttamente." +msgid "" +"First things first we need to get the server installed. There are some " +"outstanding issues that were not addressed in 10.3, but it does solve some " +"of the issues discussed below without the need for BEA patches. The previous " +"release 10.0.MP1 is also available, but requires some BEA patches to " +"function correctly." +msgstr "" +"Prima di tutto bisogna installare il server. Ci sono alcuni problemi non " +"trascurabili che non sono stati affrontati nella 10.3, che tuttavia risolve " +"alcuni di quelli discussi sotto senza dover installare le patch di BEA. E' " +"disponibile anche il precedente rilascio, 10.0.MP1, che, tuttavia, richiede " +"le patch di BEA per funzionare correttamente." #. Tag: para #: Weblogic.xml:26 #, no-c-format -msgid "<literal>Weblogic 10.0.MP1</literal> — <ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html\"> Download page </ulink>" -msgstr "<literal>Weblogic 10.0.MP1</literal> — <ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html\"> Pagina di download </ulink>" +msgid "" +"<literal>Weblogic 10.0.MP1</literal> — <ulink url=\"http://www.oracle." +"com/technology/software/products/ias/htdocs/wls_main.html\"> Download page </" +"ulink>" +msgstr "" +"<literal>Weblogic 10.0.MP1</literal> — <ulink url=\"http://www.oracle." +"com/technology/software/products/ias/htdocs/wls_main.html\"> Pagina di " +"download </ulink>" -# weblogic-ejb-issues va tradotto? #. Tag: para #: Weblogic.xml:30 #, no-c-format -msgid "10.0.MP1 has some known issues with EJBs that use <literal>varargs</literal> in their methods (it confuses them as <literal>transient</literal> ), as well as some others. See <xref linkend=\"weblogic-ejb-issues\"/> for full details on the issues and the work around." -msgstr "La versione 10.0.MP1 ha alcuni problemi noti con gli EJBs che usano <literal>varargs</literal> nei propri metodi (li confonde con <literal>transient</literal> ), e non sono gli unici. Si veda <xref linkend=\"weblogic-ejb-issues\"/> per tutti i dettagli su tali problemi e per le relative soluzioni." +msgid "" +"10.0.MP1 has some known issues with EJBs that use <literal>varargs</literal> " +"in their methods (it confuses them as <literal>transient</literal> ), as " +"well as some others. See <xref linkend=\"weblogic-ejb-issues\"/> for full " +"details on the issues and the work around." +msgstr "" +"La versione 10.0.MP1 ha alcuni problemi noti con gli EJBs che usano " +"<literal>varargs</literal> nei propri metodi (li confonde con " +"<literal>transient</literal> ), e non sono gli unici. Si veda <xref linkend=" +"\"weblogic-ejb-issues\"/> per tutti i dettagli su tali problemi e per le " +"relative soluzioni." #. Tag: para #: Weblogic.xml:37 #, no-c-format -msgid "<literal>Weblogic 10.3</literal> — <ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html\"> Download page </ulink>" -msgstr "<literal>Weblogic 10.3</literal> — <ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html\"> Pagina di download </ulink>" +msgid "" +"<literal>Weblogic 10.3</literal> — <ulink url=\"http://www.oracle.com/" +"technology/software/products/ias/htdocs/wls_main.html\"> Download page </" +"ulink>" +msgstr "" +"<literal>Weblogic 10.3</literal> — <ulink url=\"http://www.oracle.com/" +"technology/software/products/ias/htdocs/wls_main.html\"> Pagina di download " +"</ulink>" -# weblogic-ejb-issues è da tradurre? #. Tag: para #: Weblogic.xml:41 #, no-c-format -msgid "This is the latest stable release of the Weblogic server, and the one that will be used with the examples below. This version has addressed some of the issues with EJBs that were in 10.0.MP1. However one of the changes did not make it into this release. See <xref linkend=\"weblogic-ejb-issues\"/> for the details, but because of this we still need to use the special Weblogic seam jar discussed below." -msgstr "Questa è l'ultima versione stabile del server Weblogic, e quello che sarà usato negli esempi sottostanti. Questa versione ha sistemato alcuni dei malfunzionamenti relativi agli EJB che esistevano nella versione 10.0.MP1. Comunque una delle modifiche non è stata inserita in questa versione. Si veda <xref linkend=\"weblogic-ejb-issues\"/> per i dettagli, e perciò bisogna ancora usare lo speciale jar di Seam di Weblogic discusso di seguito." +msgid "" +"This is the latest stable release of the Weblogic server, and the one that " +"will be used with the examples below. This version has addressed some of the " +"issues with EJBs that were in 10.0.MP1. However one of the changes did not " +"make it into this release. See <xref linkend=\"weblogic-ejb-issues\"/> for " +"the details, but because of this we still need to use the special Weblogic " +"seam jar discussed below." +msgstr "" +"Questa è l'ultima versione stabile del server Weblogic, e quello che sarà " +"usato negli esempi sottostanti. Questa versione ha sistemato alcuni dei " +"malfunzionamenti relativi agli EJB che esistevano nella versione 10.0.MP1. " +"Comunque una delle modifiche non è stata inserita in questa versione. Si " +"veda <xref linkend=\"weblogic-ejb-issues\"/> per i dettagli, e perciò " +"bisogna ancora usare lo speciale jar di Seam di Weblogic discusso di seguito." #. Tag: title #: Weblogic.xml:53 #, no-c-format msgid "Special <literal>jboss-seam.jar</literal> for Weblogic EJB Support" -msgstr "Il jar speciale <literal>jboss-seam.jar</literal> per il supporto EJB in Weblogic" +msgstr "" +"Il jar speciale <literal>jboss-seam.jar</literal> per il supporto EJB in " +"Weblogic" #. Tag: para #: Weblogic.xml:55 #, no-c-format -msgid "Starting with Seam 2.0.2.CR2 a special Weblogic specific jar has been created that does not contain the <literal>TimerServiceDispatcher </literal>. This is the EJB that uses <literal>varargs</literal> and exposes the second EJB issue. We will be using this jar for the <literal>jee5/booking</literal> example, as it avoids the known BEA issues." -msgstr "A partire da Seam 2.0.2.CR2 per Weblogic è stato creato un jar speciale che non contiene il <literal>TimerServiceDispatcher </literal>. Questo è l'EJB che usa <literal>varargs</literal> e presenta il secondo problema relativo agli EJB. Ci troveremo ad usare questo jar per l'esempio <literal>jee5/booking</literal>, poiché evita i noti problemi di BEA." +msgid "" +"Starting with Seam 2.0.2.CR2 a special Weblogic specific jar has been " +"created that does not contain the <literal>TimerServiceDispatcher </" +"literal>. This is the EJB that uses <literal>varargs</literal> and exposes " +"the second EJB issue. We will be using this jar for the <literal>jee5/" +"booking</literal> example, as it avoids the known BEA issues." +msgstr "" +"A partire da Seam 2.0.2.CR2 per Weblogic è stato creato un jar speciale che " +"non contiene il <literal>TimerServiceDispatcher </literal>. Questo è l'EJB " +"che usa <literal>varargs</literal> e presenta il secondo problema relativo " +"agli EJB. Ci troveremo ad usare questo jar per l'esempio <literal>jee5/" +"booking</literal>, poiché evita i noti problemi di BEA." #. Tag: title #: Weblogic.xml:65 @@ -92,20 +165,39 @@ #. Tag: para #: Weblogic.xml:67 #, no-c-format -msgid "Here are the quick steps to installing Weblogic 10.3. For more details or if you are having any issues please check with the BEA docs at the <ulink url=\"http://edocs.bea.com/wls/docs103/\"> Weblogic 10.3 Doc Center </ulink> . Here we install the RHEL 5 version using the graphical installer:" -msgstr "Ecco velocemente i passi necessari ad installare Weblogic 10.3. Per maggiori dettagli e nel caso si presentino dei problemi,vi preghiamo di consultare i documenti BEA all'indirizzo <ulink url=\"http://edocs.bea.com/wls/docs103/\"> Weblogic 10.3 Doc Center </ulink> . Qui verrà installata la versione RHEL 5 usando l'installazione grafica:" +msgid "" +"Here are the quick steps to installing Weblogic 10.3. For more details or if " +"you are having any issues please check with the BEA docs at the <ulink url=" +"\"http://edocs.bea.com/wls/docs103/\"> Weblogic 10.3 Doc Center </ulink> . " +"Here we install the RHEL 5 version using the graphical installer:" +msgstr "" +"Ecco velocemente i passi necessari ad installare Weblogic 10.3. Per maggiori " +"dettagli e nel caso si presentino dei problemi,vi preghiamo di consultare i " +"documenti BEA all'indirizzo <ulink url=\"http://edocs.bea.com/wls/docs103/" +"\"> Weblogic 10.3 Doc Center </ulink> . Qui verrà installata la versione " +"RHEL 5 usando l'installazione grafica:" #. Tag: para #: Weblogic.xml:80 #, no-c-format -msgid "Follow the link given above for 10.3 and download the correct version for your environment. You will need to sign up for an account with Oracle in order to do this." -msgstr "Si segua il link alla 10.3 indicato sopra e si scarichi la versione adatta al proprio ambiente. Sarà necessario creare un account Oracle per portare a termine l'operazione." +msgid "" +"Follow the link given above for 10.3 and download the correct version for " +"your environment. You will need to sign up for an account with Oracle in " +"order to do this." +msgstr "" +"Si segua il link alla 10.3 indicato sopra e si scarichi la versione adatta " +"al proprio ambiente. Sarà necessario creare un account Oracle per portare a " +"termine l'operazione." #. Tag: para #: Weblogic.xml:85 #, no-c-format -msgid "You may need to change the the <literal>server103_XX.bin</literal> file to be executable:" -msgstr "Può essere necessario rendere eseguibile il file <literal>server103_XX.bin</literal>:" +msgid "" +"You may need to change the the <literal>server103_XX.bin</literal> file to " +"be executable:" +msgstr "" +"Può essere necessario rendere eseguibile il file <literal>server103_XX.bin</" +"literal>:" #. Tag: programlisting #: Weblogic.xml:88 @@ -128,8 +220,15 @@ #. Tag: para #: Weblogic.xml:95 #, no-c-format -msgid "When the graphical install loads, you need to set the BEA home location. This is where all BEA applications are installed. This location will be known as <literal>$BEA_HOME</literal> in this document e.g.:" -msgstr "Quando l'installazione grafica è caricata, bisogna impostare il percorso della home directory di BEA. Questo è il punto dove sono installate tutte le applicazioni BEA. In questo documento tale punto sarà identificato con <literal>$BEA_HOME</literal>, ad esempio:" +msgid "" +"When the graphical install loads, you need to set the BEA home location. " +"This is where all BEA applications are installed. This location will be " +"known as <literal>$BEA_HOME</literal> in this document e.g.:" +msgstr "" +"Quando l'installazione grafica è caricata, bisogna impostare il percorso " +"della home directory di BEA. Questo è il punto dove sono installate tutte le " +"applicazioni BEA. In questo documento tale punto sarà identificato con " +"<literal>$BEA_HOME</literal>, ad esempio:" #. Tag: programlisting #: Weblogic.xml:100 @@ -140,14 +239,24 @@ #. Tag: para #: Weblogic.xml:103 #, no-c-format -msgid "Select <literal>Complete</literal> as the installation type. You do not need all the extras of the complete install (such as struts and beehive libraries), but it will not hurt." -msgstr "Come tipo di installazione bisogna selezionare <literal>Complete</literal>. Non c'è bisogno di tutti gli extra dell'installazione competa (come le librerie struts e beehive), ma non farà alcun male." +msgid "" +"Select <literal>Complete</literal> as the installation type. You do not need " +"all the extras of the complete install (such as struts and beehive " +"libraries), but it will not hurt." +msgstr "" +"Come tipo di installazione bisogna selezionare <literal>Complete</literal>. " +"Non c'è bisogno di tutti gli extra dell'installazione competa (come le " +"librerie struts e beehive), ma non farà alcun male." #. Tag: para #: Weblogic.xml:109 #, no-c-format -msgid "You can leave the defaults for the component installation locations on the next page." -msgstr "Nella pagina successiva è possibile lasciare i valori predefiniti delle posizioni di installazione dei componenti." +msgid "" +"You can leave the defaults for the component installation locations on the " +"next page." +msgstr "" +"Nella pagina successiva è possibile lasciare i valori predefiniti delle " +"posizioni di installazione dei componenti." #. Tag: title #: Weblogic.xml:115 @@ -159,8 +268,18 @@ #. Tag: para #: Weblogic.xml:116 #, no-c-format -msgid "A Weblogic domain is similar to a JBoss server configuration - it is a self contained server instance. The Weblogic server you just installed has some example domains, but we are going to create one just for the seam examples. You can use the existing domains if you wish (modify the instructions as needed)." -msgstr "Un dominio Weblogic è simile ad una configurazione del server JBoss - è un'istanza autosufficiente del server. Il server Weblogic appena installato ha alcuni domini di esempio, ma noi ne creeremo uno apposito per gli esempi di Seam. Se si vuole, è possibile usare i domini esistenti (modificando le istruzioni opportunamente)." +msgid "" +"A Weblogic domain is similar to a JBoss server configuration - it is a self " +"contained server instance. The Weblogic server you just installed has some " +"example domains, but we are going to create one just for the seam examples. " +"You can use the existing domains if you wish (modify the instructions as " +"needed)." +msgstr "" +"Un dominio Weblogic è simile ad una configurazione del server JBoss - è " +"un'istanza autosufficiente del server. Il server Weblogic appena installato " +"ha alcuni domini di esempio, ma noi ne creeremo uno apposito per gli esempi " +"di Seam. Se si vuole, è possibile usare i domini esistenti (modificando le " +"istruzioni opportunamente)." #. Tag: para #: Weblogic.xml:123 @@ -174,12 +293,16 @@ msgid "$BEA_HOME/wlserver_10.3/common/bin/config.sh" msgstr "$BEA_HOME/wlserver_10.3/common/bin/config.sh" -# Weblogic Server è da tradurre? #. Tag: para #: Weblogic.xml:127 #, no-c-format -msgid "Choose to create a new domain, configured to support <literal>Weblogic Server</literal>. Note that this is the default domain option." -msgstr "Si scelga di creare un nuovo dominio, configurato per supportare <literal>Weblogic Server</literal>. Tenete presente che questa è l'opzione predefinita per il dominio." +msgid "" +"Choose to create a new domain, configured to support <literal>Weblogic " +"Server</literal>. Note that this is the default domain option." +msgstr "" +"Si scelga di creare un nuovo dominio, configurato per supportare " +"<literal>Weblogic Server</literal>. Tenete presente che questa è l'opzione " +"predefinita per il dominio." #. Tag: para #: Weblogic.xml:132 @@ -190,20 +313,32 @@ #. Tag: para #: Weblogic.xml:135 #, no-c-format -msgid "Next choose <literal>Development Mode</literal> and the default JDK when given the option." -msgstr "Quindi si scelga <literal>Development Mode</literal> e il JDK predefinito quando richiesto." +msgid "" +"Next choose <literal>Development Mode</literal> and the default JDK when " +"given the option." +msgstr "" +"Quindi si scelga <literal>Development Mode</literal> e il JDK predefinito " +"quando richiesto." #. Tag: para #: Weblogic.xml:139 #, no-c-format -msgid "The next screen asks if you want to customize any setting. Select <literal>No</literal>." -msgstr "La schermata successiva chiede se si vuole personalizzare qualche proprietà. Bisogna selezionare <literal>No</literal>." +msgid "" +"The next screen asks if you want to customize any setting. Select " +"<literal>No</literal>." +msgstr "" +"La schermata successiva chiede se si vuole personalizzare qualche proprietà. " +"Bisogna selezionare <literal>No</literal>." #. Tag: para #: Weblogic.xml:143 #, no-c-format -msgid "Finally set the name of the domain to <literal>seam_examples</literal> and leave the default domain location." -msgstr "Infine bisogna indicare <literal>seam_examples</literal> come nome del dominio e lasciare la sua posizione predefinita." +msgid "" +"Finally set the name of the domain to <literal>seam_examples</literal> and " +"leave the default domain location." +msgstr "" +"Infine bisogna indicare <literal>seam_examples</literal> come nome del " +"dominio e lasciare la sua posizione predefinita." #. Tag: title #: Weblogic.xml:150 @@ -214,86 +349,125 @@ #. Tag: para #: Weblogic.xml:151 #, no-c-format -msgid "Now that the server is installed and the domain is created you need to know how to start and stop it, plus how to access its configuration console." +msgid "" +"Now that the server is installed and the domain is created you need to know " +"how to start and stop it, plus how to access its configuration console." msgstr "" +"Ora che si è installato il server e creato il dominio, bisogna imparare ad " +"avviarlo ed arrestarlo, oltre ad accedere alla console di configurazione." #. Tag: para #: Weblogic.xml:158 #, no-c-format msgid "Starting the domain:" -msgstr "Avvio del dominio:" +msgstr "Avviare il dominio:" #. Tag: para #: Weblogic.xml:159 #, no-c-format -msgid "This is the easy part - go to the <literal> $BEA_HOME/user_projects/domains/seam_examples/bin </literal> directory and run the <literal>./startWeblogic.sh</literal> script." +msgid "" +"This is the easy part - go to the <literal> $BEA_HOME/user_projects/domains/" +"seam_examples/bin </literal> directory and run the <literal>./startWeblogic." +"sh</literal> script." msgstr "" +"Questa è la parte facile - entrate nella directory <literal> $BEA_HOME/" +"user_projects/domains/seam_examples/bin </literal> e lanciate lo script " +"<literal>./startWeblogic.sh</literal>" #. Tag: para #: Weblogic.xml:165 #, no-c-format msgid "Accessing the configuration console:" -msgstr "" +msgstr "Accedere alla console di configurazione:" #. Tag: para #: Weblogic.xml:166 #, no-c-format -msgid "Launch <literal>http://127.0.0.1:7001/console</literal> in your web browser. It will ask for your username and password that you entered before. We won't get into this much now, but this is the starting point for a lot of the various configurations that are needed later." +msgid "" +"Launch <literal>http://127.0.0.1:7001/console</literal> in your web browser. " +"It will ask for your username and password that you entered before. We won't " +"get into this much now, but this is the starting point for a lot of the " +"various configurations that are needed later." msgstr "" +"Col browser andate all'indirizzo <literal>http://127.0.0.1:7001/console</" +"literal>. Vi saranno richiesti l'utente e la password inseriti in " +"precedenza. Non ci addentreremo molto in questa questione, ma questo è il " +"punto di partenza per molte delle diverse configurazioni di cui avremo " +"bisogno più tardi." #. Tag: para #: Weblogic.xml:174 #, no-c-format msgid "Stopping the domain:" -msgstr "Arresto del dominio:" +msgstr "Arrestare il dominio:" #. Tag: para #: Weblogic.xml:175 #, no-c-format msgid "There are a couple of options here:" -msgstr "" +msgstr "In questo caso ci sono un paio di opzioni:" #. Tag: para #: Weblogic.xml:178 #, no-c-format msgid "The recommended way is through the configuration console:" -msgstr "" +msgstr "Il modo raccomandato si basa sulla console di configurazione:" #. Tag: para #: Weblogic.xml:182 #, no-c-format -msgid "Select <literal>seam_examples</literal> on the left hand side of the console." +msgid "" +"Select <literal>seam_examples</literal> on the left hand side of the console." msgstr "" +"Selezionate <literal>seam_examples</literal> sul lato sinistro della console." #. Tag: para #: Weblogic.xml:187 #, no-c-format msgid "Choose the <literal>Control</literal> tab in the middle of the page." msgstr "" +"Clicacte sulla linguetta <literal>Control</literal> nel mezzo della pagina." #. Tag: para #: Weblogic.xml:192 #, no-c-format msgid "Select the check box <literal>AdminServer</literal> in the table." msgstr "" +"Nella tabella selezionate la casella di spunta <literal>AdminServer</" +"literal>." #. Tag: para #: Weblogic.xml:197 #, no-c-format -msgid "Choose <literal>Shutdown</literal> just above the table, and select either <literal>When work completes</literal> or <literal>Force shutdown now</literal> as appropriate." +msgid "" +"Choose <literal>Shutdown</literal> just above the table, and select either " +"<literal>When work completes</literal> or <literal>Force shutdown now</" +"literal> as appropriate." msgstr "" +"Scegliete <literal>Shutdown</literal> appena sopra la tabella, e selezionate " +"l'opzione appropriata tra <literal>When work completes</literal> e " +"<literal>Force shutdown now</literal>." #. Tag: para #: Weblogic.xml:206 #, no-c-format -msgid "Hitting <literal>Ctrl-C</literal> in the terminal where you started the domain." +msgid "" +"Hitting <literal>Ctrl-C</literal> in the terminal where you started the " +"domain." msgstr "" +"Premere <literal>Ctrl-C</literal> nel terminale in cui è stato avviato il " +"dominio." #. Tag: para #: Weblogic.xml:208 #, no-c-format -msgid "No negative effects have been seen, but we would not recommend doing this while in the middle of configuration changes in the console." +msgid "" +"No negative effects have been seen, but we would not recommend doing this " +"while in the middle of configuration changes in the console." msgstr "" +"Non si sono visti effetti negativi, but non raccomanderemmo di effettuare " +"questa operazione mentre si stanno apportando delle modifiche alla " +"configurazione nella console." #. Tag: title #: Weblogic.xml:216 @@ -304,250 +478,481 @@ #. Tag: para #: Weblogic.xml:217 #, no-c-format -msgid "When using the <literal>/autodeploy</literal> directory as described in this chapter you may see <literal>NoClassDefFound</literal> exceptions during redeployment's. If you see this try restarting the Weblogic server. If you still see it remove the auto-deployed EAR/WAR files, restart the server, and redeploy. We could not find a specific reason for this, but others seem to be having this issue as well." +msgid "" +"When using the <literal>/autodeploy</literal> directory as described in this " +"chapter you may see <literal>NoClassDefFound</literal> exceptions during " +"redeployment's. If you see this try restarting the Weblogic server. If you " +"still see it remove the auto-deployed EAR/WAR files, restart the server, and " +"redeploy. We could not find a specific reason for this, but others seem to " +"be having this issue as well." msgstr "" +"Quando si utilizza la directory <literal>/autodeploy</literal> come " +"descritto in questo capitolo, è possibile vedere delle eccezioni " +"<literal>NoClassDefFound</literal> durante il re-deploy delle applicazioni. " +"Se le vedete, provate a riavviare il server. Se continuate a vederle, " +"eliminate i file EAR/WAR autoinstallati, riavviate il server e rifate il " +"deploy. Non abbiamo trovato la ragione specifica di questo comportamento, " +"tuttavia sembra che anche altri abbiano avuto questo genere di problema." #. Tag: title #: Weblogic.xml:230 #, no-c-format msgid "Setting up Weblogic's JSF Support" -msgstr "" +msgstr "Impostazione del supporto JSF in Weblogic" #. Tag: para #: Weblogic.xml:231 #, no-c-format -msgid "These are the instructions to deploy and configure Weblogic's JSF 1.2 libraries. Out of the box Weblogic does not come with its own JSF libraries active. For complete details see <ulink url=\"http://edocs.bea.com/wls/docs103/webapp/configurejsfandjtsl.html\"> Weblogic 10.3 Configuring JSF and JSTL Libraries </ulink>" +msgid "" +"These are the instructions to deploy and configure Weblogic's JSF 1.2 " +"libraries. Out of the box Weblogic does not come with its own JSF libraries " +"active. For complete details see <ulink url=\"http://edocs.bea.com/wls/" +"docs103/webapp/configurejsfandjtsl.html\"> Weblogic 10.3 Configuring JSF and " +"JSTL Libraries </ulink>" msgstr "" +"Queste sono le istruzioni per installare e configurare le librerie JSF 1.2 " +"di Weblogic. Weblogic non viene distribuito con le librerie JSF " +"preinstallate. Per i dettagli completi si veda <ulink url=\"http://edocs.bea." +"com/wls/docs103/webapp/configurejsfandjtsl.html\"> Weblogic 10.3 Configuring " +"JSF and JSTL Libraries </ulink>" #. Tag: para #: Weblogic.xml:240 #, no-c-format -msgid "In the administration console navigate to the <literal>Deployments</literal> page using the left hand menu." +msgid "" +"In the administration console navigate to the <literal>Deployments</literal> " +"page using the left hand menu." msgstr "" +"Nella console di amministrazione navigate alla pagina <literal>Deployments</" +"literal> usando il menù sul lato sinistro." #. Tag: para #: Weblogic.xml:245 #, no-c-format -msgid "Then select the <literal>Install</literal> button at the top of the deployments table" +msgid "" +"Then select the <literal>Install</literal> button at the top of the " +"deployments table" msgstr "" +"A questo punto prenmete il pulsante <literal>Install</literal> in cima alla " +"tabella dei deployment" #. Tag: para #: Weblogic.xml:249 #, no-c-format -msgid "Using the directory browser navigate to the <literal>$BEA_HOME/wlserver_10.3/common/deployable-libraries </literal> directory. Then select the <literal>jsf-1.2.war</literal> archive, and click the <literal>Next</literal> button." +msgid "" +"Using the directory browser navigate to the <literal>$BEA_HOME/wlserver_10.3/" +"common/deployable-libraries </literal> directory. Then select the " +"<literal>jsf-1.2.war</literal> archive, and click the <literal>Next</" +"literal> button." msgstr "" +"Usando il browser delle directory navigate alla directory <literal>$BEA_HOME/" +"wlserver_10.3/common/deployable-libraries </literal>. Selezionate l'archivio " +"<literal>jsf-1.2.war</literal>, e cliccate il pulsante <literal>Next</" +"literal>." #. Tag: para #: Weblogic.xml:256 #, no-c-format -msgid "Make sure that the <literal>Install this deployment as a library</literal> is selected. Click the <literal> Next </literal> button on the <literal>Install Application Assistant</literal> page." +msgid "" +"Make sure that the <literal>Install this deployment as a library</literal> " +"is selected. Click the <literal> Next </literal> button on the " +"<literal>Install Application Assistant</literal> page." msgstr "" +"Accertatevi che sia selezionata l'opzione <literal>Install this deployment " +"as a library</literal>. Cliccate il pulsante <literal> Next </literal> della " +"pagina <literal>Install Application Assistant</literal>." #. Tag: para #: Weblogic.xml:262 #, no-c-format -msgid "Click the <literal>Next</literal> button on the <literal> Optional Settings</literal> page." +msgid "" +"Click the <literal>Next</literal> button on the <literal> Optional Settings</" +"literal> page." msgstr "" +"Premete il pulsante <literal>Next</literal> della pagina <literal> Optional " +"Settings</literal>." #. Tag: para #: Weblogic.xml:266 #, no-c-format -msgid "Make sure that the <literal>Yes, take me to the deployment's configuration screen.</literal> is selected. Click the <literal>Finish</literal> button on the <literal> Review your choices and click Finish</literal> page." +msgid "" +"Make sure that the <literal>Yes, take me to the deployment's configuration " +"screen.</literal> is selected. Click the <literal>Finish</literal> button on " +"the <literal> Review your choices and click Finish</literal> page." msgstr "" +"Accertatevi che sia selezionata l'opzione <literal>Yes, take me to the " +"deployment's configuration screen.</literal>. Cliccate il pulsante " +"<literal>Finish</literal> della pagina <literal> Review your choices and " +"click Finish</literal>." #. Tag: para #: Weblogic.xml:272 #, no-c-format -msgid "On the <literal>Settings for jsf(1.2,1.2.3.1)</literal> page set the <literal>Deployment Order</literal> to <literal>99</literal> so that it is deployed prior to auto deployed applications. Then click the <literal> Save</literal> button." +msgid "" +"On the <literal>Settings for jsf(1.2,1.2.3.1)</literal> page set the " +"<literal>Deployment Order</literal> to <literal>99</literal> so that it is " +"deployed prior to auto deployed applications. Then click the <literal> Save</" +"literal> button." msgstr "" +"Nella pagina <literal>Impostazioni per jsf(1.2,1.2.3.1)</literal> impostate " +"<literal>Deployment Order</literal> a <literal>99</literal> in modo che il " +"supporto JSF venga installato prima delle applicazioni sottoposte ad " +"autodeploy. Poi cliccate sul bottone <literal>Save</literal>." #. Tag: para #: Weblogic.xml:280 #, no-c-format -msgid "There is another step that is needed for this to work. For some reason, even with the steps above classes in the <literal> jsf-api.jar</literal> are not found during application deployment. The only way for this to work is to put the <literal> javax.jsf_1.2.0.0.jar</literal> (the jsf-api.jar) from <literal>jsf-1.2.war</literal> in the domains shared library. This requires a restart of the server." +msgid "" +"There is another step that is needed for this to work. For some reason, even " +"with the steps above classes in the <literal> jsf-api.jar</literal> are not " +"found during application deployment. The only way for this to work is to put " +"the <literal> javax.jsf_1.2.0.0.jar</literal> (the jsf-api.jar) from " +"<literal>jsf-1.2.war</literal> in the domains shared library. This requires " +"a restart of the server." msgstr "" +"Bisogna eseguire un altro passo per far funzionare il tutto. Per qualche " +"motivo, anche eseguendo le operazioni precedenti, durante il deploy " +"dell'applicazione non vengono trovate delle classi di <literal> jsf-api.jar</" +"literal>. L'unico modo per ovviare al problema è di spostare <literal> javax." +"jsf_1.2.0.0.jar</literal> (il jsf-api.jar) da <literal>jsf-1.2.war</literal> " +"nelle librerie condivise dei domini. Questo richiede il riavvio del server." #. Tag: title #: Weblogic.xml:292 #, no-c-format msgid "The <literal>jee5/booking</literal> Example" -msgstr "" +msgstr "L'esempio <literal>jee5/booking</literal>" #. Tag: para #: Weblogic.xml:294 #, no-c-format -msgid "Do you want to run Seam using EJB's on Weblogic? If so there are some obstacles that you will have to avoid, or some patches that are needed from BEA. This section describes those obstacles and what changes are needed to the <literal>jee5/booking</literal> example to get it deployed and functioning." +msgid "" +"Do you want to run Seam using EJB's on Weblogic? If so there are some " +"obstacles that you will have to avoid, or some patches that are needed from " +"BEA. This section describes those obstacles and what changes are needed to " +"the <literal>jee5/booking</literal> example to get it deployed and " +"functioning." msgstr "" +"Si vuole usare Seam con gli EJB su Weblogic? In questo caso ci sono alcuni " +"ostacoli da evitare o alcune patch di BEA ad installare. Questa sezione " +"descrive questi ostacoli e quali modifiche apportare all'esempio " +"<literal>jee5/booking</literal> per installarlo correttamente e farlo " +"funzionare." #. Tag: title #: Weblogic.xml:303 #, no-c-format msgid "EJB3 Issues with Weblogic" -msgstr "" +msgstr "I problemi di Weblogic con EJB3" #. Tag: para #: Weblogic.xml:305 #, no-c-format -msgid "For several releases of Weblogic there has been an issue with how Weblogic generates stubs and compiles EJB's that use variable arguments in their methods. This is confirmed in the Weblogic 9.X and 10.0.MP1 versions. Unfortunately the 10.3 version only partially addresses the issue as detailed below." +msgid "" +"For several releases of Weblogic there has been an issue with how Weblogic " +"generates stubs and compiles EJB's that use variable arguments in their " +"methods. This is confirmed in the Weblogic 9.X and 10.0.MP1 versions. " +"Unfortunately the 10.3 version only partially addresses the issue as " +"detailed below." msgstr "" +"Per molte versione successive di Weblogic c'è stato un problema relativo a " +"come Weblogic genera gli stub e a come compila gli EJB che usano argomenti " +"variabili nei propri metodi. Problema confermato nelle versioni 9.X e 10.0." +"MP1. Purtroppo la versione 10.3 lo affronta solo parzialmente come " +"dettagliato di seguito." #. Tag: title #: Weblogic.xml:314 #, no-c-format msgid "The <literal>varargs</literal> Issue" -msgstr "" +msgstr "Il problema con i <literal>varargs</literal>" #. Tag: para #: Weblogic.xml:315 #, no-c-format -msgid "The basic explanation of the issue is that the Weblogic EJB compiler mistakes methods that use <literal>varargs</literal> as having the <literal>transient</literal> modifier. When BEA generates its own stub class from those classes during deployment it fails and the deployment does not succeed. Seam uses variable arguments in one of its internal EJB's ( <literal>TimerServiceDispatcher</literal>). If you see exceptions like below during deployment you are running an unpatched version of 10.0.MP1." +msgid "" +"The basic explanation of the issue is that the Weblogic EJB compiler " +"mistakes methods that use <literal>varargs</literal> as having the " +"<literal>transient</literal> modifier. When BEA generates its own stub class " +"from those classes during deployment it fails and the deployment does not " +"succeed. Seam uses variable arguments in one of its internal EJB's " +"( <literal>TimerServiceDispatcher</literal>). If you see exceptions like " +"below during deployment you are running an unpatched version of 10.0.MP1." msgstr "" +"La spiegazione base del problema è che il compilatore EJB di Weblogic " +"confonde i metodi che usano <literal>varargs</literal> con i metodi col " +"modificatore <literal>transient</literal>. Quando BEA genera le proprie " +"classi stub da quelle classi durante il deploy, esso non ha successo. Seam " +"usa argomenti variabili in uno dei suoi EJB interni " +"( <literal>TimerServiceDispatcher</literal>). Se durante il deply si vedono " +"eccezioni come quella riportata sotto, la versione corrente è la 10.0.MP1 " +"senza patch." #. Tag: programlisting #: Weblogic.xml:327 #, no-c-format msgid "" "<![CDATA[java.io.IOException: Compiler failed executable.exec: \n" -"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/AdminServer\n" +"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/" +"AdminServer\n" "/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n" -"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:194: modifier transient \n" +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:194: " +"modifier transient \n" "not allowed here\n" -" public transient javax.ejb.Timer scheduleAsynchronousEvent(java.lang.String arg0,\n" +" public transient javax.ejb.Timer scheduleAsynchronousEvent(java.lang." +"String arg0,\n" " java.lang.Object[] arg1)\n" " ^\n" -"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/AdminServer\n" +"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/" +"AdminServer\n" "/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n" -"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:275: modifier transient\n" +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:275: " +"modifier transient\n" "not allowed here\n" -" public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String arg0, \n" +" public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String " +"arg0, \n" " org.jboss.seam.async.TimerSchedule arg1, java.lang.Object[] arg2)]]>" msgstr "" "<![CDATA[java.io.IOException: Compiler failed executable.exec: \n" -"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/AdminServer\n" +"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/" +"AdminServer\n" "/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n" -"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:194: modifier transient \n" +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:194: " +"modifier transient \n" "not allowed here\n" -" public transient javax.ejb.Timer scheduleAsynchronousEvent(java.lang.String arg0,\n" +" public transient javax.ejb.Timer scheduleAsynchronousEvent(java.lang." +"String arg0,\n" " java.lang.Object[] arg1)\n" " ^\n" -"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/AdminServer\n" +"/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/" +"AdminServer\n" "/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n" -"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:275: modifier transient\n" +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:275: " +"modifier transient\n" "not allowed here\n" -" public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String arg0, \n" +" public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String " +"arg0, \n" " org.jboss.seam.async.TimerSchedule arg1, java.lang.Object[] arg2)]]>" #. Tag: para #: Weblogic.xml:328 #, no-c-format -msgid "This issue has been fixed in Weblogic 10.3, and BEA has created a patch for Weblogic 10.0.MP1 ( <literal>CR327275</literal> ) for this issue that can be requested from their support." +msgid "" +"This issue has been fixed in Weblogic 10.3, and BEA has created a patch for " +"Weblogic 10.0.MP1 ( <literal>CR327275</literal> ) for this issue that can be " +"requested from their support." msgstr "" +"Questo problema è stato risolto con Weblogic 10.3 e BEA ha rilasciato una " +"patch per Weblogic 10.0.MP1 ( <literal>CR327275</literal> ) che può essere " +"richiesta al loro supporto." #. Tag: para #: Weblogic.xml:335 #, no-c-format msgid "Unfortunately a second issue has been reported and verified by BEA." -msgstr "" +msgstr "Purtroppo BEA ha verificato e annunciato un secondo problema." #. Tag: title #: Weblogic.xml:341 #, no-c-format msgid "Missing EJB Methods Issue" -msgstr "" +msgstr "Il problema dei metodi EJB mancanti" #. Tag: para #: Weblogic.xml:343 #, no-c-format -msgid "This issue was only found once the <literal>CR327275</literal> patch had been applied to 10.0.MP1. This new issue has been confirmed by BEA and they created a patch for 10.0.MP1 that addresses this issue. This patch has been referred to as both <literal>CR370259</literal> and <literal>CR363182</literal>. As with the other patch this can be requested through the BEA support." +msgid "" +"This issue was only found once the <literal>CR327275</literal> patch had " +"been applied to 10.0.MP1. This new issue has been confirmed by BEA and they " +"created a patch for 10.0.MP1 that addresses this issue. This patch has been " +"referred to as both <literal>CR370259</literal> and <literal>CR363182</" +"literal>. As with the other patch this can be requested through the BEA " +"support." msgstr "" +"Questo problema è comparso una volta applicata la patch <literal>CR327275</" +"literal> alla 10.0.MP1. Questo nuovo errore è stato confermato da BEA che ha " +"creato una patch apposita per la 10.0.MP1. Questa patch viene identificata " +"sia come <literal>CR370259</literal> che come <literal>CR363182</literal>. " +"Come l'altra, anche questa può essere richiesta al supporto BEA." #. Tag: para #: Weblogic.xml:351 #, no-c-format -msgid "This issue causes certain EJB methods to be incorrectly left out of Weblogic's generated internal stub classes. This results in the following error messages during deployment." +msgid "" +"This issue causes certain EJB methods to be incorrectly left out of " +"Weblogic's generated internal stub classes. This results in the following " +"error messages during deployment." msgstr "" +"Questo difetto fa in modo che certi metodi EJB erroneamente non vengano " +"inseriti nelle classi stub interne di Weblogic. Questo da luogo ai seguenti " +"messaggi di errore durante il deploy." #. Tag: programlisting #: Weblogic.xml:358 #, no-c-format msgid "" -"<![CDATA[<<Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:\n" -"<Compilation Error> TimerServiceDispatcher_qzt5w2_Impl.java: The type TimerServiceDispatcher_qzt5w2_Impl must implement the inherited abstract method TimerServiceDispatcher_qzt5w2_Intf.scheduleTimedEvent(String, Schedule, Object[])\n" -"<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type mismatch: cannot convert from Object to Timer\n" -"<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type mismatch: cannot convert from Object to Timer> \n" -"<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1223409267344' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(jboss-seam.jar)]]>" +"<![CDATA[<<Error> <EJB> <BEA-012036> <Compiling generated EJB classes " +"produced the following Java compiler error message:\n" +"<Compilation Error> TimerServiceDispatcher_qzt5w2_Impl.java: The type " +"TimerServiceDispatcher_qzt5w2_Impl must implement the inherited abstract " +"method TimerServiceDispatcher_qzt5w2_Intf.scheduleTimedEvent(String, " +"Schedule, Object[])\n" +"<Compilation Error> " +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type " +"mismatch: cannot convert from Object to Timer\n" +"<Compilation Error> " +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type " +"mismatch: cannot convert from Object to Timer> \n" +"<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of " +"deployment request with ID '1223409267344' for task '0'. Error is: 'weblogic." +"application.ModuleException: Exception preparing module: EJBModule(jboss-" +"seam.jar)]]>" msgstr "" -"<![CDATA[<<Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:\n" -"<Compilation Error> TimerServiceDispatcher_qzt5w2_Impl.java: The type TimerServiceDispatcher_qzt5w2_Impl must implement the inherited abstract method TimerServiceDispatcher_qzt5w2_Intf.scheduleTimedEvent(String, Schedule, Object[])\n" -"<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type mismatch: cannot convert from Object to Timer\n" -"<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type mismatch: cannot convert from Object to Timer> \n" -"<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1223409267344' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(jboss-seam.jar)]]>" +"<![CDATA[<<Error> <EJB> <BEA-012036> <Compiling generated EJB classes " +"produced the following Java compiler error message:\n" +"<Compilation Error> TimerServiceDispatcher_qzt5w2_Impl.java: The type " +"TimerServiceDispatcher_qzt5w2_Impl must implement the inherited abstract " +"method TimerServiceDispatcher_qzt5w2_Intf.scheduleTimedEvent(String, " +"Schedule, Object[])\n" +"<Compilation Error> " +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type " +"mismatch: cannot convert from Object to Timer\n" +"<Compilation Error> " +"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java: Type " +"mismatch: cannot convert from Object to Timer> \n" +"<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of " +"deployment request with ID '1223409267344' for task '0'. Error is: 'weblogic." +"application.ModuleException: Exception preparing module: EJBModule(jboss-" +"seam.jar)]]>" #. Tag: para #: Weblogic.xml:360 #, no-c-format -msgid "It appears that when Weblogic 10.3 was released the neglected to include this fix!! This means that Weblogic 10.0.MP1 with patches will function correctly, but 10.3 will still require the special Seam jar described below. Not all users have seen this and there may be certain combinations of OS/JRE that do not see this, however is has been seen many times. Hopefully Oracle/BEA will release an updated patch for this issue on 10.3. When they do we will update this reference guide as needed." +msgid "" +"It appears that when Weblogic 10.3 was released the neglected to include " +"this fix!! This means that Weblogic 10.0.MP1 with patches will function " +"correctly, but 10.3 will still require the special Seam jar described below. " +"Not all users have seen this and there may be certain combinations of OS/JRE " +"that do not see this, however is has been seen many times. Hopefully Oracle/" +"BEA will release an updated patch for this issue on 10.3. When they do we " +"will update this reference guide as needed." msgstr "" +"Sembra che, quando Weblogic 10.3 è stato rilasciato, si siano dimenticati di " +"includere questa correzione!! Ciò significa che Weblogic 10.0.MP1 con le " +"patch funzionerà correttamente, ma che la 10.3 richiederà ancora il jar " +"speciale di Seam descritto sotto. Non tutti gli utenti si sono imbattuti in " +"questo problema, e vi possono essere delle combinazioni OS/JRE in cui non si " +"verifica, comunque è stato avvistato molte volte. Si spera che Oracle/BEA " +"rilasceranno una patch aggiornata per questo difetto per la 10.3. Quando lo " +"faranno aggiorneremo queste istruzioni come necessario." #. Tag: para #: Weblogic.xml:372 #, no-c-format -msgid "So that Seam's users can deploy an EJB application to Weblogic a special Weblogic specific jar has been created, starting with Seam 2.0.2.CR2. It is located in the <literal>$SEAM/lib/interop</literal> directory and is called <literal>jboss-seam-wls-compatible.jar</literal> . The only difference between this jar and the <literal>jboss-seam.jar</literal> is that it does not contain the <literal>TimerServiceDispatcher</literal> EJB. To use this jar simply rename the <literal>jboss-seam-wls-compatible.jar</literal> to <literal>jboss-seam.jar</literal> and replace the original in your applications <literal>EAR</literal> file. The <literal>jee5/booking</literal> example demonstrates this. Obviously with this jar you will not be able to use the <literal>TimerServiceDispatcher</literal> functionality." +msgid "" +"So that Seam's users can deploy an EJB application to Weblogic a special " +"Weblogic specific jar has been created, starting with Seam 2.0.2.CR2. It is " +"located in the <literal>$SEAM/lib/interop</literal> directory and is called " +"<literal>jboss-seam-wls-compatible.jar</literal> . The only difference " +"between this jar and the <literal>jboss-seam.jar</literal> is that it does " +"not contain the <literal>TimerServiceDispatcher</literal> EJB. To use this " +"jar simply rename the <literal>jboss-seam-wls-compatible.jar</literal> to " +"<literal>jboss-seam.jar</literal> and replace the original in your " +"applications <literal>EAR</literal> file. The <literal>jee5/booking</" +"literal> example demonstrates this. Obviously with this jar you will not be " +"able to use the <literal>TimerServiceDispatcher</literal> functionality." msgstr "" +"In modo che gli utilizzatori di Seam possano fare il deploy di " +"un'applicazione EJB su Weblogic, a partire da Seam 2.0.2.CR2, è stato creato " +"un jar speciale apposta per Weblogic. Si trova nella directory <literal>" +"$SEAM/lib/interop</literal> e si chiama <literal>jboss-seam-wls-compatible." +"jar</literal>. L'unica differenza tra questo jar e <literal>jboss-seam.jar</" +"literal> è che il primo non contiene l'EJB <literal>TimerServiceDispatcher</" +"literal>. Per usarlo basta cambiarne il nome in <literal>jboss-seam.jar</" +"literal> e sostituire il <literal>jboss-seam.jar</literal> originale nel " +"file <literal>EAR</literal> dell'applicazione. L'esempio <literal>jee5/" +"booking</literal> ne fornisce una dimostrazione. Ovviamente con questo jar " +"non sarà possibile usare le funzionalità di <literal>TimerServiceDispatcher</" +"literal>." #. Tag: title #: Weblogic.xml:399 #, no-c-format msgid "Getting the <literal>jee5/booking</literal> Working" -msgstr "" +msgstr "Far funzionare l'esempio <literal>jee5/booking</literal>" #. Tag: para #: Weblogic.xml:400 #, no-c-format -msgid "In this section we will go over the steps needed to get the <literal>jee5/booking</literal> example to up and running." +msgid "" +"In this section we will go over the steps needed to get the <literal>jee5/" +"booking</literal> example to up and running." msgstr "" +"In questa sezione passeremo in rassegna i passi necessari a preparare e far " +"funzionare l'esempio <literal>jee5/booking</literal>." #. Tag: title #: Weblogic.xml:404 #, no-c-format msgid "Setting up the hsql datasource" -msgstr "" +msgstr "Configurare il datasource hsql" #. Tag: para #: Weblogic.xml:405 #, no-c-format -msgid "This example uses the in memory hypersonic database, and the correct data source needs to be set up. The admin console uses a wizard like set of pages to configure it." +msgid "" +"This example uses the in memory hypersonic database, and the correct data " +"source needs to be set up. The admin console uses a wizard like set of pages " +"to configure it." msgstr "" +"Questo esempio usa il database hypersonic residente in memoria, e bisogna " +"allestire il datasource in modo corretto. Per configurarlo la console di " +"amministrazione si basa su un insieme di pagine in stile wizard." #. Tag: para #: Weblogic.xml:411 #, no-c-format -msgid "Copy <literal>hsqldb.jar</literal> to the Weblogic domain's shared library directory: <literal> cp $SEAM_HOME/lib/hsqldb.jar $BEA_HOME/user_projects/domains/seam_examples/lib </literal>" +msgid "" +"Copy <literal>hsqldb.jar</literal> to the Weblogic domain's shared library " +"directory: <literal> cp $SEAM_HOME/lib/hsqldb.jar $BEA_HOME/user_projects/" +"domains/seam_examples/lib </literal>" msgstr "" +"Bisogna copiare <literal>hsqldb.jar</literal> nella directory delle librerie " +"condivise del dominio Weblogic: <literal> cp $SEAM_HOME/lib/hsqldb.jar " +"$BEA_HOME/user_projects/domains/seam_examples/lib </literal>" #. Tag: para #: Weblogic.xml:419 #, no-c-format -msgid "Start up the server and navigate to the administration console following" -msgstr "" +msgid "" +"Start up the server and navigate to the administration console following" +msgstr "Avviate il server e navigate alla console amministrativa seguendo" #. Tag: para #: Weblogic.xml:424 #, no-c-format -msgid "On the left side tree navigate <literal>seam_examples - Services- JDBC - Data Sources</literal>." +msgid "" +"On the left side tree navigate <literal>seam_examples - Services- JDBC - " +"Data Sources</literal>." msgstr "" +"Nell'albero di sinistra navigate a <literal>seam_examples - Services- JDBC - " +"Data Sources</literal>." #. Tag: para #: Weblogic.xml:429 #, no-c-format -msgid "Then select the <literal>New</literal> button at the top of the data source table" +msgid "" +"Then select the <literal>New</literal> button at the top of the data source " +"table" msgstr "" +"Poi selezionate il bottone <literal>New</literal> in cima alla tabella dei " +"data source" #. Tag: para #: Weblogic.xml:433 #, no-c-format msgid "Fill in the following:" -msgstr "" +msgstr "Compilate come segue:" #. Tag: para #: Weblogic.xml:436 @@ -566,27 +971,33 @@ #, no-c-format msgid "Database Type and Driver: <literal>other</literal>" msgstr "" +"Database Type and Driver (Tipo di database e driver): <literal>other</" +"literal>" #. Tag: para -#: Weblogic.xml:450 -#: Weblogic.xml:484 -#: Weblogic.xml:514 +#: Weblogic.xml:450 Weblogic.xml:484 Weblogic.xml:514 #, no-c-format msgid "Select <literal>Next</literal> button" -msgstr "Selezionare il pulsante <literal>Next</literal>" +msgstr "Premete il pulsante <literal>Next</literal>" #. Tag: para #: Weblogic.xml:456 #, no-c-format -msgid "Select <literal>Next</literal> button on the <literal>Transaction Options</literal> page" -msgstr "Selezionare il pulsante <literal>Next</literal> nella pagina <literal>Transaction Options</literal>" +msgid "" +"Select <literal>Next</literal> button on the <literal>Transaction Options</" +"literal> page" +msgstr "" +"Cliccate il pulsante <literal>Next</literal> della pagina " +"<literal>Transaction Options</literal>" #. Tag: para -#: Weblogic.xml:461 -#: Weblogic.xml:490 +#: Weblogic.xml:461 Weblogic.xml:490 #, no-c-format -msgid "Fill in the following on the <literal>Connection Properties</literal> page:" +msgid "" +"Fill in the following on the <literal>Connection Properties</literal> page:" msgstr "" +"Compilate i campi seguenti della pagina <literal>Connection Properties</" +"literal> (Proprietà di connessione):" #. Tag: para #: Weblogic.xml:465 @@ -613,8 +1024,7 @@ msgstr "Username: <literal>sa</literal> saranno campi password vuoti." #. Tag: para -#: Weblogic.xml:481 -#: Weblogic.xml:507 +#: Weblogic.xml:481 Weblogic.xml:507 #, no-c-format msgid "Password: leave empty." msgstr "Password: lasciare vuoto." @@ -641,25 +1051,33 @@ #: Weblogic.xml:510 #, no-c-format msgid "Leave the rest of the fields as is." -msgstr "" +msgstr "Lasciare il resto dei campi come sono." #. Tag: para #: Weblogic.xml:520 #, no-c-format -msgid "Choose the target domain for the data source in our case the only one <literal>AdminServer</literal>. Click <literal>Next</literal>." +msgid "" +"Choose the target domain for the data source in our case the only one " +"<literal>AdminServer</literal>. Click <literal>Next</literal>." msgstr "" +"Scegliete il dominio di pertinenza del data source, nel nostro caso l'unico " +"esistente <literal>AdminServer</literal>. Premete <literal>Next</literal>." #. Tag: title #: Weblogic.xml:528 #, no-c-format msgid "Configuration and Build changes" -msgstr "" +msgstr "Configurazione e modifiche alla procedura di Build" #. Tag: para #: Weblogic.xml:529 #, no-c-format -msgid "OK - now we are ready to finally begin adjusting the seam application for deployment to the Weblogic server." +msgid "" +"OK - now we are ready to finally begin adjusting the seam application for " +"deployment to the Weblogic server." msgstr "" +"Bene - ora siamo finalmente pronti a cominciare a sistemare l'applicazione " +"Seam per essere installata sul server Weblogic." #. Tag: literal #: Weblogic.xml:536 @@ -670,8 +1088,11 @@ #. Tag: para #: Weblogic.xml:543 #, no-c-format -msgid "Change the <literal>jta-data-source</literal> to what you entered above :" +msgid "" +"Change the <literal>jta-data-source</literal> to what you entered above :" msgstr "" +"Modificate la proprietà <literal>jta-data-source</literal> in quello che " +"avete inserito sopra:" #. Tag: programlisting #: Weblogic.xml:548 @@ -687,13 +1108,13 @@ #: Weblogic.xml:551 #, no-c-format msgid "Then comment out the glassfish properties." -msgstr "" +msgstr "Poi commentate le proprietà di glassfish." #. Tag: para #: Weblogic.xml:556 #, no-c-format msgid "Then add these two properties for weblogic support." -msgstr "" +msgstr "Poi aggiungete queste due proprietà per il supporto di Weblogic." #. Tag: programlisting #: Weblogic.xml:560 @@ -703,14 +1124,16 @@ "<property name=\"hibernate.dialect\" \n" " value=\"org.hibernate.dialect.HSQLDialect\"/>\n" "<property name=\"hibernate.transaction.manager_lookup_class\" \n" -" value=\"org.hibernate.transaction.WeblogicTransactionManagerLookup\"/>\n" +" value=\"org.hibernate.transaction." +"WeblogicTransactionManagerLookup\"/>\n" "]]>" msgstr "" "<![CDATA[\n" "<property name=\"hibernate.dialect\" \n" " value=\"org.hibernate.dialect.HSQLDialect\"/>\n" "<property name=\"hibernate.transaction.manager_lookup_class\" \n" -" value=\"org.hibernate.transaction.WeblogicTransactionManagerLookup\"/>\n" +" value=\"org.hibernate.transaction." +"WeblogicTransactionManagerLookup\"/>\n" "]]>" #. Tag: literal @@ -720,11 +1143,10 @@ msgstr "resources/META-INF/weblogic-application.xml" #. Tag: para -#: Weblogic.xml:574 -#: Weblogic.xml:639 +#: Weblogic.xml:574 Weblogic.xml:639 #, no-c-format msgid "This file needs to be created and should contain the following:" -msgstr "" +msgstr "Questo file deve essere creato e deve contenere ciò che segue:" #. Tag: programlisting #: Weblogic.xml:578 @@ -763,8 +1185,18 @@ #. Tag: para #: Weblogic.xml:581 #, no-c-format -msgid "These changes do two two different things. The first element <literal>library-ref</literal> tells weblogic that this application will be using the deployed JSF libraries. The second element <literal> prefer-application-packages </literal> tells weblogic that the <literal>antlr</literal> jars take precedence. This avoids a conflict with hibernate." +msgid "" +"These changes do two two different things. The first element " +"<literal>library-ref</literal> tells weblogic that this application will be " +"using the deployed JSF libraries. The second element <literal> prefer-" +"application-packages </literal> tells weblogic that the <literal>antlr</" +"literal> jars take precedence. This avoids a conflict with hibernate." msgstr "" +"Queste modifiche fanno due cose differenti. Il primo elemento " +"<literal>library-ref</literal> dice a weblogic che questa applicazione userà " +"le librerie JSF installate. Il secondo elemento <literal> prefer-application-" +"packages </literal> dice a weblogic che i jar <literal>antlr</literal> hanno " +"la precedenza. Questo evita conflitti con hibernate." #. Tag: literal #: Weblogic.xml:602 @@ -775,14 +1207,32 @@ #. Tag: para #: Weblogic.xml:607 #, no-c-format -msgid "The changes described here work around an issue where Weblogic is only using a single instance of the <literal>sessionBeanInterceptor</literal> for all session beans. Seam's interceptor caches and stores some component specific attributes, so when a call comes in - the interceptor is primed for a different component and an error is seen. To solve this problem you must define a separate interceptor binding for each EJB you wish to use. When you do this Weblogic will use a separate instance for each EJB." +msgid "" +"The changes described here work around an issue where Weblogic is only using " +"a single instance of the <literal>sessionBeanInterceptor</literal> for all " +"session beans. Seam's interceptor caches and stores some component specific " +"attributes, so when a call comes in - the interceptor is primed for a " +"different component and an error is seen. To solve this problem you must " +"define a separate interceptor binding for each EJB you wish to use. When you " +"do this Weblogic will use a separate instance for each EJB." msgstr "" +"Le modifiche qui descritte aggirano un problema per cui Weblogic usa una " +"sola istanza di <literal>sessionBeanInterceptor</literal> per tutti i " +"session bean. L'interceptor di Seam tiene in memoria alcuni attributi " +"specifici del componente, così che quando arriva una chiamata - " +"l'interceptor è predisposto per un diverso componente e compare un errore. " +"Per risolvere questo difetto, per ogni EJB, bisogna definire una apposita " +"associazione con un diverso interceptor (interceptor binding). Così facendo " +"Weblogic userà un'istanza separata per ciascun EJB." #. Tag: para #: Weblogic.xml:622 #, no-c-format -msgid "Modify the <literal>assembly-descriptor</literal> element to look like this:" +msgid "" +"Modify the <literal>assembly-descriptor</literal> element to look like this:" msgstr "" +"Bisogna modificare l'elemento <literal>assembly-descriptor</literal> in modo " +"che appaia così:" #. Tag: programlisting #: Weblogic.xml:627 @@ -792,31 +1242,38 @@ "<assembly-descriptor>\n" " <interceptor-binding> \n" " <ejb-name>AuthenticatorAction</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" " <interceptor-binding> \n" " <ejb-name>BookingListAction</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" " <interceptor-binding> \n" " <ejb-name>RegisterAction</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" " <interceptor-binding> \n" " <ejb-name>ChangePasswordAction</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" " <interceptor-binding> \n" " <ejb-name>HotelBookingAction</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" " <interceptor-binding> \n" " <ejb-name>HotelSearchingAction</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" " <interceptor-binding> \n" " <ejb-name>EjbSynchronizations</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 "" @@ -824,31 +1281,38 @@ "<assembly-descriptor>\n" " <interceptor-binding> \n" " <ejb-name>AuthenticatorAction</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" " <interceptor-binding> \n" " <ejb-name>BookingListAction</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" " <interceptor-binding> \n" " <ejb-name>RegisterAction</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" " <interceptor-binding> \n" " <ejb-name>ChangePasswordAction</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" " <interceptor-binding> \n" " <ejb-name>HotelBookingAction</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" " <interceptor-binding> \n" " <ejb-name>HotelSearchingAction</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" " <interceptor-binding> \n" " <ejb-name>EjbSynchronizations</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>]]>" @@ -891,24 +1355,35 @@ #. Tag: para #: Weblogic.xml:646 #, no-c-format -msgid "This file and the element <literal>library-ref</literal> tells Weblogic that this application will using the deployed JSF libraries. This is needed in both this file and the <literal> weblogic-application.xml </literal> file because both applications require access." +msgid "" +"This file and the element <literal>library-ref</literal> tells Weblogic that " +"this application will using the deployed JSF libraries. This is needed in " +"both this file and the <literal> weblogic-application.xml </literal> file " +"because both applications require access." msgstr "" +"Questo file e l'elemento <literal>library-ref</literal> dicono a Weblogic " +"che questa applicazione userà le librerie JSF installate. Ciò è necessario " +"sia in questo file che che nel file <literal> weblogic-application.xml </" +"literal> poiché entrambe le applicazioni devono accedervi." #. Tag: title #: Weblogic.xml:665 #, no-c-format msgid "Building and Deploying the Application" -msgstr "" +msgstr "Fare il build e il deploy dell'applicazione" #. Tag: para #: Weblogic.xml:666 #, no-c-format -msgid "There are some changes needed to the build script and the <literal>jboss-seam.jar</literal> then we can deploy the app." +msgid "" +"There are some changes needed to the build script and the <literal>jboss-" +"seam.jar</literal> then we can deploy the app." msgstr "" +"Bisogna fare alcune modifiche allo script di build e al jar <literal>jboss-" +"seam.jar</literal>, poi è possibile fare il deploy dell'applicazione." #. Tag: literal -#: Weblogic.xml:674 -#: Weblogic.xml:1084 +#: Weblogic.xml:674 Weblogic.xml:1084 #, no-c-format msgid "build.xml" msgstr "build.xml" @@ -916,8 +1391,12 @@ #. Tag: para #: Weblogic.xml:679 #, no-c-format -msgid "We need to add the follow so that the <literal> weblogic-application.xml </literal> will be packaged." -msgstr "Occorre aggiungere la seguente riga affinché venga impacchettato <literal> weblogic-application.xml </literal>." +msgid "" +"We need to add the follow so that the <literal> weblogic-application.xml </" +"literal> will be packaged." +msgstr "" +"Per inserire nel pacchetto <literal>weblogic-application.xml</literal> " +"dobbiamo aggiungere ciò che segue." #. Tag: programlisting #: Weblogic.xml:686 @@ -960,32 +1439,66 @@ #. Tag: para #: Weblogic.xml:700 #, no-c-format -msgid "This is the change discussed above in <xref linkend=\"weblogic-ejb-issues\"/> . There are really two options." -msgstr "Questo è il cambiamento discusso in <xref linkend=\"weblogic-ejb-issues\"/>. Ci sono due opzioni." +msgid "" +"This is the change discussed above in <xref linkend=\"weblogic-ejb-issues\"/" +"> . There are really two options." +msgstr "" +"Questa è la modifica discussa sopra in <xref linkend=\"weblogic-ejb-issues\"/" +"> . In realtà ci sono due opzioni." #. Tag: para #: Weblogic.xml:707 #, no-c-format -msgid "Rename this jar and replace the original <literal> $SEAM/lib/jboss-seam.jar </literal> file. This approach does not require any changes to the packaged <literal>EAR</literal> archive, but overwrites the original <literal>jboss-seam.jar</literal>" +msgid "" +"Rename this jar and replace the original <literal> $SEAM/lib/jboss-seam.jar " +"</literal> file. This approach does not require any changes to the packaged " +"<literal>EAR</literal> archive, but overwrites the original <literal>jboss-" +"seam.jar</literal>" msgstr "" +"Rinominate questo e jar e sostituitelo al file originale <literal> $SEAM/lib/" +"jboss-seam.jar </literal>. Questo approccio non richiede modifiche " +"dell'archivio <literal>EAR</literal>, ma sovrascrive il <literal>jboss-seam." +"jar</literal> originale." #. Tag: para #: Weblogic.xml:720 #, no-c-format -msgid "The other option is the modify the packaged <literal>EAR</literal> archive and replace the <literal>jboss-seam.jar</literal> in the archive manually. This leaves the original jar alone, but requires a manual step when ever the archive is packaged." +msgid "" +"The other option is the modify the packaged <literal>EAR</literal> archive " +"and replace the <literal>jboss-seam.jar</literal> in the archive manually. " +"This leaves the original jar alone, but requires a manual step when ever the " +"archive is packaged." msgstr "" +"L'altra opzione consiste nel modificare l'archivio <literal>EAR</literal> e " +"nel sostituire il file <literal>jboss-seam.jar</literal> dell'archivio " +"manualmente. Questo lascia il jar originale intatto, ma richiede un " +"passaggio manuale ogni volta che si crea l'archivio." #. Tag: para #: Weblogic.xml:736 #, no-c-format -msgid "Assuming that you choose the first option for handling the <literal>jboss-seam-wls-compatible.jar</literal> we can build the application by running <literal>ant archive</literal> at the base of the <literal>jee5/booking</literal> example directory." +msgid "" +"Assuming that you choose the first option for handling the <literal>jboss-" +"seam-wls-compatible.jar</literal> we can build the application by running " +"<literal>ant archive</literal> at the base of the <literal>jee5/booking</" +"literal> example directory." msgstr "" +"Supponendo di scegliere la prima opzione per gestire il <literal>jboss-seam-" +"wls-compatible.jar</literal> possiamo fare il build dell'applicazione " +"lanciando <literal>ant archive</literal> nella directory di base " +"dell'esempio <literal>jee5/booking</literal>." #. Tag: para #: Weblogic.xml:747 #, no-c-format -msgid "Because we chose to create our Weblogic domain in development mode we can deploy the application by putting the EAR file in the domains autodeploy directory." +msgid "" +"Because we chose to create our Weblogic domain in development mode we can " +"deploy the application by putting the EAR file in the domains autodeploy " +"directory." msgstr "" +"Poichè si è scelto di creare il nostro dominio Weblogic in modalità " +"sviluppo, è possibile fare il deploy dell'applicazione mettendo il file EAR " +"nella directory degli autodeply dei domini." #. Tag: programlisting #: Weblogic.xml:752 @@ -1000,68 +1513,111 @@ #. Tag: para #: Weblogic.xml:755 #, no-c-format -msgid "Check out the application at <literal>http://localhost:7001/seam-jee5/</literal>" +msgid "" +"Check out the application at <literal>http://localhost:7001/seam-jee5/</" +"literal>" msgstr "" +"Verifichiamo il funzionamento dell'applicazione all'indirizzo " +"<literal>http://localhost:7001/seam-jee5/</literal>" #. Tag: title #: Weblogic.xml:765 #, no-c-format msgid "The <literal>jpa</literal> booking example" -msgstr "" +msgstr "L'esempio booking con <literal>jpa</literal>" #. Tag: para #: Weblogic.xml:766 #, no-c-format -msgid "This is the Hotel Booking example implemented with Seam POJOs and Hibernate JPA and does not require EJB3 support to run. The example already has a breakout of configurations and build scripts for many of the common containers including Weblogic 10.X" +msgid "" +"This is the Hotel Booking example implemented with Seam POJOs and Hibernate " +"JPA and does not require EJB3 support to run. The example already has a " +"breakout of configurations and build scripts for many of the common " +"containers including Weblogic 10.X" msgstr "" +"Questo è l'esempio Hotel Booking implementato con i POJO di Seam con la JPA " +"di Hibernate e non richiede il supporto EJB3 per funzionare. L'esempio ha " +"già un insieme predisposto di configurazioni e script di build per molti dei " +"container più comuni, incluso quelli di Weblogic 10.X" #. Tag: para #: Weblogic.xml:771 #, no-c-format -msgid "First we'll build the example for Weblogic 10.x and do the needed steps to deploy. Then we'll talk about what is different between the Weblogic versions, and with the JBoss AS version." +msgid "" +"First we'll build the example for Weblogic 10.x and do the needed steps to " +"deploy. Then we'll talk about what is different between the Weblogic " +"versions, and with the JBoss AS version." msgstr "" +"Innanzitutto faremo il build dell'esempio per Weblogic 10.x e completeremo i " +"passi necessari a farne il deploy. Poi parleremo delle differenze tra le " +"diverse versioni di Weblogic, e con la versione per JBoss." #. Tag: para #: Weblogic.xml:775 #, no-c-format -msgid "Note that this example assumes that Weblogic's JSF libraries have been configured as described in <xref linkend=\"weblogic-jsf-deploy\"/>." +msgid "" +"Note that this example assumes that Weblogic's JSF libraries have been " +"configured as described in <xref linkend=\"weblogic-jsf-deploy\"/>." msgstr "" +"Sinoti che questo esempio assume che le librerie JSF di Weblogic siano state " +"configurate come descritto in <xref linkend=\"weblogic-jsf-deploy\"/>." #. Tag: title #: Weblogic.xml:779 #, no-c-format msgid "Building and deploying <literal>jpa</literal> booking example" -msgstr "" +msgstr "Build e deploy dell'esempio booking con <literal>jpa</literal>" #. Tag: para #: Weblogic.xml:785 #, no-c-format -msgid "Step one setup the datasource, step two build the app, step three deploy." +msgid "" +"Step one setup the datasource, step two build the app, step three deploy." msgstr "" +"Nel primo passo si allestisce il datasource, nel secondo si fa il build " +"dell'applicazione e nel terzo si fa il deploy." #. Tag: title #: Weblogic.xml:791 #, no-c-format msgid "Setting up the datasource" -msgstr "Configurazione del datasource" +msgstr "Predisporre il datasource" #. Tag: para #: Weblogic.xml:793 #, no-c-format -msgid "The Weblogic 10.X version of the example will use the in memory hsql database instead of the built in PointBase database. If you wish to use the PointBase database you must setup a PointBase datasource, and adjust the hibernate setting in <literal>persistence.xml</literal> to use the PointBase dialect. For reference the <literal>jpa/weblogic92</literal> example uses PointBase." +msgid "" +"The Weblogic 10.X version of the example will use the in memory hsql " +"database instead of the built in PointBase database. If you wish to use the " +"PointBase database you must setup a PointBase datasource, and adjust the " +"hibernate setting in <literal>persistence.xml</literal> to use the PointBase " +"dialect. For reference the <literal>jpa/weblogic92</literal> example uses " +"PointBase." msgstr "" +"Le versioni 10.X dell'esempio useranno il database hsql residente in memoria " +"invece del database preconfigurato PointBase. Se si vuole usare PointBase " +"bisogna predisporre un datasource per PointBase, e sistemare l'impostazione " +"relativa al dialetto di hibernate in <literal>persistence.xml</literal> in " +"modo da utilizzare quello di PointBase. Come riferimento, l'esempio " +"<literal>jpa/weblogic92</literal> usa PointBase." #. Tag: para #: Weblogic.xml:804 #, no-c-format -msgid "Configuring the datasource is very similar to the jee5 <xref linkend=\"weblogic-hsql-jee5-ds\"/> . Follow the steps in that section, but use the following entries where needed." +msgid "" +"Configuring the datasource is very similar to the jee5 <xref linkend=" +"\"weblogic-hsql-jee5-ds\"/> . Follow the steps in that section, but use the " +"following entries where needed." msgstr "" +"La configurazione del datasource è molto simile a quanto descritto per j2ee5 " +"in <xref linkend=\"weblogic-hsql-jee5-ds\"/> . Seguite i passi di quella " +"sezione, ma usate le seguenti impostazioni dove necessario." #. Tag: para #: Weblogic.xml:811 #, no-c-format msgid "DataSource Name: <literal>seam-jpa-ds</literal>" -msgstr "" +msgstr "DataSource Name: <literal>seam-jpa-ds</literal>" #. Tag: para #: Weblogic.xml:817 @@ -1078,22 +1634,34 @@ #. Tag: para #: Weblogic.xml:828 #, no-c-format -msgid "Building it only requires running the correct ant command: <programlisting>ant weblogic10</programlisting> This will create a container specific distribution and exploded archive directories." +msgid "" +"Building it only requires running the correct ant command: " +"<programlisting>ant weblogic10</programlisting> This will create a container " +"specific distribution and exploded archive directories." msgstr "" +"Il build dell'esempio richiede di lanciare il comando ant corretto: " +"<programlisting>ant weblogic10</programlisting>. Questo creerà una " +"distribuzione e una struttura di directory d'archivio specifici per il " +"container." #. Tag: title -#: Weblogic.xml:838 -#: Weblogic.xml:1259 +#: Weblogic.xml:838 Weblogic.xml:1259 #, no-c-format msgid "Deploying the example" msgstr "Deploy dell'esempio" #. Tag: para -#: Weblogic.xml:840 -#: Weblogic.xml:1261 +#: Weblogic.xml:840 Weblogic.xml:1261 #, no-c-format -msgid "When we installed Weblogic following <xref linkend=\"weblogic-domain\"/> we chose to have the domain in development mode. This means to deploy the application all we need to do is copy it into the autodeploy directory." +msgid "" +"When we installed Weblogic following <xref linkend=\"weblogic-domain\"/> we " +"chose to have the domain in development mode. This means to deploy the " +"application all we need to do is copy it into the autodeploy directory." msgstr "" +"Quando Weblogic è stato installato seguendo <xref linkend=\"weblogic-domain" +"\"/>, abbiamo scelto di far operare il dominio in modalità sviluppo. Ciò " +"significa che per fare il deploy basta copiare l'applicazione nella " +"directory di autodeploy." #. Tag: programlisting #: Weblogic.xml:848 @@ -1108,32 +1676,57 @@ #. Tag: para #: Weblogic.xml:850 #, no-c-format -msgid "Check out the application at the following <literal>http://localhost:7001/jboss-seam-jpa/</literal> ." +msgid "" +"Check out the application at the following <literal>http://localhost:7001/" +"jboss-seam-jpa/</literal> ." msgstr "" +"Verifichiamo il funzionamento all'indirizzo <literal>http://localhost:7001/" +"jboss-seam-jpa/</literal> ." #. Tag: title #: Weblogic.xml:858 #, no-c-format msgid "What's different with Weblogic 10.x" -msgstr "" +msgstr "Differenze con Weblogic 10.x" #. Tag: para #: Weblogic.xml:861 #, no-c-format -msgid "Between the the Weblogic 10.x and 9.2 examples there are several differences:" +msgid "" +"Between the the Weblogic 10.x and 9.2 examples there are several differences:" msgstr "" +"Tra gli esempi per Weblogic 10.x e quelli per Weblogic 9.2 ci sono parecchie " +"differenze:" #. Tag: para #: Weblogic.xml:866 #, no-c-format -msgid "<literal>META-INF/persistence.xml</literal> — The 9.2 version is configured to use the <literal>PointBase</literal> database and a pre-installed datasource. The 10.x version uses the <literal>hsql</literal> database and a custom datasource." +msgid "" +"<literal>META-INF/persistence.xml</literal> — The 9.2 version is " +"configured to use the <literal>PointBase</literal> database and a pre-" +"installed datasource. The 10.x version uses the <literal>hsql</literal> " +"database and a custom datasource." msgstr "" +"<literal>META-INF/persistence.xml</literal> — La versione 9.2 è " +"configurata per usare il database <literal>PointBase</literal> e un " +"datasource preinstallato. La versione 10.x usa il database <literal>hsql</" +"literal> e un datasource personalizzato." #. Tag: para #: Weblogic.xml:876 #, no-c-format -msgid "<literal>WEB-INF/weblogic.xml</literal> — This file and its contents solve an issue with an older version of the <literal>ANTLR</literal> libraries that Weblogic 10.x uses internally. OC4J have the same issue as well. It also configures the application to use the shared JSF libraries that were installed above." +msgid "" +"<literal>WEB-INF/weblogic.xml</literal> — This file and its contents " +"solve an issue with an older version of the <literal>ANTLR</literal> " +"libraries that Weblogic 10.x uses internally. OC4J have the same issue as " +"well. It also configures the application to use the shared JSF libraries " +"that were installed above." msgstr "" +"<literal>WEB-INF/weblogic.xml</literal> — Questo file e il suo " +"contenuto risolvono un difetto di una vecchia versione delle librerie " +"<literal>ANTLR</literal> che Weblogic 10.x usa internamente. Anche OC4J ha " +"lo stesso difetto. Inoltre configura l'applicazione per usare le librerie " +"JSF condivise installate e configurate sopra." #. Tag: programlisting #: Weblogic.xml:886 @@ -1145,7 +1738,8 @@ "xmlns=\"http://www.bea.com/ns/weblogic/90\"\n" "xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" "xsi:schemaLocation=\"http://www.bea.com/ns/weblogic/90 \n" -" http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd\">\n" +" http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd" +"\">\n" " <library-ref>\n" " <library-name>jsf</library-name>\n" " <specification-version>1.2</specification-version>\n" @@ -1163,7 +1757,8 @@ "xmlns=\"http://www.bea.com/ns/weblogic/90\"\n" "xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n" "xsi:schemaLocation=\"http://www.bea.com/ns/weblogic/90 \n" -" http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd\">\n" +" http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd" +"\">\n" " <library-ref>\n" " <library-name>jsf</library-name>\n" " <specification-version>1.2</specification-version>\n" @@ -1178,8 +1773,16 @@ #. Tag: para #: Weblogic.xml:887 #, no-c-format -msgid "This make Weblogic use classes and libraries in the web application before other libraries in the classpath. Without this change hibernate is required to use a older, slower query factory by setting the following property in the <literal>META-INF/persistence.xml</literal> file." +msgid "" +"This make Weblogic use classes and libraries in the web application before " +"other libraries in the classpath. Without this change hibernate is required " +"to use a older, slower query factory by setting the following property in " +"the <literal>META-INF/persistence.xml</literal> file." msgstr "" +"Questo fa sì che Weblogic usi classi e librerie dell'applicazione web prima " +"delle classi e librerie del classpath. Senza questa modifica hibernate è " +"costretto ad usare una query factory più vecchia e più lenta impostando la " +"seguente proprietà del file <literal>META-INF/persistence.xml</literal>." #. Tag: programlisting #: Weblogic.xml:895 @@ -1196,8 +1799,12 @@ #. Tag: para #: Weblogic.xml:898 #, no-c-format -msgid "<literal>WEB-INF/components.xml</literal> — In the Weblogic 10.x version JPA entity transactions is enabled by adding:" +msgid "" +"<literal>WEB-INF/components.xml</literal> — In the Weblogic 10.x " +"version JPA entity transactions is enabled by adding:" msgstr "" +"<literal>WEB-INF/components.xml</literal> — In Weblogic 10.x le " +"transazioni JPA per gli entity vengono abilitate aggiungendo:" #. Tag: programlisting #: Weblogic.xml:904 @@ -1210,15 +1817,19 @@ " <transaction:entity-transaction entity-manager=\"#{em}\"/>]]>" #. Tag: para -#: Weblogic.xml:907 -#: Weblogic.xml:1172 +#: Weblogic.xml:907 Weblogic.xml:1172 #, no-c-format -msgid "<literal>WEB-INF/web.xml</literal> — Because the <literal>jsf-impl.jar</literal> is not in the <literal>WAR</literal> this listener need to be configured :" +msgid "" +"<literal>WEB-INF/web.xml</literal> — Because the <literal>jsf-impl." +"jar</literal> is not in the <literal>WAR</literal> this listener need to be " +"configured :" msgstr "" +"<literal>WEB-INF/web.xml</literal> — Poiché il file <literal>jsf-impl." +"jar</literal> non si trova nel <literal>WAR</literal> bisogna configurare " +"questo listener:" #. Tag: programlisting -#: Weblogic.xml:912 -#: Weblogic.xml:1180 +#: Weblogic.xml:912 Weblogic.xml:1180 #, no-c-format msgid "" "<![CDATA[\n" @@ -1234,14 +1845,22 @@ #. Tag: para #: Weblogic.xml:917 #, no-c-format -msgid "Between the Weblogic 10.x version and the JBoss version there are more changes. Here is the rundown:" +msgid "" +"Between the Weblogic 10.x version and the JBoss version there are more " +"changes. Here is the rundown:" msgstr "" +"Tra la versione per Weblogic 10.x e la versione per JBoss ci sono ulteriori " +"modifiche. Eccole di seguito:" #. Tag: para #: Weblogic.xml:922 #, no-c-format -msgid "<literal>META-INF/persistence.xml</literal> — Except for datasource name the Weblogic version sets:" +msgid "" +"<literal>META-INF/persistence.xml</literal> — Except for datasource " +"name the Weblogic version sets:" msgstr "" +"<literal>META-INF/persistence.xml</literal> — Tranne che per il nome " +"del datasource la versione Weblogic è come segue:" #. Tag: programlisting #: Weblogic.xml:927 @@ -1258,14 +1877,20 @@ #. Tag: para #: Weblogic.xml:930 #, no-c-format -msgid "<literal>WEB-INF/lib</literal> — The Weblogic version requires several library packages because they are not included as they are with JBoss AS. These are primarily for hibernate, and its dependencies." +msgid "" +"<literal>WEB-INF/lib</literal> — The Weblogic version requires several " +"library packages because they are not included as they are with JBoss AS. " +"These are primarily for hibernate, and its dependencies." msgstr "" +"<literal>WEB-INF/lib</literal> — La versione Weblogic richiede " +"parecchie librerie poiché esse non sono già incluse come avviene con JBoss. " +"Si tratta innanzitutto di quelle per hibernate e le sue dipendenze." #. Tag: para #: Weblogic.xml:938 #, no-c-format msgid "To use Hibernate as your JPA provider you need the following jars:" -msgstr "" +msgstr "Per usare Hibernate come provider JPA servono i jar seguenti:" #. Tag: literal #: Weblogic.xml:944 @@ -1292,8 +1917,7 @@ msgstr "hibernate-validator.jar" #. Tag: literal -#: Weblogic.xml:964 -#: Weblogic.xml:979 +#: Weblogic.xml:964 Weblogic.xml:979 #, no-c-format msgid "jboss-common-core.jar" msgstr "jboss-common-core.jar" @@ -1314,7 +1938,7 @@ #: Weblogic.xml:985 #, no-c-format msgid "Various third party jars that Weblogic needs:" -msgstr "" +msgstr "Ecco diversi jar di terze parti di cui Weblogic ha bisogno:" #. Tag: literal #: Weblogic.xml:991 @@ -1361,38 +1985,79 @@ #. Tag: title #: Weblogic.xml:1036 #, no-c-format -msgid "Deploying an application created using <literal>seam-gen</literal> on Weblogic 10.x" +msgid "" +"Deploying an application created using <literal>seam-gen</literal> on " +"Weblogic 10.x" msgstr "" +"Deploy di un'applicazione creata con <literal>seam-gen</literal> su Weblogic " +"10.x" #. Tag: para #: Weblogic.xml:1039 #, no-c-format -msgid "<literal>seam-gen</literal> is a very useful tool for developers to quickly get an application up and running, and provides a foundation to add your own functionality. Out of box <literal>seam-gen</literal> will produce applications configured to run on JBoss AS. These instructions will show the steps needed to get it to run on Weblogic." +msgid "" +"<literal>seam-gen</literal> is a very useful tool for developers to quickly " +"get an application up and running, and provides a foundation to add your own " +"functionality. Out of box <literal>seam-gen</literal> will produce " +"applications configured to run on JBoss AS. These instructions will show the " +"steps needed to get it to run on Weblogic." msgstr "" +"<literal>seam-gen</literal> è uno strumento molto utile agli sviluppatori " +"per creare e far funzionare velocemente un'applicazione e fornisce le " +"fondamenta cui aggiungere le proprie funzionalità. Di default <literal>seam-" +"gen</literal> produrrà applicazioni configurate per essere eseguite su JBoss " +"AS. Queste istruzioni mostreranno i passi necessari a farlo funzionare su " +"Weblogic" #. Tag: para #: Weblogic.xml:1045 #, no-c-format -msgid "<literal>seam-gen</literal> was build for simplicity so, as you can imagine, deploying an application generated by <literal>seam-gen</literal> to Weblogic 10.x is not too hard. Basically it consists of updating or removing some configuration files, and adding dependent jars that Weblogic 10.x does not ship with." +msgid "" +"<literal>seam-gen</literal> was build for simplicity so, as you can imagine, " +"deploying an application generated by <literal>seam-gen</literal> to " +"Weblogic 10.x is not too hard. Basically it consists of updating or removing " +"some configuration files, and adding dependent jars that Weblogic 10.x does " +"not ship with." msgstr "" +"<literal>seam-gen</literal> è stato realizzato per essere semplice così, " +"come si può immaginare, il deploy di un'applicazione generata da " +"<literal>seam-gen</literal> in Weblogic 10.x non è troppo difficile. " +"Sostanzialmente consiste nell'aggiornamento o nell'eliminazione di alcuni " +"file di configurazione e nell'aggiunta dei jar delle dipendenze di cui " +"Weblogic 10.x non è dotata." #. Tag: para #: Weblogic.xml:1052 #, no-c-format -msgid "This example will cover the basic <literal>seam-gen WAR</literal> deployment. This will demonstrate Seam POJO components, Hibernate JPA, Facelets, Drools security, RichFaces, and a configurable dataSource." +msgid "" +"This example will cover the basic <literal>seam-gen WAR</literal> " +"deployment. This will demonstrate Seam POJO components, Hibernate JPA, " +"Facelets, Drools security, RichFaces, and a configurable dataSource." msgstr "" +"Questo esempio illustrerà il deploy <literal>seam-gen WAR</literal> di base. " +"Mostrerà i componenti POJO di Seam, la JPA di Hibernate, i Facelets, la " +"sicurezza di Drools, le RichFaces, e un datasource configurabile." #. Tag: title #: Weblogic.xml:1058 #, no-c-format msgid "Running <literal>seam-gen</literal> setup" -msgstr "" +msgstr "Eseguire il setup di <literal>seam-gen</literal>" #. Tag: para #: Weblogic.xml:1060 #, no-c-format -msgid "The first thing we need to do it tell <literal>seam-gen</literal> about the project we want to make. This is done by running <literal>./seam setup</literal> in the base directory of the Seam distribution. Note the paths here are my own, feel free to change for you environment." +msgid "" +"The first thing we need to do it tell <literal>seam-gen</literal> about the " +"project we want to make. This is done by running <literal>./seam setup</" +"literal> in the base directory of the Seam distribution. Note the paths here " +"are my own, feel free to change for you environment." msgstr "" +"La prima cosa da fare è dare a <literal>seam-gen</literal> le informazioni " +"riguardanti il progetto da creare. A questo scopo occorre eseguire " +"<literal>./seam setup</literal> nella directory di base della distribuzione " +"di Seam. Si noti che qui i percorsi sono i nostri e devono essere " +"liberamente adattati al vostro ambiente." #. Tag: programlisting #: Weblogic.xml:1066 @@ -1405,59 +2070,76 @@ "\n" "setup:\n" " [echo] Welcome to seam-gen :-)\n" -" [input] Enter your Java project workspace (the directory that contains your \n" +" [input] Enter your Java project workspace (the directory that contains " +"your \n" "Seam projects) [C:/Projects] [C:/Projects]\n" "/home/jbalunas/workspace\n" -" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] \n" +" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3." +"GA] \n" "[C:/Program Files/jboss-4.2.3.GA]\n" "/jboss/apps/jboss-4.2.3.GA\n" " [input] Enter the project name [myproject] [myproject]\n" "weblogic-example\n" " [echo] Accepted project name as: weblogic_example\n" -" [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky]\n" +" [input] Select a RichFaces skin (not applicable if using ICEFaces) " +"[blueSky]\n" " ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n" "\n" -" [input] Is this project deployed as an EAR (with EJB components) or a WAR \n" +" [input] Is this project deployed as an EAR (with EJB components) or a " +"WAR \n" "(with no EJB support) [ear] ([ear], war, )\n" "war\n" -" [input] Enter the Java package name for your session beans [org.jboss.seam.\n" +" [input] Enter the Java package name for your session beans [org.jboss." +"seam.\n" "tutorial.weblogic.action] [org.jboss.seam.tutorial.weblogic.action]\n" "org.jboss.seam.tutorial.weblogic.action\n" -" [input] Enter the Java package name for your entity beans [org.jboss.seam.\n" +" [input] Enter the Java package name for your entity beans [org.jboss." +"seam.\n" "tutorial.weblogic.model] [org.jboss.seam.tutorial.weblogic.model]\n" "org.jboss.seam.tutorial.weblogic.model\n" -" [input] Enter the Java package name for your test cases [org.jboss.seam.\n" -"tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action.test]\n" +" [input] Enter the Java package name for your test cases [org.jboss." +"seam.\n" +"tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action." +"test]\n" "org.jboss.seam.tutorial.weblogic.test\n" -" [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle,\n" +" [input] What kind of database are you using? [hsql] ([hsql], mysql, " +"oracle,\n" " postgres, mssql, db2, sybase, enterprisedb, h2)\n" "\n" " [input] Enter the Hibernate dialect for your database [org.hibernate.\n" "dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect]\n" "\n" -" [input] Enter the filesystem path to the JDBC driver jar [/tmp/seamlib/hsqldb.jar] \n" +" [input] Enter the filesystem path to the JDBC driver jar [/tmp/seamlib/" +"hsqldb.jar] \n" "[/tmp/seam/lib/hsqldb.jar]\n" "\n" -" [input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver] \n" +" [input] Enter JDBC driver class for your database [org.hsqldb." +"jdbcDriver] \n" " [org.hsqldb.jdbcDriver]\n" "\n" -" [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:hsqldb:.]\n" +" [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:" +"hsqldb:.]\n" "\n" " [input] Enter database username [sa] [sa]\n" "\n" " [input] Enter database password [] []\n" "\n" -" [input] Enter the database schema name (it is OK to leave this blank) [] []\n" +" [input] Enter the database schema name (it is OK to leave this blank) [] " +"[]\n" "\n" -" [input] Enter the database catalog name (it is OK to leave this blank) [] []\n" +" [input] Enter the database catalog name (it is OK to leave this blank) " +"[] []\n" "\n" -" [input] Are you working with tables that already exist in the database? [n] \n" +" [input] Are you working with tables that already exist in the database? " +"[n] \n" " (y, [n], )\n" "\n" -" [input] Do you want to drop and recreate the database tables and data in \n" +" [input] Do you want to drop and recreate the database tables and data " +"in \n" "import.sql each time you deploy? [n] (y, [n], )\n" "\n" -" [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] []\n" +" [input] Enter your ICEfaces home directory (leave blank to omit " +"ICEfaces) [] []\n" "\n" "[propertyfile] Creating new property file: \n" "/rhdev/projects/jboss-seam/cvs-head/jboss-seam/seam-gen/build.properties\n" @@ -1474,59 +2156,76 @@ "\n" "setup:\n" " [echo] Welcome to seam-gen :-)\n" -" [input] Enter your Java project workspace (the directory that contains your \n" +" [input] Enter your Java project workspace (the directory that contains " +"your \n" "Seam projects) [C:/Projects] [C:/Projects]\n" "/home/jbalunas/workspace\n" -" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] \n" +" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3." +"GA] \n" "[C:/Program Files/jboss-4.2.3.GA]\n" "/jboss/apps/jboss-4.2.3.GA\n" " [input] Enter the project name [myproject] [myproject]\n" "weblogic-example\n" " [echo] Accepted project name as: weblogic_example\n" -" [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky]\n" +" [input] Select a RichFaces skin (not applicable if using ICEFaces) " +"[blueSky]\n" " ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n" "\n" -" [input] Is this project deployed as an EAR (with EJB components) or a WAR \n" +" [input] Is this project deployed as an EAR (with EJB components) or a " +"WAR \n" "(with no EJB support) [ear] ([ear], war, )\n" "war\n" -" [input] Enter the Java package name for your session beans [org.jboss.seam.\n" +" [input] Enter the Java package name for your session beans [org.jboss." +"seam.\n" "tutorial.weblogic.action] [org.jboss.seam.tutorial.weblogic.action]\n" "org.jboss.seam.tutorial.weblogic.action\n" -" [input] Enter the Java package name for your entity beans [org.jboss.seam.\n" +" [input] Enter the Java package name for your entity beans [org.jboss." +"seam.\n" "tutorial.weblogic.model] [org.jboss.seam.tutorial.weblogic.model]\n" "org.jboss.seam.tutorial.weblogic.model\n" -" [input] Enter the Java package name for your test cases [org.jboss.seam.\n" -"tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action.test]\n" +" [input] Enter the Java package name for your test cases [org.jboss." +"seam.\n" +"tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action." +"test]\n" "org.jboss.seam.tutorial.weblogic.test\n" -" [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle,\n" +" [input] What kind of database are you using? [hsql] ([hsql], mysql, " +"oracle,\n" " postgres, mssql, db2, sybase, enterprisedb, h2)\n" "\n" " [input] Enter the Hibernate dialect for your database [org.hibernate.\n" "dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect]\n" "\n" -" [input] Enter the filesystem path to the JDBC driver jar [/tmp/seamlib/hsqldb.jar] \n" +" [input] Enter the filesystem path to the JDBC driver jar [/tmp/seamlib/" +"hsqldb.jar] \n" "[/tmp/seam/lib/hsqldb.jar]\n" "\n" -" [input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver] \n" +" [input] Enter JDBC driver class for your database [org.hsqldb." +"jdbcDriver] \n" " [org.hsqldb.jdbcDriver]\n" "\n" -" [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:hsqldb:.]\n" +" [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:" +"hsqldb:.]\n" "\n" " [input] Enter database username [sa] [sa]\n" "\n" " [input] Enter database password [] []\n" "\n" -" [input] Enter the database schema name (it is OK to leave this blank) [] []\n" +" [input] Enter the database schema name (it is OK to leave this blank) [] " +"[]\n" "\n" -" [input] Enter the database catalog name (it is OK to leave this blank) [] []\n" +" [input] Enter the database catalog name (it is OK to leave this blank) " +"[] []\n" "\n" -" [input] Are you working with tables that already exist in the database? [n] \n" +" [input] Are you working with tables that already exist in the database? " +"[n] \n" " (y, [n], )\n" "\n" -" [input] Do you want to drop and recreate the database tables and data in \n" +" [input] Do you want to drop and recreate the database tables and data " +"in \n" "import.sql each time you deploy? [n] (y, [n], )\n" "\n" -" [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] []\n" +" [input] Enter your ICEfaces home directory (leave blank to omit " +"ICEfaces) [] []\n" "\n" "[propertyfile] Creating new property file: \n" "/rhdev/projects/jboss-seam/cvs-head/jboss-seam/seam-gen/build.properties\n" @@ -1539,38 +2238,52 @@ #. Tag: para #: Weblogic.xml:1068 #, no-c-format -msgid "Type <literal>./seam new-project</literal> to create your project and <literal>cd /home/jbalunas/workspace/weblogic_example</literal> to see the newly created project." +msgid "" +"Type <literal>./seam new-project</literal> to create your project and " +"<literal>cd /home/jbalunas/workspace/weblogic_example</literal> to see the " +"newly created project." msgstr "" +"Digitate <literal>./seam new-project</literal> per creare il progetto e " +"<literal>cd /home/jbalunas/workspace/weblogic_example</literal> per vedere " +"il progetto appena creato." #. Tag: title #: Weblogic.xml:1075 #, no-c-format msgid "What to change for Weblogic 10.X" -msgstr "" +msgstr "Cosa cambiare per Weblogic 10.X" #. Tag: para #: Weblogic.xml:1076 #, no-c-format -msgid "First we change and delete some configuration files, then we update the libraries that are deployed with the application." +msgid "" +"First we change and delete some configuration files, then we update the " +"libraries that are deployed with the application." msgstr "" +"Innanzitutto bisogna modificare ed eliminare dei file di configurazione, poi " +"bisogna aggiornare le librerie che sono installate insieme all'applicazione." #. Tag: title #: Weblogic.xml:1081 #, no-c-format msgid "Configuration file changes" -msgstr "" +msgstr "Modiche dei file di configurazione" #. Tag: para #: Weblogic.xml:1089 #, no-c-format msgid "Change the default target to <literal>archive</literal>." -msgstr "" +msgstr "Modificate il target di default in <literal>archive</literal>." #. Tag: programlisting #: Weblogic.xml:1092 #, no-c-format -msgid "<![CDATA[<project name=\"weblogic_example\" default=\"archive\" basedir=\".\">]]>" -msgstr "<![CDATA[<project name=\"weblogic_example\" default=\"archive\" basedir=\".\">]]>" +msgid "" +"<![CDATA[<project name=\"weblogic_example\" default=\"archive\" basedir=\"." +"\">]]>" +msgstr "" +"<![CDATA[<project name=\"weblogic_example\" default=\"archive\" basedir=\"." +"\">]]>" #. Tag: literal #: Weblogic.xml:1099 @@ -1581,30 +2294,44 @@ #. Tag: para #: Weblogic.xml:1104 #, no-c-format -msgid "Alter the <literal>jta-data-source</literal> to be <literal>seam-gen-ds</literal> (and use this as the <literal>jndi-name</literal> when creating the data source in Weblogic's admin console)" +msgid "" +"Alter the <literal>jta-data-source</literal> to be <literal>seam-gen-ds</" +"literal> (and use this as the <literal>jndi-name</literal> when creating the " +"data source in Weblogic's admin console)" msgstr "" +"Cambiate <literal>jta-data-source</literal> in <literal>seam-gen-ds</" +"literal> (e usatelo come <literal>jndi-name</literal> all'atto della " +"creazione del datasource nella console amministrativa di Weblogic)" #. Tag: para #: Weblogic.xml:1113 #, no-c-format -msgid "Change the transaction type to <literal>RESOURCE_LOCAL</literal> so that we can use JPA transactions." +msgid "" +"Change the transaction type to <literal>RESOURCE_LOCAL</literal> so that we " +"can use JPA transactions." msgstr "" +"Modificate il tipo di transazione in <literal>RESOURCE_LOCAL</literal> in " +"modo da poter usare le transazioni JPA." #. Tag: programlisting #: Weblogic.xml:1118 #, no-c-format msgid "" "<![CDATA[\n" -"<persistence-unit name=\"weblogic_example\" transaction-type=\"RESOURCE_LOCAL\">]]>" +"<persistence-unit name=\"weblogic_example\" transaction-type=\"RESOURCE_LOCAL" +"\">]]>" msgstr "" "<![CDATA[\n" -"<persistence-unit name=\"weblogic_example\" transaction-type=\"RESOURCE_LOCAL\">]]>" +"<persistence-unit name=\"weblogic_example\" transaction-type=\"RESOURCE_LOCAL" +"\">]]>" #. Tag: para #: Weblogic.xml:1121 #, no-c-format msgid "Add/modify the properties below for Weblogic support:" msgstr "" +"Per il supporto di Weblogic bisogna aggiungere/modificare le seguenti " +"proprietà:" #. Tag: programlisting #: Weblogic.xml:1125 @@ -1625,8 +2352,13 @@ #. Tag: para #: Weblogic.xml:1128 #, no-c-format -msgid "You'll need to alter <literal>persistence-prod.xml</literal> as well if you want to deploy to Weblogic using the prod profile." +msgid "" +"You'll need to alter <literal>persistence-prod.xml</literal> as well if you " +"want to deploy to Weblogic using the prod profile." msgstr "" +"Bisognerà anche aggiornare <literal>persistence-prod.xml</literal> se si " +"vuole fare il deploy in Weblogic usando il profilo prod (profilo di " +"produzione)." #. Tag: literal #: Weblogic.xml:1138 @@ -1637,8 +2369,12 @@ #. Tag: para #: Weblogic.xml:1141 #, no-c-format -msgid "You will need to create this file and populate it following <xref linkend=\"weblogic.xml\"/>." +msgid "" +"You will need to create this file and populate it following <xref linkend=" +"\"weblogic.xml\"/>." msgstr "" +"Bisogna creare questo file e popolarlo come in <xref linkend=\"weblogic.xml" +"\"/>." #. Tag: literal #: Weblogic.xml:1148 @@ -1649,32 +2385,50 @@ #. Tag: para #: Weblogic.xml:1153 #, no-c-format -msgid "We want to use JPA transactions so we need to add the following to let Seam know." +msgid "" +"We want to use JPA transactions so we need to add the following to let Seam " +"know." msgstr "" +"Vogliamo usare le transazioni JPA, quindi dobbiamo aggiungere quanto segue " +"in modo che Seam ne sia informato." #. Tag: programlisting #: Weblogic.xml:1157 #, 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 #: Weblogic.xml:1158 #, no-c-format -msgid "You will also need to add the transaction namespace and schema location to the top of the document." +msgid "" +"You will also need to add the transaction namespace and schema location to " +"the top of the document." msgstr "" +"Bisogna aggiungere anche il namespace delle transazioni e la posizione dello " +"schema in cima al documento." #. Tag: programlisting #: Weblogic.xml:1163 #, no-c-format -msgid "<![CDATA[xmlns:transaction=\"http://jboss.com/products/seam/transaction\"]]>" -msgstr "<![CDATA[xmlns:transaction=\"http://jboss.com/products/seam/transaction\"]]>" +msgid "" +"<![CDATA[xmlns:transaction=\"http://jboss.com/products/seam/transaction\"]]>" +msgstr "" +"<![CDATA[xmlns:transaction=\"http://jboss.com/products/seam/transaction\"]]>" #. Tag: programlisting #: Weblogic.xml:1164 #, no-c-format -msgid "<![CDATA[http://jboss.com/products/seam/transaction http://jboss.com/products/seam/transaction-2.1.xsd]]>" -msgstr "<![CDATA[http://jboss.com/products/seam/transaction http://jboss.com/products/seam/transaction-2.1.xsd]]>" +msgid "" +"<![CDATA[http://jboss.com/products/seam/transaction http://jboss.com/" +"products/seam/transaction-2.1.xsd]]>" +msgstr "" +"<![CDATA[http://jboss.com/products/seam/transaction http://jboss.com/" +"products/seam/transaction-2.1.xsd]]>" #. Tag: literal #: Weblogic.xml:1169 @@ -1691,8 +2445,13 @@ #. Tag: para #: Weblogic.xml:1190 #, no-c-format -msgid "You can delete this file as we aren't deploying to JBoss AS ( <literal>jboss-app.xml</literal> is used to enable classloading isolation in JBoss AS)" +msgid "" +"You can delete this file as we aren't deploying to JBoss AS ( <literal>jboss-" +"app.xml</literal> is used to enable classloading isolation in JBoss AS)" msgstr "" +"E' possibile eliminare questo file dal momento che non si sta per fare il " +"deploy su JBoss AS ( <literal>jboss-app.xml</literal> è usato per abilitare " +"l'isolamento del classloading in JBoss AS)" #. Tag: literal #: Weblogic.xml:1200 @@ -1703,26 +2462,46 @@ #. Tag: para #: Weblogic.xml:1203 #, no-c-format -msgid "You can delete these files as we aren't deploying to JBoss AS. These files define datasources in JBoss AS, in Weblogic we will use the administration console." +msgid "" +"You can delete these files as we aren't deploying to JBoss AS. These files " +"define datasources in JBoss AS, in Weblogic we will use the administration " +"console." msgstr "" +"E' possibile eliminare questi file poiché non si sta per fare il deploy in " +"JBoss AS. Questi file definiscono i datasource di JBoss, mentre per Weblogic " +"useremo la console amministrativa." #. Tag: title #: Weblogic.xml:1212 #, no-c-format msgid "Library changes" -msgstr "" +msgstr "Modifiche delle librerie" #. Tag: para #: Weblogic.xml:1213 #, no-c-format -msgid "The <literal>seam-gen</literal> application has very similar library dependencies as the <literal>jpa</literal> example above. See <xref linkend=\"weblogic-jpa-diff\"/>. Below is the changes that are needed to get them in this application." +msgid "" +"The <literal>seam-gen</literal> application has very similar library " +"dependencies as the <literal>jpa</literal> example above. See <xref linkend=" +"\"weblogic-jpa-diff\"/>. Below is the changes that are needed to get them in " +"this application." msgstr "" +"L'applicazione <literal>seam-gen</literal> ha dipendendenze delle librerie " +"molto simili a quelle dell'esempio <literal>jpa</literal> visto sopra. Si " +"veda <xref linkend=\"weblogic-jpa-diff\"/>. Sotto sono riportati i " +"cambiamenti necessari a realizzare tali dipendenze in questa applicazione." #. Tag: para #: Weblogic.xml:1221 #, no-c-format -msgid "build.xml — Now we need to adjust the <literal>build.xml</literal>. Find the target <literal>war</literal> and add the following to the end of the target." +msgid "" +"build.xml — Now we need to adjust the <literal>build.xml</literal>. " +"Find the target <literal>war</literal> and add the following to the end of " +"the target." msgstr "" +"build.xml — Ora dobbiamo sistemare il file <literal>build.xml</" +"literal>. Trovate il target <literal>war</literal> e aggiungete quanto segue " +"in fondo al target." #. Tag: programlisting #: Weblogic.xml:1225 @@ -1774,25 +2553,35 @@ #: Weblogic.xml:1232 #, no-c-format msgid "Building and Deploying your application" -msgstr "" +msgstr "Build e deploy dell'applicazione" #. Tag: para #: Weblogic.xml:1233 #, no-c-format -msgid "All that's left is deploying the application. This involves setting up a data source, building the app, and deploying it." +msgid "" +"All that's left is deploying the application. This involves setting up a " +"data source, building the app, and deploying it." msgstr "" +"Rimane solo il deploy dell'applicazione. Questo equivale a preparare il " +"datasource e fare il build e il deploy dell'applicazione." #. Tag: title #: Weblogic.xml:1238 #, no-c-format msgid "Setting up the data source" -msgstr "" +msgstr "Allestire il datasource" #. Tag: para #: Weblogic.xml:1239 #, no-c-format -msgid "Configuring the datasource is very similar to the jee5 <xref linkend=\"weblogic-hsql-jee5-ds\"/>. Except for what is listed here follow that instruction from the link." +msgid "" +"Configuring the datasource is very similar to the jee5 <xref linkend=" +"\"weblogic-hsql-jee5-ds\"/>. Except for what is listed here follow that " +"instruction from the link." msgstr "" +"La configurazione del datasource è molto simile a quella jee5 di <xref " +"linkend=\"weblogic-hsql-jee5-ds\"/>. Tranne per quanto qui indicato seguite " +"le istruzioni del link." #. Tag: para #: Weblogic.xml:1244 @@ -1810,23 +2599,34 @@ #: Weblogic.xml:1254 #, no-c-format msgid "Building the application" -msgstr "" +msgstr "Build dell'applicazione" #. Tag: para #: Weblogic.xml:1255 #, no-c-format -msgid "This is as easy as typing <literal>ant</literal> in the projects base directory." +msgid "" +"This is as easy as typing <literal>ant</literal> in the projects base " +"directory." msgstr "" +"Questo è facile quanto digitare <literal>ant</literal> nella directory di " +"base dei progetti." #. Tag: programlisting #: Weblogic.xml:1267 #, no-c-format -msgid "cp ./dist/weblogic_example.war /jboss/apps/bea/user_projects/domains/seam_examples/autodeploy" -msgstr "cp ./dist/weblogic_example.war /jboss/apps/bea/user_projects/domains/seam_examples/autodeploy" +msgid "" +"cp ./dist/weblogic_example.war /jboss/apps/bea/user_projects/domains/" +"seam_examples/autodeploy" +msgstr "" +"cp ./dist/weblogic_example.war /jboss/apps/bea/user_projects/domains/" +"seam_examples/autodeploy" #. Tag: para #: Weblogic.xml:1269 #, no-c-format -msgid "Check out the application at the following <literal>http://localhost:7001/weblogic_example/</literal>. ." +msgid "" +"Check out the application at the following <literal>http://localhost:7001/" +"weblogic_example/</literal>. ." msgstr "" - +"Verificate il funzionamento dell'applicazione all'indirizzo <literal>http://" +"localhost:7001/weblogic_example/</literal>." Modified: tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Websphere.po =================================================================== --- tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Websphere.po 2009-06-01 11:24:41 UTC (rev 11063) +++ tags/JBoss_Seam_2_1_2/doc/Seam_Reference_Guide/it-IT/Websphere.po 2009-06-01 17:17:12 UTC (rev 11064) @@ -6,7 +6,7 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-02-01 21:20+0000\n" -"PO-Revision-Date: 2009-02-07 21:28+0100\n" +"PO-Revision-Date: 2009-06-01 00:21+0100\n" "Last-Translator: Nicola Benaglia <nico.benaz(a)gmail.com>\n" "Language-Team: none\n" "MIME-Version: 1.0\n" @@ -17,80 +17,80 @@ #: Websphere.xml:2 #, no-c-format msgid "Seam on IBM's Websphere AS" -msgstr "" +msgstr "Seam su Websphere AS di IBM" #. Tag: para #: Websphere.xml:4 #, no-c-format msgid "Websphere AS V7 is IBM's application server offering. This release is fully Java EE 5 certified." -msgstr "" +msgstr "Websphere AS V7 è l'application server di IBM. Questa release è pienamente certificata Java EE 5." #. Tag: para #: Websphere.xml:7 #, no-c-format msgid "First we will go over some basic information about the Websphere AS environment that we used for these examples. We will go over the details of those steps with the JEE5 booking example. We will also deploy the JPA example application." -msgstr "" +msgstr "Innanzitutto procediamo con alcune informazioni base sull'ambiente Websphere AS che useremo negli esempi. Andremo a fondo nei dettagli con l'esempio JEE5 Prenotazione. Procederemo anche nel deploy di un'applicazione d'esempio JPA." #. Tag: title #: Websphere.xml:13 #, no-c-format msgid "Websphere AS environment and deployment information" -msgstr "" +msgstr "Informazioni sull'ambiente ed il deploy in Websphere AS" #. Tag: para #: Websphere.xml:15 #, no-c-format msgid "Websphere AS is a commercial product and so we will not discuss the details of its installation other than to say follow the directions provided by your particular installation type and license. This section will detail the exact server versions used, installation tips, and some custom properties that are needed for all of the examples." -msgstr "" +msgstr "Websphere AS è un prodotto commerciale e quindi non si discuteranno i dettagli della sua installazione, basta dire di seguire le istruzioni fornite dal particolare tipo di installazione e dalla licenza. Questa sezione dettaglierà le versioni del server, i suggerimenti sull'installazione ed alcune proprietà specifiche necessarie negli esempi." #. Tag: title #: Websphere.xml:23 #, no-c-format msgid "Installation versions" -msgstr "" +msgstr "Versioni delle installazioni" #. Tag: para #: Websphere.xml:24 #, no-c-format msgid "All of the examples and information in this chapter are based on the version V7 of Websphere AS at the time of this writing." -msgstr "" +msgstr "Tutti gli esempi e le informazioni in questo capitolo sono basate sulla versione V7 di Websphere AS al momento della scrittura." #. Tag: ulink #: Websphere.xml:29 #, no-c-format msgid "Websphere Application Server V7" -msgstr "" +msgstr "Websphere Application Server V7" #. Tag: para #: Websphere.xml:34 #, no-c-format msgid "After installing Websphere AS, create server profile with Profile Management Tool, if you didn't create profile in installation process." -msgstr "" +msgstr "Dopo l'installazione di Websphere AS, creare il profile del server con il Profile Management Tool, qualora non si sia creato il profile in fase di installazione." #. Tag: title #: Websphere.xml:42 #, no-c-format msgid "The <literal>jee5/booking</literal> example" -msgstr "" +msgstr "L'esempio <literal>jee5/booking</literal>" #. Tag: para #: Websphere.xml:44 #, no-c-format msgid "The <literal>jee5/booking</literal> example is based on the Hotel Booking example (which runs on JBoss AS). Out of the box it is designed to run on Glassfish, but with the steps below it can be deployed to Websphere. It is located in the <literal>$SEAM_DIST/examples/jee5/booking</literal> directory." -msgstr "" +msgstr "L'esempio <literal>jee5/booking</literal> è basato sull'esempio PrenotazioneHotel (che gira su JBoss AS). E' stato progettato per girare anche su Glassfish, ma con i passi descritti sotto può essere deployato in Websphere. E' collocato nella directory <literal>$SEAM_DIST/examples/jee5/booking</literal>." #. Tag: title #: Websphere.xml:52 #: Websphere.xml:710 #, no-c-format msgid "<title>Configuration file changes</title>" -msgstr "" +msgstr "<title>Cambiamenti al file di configurazione</title>" #. Tag: para #: Websphere.xml:54 #, no-c-format msgid "Below are the configuration file changes that are need to the base example." -msgstr "" +msgstr "Sotto sono riportate le modifiche al file di configurazione necessarie all'esempio base." #. Tag: literal #: Websphere.xml:60 @@ -103,7 +103,7 @@ #: Websphere.xml:63 #, no-c-format msgid "We need to change the way that we look up EJBs for WAS. We need to remove the <literal>/local</literal> from the end of the <literal>jndi-pattern</literal> attribute. It should look like this:" -msgstr "" +msgstr "Occorre cambiare il modo di ricerca EJB per WAS. Bisogna rimuovere <literal>/local</literal> dalla fine dell'attributo <literal>jndi-pattern</literal>. Dovrebbe apparire così:" #. Tag: programlisting #: Websphere.xml:70 @@ -127,7 +127,7 @@ #: Websphere.xml:79 #, no-c-format msgid "We need to replace the /local string from <literal>ejb-ref-name</literal>. See at the following final code:" -msgstr "" +msgstr "Sostituire la stringa /local da <literal>ejb-ref-name</literal>. Vedere il seguente codice finale:" #. Tag: programlisting #: Websphere.xml:82 @@ -172,7 +172,7 @@ #: Websphere.xml:91 #, no-c-format msgid "We have to make some changes to the EJB references in the <literal>web.xml</literal>. These changes are what will allow WAS to bind automatically the EJB3 references in the web module to the the actual EJB3 beans in the EAR module. Replace all of the /local strings in <literal>ejb-local-refs</literal> when the values below." -msgstr "" +msgstr "Occorre apportare alcumi cambiamenti ai riferimenti EJB in <literal>web.xml</literal>. Queste modifiche consentono a WAS di associare automaticamente i riferimenti EJB3 nel modulo web ai bean EJB3 nel modulo EAR. Sostituire tutte le stringhe /local in <literal>ejb-local-refs</literal>." #. Tag: programlisting #: Websphere.xml:100 @@ -270,7 +270,7 @@ #: Websphere.xml:102 #, no-c-format msgid "Note also that <literal>EjbSynchronizations</literal> is a built-in Seam EJB and not part of the Hotel Booking example. This means that if your application's <literal>components.xml</literal> specifies <literal>transaction:ejb-transaction</literal>, then you must include:" -msgstr "" +msgstr "Si noti che <literal>EjbSynchronizations</literal> è un EJB predefinito in Seam e non è parte dell'esempio Prenotazione Hotel. Questo significa che se <literal>components.xml</literal> specifica <literal>transaction:ejb-transaction</literal>, allora occorre includere:" #. Tag: programlisting #: Websphere.xml:107 @@ -296,13 +296,13 @@ #: Websphere.xml:108 #, no-c-format msgid "in your web.xml. If you don't include it, you'll get the following error:" -msgstr "" +msgstr "in web.xml. Se non viene incluso, si ottiene il seguente errore:" #. Tag: programlisting #: Websphere.xml:109 #, no-c-format msgid "Name comp/env/myapp/EjbSynchronizations not found in context java:" -msgstr "" +msgstr "Name comp/env/myapp/EjbSynchronizations not found in context java:" #. Tag: literal #: Websphere.xml:114 @@ -314,7 +314,7 @@ #: Websphere.xml:117 #, no-c-format msgid "For this example we will be using the default datasource that comes with WAS. To do this change the <literal>jta-data-source</literal> element:" -msgstr "" +msgstr "Per questo esempio useremo il datasource di default che è presente in WAS. Cambiare l'elemento <literal>jta-data-source</literal>:" #. Tag: programlisting #: Websphere.xml:120 @@ -332,7 +332,7 @@ #: Websphere.xml:121 #, no-c-format msgid "Then we need to adjust some of the hibernate properties. First comment out the Glassfish properties. Next you need to add/change the properties:" -msgstr "" +msgstr "Poi occorre sistemare alcune proprietà Hibernate. Innanzitutto commentare le proprietà Glassfish. Poi occorre aggiungere/modificare le proprietà:" #. Tag: programlisting #: Websphere.xml:126 @@ -360,13 +360,13 @@ #: Websphere.xml:130 #, no-c-format msgid "<literal>hibernate.transaction.manager_lookup_class</literal> — Standard Hibernate transaction manager property for WAS 6.X and 7" -msgstr "" +msgstr "<literal>hibernate.transaction.manager_lookup_class</literal> — proprietà del gestore di transazioni standard Hibernate per WAS 6.X e 7" #. Tag: para #: Websphere.xml:136 #, no-c-format msgid "<literal>hibernate.transaction.flush_before_completion</literal> — This is commented out because we want the container to manage the transactions. Also if this is set to <literal>true</literal> an exception will be thrown by WAS when the EJBContext is looked up." -msgstr "" +msgstr "<literal>hibernate.transaction.flush_before_completion</literal> — questo è commentato poiché si vuole che il container gestisce le transazioni. Inoltre se questo viene impostato a <literal>true</literal>, viene lanciata un'eccezione da WAS quando viene cercato l'EJBContext." #. Tag: programlisting #: Websphere.xml:145 @@ -382,7 +382,7 @@ #: Websphere.xml:148 #, no-c-format msgid "<literal>hibernate.dialect</literal> — From WAS 6.1.0.9 on the embedded DB was switched to the same Derby DB as is in Glassfish v2." -msgstr "" +msgstr "<literal>hibernate.dialect</literal> — a partire da WAS 6.1.0.9 l'embedded DB è stato cambiato al Derby DB come in Glassfish v2." #. Tag: literal #: Websphere.xml:158 @@ -395,7 +395,7 @@ #: Websphere.xml:161 #, no-c-format msgid "You will need to get the <literal>GlassfishDerbyDialect.java</literal> and copy it into the <literal>/src</literal> directory. The java class exists in the JPA example source directory and can be copied using the command below assuming you are in <literal>jee5/booking</literal> directory:" -msgstr "" +msgstr "Occorre prendere <literal>GlassfishDerbyDialect.java</literal> e copiarlo nella directory <literal>/src</literal>. La classe java è presente nella directory dei sorgenti dell'esempio JPA e può essere copiata usando il comando sottostante assumendo di essere nella directory <literal>jee5/booking</literal>:" #. Tag: programlisting #: Websphere.xml:169 @@ -413,19 +413,19 @@ #: Websphere.xml:170 #, no-c-format msgid "This class will be put into the <literal>jboss-seam-jee5.jar</literal> file." -msgstr "" +msgstr "Questa classe verrà messa nel file <literal>jboss-seam-jee5.jar</literal>." #. Tag: literal #: Websphere.xml:175 #, no-c-format msgid "resources/import.sql" -msgstr "" +msgstr "resources/import.sql" #. Tag: para #: Websphere.xml:178 #, no-c-format msgid "This file must also be copied from the JPA example because either the Derby DB or the dialect does not support changes to the <literal>ID</literal> column. The files are identical except for the column difference. Use the following command to make the copy" -msgstr "" +msgstr "Questo file deve essere copiato dall'esempio JPA poiché sia Derby DB od il dialetto non supportano non supportano modifiche alla colonna <literal>ID</literal>. I file sono identici tranne per questa colonna. Usare il seguente comando per eseguire la copia:" #. Tag: programlisting #: Websphere.xml:185 @@ -441,37 +441,37 @@ #: Websphere.xml:194 #, no-c-format msgid "Building the <literal>jee5/booking</literal> example" -msgstr "" +msgstr "Build dell'esempio <literal>jee5/booking</literal>" #. Tag: para #: Websphere.xml:197 #, no-c-format msgid "In order to get the changes we have made into our application we need to make some changes to the <literal>build.xml</literal>. There are also some additional jars that are required by our application in order to work with WAS. This section will cover what changes are needed to the <literal>build.xml</literal>." -msgstr "" +msgstr "Per ottenere le modifiche applicate occorre apportare dei cambiamenti a <literal>build.xml</literal>. Ci sono dei jar aggiuntivi richiesti dall'applicazione per funzionare con WAS. Questa sezione coprirà i cambiamenti da fare a <literal>build.xml</literal>." #. Tag: title #: Websphere.xml:204 #, no-c-format msgid "Library dependency changes" -msgstr "" +msgstr "Modifiche alle dipendenze di libreria" #. Tag: para #: Websphere.xml:205 #, no-c-format msgid "We remove the <literal>log4j.jar</literal> so that all of the log output from our application will be added to the WAS log. Additional steps are required to fully configure log4j and those are outside of the scope of this document." -msgstr "" +msgstr "SI rimuova <literal>log4j.jar</literal> affinché tutto l'output di log dell'applicazione venga aggiunto al log di WAS. Sono richiesti ulteriori passi per configurare log4j ma questi esulano dagli scopi di questo documento." #. Tag: title #: Websphere.xml:213 #, no-c-format msgid "Updating the <literal>build.xml</literal> file" -msgstr "" +msgstr "Aggiornamento del file <literal>build.xml</literal>" #. Tag: para #: Websphere.xml:215 #, no-c-format msgid "Add the following entry to the bottom of the <literal>build.xml</literal> file. This overrides the default fileset that is used to populate the <literal>jboss-seam-jee5.jar</literal>. :" -msgstr "" +msgstr "Aggiungere la seguente riga alla fine del file <literal>build.xml</literal>. Questa sovrascrivere il fileset di default che viene usato per popolare <literal>jboss-seam-jee5.jar</literal>:" #. Tag: programlisting #: Websphere.xml:223 @@ -497,37 +497,37 @@ #: Websphere.xml:225 #, no-c-format msgid "Now all that is left is to execute the <literal>ant archive</literal> task and the built application will be in the <literal>jee5/booking/dist</literal> directory." -msgstr "" +msgstr "Ora ciò che manca è eseguire il task <literal>ant archive</literal> ed il built dell'applicazione verrà messo nella directory <literal>jee5/booking/dist</literal>." #. Tag: title #: Websphere.xml:234 #, no-c-format msgid "Deploying the application to Websphere" -msgstr "" +msgstr "Deploy dell'applicazione in Websphere" #. Tag: para #: Websphere.xml:236 #, no-c-format msgid "So now we have everything we need in place. All that is left is to deploy it - just a few steps more." -msgstr "" +msgstr "Ora ogni cosa è al posto giusto. Ciò che manca è il deploy - qualche passo in più." #. Tag: para #: Websphere.xml:238 #, no-c-format msgid "For this we will use Websphere's administration console. As before there are some tricks and tips that must be followed." -msgstr "" +msgstr "Per questo si userà la console di amministrazione di Websphere. Come prima ecco alcuni trucchi e suggerimenti da seguire." #. Tag: para #: Websphere.xml:241 #, no-c-format msgid "The steps below are for the WAS version stated above. The ports are default values, if you changed them substitute your values." -msgstr "" +msgstr "I passi sottostanti riguardano la versione WAS dichiarata all'inizio. Le porte sono ai valori di default, se vengono cambiati occorre sostituire i valori." #. Tag: para #: Websphere.xml:245 #, no-c-format msgid "Log in to the administration console <programlisting><![CDATA[https://localhost:9043/admin]]></programlisting> or" -msgstr "" +msgstr "Fare il login nella console di amministrazione <programlisting><![CDATA[https://localhost:9043/admin]]></programlisting> oppure" #. Tag: programlisting #: Websphere.xml:250 @@ -539,26 +539,26 @@ #: Websphere.xml:254 #, no-c-format msgid "Access the <literal>Websphere enterprise applications</literal> menu option under the <literal>Applications --> Application Type</literal> left side menu." -msgstr "" +msgstr "Accedere all'opzione menu <literal>Websphere enterprise applications</literal> sotto il menu a sinistra <literal>Applications --> Application Type</literal>." #. Tag: para #: Websphere.xml:259 #, no-c-format msgid "At the top of the <literal>Enterprise Applications</literal> table select <literal>Install</literal>. Below are installation wizard pages and what needs to done on each:" -msgstr "" +msgstr "In cima alla tabella <literal>Enterprise Applications</literal> selezionare <literal>Install</literal>. Sotto sono visualizzate le pagine del wizard con ciò che va fatto su ciascuna:" #. Tag: literal #: Websphere.xml:265 #: Websphere.xml:461 #, no-c-format msgid "Preparing for the application installation" -msgstr "" +msgstr "Preparazione per l'installazione dell'applicazione" #. Tag: para #: Websphere.xml:269 #, no-c-format msgid "Browse to the <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal> file using the file upload widget." -msgstr "" +msgstr "Andare fino al file <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</literal> usando il widget di upload dei file." #. Tag: para #: Websphere.xml:275 @@ -568,309 +568,309 @@ #: Websphere.xml:496 #, no-c-format msgid "Select the <literal>Next</literal> button." -msgstr "" +msgstr "Selezionare il pulsante <literal>Next</literal>." #. Tag: para #: Websphere.xml:280 #: Websphere.xml:471 #, no-c-format msgid "Select the <literal>Fast Path</literal> button." -msgstr "" +msgstr "Selezionare il pulsante <literal>Fast Path</literal>." #. Tag: literal #: Websphere.xml:292 #, no-c-format msgid "Select installation options" -msgstr "" +msgstr "Selezionare le opzioni di installazione" #. Tag: para #: Websphere.xml:296 #, no-c-format msgid "Select the <literal>Deploy enterprise beans</literal> and <literal>Allow EJB reference targets to resolve automatically</literal> check boxes. This is needed unless you used a Websphere AS tool to package the application." -msgstr "" +msgstr "Selezionare i check box <literal>Deploy enterprise beans</literal> e <literal>Allow EJB reference targets to resolve automatically</literal>. Queso serve amenoché si usi il tool di Websphere AS per impacchettare l'applicazione." #. Tag: literal #: Websphere.xml:313 #, no-c-format msgid "Map modules to servers" -msgstr "" +msgstr "Mappare i moduli sul server" #. Tag: para #: Websphere.xml:317 #, no-c-format msgid "No changes needed here as we only have one server. Select the <literal>Next</literal> button." -msgstr "" +msgstr "Avendo un solo server non sono necessarie modifiche. Selezionare il pulsante <literal>Next</literal>." #. Tag: literal #: Websphere.xml:325 #, no-c-format msgid "Summary" -msgstr "" +msgstr "Sommario" #. Tag: para #: Websphere.xml:328 #, no-c-format msgid "No changes needed here. Select the <literal>Finish</literal> button." -msgstr "" +msgstr "Non sono necessarie modifiche. Selezionare il pulsante <literal>Finish</literal>." #. Tag: literal #: Websphere.xml:335 #, no-c-format msgid "Installation" -msgstr "" +msgstr "Installazione" #. Tag: para #: Websphere.xml:338 #, no-c-format msgid "Now you will see it installing and deploying your application." -msgstr "" +msgstr "Ora si vedra l'installazione ed il deploy dell'applicazione." #. Tag: para #: Websphere.xml:343 #, no-c-format msgid "When it finishes select the <literal>Save</literal> link and you will be returned to the <literal>Enterprise Applications</literal> table." -msgstr "" +msgstr "Quando termina selezionare il link <literal>Save</literal> e si verrà reindirizzati alla tabella <literal>Enterprise Applications</literal>." #. Tag: para #: Websphere.xml:355 #, no-c-format msgid "Now that we have our application installed we need to make some adjustments to it before we can start it:" -msgstr "" +msgstr "Ora che si è installata l'applicazione occorre fare degli aggiustamenti ad essa prima di avviarla:" #. Tag: para #: Websphere.xml:359 #, no-c-format msgid "Starting from the <literal>Enterprise Applications</literal> table select the <literal>Seam Booking</literal> link." -msgstr "" +msgstr "Partendo dalla tabella <literal>Enterprise Applications</literal> selezionare il link <literal>Seam Booking</literal>." #. Tag: para #: Websphere.xml:365 #, no-c-format msgid "Select the <literal>Manage Modules</literal> link." -msgstr "" +msgstr "Selezionare il link <literal>Manage Modules</literal>." #. Tag: para #: Websphere.xml:369 #, no-c-format msgid "Select the <literal>jboss-seam-jee5-booking.war</literal> link." -msgstr "" +msgstr "Selezionare il link <literal>jboss-seam-jee5-booking.war</literal>." #. Tag: para #: Websphere.xml:374 #, no-c-format msgid "Change the <literal>Class loader order</literal> combo box to <literal>Classes loaded with application class loader first (parent last)</literal>." -msgstr "" +msgstr "Cambiare il combo box <literal>Class loader order</literal> in <literal>Classes loaded with application class loader first (parent last)</literal>." #. Tag: para #: Websphere.xml:380 #: Websphere.xml:397 #, no-c-format msgid "Select <literal>Apply</literal> and then <literal>Save</literal> options." -msgstr "" +msgstr "Selezionare <literal>Apply</literal> poi l'opzione <literal>Save</literal>." #. Tag: para #: Websphere.xml:384 #, no-c-format msgid "Return to the <literal>Seam Booking</literal> page." -msgstr "" +msgstr "Ritornare alla pagina <literal>Seam Booking</literal>." #. Tag: para #: Websphere.xml:387 #, no-c-format msgid "On this page select the <literal>Class loading and update detection</literal> link." -msgstr "" +msgstr "Su questa pagina selezionare il link <literal>Class loading and update detection</literal>." #. Tag: para #: Websphere.xml:392 #, no-c-format msgid "Select the radio button for <literal>Classes loaded with application class loader first</literal>." -msgstr "" +msgstr "Selezionare il pulsante radio <literal>Classes loaded with application class loader first</literal>." #. Tag: para #: Websphere.xml:403 #, no-c-format msgid "To start the application return to the <literal>Enterprise Applications</literal> table and select our application in the list. Then choose the <literal>Start</literal> button at the top of the table." -msgstr "" +msgstr "Per avviare l'applicazione ritornare alla tabella <literal>Enterprise Applications</literal> e selezionare l'applicazione nella lista. Quindi scegliere il pulsante <literal>Start</literal> in cima alla tabella." #. Tag: para #: Websphere.xml:410 #, no-c-format msgid "You can now access the application at <literal>http://localhost:9080/seam-jee5-booking/index.html</literal> ." -msgstr "" +msgstr "Ora si può accedere all'applicazione all'indirizzo <literal>http://localhost:9080/seam-jee5-booking/index.html</literal>." #. Tag: title #: Websphere.xml:431 #, no-c-format msgid "The <literal>jpa</literal> booking example" -msgstr "" +msgstr "Esempio Prenotazione <literal>jpa</literal>" #. Tag: para #: Websphere.xml:432 #, no-c-format msgid "Thankfully getting the <literal>jpa</literal> example to work is much easier than the <literal>jee5</literal> example. This is the Hotel Booking example implemented in Seam POJOs and using Hibernate JPA with JPA transactions. It does not use EJB3." -msgstr "" +msgstr "Fortunatamente far funzionare l'esempio <literal>jpa</literal> è molto più semplice che per l'esempio <literal>jee5</literal>. Questo è l'esempio Prenotazione Hotel implementato in Seam POJOs usando Hibernate JPA con le transazioni JPA. Non usa EJB3." #. Tag: para #: Websphere.xml:437 #, no-c-format msgid "The example already has a breakout of configurations and build scripts for many of the common containers including Websphere." -msgstr "" +msgstr "L'esempio ha già un pò di configurazioni e build script per molti comuni container incluso Websphere." #. Tag: para #: Websphere.xml:440 #, no-c-format msgid "First thing we are going to do is build and deploy that example. Then we'll go over some key changes that we needed." -msgstr "" +msgstr "La prima cosa da fare è costruire e deployare quell'esempio. Poi verranno apportate delle modifiche chiave necessarie." #. Tag: title #: Websphere.xml:444 #, no-c-format msgid "Building the <literal>jpa</literal> example" -msgstr "" +msgstr "Build dell'esempio <literal>jpa</literal>" #. Tag: para #: Websphere.xml:445 #, no-c-format msgid "Building it only requires running the correct ant command: <programlisting>ant websphere7</programlisting> This will create container specific distribution and exploded archive directories with the <literal>websphere7</literal> label." -msgstr "" +msgstr "Il building richiede l'esecuzione del corretto comando ant: <programlisting>ant websphere7</programlisting>. Questo creerà una distribuzione specifica per il container e le directory esplose per l'archivio con etichetta <literal>websphere7</literal>." #. Tag: title #: Websphere.xml:451 #, no-c-format msgid "Deploying the <literal>jpa</literal> example" -msgstr "" +msgstr "Deploy dell'esempio <literal>jpa</literal>" #. Tag: para #: Websphere.xml:452 #, no-c-format msgid "This is similar to the <literal>jee5</literal> example at <xref linkend=\"jee5-websphere-deploy\"/>, but without so many steps." -msgstr "" +msgstr "Questo è simile all'esempio <literal>jee5</literal> all'indirizzo <xref linkend=\"jee5-websphere-deploy\"/>, ma senza molti passi." #. Tag: para #: Websphere.xml:457 #, no-c-format msgid "From the <literal>Enterprise Applications</literal> table select the <literal>Install</literal> button." -msgstr "" +msgstr "Dalla tabella <literal>Enterprise Applications</literal> selezionare il pulsante <literal>Install</literal>." #. Tag: para #: Websphere.xml:465 #, no-c-format msgid "Browse to the <literal>examples/jpa/dist-websphere7/jboss-seam-jpa.war</literal> file using the file upload widget." -msgstr "" +msgstr "Navigare fino al file <literal>examples/jpa/dist-websphere7/jboss-seam-jpa.war</literal> usando il widget per l'upload dei file." #. Tag: para #: Websphere.xml:483 #, no-c-format msgid "Select the <literal>Next</literal> button for the next three pages, no changes are needed." -msgstr "" +msgstr "Selezionare il pulsante <literal>Next</literal> per le prossime tre pagine, non servono modifiche." #. Tag: literal #: Websphere.xml:488 #, no-c-format msgid "Map context roots for Web modules" -msgstr "" +msgstr "Mappare context roots per i moduli Web" #. Tag: para #: Websphere.xml:491 #, no-c-format msgid "In the <literal>Context root</literal> text box enter <literal>jboss-seam-jpa</literal>." -msgstr "" +msgstr "Nel text box <literal>Context root</literal> inserire <literal>jboss-seam-jpa</literal>." #. Tag: para #: Websphere.xml:502 #, no-c-format msgid "<literal>Summary</literal> page" -msgstr "" +msgstr "Pagina <literal>Summario</literal>" #. Tag: para #: Websphere.xml:505 #, no-c-format msgid "Review the settings if you wish and select the <literal>Finish</literal> button to install the application. When installation finished select the <literal> Save</literal> link and you will be returned to the <literal>Enterprise Applications</literal> table." -msgstr "" +msgstr "Rivedere le impostazioni e selezionare il pulsante <literal>Finish</literal> per installre l'applicazione. Quando l'installazione è terminata selezionare il link <literal> Save</literal> e si ritornerà alla tabella <literal>Enterprise Applications</literal>." #. Tag: para #: Websphere.xml:519 #, no-c-format msgid "As with the <literal>jee5</literal> example there are some class loader changes needed before we start the application. Follow the instructions at <xref linkend=\"websphere-app-adj-after-install\"/> but exchange <literal>jboss-seam-jpa_war</literal> for <literal>Seam Booking</literal>." -msgstr "" +msgstr "Come per l'esempio <literal>jee5</literal> ci sono alcuni cambiamenti necessari al class loader prima di avviare l'applicazione. Seguire le istruzioni in <xref linkend=\"websphere-app-adj-after-install\"/> e cambiare <literal>jboss-seam-jpa_war</literal> per <literal>Seam Booking</literal>." #. Tag: para #: Websphere.xml:526 #, no-c-format msgid "Finally start the application by selecting it in the <literal>Enterprise Applications</literal> table and clicking the <literal>Start</literal> button." -msgstr "" +msgstr "Infine avviare l'applicazione selezionandola nella tabella <literal>Enterprise Applications</literal> e cliccando il pulsante <literal>Start</literal>." #. Tag: para #: Websphere.xml:532 #, no-c-format msgid "You can now access the application at the <literal>http://localhost:9080/jboss-seam-jpa/index.html</literal>." -msgstr "" +msgstr "Si può ora accedere all'applicazione all'indirizzo <literal>http://localhost:9080/jboss-seam-jpa/index.html</literal>." #. Tag: title #: Websphere.xml:540 #, no-c-format msgid "What's different for Websphere AS V7" -msgstr "" +msgstr "Cosa c'è di diverso in Websphere AS V7" #. Tag: para #: Websphere.xml:541 #, no-c-format msgid "The differences between the JPA examples that deploys to JBoss 4.2 and Websphere AS V7 are mostly expected; library and configuration file changes." -msgstr "" +msgstr "Le differenze tra gli esempi JPA che eseguono il deploy in JBoss 4.2 e Websphere AS V7 sono perlopiù attese; cambiamenti alle librerie ed al file di configurazione." #. Tag: para #: Websphere.xml:546 #, no-c-format msgid "<para>Configuration file changes</para>" -msgstr "" +msgstr "<para>Cambiamenti al file di configurazione</para>" #. Tag: para #: Websphere.xml:549 #, no-c-format msgid "<literal>META-INF/persistence.xml</literal> — the main changes here are for the datasource JNDI path, switching to the Websphere transaction manager look up class, and changing the hibernate dialect to be <literal>GlassfishDerbyDialect</literal> ." -msgstr "" +msgstr "<literal>META-INF/persistence.xml</literal> — le maggiori modifiche sono per il path JNDI del datasource, passando alla classe di ricerca del gestore di transazioni Websphere e cambiando il dialetto Hibernate a <literal>GlassfishDerbyDialect</literal>." #. Tag: para #: Websphere.xml:559 #, no-c-format msgid "<literal>WEB-INF/components.xml</literal> — the change here is <literal>jndi-pattern</literal> without /local string." -msgstr "" +msgstr "<literal>WEB-INF/components.xml</literal> — qua la modifica è <literal>jndi-pattern</literal> senza la stringa /local." #. Tag: para #: Websphere.xml:565 #, no-c-format msgid "<literal>META-INF/ejb-jar.xml</literal> — the same change in <literal>ejb-ref-name</literal>, where is replace /local string in <literal>jboss-seam-jee5/AuthenticatorAction</literal>." -msgstr "" +msgstr "<literal>META-INF/ejb-jar.xml</literal> — stessa modifica in <literal>ejb-ref-name</literal>, dove la stringa /local diventa <literal>jboss-seam-jee5/AuthenticatorAction</literal>." #. Tag: para #: Websphere.xml:572 #, no-c-format msgid "<literal>src/GlassfishDerbyDialect.java </literal> — this class is needed for the hibernate dialect change to <literal>GlassfishDerbyDialect</literal>" -msgstr "" +msgstr "<literal>src/GlassfishDerbyDialect.java </literal> — questa classe serve per la modifica del dialetto Hibernate a <literal>GlassfishDerbyDialect</literal>" #. Tag: para #: Websphere.xml:580 #, no-c-format msgid "<literal>import.sql</literal> — either for the dialect or Derby DB the <literal>ID</literal> column can not be populated by this file and was removed." -msgstr "" +msgstr "<literal>import.sql</literal> — la colonna <literal>ID</literal> sia del dialetto sia del Derby DB non può essere popolata ed è stata rimossa." #. Tag: para #: Websphere.xml:589 #, no-c-format msgid "Changes for dependent libraries" -msgstr "" +msgstr "Modifiche per le librerie dipendenti" #. Tag: para #: Websphere.xml:590 #, no-c-format msgid "The Websphere version requires several library packages because they are not included as they are with JBoss AS. These are primarily for hibernate and their dependencies. Below are listed only the additional jars needed above and beyond the JBoss <literal>JPA</literal> example." -msgstr "" +msgstr "La versione di Websphere richiede parecchi pacchetti di libreria inclusi invece in JBoss AS. Questi servono principalmente per Hibernate e le sue dipendenze. Sotto appare la lista dei jar addizionali necessari sopra e a prescindere dall'esempio JBoss <literal>JPA</literal>." #. Tag: para #: Websphere.xml:597 #, no-c-format msgid "To use Hibernate as your JPA provider you need the following jars:" -msgstr "" +msgstr "Per usare Hibernate come provider JPA occorrono i seguenti jar:" #. Tag: literal #: Websphere.xml:602 @@ -918,7 +918,7 @@ #: Websphere.xml:638 #, no-c-format msgid "Various third party jars that Websphere needs:" -msgstr "" +msgstr "Websphere richiede vari jar di Terze Parti:" #. Tag: literal #: Websphere.xml:641 @@ -960,25 +960,25 @@ #: Websphere.xml:678 #, no-c-format msgid "Deploying an application created using <literal>seam-gen</literal> on Websphere V7" -msgstr "" +msgstr "Deploy dell'applicazione creata usando <literal>seam-gen</literal> su Websphere V7" #. Tag: para #: Websphere.xml:681 #, no-c-format msgid "<literal>seam-gen</literal> is a very useful tool for developers to quickly get an application up and running, and provides a foundation to add your own functionality. Out of box <literal>seam-gen</literal> will produce applications configured to run on JBoss AS. These instructions will show the steps needed to get it to run on Websphere. As stated above in <xref linkend=\"jee5-websphere-section\"/> there are some tricky changes needed to get an EJB3 application running. This section will take you through the exact steps." -msgstr "" +msgstr "<literal>seam-gen</literal> è un tool molto utile per gli sviluppatori per ottenere velocemente applicazioni pronte per l'esecuzione e fornisce un fondamento per aggiungere proprie funzionalità. Di base <literal>seam-gen</literal> produrrà applicazioni configurate per girare su JBoss AS. Queste istruzioni mostreranno i passi necessari per farle funzionare su Websphere. Come dichiarato sopra in <xref linkend=\"jee5-websphere-section\"/> ci sono alcune modifiche sottili necessarie per avere un'applicazione EJB3 funzionante. Questa sezione mostrerà gli esatti passi da compiere." #. Tag: title #: Websphere.xml:691 #, no-c-format msgid "Running <literal>seam-gen</literal> Setup" -msgstr "" +msgstr "Eseguire il setup in <literal>seam-gen</literal>" #. Tag: para #: Websphere.xml:692 #, no-c-format msgid "The first step is setting up <literal>seam-gen</literal> to construct the base project. There are several choices made below, specifically the datasource and hibernate values that we will adjust once the project is created." -msgstr "" +msgstr "Il primo passo è impostare <literal>seam-gen</literal> per costruire il progetto base. Ci sono parecchie scelte fatte sotto, in particolar modo il datasource ed i valori Hibernate che occorre aggiustare una volta che il progetto è creato." #. Tag: programlisting #: Websphere.xml:698 @@ -1134,19 +1134,19 @@ #: Websphere.xml:700 #, no-c-format msgid "Type <literal>./seam new-project</literal> to create your project and <literal>cd /home/jbalunas/workspace/websphere_example</literal> to the newly created structure." -msgstr "" +msgstr "Digitare <literal>./seam new-project</literal> per creare il progetto e <literal>cd /home/jbalunas/workspace/websphere_example</literal> per la nuova struttura creata." #. Tag: title #: Websphere.xml:707 #, no-c-format msgid "Changes needed for deployment to Websphere" -msgstr "" +msgstr "Cambiamenti richiesti per il deploy in Websphere" #. Tag: para #: Websphere.xml:708 #, no-c-format msgid "We now need to make some changes to the generated project." -msgstr "" +msgstr "Ora serve apportare alcuni cambiamenti al progetto generato." #. Tag: literal #: Websphere.xml:714 @@ -1158,13 +1158,13 @@ #: Websphere.xml:719 #, no-c-format msgid "Alter the <literal>jta-data-source</literal> to be <literal>DefaultDatasource</literal>. We are going to be using the integrated Websphere DB." -msgstr "" +msgstr "Modificare <literal>jta-data-source</literal> in <literal>DefaultDatasource</literal>. Verrà usato il DB integrato di Websphere." #. Tag: para #: Websphere.xml:726 #, no-c-format msgid "Add or change the properties below. These are described in detail at <xref linkend=\"jee5-websphere-section\"/>:" -msgstr "" +msgstr "Aggiungere o modificare le proprietà sotto. Queste sono descritte in dettaglio in <xref linkend=\"jee5-websphere-section\"/>:" #. Tag: programlisting #: Websphere.xml:731 @@ -1194,7 +1194,7 @@ #: Websphere.xml:734 #, no-c-format msgid "Remove the JBoss AS specific method of exposing the EntityManagerFactory:" -msgstr "" +msgstr "Rimuovere i metodi specifici di JBoss AS per esporre EntityManagerFactory:" #. Tag: programlisting #: Websphere.xml:737 @@ -1212,13 +1212,13 @@ #: Websphere.xml:740 #, no-c-format msgid "You'll need to alter <literal>persistence-prod.xml</literal> as well if you want to deploy to Websphere using the prod profile." -msgstr "" +msgstr "Serve modificare <literal>persistence-prod.xml</literal> anche se si vuole eseguire il deploy in Websphere usando il profile prod." #. Tag: para #: Websphere.xml:753 #, no-c-format msgid "As with other examples we need to include this java class for DB support. It can be copied from the <literal>jpa</literal> example into the <literal>websphere_example/src</literal> directory." -msgstr "" +msgstr "Come per gli altri esempi occorre includere questa classe java per il supporto DB. Può essere copiata dall'esempio <literal>jpa</literal> nella directory <literal>websphere_example/src</literal>." #. Tag: programlisting #: Websphere.xml:759 @@ -1242,7 +1242,7 @@ #: Websphere.xml:768 #, no-c-format msgid "You can delete this file as we aren't deploying to JBoss AS ( <literal>jboss-app.xml</literal> is used to enable classloading isolation in JBoss AS)" -msgstr "" +msgstr "Si può cancellare questo file poiché non si eseguirà il deploy in JBoss AS (<literal>jboss-app.xml</literal> viene usato per abilitare l'isolamento del classloading in JBoss AS)" #. Tag: literal #: Websphere.xml:774 @@ -1254,25 +1254,25 @@ #: Websphere.xml:777 #, no-c-format msgid "You can delete these file as we aren't deploying to JBoss AS (these files define datasources in JBoss AS, we are using Websphere's default datasource)" -msgstr "" +msgstr "Si possono cancellare questi file poiché non si eseguirà il deploy in JBoss AS (questi file definiscono i datasource in JBoss AS, si userà invece il datasource di default di Websphere)" #. Tag: para #: Websphere.xml:789 #, no-c-format msgid "Enable container managed transaction integration - add the <literal> <transaction:ejb-transaction /> </literal> component, and it's namespace declaration <literal> xmlns:transaction=\"http://jboss.com/products/seam/transaction\" </literal>" -msgstr "" +msgstr "Abilitare l'integrazione delle transazioni gestite dal container - aggiungere il componente <literal><transaction:ejb-transaction /></literal> ed la sua dichiarazione di namespace <literal>xmlns:transaction=\"http://jboss.com/products/seam/transaction\"</literal>" #. Tag: para #: Websphere.xml:798 #, no-c-format msgid "Alter the <literal>jndi-pattern</literal> to <literal> java:comp/env/websphere_example/#{ejbName} </literal>" -msgstr "" +msgstr "Modificare <literal>jndi-pattern</literal> in <literal>java:comp/env/websphere_example/#{ejbName}</literal>" #. Tag: para #: Websphere.xml:804 #, no-c-format msgid "We do not need <literal>managed-persistence-context</literal> for this example and so can delete its entry." -msgstr "" +msgstr "Non serve <literal>managed-persistence-context</literal> per quest'esempio e quindi si può cancellare questa riga." #. Tag: programlisting #: Websphere.xml:810 @@ -1292,7 +1292,7 @@ #: Websphere.xml:819 #, no-c-format msgid "As with the <literal>jee5/booking</literal> example we need to add EJB references to the web.xml. These references require replacing /local string in <literal>ejb-ref-name</literal> to flag them for Websphere to perform the proper binding." -msgstr "" +msgstr "Come per l'esempio <literal>jee5/booking</literal> occorre aggiungere i riferimenti EJB a web.xml. Questi riferimenti richiedono di sostituire la stringa /local in <literal>ejb-ref-name</literal> e selezionarli affinché Websphere esegua il corretto binding." #. Tag: programlisting #: Websphere.xml:826 @@ -1328,37 +1328,37 @@ #: Websphere.xml:832 #, no-c-format msgid "Creating the <literal>AuthenticatorAction</literal> EJB" -msgstr "" +msgstr "Creazione dell'EJB <literal>AuthenticatorAction</literal>" #. Tag: para #: Websphere.xml:834 #, no-c-format msgid "We want to take the existing <literal>Authenticator</literal> Seam POJO component and create an EJB3 out of it." -msgstr "" +msgstr "Si vuole prendere il componente POJO Seam <literal>Authenticator</literal> e creare da questo un EJB3." #. Tag: para #: Websphere.xml:837 #, no-c-format msgid "Change the generated Authenticator class" -msgstr "" +msgstr "Cambiare la classe Authenticator generata" #. Tag: para #: Websphere.xml:840 #, no-c-format msgid "Rename the class to <literal>AuthenticatorAction</literal>" -msgstr "" +msgstr "Rinominare la classe in <literal>AuthenticatorAction</literal>" #. Tag: para #: Websphere.xml:844 #, no-c-format msgid "Add the <literal>@Stateless</literal> annotation to the new <literal>AuthenticatorAction</literal> class." -msgstr "" +msgstr "Aggiungere l'annotazione <literal>@Stateless</literal> alla nuova classe <literal>AuthenticatorAction</literal>." #. Tag: para #: Websphere.xml:850 #, no-c-format msgid "Create an interface called <literal>Authenticator</literal> which <literal>AuthenticatorAction</literal> implements (EJB3 requires session beans to have a local interface). Annotate the interface with <literal>@Local</literal> , and add a single method with same signature as the <literal>authenticate</literal> in <literal>AuthenticatorAction</literal> ." -msgstr "" +msgstr "Creare un'interfaccia chiamata <literal>Authenticator</literal> ed implementata da <literal>AuthenticatorAction</literal> (EJB3 richiede che i bean di sessione abbiano un'interfaccia locale). Annotare l'interfaccia con <literal>@Local</literal>, ed aggiungere un singolo metodo con la stessa firma come <literal>authenticate</literal> in <literal>AuthenticatorAction</literal>." #. Tag: programlisting #: Websphere.xml:863 @@ -1390,25 +1390,25 @@ #: Websphere.xml:869 #, no-c-format msgid "We've already added its reference to the <literal>web.xml</literal> file so are good to go." -msgstr "" +msgstr "Abbiamo già aggiunto il suo riferimento al file <literal>web.xml</literal> e quindi si può procedere." #. Tag: title #: Websphere.xml:875 #, no-c-format msgid "Extra jar dependencies and other changes to the <literal>build.xml</literal>" -msgstr "" +msgstr "Dipendenze extra ed altre modifiche a <literal>build.xml</literal>" #. Tag: para #: Websphere.xml:877 #, no-c-format msgid "This application has similar requirements as the <literal>jee5/booking</literal> example." -msgstr "" +msgstr "Quest'applicazione ha requisiti simili come nell'esempio <literal>jee5/booking</literal>." #. Tag: para #: Websphere.xml:882 #, no-c-format msgid "Change the default target to <literal>archive</literal> (we aren't going to cover automatic deployment to Websphere)." -msgstr "" +msgstr "Modificare il target di default a <literal>archive</literal> (non si tratterà il deploy automatico in Websphere)." #. Tag: programlisting #: Websphere.xml:888 @@ -1424,7 +1424,7 @@ #: Websphere.xml:892 #, no-c-format msgid "Websphere looks for the drools <literal>/security.drl</literal> file in the root of the <literal>war</literal> file instead of the root of the <literal>websphere_example.jar</literal> so we need to have the <literal>build.xml</literal> move it to the correct location at build time. The following must be added at the top of the <literal> <target name=\"war\" depends=\"compile\" description=\"Build the distribution .war file\"> </literal> target." -msgstr "" +msgstr "Websphere cerca il file drools <literal>/security.drl</literal> nella radice di file <literal>war</literal> invece che nella radice di <literal>websphere_example.jar</literal> e quindi serve spostare <literal>build.xml</literal> nella corretta posizione al momento del build. La seguente riga deve essere aggiunta in cima al target <literal> <target name=\"war\" depends=\"compile\" description=\"Build the distribution .war file\"> </literal>." #. Tag: programlisting #: Websphere.xml:903 @@ -1448,7 +1448,7 @@ #: Websphere.xml:906 #, no-c-format msgid "Now we need to get extra jars into the <literal>build.xml</literal>. Look for the <literal><fileset dir=\"${basedir}\"></literal> section of the task below. Add the new includes at the bottom of the fileset." -msgstr "" +msgstr "Ora occorre inserire i jar extra in <literal>build.xml</literal>. Cercare la sezione <literal><fileset dir=\"${basedir}\"></literal> del task sotto. Aggiungere nuovi include in fondo al fileset." #. Tag: programlisting #: Websphere.xml:914 @@ -1576,7 +1576,7 @@ #: Websphere.xml:925 #, no-c-format msgid "<literal>jboss-seam.jar</literal> - this is needed in the <literal>ear</literal> base directory." -msgstr "" +msgstr "<literal>jboss-seam.jar</literal> - questo è richiesto nella directory base <literal>ear</literal>." #. Tag: programlisting #: Websphere.xml:928 @@ -1594,7 +1594,7 @@ #: Websphere.xml:932 #, no-c-format msgid "You should end up with something like:" -msgstr "" +msgstr "Si dovrebbe terminare con qualcosa di simile a:" #. Tag: programlisting #: Websphere.xml:933 @@ -1672,23 +1672,23 @@ #: Websphere.xml:940 #, no-c-format msgid "Building and deploying the seam-gen'd application to Websphere" -msgstr "" +msgstr "Build e deploy di un'applicazione seam-gen in Websphere" #. Tag: para #: Websphere.xml:945 #, no-c-format msgid "Build your application by calling <literal>ant</literal> in the base directory of your project (ex. <literal>/home/jbalunas/workspace/websphere_example</literal> ). The target of the build will be <literal>dist/websphere_example.ear</literal> ." -msgstr "" +msgstr "Eseguire il build dell'applicazione chiamando <literal>ant</literal> nella directory base del progetto (es. <literal>/home/jbalunas/workspace/websphere_example</literal>). Il target del build sarà <literal>dist/websphere_example.ear</literal>." #. Tag: para #: Websphere.xml:954 #, no-c-format msgid "To deploy the application follow the instructions here : <xref linkend=\"jee5-websphere-deploy\"/> but use references to this project <literal>websphere_example</literal> instead of <literal>jboss-seam-jee5</literal>." -msgstr "" +msgstr "Per fare il deploy dell'applicazione seguire le istruzioni in <xref linkend=\"jee5-websphere-deploy\"/> ma usare i riferimenti a questo progetto <literal>websphere_example</literal> invece che a <literal>jboss-seam-jee5</literal>." #. Tag: para #: Websphere.xml:960 #, no-c-format msgid "Checkout the app at: <literal>http://localhost:9080/websphere_example/index.html</literal>" -msgstr "" +msgstr "Controllare l'applicazione all'indirizzo: <literal>http://localhost:9080/websphere_example/index.html</literal>"

15 years, 7 months

1
0
0 / 0

Seam SVN: r11063 - branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US.

by seam-commits＠lists.jboss.org

Author: manaRH Date: 2009-06-01 07:24:41 -0400 (Mon, 01 Jun 2009) New Revision: 11063 Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml Log: reviewed and fix some typos Modified: branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml =================================================================== --- branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml 2009-05-31 22:22:20 UTC (rev 11062) +++ branches/community/Seam_2_1/doc/Seam_Reference_Guide/en-US/ClusteringAndEJBPassivation.xml 2009-06-01 11:24:41 UTC (rev 11063) @@ -46,7 +46,7 @@ <para> But wait, there's more! Seam also offers an incredibly unique feature for clustered applications. In addition to monitoring JavaBean components, Seam ensures that managed entity instances (i.e. JPA and - Hibernate entities) don't become detatched during replication. Seam keeps a record of the entities that are + Hibernate entities) don't become detached during replication. Seam keeps a record of the entities that are loaded and automatically loads them on the secondary node. You must, however, be using a Seam-managed persistence context to get this feature. More in depth information about this feature is provided in the second half of this chapter. @@ -61,7 +61,7 @@ <title>Programming for clustering</title> <para> Any session- or conversation-scoped mutable JavaBean component that will be used in a clustered - environment must implement the <literal>Mutable</literal> interface from the Seam API. As part of the + environment must implement the <literal>org.jboss.seam.core.Mutable</literal> interface from the Seam API. As part of the contract, the component must maintain a dirty flag that is reported and reset by the <literal>clearDirty()</literal> method. Seam calls this method to determine if it is necessary to replicate the component. This avoids having to use the more cumbersome Servlet API to add and remove the @@ -82,7 +82,7 @@ </para> <note> <para> - Please note that clustering does not work with hot deployable compoennts. But then again, you shouldn't + Please note that clustering does not work with hot deployable components. But then again, you shouldn't be using hot deployable components in a non-development environment anyway. </para> </note> @@ -265,7 +265,7 @@ The MEI serves two distinct scenarios (EJB passivation and HTTP session passivation), although to accomplish the same overall goal. It ensures that throughout the life of a conversation using at least one extended persistence context, the entity instances loaded by the persistence context(s) remain managed (they do not - become detatched prematurally by a passivation event). In short, it ensures the integrity of the extended + become detached prematurally by a passivation event). In short, it ensures the integrity of the extended persistence context (and therefore its guarantees). </para> @@ -333,7 +333,7 @@ <para> Conversations were initially designed with stateful session beans (SFSBs) in mind, primarily because the EJB 3 specification designates SFSBs as hosts of the extended persistence context. Seam introduces a - compliment to the extended persistence context, known as a Seam-managed persistence context, which works + complement to the extended persistence context, known as a Seam-managed persistence context, which works around a number of limitations in the specification (complex propagation rules and lack of manual flushing). Both can be used with a SFSB. </para> @@ -354,7 +354,7 @@ individual SFSB. This process can even be disabled. However, the persistence context is not serialized (is this only true of SMPC?). In fact, what happens depends highly on the Java EE container. The spec is not very clear about this situation. Many vendors just tell you not to let it happen if you need the - guarnatees of the extended persistence context. Seam's approach is more conservative. Seam basically + guarantees of the extended persistence context. Seam's approach is more conservative. Seam basically doesn't trust the SFSB with the persistence context or the entity instances. After each invocation of the SFSB, Seam moves the reference to entity instance held by the SFSB into the current conversation (and therefore into the HTTP session), nullifying those fields on the SFSB. It then restores this

15 years, 7 months

1
0
0 / 0

← Newer
1
...
13
14
15
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

seam-commits June 2009