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&gt;\n&quot; "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&gt;(a)PostActivate&lt;/literal&gt;.&quot; +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&gt;(a)PostActivate&lt;/literal&gt;.&quot; #. 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... 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>&lt;distributable/></literal> as the first child element in WEB-INF/web.xml" -msgstr "Aggiungere <literal>&lt;distributable/></literal> come primo elemento figlio in WEB-INF/web.xml" +msgid "" +"Add <literal>&lt;distributable/></literal> as the first child element in WEB-" +"INF/web.xml" +msgstr "" +"Aggiungere <literal>&lt;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\">Ejb3Dis... 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\">Ejb3Dis... 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; @@ -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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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&gt;\n&quot; 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 "