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