[jboss-cvs] JBossAS SVN: r85753 - in projects/docs/enterprise/4.3.4/readme: es-ES and 4 other directories.

[jboss-cvs-commits at lists.jboss.org]

Author: mospina
Date: 2009-03-11 20:45:10 -0400 (Wed, 11 Mar 2009)
New Revision: 85753

Added:
   projects/docs/enterprise/4.3.4/readme/de-DE/Release_Notes_CP04.po
   projects/docs/enterprise/4.3.4/readme/de-DE/Revision_History.po
   projects/docs/enterprise/4.3.4/readme/es-ES/Release_Notes_CP04.po
   projects/docs/enterprise/4.3.4/readme/es-ES/Revision_History.po
   projects/docs/enterprise/4.3.4/readme/fr-FR/Release_Notes_CP04.po
   projects/docs/enterprise/4.3.4/readme/fr-FR/Revision_History.po
   projects/docs/enterprise/4.3.4/readme/pt-BR/Release_Notes_CP04.po
   projects/docs/enterprise/4.3.4/readme/pt-BR/Revision_History.po
   projects/docs/enterprise/4.3.4/readme/zh-CN/Release_Notes_CP04.po
   projects/docs/enterprise/4.3.4/readme/zh-CN/Revision_History.po
Modified:
   projects/docs/enterprise/4.3.4/readme/de-DE/Author_Group.po
   projects/docs/enterprise/4.3.4/readme/de-DE/Book_Info.po
   projects/docs/enterprise/4.3.4/readme/de-DE/readme.po
   projects/docs/enterprise/4.3.4/readme/es-ES/Author_Group.po
   projects/docs/enterprise/4.3.4/readme/es-ES/Book_Info.po
   projects/docs/enterprise/4.3.4/readme/es-ES/readme.po
   projects/docs/enterprise/4.3.4/readme/fr-FR/Author_Group.po
   projects/docs/enterprise/4.3.4/readme/fr-FR/Book_Info.po
   projects/docs/enterprise/4.3.4/readme/fr-FR/readme.po
   projects/docs/enterprise/4.3.4/readme/pot/Author_Group.pot
   projects/docs/enterprise/4.3.4/readme/pot/Book_Info.pot
   projects/docs/enterprise/4.3.4/readme/pot/messages.mo
   projects/docs/enterprise/4.3.4/readme/pt-BR/Author_Group.po
   projects/docs/enterprise/4.3.4/readme/pt-BR/Book_Info.po
   projects/docs/enterprise/4.3.4/readme/pt-BR/readme.po
   projects/docs/enterprise/4.3.4/readme/zh-CN/Author_Group.po
   projects/docs/enterprise/4.3.4/readme/zh-CN/Book_Info.po
   projects/docs/enterprise/4.3.4/readme/zh-CN/readme.po
Log:
PO files updated for all languages

Modified: projects/docs/enterprise/4.3.4/readme/de-DE/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/de-DE/Author_Group.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/de-DE/Author_Group.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to
+# translation of readme.po to
 # Language de-DE translations for readme package.
 #
 # Automatically generated, 2008.
 # Jasna Dimanoski <jdimanos at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-08-05 06:26+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-07 07:21+1000\n"
 "Last-Translator: Jasna Dimanoski <jdimanos at redhat.com>\n"
 "Language-Team:  <de at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -16,9 +16,10 @@
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.11.4\n"
 
-#. Tag: corpauthor
-#: Author_Group.xml:5
+#. Tag: author
+#: Author_Group.xml:6
 #, no-c-format
-msgid "Red Hat Documentation Group"
-msgstr "Red Hat Dokumentationsgruppe"
-
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/de-DE/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/de-DE/Book_Info.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/de-DE/Book_Info.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to
+# translation of readme.po to
 # Language de-DE translations for readme package.
 #
 # Automatically generated, 2008.
 # Jasna Dimanoski <jdimanos at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-08-05 06:28+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-07 07:21+1000\n"
 "Last-Translator: Jasna Dimanoski <jdimanos at redhat.com>\n"
 "Language-Team:  <de at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -18,32 +18,35 @@
 
 #. Tag: title
 #: Book_Info.xml:6
-#, no-c-format
-msgid "Release Notes"
+#, fuzzy, no-c-format
+msgid "Release Notes CP04"
 msgstr "Release Notes"
 
 #. Tag: subtitle
 #: Book_Info.xml:7
-#, no-c-format
-msgid "JBoss Enterprise Application Platform 4.3.0.CP02"
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
 msgstr "JBoss Enterprise Application Platform 4.3.0.CP02"
 
 #. Tag: para
-#: Book_Info.xml:11
-#, no-c-format
+#: Book_Info.xml:13
+#, fuzzy, no-c-format
 msgid ""
 "These release notes contain important information related to JBoss "
-"Enterprise Application Platform 4.3.0.CP02 that may not be currently "
+"Enterprise Application Platform 4.3.0.CP04 that may not be currently "
 "available in the Product Manuals. You should read these Release Notes in "
 "their entirety before installing JBoss Enterprise Application Platform 4.3.0."
-"CP02."
+"CP04."
 msgstr ""
-"Diese Release Notes enthalten wichtige Informationen zur JBoss "
-"Enterprise Application Platform 4.3.0.CP02, die momentan möglicherweise noch nicht in Produkthandbüchern verfügbar sind. Sie sollten diese Release Notes vollständig gelesen haben, ehe Sie die JBoss Enterprise Application Platform 4.3.0.CP02 installieren."
+"Diese Release Notes enthalten wichtige Informationen zur JBoss Enterprise "
+"Application Platform 4.3.0.CP02, die momentan möglicherweise noch nicht in "
+"Produkthandbüchern verfügbar sind. Sie sollten diese Release Notes "
+"vollständig gelesen haben, ehe Sie die JBoss Enterprise Application Platform "
+"4.3.0.CP02 installieren."
 
 #. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
 #, no-c-format
 msgid "&HOLDER;"
 msgstr "&HOLDER;"
-

Added: projects/docs/enterprise/4.3.4/readme/de-DE/Release_Notes_CP04.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/de-DE/Release_Notes_CP04.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/de-DE/Release_Notes_CP04.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,3084 @@
+# translation of readme.po to
+# Language de-DE translations for readme package.
+#
+# Automatically generated, 2008.
+# Jasna Dimanoski <jdimanos at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-07 07:21+1000\n"
+"Last-Translator: Jasna Dimanoski <jdimanos at redhat.com>\n"
+"Language-Team:  <de at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:9
+#, no-c-format
+msgid "Introduction"
+msgstr "Einführung"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:12
+#, no-c-format
+msgid ""
+"These release notes contain important information related to JBoss "
+"Enterprise Application Platform &VERSION;. New features, known problems, "
+"resources, and other current issues are addressed here."
+msgstr ""
+"Diese Release Notes enthalten wichtige Informationen zur JBoss Enterprise "
+"Application Platform &VERSION;. Neue Features, bekannte Probleme, Ressourcen "
+"und andere aktuellen Themen werden hier behandelt."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:16
+#, no-c-format
+msgid "Overview"
+msgstr "Übersicht"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:17
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform is the next evolutionary step in open "
+"source enterprise software. It is a powerful tool for developing rich, high "
+"performance, Web 2.0 applications on a pure Java Platform."
+msgstr ""
+"JBoss Enterprise Application Platform ist der nächste Evolutionsschritt in "
+"Open Source Enterprise Software. Sie ist ein leistungsfähiges Tool zur "
+"Entwicklung umfassender, sehr leistungsfähiger Web 2.0 Anwendungen auf einer "
+"reinen Java-Plattform."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:20
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform provides complete compatibility with "
+"existing J2EE 1.4 enterprise Java applications. At the same time, almost all "
+"the key features and components defined in the Java EE 5.0 specification are "
+"supported. So your new enterprise Java applications can take immediate "
+"advantage of the Java EE 5.0's significantly simpler POJO-based programming "
+"model."
+msgstr ""
+"JBoss Enterprise Application Platform liefert vollständige Kompatibilität "
+"mit bestehenden J2EE 1.4 Enterprise Java-Anwendungen. Gleichzeitig werden "
+"alle in der Java EE 5.0 Spezifikation definierten Schlüssel-Features und "
+"Komponenten unterstützt. Ihre neuen Enterprise Java Anwendungen können also "
+"sofort die Vorteile des wesentlich einfacheren POJO-basierten "
+"Programmiermodells von Java EE 5.0 nutzen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:23
+#, no-c-format
+msgid ""
+"Further, by integrating best-of-breed open source frameworks such as JBoss "
+"Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of "
+"innovations in the open source community. As well, JBoss Enterprise "
+"Application Platform is fully tested and supported by Red Hat, and is "
+"certified to work on many leading enterprise hardware and software products."
+msgstr ""
+"Durch Integration der besten Open-Source-Frameworks ihrer Art, wie etwa "
+"JBoss Seam, Hibernate, Tomcat und JBoss Cache nutzt die Plattform die "
+"Innovationen der Open Source Community. Die JBoss Enterprise Application "
+"Platform ist vollständig getestet und wird von Red Hat unterstützt; "
+"desweiteren ist sie für den Einsatz an vielen führenden Enterprise Hardware- "
+"und Software-Produkten zertifiziert."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:26
+#, no-c-format
+msgid ""
+"All of which means you can develop your new application taking advantage of "
+"Java EE 5.0 technologies immediately and with the confidence of knowing it "
+"will remain forward-compatible with future versions of the JBoss Platform."
+msgstr ""
+"All dies bedeutet, dass Sie Ihre neue Anwendung entwickeln und sofort die "
+"Vorteile von Java EE 5.0 Technologie nutzen können, während Sie die "
+"Gewissheit haben, dass diese mit zukünftigen Versionen der JBoss Plattform "
+"kompatibel bleibt."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:32
+#, no-c-format
+msgid "New Features in JBoss Enterprise Application Platform 4.3"
+msgstr "Neue Features in der JBoss Enterprise Application Platform 4.3"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:34 Release_Notes_CP04.xml:365
+#, no-c-format
+msgid "JBoss Messaging"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:35
+#, no-c-format
+msgid ""
+"In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
+"with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
+"messaging infrastructure for JBoss Enterprise Application Platform."
+msgstr ""
+"In JBoss Enterprise Application Platform 4.3 wurde JBoss MQ 1.3 durch JBoss "
+"Messaging 1.4 ersetzt. JBoss Messaging bietet eine sehr leistungsfähige "
+"Messaging Infrastruktur für die JBoss Enterprise Application Platform."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:40
+#, no-c-format
+msgid "JBoss Web Services 2.0.1"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:41
+#, no-c-format
+msgid ""
+"JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
+"Platform 4.3 and will now provide a complete implementation of JAX-WS."
+msgstr ""
+"Es fand ein Upgrade von JBoss Web Services zu 2.0.1 in JBoss Enterprise "
+"Application Platform 4.3 statt und bietet nun eine komplette Implementierung "
+"von JAX-WS."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:47
+#, no-c-format
+msgid "Component Versions"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:48
+#, no-c-format
+msgid ""
+"This section details the versions of the components which create the "
+"Enterprise Application Platform 4.3 that can be found in this Cumulative "
+"Patch release."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:53
+#, no-c-format
+msgid "JBoss Application Server 4.2.z"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:58
+#, no-c-format
+msgid "Hibernate Core 3.2.4.SP1.CP07"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:63
+#, no-c-format
+msgid "Hibernate Annotations 3.2.1.GA.CP03"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:68
+#, no-c-format
+msgid "Hibernate Entity Manager 3.2.1.GA_CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:73
+#, no-c-format
+msgid "JAF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:78
+#, no-c-format
+msgid "JBoss Cache 1.4.1.SP11"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:83
+#, no-c-format
+msgid "JBoss JAXR 1.2.0.SP2"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:88
+#, fuzzy, no-c-format
+msgid "JBoss Messaging 1.4.0.SP3-CP07"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:93
+#, fuzzy, no-c-format
+msgid "JBoss Remoting 2.2.2.SP11"
+msgstr "JBoss-Remoting"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:98
+#, no-c-format
+msgid "JBoss Transactions 4.2.3.SP5.CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:103
+#, fuzzy, no-c-format
+msgid "JBoss Web 2.0.0-6.CP09"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:108
+#, fuzzy, no-c-format
+msgid "JBoss Web Services 2.0.1.SP2_CP05"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:113
+#, no-c-format
+msgid "JGroups 2.4.5"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:118
+#, no-c-format
+msgid "JSF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:123
+#, no-c-format
+msgid "Seam 1.2.1.AP"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:128
+#, no-c-format
+msgid "Xalan 2.7.0.patch02"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:134
+#, no-c-format
+msgid ""
+"The Enterprise Application Platform Server has been redefined for the "
+"enterprise market to a level where direct association to a community release "
+"can no longer be drawn."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:140
+#, no-c-format
+msgid "Installation and Migration Notes"
+msgstr "Installations- und Migrationsanmerkungen"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:141
+#, no-c-format
+msgid ""
+"This section contains information related to installing or upgrading to "
+"JBoss Enterprise Application Platform version &VERSION;, including hardware "
+"and platform requirements and prerequisites."
+msgstr ""
+"Dieser Abschnitt enthält Informationen zur Installation und dem Upgrade zur "
+"JBoss Enterprise Application Platform Version &VERSION;, einschließlich "
+"Hardware- und Plattform-Anforderungen sowie Voraussetzungen."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:145
+#, no-c-format
+msgid "Installation Notes"
+msgstr "Installationshinweise"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:146
+#, fuzzy, no-c-format
+msgid ""
+"You must have adequate disk space to install JDK and JBoss Enterprise "
+"Application Platform while also allowing enough space for your applications. "
+"You must have a working installation of JDK 1.5 or 1.6. For the latest "
+"information on supported Operating System / JVM combinations, supported "
+"Database platforms and current information on the revision level of included "
+"components, please refer to <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>. Refer to the "
+"installation guide available online from <ulink url=\"http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
+"instructions to install and verify JBoss Enterprise Application Platform."
+msgstr ""
+"Sie müssen über ausreichend Platz auf der Disk verfügen, um JDK und JBoss "
+"Enterprise Application Platform zu installieren und auch für Ihre Anwendung "
+"noch genug Platz haben. Sie benötigen eine funktionierende Installation von "
+"JDK 1.5. Für aktuelle Informationen zu unterstützten Betriebssystem-/JVM-"
+"Kombinationen, unterstützten Datenbankplattformen sowie aktuellen Infos zur "
+"Revisionsebene enthaltener Komponenten, sehen Sie bitte <ulink url=\"http://"
+"www.jboss.com/products/platforms/application/testedconfigurations\">http://"
+"www.jboss.com/products/platforms/application/testedconfigurations</ulink>. "
+"Das Installationshandbuch ist online unter <ulink url=\"http://www.redhat."
+"com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat."
+"com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> verfügbar und "
+"enthält ausführliche Anleitungen zur Installation und Verifizierung der "
+"JBoss Enterprise Application Platform."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:151
+#, fuzzy, no-c-format
+msgid "Upgrading from JBoss Enterprise Application Platform 4.3.0.CP03"
+msgstr "Upgrade von JBoss Enterprise Application Platform 4.3"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:153
+#, no-c-format
+msgid "Using CSP/JON"
+msgstr "Verwendung von CSP/JON"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:154
+#, fuzzy, no-c-format
+msgid ""
+"Refer to <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
+"Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
+msgstr ""
+"Siehe <ulink url=\"https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> für Anleitungen zur Installation eines "
+"\"Cumulative Patch\"."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:164
+#, no-c-format
+msgid "Important Notes"
+msgstr "Wichtige Hinweise"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:166
+#, no-c-format
+msgid "Running the example Seam Applications"
+msgstr "Ausführen der Seam Beispielanwendungen"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:169
+#, no-c-format
+msgid ""
+"It is recommended to run the example Seam applications that are included "
+"with the documentation using the production configuration. Using another "
+"configuration may result in memory issues. Note that the default "
+"configuration for the server to start with, if no other configuration is "
+"specified, is the production configuration."
+msgstr ""
+"Es wird empfohlen, die in der Dokumentation enthaltenen Seam-"
+"Beispielanwendungen unter Verwendung der Produktionskonfiguration "
+"auszuführen. Die Verwendung einer anderen Konfiguration kann zu "
+"Speicherproblemen führen. Beachten Sie bitte, dass die Standard-"
+"Startkonfiguration des Servers die Produktionskonfiguration ist, wenn keine "
+"andere festgelegt wird."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:173
+#, no-c-format
+msgid ""
+"To avoid memory issues, adjust the memory settings before deploying the "
+"applications. You can do this by updating <literal>JAVA_OPTS</literal> "
+"settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
+"conf</filename> with these recommended values:"
+msgstr ""
+"Um Speicherprobleme zu vermeiden, passen Sie die Speichereinstellungen vor "
+"dem Deployment der Anwendungen an. Sie können dies durch ein Update der "
+"Einstellungen in der Datei <literal>JAVA_OPTS</literal> <filename>JBOSS_DIST/"
+"jboss-as/server/production/run.conf</filename> mit folgenden empfohlenen "
+"Werten tun:"
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:175
+#, no-c-format
+msgid "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+msgstr "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:178
+#, no-c-format
+msgid ""
+"Refer to the \"Seam Reference Guide\" included in the documentation set "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for "
+"important information regarding the deployment of Seam examples and detailed "
+"information on developing applications using Seam."
+msgstr ""
+"Im Seam Referenzhandbuch (\"Seam Reference Guide\") das im "
+"Dokumentationssatz eingeschlossen ist(<filename>JBOSS_DIST/doc/seam/"
+"Seam_Reference_Guide.pdf</filename>) finden Sie wichtige Informationen zum "
+"Deploment von Seam-Beispielen sowie ausführliche Informationen zur "
+"Entwicklung von Anwendungen unter Verwendung von Seam."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:186
+#, no-c-format
+msgid "Default Security Settings"
+msgstr "Standard-Sicherheitseinstellungen"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:189
+#, no-c-format
+msgid ""
+"If you are using the rpm, or the zip distribution, please note that by "
+"default, authentication is enabled and no user accounts are set up. This is "
+"done to prevent unauthorized access to various services of JBoss AS. Please "
+"refer to the Installation Guide, or see <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
+"ulink> for information on how to make the services accessible again."
+msgstr ""
+"Falls Sie die rpm oder zip-Distribution verwenden, beachten Sie bitte, dass "
+"standardmäßig die Authentifikation aktiviert ist und keine Benutzerkonten "
+"eingerichtet sind.Dies ist der Fall, um den nicht autorisierten Zugriff auf "
+"verschiedene JBoss AS Dienste zu verhindern. Informationen dazu, wie Sie "
+"diese Dienste wieder verfügbar machen, finden Sie im Installationshandbuch "
+"(Installation Guide) oder unter <ulink url=\"http://kbase.redhat.com/faq/"
+"FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</ulink>."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:194
+#, no-c-format
+msgid "Embedded Hypersonic Database"
+msgstr "Eingebettete \"Hypersonic\"-Datenbank"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:197
+#, no-c-format
+msgid ""
+"Hypersonic SQL provides default \"out of the box\" database functionality "
+"for evaluation and development use only. It is NOT recommended or supported "
+"as a production-use database. Technical support is not available for this "
+"component, and while we are happy to accept bugs filed against this "
+"component, we do not make any commitment to fix them within a specific "
+"timeframe."
+msgstr ""
+"Hypersonic SQL liefert standardmäßige und gleich einsetzbare "
+"Datenbankfunktionalität für den ausschließlichen Gebrauch bei Evaluierung "
+"und Entwicklung. Diese wird NICHT als Datenbank bei der Produktion empfohlen "
+"oder unterstützt. Für diese Komponente ist kein technischer Support "
+"verfügbar, und während wir uns über Meldungen zu Fehlern bei dieser "
+"Komponente freuen, garantieren wir keinen zeitlichen Rahmen innerhalb dessen "
+"diese behoben werden."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:202
+#, no-c-format
+msgid "Source Files"
+msgstr "Quelldateien"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:204
+#, no-c-format
+msgid "SRPMs"
+msgstr "SRPMs"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:208
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:212
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:216
+#, no-c-format
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:223
+#, no-c-format
+msgid "Source ZIP"
+msgstr "Quell-ZIP"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:228
+#, fuzzy, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP04.zip"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP02.zip"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:237
+#, no-c-format
+msgid "Product Support and License Website Links"
+msgstr "Produkt-Support und Lizenz-Website Links"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:241
+#, no-c-format
+msgid "Support Processes"
+msgstr "Support-Prozesse"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:243
+#, no-c-format
+msgid "http://www.redhat.com/support/process/"
+msgstr "http://www.redhat.com/support/process/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:248
+#, no-c-format
+msgid "Production Support Scope of Coverage"
+msgstr "Abdeckungsbereich des Produktions-Supports"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:252
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/production"
+msgstr "http://www.redhat.com/support/policy/soc/production"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:258
+#, no-c-format
+msgid "Production Support Service Level Agreement"
+msgstr "Vereinbarung zum Produktions-Support auf Service-Ebene"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:263
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/production/"
+msgstr "http://www.redhat.com/support/policy/sla/production/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:268
+#, no-c-format
+msgid "Developer Support Scope of Coverage"
+msgstr "Abdeckungsbereich des Entwickler-Supports"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:273
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/developer/"
+msgstr "http://www.redhat.com/support/policy/soc/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:278
+#, no-c-format
+msgid "Developer Support Service Level Agreement"
+msgstr "Vereinbarung zum Entwickler-Support auf Service-Ebene"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:283
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/developer/"
+msgstr "http://www.redhat.com/support/policy/sla/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:288
+#, no-c-format
+msgid "Product Update and Support Policy by Product"
+msgstr "Produkt-Aktualisierung und Support-Richtlinien nach Produkt"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:293
+#, no-c-format
+msgid "http://www.redhat.com/security/updates/jboss_notes/"
+msgstr "http://www.redhat.com/security/updates/jboss_notes/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:298
+#, no-c-format
+msgid "JBoss End User License Agreement"
+msgstr "JBoss Endnutzer-Lizenzvereinbarung"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:303
+#, no-c-format
+msgid "http://www.redhat.com/licenses/jboss_eula.html"
+msgstr "http://www.redhat.com/licenses/jboss_eula.html"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:309 Release_Notes_CP04.xml:904
+#, no-c-format
+msgid "Documentation"
+msgstr "Dokumentation"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:312
+#, no-c-format
+msgid ""
+"Refer to the index.html file in the documentation directory for a list of "
+"included documentation."
+msgstr ""
+"In der index.html-Datei im Dokumentationsverzeichnis finden Sie eine Liste "
+"der enthaltenen Dokumentation."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:315
+#, no-c-format
+msgid ""
+"In the zip distribution, documentation for the Platform and its individual "
+"components is distributed in a separate zip file, <filename>jboss-eap-docs-"
+"&lt;version&gt;.zip</filename>."
+msgstr ""
+"In der Zip-Distribution sind Dokumentation für die Plattform und deren "
+"individuelle Komponenten in einer separaten Zip-Datei <filename>jboss-eap-"
+"docs-&lt;version&gt;.zip</filename> distribuiert."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:319
+#, no-c-format
+msgid ""
+"On a Linux system, the documentation is found in two rpms that will need to "
+"be installed manually. These rpms are <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename>, and <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. For help with installing rpm packages on Red Hat "
+"Enterprise Linux, please refer to the Red Hat Knowledge base article located "
+"at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+msgstr ""
+"In einem Linux-System befindet sich die Dokumentation in zwei rpms, die "
+"manuell installiert werden müssen. Diese rpms sind <filename>jboss-seam-docs-"
+"&lt;version&gt;.noarch.rpm</filename> und <filename>rh-eap-docs-&lt;"
+"version&gt;.noarch.rpm</filename>. Hilfe zur Installation von rpm-Paketen in "
+"Red Hat Enterprise Linux finden Sie im Red Hat Knowledge Artikel unter "
+"<ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:326
+#, fuzzy, no-c-format
+msgid ""
+"<filename>Installation Guide</filename> explains how to install and verify "
+"the installation of JBoss Enterprise Application Platform using different "
+"installation modes."
+msgstr ""
+"Der <filename>Installation Guide</filename> erläutert, wie die JBoss "
+"Enterprise Application Platform mittels anderer Installationsmodi "
+"installiert und verifiziert wird."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:331
+#, no-c-format
+msgid ""
+"<filename>Getting Started</filename> details the directory structure of the "
+"platform and a quick tour of the Application Server and different "
+"configuration sets and services. Using a simple web application it "
+"illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
+"the JSF and EJB3 components."
+msgstr ""
+"<filename>Getting Started</filename> erläutert die Verzeichnisstruktur der "
+"Plattform sowie eine kurze Übersicht über der Applikationsserverund "
+"verschiedene Konfigurationseinstellungen und -dienste. Anhand einer "
+"einfachen Webanwendung werden die Verwendung der JSF-EJB3 Komponenten sowie "
+"die Verwendung von Seam zur Integration der JSF und EJB3-Komponenten "
+"dargestellt."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:336
+#, no-c-format
+msgid ""
+"<filename>Server Configuration Guide</filename> explains all administrative "
+"and configuration functions in detail."
+msgstr ""
+"Der <filename>Server Configuration Guide</filename> erläutert alle "
+"administrativen sowie Konfigurationsfunktionen im einzelnen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:342
+#, no-c-format
+msgid ""
+"Updated versions of the documentation with errata and additional "
+"information, example application code, as well as the most recent version of "
+"the release notes may be accessed via the web from <ulink url=\"http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+msgstr ""
+"Aktualisierte Versionen der Dokumentation mit Errata und "
+"zusätzlichenInformationen, Beispielen des Anwendungscode sowie der "
+"aktuellsten Version der Release Notes finden Sie im Web unter <ulink url="
+"\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"
+"\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</"
+"ulink>."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:357
+#, no-c-format
+msgid "Issues fixed in this release"
+msgstr "In dieser Release behobene Probleme"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:361
+#, no-c-format
+msgid "Following is a list of issues fixed in this release:"
+msgstr ""
+"Nachfolgend sehen Sie eine Liste von in dieser Release behobenen Problemen:"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:369
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1615\">JBPAPP-1615</"
+"ulink>: The JBoss Messaging component of the Enterprise Application Platform "
+"has been upgraded to version 1.4.0.SP3-CP07. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:374
+#, no-c-format
+msgid ""
+"There was an issue with the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method whereby the method delegates checking to "
+"the <classname>ResourceManager</classname> <varname>serverID</varname>. This "
+"instigates the case where the <methodname>xasess2.start(xid, TMJOIN)</"
+"methodname> method is called and the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method returns true but the resource manager does "
+"not hold the transaction state required to perform a <code>TMJOIN</code>. "
+"Further to this when a session is closed the <methodname>SessionAspect."
+"handleClose()</methodname> method is called, yet the <code>tx</code> was "
+"removed from the transaction manager meaning it is no longer in the "
+"<code>conn1</code> resource manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:377
+#, no-c-format
+msgid ""
+"To correct this both the <methodname>MessagingXAResource.isSameRM</"
+"methodname> method and <classname>ResourceManager</classname> have the same "
+"<code>serverID</code> and the same map of transactions, ensuring that if the "
+"<classname>ResourceManager</classname> was to ever return true, the call to "
+"<methodname>start(TMJOIN)</methodname> would correctly succeed. To note is "
+"that the transaction will rollback at completion time and any message "
+"delivered in the <code>tx</code> will be redelivered."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:382
+#, no-c-format
+msgid ""
+"Client connection parameters were not being passed to the JBoss Remoting "
+"layer, leaving parameters such as <varname>validatorPingPeriod</varname> and "
+"<varname>validatorTimeout</varname> to be used with default values within "
+"Remoting instead of the configured values. In correcting this issue, the "
+"<filename>JMSRemotingConnection.java</filename> file has been updated so "
+"that when the <methodname> client.addConnectionListener</methodname> method "
+"is called within the <methodname>addConnectionListener</methodname> and "
+"<methodname>addPlainConnectionListener</methodname> methods, it also passes "
+"the configured parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:387
+#, no-c-format
+msgid ""
+"The <literal>default</literal> profile for JBoss without any reconfiguration "
+"uses the <classname>ClusteredConnectionFactory</classname> with a non-"
+"clustered post-office, however warnings would be logged about this behavior "
+"when the log messages should be reduced from a <varname>WARN</varname> level "
+"to an <varname>INFO</varname> level. The upgrade to this version of JBoss "
+"Messaging sees this implemented within the log."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:392
+#, no-c-format
+msgid ""
+"<classname>ClusterViewUpdateTest</classname> was broken and did not work "
+"correctly in previous releases with the cause being that the expected time "
+"until failure detection for some clustering tests was too long. In order to "
+"correct this the values for <varname>validatorPingPeriod</varname> and "
+"<varname>validatorPingTimeout</varname> have been changed to be 2 seconds "
+"each, combining to 4 seconds as the total time until expected failure "
+"detection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:397
+#, no-c-format
+msgid ""
+"Client connection parameters were not passed to the JBoss Remoting layer, "
+"forcing Remoting to use default values instead of user configured values. In "
+"order to use the correct values, <filename>JMSRemotingConnection.java</"
+"filename> has been updated so that the <methodname>Client."
+"addConnectionListener</methodname> method is used with <varname>listener</"
+"varname> and <varname>serverLocator.gerParameters()</varname> as parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:402
+#, no-c-format
+msgid ""
+"Messages which are scheduled for delivery in the future were not being "
+"removed correctly when the <methodname>removeAllMessages()</methodname> "
+"method was being called, causing the messages to be re-queued as soon as the "
+"application server or queue is restarted. <filename>ChannelSupport.java</"
+"filename> has been updated to import the <filename>TimeoutExt</filename> "
+"library in order to cast the timeout value to <filename>TimeoutExt</"
+"filename> in order to obtain the reference value via the <methodname>get "
+"TimeoutTarget()</methodname> method. With this new reference value "
+"information, the scheduled messages can be correctly removed from the queue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:407
+#, no-c-format
+msgid ""
+"There was an occurrence where a user may deploy a clustered queue in a "
+"single node instead of in all the nodes and the failover process would not "
+"work because of this. When this occurred an <exceptionname>Illegal "
+"StateException</exceptionname> would be generated, however this was not "
+"considered enough of a prominent warning about not deploying clustered "
+"queues correctly. <filename>Messaging PostOffice.java</filename> has now "
+"been updated to log a warning which outlies that clustered destinations must "
+"be deployed on all nodes of a cluster, instead of generating an "
+"<exceptionname>Illegal StateException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:412
+#, no-c-format
+msgid ""
+"The <classname>Client</classname>, <classname>SecurityAspect.check()</"
+"classname> and <classname>ServerConnection FactoryEndpoint</classname> "
+"needed to be able to obtain TLC within a privileged block, otherwise an "
+"<exceptionname>Access ControlException</exceptionname> is produced. To fix "
+"this bug, the <methodname>settle</methodname>, <methodname>gettable</"
+"methodname> and other TLC methods have been set within security blocks; this "
+"prevents access denied exceptions from <classname>Client</classname>, "
+"<classname>SecurityAspect.check()</classname> and "
+"<classname>ServerConnection FactoryEndpoint</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:417
+#, no-c-format
+msgid ""
+"The logging of actions within JBoss Messaging did not include the logging of "
+"messages when they are moved to the expiry or dead letter queues as this was "
+"only logged at trace level. In order to add this enhanced level of logging, "
+"the <filename>ClientConsumer.java</filename> file has been updated to log "
+"warning messages and debug information pertaining to the move of messages to "
+"the expiry or dead letter queues; <filename>Server SessionEndpoint.java</"
+"filename> has also been updated in the same mannor."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:422
+#, no-c-format
+msgid ""
+"There was an error when a message was received under a X tx and the JBoss "
+"Messaging XAResource is prepared but not committed, a message could be "
+"received by another consumer in another transaction while the first is still "
+"in progress. The correct behavior is for JBoss Messaging to hold the message "
+"until the associated transaction is committed or rolled back, enabling "
+"duplication of message deliveries to be avoided. In the <filename>Delivery."
+"java</filename> file, messages are now marked with a boolean value detailing "
+"if they are for delivery with a X transaction and if this transaction is "
+"prepared and <filename>SimpleDelivery.java</filename> now implements this "
+"new information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:427
+#, no-c-format
+msgid ""
+"The <methodname>shutdownNow()</methodname> method was not synchronized and "
+"may cause a <exceptionname>NoSuchElementException</exceptionname> during "
+"runtime as a result. A synchronization block has been placed around the "
+"<methodname>shutdownNow()</methodname> code within "
+"<filename>OrderedExecutorFactory.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:432
+#, no-c-format
+msgid ""
+"There was an issue with the <classname>org.jboss.jms.server.messagecounter."
+"MessageCounter</classname> class not being able to be serialized as it "
+"caused an <exceptionname>UndeclaredThrowableException</exceptionname>. "
+"<filename>MessageCounter.java</filename> has been updated to now import and "
+"implement the <literal>Serializable</literal> library and be given a "
+"<varname>serialVersionUID</varname>, allowing the <classname>org.jboss.jms."
+"server.messagecounter.MessageCounter</classname> class to be serializable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:437
+#, no-c-format
+msgid ""
+"When the methods <methodname>unregisterSucker()</methodname> or "
+"<methodname>registerSucker()</methodname> was called a "
+"<exceptionname>ConcurrentModificationException</exceptionname> would be "
+"generated by the time the <literal>HashSet</literal> containing the "
+"<literal>suckers</literal> was iterated. The issue would present itself on "
+"clusters with a magnitude of nodes (for instance it appeared on a 8 node "
+"cluster but not a 4 node cluster). This bug was corrected by creating an "
+"iterator that used a private set of <literal>suckers</literal> for iteration "
+"through the <literal>HashSet</literal> of <literal>suckers</literal> in "
+"order to avoid the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:442
+#, no-c-format
+msgid ""
+"The bridge within JBoss Messaging would only retry connection creation to a "
+"remote destination after startup and if the remote provider was not "
+"available at startup, the bridge would fail to start. The <filename>Bridge."
+"java</filename> and <filename>BridgeService.java</filename> files have "
+"undergone extensive modification and now the <literal>factory</literal> is "
+"set to the <literal>bridge</literal> which undertakes the lookup itself "
+"instead of looking up the destinations."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:452
+#, fuzzy, no-c-format
+msgid "JBoss Cache"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:456
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
+"ulink>: The JBoss Cache component of the Enterprise Application Platform has "
+"been upgraded to version 1.4.1.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:461
+#, no-c-format
+msgid ""
+"The <classname>JDBCCacheLoader</classname> implementation did not work with "
+"Sybase as it would try to set a null <varname>BLOB</varname> column which is "
+"unsupported within Sybase. To correct this the <filename>JDBCCacheLoader."
+"java</filename> file has been updated so that the Sybase Driver sets a null "
+"<varname>LONGVARBINARY</varname> value, allowing the "
+"<classname>JDBCCacheLoader</classname> implementation to work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:466
+#, no-c-format
+msgid ""
+"The <classname>JDBCExtCacheLoader</classname> did not handle persistent "
+"state transfer correctly since the <methodname>JDBCExtCacheLoader.storeState"
+"()</methodname> method would use available bytes on the "
+"<classname>MarshalledValueInputStream</classname> rather than on the "
+"<classname>ByteArrayInputStream</classname> when storing the persistent "
+"state. This was an issue because the <classname>MarshalledValueInputStream</"
+"classname> always returns a null value, meaning the persistent state was "
+"never written. In fixing this issue the <filename>JDBCExtendedCacheLoader."
+"java</filename> file has been modified so that it specifies to check for "
+"available space on the <classname>ByteArrayInputStream</classname>."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:476
+#, no-c-format
+msgid "JBoss Remoting"
+msgstr "JBoss-Remoting"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:480
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
+"ulink>: The JBoss Remoting component of the Enterprise Application Platform "
+"has been upgraded to version 2.2.2.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:485
+#, no-c-format
+msgid ""
+"The <methodname>ConnectionValidator.run()</methodname> method had the "
+"ability to be called by a user before the private method "
+"<methodname>ConnectionValidator.start()</methodname> was called, resulting "
+"in the <varname>clientInvoker</varname> and <varname>timer</varname> fields "
+"being set to null and generating a <exceptionname>NullPointerException</"
+"exceptionname>. Within the <filename>ConnectionValidator.java</filename> "
+"file the fields are now checked to see if they are null upon execution of "
+"the <methodname>ConnectionValidator.run()</methodname> method, one or both "
+"are then an <exceptionname>IllegalStateException</exceptionname> is "
+"displayed to the user outlining that <methodname>ConnectionValidator.run()</"
+"methodname> should not be called directly but "
+"<methodname>addConnectionListener()</methodname> should be used instead."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:490
+#, no-c-format
+msgid ""
+"Two bugs existed within the <methodname>org.jboss.remoting.marshal."
+"MarshallerLoaderHandler.loadClassBytes()</methodname> method that prohibited "
+"remote classloading to work correctly with isolated EARs. The first was that "
+"a while loop in the code needed a break and the second was that the call to "
+"the <methodname>org.jboss.mx.loading.LoaderRepository.getCachedClass()</"
+"methodname> method should have been a general call to "
+"<methodname>LoaderRepository.loadClass()</methodname>. These two issues have "
+"been rectified with this Remoting update, allowing remote classloading to "
+"function correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:495
+#, no-c-format
+msgid ""
+"A bug existed within the Remoting component by which the RemotingClassLoader "
+"would always attempt to load a class over the network first if remote "
+"classloading was enabled, leading to conflicts if the class was available "
+"locally before. The code has been corrected to check locally first before "
+"looking remotely."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:500
+#, no-c-format
+msgid ""
+"The <classname>ServerInvokerCallbackHandler</classname> class would become "
+"unresponsive when calling the <methodname>BlockingCallbackStore.add()</"
+"methodname> method after locking the callback field with a true responce "
+"from the <methodname>persistCallback()</methodname> method. This would occur "
+"because the <methodname>BlockingCallbackStore.getNext()</methodname> needed "
+"to control the lock on the callback field to break the waiting period, "
+"however this could not be achieved because of the wait period. To fix this "
+"issue the call to the <methodname>BlockingCallbackStore.add()</methodname> "
+"method has been removed as it was an unnecessary step."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:505
+#, no-c-format
+msgid ""
+"The <classname>HTTPClientInvoker</classname> did not support Beginner's All-"
+"purpose Symbolic Instruction Code (BASIC) authentication for proxies when "
+"the proxy was configured through system property options of <methodname>http."
+"proxyHost</methodname> and <methodname>http.proxyPort</methodname>. The "
+"issue appears because the <classname>HTTPClientInvoker</classname> would not "
+"check for the existence of these options and in tern it would never create a "
+"<methodname>Proxy-Authorization</methodname> request header, which is "
+"necessary for normal operation. To fix this the "
+"<classname>HTTPClientInvoker</classname> has been modified to check for the "
+"existence of the <methodname>http.proxyHost</methodname> option and if it "
+"detects its use, creates a <methodname>Proxy-Authorization</methodname> "
+"request header."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:510
+#, no-c-format
+msgid ""
+"<classname>HTTPClientInvoker</classname> would generate a "
+"<exceptionname>NullPointerException</exceptionname> when the HTTP server "
+"returned an error code without any content and then the <methodname>java.net."
+"HttpUrlConnection.getInputStream()</methodname> method returned a null "
+"value. In order to improve control over this behavior, the new variable "
+"<varname>UNMARSHAL_NULL_STREAM</varname> has been added to the "
+"<classname>HTTPClientInvoker</classname>. If this variable is set to true "
+"(the default value) the default behavior is executed, however if it is set "
+"to false the call to the <methodname>UnMarshaller.read()</methodname> is "
+"skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:515
+#, no-c-format
+msgid ""
+"Within the <classname>InvokerRegistry</classname> an error existed "
+"associated with the sequencing of events and <classname>serverLocators</"
+"classname> would return a null on occasion. To correct this race condition, "
+"the sequencing of events within the <classname>InvokerRegistry</classname> "
+"has been rearranged so that references to "
+"<classname>transportClientFactoryClasses</classname> and "
+"<classname>clientLocators</classname> are governed by <classname>clientLock</"
+"classname> and references to <classname>transportServerFactoryClasses</"
+"classname>, <classname>serverLocators</classname>, and "
+"<classname>registeredLocators</classname> are governed by "
+"<classname>serverLock</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:520
+#, no-c-format
+msgid ""
+"A bug existed where the value in the client configuration map of the "
+"<classname>ConnectionValidator</classname> would be ignored when the "
+"overloaded <methodname>org.jboss.remoting.Client</methodname> method was "
+"called and the <varname>DEFAULT_PING_PERIOD</varname> variable value was "
+"placed into the metadata map passed to the <classname>ConnectionValidator</"
+"classname>. This has been corrected by updating <classname>org.jboss."
+"remoting.Client.addConnectionListener</classname> so that "
+"<varname>DEFAULT_PING_PERIOD</varname> is only passed if the value of "
+"<varname>VALIDATOR_PING_PERIOD</varname> within the client's configuration "
+"map has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:525
+#, no-c-format
+msgid ""
+"<classname>ConnectionValidator</classname> may become unresponsive then the "
+"<methodname>run()</methodname> method is executed and utilizes the "
+"<varname>lock</varname> variable. The methods within the <methodname>run()</"
+"methodname> method are meant to time out so that the <varname>lock</varname> "
+"variable can become available to the <methodname>notifyListeners()</"
+"methodname> in the event of a network failure; however <methodname>run()</"
+"methodname> may execute again before <methodname>notifyListeners()</"
+"methodname> can. The synchronization on the <varname>lock</varname> variable "
+"has been modified to avoid this issue to enable correct operation."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:530
+#, no-c-format
+msgid ""
+"During occurrences of the server being under heavy load, an "
+"<exceptionname>IllegalStateException</exceptionname> would occur within the "
+"<methodname>ConnectorValidator.run()</methodname> method because further "
+"synchronization on the <varname>lock</varname> variable was necessary. This "
+"issue was fixed during the rectification of the above problem."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:535
+#, no-c-format
+msgid ""
+"A synchronization error within the <classname>MarshalFactory</classname> was "
+"allowing a subsystem to add a marshaller at the same time as EJB3 was trying "
+"to extract one causing users to receive an "
+"<exceptionname>InvalidMarshallingResource</exceptionname> exception; this "
+"also applied to unmarshallers. The error has been fixed by updating the "
+"<filename>jboss-remoting.jar</filename> file to include synchronized static "
+"Maps within the <classname>MarshalFactory</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:540
+#, no-c-format
+msgid ""
+"The <classname>SocketServerInvoker</classname> had an issue when shutting "
+"down <varname>ServerThreads</varname> causing a user to possibly receive an "
+"invocation to a closed <classname>SocketServerInvoker</classname> on the "
+"client side, causing an <exceptionname>InvalidStateException</"
+"exceptionname>. Allowing this exception would cause a clustered EJB3 system "
+"to generate a <exceptionname>UndeclaredThrowableException</exceptionname> "
+"instead of trying alternative servers. To allow for alternatives to be "
+"attempted, an optional behavior of allowing the "
+"<classname>MicroRemoteClientInvoker</classname> to interpret an "
+"<exceptionname>InvalidStateException</exceptionname> as a "
+"<exceptionname>CannotConnectException</exceptionname>, allowing for other "
+"servers to be attempted."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:550
+#, fuzzy, no-c-format
+msgid "JBoss Web"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:554
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1493\">JBPAPP-1493</"
+"ulink>: An error would be shown on occasion by <emphasis>Internet Explorer</"
+"emphasis> because xml content would not be sent when <emphasis>PROPFIND</"
+"emphasis> requests were being used. This has been fixed by creating a new "
+"method within <filename>WebdavServlet.java</filename> that overrides the "
+"<methodname>DefaultServlet</methodname> implementation for servlet request "
+"processing and testing for input before launching the "
+"<methodname>DocumentBuilder</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:559
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1470\">JBPAPP-1470</"
+"ulink>: When using APR (Apache Portable Runtime) on any operating system "
+"other than those which use the Linux Kernal 2.4 or newer, the "
+"<parameter>deferAccept</parameter> option would be set to false in the "
+"<methodname>AprEndpoint</methodname>. This may lead to a "
+"<exceptionname>NullPointerException</exceptionname> as the "
+"<methodname>accepter</methodname> thread starts to process a request while "
+"also calling for a <methodname>poller</methodname> before initialization. "
+"The issue has been resolved by moving the <methodname>acceptor</methodname> "
+"threads to being executed last when starting the <methodname>AprEndpoint</"
+"methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:564
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1334\">JBPAPP-1334</"
+"ulink>: The JBoss Web component of the Enterprise Application Platform has "
+"been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:569
+#, no-c-format
+msgid ""
+"If a war deployment included its own version of <filename>xalan.jar</"
+"filename> and <filename>xercesImpl.jar</filename> in <filename>WEB-INF/lib</"
+"filename>, the JBossWeb servlet container classloader returns JBoss provided "
+"version of the <literal>SAXParser</literal> from "
+"<methodname>SAXParserFactory.newInstance().newSAXParser()</methodname> "
+"rather than the version provided in the war deployment. To fix this bug the "
+"<filename>WebAppClassLoader.java</filename> has been updated to ensure the "
+"correct parser is used."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:579
+#, no-c-format
+msgid "JBoss Web Services"
+msgstr "JBoss-Webdienste"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:583
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1560\">JBPAPP-1560</"
+"ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component "
+"of the Enterprise Application Platform has been upgraded to version 2.1.4."
+"patch01. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:588
+#, no-c-format
+msgid ""
+"The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package "
+"contains classes to optimize field and method access by dynamically "
+"generating classes. Within the <classname>Injector</classname> class there "
+"is a <literal>HashMap</literal> value that is wrapped within a "
+"<literal>WeakReference</literal> however since there is only a "
+"<literal>WeakReference</literal> to the <classname>Injector</classname> "
+"class within this, the <literal>HashMap</literal> is garbage collected. To "
+"fix this the reference has been changed to a <literal>StrongReference</"
+"literal> and in order to maintain the original requirements, the "
+"<classname>Injector</classname> is now passed a reference to the ClassLoader "
+"instead of containing one specifically."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:595
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1210\">JBPAPP-1210</"
+"ulink>: The JBoss Web Services component of the Enterprise Application "
+"Platform has been upgraded to version 2.0.1.SP2_CP05. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:600
+#, no-c-format
+msgid ""
+"When deploying JBoss Web Services within Enterprise Application Platform "
+"without internet access, <classname>JBossWSEntityResolver</classname> would "
+"not resolve any schemas causing Web Services for Remote Portlets (WSRP) to "
+"produce an error. This issue has been fixed by modifying "
+"<classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader."
+"java</filename> to resolve schemas locally when an internet connection is "
+"unavailable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:605
+#, no-c-format
+msgid ""
+"WSProvide would ignore a <literal>SOAPBinding</literal> declaration "
+"specified in the EJB3 stateless session bean. To correct this and allow "
+"<literal>SOAPBinding</literal> to work as expected the following files have "
+"been modified: <filename>WSDLGenerator.java</filename>, "
+"<filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, "
+"<filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</"
+"filename> and <filename>WSDL11Writer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:610
+#, no-c-format
+msgid ""
+"The component <emphasis>Xerces</emphasis> of JBoss Web Services has a "
+"feature that optimizes the parsing of messages called <methodname>Deffered "
+"Node Expansion</methodname>.This defers node expansion until the nodes are "
+"accessed, improving performance where not all nodes need to be visited. "
+"However memory overheads are increased, which can be considerable for large "
+"messages."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:613
+#, no-c-format
+msgid ""
+"This release grants the user an option to disable the <methodname>Deffered "
+"Node Expansion</methodname> feature and have all nodes expand. To achieve "
+"this the following system property needs to be set:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:616
+#, no-c-format
+msgid "-Dorg.jboss.ws.disable_deferred_node_expansion=true"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:619
+#, no-c-format
+msgid ""
+"A regression with <literal>TCK5 SAAJ</literal> in the <classname>SOAPBody</"
+"classname> class was introduced with a fix to a previous bug and this has "
+"now been rectified by modifying the <filename>SOAPBodyImpl.java</filename> "
+"file to perform a <code>break</code> after assigning the "
+"<varname>childElement</varname> property."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:624
+#, no-c-format
+msgid ""
+"The end points for a <literal>transport-guarantee</literal> that is set to "
+"be confidential would see an attempt to exactly map the URL pattern in the "
+"WSDL. However since the servlet and security constraints will not be defined "
+"exactly the same a bug occurred whereby JBoss Web Services would assume the "
+"<literal>transport-guarantee</literal> was not confidential when generating "
+"the address, causing the WSDL to be generated with a http address. The "
+"<literal>transport-guarantee</literal> would still be enforced by JBoss Web "
+"Services as confidential but the WSDL would contain the wrong address, "
+"leading to clients attempting to connect to an incorrect address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:627
+#, no-c-format
+msgid ""
+"In order to rectify this occurrence, the <filename>MetaDataBuilder.java</"
+"filename> file has been modified so that when testing the servlet pattern it "
+"also tests correctly for the security constraint instead of assuming both "
+"with be of the same value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:632
+#, no-c-format
+msgid ""
+"When creating messages in SOAP 1.2 without attachments, the "
+"<classname>SOAPMessageImpl</classname> class sets the <varname>contentType</"
+"varname> variable to <literal>text/xml</literal>, which was incorrect. This "
+"has now been rectified by amending <varname>contentType</varname> to use the "
+"value <literal>application/soap+xml</literal> by adding the "
+"<methodname>getSAPContentType()</methodname> method to "
+"<filename>SOAPMessageImpl.java</filename> and updating "
+"<filename>DispatchImpl.java</filename> to correctly reference the SOAP "
+"message context."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:638
+#, no-c-format
+msgid ""
+"Deployments of JAX-WS nature would fail for JBoss AOP instrumented "
+"endpoints, generating an <exceptionname>IllegalAnnotationsException</"
+"exceptionname> as JBoss Web Services attempted to process the JBoss AOP "
+"methods. <filename>JAXWSMetaDataBuilder.java</filename> has been updated to "
+"mark JBoss AOP methods as synthetic which allows them to be skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:643
+#, no-c-format
+msgid ""
+"WSDL dynamic address replacement was not working correctly in previous "
+"versions of the Enterprise Application Platform since port and protocol "
+"numbers were not being considered. The <filename>WSDLRequestHandler.java</"
+"filename> file has been modified to use a new URL and protocol instead of "
+"the original URL and protocol in order to use the dynamically generated port "
+"and protocol numbers."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:648
+#, no-c-format
+msgid ""
+"In converting WSDL to Java, anonymous types that are nested within anonymous "
+"types generated a JAX-RPC mapping that did not match the source. The "
+"<filename>MappingFileGeneratorHelper.java</filename> file has been corrected "
+"to ensure that the generated mapping matches the source of the information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:653
+#, no-c-format
+msgid ""
+"JAAS certificate authentication support was not supported in the JBoss Web "
+"Services Security implementation, meaning that authentication via this "
+"method could not take place based on the certificate the client used to sign "
+"the message. Support for this has been added to JBoss Web Services and in "
+"tern the Enterprise Application Platform with this component upgrade."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:658
+#, no-c-format
+msgid ""
+"When the default port for a protocol was being used within JBoss Web "
+"Services, the port number still appeared at the end of the URL even though "
+"this was unnecessary. In order to remove the port number from the end of the "
+"URL, the <filename>MetaDataBuilder.java</filename> has been modified for "
+"each individual service that uses the default port."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:663
+#, no-c-format
+msgid ""
+"When JBoss Web Services is being used as a client, the information within "
+"the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not "
+"cleared for incoming client calls. In order to fix this the call to "
+"<methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the "
+"<classname>MessageContextAssociation</classname> class and is executed once "
+"the last message has been processed. The files that have been updated in "
+"order to incorporate the fix are: <filename>DOMUtils.java</filename>, "
+"<filename>XMLContent.java</filename>, <filename>ProviderImpl.java</"
+"filename>, <filename>MessageContextAssociation.java</filename>, "
+"<filename>MessageContextJAXWS.java</filename> and "
+"<filename>RequestHandlerImpl.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:668
+#, no-c-format
+msgid ""
+"When the <varname>webServiceHost</varname> property was not set, the <ulink "
+"url=\"http://localhost:8080/jbossws/services \">http://localhost:8080/"
+"jbossws/services</ulink> page presented the host name as "
+"<exceptionname>jbossws.undefined.host</exceptionname>. A "
+"<methodname>createAddress</methodname> method has been added to "
+"<filename>ContextServlet.java</filename> which dynamically updates the WSDL "
+"and XSD files with the address from the request URL before displaying "
+"information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:674
+#, no-c-format
+msgid ""
+"The JBoss Web Services upgrade 2.0.1.SP2_CP05 also includes the security fix "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>, discussed in the Security Issue section."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:683
+#, no-c-format
+msgid "JBoss Seam"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:687
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1553\">JBPAPP-1553</"
+"ulink>: When the <methodname>parseRequest()</methodname> method of the "
+"<classname>org.jboss.seam.web.MultipartRequest</classname> class uploaded a "
+"large file, there were occurrences when this would cause an endless loop and "
+"use 100% of the computers CPU. In order to break out of the loop, a "
+"<varname>loopCounter</varname> has been implemented within the "
+"<filename>MultipartRequest.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:692
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1494\">JBPAPP-1494</"
+"ulink>: The portal example that was previously included with the Seam "
+"Enterprise Application Platform distribution has been removed in order to "
+"avoid confusion that Seam 1.2.1 included with the EAP supports portal."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:697
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1044\">JBPAPP-1044</"
+"ulink>: After basic interaction with the Seam examples <filename>chatroom</"
+"filename>, <filename>mail</filename>, <filename>registration</filename>, "
+"<filename>booking</filename> and <filename>dvdstore</filename> would "
+"generate a <exceptionname>NullPointerException</exceptionname> during "
+"undeployment. In correcting this issue, the <filename>RootInterceptor.java</"
+"filename> file was updated to check if an applications context still active "
+"upon undeployment and deal with this appropriately."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:705
+#, no-c-format
+msgid "JBoss Hibernate"
+msgstr "JBoss Hibernate"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:709
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1580\">JBPAPP-1580</"
+"ulink>: The JBoss Hibernate Core component of the Enterprise Application "
+"Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:714
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1628\">JBPAPP-1628</"
+"ulink>: In an earlier fix to Hibernate the <methodname>org.hibernate.jdbc."
+"AbstractBatcher#closeQueryStatement()</methodname> method was changed to "
+"check for the existence of the prepared statement in the "
+"<classname>statementsToClose</classname> collection instead of closing it "
+"unconditionally. This has now caused a properties leak as the "
+"<methodname>org.hibernate.persister.entity."
+"AbstractEntityPersister#processGeneratedProperties()</methodname> used "
+"<methodname>org.hibernate.jdbc.AbstractBatcher#closeQueryStatement()</"
+"methodname> and the statement within <methodname>org.hibernate.persister."
+"entity.AbstractEntityPersister#processGeneratedProperties()</methodname> is "
+"not added to the <classname>statementsToClose</classname> collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:717
+#, no-c-format
+msgid ""
+"<filename>AbstractEntityPersister.java</filename> has been updated to "
+"execute a prepared statement on the result set and after calculating the "
+"<varname>propValue</varname> the result set is closed if it is not null; "
+"ensuring that no leak can occur."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:722
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1582\">JBPAPP-1582</"
+"ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</"
+"classname> is included with this CP release to support Sybase ASE 15 and "
+"this dialect now becomes apart of the Enterprise Application Platform "
+"certified configuration. Previous Sybase dialects are now considered "
+"deprecated and may be removed from future releases; however support will "
+"still be maintained for users who do not wish to move to the new dialect."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:742
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1524\">JBPAPP-1524</"
+"ulink>: The Sybase functions <methodname>second()</methodname>, "
+"<methodname>minute()</methodname>, <methodname>hour()</methodname> and "
+"<methodname>extract()</methodname> caused a "
+"<exceptionname>GenericJDBCException</exceptionname> when used. Moving these "
+"functions from the <filename>SQLServerDialect.java</filename> file to the "
+"<filename>SybaseDialect.java</filename> file allows for these functions to "
+"work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:757
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1519\">JBPAPP-1519</"
+"ulink>: Sybase does not support the operation <emphasis>on cascade delete</"
+"emphasis> while SQL Server does. To make sure that both operate correctly "
+"the <filename>SQLServerDialect.java</filename> file has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns true and <filename>SybaseDialect.java</filename> has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns false."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:762
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1496\">JBPAPP-1496</"
+"ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</"
+"emphasis> when using the <emphasis>Identity</emphasis> generator option. To "
+"close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make "
+"sure it is closed before returning the generated identity value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:767
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1480\">JBPAPP-1480</"
+"ulink>: Hibernate would attempt to read from an invalid column in the "
+"collection result set when the following conditions were present:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
+"ulink>: Die SQL-Standardkonfiguration hatte Fehler, die zu einem Problem mit "
+"hsqldb führten, das diese Konfiguration verwendet. Das Problem mit der "
+"Standardkonfiguration ist jetzt behoben."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:772
+#, no-c-format
+msgid "Instances of a subclass were contained in a collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:777
+#, no-c-format
+msgid ""
+"The subclasses were single-table and used a &lt;join&gt; (table-per-subclass "
+"with discriminator)."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:782
+#, no-c-format
+msgid ""
+"The &lt;join&gt; portion of the subclass contained at least 3 of its own "
+"columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:787
+#, no-c-format
+msgid ""
+"The &lt;join&gt; tables were fetched by select and not the default method "
+"for this task."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:792
+#, no-c-format
+msgid ""
+"To fix this issue the <filename>AbstractEntityPersister.java</filename> file "
+"was updated so that the <varname>columnNumber</varname> variable is passed "
+"to the <methodname>subclassColumnSelectableClosure</methodname> method "
+"instead of an increment of the for loop variable <varname>i</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:795
+#, no-c-format
+msgid ""
+"<filename>CollectionTest.java</filename> has also been updated and "
+"<filename>Animal.java</filename>, <filename>Mammal.java</filename>, "
+"<filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been "
+"added for testing purposes."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:800
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1467\">JBPAPP-1467</"
+"ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur "
+"when merging a detached instance of a <classname>One</classname> class that "
+"contains a new <classname>Many</classname> class instance and if and only if "
+"the <classname>One</classname> class was previously loaded as a proxy during "
+"the same transaction. The files <filename>StatefulPersistenceContext.java</"
+"filename>, <filename>BackrefPropertyAccessor.java</filename>, "
+"<filename>BackrefTest.java</filename> and <filename>Child.java</filename> "
+"have been updated to check for the proxy issue in the merging and once the "
+"proxy entity is found the <methodname>mergeMap</methodname> is updated to "
+"deal with this eventuality."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:805
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1365\">JBPAPP-1365</"
+"ulink>: A bug existed within Hibernate Core where the "
+"<methodname>addDuplicateAlias</methodname> method would include an entry "
+"into the hash map even when the <varname>classAlias</varname> variable was "
+"set to null; causing a <exceptionname>NullPointerException</exceptionname> "
+"when the <methodname>CrazyJPARRequirements()</methodname> method is called. "
+"To correct this issue the <filename>FromClause.java</filename> file has been "
+"modified to correct the <methodname>addDuplicateAlias</methodname> method by "
+"testing if the <varname>alias</varname> variable is null and if it is not "
+"null then the <methodname>fromElementByClassAlias.put</methodname> is now "
+"called, instead of this method being called even if <varname>alias</varname> "
+"contained a null value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:810
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1259\">JBPAPP-1259</"
+"ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL "
+"and the version field is specified by the user to not be updated, the "
+"<methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method "
+"would still update the field causing exceptions to appear in certain cases. "
+"Within this Enterprise Application Platform update "
+"<filename>AbstractEntityPersister.java</filename> has been corrected to "
+"check if the user has explicitly said that the version field should not be "
+"updated and does not update the field if this is the case."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:815
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1251\">JBPAPP-1251</"
+"ulink>: Filters that were enabled for Hibernate did not apply to update and "
+"delete Hibernate Query Language (HQL) statements. In correcting this bug "
+"numerous files have been updated to ensure that the filters work correctly. "
+"This fix is related to JBPAPP-1250 below."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:820
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1250\">JBPAPP-1250</"
+"ulink>: When creating queries with subqueries in Hibernate, any added "
+"filters would only apply to the top-level of the query and not to any "
+"subquery component or beneath. The Criteria code and HQL code associated "
+"with this has undergone significant re-tooling to allow filters to work "
+"appropriately with subqueries and extent as far as the Hibernate Query "
+"Language does."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:823
+#, no-c-format
+msgid ""
+"Though this is a significant fix to Hibernate, it has been included within "
+"this CP release because of its undeniable advantage to all users and ensures "
+"that filters on queries operate how a user would expect them to."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:833
+#, no-c-format
+msgid "JBoss Transaction Service (JBossTS)"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:837
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1510\">JBPAPP-1510</"
+"ulink>: The JBoss Transaction Service component of the Enterprise "
+"Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of "
+"the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:842
+#, no-c-format
+msgid ""
+"The <classname>AppServerJDBCXARecovery</classname> class was using the Java "
+"1.5 syntax when it should compile with Java 1.4. This error has been "
+"rectified with this release by modifying the "
+"<filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:847
+#, no-c-format
+msgid ""
+"When the Application Server started, the transaction manager may have "
+"deployed before the datasources, starting a recovery pass and causing "
+"exceptions. This issue has been rectified by modifying the "
+"<classname>AppServerJDBCXARecovery</classname> class and adding the "
+"<methodname>createConnection() throws SQLException</methodname> method which "
+"makes sure a connection exists before deploying the transaction manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:852
+#, no-c-format
+msgid ""
+"There were occurrences when the <classname>AppServerJDBCXARecovery</"
+"classname> class would contain information to an invalid connection because "
+"of database failure. This bug was fixed with the same correction as the "
+"above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</"
+"classname> class and adding the <methodname>createConnection() throws "
+"SQLException</methodname> method which makes sure a connection exists."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:857
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method would be run even when "
+"the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, "
+"when this method should only be executed before commit attempts and not "
+"rollbacks. In order to correct this and make sure the "
+"<methodname>beforeCompletion</methodname> method does not get executed for "
+"rollback events the <filename>SubordinateAtomicAction.java</filename> file "
+"has been modified."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:862
+#, no-c-format
+msgid ""
+"<methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a "
+"<exceptionname>HeuristicRollbackException</exceptionname> when the commit "
+"was aborted. This meant that <methodname>XATerminatorImple.commit</"
+"methodname> was unable to distinguish between a successful rollback and one "
+"in error. Fixed in this CP release, the <filename>TransactionImple.java</"
+"filename> file has been modified so that the <methodname>TransactionImple."
+"doOnePhaseCommit</methodname> method now generates a "
+"<exceptionname>RollbackException</exceptionname> instead of a heuristic when "
+"a successful rollback is performed."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:867
+#, no-c-format
+msgid ""
+"When the <literal>tx</literal> had been set to <varname>rollbackOnly</"
+"varname> and the <methodname>XATerminatorImple.prepare</methodname> method "
+"was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would "
+"be generated and yet the rollback would not be undertaken and the "
+"<literal>tx</literal> reference would be removed meaning no cleanup via the "
+"<methodname>commit</methodname> or <methodname>rollback</methodname> methods "
+"were possible. The <filename>XATerminatorImple.java</filename> file has been "
+"updated to correct this by improving the cleanup and exception reporting for "
+"rollbacks in <methodname>XATerminatorImple.prepare</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:872
+#, no-c-format
+msgid ""
+"The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called "
+"<methodname>beforeCompletion</methodname> but did not call "
+"<methodname>afterCompletion</methodname> when the return status was "
+"<literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</"
+"filename> now has corrected synchronization handling for transaction "
+"termination."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:877
+#, no-c-format
+msgid ""
+"The JCA coordinator did not call synchronizations during the phase commit "
+"cycle (1PC). Synchronization has been added to the JCA coordinator through "
+"the modification of the <filename>SubordinateAtomicAction.java</filename> "
+"file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:882
+#, no-c-format
+msgid ""
+"Coordinator methods would not perform a cleanup correctly. In order to "
+"rectify this cleanup routines have been added to the "
+"<methodname>phase2Commit</methodname> and <methodname>phase2Abort</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:892
+#, no-c-format
+msgid "Security Issues"
+msgstr "Sicherheitsprobleme"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:896
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>: An exploit existed within the JBoss Web Services component of the "
+"Enterprise Application Platform that would allow anyone to view any xml file "
+"from any location if <literal>&amp;resource=path/of/an/xmlfile.xml</literal> "
+"was applied to the end of any WSDL (Web Services Definition Language) access "
+"URL. The <filename>WSDLRequestHandler.java</filename> file has been updated "
+"to only allow the parent of a WSDL file, a servers data or WSDL or "
+"overridden WSDL publish directories access to xml file resources. Additional "
+"test files are also included which were created to ensure proper operation "
+"was being undertaken. (CVE-2009-0027 )"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:908
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1649\">JBPAPP-1649</"
+"ulink>: The documentation on the isolation of JGroup channels within the "
+"Server Configuration Guide was missing two parameters specific to the "
+"Enterprise Application Platform 4.3 distribution. The parameters of "
+"<varname>-Djboss.messaging.controlchanneludpport</varname> and <varname>-"
+"Djboss.messaging.datachanneludpport</varname> have been includedin section "
+"19.7.10 with example ports and the text addressing the concern of "
+"<emphasis>Why do I need to change the multicast port if I change the address?"
+"</emphasis> has been updated to reflect what is happening in an improved way."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:914
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1498\">JBPAPP-1498</"
+"ulink>: File set information within the Getting Started Guide (sections "
+"2.2.2 and 2.2.3) was outdated and required new information added and old "
+"information removed from the <literal>default</literal> server configuration "
+"file set and the contents of the <literal>conf</literal>, <literal>deploy</"
+"literal> and <literal>all</literal> directory sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:919
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1472\">JBPAPP-1472</"
+"ulink>: The instructions for adding SSL to EJB 2.1 in the Server "
+"Configuration Guide were incorrect as they did not include code pertaining "
+"to marshalling. The appropriate code has now been added to the instructions "
+"in section 9.8.2.3."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:924
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1362\">JBPAPP-1362</"
+"ulink>: The Getting Started Guide section 2.3 has been updated to include "
+"information about the <code>-b</code> option (and equivalents) that can be "
+"used on the command line to change the binding addresses of the Enterprise "
+"Application Platform for remote connectivity."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:929
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1346\">JBPAPP-1346</"
+"ulink>: Confusion existed when starting and stopping a <code>ZIP</code> "
+"installation of the server locally or remotely because a different username "
+"and password may be used. The Getting Started Guide has now been updated to "
+"explain that user credentials for the operating system will be used for "
+"local authentication and JBoss server credentials for remote authentication."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:937
+#, no-c-format
+msgid "Core Server"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:941
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1670\">JBPAPP-1670</"
+"ulink>: The JacORB component of the Enterprise Application Platform has been "
+"upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:946
+#, no-c-format
+msgid ""
+"A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to "
+"become unresponsive during shutdown. In rectifying this issue, the "
+"<filename>POA.java</filename> file has been modified so that instead of "
+"executing:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:949
+#, no-c-format
+msgid "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:950
+#, no-c-format
+msgid "the following is now executed:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:953
+#, no-c-format
+msgid "throw new ObjectNotActive();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:958
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1636\">JBPAPP-1636</"
+"ulink>: Affecting only third party adapters was an issue when one of these "
+"adapters handled the scheduling of work to be performed. The "
+"<classname>ExecutionContext</classname> class contained a value in seconds, "
+"from which the <methodname>getCompletionTimeout</methodname> method of "
+"<classname>org.jboss.resource.work.WorkWrapper</classname> obtains its "
+"information. An issue arises with <methodname>getCompletionTimeout</"
+"methodname> expecting the value to be in milliseconds, creating an error "
+"where the initially set timeout value may be 6 seconds but be passed to the "
+"thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> "
+"file has been updated and correctly converts the timeout value from seconds "
+"to milliseconds."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:963
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1635\">JBPAPP-1635</"
+"ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced "
+"for this release with new error codes of 17002 (connection reset) and 17008 "
+"(connection closed) now able to be handled. These enhancements have been "
+"applied to the <filename>OracleExceptionSorter.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:968
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1602\">JBPAPP-1602</"
+"ulink>: A <exceptionname>ConcurrentModificationException </exceptionname> "
+"would occur when a classloader would be undeployed while another user was "
+"attempting to load a class from the package. This error arose because the "
+"<classname>packagesMap</classname> within "
+"<classname>UnifiedLoaderRepository3</classname> had a <classname>TreeSet</"
+"classname> that was not correctly synchronized with changes. In order to "
+"rectify this, the <filename>ClassLoaderUtils.java</filename> file has been "
+"updated to import the <classname>Collections</classname> library and use the "
+"<methodname>synchronizedSet</methodname> method of the library in returning "
+"the <methodname>TreeSet</methodname> of the <methodname>newPackageSet</"
+"methodname> method."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:973
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1540\">JBPAPP-1540</"
+"ulink>: Within the cluster section of the Enterprise Application Platform, "
+"the <classname>GossipRouter</classname> and <classname>GossipClient</"
+"classname> (TCPGOSSIP) did not have socket read timeouts, socket linger "
+"timeouts and backlog set to provide the best behavior when heavily utilized "
+"or under network situations in need of improvement. This fix provides "
+"default values and configuration options for these in order to avoid "
+"problematic situations."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:978
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1539\">JBPAPP-1539</"
+"ulink>: When running parallel instances of the Enterprise Application "
+"Platform on Linux a bug existed where messages between the JGroups component "
+"of each instance would be picked up by both because all messages sent to the "
+"port number for Multicast Sockets would be picked up by both instances. The "
+"issue has been fixed by re-writing the code for Multicast Sockets so that "
+"the constructor uses a group address along with the port number as "
+"identifiers. This ensures that an instance of the EAP only receives messages "
+"pertaining to its specific group and thus inhibits channel crosstalk."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:983
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1538\">JBPAPP-1538</"
+"ulink>:The Probe Client had not been updated to use the same address as the "
+"Probe Listener does which is now 224.0.75.75. Correcting this issue, the "
+"Proble Client now uses 224.0.75.75 instead of 224.0.0.75 which allows the "
+"client and the listener to work together correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:988
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1535\">JBPAPP-1535</"
+"ulink>: The JDBCExtCacheLoader didn't handle persistent state transfer "
+"correctly since the <methodname>storeState</methodname> method would use "
+"available space on the <classname>MarshalledValueInputStream</classname> "
+"instead of on the <classname>ByteArrayInputStream</classname>. To correct "
+"the stream usage, <filename>JDBCExtendedCacheLoader.java</filename> has been "
+"updated to store the new state using the <varname>in_stream</varname> value "
+"as long as there is space available."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:993
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1534\">JBPAPP-1534</"
+"ulink>: The JDBCCacheLoader didn't work with Sybase as it tried to set a "
+"null <varname>BLOB</varname> (Binary Large OBject) column which is "
+"unsupported in Sybase. To correct this the <filename>JDBCCacheLoader.java</"
+"filename> and <filename>AdjListJDBCCacheLoader.java</filename> files have "
+"been updated to select the Sybase Driver if Sybase is to be used, ensuring "
+"that null values are set as <varname>LONGVARBINARY</varname> rather than "
+"<varname>BLOB</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:998
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1532\">JBPAPP-1532</"
+"ulink>: The JGroups clustering component of the Enterprise Application "
+"Platform has been upgraded to version 2.4.5. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1003
+#, no-c-format
+msgid ""
+"The probe listener within JGroups still used the old default address of "
+"224.0.0.75 instead of the new address of 224.0.75.75. The probe listener "
+"within JGroups has been updated with this release to use the correct default "
+"address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1008
+#, no-c-format
+msgid ""
+"The MPING protocol which sends a multicast ping over TCP contained cross-"
+"talk in Linux. the MPING protocol has since been corrected to eliminate "
+"cross-talk on the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1013
+#, no-c-format
+msgid ""
+"A problem was encountered within JGroups when two distinct processes were "
+"setup on the same machine, each using a different stack with different UDP "
+"multicast addresses. The issue was that each process would not work "
+"correctly because of the other, as each process would receive incorrect "
+"datagrams in reference to the groups each joined. To correct this the "
+"<classname>MulticastSocket</classname> constructor is now used in "
+"combination with a <varname>SocketAddress</varname> when JGroups is used on "
+"the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1018
+#, no-c-format
+msgid ""
+"The <literal>Gossip Router</literal> component of JGroups provided options "
+"to set <literal>backlog</literal>, <literal>socket read timeout</literal> "
+"and <literal>socket linger timeout</literal> within the code, however these "
+"options are not available via the command line. This update of the JGroups "
+"component, now includes the availability of these options to be set through "
+"the command line."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1023
+#, no-c-format
+msgid ""
+"Within the <literal>Gossip Router</literal> component of JGroups "
+"<methodname>Math.min</methodname> was used in calculating the socket linger "
+"timeout which caused incorrect results since this meant that the socket "
+"linger timeout would always be 1. <literal>Gossip Router</literal> has been "
+"updated to instead use <methodname>Math.max</methodname> in the calculation "
+"of the socket linger timeout."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1028
+#, no-c-format
+msgid ""
+"The <classname>RouterStub</classname> and <classname>GossipRouter</"
+"classname> classes have the <varname>setSoLinger</varname> value set "
+"incorrectly to use a seconds value when <varname>setSoLinger</varname> uses "
+"millisecond values. This meant that a value of 500 was 500 seconds rather "
+"than 500 milliseconds. The <classname>RouterStub</classname> class has had "
+"its <varname>setSoLinger</varname> corrected and the "
+"<classname>GossipRouter</classname> class has had the <varname>setSoLinger</"
+"varname> value corrected and timouts configurable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1035
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1530\">JBPAPP-1530</"
+"ulink>: The JCA adapter inflow did not roll back messages if a non-xa "
+"connection factory was being used within the JNDIProviderAdapter. In order "
+"to fix this issue the <filename>JmsServerSession.java</filename> file has "
+"been updated with added logic to the local transaction separation strategy "
+"as to allow for non-xa sessions to be rolled back using transaction session."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1040
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1521\">JBPAPP-1521</"
+"ulink>: The <classname>CleanShutdownInterceptor</classname> class would log "
+"a <exceptionname>GenericClusteringException</exceptionname> when the "
+"container had failed to shut down correctly or failed to start correctly and "
+"because of this behavior the error message displayed because of the "
+"exception should be updated to indicate that it may be an issue with the "
+"container failing to start instead of only failing to shut down. In this "
+"latest Enterprise Application Platform update, the error message has been "
+"updated to reflect both situations which may be the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1045
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1458\">JBPAPP-1458</"
+"ulink>: The JTA recovery configuration did not contain a line to enable "
+"JBoss Messaging (JBM) <classname>XAResourceRecovery</classname> even though "
+"it is stated in the JBM user guide. This CP release modifies the "
+"<filename>build-distr.xml</filename> file to all "
+"<classname>XAResourceRecovery</classname> to be enabled for JTA recovery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1050
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1479\">JBPAPP-1479</"
+"ulink>: Within the different distributions of the Enterprise Application "
+"Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and "
+"<filename>JBoss Messaging</filename> application policies have been present "
+"within the <filename>login-config.xml</filename> file, when "
+"<filename>JBossMQ</filename> is only included in the 4.2 distribution and "
+"<filename>JBoss Messaging</filename> is similarly only included in the 4.3 "
+"distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1053
+#, no-c-format
+msgid ""
+"This has been rectified in this release by modifying <filename>build.xml</"
+"filename> and <filename>login-config.xml</filename> to differentiate between "
+"requirements for each individual distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1058
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1473\">JBPAPP-1473</"
+"ulink>: The "
+"<classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</"
+"classname> within clustering didn't correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>, which would "
+"lead to the repeated calling of itself and eventually "
+"<exceptionname>StackOverflow</exceptionname> errors. In order to correct "
+"this the <filename>IgnoreUndeployLegacyClusteredSessionNotificationPolicy."
+"java</filename> file has been modified to correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1063
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1460\">JBPAPP-1460</"
+"ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for "
+"this Enterprise Application Platform release. This update corrects numerous "
+"bugs and details on these fixes can be found at <ulink url=\"https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html\">https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1068
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1366\">JBPAPP-1366</"
+"ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the "
+"<option>Oracle</option> schema is specified. To correct this the "
+"<filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has "
+"been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</"
+"methodname> function which changes all dots in a constraint name to "
+"underscores. This ensures that constraint names are compatible with Oracle."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1073
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1307\">JBPAPP-1307</"
+"ulink>: The Persistence Unit (PU) root was incorrectly detected within "
+"deployments that contained nested <filename>.jar</filename> files. The root "
+"PU was being detected as the first nested <filename>.jar</filename> "
+"encountered instead of being the deployment which contains the "
+"<filename>persistence.xml</filename> file. To make sure that the PU root is "
+"always set correctly, the <filename>JmxDeploymentUnit.java</filename> file "
+"has been updated with the removal of testing for the url being null and the "
+"<parameter>deploymentInfo.parent</parameter> not being null. This means that "
+"the url is now always taken straight from the "
+"<parameter>extractDescriptorUrl</parameter> of <filename>META-INF/"
+"persistence.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1078
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1289\">JBPAPP-1289</"
+"ulink>: The JBoss JAXR component of the Enterprise Application Platform has "
+"been upgraded to version 1.2.0.SP2. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1083
+#, no-c-format
+msgid ""
+"In the <filename>org.jboss.jaxr.juddi.JUDDIServlet</filename> and "
+"<filename>org.jboss.jaxr.juddi.transport.SaajTransport</filename> files the "
+"namespace value for <varname>xml:lang</varname> contained <literal>http://"
+"www.w3.org/TR/REC-xml/</literal>, which caused an exception within the metro "
+"stack. The namespace value should instead be null and this has been applied "
+"for this JAXR update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1090
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1275\">JBPAPP-1275</"
+"ulink>: The Xalan part of the Enterprise Application Platform has been "
+"upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the "
+"circumstance where an application which heavily used Xalan within large "
+"multi-threaded environments would encounter blocking situations."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
+"ulink>: Es fand ein Upgrade der JBoss Web Services Komponente zu Version "
+"2.0.1.SP2_CP02 statt. Dieses Upgrade beinhaltet verschiedene "
+"Fehlerbehebungen und Verbesserungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1095
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1267\">JBPAPP-1267</"
+"ulink>: <classname>UserTransaction</classname> (UT) was not able to be "
+"deployed with a clustered proxy that supported sticky transactions "
+"correctly. This has been fixed by modifying numerous files which make "
+"<classname>UserTransaction</classname> deployable with transaction sticky "
+"load balance policies."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1100
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1249\">JBPAPP-1249</"
+"ulink>: The JSF component of the Enterprise Application Platform has been "
+"upgraded to version 1.2_10. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1105
+#, no-c-format
+msgid ""
+"A mixed EL expression ending with a literal failed to parse as a managed "
+"bean property value. The <filename>BeanBuilder.java</filename> file was "
+"updated with the removal of <code>ELUtils.getScope(this.expressionString, "
+"segment);</code> in order to fix this issue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1110
+#, no-c-format
+msgid ""
+"<methodname>LifecycleImpl</methodname> and <methodname>RestoreViewPhase</"
+"methodname> forced the <methodname>responseComplete()</methodname> method "
+"for the status of an existing view. To correct this problem the "
+"<filename>RestoreViewPhase.java</filename> file has been edited with the "
+"code <code>facesContext.responseComplete();</code> removed and replaced with "
+"<code>facesContext.renderResponse();</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1115
+#, no-c-format
+msgid ""
+"For a &lt;h:dataTable&gt; tag which does not set the <varname>var</varname> "
+"attribute, if the UIData component is created using a binding and calls the "
+"<methodname>setVar()</methodname> method to set the <varname>var</varname> "
+"attribute, it would be overwritten as a null value by the &lt;h:"
+"dataTable&gt; tag. This bug has been fixed by modifying the "
+"<filename>HtmlTaglib21Generator.java</filename> file so that component "
+"properties are not set if the tag attribute has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1120
+#, no-c-format
+msgid ""
+"The <classname>BindingValidator</classname> would generate a "
+"<exceptionname>ConverterException</exceptionname> instead of a "
+"<exceptionname>ValidatorException</exceptionname>. For this update, "
+"<classname>BindingValidator</classname> has been modified to generate the "
+"correct exception; <exceptionname>ValidatorException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1125
+#, no-c-format
+msgid ""
+"The cause of a <classname>PostConstruct</classname> exception within the "
+"<classname>BeanBuilder</classname> was not communicated to the user "
+"correctly. To correct the issue so that no information is hidden from the "
+"user, the <exceptionname>ManagedBeanCreationException</exceptionname> has "
+"been updated to provide more information about the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1130
+#, no-c-format
+msgid ""
+"An issue was present that would cause majarra to execute <filename>faces-"
+"config.xml </filename> initialization files twice, creating duplicate "
+"operations. This was caused since a record was not kept of which files had "
+"been initialized and which had not. File initialization tracking has been "
+"implemented to correct this issue and this has seen the modification of the "
+"following files: <filename>ConfigManager.java</filename>, "
+"<filename>ConfigureListener.java</filename>, <filename>WebConfiguration."
+"java</filename>, <filename>ConfigurationResourceProvider.java</filename>, "
+"<filename>MetaInfResourceProvider.java</filename>, "
+"<filename>RIConfigResourceProvider.java</filename> and "
+"<filename>WebResourceProvider.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1135
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.ApplicationObjectInputStream</"
+"classname> extends the functionality of <classname>java.io."
+"ObjectInputStream</classname> but failed to preserve the functionality as "
+"<classname>com.sun.faces.renderkit.ApplicationObjectInputStream</classname> "
+"would fail when primitives were used, unlike the <classname>java.io."
+"ObjectInputStream</classname> class which contains a special case to handle "
+"such a case. This would cause problems for <literal>UIComponents</literal>. "
+"<filename>ApplicationObjectInputStream.java</filename> has been updated to "
+"explicitly handle primitive cases and catch the "
+"<exceptionname>ClassNotFoundException</exceptionname> which may be generated."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1140
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.renderkit.html_basic.OutputLinkRenderer</classname> "
+"did not encode parameters correctly, missing the <literal>URLEncoding</"
+"literal>. <literal>URLEncoding</literal> has been added, correcting this "
+"bug, along with the parameter names."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1145
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.BaseTableRenderer</"
+"classname> did not allow for empty <varname>columnClasses</varname> when "
+"generating columns from user input. The issue was realizing when to create "
+"numerous columns rather just one; for instance if the user input "
+"<literal>foo, </literal> with a trailing space then the expected output "
+"would be one column with the name <literal>foo</literal> and another empty "
+"column. This was not the case though, as <literal>foo, </literal> would "
+"generate just one column with <literal>foo, </literal> in its entirety as "
+"the column name, instead of splitting the columns on the comma. This "
+"behavior has now been corrected so that <classname>com.sun.faces.renderkit."
+"html_basic.BaseTableRenderer</classname> no generates columns correctly, and "
+"in order to achieve this the following files have been updated: "
+"<filename>BasetableRenderer.java</filename>, <filename>GridRenderer.java</"
+"filename> and <filename>TableRenderer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1150
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.MenuRenderer</classname> "
+"class did not correctly differentiate between <literal>Objects</literal>; "
+"for instance the different between <literal>Boolean</literal> and "
+"<literal>boolean</literal>, noting the capitalization of the first. The "
+"error was with the logic in <classname>UISelect</classname> and "
+"<classname>MenuRenderer</classname>. To correct this, proper use of the "
+"converter for these classes has been implemented to deal with Objects "
+"correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1155
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.lifecycle.RestoreViewPhase</classname> called "
+"<methodname>DebugUtil.printTree</methodname> after restoring the view if "
+"debugging was enabled, causing incorrect initialization of calls when a "
+"listbox is being used and returning an incorrect value in the "
+"<classname>RenderResponse</classname> phase. Method calls have been "
+"restructured with the removal of references to the <methodname>DebugUtil."
+"printTree()</methodname> method from <filename>ViewHandlerImpl.java</"
+"filename> and <filename>RestoreViewPhase.java</filename> and "
+"<filename>RenderResponsePhase.java</filename> has been modified to call "
+"<methodname>DebugUtil.printTree</methodname> (if <varname>FINEST</varname> "
+"logging is enabled) at the end of the <classname>RenderResponse</classname> "
+"phase, fixing the issue (with the above changes also) and providing a more "
+"accurate view of the tree."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1159
+#, no-c-format
+msgid ""
+"<literal>CGLIB Enhanced UIComponents</literal> in a component tree would "
+"return a value of null for their class when calling <methodname>getPackage()"
+"</methodname> causing <classname>HtmlInputText.handleAttribute</classname> "
+"to fail as it relies on a not-nulll value. This issue has been corrected by "
+"ignoring a returned value of null from the <methodname>getPackage()</"
+"methodname> method for every instance in the codebase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1164
+#, no-c-format
+msgid ""
+"The <classname>UIComponentBase</classname> did not allow for the children of "
+"a tree to be iterated through in reverse order using a list iterator as it "
+"would produce an <exceptionname>IndexOutOfBoundsException</exceptionname> "
+"when the execution tries to calculate the size of the children. "
+"<methodname>ChildrenListIterator</methodname> method has been modified "
+"within the <classname>UIComponentBase</classname> class by changing the line "
+"of code <code>if ((index &lt; 0) || (index &gt;= list.size())) { </code> to "
+"<code>if ((index &lt; 0) || (index &gt; list.size())) {</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1169
+#, no-c-format
+msgid ""
+"Renderer kits for <filename>faces-config.xml</filename> were processed out "
+"of order depending on if <literal>ICEfaces</literal> or <literal>Mojara "
+"1.2_09</literal> is in use. This occurred due to containing all renderer DOM "
+"nods in a list associated with a namespace. This was done so that the "
+"renderer nodes could then be processed prior to the <literal>RenderKits</"
+"literal> being created and the nodes could be processed using the proper "
+"namespace. However, by placing all the renderers into this list, we lost the "
+"document ordering. The issue has been fixed by associating the renderer "
+"nodes with their owning document and processed in the parsing order."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1175
+#, no-c-format
+msgid ""
+"The <methodname>Class.getPackage()</methodname> method calls to synchronized "
+"methods, inhibiting scalability if the method has to be repeatedly executed. "
+"Use of the <methodname>Class.getPackage()</methodname> method has now been "
+"removed from <filename>UIComponent.java</filename>, <filename>RenderKitUtils."
+"java</filename> and <filename>HtmlComponentGenerator.java</filename>. "
+"Instead, the class name is now checked if it starts with the package name "
+"that is of interest, <classname>javax.faces.component.</classname>. This "
+"includes the components that are generated by the "
+"<classname>HtmlComponentGenerator</classname> since they are packaged in "
+"<classname>javax.faces.component.html</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1180
+#, no-c-format
+msgid ""
+"A bug presented itself in the <classname>RenderKitUtils</classname> class "
+"when a semicolon (<code>;</code>) followed a forward-slash (<code>/</code>) "
+"in a header Accept value (for instance: <code>text/;q=0.5</code>). To "
+"rectify this issue the <classname>RenderKitUtils</classname> class has been "
+"updated to assume <code>*</code> as the subtype for an Accept header that "
+"contains no subtype."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1187
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1224\">JBPAPP-1224</"
+"ulink>: Attribute default values in EJB were not set when in use with "
+"<literal>@Service</literal> and <literal>XMBean XML</literal> . In order to "
+"correct this the behavior has been re-written to improve the mimicking of "
+"<classname>ServerCreator</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1192
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1170\">JBPAPP-1170</"
+"ulink>: When the <methodname>getMBeanInfo</methodname> method is called "
+"within <classname>MBeanServerImpl</classname> and "
+"<classname>RawDynamicInvoker</classname>, the underlying exception to "
+"<exceptionname>NotCompliantMBeanException</exceptionname> is not expressed "
+"to the user. <filename>RawDynamicInvoker.java</filename> has now been "
+"updated to provide this useful information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1197
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1099\">JBPAPP-1099</"
+"ulink>: The <filename>commons-beanutils.jar</filename> file within the "
+"Enterprise Application Platform had the incorrect version in the "
+"<filename>manifest.mf</filename> file. Through the course of correcting this "
+"bug, it was found that the <literal>beanutils</literal> component was "
+"outdated and a newer version contained many advantages. In this update to "
+"the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, "
+"which sees the significant improvement that fixes a memory leak caused by a "
+"circular reference concerning the <classname>WeakHashMap</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1202
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1002\">JBPAPP-1002</"
+"ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be "
+"logged when transactions were not completed between invocations. However "
+"this was an error as BMT Stateful Session Beans are allowed to have this "
+"occurrence and so this logging measure has been removed in this Enterprise "
+"Application Platform update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1207
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
+"ulink>: Discrepancies existed between the port schemes within the "
+"<filename>sample-bindings.xml</filename> file. These include:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-961\">JBPAPP-961</"
+"ulink>: Es fand ein Upgrade von JBoss Web zu Version 2.0.0.GA CP06 statt."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1212
+#, no-c-format
+msgid ""
+"The remoting connectors were inserted in different places within the ports "
+"definition sections, making the comparison of the sections more difficult "
+"than was necessary."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1217
+#, no-c-format
+msgid ""
+"The <literal>ports-03</literal> section was missing the <literal>EJB "
+"remoting connector</literal> and the <literal>remoting connector</literal> "
+"sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1222
+#, no-c-format
+msgid ""
+"<literal>mq</literal> was used in the name property of the "
+"<varname>HAJNDIJMSProvider</varname> instead of <literal>jms</literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1227
+#, no-c-format
+msgid ""
+"The <literal>ports-01</literal>, <literal>ports-02</literal>, and "
+"<literal>ports-03</literal> schemes defined the <varname>timeout</varname> "
+"attribute twice in the <literal>JBoss Messaging</literal> section:"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1233
+#, no-c-format
+msgid "The above issues have been fixed appropriately in this update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1238
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-713\">JBPAPP-713</"
+"ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: "
+"PermGen</errorname> error. To correct this issue the Enterprise Application "
+"Platform now uses <filename>beanutils 1.8.0</filename> which fixes this "
+"<errorname>OutOfMemoryError</errorname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1243
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
+"ulink>: JMX source code was being exposed to the user when a "
+"<exceptionname>HTTP Status 500</exceptionname> exception would occur. To "
+"correct this, an error page <filename>genericError.jsp</filename> has been "
+"created and is now displayed whenever a <exceptionname>HTTP Status 500</"
+"exceptionname> exception occurs."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1252
+#, no-c-format
+msgid "Known Issues with this release"
+msgstr "Bei dieser Release bekannte Probleme"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1255
+#, no-c-format
+msgid "Following is a list of known issues at the time of release."
+msgstr ""
+"Nachfolgend eine Liste der zum Zeitpunkt der Release bekannten Probleme."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1259
+#, no-c-format
+msgid "General Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1263
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>: Footnotes within documentation tables and lists do not appear within "
+"PDFs. This issue resides within FOP and currently no workaround exists. "
+"Where possible footnotes are not used in the circumstances mentioned, "
+"however in documents such as the Release Notes the web address of a JIRA is "
+"automatically generated as a footnote and places a number beside that of the "
+"JIRA, referencing a footnote that does not appear."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1268
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-885\">JBPAPP-885</"
+"ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</"
+"methodname> or <methodname>RedeliveryDelay</methodname> is set to a value "
+"apart from zero, messages will not be redelivered even though the method "
+"<methodname>session.rollback()</methodname> had been called. This issue will "
+"not be fixed because redelivery delay is handled on the server side and the "
+"message is already acknowledged before delivery of the message with a non "
+"durable subscription. For the Enterprise Application Platform, this means "
+"that redelivery delays with non durable subscriptions cannot be supported."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1276
+#, no-c-format
+msgid "Hibernate Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1280
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1613\">JBPAPP-1613</"
+"ulink>: Null values for columns mapped as boolean in Hibernate, are "
+"persisted as zero instead of null. When the <methodname>PreparedStatement."
+"setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the "
+"Sybase environment, Sybase JDBC converts the null value to a zero because "
+"Sybase does not allow null bit columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1285
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
+"ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it "
+"should be set up to use image and text. Tests attaining to this currently "
+"fail with the message:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Gestatten die Einstellung multipler Instanzen auf einer Machine "
+"unter Verwendung einer Subpackage-Methode. Diese Funktionalität wurde in "
+"dieser Release mit -bin Dateien hinzugefügt."
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1288
+#, no-c-format
+msgid ""
+"The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not "
+"supported and should not be called."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1291
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1554\">JBPAPP-1554</"
+"ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</"
+"methodname> method within Hibernate fails since Sybase currently only allows "
+"one column in a subquery select list, with the only exception to this being "
+"that a subquery in an <code>EXISTS()</code> predicate can have <code>*</"
+"code> as the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1294
+#, no-c-format
+msgid ""
+"The current workaround for this is to not use the HQL <methodname>elements()"
+"</methodname> method if the elements have a composite key. Instead the HQL "
+"should be reformatted to ensure there is no subquery with more than one item "
+"in the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1299
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1546\">JBPAPP-1546</"
+"ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be "
+"used to create stored procedures while in chained transaction mode. The "
+"suggested workaround for this case is to add the following code follwing the "
+"defining of the new stored procedure:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:1302
+#, no-c-format
+msgid ""
+"&lt;database-object&gt;\n"
+"        &lt;create&gt;\n"
+"                sp_procxmode paramHandling, 'chained'\n"
+"        &lt;/create&gt;\n"
+"        &lt;drop/&gt;\n"
+"&lt;/database-object&gt;"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1305
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
+"ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase "
+"environment and there are three or more joins where at least one of the "
+"joins involves a union."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Gestatten die Einstellung multipler Instanzen auf einer Machine "
+"unter Verwendung einer Subpackage-Methode. Diese Funktionalität wurde in "
+"dieser Release mit -bin Dateien hinzugefügt."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1308
+#, no-c-format
+msgid ""
+"A workaround for this issue exists where it is reconmended that a user does "
+"not use <literal>join fetches</literal> involving <literal>union subclasses</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1313
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1230\">JBPAPP-1230</"
+"ulink>: In the Sybase environment when creating a subquery with an alias in "
+"use, the query will be incorrectly generated and cause an "
+"<exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. "
+"This bug impacts the following tests such that at present they are expected "
+"to fail: <classname>CriteriaQueryTest.testSubselect</classname>, "
+"<classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, "
+"<classname>DynamicFilterTest.testCriteriaControl</classname> and "
+"<classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1316
+#, no-c-format
+msgid ""
+"The known workaround is to use a HQL query instead of using a "
+"<methodname>DetachedCriteria</methodname> method in a subquery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1321
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1082\">JBPAPP-1082</"
+"ulink>: A limitation in the PostgreSQL JDBC driver causes a "
+"<exceptionname>javax.persistence.RollbackException</exceptionname>. This "
+"occurs when the <code>char</code> property is used without a value set as "
+"Hibernate then persists a string containing the character <code>\\u0000</"
+"code>, which causes PostgreSQL to generate an exception as it does not allow "
+"this character to be embedded in a string."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1324
+#, no-c-format
+msgid ""
+"Currently a workaround for persisting the <code>\\u0000</code> character in "
+"a <code>char</code> column using PostgreSQL does not exist. Instead it is "
+"reconmended that to persist a null value for the <code>char</code> property "
+"when it is uninitialized, the <methodname>java.lang.Character</methodname> "
+"method should be used."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1329
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1081\">JBPAPP-1081</"
+"ulink>: In the Entity Manager documentation it is stated that table aliases "
+"are supported in <code>update</code> clauses, however at present this is not "
+"the case. To fix this, the code has to be modified to remove the "
+"identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1334
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1068\">JBPAPP-1068</"
+"ulink>: When using Microsoft SQL and <code>@Type(type=\"text\")</code> in "
+"creating a table, the field is correctly created as <code>\"text\"</code> "
+"however when a delete operation is issued the field becomes set as a "
+"<varname>varchar</varname>, forcing the Microsoft SQL driver to return the "
+"error:"
+msgstr ""
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1337
+#, no-c-format
+msgid ""
+"The data types text and nvarchar are incompatible in the equal to operator."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1340
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1063\">JBPAPP-1063</"
+"ulink>: Currently MySQL does not support millisecond and microsecond "
+"measurements when returning database values such as <code>TIME</code> and "
+"<code>TIMESTAMP</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1345
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-953\">JBPAPP-953</"
+"ulink>: Hibernate Core and Annotations do not currently support the "
+"Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the "
+"Hypersonic database is planned for future releases."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1350
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-946\">JBPAPP-946</"
+"ulink>: Within the Hibernate Entity Manager three different "
+"<exceptionname>NullPointerExceptions</exceptionname> are being investigated "
+"in relation to the EJB3 configuration, transaction operations when they are "
+"extended and packaging."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1355
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-906\">JBPAPP-906</"
+"ulink>: A bug exists within the Hibernate Core whereby the unstable "
+"synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is "
+"utilized creating a deserialized String. This causes a problem where if "
+"multiple threads are loading database rows containing arrays of strings, one "
+"thread is forced to undertake all the procedure while the other threads are "
+"left dormant."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1358
+#, no-c-format
+msgid ""
+"The implemented workaround for this issue is to use <code>-Dsun.lang."
+"ClassLoader.allowArraySyntax=true</code>, which can be a default setting "
+"within the <filename>run.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1363
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Within the Hibernate component of the Enterprise Application "
+"Platform the HashMap and HashSet iteration order changed from past releases "
+"because of support for JDK 1.6. However this has meant that the order of "
+"columns in union clauses and union-subclasses has changed, generating a "
+"slight impact on the components performance."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Innerhalb der Hibernate-Komponente des EAP hat sich die Reihenfolge "
+"von HashMap und HashSet-Iteration im Vergleich zu früheren Releases wegen "
+"des Support für JDK 1.6 verändert. Dies bedeutete jedoch, dass die "
+"Reihenfolge von Spalten in Union-Clauses und Union-Subclasses sich verändert "
+"hat, wodurch es zu einer leichten Auswirkung auf die Komponenten-Performance "
+"kam."

Added: projects/docs/enterprise/4.3.4/readme/de-DE/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/de-DE/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/de-DE/Revision_History.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,29 @@
+# translation of readme.po to
+# Language de-DE translations for readme package.
+#
+# Automatically generated, 2008.
+# Jasna Dimanoski <jdimanos at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-07 07:21+1000\n"
+"Last-Translator: Jasna Dimanoski <jdimanos at redhat.com>\n"
+"Language-Team:  <de at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/de-DE/readme.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/de-DE/readme.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/de-DE/readme.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -30,8 +30,9 @@
 "Enterprise Application Platform &VERSION;. New features, known problems, "
 "resources, and other current issues are addressed here."
 msgstr ""
-"Diese Release Notes enthalten wichtige Informationen zur JBoss "
-"Enterprise Application Platform &VERSION;. Neue Features, bekannte Probleme, Ressourcen und andere aktuellen Themen werden hier behandelt."
+"Diese Release Notes enthalten wichtige Informationen zur JBoss Enterprise "
+"Application Platform &VERSION;. Neue Features, bekannte Probleme, Ressourcen "
+"und andere aktuellen Themen werden hier behandelt."
 
 #. Tag: title
 #: readme.xml:16
@@ -46,7 +47,11 @@
 "JBoss Enterprise Application Platform is the next evolutionary step in open "
 "source enterprise software. It is a powerful tool for developing rich, high "
 "performance, Web 2.0 applications on a pure Java Platform."
-msgstr "JBoss Enterprise Application Platform ist der nächste Evolutionsschritt in Open Source Enterprise Software. Sie ist ein leistungsfähiges Tool zur Entwicklung umfassender, sehr leistungsfähiger Web 2.0 Anwendungen auf einer reinen Java-Plattform."
+msgstr ""
+"JBoss Enterprise Application Platform ist der nächste Evolutionsschritt in "
+"Open Source Enterprise Software. Sie ist ein leistungsfähiges Tool zur "
+"Entwicklung umfassender, sehr leistungsfähiger Web 2.0 Anwendungen auf einer "
+"reinen Java-Plattform."
 
 #. Tag: para
 #: readme.xml:20
@@ -58,7 +63,13 @@
 "supported. So your new enterprise Java applications can take immediate "
 "advantage of the Java EE 5.0's significantly simpler POJO-based programming "
 "model."
-msgstr "JBoss Enterprise Application Platform liefert vollständige Kompatibilität mit bestehenden J2EE 1.4 Enterprise Java-Anwendungen. Gleichzeitig werden alle in der Java EE 5.0 Spezifikation definierten Schlüssel-Features und Komponenten unterstützt. Ihre neuen Enterprise Java Anwendungen können also sofort die Vorteile des wesentlich einfacheren POJO-basierten Programmiermodells von Java EE 5.0 nutzen."
+msgstr ""
+"JBoss Enterprise Application Platform liefert vollständige Kompatibilität "
+"mit bestehenden J2EE 1.4 Enterprise Java-Anwendungen. Gleichzeitig werden "
+"alle in der Java EE 5.0 Spezifikation definierten Schlüssel-Features und "
+"Komponenten unterstützt. Ihre neuen Enterprise Java Anwendungen können also "
+"sofort die Vorteile des wesentlich einfacheren POJO-basierten "
+"Programmiermodells von Java EE 5.0 nutzen."
 
 #. Tag: para
 #: readme.xml:23
@@ -70,8 +81,12 @@
 "Application Platform is fully tested and supported by Red Hat, and is "
 "certified to work on many leading enterprise hardware and software products."
 msgstr ""
-"Durch Integration der besten Open-Source-Frameworks ihrer Art, wie etwa JBoss Seam, Hibernate, Tomcat und JBoss Cache nutzt die Plattform die Innovationen der Open Source Community. Die JBoss Enterprise "
-"Application Platform ist vollständig getestet und wird von Red Hat unterstützt; desweiteren ist sie für den Einsatz an vielen führenden Enterprise Hardware- und Software-Produkten zertifiziert."
+"Durch Integration der besten Open-Source-Frameworks ihrer Art, wie etwa "
+"JBoss Seam, Hibernate, Tomcat und JBoss Cache nutzt die Plattform die "
+"Innovationen der Open Source Community. Die JBoss Enterprise Application "
+"Platform ist vollständig getestet und wird von Red Hat unterstützt; "
+"desweiteren ist sie für den Einsatz an vielen führenden Enterprise Hardware- "
+"und Software-Produkten zertifiziert."
 
 #. Tag: para
 #: readme.xml:26
@@ -80,7 +95,11 @@
 "All of which means you can develop your new application taking advantage of "
 "Java EE 5.0 technologies immediately and with the confidence of knowing it "
 "will remain forward-compatible with future versions of the JBoss Platform."
-msgstr "All dies bedeutet, dass Sie Ihre neue Anwendung entwickeln und sofort die Vorteile von Java EE 5.0 Technologie nutzen können, während Sie die Gewissheit haben, dass diese mit zukünftigen Versionen der JBoss Plattform kompatibel bleibt."
+msgstr ""
+"All dies bedeutet, dass Sie Ihre neue Anwendung entwickeln und sofort die "
+"Vorteile von Java EE 5.0 Technologie nutzen können, während Sie die "
+"Gewissheit haben, dass diese mit zukünftigen Versionen der JBoss Plattform "
+"kompatibel bleibt."
 
 #. Tag: title
 #: readme.xml:32
@@ -101,7 +120,10 @@
 "In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
 "with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
 "messaging infrastructure for JBoss Enterprise Application Platform."
-msgstr "In JBoss Enterprise Application Platform 4.3 wurde JBoss MQ 1.3 durch JBoss Messaging 1.4 ersetzt. JBoss Messaging bietet eine sehr leistungsfähige Messaging Infrastruktur für die JBoss Enterprise Application Platform."
+msgstr ""
+"In JBoss Enterprise Application Platform 4.3 wurde JBoss MQ 1.3 durch JBoss "
+"Messaging 1.4 ersetzt. JBoss Messaging bietet eine sehr leistungsfähige "
+"Messaging Infrastruktur für die JBoss Enterprise Application Platform."
 
 #. Tag: title
 #: readme.xml:40
@@ -115,7 +137,10 @@
 msgid ""
 "JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
 "Platform 4.3 and will now provide a complete implementation of JAX-WS."
-msgstr "Es fand ein Upgrade von JBoss Web Services zu 2.0.1 in JBoss Enterprise Application Platform 4.3 statt und bietet nun eine komplette Implementierung von JAX-WS."
+msgstr ""
+"Es fand ein Upgrade von JBoss Web Services zu 2.0.1 in JBoss Enterprise "
+"Application Platform 4.3 statt und bietet nun eine komplette Implementierung "
+"von JAX-WS."
 
 #. Tag: title
 #: readme.xml:48
@@ -132,7 +157,8 @@
 "and platform requirements and prerequisites."
 msgstr ""
 "Dieser Abschnitt enthält Informationen zur Installation und dem Upgrade zur "
-"JBoss Enterprise Application Platform Version &VERSION;, einschließlich Hardware- und Plattform-Anforderungen sowie Voraussetzungen."
+"JBoss Enterprise Application Platform Version &VERSION;, einschließlich "
+"Hardware- und Plattform-Anforderungen sowie Voraussetzungen."
 
 #. Tag: title
 #: readme.xml:53
@@ -157,12 +183,19 @@
 "docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
 "instructions to install and verify JBoss Enterprise Application Platform."
 msgstr ""
-"Sie müssen über ausreichend Platz auf der Disk verfügen, um JDK und JBoss Enterprise Application Platform zu installieren und auch für Ihre Anwendung noch genug Platz haben. "
-"Sie benötigen eine funktionierende Installation von JDK 1.5. Für aktuelle Informationen zu unterstützten Betriebssystem-/JVM-Kombinationen, unterstützten Datenbankplattformen sowie aktuellen Infos zur Revisionsebene enthaltener Komponenten, sehen Sie bitte <ulink url=\"http://www.jboss.com/products/"
-"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
-"platforms/application/testedconfigurations</ulink>. Das Installationshandbuch ist online unter <ulink url=\"http://www.redhat.com/"
-"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
-"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> verfügbar und enthält ausführliche Anleitungen zur Installation und Verifizierung der JBoss Enterprise Application Platform."
+"Sie müssen über ausreichend Platz auf der Disk verfügen, um JDK und JBoss "
+"Enterprise Application Platform zu installieren und auch für Ihre Anwendung "
+"noch genug Platz haben. Sie benötigen eine funktionierende Installation von "
+"JDK 1.5. Für aktuelle Informationen zu unterstützten Betriebssystem-/JVM-"
+"Kombinationen, unterstützten Datenbankplattformen sowie aktuellen Infos zur "
+"Revisionsebene enthaltener Komponenten, sehen Sie bitte <ulink url=\"http://"
+"www.jboss.com/products/platforms/application/testedconfigurations\">http://"
+"www.jboss.com/products/platforms/application/testedconfigurations</ulink>. "
+"Das Installationshandbuch ist online unter <ulink url=\"http://www.redhat."
+"com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat."
+"com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> verfügbar und "
+"enthält ausführliche Anleitungen zur Installation und Verifizierung der "
+"JBoss Enterprise Application Platform."
 
 #. Tag: title
 #: readme.xml:59
@@ -186,7 +219,8 @@
 msgstr ""
 "Siehe <ulink url=\"https://network.jboss.com/confluence/display/DOC/"
 "Installing+a+Patch\">https://network.jboss.com/confluence/display/DOC/"
-"Installing+a+Patch</ulink> für Anleitungen zur Installation eines \"Cumulative Patch\"."
+"Installing+a+Patch</ulink> für Anleitungen zur Installation eines "
+"\"Cumulative Patch\"."
 
 #. Tag: title
 #: readme.xml:72
@@ -209,7 +243,13 @@
 "configuration may result in memory issues. Note that the default "
 "configuration for the server to start with, if no other configuration is "
 "specified, is the production configuration."
-msgstr "Es wird empfohlen, die in der Dokumentation enthaltenen Seam-Beispielanwendungen unter Verwendung der Produktionskonfiguration auszuführen. Die Verwendung einer anderen Konfiguration kann zu Speicherproblemen führen. Beachten Sie bitte, dass die Standard-Startkonfiguration des Servers die Produktionskonfiguration ist, wenn keine andere festgelegt wird."
+msgstr ""
+"Es wird empfohlen, die in der Dokumentation enthaltenen Seam-"
+"Beispielanwendungen unter Verwendung der Produktionskonfiguration "
+"auszuführen. Die Verwendung einer anderen Konfiguration kann zu "
+"Speicherproblemen führen. Beachten Sie bitte, dass die Standard-"
+"Startkonfiguration des Servers die Produktionskonfiguration ist, wenn keine "
+"andere festgelegt wird."
 
 #. Tag: para
 #: readme.xml:81
@@ -220,8 +260,11 @@
 "settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
 "conf</filename> with these recommended values:"
 msgstr ""
-"Um Speicherprobleme zu vermeiden, passen Sie die Speichereinstellungen vor dem Deployment der Anwendungen an. Sie können dies durch ein Update der Einstellungen in der Datei <literal>JAVA_OPTS</literal> <filename>JBOSS_DIST/jboss-as/server/production/run."
-"conf</filename> mit folgenden empfohlenen Werten tun:"
+"Um Speicherprobleme zu vermeiden, passen Sie die Speichereinstellungen vor "
+"dem Deployment der Anwendungen an. Sie können dies durch ein Update der "
+"Einstellungen in der Datei <literal>JAVA_OPTS</literal> <filename>JBOSS_DIST/"
+"jboss-as/server/production/run.conf</filename> mit folgenden empfohlenen "
+"Werten tun:"
 
 #. Tag: programlisting
 #: readme.xml:83
@@ -238,8 +281,11 @@
 "important information regarding the deployment of Seam examples and detailed "
 "information on developing applications using Seam."
 msgstr ""
-"Im Seam Referenzhandbuch (\"Seam Reference Guide\") das im Dokumentationssatz eingeschlossen ist"
-"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) finden Sie wichtige Informationen zum Deploment von Seam-Beispielen sowie ausführliche Informationen zur Entwicklung von Anwendungen unter Verwendung von Seam."
+"Im Seam Referenzhandbuch (\"Seam Reference Guide\") das im "
+"Dokumentationssatz eingeschlossen ist(<filename>JBOSS_DIST/doc/seam/"
+"Seam_Reference_Guide.pdf</filename>) finden Sie wichtige Informationen zum "
+"Deploment von Seam-Beispielen sowie ausführliche Informationen zur "
+"Entwicklung von Anwendungen unter Verwendung von Seam."
 
 #. Tag: title
 #: readme.xml:94
@@ -258,11 +304,13 @@
 "faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
 "ulink> for information on how to make the services accessible again."
 msgstr ""
-"Falls Sie die rpm oder zip-Distribution verwenden, beachten Sie bitte, dass standardmäßig die Authentifikation aktiviert ist und keine Benutzerkonten eingerichtet sind."
-"Dies ist der Fall, um den nicht autorisierten Zugriff auf verschiedene "
-"JBoss AS Dienste zu verhindern. Informationen dazu, wie Sie diese Dienste wieder verfügbar machen, finden Sie im Installationshandbuch (Installation Guide) oder unter <ulink url=\"http://kbase.redhat.com/"
-"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
-"ulink>."
+"Falls Sie die rpm oder zip-Distribution verwenden, beachten Sie bitte, dass "
+"standardmäßig die Authentifikation aktiviert ist und keine Benutzerkonten "
+"eingerichtet sind.Dies ist der Fall, um den nicht autorisierten Zugriff auf "
+"verschiedene JBoss AS Dienste zu verhindern. Informationen dazu, wie Sie "
+"diese Dienste wieder verfügbar machen, finden Sie im Installationshandbuch "
+"(Installation Guide) oder unter <ulink url=\"http://kbase.redhat.com/faq/"
+"FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</ulink>."
 
 #. Tag: title
 #: readme.xml:102
@@ -280,7 +328,14 @@
 "component, and while we are happy to accept bugs filed against this "
 "component, we do not make any commitment to fix them within a specific "
 "timeframe."
-msgstr "Hypersonic SQL liefert standardmäßige und gleich einsetzbare Datenbankfunktionalität für den ausschließlichen Gebrauch bei Evaluierung und Entwicklung. Diese wird NICHT als Datenbank bei der Produktion empfohlen oder unterstützt. Für diese Komponente ist kein technischer Support verfügbar, und während wir uns über Meldungen zu Fehlern bei dieser Komponente freuen, garantieren wir keinen zeitlichen Rahmen innerhalb dessen diese behoben werden."
+msgstr ""
+"Hypersonic SQL liefert standardmäßige und gleich einsetzbare "
+"Datenbankfunktionalität für den ausschließlichen Gebrauch bei Evaluierung "
+"und Entwicklung. Diese wird NICHT als Datenbank bei der Produktion empfohlen "
+"oder unterstützt. Für diese Komponente ist kein technischer Support "
+"verfügbar, und während wir uns über Meldungen zu Fehlern bei dieser "
+"Komponente freuen, garantieren wir keinen zeitlichen Rahmen innerhalb dessen "
+"diese behoben werden."
 
 #. Tag: title
 #: readme.xml:110
@@ -297,20 +352,25 @@
 #. Tag: ulink
 #: readme.xml:116
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:120
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:124
 #, no-c-format
 msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
 
 #. Tag: title
 #: readme.xml:131
@@ -430,7 +490,9 @@
 msgid ""
 "Refer to the index.html file in the documentation directory for a list of "
 "included documentation."
-msgstr "In der index.html-Datei im Dokumentationsverzeichnis finden Sie eine Liste der enthaltenen Dokumentation."
+msgstr ""
+"In der index.html-Datei im Dokumentationsverzeichnis finden Sie eine Liste "
+"der enthaltenen Dokumentation."
 
 #. Tag: para
 #: readme.xml:223
@@ -440,8 +502,9 @@
 "components is distributed in a separate zip file, <filename>jboss-eap-docs-"
 "&lt;version&gt;.zip</filename>."
 msgstr ""
-"In der Zip-Distribution sind Dokumentation für die Plattform und deren individuelle Komponenten in einer separaten Zip-Datei <filename>jboss-eap-docs-"
-"&lt;version&gt;.zip</filename> distribuiert."
+"In der Zip-Distribution sind Dokumentation für die Plattform und deren "
+"individuelle Komponenten in einer separaten Zip-Datei <filename>jboss-eap-"
+"docs-&lt;version&gt;.zip</filename> distribuiert."
 
 #. Tag: para
 #: readme.xml:227
@@ -455,10 +518,12 @@
 "at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
 "redhat.com/faq/FAQ_35_198.shtm</ulink>"
 msgstr ""
-"In einem Linux-System befindet sich die Dokumentation in zwei rpms, die manuell installiert werden müssen. Diese rpms sind <filename>jboss-seam-docs-&lt;"
-"version&gt;.noarch.rpm</filename> und <filename>rh-eap-docs-&lt;version&gt;."
-"noarch.rpm</filename>. Hilfe zur Installation von rpm-Paketen in Red Hat "
-"Enterprise Linux finden Sie im Red Hat Knowledge Artikel unter <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"In einem Linux-System befindet sich die Dokumentation in zwei rpms, die "
+"manuell installiert werden müssen. Diese rpms sind <filename>jboss-seam-docs-"
+"&lt;version&gt;.noarch.rpm</filename> und <filename>rh-eap-docs-&lt;"
+"version&gt;.noarch.rpm</filename>. Hilfe zur Installation von rpm-Paketen in "
+"Red Hat Enterprise Linux finden Sie im Red Hat Knowledge Artikel unter "
+"<ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
 "redhat.com/faq/FAQ_35_198.shtm</ulink>"
 
 #. Tag: para
@@ -468,7 +533,10 @@
 "<filename>Installation Guide</filename> explains how to install and verify "
 "the installation of JBoss Enteprise Application Platform using different "
 "installation modes."
-msgstr "Der <filename>Installation Guide</filename> erläutert, wie die JBoss Enterprise Application Platform mittels anderer Installationsmodi installiert und verifiziert wird."
+msgstr ""
+"Der <filename>Installation Guide</filename> erläutert, wie die JBoss "
+"Enterprise Application Platform mittels anderer Installationsmodi "
+"installiert und verifiziert wird."
 
 #. Tag: para
 #: readme.xml:239
@@ -480,8 +548,12 @@
 "illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
 "the JSF and EJB3 components."
 msgstr ""
-"<filename>Getting Started</filename> erläutert die Verzeichnisstruktur der Plattform sowie eine kurze Übersicht über der Applikationsserver"
-"und verschiedene Konfigurationseinstellungen und -dienste. Anhand einer einfachen Webanwendung werden die Verwendung der JSF-EJB3 Komponenten sowie die Verwendung von Seam zur Integration der JSF und EJB3-Komponenten dargestellt."
+"<filename>Getting Started</filename> erläutert die Verzeichnisstruktur der "
+"Plattform sowie eine kurze Übersicht über der Applikationsserverund "
+"verschiedene Konfigurationseinstellungen und -dienste. Anhand einer "
+"einfachen Webanwendung werden die Verwendung der JSF-EJB3 Komponenten sowie "
+"die Verwendung von Seam zur Integration der JSF und EJB3-Komponenten "
+"dargestellt."
 
 #. Tag: para
 #: readme.xml:244
@@ -489,7 +561,9 @@
 msgid ""
 "<filename>Server Configuration Guide</filename> explains all administrative "
 "and configuration functions in detail."
-msgstr "Der <filename>Server Configuration Guide</filename> erläutert alle administrativen sowie Konfigurationsfunktionen im einzelnen."
+msgstr ""
+"Der <filename>Server Configuration Guide</filename> erläutert alle "
+"administrativen sowie Konfigurationsfunktionen im einzelnen."
 
 #. Tag: para
 #: readme.xml:250
@@ -501,10 +575,12 @@
 "redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
 "redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
 msgstr ""
-"Aktualisierte Versionen der Dokumentation mit Errata und zusätzlichen"
-"Informationen, Beispielen des Anwendungscode sowie der aktuellsten Version der Release Notes finden Sie im Web unter <ulink url=\"http://www."
-"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
-"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+"Aktualisierte Versionen der Dokumentation mit Errata und "
+"zusätzlichenInformationen, Beispielen des Anwendungscode sowie der "
+"aktuellsten Version der Release Notes finden Sie im Web unter <ulink url="
+"\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"
+"\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</"
+"ulink>."
 
 #. Tag: title
 #: readme.xml:265
@@ -516,7 +592,8 @@
 #: readme.xml:269
 #, no-c-format
 msgid "Following is a list of issues fixed in this release:"
-msgstr "Nachfolgend sehen Sie eine Liste von in dieser Release behobenen Problemen:"
+msgstr ""
+"Nachfolgend sehen Sie eine Liste von in dieser Release behobenen Problemen:"
 
 #. Tag: para
 #: readme.xml:277
@@ -527,7 +604,9 @@
 "update includes numerious bug fixes that improves the overall component."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-925\">JBPAPP-925</"
-"ulink>: Es fand ein Upgrade von JBoss Messaging zu Version 1.4.0.SP3_CP03 statt. Diese Aktualisierung behebt zahlreiche Fehler und verbessert die Komponente insgesamt."
+"ulink>: Es fand ein Upgrade von JBoss Messaging zu Version 1.4.0.SP3_CP03 "
+"statt. Diese Aktualisierung behebt zahlreiche Fehler und verbessert die "
+"Komponente insgesamt."
 
 #. Tag: para
 #: readme.xml:282
@@ -551,7 +630,9 @@
 "configuration has now been corrected."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
-"ulink>: Die SQL-Standardkonfiguration hatte Fehler, die zu einem Problem mit hsqldb führten, das diese Konfiguration verwendet. Das Problem mit der Standardkonfiguration ist jetzt behoben."
+"ulink>: Die SQL-Standardkonfiguration hatte Fehler, die zu einem Problem mit "
+"hsqldb führten, das diese Konfiguration verwendet. Das Problem mit der "
+"Standardkonfiguration ist jetzt behoben."
 
 #. Tag: para
 #: readme.xml:292
@@ -564,7 +645,10 @@
 "creating a more stable Messaging component."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-813\">JBPAPP-813</"
-"ulink>: Der Messaging Client enthielt einen Bug, der dazu führte, dass dieser dauerhaft hängenblieb, wodurch ein <code>ClusteredConnectionFactory</code>-Failover entstand. Dieses Problem wurde in der aktuellen EAP-Release nun behoben, so dass eine stabilere Messaging-Komponente existiert."
+"ulink>: Der Messaging Client enthielt einen Bug, der dazu führte, dass "
+"dieser dauerhaft hängenblieb, wodurch ein <code>ClusteredConnectionFactory</"
+"code>-Failover entstand. Dieses Problem wurde in der aktuellen EAP-Release "
+"nun behoben, so dass eine stabilere Messaging-Komponente existiert."
 
 #. Tag: title
 #: readme.xml:311
@@ -581,7 +665,8 @@
 "2.2.2.SP8. This upgrade includes numerious bug fixes."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
-"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version 2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
+"ulink>: Es fand ein Upgrade der JBoss Remoting Komponente des EAP zu Version "
+"2.2.2.SP8 statt. Dieses Upgrade enthält zahlreiche Fehlerbehebungen."
 
 #. Tag: title
 #: readme.xml:323
@@ -598,8 +683,8 @@
 "CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-930\">JBPAPP-930</"
-"ulink>: Das Upgrade zu JBossWS Common 1.0.0.GA_CP01 ist in dieser "
-"CP Release enthalten."
+"ulink>: Das Upgrade zu JBossWS Common 1.0.0.GA_CP01 ist in dieser CP Release "
+"enthalten."
 
 #. Tag: para
 #: readme.xml:332
@@ -610,7 +695,8 @@
 "version 1.2.0.SP1 which addresses various bugs."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-887\">JBPAPP-887</"
-"ulink>: JBoss Java API für XML Redistries (JAXR) erhielt ein Upgrade zu Version 1.2.0.SP1, das eine Reihe verschiedener Fehler behebt."
+"ulink>: JBoss Java API für XML Redistries (JAXR) erhielt ein Upgrade zu "
+"Version 1.2.0.SP1, das eine Reihe verschiedener Fehler behebt."
 
 #. Tag: para
 #: readme.xml:337
@@ -621,8 +707,9 @@
 "SP2_CP02. This upgrade incorporates various bug fixes and enhancements."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
-"ulink>: Es fand ein Upgrade der JBoss Web Services Komponente zu Version 2.0.1."
-"SP2_CP02 statt. Dieses Upgrade beinhaltet verschiedene Fehlerbehebungen und Verbesserungen."
+"ulink>: Es fand ein Upgrade der JBoss Web Services Komponente zu Version "
+"2.0.1.SP2_CP02 statt. Dieses Upgrade beinhaltet verschiedene "
+"Fehlerbehebungen und Verbesserungen."
 
 #. Tag: title
 #: readme.xml:345
@@ -641,7 +728,8 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-755\">JBPAPP-755</"
 "ulink>: Die Seam Quell-readme.txt-Datei erforderte aktualisierte Links zu "
-"seamframework.org und erwähnt EAP statt JBoss AS. Diese Datei wurde in dieser Release mit den obigen Änderungen aktualisiert."
+"seamframework.org und erwähnt EAP statt JBoss AS. Diese Datei wurde in "
+"dieser Release mit den obigen Änderungen aktualisiert."
 
 #. Tag: title
 #: readme.xml:357
@@ -662,9 +750,13 @@
 "()</methodname> to <filename>MergeTest.java</filename>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-938\">JBPAPP-938</"
-"ulink>: Bei einer unveränderten übergeordnete Entity würde zu Unrecht der Versionswert erhöht, wenn sie Teil einer \"One-to-Many\"-Beziehung wäre. Dieser Fehler wurde in der aktuellen CP-Release durch Korrektur eines Problems in der "
-"<filename>CollectionType.java</filename>-Datei und Hinzufügen der neuen Methode namens <methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection"
-"()</methodname> zu <filename>MergeTest.java</filename> behoben."
+"ulink>: Bei einer unveränderten übergeordnete Entity würde zu Unrecht der "
+"Versionswert erhöht, wenn sie Teil einer \"One-to-Many\"-Beziehung wäre. "
+"Dieser Fehler wurde in der aktuellen CP-Release durch Korrektur eines "
+"Problems in der <filename>CollectionType.java</filename>-Datei und "
+"Hinzufügen der neuen Methode namens "
+"<methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection()</"
+"methodname> zu <filename>MergeTest.java</filename> behoben."
 
 #. Tag: para
 #: readme.xml:366
@@ -681,8 +773,12 @@
 "<emphasis>junitinstrument</emphasis> test now runs successfully."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-936\">JBPAPP-936</"
-"ulink>: Die <methodname>AnnotationBinder.mustBeSkipped</methodname>-Methode besaß eine inkorrekt hardkodierte String-Referenz zur <classname>org.hibernate."
-"tool.instrument.javassist.FieldHandler</classname>-Klasse. Aufgrund diesen Fehlers lief der <emphasis>junitinstrument</emphasis>-Test nicht ordnungsgemäß. Das Problem wurde jetzt behoben, wobei der korrekte Speicherort des Pakets durch den Klassennamen <classname>org.hibernate."
+"ulink>: Die <methodname>AnnotationBinder.mustBeSkipped</methodname>-Methode "
+"besaß eine inkorrekt hardkodierte String-Referenz zur <classname>org."
+"hibernate.tool.instrument.javassist.FieldHandler</classname>-Klasse. "
+"Aufgrund diesen Fehlers lief der <emphasis>junitinstrument</emphasis>-Test "
+"nicht ordnungsgemäß. Das Problem wurde jetzt behoben, wobei der korrekte "
+"Speicherort des Pakets durch den Klassennamen <classname>org.hibernate."
 "bytecode.javassist.FieldHandler</classname> referenziert ist und der "
 "<emphasis>junitinstrument</emphasis>-Test nun erfolgreich läuft."
 
@@ -697,7 +793,10 @@
 "supporting JDK 6."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-915\">JBPAPP-915</"
-"ulink>: Eine Misch-Operation (\"merge\") würde fehlschlagen, wenn eine transiente Entity vorhanden wäre, die durch mehrere Pfade erreichbar wäre, von denen mindestens einer bei einem Merge-Vorgang nicht kaskadieren würde. Dieses Problem ist damit behoben, dass EAP 4.3 jetzt JDK 6 unterstützt."
+"ulink>: Eine Misch-Operation (\"merge\") würde fehlschlagen, wenn eine "
+"transiente Entity vorhanden wäre, die durch mehrere Pfade erreichbar wäre, "
+"von denen mindestens einer bei einem Merge-Vorgang nicht kaskadieren würde. "
+"Dieses Problem ist damit behoben, dass EAP 4.3 jetzt JDK 6 unterstützt."
 
 #. Tag: para
 #: readme.xml:376
@@ -710,7 +809,8 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-908\">JBPAPP-908</"
 "ulink>: Hibernate Proxy-Serialisierung funktionierte nicht, weil die "
-"<classname>AbstractLazyInitializer</classname>-Klasse nicht serialisierbar war. Dies wurde in dieser CP-Release behoben."
+"<classname>AbstractLazyInitializer</classname>-Klasse nicht serialisierbar "
+"war. Dies wurde in dieser CP-Release behoben."
 
 #. Tag: para
 #: readme.xml:381
@@ -725,7 +825,8 @@
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-899\">JBPAPP-899</"
 "ulink>: Es gab einen Fehler innerhalb des Entity-Managers wobei Methoden "
 "<methodname>getSingleResult()</methodname> und <methodname>fetch()</"
-"methodname> eine <code>NonUniqueResultException</code> wiedergaben, weil Elemente nicht eindeutig waren. Dies wurde in dieser CP-Release behoben."
+"methodname> eine <code>NonUniqueResultException</code> wiedergaben, weil "
+"Elemente nicht eindeutig waren. Dies wurde in dieser CP-Release behoben."
 
 #. Tag: para
 #: readme.xml:386
@@ -737,7 +838,9 @@
 "on error</option>, <option>format</option> options now avaliable."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-859\">JBPAPP-859</"
-"ulink>: Die <classname>SchemaUpdate</classname>-Klasse wurde durch die jetzt verfügbaren Optionen <option>output file name</option>, <option>delimiter</option>, <option>halt on error</option>, <option>format</option> verbessert."
+"ulink>: Die <classname>SchemaUpdate</classname>-Klasse wurde durch die jetzt "
+"verfügbaren Optionen <option>output file name</option>, <option>delimiter</"
+"option>, <option>halt on error</option>, <option>format</option> verbessert."
 
 #. Tag: para
 #: readme.xml:391
@@ -750,7 +853,11 @@
 "EAP and Oracle. This issue has now been rectified in this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-782\">JBPAPP-782</"
-"ulink>: Die <classname>MapBinder</classname>-Klasse besaß die Fähigkeit zur Generierung von SQL-Anweisungen, die durch die Oracle 10g Datenbank nicht unterstützt wurden. Dies war insbesondere für einige Benutzer von EJB3 Persistenz auf EAP und Oracle problematisch. Das Problem wurde in dieser CP-Release behoben."
+"ulink>: Die <classname>MapBinder</classname>-Klasse besaß die Fähigkeit zur "
+"Generierung von SQL-Anweisungen, die durch die Oracle 10g Datenbank nicht "
+"unterstützt wurden. Dies war insbesondere für einige Benutzer von EJB3 "
+"Persistenz auf EAP und Oracle problematisch. Das Problem wurde in dieser CP-"
+"Release behoben."
 
 #. Tag: title
 #: readme.xml:410
@@ -782,7 +889,9 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1004\">JBPAPP-1004</"
 "ulink>: Frühere Versionen des EAP enthielten eine inkorrekte "
-"<property>serialVersionUID</property>-Nummer, die sich störend auf die rückwärtige Kompatibilität auswirkte. Die korrekte <property>serialVersionUID</property>-Nummer ist in dieser Release enthalten."
+"<property>serialVersionUID</property>-Nummer, die sich störend auf die "
+"rückwärtige Kompatibilität auswirkte. Die korrekte "
+"<property>serialVersionUID</property>-Nummer ist in dieser Release enthalten."
 
 #. Tag: title
 #: readme.xml:428
@@ -799,7 +908,8 @@
 "1.5.GA_CP02."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-972\">JBPAPP-972</"
-"ulink>: Von JBoss Aspect-Oriented Programming (AOP) fand ein Upgrade zu Version 1.5.GA_CP02 statt."
+"ulink>: Von JBoss Aspect-Oriented Programming (AOP) fand ein Upgrade zu "
+"Version 1.5.GA_CP02 statt."
 
 #. Tag: title
 #: readme.xml:434
@@ -816,7 +926,8 @@
 "issues related to this class library."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-971\">JBPAPP-971</"
-"ulink>: Bei Javassist fand ein Upgrade zu Version 3.8.0.GA statt, wobei zahlreiche Probleme dieser Klassenbibliothek behoben wurden."
+"ulink>: Bei Javassist fand ein Upgrade zu Version 3.8.0.GA statt, wobei "
+"zahlreiche Probleme dieser Klassenbibliothek behoben wurden."
 
 #. Tag: title
 #: readme.xml:440
@@ -855,10 +966,15 @@
 "attribute&gt;</programlisting>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-944\">JBPAPP-944</"
-"ulink>: <classname>ClusteredSession</classname> enthielt Logik, die Session-Metadaten-Replikation übersprang, wenn die einzige Veränderung den Zeitstempel betraf. Dieses Problem wurde behoben, indem der standardmäßige maximale Intervall zwischen Anfrage verändert wurde. Der Standardintervall beträgt jetzt 60 Sekunden und der Wert ist nun konfigurierbar. Dieses Attribut kann durch hinzufügen eines Attributs zur "
-"<filename>jboss-service.xml</filename>-Datei verändert werden, was "
-"<programlisting>&lt;attribute name=\"MaxUnreplicatedInterval\"&gt;30&lt;/"
-"attribute&gt;</programlisting> entspricht."
+"ulink>: <classname>ClusteredSession</classname> enthielt Logik, die Session-"
+"Metadaten-Replikation übersprang, wenn die einzige Veränderung den "
+"Zeitstempel betraf. Dieses Problem wurde behoben, indem der standardmäßige "
+"maximale Intervall zwischen Anfrage verändert wurde. Der Standardintervall "
+"beträgt jetzt 60 Sekunden und der Wert ist nun konfigurierbar. Dieses "
+"Attribut kann durch hinzufügen eines Attributs zur <filename>jboss-service."
+"xml</filename>-Datei verändert werden, was <programlisting>&lt;attribute "
+"name=\"MaxUnreplicatedInterval\"&gt;30&lt;/attribute&gt;</programlisting> "
+"entspricht."
 
 #. Tag: title
 #: readme.xml:452
@@ -878,8 +994,12 @@
 "classes affected."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-926\">JBPAPP-926</"
-"ulink>: Ein Abschnitt des Server Configuration Guide (Handbuch zur Serverkonfiguration) namens "
-"<emphasis>Existing Entity Commands</emphasis> (Bestehende Entity-Befehle) legte für einige Klassen die falschen Pakete fest. Diese aktualisierte Version des Handbuchs zur Serverkonfiguration mit dieser CP, enthält die korrekten Paketinformationen für die betroffenen Klassen."
+"ulink>: Ein Abschnitt des Server Configuration Guide (Handbuch zur "
+"Serverkonfiguration) namens <emphasis>Existing Entity Commands</emphasis> "
+"(Bestehende Entity-Befehle) legte für einige Klassen die falschen Pakete "
+"fest. Diese aktualisierte Version des Handbuchs zur Serverkonfiguration mit "
+"dieser CP, enthält die korrekten Paketinformationen für die betroffenen "
+"Klassen."
 
 #. Tag: title
 #: readme.xml:458
@@ -898,8 +1018,10 @@
 "ClassLoader.allowArraySyntax=true</programlisting>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-907\">JBPAPP-907</"
-"ulink>: Es gab ein Problem, bei dem ein Deserialisierungsengpass in Arrays für JDK 1.6 vorkam. Um dies zu beheben, wurde folgendes der <filename>run.conf</filename>-Datei hinzugefügt: <programlisting>-Dsun.lang."
-"ClassLoader.allowArraySyntax=true</programlisting>."
+"ulink>: Es gab ein Problem, bei dem ein Deserialisierungsengpass in Arrays "
+"für JDK 1.6 vorkam. Um dies zu beheben, wurde folgendes der <filename>run."
+"conf</filename>-Datei hinzugefügt: <programlisting>-Dsun.lang.ClassLoader."
+"allowArraySyntax=true</programlisting>."
 
 #. Tag: title
 #: readme.xml:464
@@ -916,7 +1038,8 @@
 "CP02."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-897\">JBPAPP-897</"
-"ulink>: Es fand ein Upgrade der JBoss Transaction Services zu Version 4.2.3 SP5 CP02 statt."
+"ulink>: Es fand ein Upgrade der JBoss Transaction Services zu Version 4.2.3 "
+"SP5 CP02 statt."
 
 #. Tag: title
 #: readme.xml:470
@@ -934,8 +1057,9 @@
 "These connections are now always closed to restrict exceptions."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-895\">JBPAPP-895</"
-"ulink>: Die Java Messaging Service (JMS) Verbindungen mussten in Referenz zur J2EE Connector Architecture (JCA) stets geschlossen sein. "
-"Diese Verbindungen sind jetzt immer geschlossen, um Ausnahmen einzuschränken."
+"ulink>: Die Java Messaging Service (JMS) Verbindungen mussten in Referenz "
+"zur J2EE Connector Architecture (JCA) stets geschlossen sein. Diese "
+"Verbindungen sind jetzt immer geschlossen, um Ausnahmen einzuschränken."
 
 #. Tag: title
 #: readme.xml:476
@@ -956,8 +1080,11 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-891\">JBPAPP-891</"
 "ulink>: Das Monitoring-Tool <emphasis>Twiddle</emphasis> druckte keine  "
-"<code>invoke</code>-Ergebnisse selbst wenn ein Property-Editor für "
-"das wiedergegebene Objekt fehlte. Innerhalb dieser CP-Release nun korrigiert, so dass <emphasis>Twiddle</emphasis> jetzt die <methodname>toString()</methodname>-Methode an wiedergegebenen Objekten aufruft, wenn kein Property-Editor aufgefunden wird."
+"<code>invoke</code>-Ergebnisse selbst wenn ein Property-Editor für das "
+"wiedergegebene Objekt fehlte. Innerhalb dieser CP-Release nun korrigiert, so "
+"dass <emphasis>Twiddle</emphasis> jetzt die <methodname>toString()</"
+"methodname>-Methode an wiedergegebenen Objekten aufruft, wenn kein Property-"
+"Editor aufgefunden wird."
 
 #. Tag: title
 #: readme.xml:488
@@ -975,7 +1102,9 @@
 "issue so that serialization functions correctly."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-877\">JBPAPP-877</"
-"ulink>: JBoss Serialization Version 1.0.3GA würde bei Verwendung zur Meldung von <code>ClassCastExceptions</code> führen. Dieses Update behebt dieses Problem, so dass Serialisierung ordnungsgemäß funktioniert."
+"ulink>: JBoss Serialization Version 1.0.3GA würde bei Verwendung zur Meldung "
+"von <code>ClassCastExceptions</code> führen. Dieses Update behebt dieses "
+"Problem, so dass Serialisierung ordnungsgemäß funktioniert."
 
 #. Tag: title
 #: readme.xml:494
@@ -993,7 +1122,10 @@
 "enhancement to the EAP is included within this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-867\">JBPAPP-867</"
-"ulink>: Eine Implementierung des <interfacename>ExceptionSorter</interfacename>-Interface sollte für Benutzer des IBM DB2 Data Server bereitgestellt werden. Diese Verbesserung des EAP ist in dieser CP-Release enthalten."
+"ulink>: Eine Implementierung des <interfacename>ExceptionSorter</"
+"interfacename>-Interface sollte für Benutzer des IBM DB2 Data Server "
+"bereitgestellt werden. Diese Verbesserung des EAP ist in dieser CP-Release "
+"enthalten."
 
 #. Tag: title
 #: readme.xml:500
@@ -1013,8 +1145,11 @@
 "default policy for EJB2 home proxies."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-864\">JBPAPP-864</"
-"ulink>: Geclusterte Proxy-Factories banden keine Home-Proxies. Dieses Problem wurde behoben, und geclusterte Home-Proxies für EJB3-Beans werden jetzt unterstützt. "
-"Um jedoch Probleme mit rückwärtiger Kompatibilität zu vermeiden wurde die Load-Balance-Richtlinie für Home-Proxies zu \"Round-Robin\" hardkodiert. Dies ist auch die Standardrichtlinie für EJB2-Home-Proxies."
+"ulink>: Geclusterte Proxy-Factories banden keine Home-Proxies. Dieses "
+"Problem wurde behoben, und geclusterte Home-Proxies für EJB3-Beans werden "
+"jetzt unterstützt. Um jedoch Probleme mit rückwärtiger Kompatibilität zu "
+"vermeiden wurde die Load-Balance-Richtlinie für Home-Proxies zu \"Round-Robin"
+"\" hardkodiert. Dies ist auch die Standardrichtlinie für EJB2-Home-Proxies."
 
 #. Tag: title
 #: readme.xml:508
@@ -1032,7 +1167,9 @@
 "bin files."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>: Gestatten die Einstellung multipler Instanzen auf einer Machine unter Verwendung einer Subpackage-Methode. Diese Funktionalität wurde in dieser Release mit -bin Dateien hinzugefügt."
+"ulink>: Gestatten die Einstellung multipler Instanzen auf einer Machine "
+"unter Verwendung einer Subpackage-Methode. Diese Funktionalität wurde in "
+"dieser Release mit -bin Dateien hinzugefügt."
 
 #. Tag: para
 #: readme.xml:513
@@ -1044,8 +1181,12 @@
 "jbossas installation. If you only have one version of the AS, it will have "
 "to be the regular RPM installation (or ZIP or installer for older versions)."
 msgstr ""
-"Es ist wichtig, dass eine reguläre jbossas-Installation ivor der Installation der -bin auf dem Server vorhanden ist. Die -bin ist lediglich für eine zusätzliche Installation und kann nicht anstatt einer regulären RPM "
-"jbossas Installation verwendet werden. Falls Sie nur eine Version des AS besitzen, so muss es die reguläre RPM-Installation sein (oder ZIP oder Installer für ältere Versionen)."
+"Es ist wichtig, dass eine reguläre jbossas-Installation ivor der "
+"Installation der -bin auf dem Server vorhanden ist. Die -bin ist lediglich "
+"für eine zusätzliche Installation und kann nicht anstatt einer regulären RPM "
+"jbossas Installation verwendet werden. Falls Sie nur eine Version des AS "
+"besitzen, so muss es die reguläre RPM-Installation sein (oder ZIP oder "
+"Installer für ältere Versionen)."
 
 #. Tag: title
 #: readme.xml:517
@@ -1063,7 +1204,9 @@
 "from the distribution. This missing file has now been re-included."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-857\">JBPAPP-857</"
-"ulink>: Die innerhalb des Applikationsservers zum Empfang von E-Mails mittels JavaMail API verwendete .rar-Datei <filename>mail-ra.rar</filename> fehlte in der Distribution. Diese fehlende Datei ist nun wieder enthalten."
+"ulink>: Die innerhalb des Applikationsservers zum Empfang von E-Mails "
+"mittels JavaMail API verwendete .rar-Datei <filename>mail-ra.rar</filename> "
+"fehlte in der Distribution. Diese fehlende Datei ist nun wieder enthalten."
 
 #. Tag: title
 #: readme.xml:523
@@ -1082,7 +1225,9 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-856\">JBPAPP-856</"
 "ulink>: Support der DeliveryActive MDB Aktivierungskonfigurations-Property "
-"beim Deployment. Dieser Mechanismus aktiviert die Fähigkeit zum Starten und Stoppen des Verbrauchs von Nachrichten während des Deployments und wird in dieser Release unterstützt."
+"beim Deployment. Dieser Mechanismus aktiviert die Fähigkeit zum Starten und "
+"Stoppen des Verbrauchs von Nachrichten während des Deployments und wird in "
+"dieser Release unterstützt."
 
 #. Tag: title
 #: readme.xml:529
@@ -1103,10 +1248,14 @@
 "With these changes the example now functions correctly under SQL Server 2005."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-844\">JBPAPP-844</"
-"ulink>: Das MSSQL-Datenquellenbeispiel war nicht kompatibel mit dem SQL Server 2005. "
-"Um dieses Inkompatibilitätsproblem zu beheben wurde <code>driver-class</code> von <code>com.microsoft.jdbc.sqlserver.SQLServerDriver</code> zu "
-"<code>com.microsoft.sqlserver.jdbc.SQLServerDriver</code> aktualisiert und der Standard-Port für die <code>connection-url</code> wurde von 1433 zu 3918 geändert. "
-"Mit diesen Änderungen funktioniert das Beispiel nun unter dem SQL Server 2005 ordnungsgemäß."
+"ulink>: Das MSSQL-Datenquellenbeispiel war nicht kompatibel mit dem SQL "
+"Server 2005. Um dieses Inkompatibilitätsproblem zu beheben wurde "
+"<code>driver-class</code> von <code>com.microsoft.jdbc.sqlserver."
+"SQLServerDriver</code> zu <code>com.microsoft.sqlserver.jdbc."
+"SQLServerDriver</code> aktualisiert und der Standard-Port für die "
+"<code>connection-url</code> wurde von 1433 zu 3918 geändert. Mit diesen "
+"Änderungen funktioniert das Beispiel nun unter dem SQL Server 2005 "
+"ordnungsgemäß."
 
 #. Tag: title
 #: readme.xml:535
@@ -1127,9 +1276,12 @@
 "which has since been fixed."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-815\">JBPAPP-815</"
-"ulink>: Es gab ein Problem damit, dass wenn DOCTYPE der Datei <filename>-"
-"ds.xml</filename> hinzugefügt wurde und die Option <option>ValidateDTDs</option> in <filename>jbossjca-services.xml</filename> auf \"true\" gesetzt war Validierungsfehler auftraten. Der Grund hierfür war ein Problem mit dem <property>tx-"
-"connection-factory</property>-Element in <filename>jms-ds.xml</filename>, das jetzt behoben wurde."
+"ulink>: Es gab ein Problem damit, dass wenn DOCTYPE der Datei <filename>-ds."
+"xml</filename> hinzugefügt wurde und die Option <option>ValidateDTDs</"
+"option> in <filename>jbossjca-services.xml</filename> auf \"true\" gesetzt "
+"war Validierungsfehler auftraten. Der Grund hierfür war ein Problem mit dem "
+"<property>tx-connection-factory</property>-Element in <filename>jms-ds.xml</"
+"filename>, das jetzt behoben wurde."
 
 #. Tag: title
 #: readme.xml:541
@@ -1148,7 +1300,11 @@
 "has now been restored, enabling the example to be run correctly."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-805\">JBPAPP-805</"
-"ulink>: Es gab eine fehlende Java-Datei im ersten Sicherheitsbeispiel innerhalb des Handbuchs zur Server-Konfiguration, das dazu führte, das das Beispiel nicht erfolgreich ausgeführt werden konnte. Die fehlende <filename>EchoSecurityProxy.java</filename>-Datei wurde nun wieder hergestellt, so dass das Beispiel ordnungsgemäß ausgeführt werden kann."
+"ulink>: Es gab eine fehlende Java-Datei im ersten Sicherheitsbeispiel "
+"innerhalb des Handbuchs zur Server-Konfiguration, das dazu führte, das das "
+"Beispiel nicht erfolgreich ausgeführt werden konnte. Die fehlende "
+"<filename>EchoSecurityProxy.java</filename>-Datei wurde nun wieder "
+"hergestellt, so dass das Beispiel ordnungsgemäß ausgeführt werden kann."
 
 #. Tag: title
 #: readme.xml:547
@@ -1167,7 +1323,11 @@
 "issue and allowing the example to execute correctly."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-799\">JBPAPP-799</"
-"ulink>: Das seamejb3-Beispiel würde einen <code>FaceletException</code>-Fehler generieren. Ursache dieses Problems war der Einschluss inkorrekter .jar-Dateien für das Beispiel. Dieses CP-Update beinhaltet die korrekten .jar-Dateien, wodurch der Fehler behoben ist und das Beispiel ordnungsgemäß ausgeführt werden kann."
+"ulink>: Das seamejb3-Beispiel würde einen <code>FaceletException</code>-"
+"Fehler generieren. Ursache dieses Problems war der Einschluss inkorrekter ."
+"jar-Dateien für das Beispiel. Dieses CP-Update beinhaltet die korrekten .jar-"
+"Dateien, wodurch der Fehler behoben ist und das Beispiel ordnungsgemäß "
+"ausgeführt werden kann."
 
 #. Tag: title
 #: readme.xml:553
@@ -1185,7 +1345,9 @@
 "ability to accomplish this is now included."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-783\">JBPAPP-783</"
-"ulink>: Es gab ein Problem, weil ein Mechanismus zum Beenden von JMS-Verbindungen fehlte, wenn MDB auf eine <code>RuntimeException</code> traf. Die Möglichkeit hierfür ist jetzt enthalten."
+"ulink>: Es gab ein Problem, weil ein Mechanismus zum Beenden von JMS-"
+"Verbindungen fehlte, wenn MDB auf eine <code>RuntimeException</code> traf. "
+"Die Möglichkeit hierfür ist jetzt enthalten."
 
 #. Tag: title
 #: readme.xml:559
@@ -1204,7 +1366,10 @@
 "included within this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-746\">JBPAPP-746</"
-"ulink>: Es bestand ein Bug innerhalb des JavaServer Pages (JSP) Compilers, der Auswirkungen auf Tomcat hatte, wo der Körper der doTag()-Methode leer war. Dies bedeutete, dass kein html ausgegeben wurde. Dieses mit Tomcat zusammenhängende Problem wurde in dieser CP-Release behoben."
+"ulink>: Es bestand ein Bug innerhalb des JavaServer Pages (JSP) Compilers, "
+"der Auswirkungen auf Tomcat hatte, wo der Körper der doTag()-Methode leer "
+"war. Dies bedeutete, dass kein html ausgegeben wurde. Dieses mit Tomcat "
+"zusammenhängende Problem wurde in dieser CP-Release behoben."
 
 #. Tag: title
 #: readme.xml:565
@@ -1222,7 +1387,9 @@
 "URLs are decoded correctly after servelt redirects."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-729\">JBPAPP-729</"
-"ulink>: Ein falscher Zeichensatz wurde für die Dekodierung von URL-Parametern nach einem Servlet-Redirect verwendet. Innerhalb dieser CP nun behoben, werden URLs nun ordnungsgemäß nach Servelt-Redirects dekodiert."
+"ulink>: Ein falscher Zeichensatz wurde für die Dekodierung von URL-"
+"Parametern nach einem Servlet-Redirect verwendet. Innerhalb dieser CP nun "
+"behoben, werden URLs nun ordnungsgemäß nach Servelt-Redirects dekodiert."
 
 #. Tag: title
 #: readme.xml:571
@@ -1242,8 +1409,11 @@
 "the user is redirected to the displayMbeans page."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
-"ulink>: JavaServer Pages (JSP) Quellcode war innerhalb der jmx-"
-"Konsole offengelegt, wenn es zu einer Fehlerseite kam. Dieses Problem wurde behoben, indem geprüft wurde, ob die Klasse ein bestehendes  Bean vom angefragten Bereich verwendet oder ein neues instantiiert hat. Ist eines von angefragten Bereich Null, so wird der Nutzer zur displayMbeans-Seite umgeleitet."
+"ulink>: JavaServer Pages (JSP) Quellcode war innerhalb der jmx-Konsole "
+"offengelegt, wenn es zu einer Fehlerseite kam. Dieses Problem wurde behoben, "
+"indem geprüft wurde, ob die Klasse ein bestehendes  Bean vom angefragten "
+"Bereich verwendet oder ein neues instantiiert hat. Ist eines von angefragten "
+"Bereich Null, so wird der Nutzer zur displayMbeans-Seite umgeleitet."
 
 #. Tag: title
 #: readme.xml:577
@@ -1261,7 +1431,10 @@
 "optimization required is now included within this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-295\">JBPAPP-295</"
-"ulink>: Das replizierte Stateful Session Bean (SFSB) erforderte Optimierung für die Verwendung mit Buddy Replication. Nach ausführlichen Tests und Fehlerbehebung ist die benötigte Optimierung nun in dieser CP-Release enthalten."
+"ulink>: Das replizierte Stateful Session Bean (SFSB) erforderte Optimierung "
+"für die Verwendung mit Buddy Replication. Nach ausführlichen Tests und "
+"Fehlerbehebung ist die benötigte Optimierung nun in dieser CP-Release "
+"enthalten."
 
 #. Tag: title
 #: readme.xml:593
@@ -1273,7 +1446,8 @@
 #: readme.xml:596
 #, no-c-format
 msgid "Following is a list of known issues at the time of release."
-msgstr "Nachfolgend eine Liste der zum Zeitpunkt der Release bekannten Probleme."
+msgstr ""
+"Nachfolgend eine Liste der zum Zeitpunkt der Release bekannten Probleme."
 
 #. Tag: para
 #: readme.xml:601
@@ -1287,6 +1461,9 @@
 "performance."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
-"ulink>: Innerhalb der Hibernate-Komponente des EAP hat sich die Reihenfolge von HashMap und HashSet-Iteration im Vergleich zu früheren Releases wegen des Support für JDK 1.6 verändert. "
-"Dies bedeutete jedoch, dass die Reihenfolge von Spalten in Union-Clauses und Union-Subclasses sich verändert hat, wodurch es zu einer leichten Auswirkung auf die Komponenten-Performance kam."
-
+"ulink>: Innerhalb der Hibernate-Komponente des EAP hat sich die Reihenfolge "
+"von HashMap und HashSet-Iteration im Vergleich zu früheren Releases wegen "
+"des Support für JDK 1.6 verändert. Dies bedeutete jedoch, dass die "
+"Reihenfolge von Spalten in Union-Clauses und Union-Subclasses sich verändert "
+"hat, wodurch es zu einer leichten Auswirkung auf die Komponenten-Performance "
+"kam."

Modified: projects/docs/enterprise/4.3.4/readme/es-ES/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/es-ES/Author_Group.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/es-ES/Author_Group.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,13 +1,13 @@
-# translation of Author_Group.po to
+# translation of readme.po to
 # Language es-ES translations for readme package.
 # Automatically generated, 2008.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-07-29 14:00+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 11:00+1000\n"
 "Last-Translator: Angela Garcia\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -15,9 +15,10 @@
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.11.4\n"
 
-#. Tag: corpauthor
-#: Author_Group.xml:5
+#. Tag: author
+#: Author_Group.xml:6
 #, no-c-format
-msgid "Red Hat Documentation Group"
-msgstr "Grupo de documentación de Red Hat "
-
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/es-ES/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/es-ES/Book_Info.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/es-ES/Book_Info.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,13 +1,13 @@
-# translation of Book_Info.po to
+# translation of readme.po to
 # Language es-ES translations for readme package.
 # Automatically generated, 2008.
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-07-29 14:33+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 11:00+1000\n"
 "Last-Translator: Angela Garcia\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -17,33 +17,35 @@
 
 #. Tag: title
 #: Book_Info.xml:6
-#, no-c-format
-msgid "Release Notes"
+#, fuzzy, no-c-format
+msgid "Release Notes CP04"
 msgstr "Notas de Lanzamiento "
 
 #. Tag: subtitle
 #: Book_Info.xml:7
-#, no-c-format
-msgid "JBoss Enterprise Application Platform 4.3.0.CP02"
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
 msgstr "JBoss Enterprise Application Platform 4.3.0.CP02"
 
 #. Tag: para
-#: Book_Info.xml:11
-#, no-c-format
+#: Book_Info.xml:13
+#, fuzzy, no-c-format
 msgid ""
 "These release notes contain important information related to JBoss "
-"Enterprise Application Platform 4.3.0.CP02 that may not be currently "
+"Enterprise Application Platform 4.3.0.CP04 that may not be currently "
 "available in the Product Manuals. You should read these Release Notes in "
 "their entirety before installing JBoss Enterprise Application Platform 4.3.0."
-"CP02."
+"CP04."
 msgstr ""
-"Estas notas de lanzamiento contienen información importante relacionada con JBoss "
-"Enterprise Application Platform 4.3.0.CP02 que puede que no esté actualmente disponible en los manuales del producto. Debe leer estas notas de lanzamiento por completo antes de instalar JBoss Enterprise Application Platform 4.3.0."
-"CP02."
+"Estas notas de lanzamiento contienen información importante relacionada con "
+"JBoss Enterprise Application Platform 4.3.0.CP02 que puede que no esté "
+"actualmente disponible en los manuales del producto. Debe leer estas notas "
+"de lanzamiento por completo antes de instalar JBoss Enterprise Application "
+"Platform 4.3.0.CP02."
 
 #. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
 #, no-c-format
 msgid "&HOLDER;"
 msgstr "&HOLDER;"
-

Added: projects/docs/enterprise/4.3.4/readme/es-ES/Release_Notes_CP04.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/es-ES/Release_Notes_CP04.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/es-ES/Release_Notes_CP04.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,3080 @@
+# translation of readme.po to
+# Language es-ES translations for readme package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 11:00+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:9
+#, no-c-format
+msgid "Introduction"
+msgstr "Introducción "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:12
+#, no-c-format
+msgid ""
+"These release notes contain important information related to JBoss "
+"Enterprise Application Platform &VERSION;. New features, known problems, "
+"resources, and other current issues are addressed here."
+msgstr ""
+"Estas notas de lanzamiento contienen información importante relacionada con "
+"JBoss Enterprise Application Platform &VERSION;. Aquí abordamos las nuevas "
+"características, los problemas conocidos, los recursos y otros problemas "
+"actuales. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:16
+#, no-c-format
+msgid "Overview"
+msgstr "Sinopsis "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:17
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform is the next evolutionary step in open "
+"source enterprise software. It is a powerful tool for developing rich, high "
+"performance, Web 2.0 applications on a pure Java Platform."
+msgstr ""
+"JBoss Enterprise Application Platform es el siguiente paso en la evolución "
+"del software empresarial de código abierto. Es una herramienta poderosa para "
+"desarrollar aplicaciones Web 2.0 de alto rendimiento en una plataforma de "
+"Java pura. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:20
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform provides complete compatibility with "
+"existing J2EE 1.4 enterprise Java applications. At the same time, almost all "
+"the key features and components defined in the Java EE 5.0 specification are "
+"supported. So your new enterprise Java applications can take immediate "
+"advantage of the Java EE 5.0's significantly simpler POJO-based programming "
+"model."
+msgstr ""
+"JBoss Enterprise Application Platform proporciona una compatibilidad "
+"completa con las aplicaciones ya existentes de Java enterprise J2EE 1.4. Al "
+"mismo tiempo, se soportan casi todas la características y componentes claves "
+"definidos en la especificación Java EE 5.0. De esta manera sus nuevas "
+"aplicaciones Java empresariales pueden sacar ventaja de manera inmediata del "
+"modelo de programación con base en POJO mucho más simple de Java EE 5.0."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:23
+#, no-c-format
+msgid ""
+"Further, by integrating best-of-breed open source frameworks such as JBoss "
+"Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of "
+"innovations in the open source community. As well, JBoss Enterprise "
+"Application Platform is fully tested and supported by Red Hat, and is "
+"certified to work on many leading enterprise hardware and software products."
+msgstr ""
+"Además al integrar las mejores estructuras de código abierto tal como JBoss "
+"Seam, Hibernate, Tomcat y JBoss Cache - la platforma saca provecho de las "
+"innovaciones en la comunidad de código abierto. De la misma manera, JBoss "
+"Enterprise Application Platform ha sido probado por completo y es soportado "
+"por Red Hat y está certificado para trabajar con mucho del hardware "
+"empresarial y muchos de los productos software líderes del mercado. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:26
+#, no-c-format
+msgid ""
+"All of which means you can develop your new application taking advantage of "
+"Java EE 5.0 technologies immediately and with the confidence of knowing it "
+"will remain forward-compatible with future versions of the JBoss Platform."
+msgstr ""
+"Todo esto significa que puede desarrollar su nueva aplicación sacando "
+"ventaja de la tecnología Java EE 5.0 de manera inmediata y con la "
+"tranquilidad de saber que seguirá siendo compatible con las versiones "
+"futuras de la plataforma de JBoss."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:32
+#, no-c-format
+msgid "New Features in JBoss Enterprise Application Platform 4.3"
+msgstr "Nuevas características en JBoss Enterprise Application Platform 4.3 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:34 Release_Notes_CP04.xml:365
+#, no-c-format
+msgid "JBoss Messaging"
+msgstr "JBoss Messaging "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:35
+#, no-c-format
+msgid ""
+"In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
+"with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
+"messaging infrastructure for JBoss Enterprise Application Platform."
+msgstr ""
+"En JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 ha sido "
+"reemplazado por JBoss Messaging 1.4. JBoss Messaging proporciona una "
+"infraestructura de mensajes de alto rendimiento para la plataforma de "
+"aplicaciones empresariales de JBoss. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:40
+#, no-c-format
+msgid "JBoss Web Services 2.0.1"
+msgstr "JBoss Web Services 2.0.1 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:41
+#, no-c-format
+msgid ""
+"JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
+"Platform 4.3 and will now provide a complete implementation of JAX-WS."
+msgstr ""
+"JBoss Web Services se ha actualizado a 2.0.1 en JBoss Enterprise Application "
+"Platform 4.3 y ahora proporciona una implementación completa de JAX-WS. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:47
+#, no-c-format
+msgid "Component Versions"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:48
+#, no-c-format
+msgid ""
+"This section details the versions of the components which create the "
+"Enterprise Application Platform 4.3 that can be found in this Cumulative "
+"Patch release."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:53
+#, no-c-format
+msgid "JBoss Application Server 4.2.z"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:58
+#, no-c-format
+msgid "Hibernate Core 3.2.4.SP1.CP07"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:63
+#, no-c-format
+msgid "Hibernate Annotations 3.2.1.GA.CP03"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:68
+#, no-c-format
+msgid "Hibernate Entity Manager 3.2.1.GA_CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:73
+#, no-c-format
+msgid "JAF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:78
+#, no-c-format
+msgid "JBoss Cache 1.4.1.SP11"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:83
+#, no-c-format
+msgid "JBoss JAXR 1.2.0.SP2"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:88
+#, fuzzy, no-c-format
+msgid "JBoss Messaging 1.4.0.SP3-CP07"
+msgstr "JBoss Messaging "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:93
+#, fuzzy, no-c-format
+msgid "JBoss Remoting 2.2.2.SP11"
+msgstr "JBoss Remoting "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:98
+#, no-c-format
+msgid "JBoss Transactions 4.2.3.SP5.CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:103
+#, fuzzy, no-c-format
+msgid "JBoss Web 2.0.0-6.CP09"
+msgstr "JBoss Web Services 2.0.1 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:108
+#, fuzzy, no-c-format
+msgid "JBoss Web Services 2.0.1.SP2_CP05"
+msgstr "JBoss Web Services 2.0.1 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:113
+#, no-c-format
+msgid "JGroups 2.4.5"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:118
+#, no-c-format
+msgid "JSF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:123
+#, no-c-format
+msgid "Seam 1.2.1.AP"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:128
+#, no-c-format
+msgid "Xalan 2.7.0.patch02"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:134
+#, no-c-format
+msgid ""
+"The Enterprise Application Platform Server has been redefined for the "
+"enterprise market to a level where direct association to a community release "
+"can no longer be drawn."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:140
+#, no-c-format
+msgid "Installation and Migration Notes"
+msgstr "Notas de instalación y de migración "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:141
+#, no-c-format
+msgid ""
+"This section contains information related to installing or upgrading to "
+"JBoss Enterprise Application Platform version &VERSION;, including hardware "
+"and platform requirements and prerequisites."
+msgstr ""
+"Esta sección contiene información relacionada con la instalación o "
+"actualización a JBoss Enterprise Application Platform version &VERSION;,"
+"incluyendo los requisitos y los pre-requisitos del hardware y las "
+"plataformas. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:145
+#, no-c-format
+msgid "Installation Notes"
+msgstr "Notas de instalación "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:146
+#, fuzzy, no-c-format
+msgid ""
+"You must have adequate disk space to install JDK and JBoss Enterprise "
+"Application Platform while also allowing enough space for your applications. "
+"You must have a working installation of JDK 1.5 or 1.6. For the latest "
+"information on supported Operating System / JVM combinations, supported "
+"Database platforms and current information on the revision level of included "
+"components, please refer to <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>. Refer to the "
+"installation guide available online from <ulink url=\"http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
+"instructions to install and verify JBoss Enterprise Application Platform."
+msgstr ""
+"Debe contar con el suficiente espacio de disco para instalar JDK y JBoss "
+"Enterprise Application Platform y al mismo tiempo debe tener suficiente "
+"espacio para sus aplicaciones. Debe tener una instalación de JDK 1.5 ya "
+"funcionando. Para obtener la última información sobre sistemas operactivos/ "
+"combinaciones MVJ, plataformas de bases de datos soportadas e información "
+"actual sobre el nivel de revisión de los componentes incluidos consulte "
+"<ulink url=\"http://www.jboss.com/products/platforms/application/"
+"testedconfigurations\">http://www.jboss.com/products/platforms/application/"
+"testedconfigurations</ulink>. Refiérase al manual de instalación disponible "
+"en-línea en <ulink url=\"http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/</ulink> para obtener instrucciones "
+"detalladas sobre cómo instalar y verificar JBoss Enterprise Application "
+"Platform."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:151
+#, fuzzy, no-c-format
+msgid "Upgrading from JBoss Enterprise Application Platform 4.3.0.CP03"
+msgstr "Actualización desde JBoss Enterprise Application Platform 4.3 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:153
+#, no-c-format
+msgid "Using CSP/JON"
+msgstr "Uso de CSP/JON"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:154
+#, fuzzy, no-c-format
+msgid ""
+"Refer to <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
+"Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
+msgstr ""
+"Consulte <ulink url=\"https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> para obtener instrucciones sobre como instalar "
+"parches acumulativos."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:164
+#, no-c-format
+msgid "Important Notes"
+msgstr "Notas importantes"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:166
+#, no-c-format
+msgid "Running the example Seam Applications"
+msgstr "Ejecución de las aplicaciones Seam de ejemplo"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:169
+#, no-c-format
+msgid ""
+"It is recommended to run the example Seam applications that are included "
+"with the documentation using the production configuration. Using another "
+"configuration may result in memory issues. Note that the default "
+"configuration for the server to start with, if no other configuration is "
+"specified, is the production configuration."
+msgstr ""
+"Se recomienda que ejecute las aplicaciones Seam de ejemplo que se encuentran "
+"con la documentación utilizando la configuración de producción. Si utiliza "
+"otra configuración esto podría generar problemas con la memoria. Observe que "
+"la configuración predeterminada para el servidor para iniciar es la "
+"configuración de producción a menos de que se especifique otra configuración."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:173
+#, no-c-format
+msgid ""
+"To avoid memory issues, adjust the memory settings before deploying the "
+"applications. You can do this by updating <literal>JAVA_OPTS</literal> "
+"settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
+"conf</filename> with these recommended values:"
+msgstr ""
+"Para evitar problemas con la memoria, ajuste la configuración de la memoria "
+"antes de desplegar las aplicaciones. Puede lograr esto actualizando la "
+"configuración <literal>JAVA_OPTS</literal> en el archivo "
+"<filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> con "
+"estos valores recomendados:"
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:175
+#, no-c-format
+msgid "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+msgstr "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:178
+#, no-c-format
+msgid ""
+"Refer to the \"Seam Reference Guide\" included in the documentation set "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for "
+"important information regarding the deployment of Seam examples and detailed "
+"information on developing applications using Seam."
+msgstr ""
+"Consulte el \"Manual de referencia de Seam\" en la documentación "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) y allí "
+"encontrará información importante sobre el despliegue de ejemplos Seam así "
+"como información sobre el desarrollo de aplicaciones utilizando Seam. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:186
+#, no-c-format
+msgid "Default Security Settings"
+msgstr "Configuración predeterminada de la seguridad"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:189
+#, no-c-format
+msgid ""
+"If you are using the rpm, or the zip distribution, please note that by "
+"default, authentication is enabled and no user accounts are set up. This is "
+"done to prevent unauthorized access to various services of JBoss AS. Please "
+"refer to the Installation Guide, or see <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
+"ulink> for information on how to make the services accessible again."
+msgstr ""
+"Si está utilizando el rpm o la distribución en formato zip observe que por "
+"defecto se habilita la autenticación y no se configuran las cuentas de "
+"usuario. Esto se hace con el fin de prevenir el acceso no autorizado a "
+"varios de los servicios de JBoss AS. Consulte el manual de instalación o vea "
+"<ulink url=\"http://kbase.redhat.com/faq/FAQ_107_9963.shtm\">http://kbase."
+"redhat.com/faq/FAQ_107_9963.shtm</ulink> para obtener mayor información "
+"sobre como hacer accesibles los servicios de nuevo. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:194
+#, no-c-format
+msgid "Embedded Hypersonic Database"
+msgstr "La base de datos Hypersonic incluída"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:197
+#, no-c-format
+msgid ""
+"Hypersonic SQL provides default \"out of the box\" database functionality "
+"for evaluation and development use only. It is NOT recommended or supported "
+"as a production-use database. Technical support is not available for this "
+"component, and while we are happy to accept bugs filed against this "
+"component, we do not make any commitment to fix them within a specific "
+"timeframe."
+msgstr ""
+"Hypersonic SQL proporciona funcionalidades de base de datos tal como viene "
+"por defecto para desarrollo y evaluación sólamente. No se recomienda ni se "
+"soporta como base de datos en entornos de producción. No hay soporte técnico "
+"disponible para este componente y a pesar de que recibimos los reportes de "
+"errores sobre este componente no nos comprometemos a arreglarlos dentro de "
+"un plazo de tiempo específico. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:202
+#, no-c-format
+msgid "Source Files"
+msgstr "Archivos fuente"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:204
+#, no-c-format
+msgid "SRPMs"
+msgstr "SRPMs"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:208
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:212
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:216
+#, no-c-format
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:223
+#, no-c-format
+msgid "Source ZIP"
+msgstr "ZIP fuente "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:228
+#, fuzzy, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP04.zip"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP02.zip"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:237
+#, no-c-format
+msgid "Product Support and License Website Links"
+msgstr "Enlaces del sitio web para soporte del producto y la licencia "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:241
+#, no-c-format
+msgid "Support Processes"
+msgstr "Procesos de soporte"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:243
+#, no-c-format
+msgid "http://www.redhat.com/support/process/"
+msgstr "http://www.redhat.com/support/process/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:248
+#, no-c-format
+msgid "Production Support Scope of Coverage"
+msgstr "Cubrimiento del alcance del soporte de producción"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:252
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/production"
+msgstr "http://www.redhat.com/support/policy/soc/production"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:258
+#, no-c-format
+msgid "Production Support Service Level Agreement"
+msgstr "Acuerdo a nivel del servicio de soporte de producción"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:263
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/production/"
+msgstr "http://www.redhat.com/support/policy/sla/production/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:268
+#, no-c-format
+msgid "Developer Support Scope of Coverage"
+msgstr "Cubrimiento del alcance del soporte del desarrollador"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:273
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/developer/"
+msgstr "http://www.redhat.com/support/policy/soc/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:278
+#, no-c-format
+msgid "Developer Support Service Level Agreement"
+msgstr "Acuerdo a nivel de servicios de soporte del desarrollador"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:283
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/developer/"
+msgstr "http://www.redhat.com/support/policy/sla/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:288
+#, no-c-format
+msgid "Product Update and Support Policy by Product"
+msgstr "Actualizazión de productos y política de soporte por producto"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:293
+#, no-c-format
+msgid "http://www.redhat.com/security/updates/jboss_notes/"
+msgstr "http://www.redhat.com/security/updates/jboss_notes/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:298
+#, no-c-format
+msgid "JBoss End User License Agreement"
+msgstr "Acuerdo de licencia del usuario final de JBoss"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:303
+#, no-c-format
+msgid "http://www.redhat.com/licenses/jboss_eula.html"
+msgstr "http://www.redhat.com/licenses/jboss_eula.html"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:309 Release_Notes_CP04.xml:904
+#, no-c-format
+msgid "Documentation"
+msgstr "Documentación"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:312
+#, no-c-format
+msgid ""
+"Refer to the index.html file in the documentation directory for a list of "
+"included documentation."
+msgstr ""
+"Consulte el archivo index.html en el directorio de la documentación para "
+"obtener una lista de la documentación incluida. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:315
+#, no-c-format
+msgid ""
+"In the zip distribution, documentation for the Platform and its individual "
+"components is distributed in a separate zip file, <filename>jboss-eap-docs-"
+"&lt;version&gt;.zip</filename>."
+msgstr ""
+"En la distribución zip, la documentación para la plataforma y sus "
+"componentes individuales se distribuyen en un archivo zip que viene por "
+"separado, <filename>jboss-eap-docs-&lt;version&gt;.zip</filename>. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:319
+#, no-c-format
+msgid ""
+"On a Linux system, the documentation is found in two rpms that will need to "
+"be installed manually. These rpms are <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename>, and <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. For help with installing rpm packages on Red Hat "
+"Enterprise Linux, please refer to the Red Hat Knowledge base article located "
+"at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+msgstr ""
+"En un sistema Linux, la documentación se encuentra en dos rpms que se deben "
+"instalar manualmente. Estos rpms son <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename> y <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. Para obtener ayuda sobre cómo instalar paquetes rpm "
+"en Red Hat Enterprise Linux consulte el artículo básico sobre Red Hat que "
+"encontrará en <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm"
+"\">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink> "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:326
+#, fuzzy, no-c-format
+msgid ""
+"<filename>Installation Guide</filename> explains how to install and verify "
+"the installation of JBoss Enterprise Application Platform using different "
+"installation modes."
+msgstr ""
+"<filename>Installation Guide</filename> explica cómo instalar y verificar la "
+"instalación de JBoss Enteprise Application Platform utilizando diferentes "
+"modos de instalación."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:331
+#, no-c-format
+msgid ""
+"<filename>Getting Started</filename> details the directory structure of the "
+"platform and a quick tour of the Application Server and different "
+"configuration sets and services. Using a simple web application it "
+"illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
+"the JSF and EJB3 components."
+msgstr ""
+"<filename>Getting Started</filename> detalla la estructura del directorio de "
+"la platforma y contiene un tour rápido del servidor de aplicaciones y "
+"diferentes grupos de configuraciones y servicios. Utilizando una aplicación "
+"web simple ilustra el uso de componentes JSF-EJB3 y cómo utilizar Seam para "
+"integrar los componentes JSF y EJB3. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:336
+#, no-c-format
+msgid ""
+"<filename>Server Configuration Guide</filename> explains all administrative "
+"and configuration functions in detail."
+msgstr ""
+"<filename>Server Configuration Guide</filename> explica todas las funciones "
+"administrativas y de configuración en detalle."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:342
+#, no-c-format
+msgid ""
+"Updated versions of the documentation with errata and additional "
+"information, example application code, as well as the most recent version of "
+"the release notes may be accessed via the web from <ulink url=\"http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+msgstr ""
+"Puede acceder a versiones actualizadas de la documentación con errores e "
+"información adicional, código de aplicación de ejemplo así como la versión "
+"más reciente de las notas de lanzamiento en <ulink url=\"http://www.redhat."
+"com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat."
+"com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:357
+#, no-c-format
+msgid "Issues fixed in this release"
+msgstr "Problemas resueltos en este lanzamiento"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:361
+#, no-c-format
+msgid "Following is a list of issues fixed in this release:"
+msgstr ""
+"La siguiente es una lista de los problemas resueltos en este lanzamiento: "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:369
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1615\">JBPAPP-1615</"
+"ulink>: The JBoss Messaging component of the Enterprise Application Platform "
+"has been upgraded to version 1.4.0.SP3-CP07. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:374
+#, no-c-format
+msgid ""
+"There was an issue with the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method whereby the method delegates checking to "
+"the <classname>ResourceManager</classname> <varname>serverID</varname>. This "
+"instigates the case where the <methodname>xasess2.start(xid, TMJOIN)</"
+"methodname> method is called and the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method returns true but the resource manager does "
+"not hold the transaction state required to perform a <code>TMJOIN</code>. "
+"Further to this when a session is closed the <methodname>SessionAspect."
+"handleClose()</methodname> method is called, yet the <code>tx</code> was "
+"removed from the transaction manager meaning it is no longer in the "
+"<code>conn1</code> resource manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:377
+#, no-c-format
+msgid ""
+"To correct this both the <methodname>MessagingXAResource.isSameRM</"
+"methodname> method and <classname>ResourceManager</classname> have the same "
+"<code>serverID</code> and the same map of transactions, ensuring that if the "
+"<classname>ResourceManager</classname> was to ever return true, the call to "
+"<methodname>start(TMJOIN)</methodname> would correctly succeed. To note is "
+"that the transaction will rollback at completion time and any message "
+"delivered in the <code>tx</code> will be redelivered."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:382
+#, no-c-format
+msgid ""
+"Client connection parameters were not being passed to the JBoss Remoting "
+"layer, leaving parameters such as <varname>validatorPingPeriod</varname> and "
+"<varname>validatorTimeout</varname> to be used with default values within "
+"Remoting instead of the configured values. In correcting this issue, the "
+"<filename>JMSRemotingConnection.java</filename> file has been updated so "
+"that when the <methodname> client.addConnectionListener</methodname> method "
+"is called within the <methodname>addConnectionListener</methodname> and "
+"<methodname>addPlainConnectionListener</methodname> methods, it also passes "
+"the configured parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:387
+#, no-c-format
+msgid ""
+"The <literal>default</literal> profile for JBoss without any reconfiguration "
+"uses the <classname>ClusteredConnectionFactory</classname> with a non-"
+"clustered post-office, however warnings would be logged about this behavior "
+"when the log messages should be reduced from a <varname>WARN</varname> level "
+"to an <varname>INFO</varname> level. The upgrade to this version of JBoss "
+"Messaging sees this implemented within the log."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:392
+#, no-c-format
+msgid ""
+"<classname>ClusterViewUpdateTest</classname> was broken and did not work "
+"correctly in previous releases with the cause being that the expected time "
+"until failure detection for some clustering tests was too long. In order to "
+"correct this the values for <varname>validatorPingPeriod</varname> and "
+"<varname>validatorPingTimeout</varname> have been changed to be 2 seconds "
+"each, combining to 4 seconds as the total time until expected failure "
+"detection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:397
+#, no-c-format
+msgid ""
+"Client connection parameters were not passed to the JBoss Remoting layer, "
+"forcing Remoting to use default values instead of user configured values. In "
+"order to use the correct values, <filename>JMSRemotingConnection.java</"
+"filename> has been updated so that the <methodname>Client."
+"addConnectionListener</methodname> method is used with <varname>listener</"
+"varname> and <varname>serverLocator.gerParameters()</varname> as parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:402
+#, no-c-format
+msgid ""
+"Messages which are scheduled for delivery in the future were not being "
+"removed correctly when the <methodname>removeAllMessages()</methodname> "
+"method was being called, causing the messages to be re-queued as soon as the "
+"application server or queue is restarted. <filename>ChannelSupport.java</"
+"filename> has been updated to import the <filename>TimeoutExt</filename> "
+"library in order to cast the timeout value to <filename>TimeoutExt</"
+"filename> in order to obtain the reference value via the <methodname>get "
+"TimeoutTarget()</methodname> method. With this new reference value "
+"information, the scheduled messages can be correctly removed from the queue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:407
+#, no-c-format
+msgid ""
+"There was an occurrence where a user may deploy a clustered queue in a "
+"single node instead of in all the nodes and the failover process would not "
+"work because of this. When this occurred an <exceptionname>Illegal "
+"StateException</exceptionname> would be generated, however this was not "
+"considered enough of a prominent warning about not deploying clustered "
+"queues correctly. <filename>Messaging PostOffice.java</filename> has now "
+"been updated to log a warning which outlies that clustered destinations must "
+"be deployed on all nodes of a cluster, instead of generating an "
+"<exceptionname>Illegal StateException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:412
+#, no-c-format
+msgid ""
+"The <classname>Client</classname>, <classname>SecurityAspect.check()</"
+"classname> and <classname>ServerConnection FactoryEndpoint</classname> "
+"needed to be able to obtain TLC within a privileged block, otherwise an "
+"<exceptionname>Access ControlException</exceptionname> is produced. To fix "
+"this bug, the <methodname>settle</methodname>, <methodname>gettable</"
+"methodname> and other TLC methods have been set within security blocks; this "
+"prevents access denied exceptions from <classname>Client</classname>, "
+"<classname>SecurityAspect.check()</classname> and "
+"<classname>ServerConnection FactoryEndpoint</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:417
+#, no-c-format
+msgid ""
+"The logging of actions within JBoss Messaging did not include the logging of "
+"messages when they are moved to the expiry or dead letter queues as this was "
+"only logged at trace level. In order to add this enhanced level of logging, "
+"the <filename>ClientConsumer.java</filename> file has been updated to log "
+"warning messages and debug information pertaining to the move of messages to "
+"the expiry or dead letter queues; <filename>Server SessionEndpoint.java</"
+"filename> has also been updated in the same mannor."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:422
+#, no-c-format
+msgid ""
+"There was an error when a message was received under a X tx and the JBoss "
+"Messaging XAResource is prepared but not committed, a message could be "
+"received by another consumer in another transaction while the first is still "
+"in progress. The correct behavior is for JBoss Messaging to hold the message "
+"until the associated transaction is committed or rolled back, enabling "
+"duplication of message deliveries to be avoided. In the <filename>Delivery."
+"java</filename> file, messages are now marked with a boolean value detailing "
+"if they are for delivery with a X transaction and if this transaction is "
+"prepared and <filename>SimpleDelivery.java</filename> now implements this "
+"new information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:427
+#, no-c-format
+msgid ""
+"The <methodname>shutdownNow()</methodname> method was not synchronized and "
+"may cause a <exceptionname>NoSuchElementException</exceptionname> during "
+"runtime as a result. A synchronization block has been placed around the "
+"<methodname>shutdownNow()</methodname> code within "
+"<filename>OrderedExecutorFactory.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:432
+#, no-c-format
+msgid ""
+"There was an issue with the <classname>org.jboss.jms.server.messagecounter."
+"MessageCounter</classname> class not being able to be serialized as it "
+"caused an <exceptionname>UndeclaredThrowableException</exceptionname>. "
+"<filename>MessageCounter.java</filename> has been updated to now import and "
+"implement the <literal>Serializable</literal> library and be given a "
+"<varname>serialVersionUID</varname>, allowing the <classname>org.jboss.jms."
+"server.messagecounter.MessageCounter</classname> class to be serializable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:437
+#, no-c-format
+msgid ""
+"When the methods <methodname>unregisterSucker()</methodname> or "
+"<methodname>registerSucker()</methodname> was called a "
+"<exceptionname>ConcurrentModificationException</exceptionname> would be "
+"generated by the time the <literal>HashSet</literal> containing the "
+"<literal>suckers</literal> was iterated. The issue would present itself on "
+"clusters with a magnitude of nodes (for instance it appeared on a 8 node "
+"cluster but not a 4 node cluster). This bug was corrected by creating an "
+"iterator that used a private set of <literal>suckers</literal> for iteration "
+"through the <literal>HashSet</literal> of <literal>suckers</literal> in "
+"order to avoid the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:442
+#, no-c-format
+msgid ""
+"The bridge within JBoss Messaging would only retry connection creation to a "
+"remote destination after startup and if the remote provider was not "
+"available at startup, the bridge would fail to start. The <filename>Bridge."
+"java</filename> and <filename>BridgeService.java</filename> files have "
+"undergone extensive modification and now the <literal>factory</literal> is "
+"set to the <literal>bridge</literal> which undertakes the lookup itself "
+"instead of looking up the destinations."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:452
+#, fuzzy, no-c-format
+msgid "JBoss Cache"
+msgstr "JBoss Seam "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:456
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
+"ulink>: The JBoss Cache component of the Enterprise Application Platform has "
+"been upgraded to version 1.4.1.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:461
+#, no-c-format
+msgid ""
+"The <classname>JDBCCacheLoader</classname> implementation did not work with "
+"Sybase as it would try to set a null <varname>BLOB</varname> column which is "
+"unsupported within Sybase. To correct this the <filename>JDBCCacheLoader."
+"java</filename> file has been updated so that the Sybase Driver sets a null "
+"<varname>LONGVARBINARY</varname> value, allowing the "
+"<classname>JDBCCacheLoader</classname> implementation to work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:466
+#, no-c-format
+msgid ""
+"The <classname>JDBCExtCacheLoader</classname> did not handle persistent "
+"state transfer correctly since the <methodname>JDBCExtCacheLoader.storeState"
+"()</methodname> method would use available bytes on the "
+"<classname>MarshalledValueInputStream</classname> rather than on the "
+"<classname>ByteArrayInputStream</classname> when storing the persistent "
+"state. This was an issue because the <classname>MarshalledValueInputStream</"
+"classname> always returns a null value, meaning the persistent state was "
+"never written. In fixing this issue the <filename>JDBCExtendedCacheLoader."
+"java</filename> file has been modified so that it specifies to check for "
+"available space on the <classname>ByteArrayInputStream</classname>."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:476
+#, no-c-format
+msgid "JBoss Remoting"
+msgstr "JBoss Remoting "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:480
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
+"ulink>: The JBoss Remoting component of the Enterprise Application Platform "
+"has been upgraded to version 2.2.2.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:485
+#, no-c-format
+msgid ""
+"The <methodname>ConnectionValidator.run()</methodname> method had the "
+"ability to be called by a user before the private method "
+"<methodname>ConnectionValidator.start()</methodname> was called, resulting "
+"in the <varname>clientInvoker</varname> and <varname>timer</varname> fields "
+"being set to null and generating a <exceptionname>NullPointerException</"
+"exceptionname>. Within the <filename>ConnectionValidator.java</filename> "
+"file the fields are now checked to see if they are null upon execution of "
+"the <methodname>ConnectionValidator.run()</methodname> method, one or both "
+"are then an <exceptionname>IllegalStateException</exceptionname> is "
+"displayed to the user outlining that <methodname>ConnectionValidator.run()</"
+"methodname> should not be called directly but "
+"<methodname>addConnectionListener()</methodname> should be used instead."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:490
+#, no-c-format
+msgid ""
+"Two bugs existed within the <methodname>org.jboss.remoting.marshal."
+"MarshallerLoaderHandler.loadClassBytes()</methodname> method that prohibited "
+"remote classloading to work correctly with isolated EARs. The first was that "
+"a while loop in the code needed a break and the second was that the call to "
+"the <methodname>org.jboss.mx.loading.LoaderRepository.getCachedClass()</"
+"methodname> method should have been a general call to "
+"<methodname>LoaderRepository.loadClass()</methodname>. These two issues have "
+"been rectified with this Remoting update, allowing remote classloading to "
+"function correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:495
+#, no-c-format
+msgid ""
+"A bug existed within the Remoting component by which the RemotingClassLoader "
+"would always attempt to load a class over the network first if remote "
+"classloading was enabled, leading to conflicts if the class was available "
+"locally before. The code has been corrected to check locally first before "
+"looking remotely."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:500
+#, no-c-format
+msgid ""
+"The <classname>ServerInvokerCallbackHandler</classname> class would become "
+"unresponsive when calling the <methodname>BlockingCallbackStore.add()</"
+"methodname> method after locking the callback field with a true responce "
+"from the <methodname>persistCallback()</methodname> method. This would occur "
+"because the <methodname>BlockingCallbackStore.getNext()</methodname> needed "
+"to control the lock on the callback field to break the waiting period, "
+"however this could not be achieved because of the wait period. To fix this "
+"issue the call to the <methodname>BlockingCallbackStore.add()</methodname> "
+"method has been removed as it was an unnecessary step."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:505
+#, no-c-format
+msgid ""
+"The <classname>HTTPClientInvoker</classname> did not support Beginner's All-"
+"purpose Symbolic Instruction Code (BASIC) authentication for proxies when "
+"the proxy was configured through system property options of <methodname>http."
+"proxyHost</methodname> and <methodname>http.proxyPort</methodname>. The "
+"issue appears because the <classname>HTTPClientInvoker</classname> would not "
+"check for the existence of these options and in tern it would never create a "
+"<methodname>Proxy-Authorization</methodname> request header, which is "
+"necessary for normal operation. To fix this the "
+"<classname>HTTPClientInvoker</classname> has been modified to check for the "
+"existence of the <methodname>http.proxyHost</methodname> option and if it "
+"detects its use, creates a <methodname>Proxy-Authorization</methodname> "
+"request header."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:510
+#, no-c-format
+msgid ""
+"<classname>HTTPClientInvoker</classname> would generate a "
+"<exceptionname>NullPointerException</exceptionname> when the HTTP server "
+"returned an error code without any content and then the <methodname>java.net."
+"HttpUrlConnection.getInputStream()</methodname> method returned a null "
+"value. In order to improve control over this behavior, the new variable "
+"<varname>UNMARSHAL_NULL_STREAM</varname> has been added to the "
+"<classname>HTTPClientInvoker</classname>. If this variable is set to true "
+"(the default value) the default behavior is executed, however if it is set "
+"to false the call to the <methodname>UnMarshaller.read()</methodname> is "
+"skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:515
+#, no-c-format
+msgid ""
+"Within the <classname>InvokerRegistry</classname> an error existed "
+"associated with the sequencing of events and <classname>serverLocators</"
+"classname> would return a null on occasion. To correct this race condition, "
+"the sequencing of events within the <classname>InvokerRegistry</classname> "
+"has been rearranged so that references to "
+"<classname>transportClientFactoryClasses</classname> and "
+"<classname>clientLocators</classname> are governed by <classname>clientLock</"
+"classname> and references to <classname>transportServerFactoryClasses</"
+"classname>, <classname>serverLocators</classname>, and "
+"<classname>registeredLocators</classname> are governed by "
+"<classname>serverLock</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:520
+#, no-c-format
+msgid ""
+"A bug existed where the value in the client configuration map of the "
+"<classname>ConnectionValidator</classname> would be ignored when the "
+"overloaded <methodname>org.jboss.remoting.Client</methodname> method was "
+"called and the <varname>DEFAULT_PING_PERIOD</varname> variable value was "
+"placed into the metadata map passed to the <classname>ConnectionValidator</"
+"classname>. This has been corrected by updating <classname>org.jboss."
+"remoting.Client.addConnectionListener</classname> so that "
+"<varname>DEFAULT_PING_PERIOD</varname> is only passed if the value of "
+"<varname>VALIDATOR_PING_PERIOD</varname> within the client's configuration "
+"map has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:525
+#, no-c-format
+msgid ""
+"<classname>ConnectionValidator</classname> may become unresponsive then the "
+"<methodname>run()</methodname> method is executed and utilizes the "
+"<varname>lock</varname> variable. The methods within the <methodname>run()</"
+"methodname> method are meant to time out so that the <varname>lock</varname> "
+"variable can become available to the <methodname>notifyListeners()</"
+"methodname> in the event of a network failure; however <methodname>run()</"
+"methodname> may execute again before <methodname>notifyListeners()</"
+"methodname> can. The synchronization on the <varname>lock</varname> variable "
+"has been modified to avoid this issue to enable correct operation."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:530
+#, no-c-format
+msgid ""
+"During occurrences of the server being under heavy load, an "
+"<exceptionname>IllegalStateException</exceptionname> would occur within the "
+"<methodname>ConnectorValidator.run()</methodname> method because further "
+"synchronization on the <varname>lock</varname> variable was necessary. This "
+"issue was fixed during the rectification of the above problem."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:535
+#, no-c-format
+msgid ""
+"A synchronization error within the <classname>MarshalFactory</classname> was "
+"allowing a subsystem to add a marshaller at the same time as EJB3 was trying "
+"to extract one causing users to receive an "
+"<exceptionname>InvalidMarshallingResource</exceptionname> exception; this "
+"also applied to unmarshallers. The error has been fixed by updating the "
+"<filename>jboss-remoting.jar</filename> file to include synchronized static "
+"Maps within the <classname>MarshalFactory</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:540
+#, no-c-format
+msgid ""
+"The <classname>SocketServerInvoker</classname> had an issue when shutting "
+"down <varname>ServerThreads</varname> causing a user to possibly receive an "
+"invocation to a closed <classname>SocketServerInvoker</classname> on the "
+"client side, causing an <exceptionname>InvalidStateException</"
+"exceptionname>. Allowing this exception would cause a clustered EJB3 system "
+"to generate a <exceptionname>UndeclaredThrowableException</exceptionname> "
+"instead of trying alternative servers. To allow for alternatives to be "
+"attempted, an optional behavior of allowing the "
+"<classname>MicroRemoteClientInvoker</classname> to interpret an "
+"<exceptionname>InvalidStateException</exceptionname> as a "
+"<exceptionname>CannotConnectException</exceptionname>, allowing for other "
+"servers to be attempted."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:550
+#, fuzzy, no-c-format
+msgid "JBoss Web"
+msgstr "JBoss Seam "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:554
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1493\">JBPAPP-1493</"
+"ulink>: An error would be shown on occasion by <emphasis>Internet Explorer</"
+"emphasis> because xml content would not be sent when <emphasis>PROPFIND</"
+"emphasis> requests were being used. This has been fixed by creating a new "
+"method within <filename>WebdavServlet.java</filename> that overrides the "
+"<methodname>DefaultServlet</methodname> implementation for servlet request "
+"processing and testing for input before launching the "
+"<methodname>DocumentBuilder</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:559
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1470\">JBPAPP-1470</"
+"ulink>: When using APR (Apache Portable Runtime) on any operating system "
+"other than those which use the Linux Kernal 2.4 or newer, the "
+"<parameter>deferAccept</parameter> option would be set to false in the "
+"<methodname>AprEndpoint</methodname>. This may lead to a "
+"<exceptionname>NullPointerException</exceptionname> as the "
+"<methodname>accepter</methodname> thread starts to process a request while "
+"also calling for a <methodname>poller</methodname> before initialization. "
+"The issue has been resolved by moving the <methodname>acceptor</methodname> "
+"threads to being executed last when starting the <methodname>AprEndpoint</"
+"methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:564
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1334\">JBPAPP-1334</"
+"ulink>: The JBoss Web component of the Enterprise Application Platform has "
+"been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:569
+#, no-c-format
+msgid ""
+"If a war deployment included its own version of <filename>xalan.jar</"
+"filename> and <filename>xercesImpl.jar</filename> in <filename>WEB-INF/lib</"
+"filename>, the JBossWeb servlet container classloader returns JBoss provided "
+"version of the <literal>SAXParser</literal> from "
+"<methodname>SAXParserFactory.newInstance().newSAXParser()</methodname> "
+"rather than the version provided in the war deployment. To fix this bug the "
+"<filename>WebAppClassLoader.java</filename> has been updated to ensure the "
+"correct parser is used."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:579
+#, no-c-format
+msgid "JBoss Web Services"
+msgstr "Servicios JBoss Web"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:583
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1560\">JBPAPP-1560</"
+"ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component "
+"of the Enterprise Application Platform has been upgraded to version 2.1.4."
+"patch01. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:588
+#, no-c-format
+msgid ""
+"The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package "
+"contains classes to optimize field and method access by dynamically "
+"generating classes. Within the <classname>Injector</classname> class there "
+"is a <literal>HashMap</literal> value that is wrapped within a "
+"<literal>WeakReference</literal> however since there is only a "
+"<literal>WeakReference</literal> to the <classname>Injector</classname> "
+"class within this, the <literal>HashMap</literal> is garbage collected. To "
+"fix this the reference has been changed to a <literal>StrongReference</"
+"literal> and in order to maintain the original requirements, the "
+"<classname>Injector</classname> is now passed a reference to the ClassLoader "
+"instead of containing one specifically."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:595
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1210\">JBPAPP-1210</"
+"ulink>: The JBoss Web Services component of the Enterprise Application "
+"Platform has been upgraded to version 2.0.1.SP2_CP05. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:600
+#, no-c-format
+msgid ""
+"When deploying JBoss Web Services within Enterprise Application Platform "
+"without internet access, <classname>JBossWSEntityResolver</classname> would "
+"not resolve any schemas causing Web Services for Remote Portlets (WSRP) to "
+"produce an error. This issue has been fixed by modifying "
+"<classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader."
+"java</filename> to resolve schemas locally when an internet connection is "
+"unavailable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:605
+#, no-c-format
+msgid ""
+"WSProvide would ignore a <literal>SOAPBinding</literal> declaration "
+"specified in the EJB3 stateless session bean. To correct this and allow "
+"<literal>SOAPBinding</literal> to work as expected the following files have "
+"been modified: <filename>WSDLGenerator.java</filename>, "
+"<filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, "
+"<filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</"
+"filename> and <filename>WSDL11Writer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:610
+#, no-c-format
+msgid ""
+"The component <emphasis>Xerces</emphasis> of JBoss Web Services has a "
+"feature that optimizes the parsing of messages called <methodname>Deffered "
+"Node Expansion</methodname>.This defers node expansion until the nodes are "
+"accessed, improving performance where not all nodes need to be visited. "
+"However memory overheads are increased, which can be considerable for large "
+"messages."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:613
+#, no-c-format
+msgid ""
+"This release grants the user an option to disable the <methodname>Deffered "
+"Node Expansion</methodname> feature and have all nodes expand. To achieve "
+"this the following system property needs to be set:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:616
+#, no-c-format
+msgid "-Dorg.jboss.ws.disable_deferred_node_expansion=true"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:619
+#, no-c-format
+msgid ""
+"A regression with <literal>TCK5 SAAJ</literal> in the <classname>SOAPBody</"
+"classname> class was introduced with a fix to a previous bug and this has "
+"now been rectified by modifying the <filename>SOAPBodyImpl.java</filename> "
+"file to perform a <code>break</code> after assigning the "
+"<varname>childElement</varname> property."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:624
+#, no-c-format
+msgid ""
+"The end points for a <literal>transport-guarantee</literal> that is set to "
+"be confidential would see an attempt to exactly map the URL pattern in the "
+"WSDL. However since the servlet and security constraints will not be defined "
+"exactly the same a bug occurred whereby JBoss Web Services would assume the "
+"<literal>transport-guarantee</literal> was not confidential when generating "
+"the address, causing the WSDL to be generated with a http address. The "
+"<literal>transport-guarantee</literal> would still be enforced by JBoss Web "
+"Services as confidential but the WSDL would contain the wrong address, "
+"leading to clients attempting to connect to an incorrect address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:627
+#, no-c-format
+msgid ""
+"In order to rectify this occurrence, the <filename>MetaDataBuilder.java</"
+"filename> file has been modified so that when testing the servlet pattern it "
+"also tests correctly for the security constraint instead of assuming both "
+"with be of the same value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:632
+#, no-c-format
+msgid ""
+"When creating messages in SOAP 1.2 without attachments, the "
+"<classname>SOAPMessageImpl</classname> class sets the <varname>contentType</"
+"varname> variable to <literal>text/xml</literal>, which was incorrect. This "
+"has now been rectified by amending <varname>contentType</varname> to use the "
+"value <literal>application/soap+xml</literal> by adding the "
+"<methodname>getSAPContentType()</methodname> method to "
+"<filename>SOAPMessageImpl.java</filename> and updating "
+"<filename>DispatchImpl.java</filename> to correctly reference the SOAP "
+"message context."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:638
+#, no-c-format
+msgid ""
+"Deployments of JAX-WS nature would fail for JBoss AOP instrumented "
+"endpoints, generating an <exceptionname>IllegalAnnotationsException</"
+"exceptionname> as JBoss Web Services attempted to process the JBoss AOP "
+"methods. <filename>JAXWSMetaDataBuilder.java</filename> has been updated to "
+"mark JBoss AOP methods as synthetic which allows them to be skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:643
+#, no-c-format
+msgid ""
+"WSDL dynamic address replacement was not working correctly in previous "
+"versions of the Enterprise Application Platform since port and protocol "
+"numbers were not being considered. The <filename>WSDLRequestHandler.java</"
+"filename> file has been modified to use a new URL and protocol instead of "
+"the original URL and protocol in order to use the dynamically generated port "
+"and protocol numbers."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:648
+#, no-c-format
+msgid ""
+"In converting WSDL to Java, anonymous types that are nested within anonymous "
+"types generated a JAX-RPC mapping that did not match the source. The "
+"<filename>MappingFileGeneratorHelper.java</filename> file has been corrected "
+"to ensure that the generated mapping matches the source of the information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:653
+#, no-c-format
+msgid ""
+"JAAS certificate authentication support was not supported in the JBoss Web "
+"Services Security implementation, meaning that authentication via this "
+"method could not take place based on the certificate the client used to sign "
+"the message. Support for this has been added to JBoss Web Services and in "
+"tern the Enterprise Application Platform with this component upgrade."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:658
+#, no-c-format
+msgid ""
+"When the default port for a protocol was being used within JBoss Web "
+"Services, the port number still appeared at the end of the URL even though "
+"this was unnecessary. In order to remove the port number from the end of the "
+"URL, the <filename>MetaDataBuilder.java</filename> has been modified for "
+"each individual service that uses the default port."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:663
+#, no-c-format
+msgid ""
+"When JBoss Web Services is being used as a client, the information within "
+"the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not "
+"cleared for incoming client calls. In order to fix this the call to "
+"<methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the "
+"<classname>MessageContextAssociation</classname> class and is executed once "
+"the last message has been processed. The files that have been updated in "
+"order to incorporate the fix are: <filename>DOMUtils.java</filename>, "
+"<filename>XMLContent.java</filename>, <filename>ProviderImpl.java</"
+"filename>, <filename>MessageContextAssociation.java</filename>, "
+"<filename>MessageContextJAXWS.java</filename> and "
+"<filename>RequestHandlerImpl.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:668
+#, no-c-format
+msgid ""
+"When the <varname>webServiceHost</varname> property was not set, the <ulink "
+"url=\"http://localhost:8080/jbossws/services \">http://localhost:8080/"
+"jbossws/services</ulink> page presented the host name as "
+"<exceptionname>jbossws.undefined.host</exceptionname>. A "
+"<methodname>createAddress</methodname> method has been added to "
+"<filename>ContextServlet.java</filename> which dynamically updates the WSDL "
+"and XSD files with the address from the request URL before displaying "
+"information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:674
+#, no-c-format
+msgid ""
+"The JBoss Web Services upgrade 2.0.1.SP2_CP05 also includes the security fix "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>, discussed in the Security Issue section."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:683
+#, no-c-format
+msgid "JBoss Seam"
+msgstr "JBoss Seam "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:687
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1553\">JBPAPP-1553</"
+"ulink>: When the <methodname>parseRequest()</methodname> method of the "
+"<classname>org.jboss.seam.web.MultipartRequest</classname> class uploaded a "
+"large file, there were occurrences when this would cause an endless loop and "
+"use 100% of the computers CPU. In order to break out of the loop, a "
+"<varname>loopCounter</varname> has been implemented within the "
+"<filename>MultipartRequest.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:692
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1494\">JBPAPP-1494</"
+"ulink>: The portal example that was previously included with the Seam "
+"Enterprise Application Platform distribution has been removed in order to "
+"avoid confusion that Seam 1.2.1 included with the EAP supports portal."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:697
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1044\">JBPAPP-1044</"
+"ulink>: After basic interaction with the Seam examples <filename>chatroom</"
+"filename>, <filename>mail</filename>, <filename>registration</filename>, "
+"<filename>booking</filename> and <filename>dvdstore</filename> would "
+"generate a <exceptionname>NullPointerException</exceptionname> during "
+"undeployment. In correcting this issue, the <filename>RootInterceptor.java</"
+"filename> file was updated to check if an applications context still active "
+"upon undeployment and deal with this appropriately."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:705
+#, no-c-format
+msgid "JBoss Hibernate"
+msgstr "JBoss Hibernate "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:709
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1580\">JBPAPP-1580</"
+"ulink>: The JBoss Hibernate Core component of the Enterprise Application "
+"Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:714
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1628\">JBPAPP-1628</"
+"ulink>: In an earlier fix to Hibernate the <methodname>org.hibernate.jdbc."
+"AbstractBatcher#closeQueryStatement()</methodname> method was changed to "
+"check for the existence of the prepared statement in the "
+"<classname>statementsToClose</classname> collection instead of closing it "
+"unconditionally. This has now caused a properties leak as the "
+"<methodname>org.hibernate.persister.entity."
+"AbstractEntityPersister#processGeneratedProperties()</methodname> used "
+"<methodname>org.hibernate.jdbc.AbstractBatcher#closeQueryStatement()</"
+"methodname> and the statement within <methodname>org.hibernate.persister."
+"entity.AbstractEntityPersister#processGeneratedProperties()</methodname> is "
+"not added to the <classname>statementsToClose</classname> collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:717
+#, no-c-format
+msgid ""
+"<filename>AbstractEntityPersister.java</filename> has been updated to "
+"execute a prepared statement on the result set and after calculating the "
+"<varname>propValue</varname> the result set is closed if it is not null; "
+"ensuring that no leak can occur."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:722
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1582\">JBPAPP-1582</"
+"ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</"
+"classname> is included with this CP release to support Sybase ASE 15 and "
+"this dialect now becomes apart of the Enterprise Application Platform "
+"certified configuration. Previous Sybase dialects are now considered "
+"deprecated and may be removed from future releases; however support will "
+"still be maintained for users who do not wish to move to the new dialect."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:742
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1524\">JBPAPP-1524</"
+"ulink>: The Sybase functions <methodname>second()</methodname>, "
+"<methodname>minute()</methodname>, <methodname>hour()</methodname> and "
+"<methodname>extract()</methodname> caused a "
+"<exceptionname>GenericJDBCException</exceptionname> when used. Moving these "
+"functions from the <filename>SQLServerDialect.java</filename> file to the "
+"<filename>SybaseDialect.java</filename> file allows for these functions to "
+"work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:757
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1519\">JBPAPP-1519</"
+"ulink>: Sybase does not support the operation <emphasis>on cascade delete</"
+"emphasis> while SQL Server does. To make sure that both operate correctly "
+"the <filename>SQLServerDialect.java</filename> file has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns true and <filename>SybaseDialect.java</filename> has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns false."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:762
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1496\">JBPAPP-1496</"
+"ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</"
+"emphasis> when using the <emphasis>Identity</emphasis> generator option. To "
+"close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make "
+"sure it is closed before returning the generated identity value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:767
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1480\">JBPAPP-1480</"
+"ulink>: Hibernate would attempt to read from an invalid column in the "
+"collection result set when the following conditions were present:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
+"ulink>: La configuración SQL predeterminada tenía errores, lo cual causaba "
+"un problema dentro de hsqldb el cual usa esta configuración. El problema con "
+"la configuración predeterminada ahora ha sido corregido."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:772
+#, no-c-format
+msgid "Instances of a subclass were contained in a collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:777
+#, no-c-format
+msgid ""
+"The subclasses were single-table and used a &lt;join&gt; (table-per-subclass "
+"with discriminator)."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:782
+#, no-c-format
+msgid ""
+"The &lt;join&gt; portion of the subclass contained at least 3 of its own "
+"columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:787
+#, no-c-format
+msgid ""
+"The &lt;join&gt; tables were fetched by select and not the default method "
+"for this task."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:792
+#, no-c-format
+msgid ""
+"To fix this issue the <filename>AbstractEntityPersister.java</filename> file "
+"was updated so that the <varname>columnNumber</varname> variable is passed "
+"to the <methodname>subclassColumnSelectableClosure</methodname> method "
+"instead of an increment of the for loop variable <varname>i</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:795
+#, no-c-format
+msgid ""
+"<filename>CollectionTest.java</filename> has also been updated and "
+"<filename>Animal.java</filename>, <filename>Mammal.java</filename>, "
+"<filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been "
+"added for testing purposes."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:800
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1467\">JBPAPP-1467</"
+"ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur "
+"when merging a detached instance of a <classname>One</classname> class that "
+"contains a new <classname>Many</classname> class instance and if and only if "
+"the <classname>One</classname> class was previously loaded as a proxy during "
+"the same transaction. The files <filename>StatefulPersistenceContext.java</"
+"filename>, <filename>BackrefPropertyAccessor.java</filename>, "
+"<filename>BackrefTest.java</filename> and <filename>Child.java</filename> "
+"have been updated to check for the proxy issue in the merging and once the "
+"proxy entity is found the <methodname>mergeMap</methodname> is updated to "
+"deal with this eventuality."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:805
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1365\">JBPAPP-1365</"
+"ulink>: A bug existed within Hibernate Core where the "
+"<methodname>addDuplicateAlias</methodname> method would include an entry "
+"into the hash map even when the <varname>classAlias</varname> variable was "
+"set to null; causing a <exceptionname>NullPointerException</exceptionname> "
+"when the <methodname>CrazyJPARRequirements()</methodname> method is called. "
+"To correct this issue the <filename>FromClause.java</filename> file has been "
+"modified to correct the <methodname>addDuplicateAlias</methodname> method by "
+"testing if the <varname>alias</varname> variable is null and if it is not "
+"null then the <methodname>fromElementByClassAlias.put</methodname> is now "
+"called, instead of this method being called even if <varname>alias</varname> "
+"contained a null value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:810
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1259\">JBPAPP-1259</"
+"ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL "
+"and the version field is specified by the user to not be updated, the "
+"<methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method "
+"would still update the field causing exceptions to appear in certain cases. "
+"Within this Enterprise Application Platform update "
+"<filename>AbstractEntityPersister.java</filename> has been corrected to "
+"check if the user has explicitly said that the version field should not be "
+"updated and does not update the field if this is the case."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:815
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1251\">JBPAPP-1251</"
+"ulink>: Filters that were enabled for Hibernate did not apply to update and "
+"delete Hibernate Query Language (HQL) statements. In correcting this bug "
+"numerous files have been updated to ensure that the filters work correctly. "
+"This fix is related to JBPAPP-1250 below."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:820
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1250\">JBPAPP-1250</"
+"ulink>: When creating queries with subqueries in Hibernate, any added "
+"filters would only apply to the top-level of the query and not to any "
+"subquery component or beneath. The Criteria code and HQL code associated "
+"with this has undergone significant re-tooling to allow filters to work "
+"appropriately with subqueries and extent as far as the Hibernate Query "
+"Language does."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:823
+#, no-c-format
+msgid ""
+"Though this is a significant fix to Hibernate, it has been included within "
+"this CP release because of its undeniable advantage to all users and ensures "
+"that filters on queries operate how a user would expect them to."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:833
+#, no-c-format
+msgid "JBoss Transaction Service (JBossTS)"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:837
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1510\">JBPAPP-1510</"
+"ulink>: The JBoss Transaction Service component of the Enterprise "
+"Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of "
+"the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:842
+#, no-c-format
+msgid ""
+"The <classname>AppServerJDBCXARecovery</classname> class was using the Java "
+"1.5 syntax when it should compile with Java 1.4. This error has been "
+"rectified with this release by modifying the "
+"<filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:847
+#, no-c-format
+msgid ""
+"When the Application Server started, the transaction manager may have "
+"deployed before the datasources, starting a recovery pass and causing "
+"exceptions. This issue has been rectified by modifying the "
+"<classname>AppServerJDBCXARecovery</classname> class and adding the "
+"<methodname>createConnection() throws SQLException</methodname> method which "
+"makes sure a connection exists before deploying the transaction manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:852
+#, no-c-format
+msgid ""
+"There were occurrences when the <classname>AppServerJDBCXARecovery</"
+"classname> class would contain information to an invalid connection because "
+"of database failure. This bug was fixed with the same correction as the "
+"above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</"
+"classname> class and adding the <methodname>createConnection() throws "
+"SQLException</methodname> method which makes sure a connection exists."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:857
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method would be run even when "
+"the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, "
+"when this method should only be executed before commit attempts and not "
+"rollbacks. In order to correct this and make sure the "
+"<methodname>beforeCompletion</methodname> method does not get executed for "
+"rollback events the <filename>SubordinateAtomicAction.java</filename> file "
+"has been modified."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:862
+#, no-c-format
+msgid ""
+"<methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a "
+"<exceptionname>HeuristicRollbackException</exceptionname> when the commit "
+"was aborted. This meant that <methodname>XATerminatorImple.commit</"
+"methodname> was unable to distinguish between a successful rollback and one "
+"in error. Fixed in this CP release, the <filename>TransactionImple.java</"
+"filename> file has been modified so that the <methodname>TransactionImple."
+"doOnePhaseCommit</methodname> method now generates a "
+"<exceptionname>RollbackException</exceptionname> instead of a heuristic when "
+"a successful rollback is performed."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:867
+#, no-c-format
+msgid ""
+"When the <literal>tx</literal> had been set to <varname>rollbackOnly</"
+"varname> and the <methodname>XATerminatorImple.prepare</methodname> method "
+"was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would "
+"be generated and yet the rollback would not be undertaken and the "
+"<literal>tx</literal> reference would be removed meaning no cleanup via the "
+"<methodname>commit</methodname> or <methodname>rollback</methodname> methods "
+"were possible. The <filename>XATerminatorImple.java</filename> file has been "
+"updated to correct this by improving the cleanup and exception reporting for "
+"rollbacks in <methodname>XATerminatorImple.prepare</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:872
+#, no-c-format
+msgid ""
+"The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called "
+"<methodname>beforeCompletion</methodname> but did not call "
+"<methodname>afterCompletion</methodname> when the return status was "
+"<literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</"
+"filename> now has corrected synchronization handling for transaction "
+"termination."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:877
+#, no-c-format
+msgid ""
+"The JCA coordinator did not call synchronizations during the phase commit "
+"cycle (1PC). Synchronization has been added to the JCA coordinator through "
+"the modification of the <filename>SubordinateAtomicAction.java</filename> "
+"file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:882
+#, no-c-format
+msgid ""
+"Coordinator methods would not perform a cleanup correctly. In order to "
+"rectify this cleanup routines have been added to the "
+"<methodname>phase2Commit</methodname> and <methodname>phase2Abort</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:892
+#, no-c-format
+msgid "Security Issues"
+msgstr "Problemas de seguridad"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:896
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>: An exploit existed within the JBoss Web Services component of the "
+"Enterprise Application Platform that would allow anyone to view any xml file "
+"from any location if <literal>&amp;resource=path/of/an/xmlfile.xml</literal> "
+"was applied to the end of any WSDL (Web Services Definition Language) access "
+"URL. The <filename>WSDLRequestHandler.java</filename> file has been updated "
+"to only allow the parent of a WSDL file, a servers data or WSDL or "
+"overridden WSDL publish directories access to xml file resources. Additional "
+"test files are also included which were created to ensure proper operation "
+"was being undertaken. (CVE-2009-0027 )"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:908
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1649\">JBPAPP-1649</"
+"ulink>: The documentation on the isolation of JGroup channels within the "
+"Server Configuration Guide was missing two parameters specific to the "
+"Enterprise Application Platform 4.3 distribution. The parameters of "
+"<varname>-Djboss.messaging.controlchanneludpport</varname> and <varname>-"
+"Djboss.messaging.datachanneludpport</varname> have been includedin section "
+"19.7.10 with example ports and the text addressing the concern of "
+"<emphasis>Why do I need to change the multicast port if I change the address?"
+"</emphasis> has been updated to reflect what is happening in an improved way."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:914
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1498\">JBPAPP-1498</"
+"ulink>: File set information within the Getting Started Guide (sections "
+"2.2.2 and 2.2.3) was outdated and required new information added and old "
+"information removed from the <literal>default</literal> server configuration "
+"file set and the contents of the <literal>conf</literal>, <literal>deploy</"
+"literal> and <literal>all</literal> directory sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:919
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1472\">JBPAPP-1472</"
+"ulink>: The instructions for adding SSL to EJB 2.1 in the Server "
+"Configuration Guide were incorrect as they did not include code pertaining "
+"to marshalling. The appropriate code has now been added to the instructions "
+"in section 9.8.2.3."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:924
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1362\">JBPAPP-1362</"
+"ulink>: The Getting Started Guide section 2.3 has been updated to include "
+"information about the <code>-b</code> option (and equivalents) that can be "
+"used on the command line to change the binding addresses of the Enterprise "
+"Application Platform for remote connectivity."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:929
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1346\">JBPAPP-1346</"
+"ulink>: Confusion existed when starting and stopping a <code>ZIP</code> "
+"installation of the server locally or remotely because a different username "
+"and password may be used. The Getting Started Guide has now been updated to "
+"explain that user credentials for the operating system will be used for "
+"local authentication and JBoss server credentials for remote authentication."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:937
+#, no-c-format
+msgid "Core Server"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:941
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1670\">JBPAPP-1670</"
+"ulink>: The JacORB component of the Enterprise Application Platform has been "
+"upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:946
+#, no-c-format
+msgid ""
+"A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to "
+"become unresponsive during shutdown. In rectifying this issue, the "
+"<filename>POA.java</filename> file has been modified so that instead of "
+"executing:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:949
+#, no-c-format
+msgid "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:950
+#, no-c-format
+msgid "the following is now executed:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:953
+#, no-c-format
+msgid "throw new ObjectNotActive();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:958
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1636\">JBPAPP-1636</"
+"ulink>: Affecting only third party adapters was an issue when one of these "
+"adapters handled the scheduling of work to be performed. The "
+"<classname>ExecutionContext</classname> class contained a value in seconds, "
+"from which the <methodname>getCompletionTimeout</methodname> method of "
+"<classname>org.jboss.resource.work.WorkWrapper</classname> obtains its "
+"information. An issue arises with <methodname>getCompletionTimeout</"
+"methodname> expecting the value to be in milliseconds, creating an error "
+"where the initially set timeout value may be 6 seconds but be passed to the "
+"thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> "
+"file has been updated and correctly converts the timeout value from seconds "
+"to milliseconds."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:963
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1635\">JBPAPP-1635</"
+"ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced "
+"for this release with new error codes of 17002 (connection reset) and 17008 "
+"(connection closed) now able to be handled. These enhancements have been "
+"applied to the <filename>OracleExceptionSorter.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:968
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1602\">JBPAPP-1602</"
+"ulink>: A <exceptionname>ConcurrentModificationException </exceptionname> "
+"would occur when a classloader would be undeployed while another user was "
+"attempting to load a class from the package. This error arose because the "
+"<classname>packagesMap</classname> within "
+"<classname>UnifiedLoaderRepository3</classname> had a <classname>TreeSet</"
+"classname> that was not correctly synchronized with changes. In order to "
+"rectify this, the <filename>ClassLoaderUtils.java</filename> file has been "
+"updated to import the <classname>Collections</classname> library and use the "
+"<methodname>synchronizedSet</methodname> method of the library in returning "
+"the <methodname>TreeSet</methodname> of the <methodname>newPackageSet</"
+"methodname> method."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:973
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1540\">JBPAPP-1540</"
+"ulink>: Within the cluster section of the Enterprise Application Platform, "
+"the <classname>GossipRouter</classname> and <classname>GossipClient</"
+"classname> (TCPGOSSIP) did not have socket read timeouts, socket linger "
+"timeouts and backlog set to provide the best behavior when heavily utilized "
+"or under network situations in need of improvement. This fix provides "
+"default values and configuration options for these in order to avoid "
+"problematic situations."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:978
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1539\">JBPAPP-1539</"
+"ulink>: When running parallel instances of the Enterprise Application "
+"Platform on Linux a bug existed where messages between the JGroups component "
+"of each instance would be picked up by both because all messages sent to the "
+"port number for Multicast Sockets would be picked up by both instances. The "
+"issue has been fixed by re-writing the code for Multicast Sockets so that "
+"the constructor uses a group address along with the port number as "
+"identifiers. This ensures that an instance of the EAP only receives messages "
+"pertaining to its specific group and thus inhibits channel crosstalk."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:983
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1538\">JBPAPP-1538</"
+"ulink>:The Probe Client had not been updated to use the same address as the "
+"Probe Listener does which is now 224.0.75.75. Correcting this issue, the "
+"Proble Client now uses 224.0.75.75 instead of 224.0.0.75 which allows the "
+"client and the listener to work together correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:988
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1535\">JBPAPP-1535</"
+"ulink>: The JDBCExtCacheLoader didn't handle persistent state transfer "
+"correctly since the <methodname>storeState</methodname> method would use "
+"available space on the <classname>MarshalledValueInputStream</classname> "
+"instead of on the <classname>ByteArrayInputStream</classname>. To correct "
+"the stream usage, <filename>JDBCExtendedCacheLoader.java</filename> has been "
+"updated to store the new state using the <varname>in_stream</varname> value "
+"as long as there is space available."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:993
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1534\">JBPAPP-1534</"
+"ulink>: The JDBCCacheLoader didn't work with Sybase as it tried to set a "
+"null <varname>BLOB</varname> (Binary Large OBject) column which is "
+"unsupported in Sybase. To correct this the <filename>JDBCCacheLoader.java</"
+"filename> and <filename>AdjListJDBCCacheLoader.java</filename> files have "
+"been updated to select the Sybase Driver if Sybase is to be used, ensuring "
+"that null values are set as <varname>LONGVARBINARY</varname> rather than "
+"<varname>BLOB</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:998
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1532\">JBPAPP-1532</"
+"ulink>: The JGroups clustering component of the Enterprise Application "
+"Platform has been upgraded to version 2.4.5. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1003
+#, no-c-format
+msgid ""
+"The probe listener within JGroups still used the old default address of "
+"224.0.0.75 instead of the new address of 224.0.75.75. The probe listener "
+"within JGroups has been updated with this release to use the correct default "
+"address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1008
+#, no-c-format
+msgid ""
+"The MPING protocol which sends a multicast ping over TCP contained cross-"
+"talk in Linux. the MPING protocol has since been corrected to eliminate "
+"cross-talk on the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1013
+#, no-c-format
+msgid ""
+"A problem was encountered within JGroups when two distinct processes were "
+"setup on the same machine, each using a different stack with different UDP "
+"multicast addresses. The issue was that each process would not work "
+"correctly because of the other, as each process would receive incorrect "
+"datagrams in reference to the groups each joined. To correct this the "
+"<classname>MulticastSocket</classname> constructor is now used in "
+"combination with a <varname>SocketAddress</varname> when JGroups is used on "
+"the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1018
+#, no-c-format
+msgid ""
+"The <literal>Gossip Router</literal> component of JGroups provided options "
+"to set <literal>backlog</literal>, <literal>socket read timeout</literal> "
+"and <literal>socket linger timeout</literal> within the code, however these "
+"options are not available via the command line. This update of the JGroups "
+"component, now includes the availability of these options to be set through "
+"the command line."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1023
+#, no-c-format
+msgid ""
+"Within the <literal>Gossip Router</literal> component of JGroups "
+"<methodname>Math.min</methodname> was used in calculating the socket linger "
+"timeout which caused incorrect results since this meant that the socket "
+"linger timeout would always be 1. <literal>Gossip Router</literal> has been "
+"updated to instead use <methodname>Math.max</methodname> in the calculation "
+"of the socket linger timeout."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1028
+#, no-c-format
+msgid ""
+"The <classname>RouterStub</classname> and <classname>GossipRouter</"
+"classname> classes have the <varname>setSoLinger</varname> value set "
+"incorrectly to use a seconds value when <varname>setSoLinger</varname> uses "
+"millisecond values. This meant that a value of 500 was 500 seconds rather "
+"than 500 milliseconds. The <classname>RouterStub</classname> class has had "
+"its <varname>setSoLinger</varname> corrected and the "
+"<classname>GossipRouter</classname> class has had the <varname>setSoLinger</"
+"varname> value corrected and timouts configurable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1035
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1530\">JBPAPP-1530</"
+"ulink>: The JCA adapter inflow did not roll back messages if a non-xa "
+"connection factory was being used within the JNDIProviderAdapter. In order "
+"to fix this issue the <filename>JmsServerSession.java</filename> file has "
+"been updated with added logic to the local transaction separation strategy "
+"as to allow for non-xa sessions to be rolled back using transaction session."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1040
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1521\">JBPAPP-1521</"
+"ulink>: The <classname>CleanShutdownInterceptor</classname> class would log "
+"a <exceptionname>GenericClusteringException</exceptionname> when the "
+"container had failed to shut down correctly or failed to start correctly and "
+"because of this behavior the error message displayed because of the "
+"exception should be updated to indicate that it may be an issue with the "
+"container failing to start instead of only failing to shut down. In this "
+"latest Enterprise Application Platform update, the error message has been "
+"updated to reflect both situations which may be the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1045
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1458\">JBPAPP-1458</"
+"ulink>: The JTA recovery configuration did not contain a line to enable "
+"JBoss Messaging (JBM) <classname>XAResourceRecovery</classname> even though "
+"it is stated in the JBM user guide. This CP release modifies the "
+"<filename>build-distr.xml</filename> file to all "
+"<classname>XAResourceRecovery</classname> to be enabled for JTA recovery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1050
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1479\">JBPAPP-1479</"
+"ulink>: Within the different distributions of the Enterprise Application "
+"Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and "
+"<filename>JBoss Messaging</filename> application policies have been present "
+"within the <filename>login-config.xml</filename> file, when "
+"<filename>JBossMQ</filename> is only included in the 4.2 distribution and "
+"<filename>JBoss Messaging</filename> is similarly only included in the 4.3 "
+"distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1053
+#, no-c-format
+msgid ""
+"This has been rectified in this release by modifying <filename>build.xml</"
+"filename> and <filename>login-config.xml</filename> to differentiate between "
+"requirements for each individual distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1058
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1473\">JBPAPP-1473</"
+"ulink>: The "
+"<classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</"
+"classname> within clustering didn't correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>, which would "
+"lead to the repeated calling of itself and eventually "
+"<exceptionname>StackOverflow</exceptionname> errors. In order to correct "
+"this the <filename>IgnoreUndeployLegacyClusteredSessionNotificationPolicy."
+"java</filename> file has been modified to correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1063
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1460\">JBPAPP-1460</"
+"ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for "
+"this Enterprise Application Platform release. This update corrects numerous "
+"bugs and details on these fixes can be found at <ulink url=\"https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html\">https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1068
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1366\">JBPAPP-1366</"
+"ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the "
+"<option>Oracle</option> schema is specified. To correct this the "
+"<filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has "
+"been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</"
+"methodname> function which changes all dots in a constraint name to "
+"underscores. This ensures that constraint names are compatible with Oracle."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1073
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1307\">JBPAPP-1307</"
+"ulink>: The Persistence Unit (PU) root was incorrectly detected within "
+"deployments that contained nested <filename>.jar</filename> files. The root "
+"PU was being detected as the first nested <filename>.jar</filename> "
+"encountered instead of being the deployment which contains the "
+"<filename>persistence.xml</filename> file. To make sure that the PU root is "
+"always set correctly, the <filename>JmxDeploymentUnit.java</filename> file "
+"has been updated with the removal of testing for the url being null and the "
+"<parameter>deploymentInfo.parent</parameter> not being null. This means that "
+"the url is now always taken straight from the "
+"<parameter>extractDescriptorUrl</parameter> of <filename>META-INF/"
+"persistence.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1078
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1289\">JBPAPP-1289</"
+"ulink>: The JBoss JAXR component of the Enterprise Application Platform has "
+"been upgraded to version 1.2.0.SP2. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1083
+#, no-c-format
+msgid ""
+"In the <filename>org.jboss.jaxr.juddi.JUDDIServlet</filename> and "
+"<filename>org.jboss.jaxr.juddi.transport.SaajTransport</filename> files the "
+"namespace value for <varname>xml:lang</varname> contained <literal>http://"
+"www.w3.org/TR/REC-xml/</literal>, which caused an exception within the metro "
+"stack. The namespace value should instead be null and this has been applied "
+"for this JAXR update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1090
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1275\">JBPAPP-1275</"
+"ulink>: The Xalan part of the Enterprise Application Platform has been "
+"upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the "
+"circumstance where an application which heavily used Xalan within large "
+"multi-threaded environments would encounter blocking situations."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
+"ulink>: El componente JBoss Web Services ha sido actualizado a la versión "
+"2.0.1.SP2_CP02. Esta actualización incorpora varios arreglos y mejoras."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1095
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1267\">JBPAPP-1267</"
+"ulink>: <classname>UserTransaction</classname> (UT) was not able to be "
+"deployed with a clustered proxy that supported sticky transactions "
+"correctly. This has been fixed by modifying numerous files which make "
+"<classname>UserTransaction</classname> deployable with transaction sticky "
+"load balance policies."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1100
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1249\">JBPAPP-1249</"
+"ulink>: The JSF component of the Enterprise Application Platform has been "
+"upgraded to version 1.2_10. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1105
+#, no-c-format
+msgid ""
+"A mixed EL expression ending with a literal failed to parse as a managed "
+"bean property value. The <filename>BeanBuilder.java</filename> file was "
+"updated with the removal of <code>ELUtils.getScope(this.expressionString, "
+"segment);</code> in order to fix this issue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1110
+#, no-c-format
+msgid ""
+"<methodname>LifecycleImpl</methodname> and <methodname>RestoreViewPhase</"
+"methodname> forced the <methodname>responseComplete()</methodname> method "
+"for the status of an existing view. To correct this problem the "
+"<filename>RestoreViewPhase.java</filename> file has been edited with the "
+"code <code>facesContext.responseComplete();</code> removed and replaced with "
+"<code>facesContext.renderResponse();</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1115
+#, no-c-format
+msgid ""
+"For a &lt;h:dataTable&gt; tag which does not set the <varname>var</varname> "
+"attribute, if the UIData component is created using a binding and calls the "
+"<methodname>setVar()</methodname> method to set the <varname>var</varname> "
+"attribute, it would be overwritten as a null value by the &lt;h:"
+"dataTable&gt; tag. This bug has been fixed by modifying the "
+"<filename>HtmlTaglib21Generator.java</filename> file so that component "
+"properties are not set if the tag attribute has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1120
+#, no-c-format
+msgid ""
+"The <classname>BindingValidator</classname> would generate a "
+"<exceptionname>ConverterException</exceptionname> instead of a "
+"<exceptionname>ValidatorException</exceptionname>. For this update, "
+"<classname>BindingValidator</classname> has been modified to generate the "
+"correct exception; <exceptionname>ValidatorException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1125
+#, no-c-format
+msgid ""
+"The cause of a <classname>PostConstruct</classname> exception within the "
+"<classname>BeanBuilder</classname> was not communicated to the user "
+"correctly. To correct the issue so that no information is hidden from the "
+"user, the <exceptionname>ManagedBeanCreationException</exceptionname> has "
+"been updated to provide more information about the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1130
+#, no-c-format
+msgid ""
+"An issue was present that would cause majarra to execute <filename>faces-"
+"config.xml </filename> initialization files twice, creating duplicate "
+"operations. This was caused since a record was not kept of which files had "
+"been initialized and which had not. File initialization tracking has been "
+"implemented to correct this issue and this has seen the modification of the "
+"following files: <filename>ConfigManager.java</filename>, "
+"<filename>ConfigureListener.java</filename>, <filename>WebConfiguration."
+"java</filename>, <filename>ConfigurationResourceProvider.java</filename>, "
+"<filename>MetaInfResourceProvider.java</filename>, "
+"<filename>RIConfigResourceProvider.java</filename> and "
+"<filename>WebResourceProvider.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1135
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.ApplicationObjectInputStream</"
+"classname> extends the functionality of <classname>java.io."
+"ObjectInputStream</classname> but failed to preserve the functionality as "
+"<classname>com.sun.faces.renderkit.ApplicationObjectInputStream</classname> "
+"would fail when primitives were used, unlike the <classname>java.io."
+"ObjectInputStream</classname> class which contains a special case to handle "
+"such a case. This would cause problems for <literal>UIComponents</literal>. "
+"<filename>ApplicationObjectInputStream.java</filename> has been updated to "
+"explicitly handle primitive cases and catch the "
+"<exceptionname>ClassNotFoundException</exceptionname> which may be generated."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1140
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.renderkit.html_basic.OutputLinkRenderer</classname> "
+"did not encode parameters correctly, missing the <literal>URLEncoding</"
+"literal>. <literal>URLEncoding</literal> has been added, correcting this "
+"bug, along with the parameter names."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1145
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.BaseTableRenderer</"
+"classname> did not allow for empty <varname>columnClasses</varname> when "
+"generating columns from user input. The issue was realizing when to create "
+"numerous columns rather just one; for instance if the user input "
+"<literal>foo, </literal> with a trailing space then the expected output "
+"would be one column with the name <literal>foo</literal> and another empty "
+"column. This was not the case though, as <literal>foo, </literal> would "
+"generate just one column with <literal>foo, </literal> in its entirety as "
+"the column name, instead of splitting the columns on the comma. This "
+"behavior has now been corrected so that <classname>com.sun.faces.renderkit."
+"html_basic.BaseTableRenderer</classname> no generates columns correctly, and "
+"in order to achieve this the following files have been updated: "
+"<filename>BasetableRenderer.java</filename>, <filename>GridRenderer.java</"
+"filename> and <filename>TableRenderer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1150
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.MenuRenderer</classname> "
+"class did not correctly differentiate between <literal>Objects</literal>; "
+"for instance the different between <literal>Boolean</literal> and "
+"<literal>boolean</literal>, noting the capitalization of the first. The "
+"error was with the logic in <classname>UISelect</classname> and "
+"<classname>MenuRenderer</classname>. To correct this, proper use of the "
+"converter for these classes has been implemented to deal with Objects "
+"correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1155
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.lifecycle.RestoreViewPhase</classname> called "
+"<methodname>DebugUtil.printTree</methodname> after restoring the view if "
+"debugging was enabled, causing incorrect initialization of calls when a "
+"listbox is being used and returning an incorrect value in the "
+"<classname>RenderResponse</classname> phase. Method calls have been "
+"restructured with the removal of references to the <methodname>DebugUtil."
+"printTree()</methodname> method from <filename>ViewHandlerImpl.java</"
+"filename> and <filename>RestoreViewPhase.java</filename> and "
+"<filename>RenderResponsePhase.java</filename> has been modified to call "
+"<methodname>DebugUtil.printTree</methodname> (if <varname>FINEST</varname> "
+"logging is enabled) at the end of the <classname>RenderResponse</classname> "
+"phase, fixing the issue (with the above changes also) and providing a more "
+"accurate view of the tree."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1159
+#, no-c-format
+msgid ""
+"<literal>CGLIB Enhanced UIComponents</literal> in a component tree would "
+"return a value of null for their class when calling <methodname>getPackage()"
+"</methodname> causing <classname>HtmlInputText.handleAttribute</classname> "
+"to fail as it relies on a not-nulll value. This issue has been corrected by "
+"ignoring a returned value of null from the <methodname>getPackage()</"
+"methodname> method for every instance in the codebase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1164
+#, no-c-format
+msgid ""
+"The <classname>UIComponentBase</classname> did not allow for the children of "
+"a tree to be iterated through in reverse order using a list iterator as it "
+"would produce an <exceptionname>IndexOutOfBoundsException</exceptionname> "
+"when the execution tries to calculate the size of the children. "
+"<methodname>ChildrenListIterator</methodname> method has been modified "
+"within the <classname>UIComponentBase</classname> class by changing the line "
+"of code <code>if ((index &lt; 0) || (index &gt;= list.size())) { </code> to "
+"<code>if ((index &lt; 0) || (index &gt; list.size())) {</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1169
+#, no-c-format
+msgid ""
+"Renderer kits for <filename>faces-config.xml</filename> were processed out "
+"of order depending on if <literal>ICEfaces</literal> or <literal>Mojara "
+"1.2_09</literal> is in use. This occurred due to containing all renderer DOM "
+"nods in a list associated with a namespace. This was done so that the "
+"renderer nodes could then be processed prior to the <literal>RenderKits</"
+"literal> being created and the nodes could be processed using the proper "
+"namespace. However, by placing all the renderers into this list, we lost the "
+"document ordering. The issue has been fixed by associating the renderer "
+"nodes with their owning document and processed in the parsing order."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1175
+#, no-c-format
+msgid ""
+"The <methodname>Class.getPackage()</methodname> method calls to synchronized "
+"methods, inhibiting scalability if the method has to be repeatedly executed. "
+"Use of the <methodname>Class.getPackage()</methodname> method has now been "
+"removed from <filename>UIComponent.java</filename>, <filename>RenderKitUtils."
+"java</filename> and <filename>HtmlComponentGenerator.java</filename>. "
+"Instead, the class name is now checked if it starts with the package name "
+"that is of interest, <classname>javax.faces.component.</classname>. This "
+"includes the components that are generated by the "
+"<classname>HtmlComponentGenerator</classname> since they are packaged in "
+"<classname>javax.faces.component.html</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1180
+#, no-c-format
+msgid ""
+"A bug presented itself in the <classname>RenderKitUtils</classname> class "
+"when a semicolon (<code>;</code>) followed a forward-slash (<code>/</code>) "
+"in a header Accept value (for instance: <code>text/;q=0.5</code>). To "
+"rectify this issue the <classname>RenderKitUtils</classname> class has been "
+"updated to assume <code>*</code> as the subtype for an Accept header that "
+"contains no subtype."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1187
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1224\">JBPAPP-1224</"
+"ulink>: Attribute default values in EJB were not set when in use with "
+"<literal>@Service</literal> and <literal>XMBean XML</literal> . In order to "
+"correct this the behavior has been re-written to improve the mimicking of "
+"<classname>ServerCreator</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1192
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1170\">JBPAPP-1170</"
+"ulink>: When the <methodname>getMBeanInfo</methodname> method is called "
+"within <classname>MBeanServerImpl</classname> and "
+"<classname>RawDynamicInvoker</classname>, the underlying exception to "
+"<exceptionname>NotCompliantMBeanException</exceptionname> is not expressed "
+"to the user. <filename>RawDynamicInvoker.java</filename> has now been "
+"updated to provide this useful information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1197
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1099\">JBPAPP-1099</"
+"ulink>: The <filename>commons-beanutils.jar</filename> file within the "
+"Enterprise Application Platform had the incorrect version in the "
+"<filename>manifest.mf</filename> file. Through the course of correcting this "
+"bug, it was found that the <literal>beanutils</literal> component was "
+"outdated and a newer version contained many advantages. In this update to "
+"the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, "
+"which sees the significant improvement that fixes a memory leak caused by a "
+"circular reference concerning the <classname>WeakHashMap</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1202
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1002\">JBPAPP-1002</"
+"ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be "
+"logged when transactions were not completed between invocations. However "
+"this was an error as BMT Stateful Session Beans are allowed to have this "
+"occurrence and so this logging measure has been removed in this Enterprise "
+"Application Platform update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1207
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
+"ulink>: Discrepancies existed between the port schemes within the "
+"<filename>sample-bindings.xml</filename> file. These include:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-961\">JBPAPP-961</"
+"ulink>: JBoss Web ha sido actualiado a la versión 2.0.0.GA CP06. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1212
+#, no-c-format
+msgid ""
+"The remoting connectors were inserted in different places within the ports "
+"definition sections, making the comparison of the sections more difficult "
+"than was necessary."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1217
+#, no-c-format
+msgid ""
+"The <literal>ports-03</literal> section was missing the <literal>EJB "
+"remoting connector</literal> and the <literal>remoting connector</literal> "
+"sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1222
+#, no-c-format
+msgid ""
+"<literal>mq</literal> was used in the name property of the "
+"<varname>HAJNDIJMSProvider</varname> instead of <literal>jms</literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1227
+#, no-c-format
+msgid ""
+"The <literal>ports-01</literal>, <literal>ports-02</literal>, and "
+"<literal>ports-03</literal> schemes defined the <varname>timeout</varname> "
+"attribute twice in the <literal>JBoss Messaging</literal> section:"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1233
+#, no-c-format
+msgid "The above issues have been fixed appropriately in this update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1238
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-713\">JBPAPP-713</"
+"ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: "
+"PermGen</errorname> error. To correct this issue the Enterprise Application "
+"Platform now uses <filename>beanutils 1.8.0</filename> which fixes this "
+"<errorname>OutOfMemoryError</errorname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1243
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
+"ulink>: JMX source code was being exposed to the user when a "
+"<exceptionname>HTTP Status 500</exceptionname> exception would occur. To "
+"correct this, an error page <filename>genericError.jsp</filename> has been "
+"created and is now displayed whenever a <exceptionname>HTTP Status 500</"
+"exceptionname> exception occurs."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1252
+#, no-c-format
+msgid "Known Issues with this release"
+msgstr "Problemas conocidos con este lanzamiento"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1255
+#, no-c-format
+msgid "Following is a list of known issues at the time of release."
+msgstr ""
+"La siguiente es una lista de los problemas conocidos al momento del "
+"lanzamiento."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1259
+#, no-c-format
+msgid "General Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1263
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>: Footnotes within documentation tables and lists do not appear within "
+"PDFs. This issue resides within FOP and currently no workaround exists. "
+"Where possible footnotes are not used in the circumstances mentioned, "
+"however in documents such as the Release Notes the web address of a JIRA is "
+"automatically generated as a footnote and places a number beside that of the "
+"JIRA, referencing a footnote that does not appear."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1268
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-885\">JBPAPP-885</"
+"ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</"
+"methodname> or <methodname>RedeliveryDelay</methodname> is set to a value "
+"apart from zero, messages will not be redelivered even though the method "
+"<methodname>session.rollback()</methodname> had been called. This issue will "
+"not be fixed because redelivery delay is handled on the server side and the "
+"message is already acknowledged before delivery of the message with a non "
+"durable subscription. For the Enterprise Application Platform, this means "
+"that redelivery delays with non durable subscriptions cannot be supported."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1276
+#, no-c-format
+msgid "Hibernate Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1280
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1613\">JBPAPP-1613</"
+"ulink>: Null values for columns mapped as boolean in Hibernate, are "
+"persisted as zero instead of null. When the <methodname>PreparedStatement."
+"setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the "
+"Sybase environment, Sybase JDBC converts the null value to a zero because "
+"Sybase does not allow null bit columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1285
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
+"ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it "
+"should be set up to use image and text. Tests attaining to this currently "
+"fail with the message:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Permite configurar múltiples instancias en una máquina utilizando un "
+"método subpackage. Esta funcionalidad se añadió en este lanzamiento con los "
+"archivos -bin."
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1288
+#, no-c-format
+msgid ""
+"The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not "
+"supported and should not be called."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1291
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1554\">JBPAPP-1554</"
+"ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</"
+"methodname> method within Hibernate fails since Sybase currently only allows "
+"one column in a subquery select list, with the only exception to this being "
+"that a subquery in an <code>EXISTS()</code> predicate can have <code>*</"
+"code> as the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1294
+#, no-c-format
+msgid ""
+"The current workaround for this is to not use the HQL <methodname>elements()"
+"</methodname> method if the elements have a composite key. Instead the HQL "
+"should be reformatted to ensure there is no subquery with more than one item "
+"in the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1299
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1546\">JBPAPP-1546</"
+"ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be "
+"used to create stored procedures while in chained transaction mode. The "
+"suggested workaround for this case is to add the following code follwing the "
+"defining of the new stored procedure:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:1302
+#, no-c-format
+msgid ""
+"&lt;database-object&gt;\n"
+"        &lt;create&gt;\n"
+"                sp_procxmode paramHandling, 'chained'\n"
+"        &lt;/create&gt;\n"
+"        &lt;drop/&gt;\n"
+"&lt;/database-object&gt;"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1305
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
+"ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase "
+"environment and there are three or more joins where at least one of the "
+"joins involves a union."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Permite configurar múltiples instancias en una máquina utilizando un "
+"método subpackage. Esta funcionalidad se añadió en este lanzamiento con los "
+"archivos -bin."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1308
+#, no-c-format
+msgid ""
+"A workaround for this issue exists where it is reconmended that a user does "
+"not use <literal>join fetches</literal> involving <literal>union subclasses</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1313
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1230\">JBPAPP-1230</"
+"ulink>: In the Sybase environment when creating a subquery with an alias in "
+"use, the query will be incorrectly generated and cause an "
+"<exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. "
+"This bug impacts the following tests such that at present they are expected "
+"to fail: <classname>CriteriaQueryTest.testSubselect</classname>, "
+"<classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, "
+"<classname>DynamicFilterTest.testCriteriaControl</classname> and "
+"<classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1316
+#, no-c-format
+msgid ""
+"The known workaround is to use a HQL query instead of using a "
+"<methodname>DetachedCriteria</methodname> method in a subquery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1321
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1082\">JBPAPP-1082</"
+"ulink>: A limitation in the PostgreSQL JDBC driver causes a "
+"<exceptionname>javax.persistence.RollbackException</exceptionname>. This "
+"occurs when the <code>char</code> property is used without a value set as "
+"Hibernate then persists a string containing the character <code>\\u0000</"
+"code>, which causes PostgreSQL to generate an exception as it does not allow "
+"this character to be embedded in a string."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1324
+#, no-c-format
+msgid ""
+"Currently a workaround for persisting the <code>\\u0000</code> character in "
+"a <code>char</code> column using PostgreSQL does not exist. Instead it is "
+"reconmended that to persist a null value for the <code>char</code> property "
+"when it is uninitialized, the <methodname>java.lang.Character</methodname> "
+"method should be used."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1329
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1081\">JBPAPP-1081</"
+"ulink>: In the Entity Manager documentation it is stated that table aliases "
+"are supported in <code>update</code> clauses, however at present this is not "
+"the case. To fix this, the code has to be modified to remove the "
+"identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1334
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1068\">JBPAPP-1068</"
+"ulink>: When using Microsoft SQL and <code>@Type(type=\"text\")</code> in "
+"creating a table, the field is correctly created as <code>\"text\"</code> "
+"however when a delete operation is issued the field becomes set as a "
+"<varname>varchar</varname>, forcing the Microsoft SQL driver to return the "
+"error:"
+msgstr ""
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1337
+#, no-c-format
+msgid ""
+"The data types text and nvarchar are incompatible in the equal to operator."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1340
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1063\">JBPAPP-1063</"
+"ulink>: Currently MySQL does not support millisecond and microsecond "
+"measurements when returning database values such as <code>TIME</code> and "
+"<code>TIMESTAMP</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1345
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-953\">JBPAPP-953</"
+"ulink>: Hibernate Core and Annotations do not currently support the "
+"Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the "
+"Hypersonic database is planned for future releases."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: El componente JBoss Remoting de EAP ha sido actualizado a la versión "
+"2.2.2.SP8. Esta actualización incluye varias soluciones de errores."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1350
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-946\">JBPAPP-946</"
+"ulink>: Within the Hibernate Entity Manager three different "
+"<exceptionname>NullPointerExceptions</exceptionname> are being investigated "
+"in relation to the EJB3 configuration, transaction operations when they are "
+"extended and packaging."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1355
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-906\">JBPAPP-906</"
+"ulink>: A bug exists within the Hibernate Core whereby the unstable "
+"synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is "
+"utilized creating a deserialized String. This causes a problem where if "
+"multiple threads are loading database rows containing arrays of strings, one "
+"thread is forced to undertake all the procedure while the other threads are "
+"left dormant."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1358
+#, no-c-format
+msgid ""
+"The implemented workaround for this issue is to use <code>-Dsun.lang."
+"ClassLoader.allowArraySyntax=true</code>, which can be a default setting "
+"within the <filename>run.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1363
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Within the Hibernate component of the Enterprise Application "
+"Platform the HashMap and HashSet iteration order changed from past releases "
+"because of support for JDK 1.6. However this has meant that the order of "
+"columns in union clauses and union-subclasses has changed, generating a "
+"slight impact on the components performance."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Dentro del componente Hibernate del EAP el orden de las iteraciones "
+"HashMap y HashSet cambió con referencia a los lanzamientos pasados debido al "
+"soporte para JDK 1.6. Sin embargo esto significa que el orden de las "
+"columnas en cláusulas unión y sub-clases unión ha cambiado, generando un "
+"pequeño impacto en el rendimiento de los componentes."

Added: projects/docs/enterprise/4.3.4/readme/es-ES/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/es-ES/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/es-ES/Revision_History.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,28 @@
+# translation of readme.po to
+# Language es-ES translations for readme package.
+# Automatically generated, 2008.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 11:00+1000\n"
+"Last-Translator: Angela Garcia\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/es-ES/readme.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/es-ES/readme.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/es-ES/readme.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -158,7 +158,8 @@
 msgstr ""
 "Esta sección contiene información relacionada con la instalación o "
 "actualización a JBoss Enterprise Application Platform version &VERSION;,"
-"incluyendo los requisitos y los pre-requisitos del hardware y las plataformas. "
+"incluyendo los requisitos y los pre-requisitos del hardware y las "
+"plataformas. "
 
 #. Tag: title
 #: readme.xml:53
@@ -305,11 +306,11 @@
 msgstr ""
 "Si está utilizando el rpm o la distribución en formato zip observe que por "
 "defecto se habilita la autenticación y no se configuran las cuentas de "
-"usuario. Esto se hace con el fin de prevenir el acceso no autorizado a varios de los "
-"servicios de JBoss AS. Consulte el manual de instalación o vea <ulink url="
-"\"http://kbase.redhat.com/faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/"
-"faq/FAQ_107_9963.shtm</ulink> para obtener mayor información sobre como "
-"hacer accesibles los servicios de nuevo. "
+"usuario. Esto se hace con el fin de prevenir el acceso no autorizado a "
+"varios de los servicios de JBoss AS. Consulte el manual de instalación o vea "
+"<ulink url=\"http://kbase.redhat.com/faq/FAQ_107_9963.shtm\">http://kbase."
+"redhat.com/faq/FAQ_107_9963.shtm</ulink> para obtener mayor información "
+"sobre como hacer accesibles los servicios de nuevo. "
 
 #. Tag: title
 #: readme.xml:102
@@ -350,20 +351,25 @@
 #. Tag: ulink
 #: readme.xml:116
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:120
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:124
 #, no-c-format
 msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
 
 #. Tag: title
 #: readme.xml:131
@@ -583,7 +589,8 @@
 #: readme.xml:269
 #, no-c-format
 msgid "Following is a list of issues fixed in this release:"
-msgstr "La siguiente es una lista de los problemas resueltos en este lanzamiento: "
+msgstr ""
+"La siguiente es una lista de los problemas resueltos en este lanzamiento: "
 
 #. Tag: para
 #: readme.xml:277
@@ -785,10 +792,10 @@
 "supporting JDK 6."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-915\">JBPAPP-915</"
-"ulink>: Una operación de fusión fallaba cuando había una entidad "
-"transitoria que se podía alcanzar por múltiples rutas y por lo menos una de "
-"estas rutas no realizaba cascada al llevar a cabo una fusión. Este problema "
-"ha sido arreglado con el EAP 4.3 que ahora soporta JDK 6. "
+"ulink>: Una operación de fusión fallaba cuando había una entidad transitoria "
+"que se podía alcanzar por múltiples rutas y por lo menos una de estas rutas "
+"no realizaba cascada al llevar a cabo una fusión. Este problema ha sido "
+"arreglado con el EAP 4.3 que ahora soporta JDK 6. "
 
 #. Tag: para
 #: readme.xml:376
@@ -882,7 +889,10 @@
 "number is included with this release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1004\">JBPAPP-1004</"
-"ulink>: Versiones anteriores de EAP contenía un número <property>serialVersionUID</property> incorrecto, el cual interfería con la compatabilidad retroactiva. El número <property>serialVersionUID</property> correcto está incluido con este lanzamiento."
+"ulink>: Versiones anteriores de EAP contenía un número "
+"<property>serialVersionUID</property> incorrecto, el cual interfería con la "
+"compatabilidad retroactiva. El número <property>serialVersionUID</property> "
+"correcto está incluido con este lanzamiento."
 
 #. Tag: title
 #: readme.xml:428
@@ -1159,7 +1169,9 @@
 "bin files."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>: Permite configurar múltiples instancias en una máquina utilizando un método subpackage. Esta funcionalidad se añadió en este lanzamiento con los archivos -bin."
+"ulink>: Permite configurar múltiples instancias en una máquina utilizando un "
+"método subpackage. Esta funcionalidad se añadió en este lanzamiento con los "
+"archivos -bin."
 
 #. Tag: para
 #: readme.xml:513
@@ -1170,7 +1182,13 @@
 "additional installation only and cannot be used in place of a regular RPM "
 "jbossas installation. If you only have one version of the AS, it will have "
 "to be the regular RPM installation (or ZIP or installer for older versions)."
-msgstr "Es importante observar que se requiere una instalación jbossas regular en el servidor primero antes de la instalación de -bin. El -bin es para una instalación adicional sólamente y no se puede utilizar en lugar de la instalación jbossas RPM regular. Si sólo tiene una versión del AS entonces tendrá que ser una instalación RPM regular (o con ZIP o por medio del instalador para versiones anteriores). "
+msgstr ""
+"Es importante observar que se requiere una instalación jbossas regular en el "
+"servidor primero antes de la instalación de -bin. El -bin es para una "
+"instalación adicional sólamente y no se puede utilizar en lugar de la "
+"instalación jbossas RPM regular. Si sólo tiene una versión del AS entonces "
+"tendrá que ser una instalación RPM regular (o con ZIP o por medio del "
+"instalador para versiones anteriores). "
 
 #. Tag: title
 #: readme.xml:517
@@ -1190,7 +1208,8 @@
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-857\">JBPAPP-857</"
 "ulink>: En la distribución faltaba el archivo .rar <filename>mail-ra.rar</"
 "filename> utilizado dentro del servidor de aplicaciones para recibir correos "
-"electrónicos al utilizar la API JavaMail. Este archivo que faltaba ahora se ha vuelto a incluir. "
+"electrónicos al utilizar la API JavaMail. Este archivo que faltaba ahora se "
+"ha vuelto a incluir. "
 
 #. Tag: title
 #: readme.xml:523
@@ -1232,13 +1251,13 @@
 "With these changes the example now functions correctly under SQL Server 2005."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-844\">JBPAPP-844</"
-"ulink>: El ejemplo de la fuente de datos MSSQL era incompatible con el servidor "
-"SQL 2005. Para solucionar este problema de compatabilidad, se ha actualizado "
-"el <code>driver-class</code> de <code>com.microsoft.jdbc.sqlserver."
-"SQLServerDriver</code> a <code>com.microsoft.sqlserver.jdbc.SQLServerDriver</"
-"code> y el puerto predeterminado para el <code>connection-url</code> ha sido "
-"cambiado de 1433 a 3918. Con estos cambios el ejemplo ahora funciona "
-"correctamente bajo el servidor SQL 2005. "
+"ulink>: El ejemplo de la fuente de datos MSSQL era incompatible con el "
+"servidor SQL 2005. Para solucionar este problema de compatabilidad, se ha "
+"actualizado el <code>driver-class</code> de <code>com.microsoft.jdbc."
+"sqlserver.SQLServerDriver</code> a <code>com.microsoft.sqlserver.jdbc."
+"SQLServerDriver</code> y el puerto predeterminado para el <code>connection-"
+"url</code> ha sido cambiado de 1433 a 3918. Con estos cambios el ejemplo "
+"ahora funciona correctamente bajo el servidor SQL 2005. "
 
 #. Tag: title
 #: readme.xml:535
@@ -1396,11 +1415,10 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
 "ulink>:el código de JavaServer Pages (JSP) se exponía dentro de la consola "
-"jmx cuando encontraba un error de página. Este problema ha sido "
-"abordado chequeando si la clase está utilizando un Bean existente desde el "
-"ámbito requerido o si ha instanciado uno nuevo. Si el del ámbito de la "
-"petición es nulo entonces el usuario es redireccionado a la página "
-"displayMbeans."
+"jmx cuando encontraba un error de página. Este problema ha sido abordado "
+"chequeando si la clase está utilizando un Bean existente desde el ámbito "
+"requerido o si ha instanciado uno nuevo. Si el del ámbito de la petición es "
+"nulo entonces el usuario es redireccionado a la página displayMbeans."
 
 #. Tag: title
 #: readme.xml:577
@@ -1453,4 +1471,3 @@
 "soporte para JDK 1.6. Sin embargo esto significa que el orden de las "
 "columnas en cláusulas unión y sub-clases unión ha cambiado, generando un "
 "pequeño impacto en el rendimiento de los componentes."
-

Modified: projects/docs/enterprise/4.3.4/readme/fr-FR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/fr-FR/Author_Group.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/fr-FR/Author_Group.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to French
+# translation of readme.po to French
 # Language fr-FR translations for readme package.
 #
 # Automatically generated, 2008.
 # Corina Roe <croe at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-08-01 11:07+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-05 14:14+1000\n"
 "Last-Translator: Corina Roe <croe at redhat.com>\n"
 "Language-Team: French <i18 at redhat.com>\n"
 "MIME-Version: 1.0\n"
@@ -16,9 +16,10 @@
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.11.4\n"
 
-#. Tag: corpauthor
-#: Author_Group.xml:5
+#. Tag: author
+#: Author_Group.xml:6
 #, no-c-format
-msgid "Red Hat Documentation Group"
-msgstr "Red Hat Documentation Group"
-
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/fr-FR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/fr-FR/Book_Info.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/fr-FR/Book_Info.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to French
+# translation of readme.po to French
 # Language fr-FR translations for readme package.
 #
 # Automatically generated, 2008.
 # Corina Roe <croe at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-08-01 11:11+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-05 14:14+1000\n"
 "Last-Translator: Corina Roe <croe at redhat.com>\n"
 "Language-Team: French <i18 at redhat.com>\n"
 "MIME-Version: 1.0\n"
@@ -18,30 +18,35 @@
 
 #. Tag: title
 #: Book_Info.xml:6
-#, no-c-format
-msgid "Release Notes"
+#, fuzzy, no-c-format
+msgid "Release Notes CP04"
 msgstr "Notes de mise à jour "
 
 #. Tag: subtitle
 #: Book_Info.xml:7
-#, no-c-format
-msgid "JBoss Enterprise Application Platform 4.3.0.CP02"
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
 msgstr "JBoss Enterprise Application Platform 4.3.0.CP02"
 
 #. Tag: para
-#: Book_Info.xml:11
-#, no-c-format
+#: Book_Info.xml:13
+#, fuzzy, no-c-format
 msgid ""
 "These release notes contain important information related to JBoss "
-"Enterprise Application Platform 4.3.0.CP02 that may not be currently "
+"Enterprise Application Platform 4.3.0.CP04 that may not be currently "
 "available in the Product Manuals. You should read these Release Notes in "
 "their entirety before installing JBoss Enterprise Application Platform 4.3.0."
-"CP02."
-msgstr "Ces notes de mise à jour contiennent des informations importantes sur JBoss Enterprise Application Platform 4.3.0.CP02 qui ne sont peut-être pas actuellement disponibles dans le manuel. Il est recommandé de lire l'intégralité de ces notes de mise à jour avant d'installer JBoss Enterprise Application Platform 4.3.0.CP02."
+"CP04."
+msgstr ""
+"Ces notes de mise à jour contiennent des informations importantes sur JBoss "
+"Enterprise Application Platform 4.3.0.CP02 qui ne sont peut-être pas "
+"actuellement disponibles dans le manuel. Il est recommandé de lire "
+"l'intégralité de ces notes de mise à jour avant d'installer JBoss Enterprise "
+"Application Platform 4.3.0.CP02."
 
 #. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
 #, no-c-format
 msgid "&HOLDER;"
 msgstr "&HOLDER;"
-

Added: projects/docs/enterprise/4.3.4/readme/fr-FR/Release_Notes_CP04.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/fr-FR/Release_Notes_CP04.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/fr-FR/Release_Notes_CP04.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,3084 @@
+# translation of readme.po to French
+# Language fr-FR translations for readme package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-05 14:14+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:9
+#, no-c-format
+msgid "Introduction"
+msgstr "Introduction"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:12
+#, no-c-format
+msgid ""
+"These release notes contain important information related to JBoss "
+"Enterprise Application Platform &VERSION;. New features, known problems, "
+"resources, and other current issues are addressed here."
+msgstr ""
+"Ces notes de mise à jour contiennent des informations importantes sur  JBoss "
+"Enterprise Application Platform &VERSION;. On y traite de nouvelles "
+"fonctionnalités, de nouveaux problèmes, ressources, et autres sujets "
+"d'actualité."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:16
+#, no-c-format
+msgid "Overview"
+msgstr "Aperçu"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:17
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform is the next evolutionary step in open "
+"source enterprise software. It is a powerful tool for developing rich, high "
+"performance, Web 2.0 applications on a pure Java Platform."
+msgstr ""
+"JBoss Enterprise Application Platform est la nouvelle étape de l'évolution "
+"en matière de logiciels d'entreprise en source ouverte. C'est un outil "
+"puissant pour développer les applications de haute performance Web 2.0, sur "
+"une Plateforme Java pure."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:20
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform provides complete compatibility with "
+"existing J2EE 1.4 enterprise Java applications. At the same time, almost all "
+"the key features and components defined in the Java EE 5.0 specification are "
+"supported. So your new enterprise Java applications can take immediate "
+"advantage of the Java EE 5.0's significantly simpler POJO-based programming "
+"model."
+msgstr ""
+"JBoss Enterprise Application Platform est totalement compatible avec les "
+"applications J2EE 1.4 enterprise Java. En même temps, presque tous les "
+"composants et fonctions clé définis dans les spécifications Java EE 5.0 sont "
+"pris en charge. Donc, vos applications Java new enterprise peuvent peuvent "
+"bénéficier immédiatement du modèle de programmation basé-POJO Java EE 5.0, "
+"bien plus simple."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:23
+#, no-c-format
+msgid ""
+"Further, by integrating best-of-breed open source frameworks such as JBoss "
+"Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of "
+"innovations in the open source community. As well, JBoss Enterprise "
+"Application Platform is fully tested and supported by Red Hat, and is "
+"certified to work on many leading enterprise hardware and software products."
+msgstr ""
+"De plus, en intégrant des infrastructures SO prestigieuses comme JBoss Seam, "
+"Hibernate, Tomcat, et JBoss Cache, la plate-forme tire avantage des "
+"innovations émanant de la communauté en source ouverte. De plus, JBoss "
+"Enterprise Application Platform est entièrement testée, supportée par Red "
+"Hat, et est certifiée pour opérer sur du matériel varié et sur des logiciels "
+"enterprise principaux.  "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:26
+#, no-c-format
+msgid ""
+"All of which means you can develop your new application taking advantage of "
+"Java EE 5.0 technologies immediately and with the confidence of knowing it "
+"will remain forward-compatible with future versions of the JBoss Platform."
+msgstr ""
+"Tout cela signifie que vous pouvez développer votre nouvelle application en "
+"bénéficiant immédiatement des technologies Java EE 5.0 dans la certitude "
+"qu'elle demeurera compatible avec les versions futures de JBoss Platform."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:32
+#, no-c-format
+msgid "New Features in JBoss Enterprise Application Platform 4.3"
+msgstr "Nouvelles fonctionnalités de JBoss Enterprise Application Paltform 4.3"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:34 Release_Notes_CP04.xml:365
+#, no-c-format
+msgid "JBoss Messaging"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:35
+#, no-c-format
+msgid ""
+"In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
+"with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
+"messaging infrastructure for JBoss Enterprise Application Platform."
+msgstr ""
+"Dans JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 est remplacé "
+"par JBoss Messaging 1.4. JBoss Messaging propose une infrastructure de "
+"messagerie de haut niveau pour la plate-forme JBoss Enterprise Application "
+"Platform."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:40
+#, no-c-format
+msgid "JBoss Web Services 2.0.1"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:41
+#, no-c-format
+msgid ""
+"JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
+"Platform 4.3 and will now provide a complete implementation of JAX-WS."
+msgstr ""
+"JBoss Web Services sont mis à niveau à la version 2.0.1 dans JBoss "
+"Enterprise Application Platform 4.3 et vont maintenant procurer une "
+"implémentation complète de JAX-WS."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:47
+#, no-c-format
+msgid "Component Versions"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:48
+#, no-c-format
+msgid ""
+"This section details the versions of the components which create the "
+"Enterprise Application Platform 4.3 that can be found in this Cumulative "
+"Patch release."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:53
+#, no-c-format
+msgid "JBoss Application Server 4.2.z"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:58
+#, no-c-format
+msgid "Hibernate Core 3.2.4.SP1.CP07"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:63
+#, no-c-format
+msgid "Hibernate Annotations 3.2.1.GA.CP03"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:68
+#, no-c-format
+msgid "Hibernate Entity Manager 3.2.1.GA_CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:73
+#, no-c-format
+msgid "JAF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:78
+#, no-c-format
+msgid "JBoss Cache 1.4.1.SP11"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:83
+#, no-c-format
+msgid "JBoss JAXR 1.2.0.SP2"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:88
+#, fuzzy, no-c-format
+msgid "JBoss Messaging 1.4.0.SP3-CP07"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:93
+#, fuzzy, no-c-format
+msgid "JBoss Remoting 2.2.2.SP11"
+msgstr "JBoss Remoting"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:98
+#, no-c-format
+msgid "JBoss Transactions 4.2.3.SP5.CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:103
+#, fuzzy, no-c-format
+msgid "JBoss Web 2.0.0-6.CP09"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:108
+#, fuzzy, no-c-format
+msgid "JBoss Web Services 2.0.1.SP2_CP05"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:113
+#, no-c-format
+msgid "JGroups 2.4.5"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:118
+#, no-c-format
+msgid "JSF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:123
+#, no-c-format
+msgid "Seam 1.2.1.AP"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:128
+#, no-c-format
+msgid "Xalan 2.7.0.patch02"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:134
+#, no-c-format
+msgid ""
+"The Enterprise Application Platform Server has been redefined for the "
+"enterprise market to a level where direct association to a community release "
+"can no longer be drawn."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:140
+#, no-c-format
+msgid "Installation and Migration Notes"
+msgstr "Notes d'installation et de migration"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:141
+#, no-c-format
+msgid ""
+"This section contains information related to installing or upgrading to "
+"JBoss Enterprise Application Platform version &VERSION;, including hardware "
+"and platform requirements and prerequisites."
+msgstr ""
+"Cette section contient des informations relatives à l'installation et à la "
+"mise à niveau de JBoss Enterprise Application Platform version &VERSION;, y "
+"compris les prérequis et les exigences de la plate-forme et du matériel."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:145
+#, no-c-format
+msgid "Installation Notes"
+msgstr "Notes d'installation"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:146
+#, fuzzy, no-c-format
+msgid ""
+"You must have adequate disk space to install JDK and JBoss Enterprise "
+"Application Platform while also allowing enough space for your applications. "
+"You must have a working installation of JDK 1.5 or 1.6. For the latest "
+"information on supported Operating System / JVM combinations, supported "
+"Database platforms and current information on the revision level of included "
+"components, please refer to <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>. Refer to the "
+"installation guide available online from <ulink url=\"http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
+"instructions to install and verify JBoss Enterprise Application Platform."
+msgstr ""
+"Vous devez posséder suffisamment d'espace disque pour installer la plate-"
+"forme JDK et JBoss Enterprise Application Platform tout en provisionnant de "
+"l'espace pour vos applications. Vous devez posséder une installation "
+"opérante JDK 1.5. Pour les dernières informations sur les combinaisons JMW/"
+"Systèmes d'exploitation supportés, plate-formes Database et informations "
+"courantes sur le niveau de révision des composants inclus, veuillez vous "
+"référer au lien <ulink url=\"http://www.jboss.com/products/platforms/"
+"application/testedconfigurations\">http://www.jboss.com/products/platforms/"
+"application/testedconfigurations</ulink>. Référez-vous au guide "
+"d'installation disponible en ligne sur le lien suivant <ulink url=\"http://"
+"www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://"
+"www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> "
+"pour des instructions détaillées pour installer et vérifier JBoss Enterprise "
+"Application Platform."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:151
+#, fuzzy, no-c-format
+msgid "Upgrading from JBoss Enterprise Application Platform 4.3.0.CP03"
+msgstr ""
+"Mise à niveau à partir de la plate-forme JBoss Enterprise Application "
+"Platform 4.3"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:153
+#, no-c-format
+msgid "Using CSP/JON"
+msgstr "Utiliser CSP/JON"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:154
+#, fuzzy, no-c-format
+msgid ""
+"Refer to <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
+"Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
+msgstr ""
+"Voir <ulink url=\"https://network.jboss.com/confluence/display/DOC/Installing"
+"+a+Patch\">https://network.jboss.com/confluence/display/DOC/Installing+a"
+"+Patch</ulink> pour les instructions sur la manière d'installer un Patch "
+"Cumulatif."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:164
+#, no-c-format
+msgid "Important Notes"
+msgstr "Remarques importantes"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:166
+#, no-c-format
+msgid "Running the example Seam Applications"
+msgstr "Exécuter l'exemple Seam Applications"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:169
+#, no-c-format
+msgid ""
+"It is recommended to run the example Seam applications that are included "
+"with the documentation using the production configuration. Using another "
+"configuration may result in memory issues. Note that the default "
+"configuration for the server to start with, if no other configuration is "
+"specified, is the production configuration."
+msgstr ""
+"Il est recommandé d'exécuter les exemples Seam applications qui sont inclus "
+"dans la documentation, en utilisant la configuration de production. "
+"L'utilisation d'une autre configuration peut résulter par des problèmes au "
+"niveau de la mémoire. Notez que la configuration par défaut du serveur au "
+"départ est la configuration de production, si aucune autre configuration "
+"n'est spécifiée."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:173
+#, no-c-format
+msgid ""
+"To avoid memory issues, adjust the memory settings before deploying the "
+"applications. You can do this by updating <literal>JAVA_OPTS</literal> "
+"settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
+"conf</filename> with these recommended values:"
+msgstr ""
+"Pour éviter les problèmes de mémoire, ajuster les paramètres de mémoire "
+"avant de déployer les applications. Vous pouvez effectuer cela en mettant à "
+"jour les paramètres <literal>JAVA_OPTS</literal> dans le fichier "
+"<filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> avec les "
+"valeurs recommandées:"
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:175
+#, no-c-format
+msgid "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+msgstr "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:178
+#, no-c-format
+msgid ""
+"Refer to the \"Seam Reference Guide\" included in the documentation set "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for "
+"important information regarding the deployment of Seam examples and detailed "
+"information on developing applications using Seam."
+msgstr ""
+"Voir le \"Guide de référence Seam\" inclus dans la documentation "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) pour les "
+"informations principales pour le déploiement des exemples Seam et les "
+"informations détaillées sur les applications de développement utilisant Seam."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:186
+#, no-c-format
+msgid "Default Security Settings"
+msgstr "Paramètres de sécurité par défaut"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:189
+#, no-c-format
+msgid ""
+"If you are using the rpm, or the zip distribution, please note that by "
+"default, authentication is enabled and no user accounts are set up. This is "
+"done to prevent unauthorized access to various services of JBoss AS. Please "
+"refer to the Installation Guide, or see <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
+"ulink> for information on how to make the services accessible again."
+msgstr ""
+"Si vous utilisez le rpm, ou la distribution zip, veuillez noter que par "
+"défaut, l'authentification est activée et qu'aucun compte utilisateur n'est "
+"mis en place. Ceci est conçu pour éviter tout accès non autorisé aux divers "
+"services JBoss AS. Veuillez consulter le guide d'installation, ou bien voir "
+"<ulink url=\"http://kbase.redhat.com/faq/FAQ_107_9963.shtm\">http://kbase."
+"redhat.com/faq/FAQ_107_9963.shtm</ulink> pour accéder aux informations sur "
+"la façon de rendre ces services accessibles à nouveau."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:194
+#, no-c-format
+msgid "Embedded Hypersonic Database"
+msgstr "Embedded Hypersonic Database (Base de données hypersonique intégrée)"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:197
+#, no-c-format
+msgid ""
+"Hypersonic SQL provides default \"out of the box\" database functionality "
+"for evaluation and development use only. It is NOT recommended or supported "
+"as a production-use database. Technical support is not available for this "
+"component, and while we are happy to accept bugs filed against this "
+"component, we do not make any commitment to fix them within a specific "
+"timeframe."
+msgstr ""
+"Hypersonic SQL propose une fonctionnalité de base de données pour "
+"l'évaluation et pour le développement uniquement. N'est PAS recommandé ou "
+"supporté en tant que base de données utilisable en production. Le support "
+"technique n'est pas disponible pour ce composant, et malgré que nous soyons "
+"heureux d'accepter des bogues se rapportant à ce composant, nous ne nous "
+"engageons pas à les réparer sous une période fixe."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:202
+#, no-c-format
+msgid "Source Files"
+msgstr "Fichiers source"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:204
+#, no-c-format
+msgid "SRPMs"
+msgstr "SRPMs"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:208
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:212
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:216
+#, no-c-format
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:223
+#, no-c-format
+msgid "Source ZIP"
+msgstr "Source ZIP"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:228
+#, fuzzy, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP04.zip"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP02.zip"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:237
+#, no-c-format
+msgid "Product Support and License Website Links"
+msgstr "Liens internet pour le support produit et la licence"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:241
+#, no-c-format
+msgid "Support Processes"
+msgstr "Support des processus"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:243
+#, no-c-format
+msgid "http://www.redhat.com/support/process/"
+msgstr "http://www.redhat.com/support/process/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:248
+#, no-c-format
+msgid "Production Support Scope of Coverage"
+msgstr "Etendue du support de production"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:252
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/production"
+msgstr "http://www.redhat.com/support/policy/soc/production"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:258
+#, no-c-format
+msgid "Production Support Service Level Agreement"
+msgstr "Contrat de niveau service pour support de production"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:263
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/production/"
+msgstr "http://www.redhat.com/support/policy/sla/production/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:268
+#, no-c-format
+msgid "Developer Support Scope of Coverage"
+msgstr "Etendue du support développeur"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:273
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/developer/"
+msgstr "http://www.redhat.com/support/policy/soc/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:278
+#, no-c-format
+msgid "Developer Support Service Level Agreement"
+msgstr "Contrat de niveau de service pour le support développeur "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:283
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/developer/"
+msgstr "http://www.redhat.com/support/policy/sla/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:288
+#, no-c-format
+msgid "Product Update and Support Policy by Product"
+msgstr "Mise à jour produit et politique de support par produit"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:293
+#, no-c-format
+msgid "http://www.redhat.com/security/updates/jboss_notes/"
+msgstr "http://www.redhat.com/security/updates/jboss_notes/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:298
+#, no-c-format
+msgid "JBoss End User License Agreement"
+msgstr "Contrat de licence pour l'utilisateur JBoss"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:303
+#, no-c-format
+msgid "http://www.redhat.com/licenses/jboss_eula.html"
+msgstr "http://www.redhat.com/licenses/jboss_eula.html"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:309 Release_Notes_CP04.xml:904
+#, no-c-format
+msgid "Documentation"
+msgstr "Documentation"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:312
+#, no-c-format
+msgid ""
+"Refer to the index.html file in the documentation directory for a list of "
+"included documentation."
+msgstr ""
+"Voir le fichier index.html dans le répertoire documentation pour une liste "
+"couvrant la documentation incluse."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:315
+#, no-c-format
+msgid ""
+"In the zip distribution, documentation for the Platform and its individual "
+"components is distributed in a separate zip file, <filename>jboss-eap-docs-"
+"&lt;version&gt;.zip</filename>."
+msgstr ""
+"Dans la distribution zip, la documentation pour le plate-forme et pour ses "
+"composants individuels, est distribuée dans un fichier zip séparé, "
+"<filename>jboss-eap-docs-&lt;version&gt;.zip</filename>."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:319
+#, no-c-format
+msgid ""
+"On a Linux system, the documentation is found in two rpms that will need to "
+"be installed manually. These rpms are <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename>, and <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. For help with installing rpm packages on Red Hat "
+"Enterprise Linux, please refer to the Red Hat Knowledge base article located "
+"at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+msgstr ""
+"Dans le système Linux, la documentation se trouve dans deux rpm qui devront "
+"être installés manuellement. Ces rpm sont <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename>, et <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. Pour obtenir de l'aide sur l'installation des "
+"packages rpm sur Red Hat Enterprise Linux, veuillez vous référer à l'article "
+"de base Red Hat Knowledge qui se situe  <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_35_198.shtm\">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:326
+#, fuzzy, no-c-format
+msgid ""
+"<filename>Installation Guide</filename> explains how to install and verify "
+"the installation of JBoss Enterprise Application Platform using different "
+"installation modes."
+msgstr ""
+"<filename>Installation Guide</filename> explique comment installer et "
+"comment vérifier l'installation de JBoss Enteprise Application Platform en "
+"utilisant les différents modes d'installation."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:331
+#, no-c-format
+msgid ""
+"<filename>Getting Started</filename> details the directory structure of the "
+"platform and a quick tour of the Application Server and different "
+"configuration sets and services. Using a simple web application it "
+"illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
+"the JSF and EJB3 components."
+msgstr ""
+"<filename>Getting Started</filename> décrit la structure du répertoire de la "
+"plateforme et donne un aperçu rapide du serveur d'application et des "
+"différents services et cas de configurations. Par l'utilisation d'une simple "
+"application web, il illustre l'utilisation des composants JSF-EJB3 et "
+"comment Seam intègre les composants JSF et EJB3."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:336
+#, no-c-format
+msgid ""
+"<filename>Server Configuration Guide</filename> explains all administrative "
+"and configuration functions in detail."
+msgstr ""
+"<filename>Le guide de configuration du serveur</filename> explique toutes "
+"les fonctions administratives et de configuration en détails."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:342
+#, no-c-format
+msgid ""
+"Updated versions of the documentation with errata and additional "
+"information, example application code, as well as the most recent version of "
+"the release notes may be accessed via the web from <ulink url=\"http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+msgstr ""
+"Les versions mises à jour de la documentation comprenant les errata et les "
+"informations supplémentaires, comme le code d'application, ainsi que la "
+"dernière version des notes de mise à jour, sont disponible sur internet par "
+"le lien suivant <ulink url=\"http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/</ulink>."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:357
+#, no-c-format
+msgid "Issues fixed in this release"
+msgstr "Problèmes réglés dans cette version"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:361
+#, no-c-format
+msgid "Following is a list of issues fixed in this release:"
+msgstr "Voici une liste de problèmes réglés dans cette version:"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:369
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1615\">JBPAPP-1615</"
+"ulink>: The JBoss Messaging component of the Enterprise Application Platform "
+"has been upgraded to version 1.4.0.SP3-CP07. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:374
+#, no-c-format
+msgid ""
+"There was an issue with the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method whereby the method delegates checking to "
+"the <classname>ResourceManager</classname> <varname>serverID</varname>. This "
+"instigates the case where the <methodname>xasess2.start(xid, TMJOIN)</"
+"methodname> method is called and the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method returns true but the resource manager does "
+"not hold the transaction state required to perform a <code>TMJOIN</code>. "
+"Further to this when a session is closed the <methodname>SessionAspect."
+"handleClose()</methodname> method is called, yet the <code>tx</code> was "
+"removed from the transaction manager meaning it is no longer in the "
+"<code>conn1</code> resource manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:377
+#, no-c-format
+msgid ""
+"To correct this both the <methodname>MessagingXAResource.isSameRM</"
+"methodname> method and <classname>ResourceManager</classname> have the same "
+"<code>serverID</code> and the same map of transactions, ensuring that if the "
+"<classname>ResourceManager</classname> was to ever return true, the call to "
+"<methodname>start(TMJOIN)</methodname> would correctly succeed. To note is "
+"that the transaction will rollback at completion time and any message "
+"delivered in the <code>tx</code> will be redelivered."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:382
+#, no-c-format
+msgid ""
+"Client connection parameters were not being passed to the JBoss Remoting "
+"layer, leaving parameters such as <varname>validatorPingPeriod</varname> and "
+"<varname>validatorTimeout</varname> to be used with default values within "
+"Remoting instead of the configured values. In correcting this issue, the "
+"<filename>JMSRemotingConnection.java</filename> file has been updated so "
+"that when the <methodname> client.addConnectionListener</methodname> method "
+"is called within the <methodname>addConnectionListener</methodname> and "
+"<methodname>addPlainConnectionListener</methodname> methods, it also passes "
+"the configured parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:387
+#, no-c-format
+msgid ""
+"The <literal>default</literal> profile for JBoss without any reconfiguration "
+"uses the <classname>ClusteredConnectionFactory</classname> with a non-"
+"clustered post-office, however warnings would be logged about this behavior "
+"when the log messages should be reduced from a <varname>WARN</varname> level "
+"to an <varname>INFO</varname> level. The upgrade to this version of JBoss "
+"Messaging sees this implemented within the log."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:392
+#, no-c-format
+msgid ""
+"<classname>ClusterViewUpdateTest</classname> was broken and did not work "
+"correctly in previous releases with the cause being that the expected time "
+"until failure detection for some clustering tests was too long. In order to "
+"correct this the values for <varname>validatorPingPeriod</varname> and "
+"<varname>validatorPingTimeout</varname> have been changed to be 2 seconds "
+"each, combining to 4 seconds as the total time until expected failure "
+"detection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:397
+#, no-c-format
+msgid ""
+"Client connection parameters were not passed to the JBoss Remoting layer, "
+"forcing Remoting to use default values instead of user configured values. In "
+"order to use the correct values, <filename>JMSRemotingConnection.java</"
+"filename> has been updated so that the <methodname>Client."
+"addConnectionListener</methodname> method is used with <varname>listener</"
+"varname> and <varname>serverLocator.gerParameters()</varname> as parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:402
+#, no-c-format
+msgid ""
+"Messages which are scheduled for delivery in the future were not being "
+"removed correctly when the <methodname>removeAllMessages()</methodname> "
+"method was being called, causing the messages to be re-queued as soon as the "
+"application server or queue is restarted. <filename>ChannelSupport.java</"
+"filename> has been updated to import the <filename>TimeoutExt</filename> "
+"library in order to cast the timeout value to <filename>TimeoutExt</"
+"filename> in order to obtain the reference value via the <methodname>get "
+"TimeoutTarget()</methodname> method. With this new reference value "
+"information, the scheduled messages can be correctly removed from the queue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:407
+#, no-c-format
+msgid ""
+"There was an occurrence where a user may deploy a clustered queue in a "
+"single node instead of in all the nodes and the failover process would not "
+"work because of this. When this occurred an <exceptionname>Illegal "
+"StateException</exceptionname> would be generated, however this was not "
+"considered enough of a prominent warning about not deploying clustered "
+"queues correctly. <filename>Messaging PostOffice.java</filename> has now "
+"been updated to log a warning which outlies that clustered destinations must "
+"be deployed on all nodes of a cluster, instead of generating an "
+"<exceptionname>Illegal StateException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:412
+#, no-c-format
+msgid ""
+"The <classname>Client</classname>, <classname>SecurityAspect.check()</"
+"classname> and <classname>ServerConnection FactoryEndpoint</classname> "
+"needed to be able to obtain TLC within a privileged block, otherwise an "
+"<exceptionname>Access ControlException</exceptionname> is produced. To fix "
+"this bug, the <methodname>settle</methodname>, <methodname>gettable</"
+"methodname> and other TLC methods have been set within security blocks; this "
+"prevents access denied exceptions from <classname>Client</classname>, "
+"<classname>SecurityAspect.check()</classname> and "
+"<classname>ServerConnection FactoryEndpoint</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:417
+#, no-c-format
+msgid ""
+"The logging of actions within JBoss Messaging did not include the logging of "
+"messages when they are moved to the expiry or dead letter queues as this was "
+"only logged at trace level. In order to add this enhanced level of logging, "
+"the <filename>ClientConsumer.java</filename> file has been updated to log "
+"warning messages and debug information pertaining to the move of messages to "
+"the expiry or dead letter queues; <filename>Server SessionEndpoint.java</"
+"filename> has also been updated in the same mannor."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:422
+#, no-c-format
+msgid ""
+"There was an error when a message was received under a X tx and the JBoss "
+"Messaging XAResource is prepared but not committed, a message could be "
+"received by another consumer in another transaction while the first is still "
+"in progress. The correct behavior is for JBoss Messaging to hold the message "
+"until the associated transaction is committed or rolled back, enabling "
+"duplication of message deliveries to be avoided. In the <filename>Delivery."
+"java</filename> file, messages are now marked with a boolean value detailing "
+"if they are for delivery with a X transaction and if this transaction is "
+"prepared and <filename>SimpleDelivery.java</filename> now implements this "
+"new information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:427
+#, no-c-format
+msgid ""
+"The <methodname>shutdownNow()</methodname> method was not synchronized and "
+"may cause a <exceptionname>NoSuchElementException</exceptionname> during "
+"runtime as a result. A synchronization block has been placed around the "
+"<methodname>shutdownNow()</methodname> code within "
+"<filename>OrderedExecutorFactory.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:432
+#, no-c-format
+msgid ""
+"There was an issue with the <classname>org.jboss.jms.server.messagecounter."
+"MessageCounter</classname> class not being able to be serialized as it "
+"caused an <exceptionname>UndeclaredThrowableException</exceptionname>. "
+"<filename>MessageCounter.java</filename> has been updated to now import and "
+"implement the <literal>Serializable</literal> library and be given a "
+"<varname>serialVersionUID</varname>, allowing the <classname>org.jboss.jms."
+"server.messagecounter.MessageCounter</classname> class to be serializable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:437
+#, no-c-format
+msgid ""
+"When the methods <methodname>unregisterSucker()</methodname> or "
+"<methodname>registerSucker()</methodname> was called a "
+"<exceptionname>ConcurrentModificationException</exceptionname> would be "
+"generated by the time the <literal>HashSet</literal> containing the "
+"<literal>suckers</literal> was iterated. The issue would present itself on "
+"clusters with a magnitude of nodes (for instance it appeared on a 8 node "
+"cluster but not a 4 node cluster). This bug was corrected by creating an "
+"iterator that used a private set of <literal>suckers</literal> for iteration "
+"through the <literal>HashSet</literal> of <literal>suckers</literal> in "
+"order to avoid the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:442
+#, no-c-format
+msgid ""
+"The bridge within JBoss Messaging would only retry connection creation to a "
+"remote destination after startup and if the remote provider was not "
+"available at startup, the bridge would fail to start. The <filename>Bridge."
+"java</filename> and <filename>BridgeService.java</filename> files have "
+"undergone extensive modification and now the <literal>factory</literal> is "
+"set to the <literal>bridge</literal> which undertakes the lookup itself "
+"instead of looking up the destinations."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:452
+#, fuzzy, no-c-format
+msgid "JBoss Cache"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:456
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
+"ulink>: The JBoss Cache component of the Enterprise Application Platform has "
+"been upgraded to version 1.4.1.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:461
+#, no-c-format
+msgid ""
+"The <classname>JDBCCacheLoader</classname> implementation did not work with "
+"Sybase as it would try to set a null <varname>BLOB</varname> column which is "
+"unsupported within Sybase. To correct this the <filename>JDBCCacheLoader."
+"java</filename> file has been updated so that the Sybase Driver sets a null "
+"<varname>LONGVARBINARY</varname> value, allowing the "
+"<classname>JDBCCacheLoader</classname> implementation to work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:466
+#, no-c-format
+msgid ""
+"The <classname>JDBCExtCacheLoader</classname> did not handle persistent "
+"state transfer correctly since the <methodname>JDBCExtCacheLoader.storeState"
+"()</methodname> method would use available bytes on the "
+"<classname>MarshalledValueInputStream</classname> rather than on the "
+"<classname>ByteArrayInputStream</classname> when storing the persistent "
+"state. This was an issue because the <classname>MarshalledValueInputStream</"
+"classname> always returns a null value, meaning the persistent state was "
+"never written. In fixing this issue the <filename>JDBCExtendedCacheLoader."
+"java</filename> file has been modified so that it specifies to check for "
+"available space on the <classname>ByteArrayInputStream</classname>."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:476
+#, no-c-format
+msgid "JBoss Remoting"
+msgstr "JBoss Remoting"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:480
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
+"ulink>: The JBoss Remoting component of the Enterprise Application Platform "
+"has been upgraded to version 2.2.2.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:485
+#, no-c-format
+msgid ""
+"The <methodname>ConnectionValidator.run()</methodname> method had the "
+"ability to be called by a user before the private method "
+"<methodname>ConnectionValidator.start()</methodname> was called, resulting "
+"in the <varname>clientInvoker</varname> and <varname>timer</varname> fields "
+"being set to null and generating a <exceptionname>NullPointerException</"
+"exceptionname>. Within the <filename>ConnectionValidator.java</filename> "
+"file the fields are now checked to see if they are null upon execution of "
+"the <methodname>ConnectionValidator.run()</methodname> method, one or both "
+"are then an <exceptionname>IllegalStateException</exceptionname> is "
+"displayed to the user outlining that <methodname>ConnectionValidator.run()</"
+"methodname> should not be called directly but "
+"<methodname>addConnectionListener()</methodname> should be used instead."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:490
+#, no-c-format
+msgid ""
+"Two bugs existed within the <methodname>org.jboss.remoting.marshal."
+"MarshallerLoaderHandler.loadClassBytes()</methodname> method that prohibited "
+"remote classloading to work correctly with isolated EARs. The first was that "
+"a while loop in the code needed a break and the second was that the call to "
+"the <methodname>org.jboss.mx.loading.LoaderRepository.getCachedClass()</"
+"methodname> method should have been a general call to "
+"<methodname>LoaderRepository.loadClass()</methodname>. These two issues have "
+"been rectified with this Remoting update, allowing remote classloading to "
+"function correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:495
+#, no-c-format
+msgid ""
+"A bug existed within the Remoting component by which the RemotingClassLoader "
+"would always attempt to load a class over the network first if remote "
+"classloading was enabled, leading to conflicts if the class was available "
+"locally before. The code has been corrected to check locally first before "
+"looking remotely."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:500
+#, no-c-format
+msgid ""
+"The <classname>ServerInvokerCallbackHandler</classname> class would become "
+"unresponsive when calling the <methodname>BlockingCallbackStore.add()</"
+"methodname> method after locking the callback field with a true responce "
+"from the <methodname>persistCallback()</methodname> method. This would occur "
+"because the <methodname>BlockingCallbackStore.getNext()</methodname> needed "
+"to control the lock on the callback field to break the waiting period, "
+"however this could not be achieved because of the wait period. To fix this "
+"issue the call to the <methodname>BlockingCallbackStore.add()</methodname> "
+"method has been removed as it was an unnecessary step."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:505
+#, no-c-format
+msgid ""
+"The <classname>HTTPClientInvoker</classname> did not support Beginner's All-"
+"purpose Symbolic Instruction Code (BASIC) authentication for proxies when "
+"the proxy was configured through system property options of <methodname>http."
+"proxyHost</methodname> and <methodname>http.proxyPort</methodname>. The "
+"issue appears because the <classname>HTTPClientInvoker</classname> would not "
+"check for the existence of these options and in tern it would never create a "
+"<methodname>Proxy-Authorization</methodname> request header, which is "
+"necessary for normal operation. To fix this the "
+"<classname>HTTPClientInvoker</classname> has been modified to check for the "
+"existence of the <methodname>http.proxyHost</methodname> option and if it "
+"detects its use, creates a <methodname>Proxy-Authorization</methodname> "
+"request header."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:510
+#, no-c-format
+msgid ""
+"<classname>HTTPClientInvoker</classname> would generate a "
+"<exceptionname>NullPointerException</exceptionname> when the HTTP server "
+"returned an error code without any content and then the <methodname>java.net."
+"HttpUrlConnection.getInputStream()</methodname> method returned a null "
+"value. In order to improve control over this behavior, the new variable "
+"<varname>UNMARSHAL_NULL_STREAM</varname> has been added to the "
+"<classname>HTTPClientInvoker</classname>. If this variable is set to true "
+"(the default value) the default behavior is executed, however if it is set "
+"to false the call to the <methodname>UnMarshaller.read()</methodname> is "
+"skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:515
+#, no-c-format
+msgid ""
+"Within the <classname>InvokerRegistry</classname> an error existed "
+"associated with the sequencing of events and <classname>serverLocators</"
+"classname> would return a null on occasion. To correct this race condition, "
+"the sequencing of events within the <classname>InvokerRegistry</classname> "
+"has been rearranged so that references to "
+"<classname>transportClientFactoryClasses</classname> and "
+"<classname>clientLocators</classname> are governed by <classname>clientLock</"
+"classname> and references to <classname>transportServerFactoryClasses</"
+"classname>, <classname>serverLocators</classname>, and "
+"<classname>registeredLocators</classname> are governed by "
+"<classname>serverLock</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:520
+#, no-c-format
+msgid ""
+"A bug existed where the value in the client configuration map of the "
+"<classname>ConnectionValidator</classname> would be ignored when the "
+"overloaded <methodname>org.jboss.remoting.Client</methodname> method was "
+"called and the <varname>DEFAULT_PING_PERIOD</varname> variable value was "
+"placed into the metadata map passed to the <classname>ConnectionValidator</"
+"classname>. This has been corrected by updating <classname>org.jboss."
+"remoting.Client.addConnectionListener</classname> so that "
+"<varname>DEFAULT_PING_PERIOD</varname> is only passed if the value of "
+"<varname>VALIDATOR_PING_PERIOD</varname> within the client's configuration "
+"map has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:525
+#, no-c-format
+msgid ""
+"<classname>ConnectionValidator</classname> may become unresponsive then the "
+"<methodname>run()</methodname> method is executed and utilizes the "
+"<varname>lock</varname> variable. The methods within the <methodname>run()</"
+"methodname> method are meant to time out so that the <varname>lock</varname> "
+"variable can become available to the <methodname>notifyListeners()</"
+"methodname> in the event of a network failure; however <methodname>run()</"
+"methodname> may execute again before <methodname>notifyListeners()</"
+"methodname> can. The synchronization on the <varname>lock</varname> variable "
+"has been modified to avoid this issue to enable correct operation."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:530
+#, no-c-format
+msgid ""
+"During occurrences of the server being under heavy load, an "
+"<exceptionname>IllegalStateException</exceptionname> would occur within the "
+"<methodname>ConnectorValidator.run()</methodname> method because further "
+"synchronization on the <varname>lock</varname> variable was necessary. This "
+"issue was fixed during the rectification of the above problem."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:535
+#, no-c-format
+msgid ""
+"A synchronization error within the <classname>MarshalFactory</classname> was "
+"allowing a subsystem to add a marshaller at the same time as EJB3 was trying "
+"to extract one causing users to receive an "
+"<exceptionname>InvalidMarshallingResource</exceptionname> exception; this "
+"also applied to unmarshallers. The error has been fixed by updating the "
+"<filename>jboss-remoting.jar</filename> file to include synchronized static "
+"Maps within the <classname>MarshalFactory</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:540
+#, no-c-format
+msgid ""
+"The <classname>SocketServerInvoker</classname> had an issue when shutting "
+"down <varname>ServerThreads</varname> causing a user to possibly receive an "
+"invocation to a closed <classname>SocketServerInvoker</classname> on the "
+"client side, causing an <exceptionname>InvalidStateException</"
+"exceptionname>. Allowing this exception would cause a clustered EJB3 system "
+"to generate a <exceptionname>UndeclaredThrowableException</exceptionname> "
+"instead of trying alternative servers. To allow for alternatives to be "
+"attempted, an optional behavior of allowing the "
+"<classname>MicroRemoteClientInvoker</classname> to interpret an "
+"<exceptionname>InvalidStateException</exceptionname> as a "
+"<exceptionname>CannotConnectException</exceptionname>, allowing for other "
+"servers to be attempted."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:550
+#, fuzzy, no-c-format
+msgid "JBoss Web"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:554
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1493\">JBPAPP-1493</"
+"ulink>: An error would be shown on occasion by <emphasis>Internet Explorer</"
+"emphasis> because xml content would not be sent when <emphasis>PROPFIND</"
+"emphasis> requests were being used. This has been fixed by creating a new "
+"method within <filename>WebdavServlet.java</filename> that overrides the "
+"<methodname>DefaultServlet</methodname> implementation for servlet request "
+"processing and testing for input before launching the "
+"<methodname>DocumentBuilder</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:559
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1470\">JBPAPP-1470</"
+"ulink>: When using APR (Apache Portable Runtime) on any operating system "
+"other than those which use the Linux Kernal 2.4 or newer, the "
+"<parameter>deferAccept</parameter> option would be set to false in the "
+"<methodname>AprEndpoint</methodname>. This may lead to a "
+"<exceptionname>NullPointerException</exceptionname> as the "
+"<methodname>accepter</methodname> thread starts to process a request while "
+"also calling for a <methodname>poller</methodname> before initialization. "
+"The issue has been resolved by moving the <methodname>acceptor</methodname> "
+"threads to being executed last when starting the <methodname>AprEndpoint</"
+"methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:564
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1334\">JBPAPP-1334</"
+"ulink>: The JBoss Web component of the Enterprise Application Platform has "
+"been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:569
+#, no-c-format
+msgid ""
+"If a war deployment included its own version of <filename>xalan.jar</"
+"filename> and <filename>xercesImpl.jar</filename> in <filename>WEB-INF/lib</"
+"filename>, the JBossWeb servlet container classloader returns JBoss provided "
+"version of the <literal>SAXParser</literal> from "
+"<methodname>SAXParserFactory.newInstance().newSAXParser()</methodname> "
+"rather than the version provided in the war deployment. To fix this bug the "
+"<filename>WebAppClassLoader.java</filename> has been updated to ensure the "
+"correct parser is used."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:579
+#, no-c-format
+msgid "JBoss Web Services"
+msgstr "JBoss Web Services"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:583
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1560\">JBPAPP-1560</"
+"ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component "
+"of the Enterprise Application Platform has been upgraded to version 2.1.4."
+"patch01. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:588
+#, no-c-format
+msgid ""
+"The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package "
+"contains classes to optimize field and method access by dynamically "
+"generating classes. Within the <classname>Injector</classname> class there "
+"is a <literal>HashMap</literal> value that is wrapped within a "
+"<literal>WeakReference</literal> however since there is only a "
+"<literal>WeakReference</literal> to the <classname>Injector</classname> "
+"class within this, the <literal>HashMap</literal> is garbage collected. To "
+"fix this the reference has been changed to a <literal>StrongReference</"
+"literal> and in order to maintain the original requirements, the "
+"<classname>Injector</classname> is now passed a reference to the ClassLoader "
+"instead of containing one specifically."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:595
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1210\">JBPAPP-1210</"
+"ulink>: The JBoss Web Services component of the Enterprise Application "
+"Platform has been upgraded to version 2.0.1.SP2_CP05. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:600
+#, no-c-format
+msgid ""
+"When deploying JBoss Web Services within Enterprise Application Platform "
+"without internet access, <classname>JBossWSEntityResolver</classname> would "
+"not resolve any schemas causing Web Services for Remote Portlets (WSRP) to "
+"produce an error. This issue has been fixed by modifying "
+"<classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader."
+"java</filename> to resolve schemas locally when an internet connection is "
+"unavailable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:605
+#, no-c-format
+msgid ""
+"WSProvide would ignore a <literal>SOAPBinding</literal> declaration "
+"specified in the EJB3 stateless session bean. To correct this and allow "
+"<literal>SOAPBinding</literal> to work as expected the following files have "
+"been modified: <filename>WSDLGenerator.java</filename>, "
+"<filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, "
+"<filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</"
+"filename> and <filename>WSDL11Writer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:610
+#, no-c-format
+msgid ""
+"The component <emphasis>Xerces</emphasis> of JBoss Web Services has a "
+"feature that optimizes the parsing of messages called <methodname>Deffered "
+"Node Expansion</methodname>.This defers node expansion until the nodes are "
+"accessed, improving performance where not all nodes need to be visited. "
+"However memory overheads are increased, which can be considerable for large "
+"messages."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:613
+#, no-c-format
+msgid ""
+"This release grants the user an option to disable the <methodname>Deffered "
+"Node Expansion</methodname> feature and have all nodes expand. To achieve "
+"this the following system property needs to be set:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:616
+#, no-c-format
+msgid "-Dorg.jboss.ws.disable_deferred_node_expansion=true"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:619
+#, no-c-format
+msgid ""
+"A regression with <literal>TCK5 SAAJ</literal> in the <classname>SOAPBody</"
+"classname> class was introduced with a fix to a previous bug and this has "
+"now been rectified by modifying the <filename>SOAPBodyImpl.java</filename> "
+"file to perform a <code>break</code> after assigning the "
+"<varname>childElement</varname> property."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:624
+#, no-c-format
+msgid ""
+"The end points for a <literal>transport-guarantee</literal> that is set to "
+"be confidential would see an attempt to exactly map the URL pattern in the "
+"WSDL. However since the servlet and security constraints will not be defined "
+"exactly the same a bug occurred whereby JBoss Web Services would assume the "
+"<literal>transport-guarantee</literal> was not confidential when generating "
+"the address, causing the WSDL to be generated with a http address. The "
+"<literal>transport-guarantee</literal> would still be enforced by JBoss Web "
+"Services as confidential but the WSDL would contain the wrong address, "
+"leading to clients attempting to connect to an incorrect address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:627
+#, no-c-format
+msgid ""
+"In order to rectify this occurrence, the <filename>MetaDataBuilder.java</"
+"filename> file has been modified so that when testing the servlet pattern it "
+"also tests correctly for the security constraint instead of assuming both "
+"with be of the same value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:632
+#, no-c-format
+msgid ""
+"When creating messages in SOAP 1.2 without attachments, the "
+"<classname>SOAPMessageImpl</classname> class sets the <varname>contentType</"
+"varname> variable to <literal>text/xml</literal>, which was incorrect. This "
+"has now been rectified by amending <varname>contentType</varname> to use the "
+"value <literal>application/soap+xml</literal> by adding the "
+"<methodname>getSAPContentType()</methodname> method to "
+"<filename>SOAPMessageImpl.java</filename> and updating "
+"<filename>DispatchImpl.java</filename> to correctly reference the SOAP "
+"message context."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:638
+#, no-c-format
+msgid ""
+"Deployments of JAX-WS nature would fail for JBoss AOP instrumented "
+"endpoints, generating an <exceptionname>IllegalAnnotationsException</"
+"exceptionname> as JBoss Web Services attempted to process the JBoss AOP "
+"methods. <filename>JAXWSMetaDataBuilder.java</filename> has been updated to "
+"mark JBoss AOP methods as synthetic which allows them to be skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:643
+#, no-c-format
+msgid ""
+"WSDL dynamic address replacement was not working correctly in previous "
+"versions of the Enterprise Application Platform since port and protocol "
+"numbers were not being considered. The <filename>WSDLRequestHandler.java</"
+"filename> file has been modified to use a new URL and protocol instead of "
+"the original URL and protocol in order to use the dynamically generated port "
+"and protocol numbers."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:648
+#, no-c-format
+msgid ""
+"In converting WSDL to Java, anonymous types that are nested within anonymous "
+"types generated a JAX-RPC mapping that did not match the source. The "
+"<filename>MappingFileGeneratorHelper.java</filename> file has been corrected "
+"to ensure that the generated mapping matches the source of the information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:653
+#, no-c-format
+msgid ""
+"JAAS certificate authentication support was not supported in the JBoss Web "
+"Services Security implementation, meaning that authentication via this "
+"method could not take place based on the certificate the client used to sign "
+"the message. Support for this has been added to JBoss Web Services and in "
+"tern the Enterprise Application Platform with this component upgrade."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:658
+#, no-c-format
+msgid ""
+"When the default port for a protocol was being used within JBoss Web "
+"Services, the port number still appeared at the end of the URL even though "
+"this was unnecessary. In order to remove the port number from the end of the "
+"URL, the <filename>MetaDataBuilder.java</filename> has been modified for "
+"each individual service that uses the default port."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:663
+#, no-c-format
+msgid ""
+"When JBoss Web Services is being used as a client, the information within "
+"the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not "
+"cleared for incoming client calls. In order to fix this the call to "
+"<methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the "
+"<classname>MessageContextAssociation</classname> class and is executed once "
+"the last message has been processed. The files that have been updated in "
+"order to incorporate the fix are: <filename>DOMUtils.java</filename>, "
+"<filename>XMLContent.java</filename>, <filename>ProviderImpl.java</"
+"filename>, <filename>MessageContextAssociation.java</filename>, "
+"<filename>MessageContextJAXWS.java</filename> and "
+"<filename>RequestHandlerImpl.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:668
+#, no-c-format
+msgid ""
+"When the <varname>webServiceHost</varname> property was not set, the <ulink "
+"url=\"http://localhost:8080/jbossws/services \">http://localhost:8080/"
+"jbossws/services</ulink> page presented the host name as "
+"<exceptionname>jbossws.undefined.host</exceptionname>. A "
+"<methodname>createAddress</methodname> method has been added to "
+"<filename>ContextServlet.java</filename> which dynamically updates the WSDL "
+"and XSD files with the address from the request URL before displaying "
+"information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:674
+#, no-c-format
+msgid ""
+"The JBoss Web Services upgrade 2.0.1.SP2_CP05 also includes the security fix "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>, discussed in the Security Issue section."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:683
+#, no-c-format
+msgid "JBoss Seam"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:687
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1553\">JBPAPP-1553</"
+"ulink>: When the <methodname>parseRequest()</methodname> method of the "
+"<classname>org.jboss.seam.web.MultipartRequest</classname> class uploaded a "
+"large file, there were occurrences when this would cause an endless loop and "
+"use 100% of the computers CPU. In order to break out of the loop, a "
+"<varname>loopCounter</varname> has been implemented within the "
+"<filename>MultipartRequest.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:692
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1494\">JBPAPP-1494</"
+"ulink>: The portal example that was previously included with the Seam "
+"Enterprise Application Platform distribution has been removed in order to "
+"avoid confusion that Seam 1.2.1 included with the EAP supports portal."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:697
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1044\">JBPAPP-1044</"
+"ulink>: After basic interaction with the Seam examples <filename>chatroom</"
+"filename>, <filename>mail</filename>, <filename>registration</filename>, "
+"<filename>booking</filename> and <filename>dvdstore</filename> would "
+"generate a <exceptionname>NullPointerException</exceptionname> during "
+"undeployment. In correcting this issue, the <filename>RootInterceptor.java</"
+"filename> file was updated to check if an applications context still active "
+"upon undeployment and deal with this appropriately."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:705
+#, no-c-format
+msgid "JBoss Hibernate"
+msgstr "JBoss Hibernate"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:709
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1580\">JBPAPP-1580</"
+"ulink>: The JBoss Hibernate Core component of the Enterprise Application "
+"Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:714
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1628\">JBPAPP-1628</"
+"ulink>: In an earlier fix to Hibernate the <methodname>org.hibernate.jdbc."
+"AbstractBatcher#closeQueryStatement()</methodname> method was changed to "
+"check for the existence of the prepared statement in the "
+"<classname>statementsToClose</classname> collection instead of closing it "
+"unconditionally. This has now caused a properties leak as the "
+"<methodname>org.hibernate.persister.entity."
+"AbstractEntityPersister#processGeneratedProperties()</methodname> used "
+"<methodname>org.hibernate.jdbc.AbstractBatcher#closeQueryStatement()</"
+"methodname> and the statement within <methodname>org.hibernate.persister."
+"entity.AbstractEntityPersister#processGeneratedProperties()</methodname> is "
+"not added to the <classname>statementsToClose</classname> collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:717
+#, no-c-format
+msgid ""
+"<filename>AbstractEntityPersister.java</filename> has been updated to "
+"execute a prepared statement on the result set and after calculating the "
+"<varname>propValue</varname> the result set is closed if it is not null; "
+"ensuring that no leak can occur."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:722
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1582\">JBPAPP-1582</"
+"ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</"
+"classname> is included with this CP release to support Sybase ASE 15 and "
+"this dialect now becomes apart of the Enterprise Application Platform "
+"certified configuration. Previous Sybase dialects are now considered "
+"deprecated and may be removed from future releases; however support will "
+"still be maintained for users who do not wish to move to the new dialect."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:742
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1524\">JBPAPP-1524</"
+"ulink>: The Sybase functions <methodname>second()</methodname>, "
+"<methodname>minute()</methodname>, <methodname>hour()</methodname> and "
+"<methodname>extract()</methodname> caused a "
+"<exceptionname>GenericJDBCException</exceptionname> when used. Moving these "
+"functions from the <filename>SQLServerDialect.java</filename> file to the "
+"<filename>SybaseDialect.java</filename> file allows for these functions to "
+"work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:757
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1519\">JBPAPP-1519</"
+"ulink>: Sybase does not support the operation <emphasis>on cascade delete</"
+"emphasis> while SQL Server does. To make sure that both operate correctly "
+"the <filename>SQLServerDialect.java</filename> file has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns true and <filename>SybaseDialect.java</filename> has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns false."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:762
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1496\">JBPAPP-1496</"
+"ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</"
+"emphasis> when using the <emphasis>Identity</emphasis> generator option. To "
+"close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make "
+"sure it is closed before returning the generated identity value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:767
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1480\">JBPAPP-1480</"
+"ulink>: Hibernate would attempt to read from an invalid column in the "
+"collection result set when the following conditions were present:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
+"ulink>: La configuration SQL par défaut contient des erreurs, ce qui pose un "
+"problème dans hsqldb qui utilise cette configuration. Ce problème a été "
+"résolu avec la configuration par défaut."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:772
+#, no-c-format
+msgid "Instances of a subclass were contained in a collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:777
+#, no-c-format
+msgid ""
+"The subclasses were single-table and used a &lt;join&gt; (table-per-subclass "
+"with discriminator)."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:782
+#, no-c-format
+msgid ""
+"The &lt;join&gt; portion of the subclass contained at least 3 of its own "
+"columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:787
+#, no-c-format
+msgid ""
+"The &lt;join&gt; tables were fetched by select and not the default method "
+"for this task."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:792
+#, no-c-format
+msgid ""
+"To fix this issue the <filename>AbstractEntityPersister.java</filename> file "
+"was updated so that the <varname>columnNumber</varname> variable is passed "
+"to the <methodname>subclassColumnSelectableClosure</methodname> method "
+"instead of an increment of the for loop variable <varname>i</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:795
+#, no-c-format
+msgid ""
+"<filename>CollectionTest.java</filename> has also been updated and "
+"<filename>Animal.java</filename>, <filename>Mammal.java</filename>, "
+"<filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been "
+"added for testing purposes."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:800
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1467\">JBPAPP-1467</"
+"ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur "
+"when merging a detached instance of a <classname>One</classname> class that "
+"contains a new <classname>Many</classname> class instance and if and only if "
+"the <classname>One</classname> class was previously loaded as a proxy during "
+"the same transaction. The files <filename>StatefulPersistenceContext.java</"
+"filename>, <filename>BackrefPropertyAccessor.java</filename>, "
+"<filename>BackrefTest.java</filename> and <filename>Child.java</filename> "
+"have been updated to check for the proxy issue in the merging and once the "
+"proxy entity is found the <methodname>mergeMap</methodname> is updated to "
+"deal with this eventuality."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:805
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1365\">JBPAPP-1365</"
+"ulink>: A bug existed within Hibernate Core where the "
+"<methodname>addDuplicateAlias</methodname> method would include an entry "
+"into the hash map even when the <varname>classAlias</varname> variable was "
+"set to null; causing a <exceptionname>NullPointerException</exceptionname> "
+"when the <methodname>CrazyJPARRequirements()</methodname> method is called. "
+"To correct this issue the <filename>FromClause.java</filename> file has been "
+"modified to correct the <methodname>addDuplicateAlias</methodname> method by "
+"testing if the <varname>alias</varname> variable is null and if it is not "
+"null then the <methodname>fromElementByClassAlias.put</methodname> is now "
+"called, instead of this method being called even if <varname>alias</varname> "
+"contained a null value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:810
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1259\">JBPAPP-1259</"
+"ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL "
+"and the version field is specified by the user to not be updated, the "
+"<methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method "
+"would still update the field causing exceptions to appear in certain cases. "
+"Within this Enterprise Application Platform update "
+"<filename>AbstractEntityPersister.java</filename> has been corrected to "
+"check if the user has explicitly said that the version field should not be "
+"updated and does not update the field if this is the case."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:815
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1251\">JBPAPP-1251</"
+"ulink>: Filters that were enabled for Hibernate did not apply to update and "
+"delete Hibernate Query Language (HQL) statements. In correcting this bug "
+"numerous files have been updated to ensure that the filters work correctly. "
+"This fix is related to JBPAPP-1250 below."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:820
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1250\">JBPAPP-1250</"
+"ulink>: When creating queries with subqueries in Hibernate, any added "
+"filters would only apply to the top-level of the query and not to any "
+"subquery component or beneath. The Criteria code and HQL code associated "
+"with this has undergone significant re-tooling to allow filters to work "
+"appropriately with subqueries and extent as far as the Hibernate Query "
+"Language does."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:823
+#, no-c-format
+msgid ""
+"Though this is a significant fix to Hibernate, it has been included within "
+"this CP release because of its undeniable advantage to all users and ensures "
+"that filters on queries operate how a user would expect them to."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:833
+#, no-c-format
+msgid "JBoss Transaction Service (JBossTS)"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:837
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1510\">JBPAPP-1510</"
+"ulink>: The JBoss Transaction Service component of the Enterprise "
+"Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of "
+"the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:842
+#, no-c-format
+msgid ""
+"The <classname>AppServerJDBCXARecovery</classname> class was using the Java "
+"1.5 syntax when it should compile with Java 1.4. This error has been "
+"rectified with this release by modifying the "
+"<filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:847
+#, no-c-format
+msgid ""
+"When the Application Server started, the transaction manager may have "
+"deployed before the datasources, starting a recovery pass and causing "
+"exceptions. This issue has been rectified by modifying the "
+"<classname>AppServerJDBCXARecovery</classname> class and adding the "
+"<methodname>createConnection() throws SQLException</methodname> method which "
+"makes sure a connection exists before deploying the transaction manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:852
+#, no-c-format
+msgid ""
+"There were occurrences when the <classname>AppServerJDBCXARecovery</"
+"classname> class would contain information to an invalid connection because "
+"of database failure. This bug was fixed with the same correction as the "
+"above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</"
+"classname> class and adding the <methodname>createConnection() throws "
+"SQLException</methodname> method which makes sure a connection exists."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:857
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method would be run even when "
+"the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, "
+"when this method should only be executed before commit attempts and not "
+"rollbacks. In order to correct this and make sure the "
+"<methodname>beforeCompletion</methodname> method does not get executed for "
+"rollback events the <filename>SubordinateAtomicAction.java</filename> file "
+"has been modified."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:862
+#, no-c-format
+msgid ""
+"<methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a "
+"<exceptionname>HeuristicRollbackException</exceptionname> when the commit "
+"was aborted. This meant that <methodname>XATerminatorImple.commit</"
+"methodname> was unable to distinguish between a successful rollback and one "
+"in error. Fixed in this CP release, the <filename>TransactionImple.java</"
+"filename> file has been modified so that the <methodname>TransactionImple."
+"doOnePhaseCommit</methodname> method now generates a "
+"<exceptionname>RollbackException</exceptionname> instead of a heuristic when "
+"a successful rollback is performed."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:867
+#, no-c-format
+msgid ""
+"When the <literal>tx</literal> had been set to <varname>rollbackOnly</"
+"varname> and the <methodname>XATerminatorImple.prepare</methodname> method "
+"was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would "
+"be generated and yet the rollback would not be undertaken and the "
+"<literal>tx</literal> reference would be removed meaning no cleanup via the "
+"<methodname>commit</methodname> or <methodname>rollback</methodname> methods "
+"were possible. The <filename>XATerminatorImple.java</filename> file has been "
+"updated to correct this by improving the cleanup and exception reporting for "
+"rollbacks in <methodname>XATerminatorImple.prepare</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:872
+#, no-c-format
+msgid ""
+"The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called "
+"<methodname>beforeCompletion</methodname> but did not call "
+"<methodname>afterCompletion</methodname> when the return status was "
+"<literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</"
+"filename> now has corrected synchronization handling for transaction "
+"termination."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:877
+#, no-c-format
+msgid ""
+"The JCA coordinator did not call synchronizations during the phase commit "
+"cycle (1PC). Synchronization has been added to the JCA coordinator through "
+"the modification of the <filename>SubordinateAtomicAction.java</filename> "
+"file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:882
+#, no-c-format
+msgid ""
+"Coordinator methods would not perform a cleanup correctly. In order to "
+"rectify this cleanup routines have been added to the "
+"<methodname>phase2Commit</methodname> and <methodname>phase2Abort</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:892
+#, no-c-format
+msgid "Security Issues"
+msgstr "Problèmes de sécurité"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:896
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>: An exploit existed within the JBoss Web Services component of the "
+"Enterprise Application Platform that would allow anyone to view any xml file "
+"from any location if <literal>&amp;resource=path/of/an/xmlfile.xml</literal> "
+"was applied to the end of any WSDL (Web Services Definition Language) access "
+"URL. The <filename>WSDLRequestHandler.java</filename> file has been updated "
+"to only allow the parent of a WSDL file, a servers data or WSDL or "
+"overridden WSDL publish directories access to xml file resources. Additional "
+"test files are also included which were created to ensure proper operation "
+"was being undertaken. (CVE-2009-0027 )"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:908
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1649\">JBPAPP-1649</"
+"ulink>: The documentation on the isolation of JGroup channels within the "
+"Server Configuration Guide was missing two parameters specific to the "
+"Enterprise Application Platform 4.3 distribution. The parameters of "
+"<varname>-Djboss.messaging.controlchanneludpport</varname> and <varname>-"
+"Djboss.messaging.datachanneludpport</varname> have been includedin section "
+"19.7.10 with example ports and the text addressing the concern of "
+"<emphasis>Why do I need to change the multicast port if I change the address?"
+"</emphasis> has been updated to reflect what is happening in an improved way."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:914
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1498\">JBPAPP-1498</"
+"ulink>: File set information within the Getting Started Guide (sections "
+"2.2.2 and 2.2.3) was outdated and required new information added and old "
+"information removed from the <literal>default</literal> server configuration "
+"file set and the contents of the <literal>conf</literal>, <literal>deploy</"
+"literal> and <literal>all</literal> directory sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:919
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1472\">JBPAPP-1472</"
+"ulink>: The instructions for adding SSL to EJB 2.1 in the Server "
+"Configuration Guide were incorrect as they did not include code pertaining "
+"to marshalling. The appropriate code has now been added to the instructions "
+"in section 9.8.2.3."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:924
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1362\">JBPAPP-1362</"
+"ulink>: The Getting Started Guide section 2.3 has been updated to include "
+"information about the <code>-b</code> option (and equivalents) that can be "
+"used on the command line to change the binding addresses of the Enterprise "
+"Application Platform for remote connectivity."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:929
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1346\">JBPAPP-1346</"
+"ulink>: Confusion existed when starting and stopping a <code>ZIP</code> "
+"installation of the server locally or remotely because a different username "
+"and password may be used. The Getting Started Guide has now been updated to "
+"explain that user credentials for the operating system will be used for "
+"local authentication and JBoss server credentials for remote authentication."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:937
+#, no-c-format
+msgid "Core Server"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:941
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1670\">JBPAPP-1670</"
+"ulink>: The JacORB component of the Enterprise Application Platform has been "
+"upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:946
+#, no-c-format
+msgid ""
+"A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to "
+"become unresponsive during shutdown. In rectifying this issue, the "
+"<filename>POA.java</filename> file has been modified so that instead of "
+"executing:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:949
+#, no-c-format
+msgid "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:950
+#, no-c-format
+msgid "the following is now executed:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:953
+#, no-c-format
+msgid "throw new ObjectNotActive();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:958
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1636\">JBPAPP-1636</"
+"ulink>: Affecting only third party adapters was an issue when one of these "
+"adapters handled the scheduling of work to be performed. The "
+"<classname>ExecutionContext</classname> class contained a value in seconds, "
+"from which the <methodname>getCompletionTimeout</methodname> method of "
+"<classname>org.jboss.resource.work.WorkWrapper</classname> obtains its "
+"information. An issue arises with <methodname>getCompletionTimeout</"
+"methodname> expecting the value to be in milliseconds, creating an error "
+"where the initially set timeout value may be 6 seconds but be passed to the "
+"thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> "
+"file has been updated and correctly converts the timeout value from seconds "
+"to milliseconds."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:963
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1635\">JBPAPP-1635</"
+"ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced "
+"for this release with new error codes of 17002 (connection reset) and 17008 "
+"(connection closed) now able to be handled. These enhancements have been "
+"applied to the <filename>OracleExceptionSorter.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:968
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1602\">JBPAPP-1602</"
+"ulink>: A <exceptionname>ConcurrentModificationException </exceptionname> "
+"would occur when a classloader would be undeployed while another user was "
+"attempting to load a class from the package. This error arose because the "
+"<classname>packagesMap</classname> within "
+"<classname>UnifiedLoaderRepository3</classname> had a <classname>TreeSet</"
+"classname> that was not correctly synchronized with changes. In order to "
+"rectify this, the <filename>ClassLoaderUtils.java</filename> file has been "
+"updated to import the <classname>Collections</classname> library and use the "
+"<methodname>synchronizedSet</methodname> method of the library in returning "
+"the <methodname>TreeSet</methodname> of the <methodname>newPackageSet</"
+"methodname> method."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:973
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1540\">JBPAPP-1540</"
+"ulink>: Within the cluster section of the Enterprise Application Platform, "
+"the <classname>GossipRouter</classname> and <classname>GossipClient</"
+"classname> (TCPGOSSIP) did not have socket read timeouts, socket linger "
+"timeouts and backlog set to provide the best behavior when heavily utilized "
+"or under network situations in need of improvement. This fix provides "
+"default values and configuration options for these in order to avoid "
+"problematic situations."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:978
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1539\">JBPAPP-1539</"
+"ulink>: When running parallel instances of the Enterprise Application "
+"Platform on Linux a bug existed where messages between the JGroups component "
+"of each instance would be picked up by both because all messages sent to the "
+"port number for Multicast Sockets would be picked up by both instances. The "
+"issue has been fixed by re-writing the code for Multicast Sockets so that "
+"the constructor uses a group address along with the port number as "
+"identifiers. This ensures that an instance of the EAP only receives messages "
+"pertaining to its specific group and thus inhibits channel crosstalk."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:983
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1538\">JBPAPP-1538</"
+"ulink>:The Probe Client had not been updated to use the same address as the "
+"Probe Listener does which is now 224.0.75.75. Correcting this issue, the "
+"Proble Client now uses 224.0.75.75 instead of 224.0.0.75 which allows the "
+"client and the listener to work together correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:988
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1535\">JBPAPP-1535</"
+"ulink>: The JDBCExtCacheLoader didn't handle persistent state transfer "
+"correctly since the <methodname>storeState</methodname> method would use "
+"available space on the <classname>MarshalledValueInputStream</classname> "
+"instead of on the <classname>ByteArrayInputStream</classname>. To correct "
+"the stream usage, <filename>JDBCExtendedCacheLoader.java</filename> has been "
+"updated to store the new state using the <varname>in_stream</varname> value "
+"as long as there is space available."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:993
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1534\">JBPAPP-1534</"
+"ulink>: The JDBCCacheLoader didn't work with Sybase as it tried to set a "
+"null <varname>BLOB</varname> (Binary Large OBject) column which is "
+"unsupported in Sybase. To correct this the <filename>JDBCCacheLoader.java</"
+"filename> and <filename>AdjListJDBCCacheLoader.java</filename> files have "
+"been updated to select the Sybase Driver if Sybase is to be used, ensuring "
+"that null values are set as <varname>LONGVARBINARY</varname> rather than "
+"<varname>BLOB</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:998
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1532\">JBPAPP-1532</"
+"ulink>: The JGroups clustering component of the Enterprise Application "
+"Platform has been upgraded to version 2.4.5. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1003
+#, no-c-format
+msgid ""
+"The probe listener within JGroups still used the old default address of "
+"224.0.0.75 instead of the new address of 224.0.75.75. The probe listener "
+"within JGroups has been updated with this release to use the correct default "
+"address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1008
+#, no-c-format
+msgid ""
+"The MPING protocol which sends a multicast ping over TCP contained cross-"
+"talk in Linux. the MPING protocol has since been corrected to eliminate "
+"cross-talk on the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1013
+#, no-c-format
+msgid ""
+"A problem was encountered within JGroups when two distinct processes were "
+"setup on the same machine, each using a different stack with different UDP "
+"multicast addresses. The issue was that each process would not work "
+"correctly because of the other, as each process would receive incorrect "
+"datagrams in reference to the groups each joined. To correct this the "
+"<classname>MulticastSocket</classname> constructor is now used in "
+"combination with a <varname>SocketAddress</varname> when JGroups is used on "
+"the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1018
+#, no-c-format
+msgid ""
+"The <literal>Gossip Router</literal> component of JGroups provided options "
+"to set <literal>backlog</literal>, <literal>socket read timeout</literal> "
+"and <literal>socket linger timeout</literal> within the code, however these "
+"options are not available via the command line. This update of the JGroups "
+"component, now includes the availability of these options to be set through "
+"the command line."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1023
+#, no-c-format
+msgid ""
+"Within the <literal>Gossip Router</literal> component of JGroups "
+"<methodname>Math.min</methodname> was used in calculating the socket linger "
+"timeout which caused incorrect results since this meant that the socket "
+"linger timeout would always be 1. <literal>Gossip Router</literal> has been "
+"updated to instead use <methodname>Math.max</methodname> in the calculation "
+"of the socket linger timeout."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1028
+#, no-c-format
+msgid ""
+"The <classname>RouterStub</classname> and <classname>GossipRouter</"
+"classname> classes have the <varname>setSoLinger</varname> value set "
+"incorrectly to use a seconds value when <varname>setSoLinger</varname> uses "
+"millisecond values. This meant that a value of 500 was 500 seconds rather "
+"than 500 milliseconds. The <classname>RouterStub</classname> class has had "
+"its <varname>setSoLinger</varname> corrected and the "
+"<classname>GossipRouter</classname> class has had the <varname>setSoLinger</"
+"varname> value corrected and timouts configurable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1035
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1530\">JBPAPP-1530</"
+"ulink>: The JCA adapter inflow did not roll back messages if a non-xa "
+"connection factory was being used within the JNDIProviderAdapter. In order "
+"to fix this issue the <filename>JmsServerSession.java</filename> file has "
+"been updated with added logic to the local transaction separation strategy "
+"as to allow for non-xa sessions to be rolled back using transaction session."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1040
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1521\">JBPAPP-1521</"
+"ulink>: The <classname>CleanShutdownInterceptor</classname> class would log "
+"a <exceptionname>GenericClusteringException</exceptionname> when the "
+"container had failed to shut down correctly or failed to start correctly and "
+"because of this behavior the error message displayed because of the "
+"exception should be updated to indicate that it may be an issue with the "
+"container failing to start instead of only failing to shut down. In this "
+"latest Enterprise Application Platform update, the error message has been "
+"updated to reflect both situations which may be the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1045
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1458\">JBPAPP-1458</"
+"ulink>: The JTA recovery configuration did not contain a line to enable "
+"JBoss Messaging (JBM) <classname>XAResourceRecovery</classname> even though "
+"it is stated in the JBM user guide. This CP release modifies the "
+"<filename>build-distr.xml</filename> file to all "
+"<classname>XAResourceRecovery</classname> to be enabled for JTA recovery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1050
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1479\">JBPAPP-1479</"
+"ulink>: Within the different distributions of the Enterprise Application "
+"Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and "
+"<filename>JBoss Messaging</filename> application policies have been present "
+"within the <filename>login-config.xml</filename> file, when "
+"<filename>JBossMQ</filename> is only included in the 4.2 distribution and "
+"<filename>JBoss Messaging</filename> is similarly only included in the 4.3 "
+"distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1053
+#, no-c-format
+msgid ""
+"This has been rectified in this release by modifying <filename>build.xml</"
+"filename> and <filename>login-config.xml</filename> to differentiate between "
+"requirements for each individual distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1058
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1473\">JBPAPP-1473</"
+"ulink>: The "
+"<classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</"
+"classname> within clustering didn't correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>, which would "
+"lead to the repeated calling of itself and eventually "
+"<exceptionname>StackOverflow</exceptionname> errors. In order to correct "
+"this the <filename>IgnoreUndeployLegacyClusteredSessionNotificationPolicy."
+"java</filename> file has been modified to correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1063
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1460\">JBPAPP-1460</"
+"ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for "
+"this Enterprise Application Platform release. This update corrects numerous "
+"bugs and details on these fixes can be found at <ulink url=\"https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html\">https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1068
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1366\">JBPAPP-1366</"
+"ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the "
+"<option>Oracle</option> schema is specified. To correct this the "
+"<filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has "
+"been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</"
+"methodname> function which changes all dots in a constraint name to "
+"underscores. This ensures that constraint names are compatible with Oracle."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1073
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1307\">JBPAPP-1307</"
+"ulink>: The Persistence Unit (PU) root was incorrectly detected within "
+"deployments that contained nested <filename>.jar</filename> files. The root "
+"PU was being detected as the first nested <filename>.jar</filename> "
+"encountered instead of being the deployment which contains the "
+"<filename>persistence.xml</filename> file. To make sure that the PU root is "
+"always set correctly, the <filename>JmxDeploymentUnit.java</filename> file "
+"has been updated with the removal of testing for the url being null and the "
+"<parameter>deploymentInfo.parent</parameter> not being null. This means that "
+"the url is now always taken straight from the "
+"<parameter>extractDescriptorUrl</parameter> of <filename>META-INF/"
+"persistence.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1078
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1289\">JBPAPP-1289</"
+"ulink>: The JBoss JAXR component of the Enterprise Application Platform has "
+"been upgraded to version 1.2.0.SP2. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1083
+#, no-c-format
+msgid ""
+"In the <filename>org.jboss.jaxr.juddi.JUDDIServlet</filename> and "
+"<filename>org.jboss.jaxr.juddi.transport.SaajTransport</filename> files the "
+"namespace value for <varname>xml:lang</varname> contained <literal>http://"
+"www.w3.org/TR/REC-xml/</literal>, which caused an exception within the metro "
+"stack. The namespace value should instead be null and this has been applied "
+"for this JAXR update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1090
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1275\">JBPAPP-1275</"
+"ulink>: The Xalan part of the Enterprise Application Platform has been "
+"upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the "
+"circumstance where an application which heavily used Xalan within large "
+"multi-threaded environments would encounter blocking situations."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
+"ulink>: Le composant JBoss Web Services a été mis à niveau à la version "
+"2.0.1.SP2_CP02. Cette mise à niveau comprend de nombreuses résolutions de "
+"bogues et des améliorations."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1095
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1267\">JBPAPP-1267</"
+"ulink>: <classname>UserTransaction</classname> (UT) was not able to be "
+"deployed with a clustered proxy that supported sticky transactions "
+"correctly. This has been fixed by modifying numerous files which make "
+"<classname>UserTransaction</classname> deployable with transaction sticky "
+"load balance policies."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1100
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1249\">JBPAPP-1249</"
+"ulink>: The JSF component of the Enterprise Application Platform has been "
+"upgraded to version 1.2_10. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1105
+#, no-c-format
+msgid ""
+"A mixed EL expression ending with a literal failed to parse as a managed "
+"bean property value. The <filename>BeanBuilder.java</filename> file was "
+"updated with the removal of <code>ELUtils.getScope(this.expressionString, "
+"segment);</code> in order to fix this issue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1110
+#, no-c-format
+msgid ""
+"<methodname>LifecycleImpl</methodname> and <methodname>RestoreViewPhase</"
+"methodname> forced the <methodname>responseComplete()</methodname> method "
+"for the status of an existing view. To correct this problem the "
+"<filename>RestoreViewPhase.java</filename> file has been edited with the "
+"code <code>facesContext.responseComplete();</code> removed and replaced with "
+"<code>facesContext.renderResponse();</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1115
+#, no-c-format
+msgid ""
+"For a &lt;h:dataTable&gt; tag which does not set the <varname>var</varname> "
+"attribute, if the UIData component is created using a binding and calls the "
+"<methodname>setVar()</methodname> method to set the <varname>var</varname> "
+"attribute, it would be overwritten as a null value by the &lt;h:"
+"dataTable&gt; tag. This bug has been fixed by modifying the "
+"<filename>HtmlTaglib21Generator.java</filename> file so that component "
+"properties are not set if the tag attribute has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1120
+#, no-c-format
+msgid ""
+"The <classname>BindingValidator</classname> would generate a "
+"<exceptionname>ConverterException</exceptionname> instead of a "
+"<exceptionname>ValidatorException</exceptionname>. For this update, "
+"<classname>BindingValidator</classname> has been modified to generate the "
+"correct exception; <exceptionname>ValidatorException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1125
+#, no-c-format
+msgid ""
+"The cause of a <classname>PostConstruct</classname> exception within the "
+"<classname>BeanBuilder</classname> was not communicated to the user "
+"correctly. To correct the issue so that no information is hidden from the "
+"user, the <exceptionname>ManagedBeanCreationException</exceptionname> has "
+"been updated to provide more information about the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1130
+#, no-c-format
+msgid ""
+"An issue was present that would cause majarra to execute <filename>faces-"
+"config.xml </filename> initialization files twice, creating duplicate "
+"operations. This was caused since a record was not kept of which files had "
+"been initialized and which had not. File initialization tracking has been "
+"implemented to correct this issue and this has seen the modification of the "
+"following files: <filename>ConfigManager.java</filename>, "
+"<filename>ConfigureListener.java</filename>, <filename>WebConfiguration."
+"java</filename>, <filename>ConfigurationResourceProvider.java</filename>, "
+"<filename>MetaInfResourceProvider.java</filename>, "
+"<filename>RIConfigResourceProvider.java</filename> and "
+"<filename>WebResourceProvider.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1135
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.ApplicationObjectInputStream</"
+"classname> extends the functionality of <classname>java.io."
+"ObjectInputStream</classname> but failed to preserve the functionality as "
+"<classname>com.sun.faces.renderkit.ApplicationObjectInputStream</classname> "
+"would fail when primitives were used, unlike the <classname>java.io."
+"ObjectInputStream</classname> class which contains a special case to handle "
+"such a case. This would cause problems for <literal>UIComponents</literal>. "
+"<filename>ApplicationObjectInputStream.java</filename> has been updated to "
+"explicitly handle primitive cases and catch the "
+"<exceptionname>ClassNotFoundException</exceptionname> which may be generated."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1140
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.renderkit.html_basic.OutputLinkRenderer</classname> "
+"did not encode parameters correctly, missing the <literal>URLEncoding</"
+"literal>. <literal>URLEncoding</literal> has been added, correcting this "
+"bug, along with the parameter names."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1145
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.BaseTableRenderer</"
+"classname> did not allow for empty <varname>columnClasses</varname> when "
+"generating columns from user input. The issue was realizing when to create "
+"numerous columns rather just one; for instance if the user input "
+"<literal>foo, </literal> with a trailing space then the expected output "
+"would be one column with the name <literal>foo</literal> and another empty "
+"column. This was not the case though, as <literal>foo, </literal> would "
+"generate just one column with <literal>foo, </literal> in its entirety as "
+"the column name, instead of splitting the columns on the comma. This "
+"behavior has now been corrected so that <classname>com.sun.faces.renderkit."
+"html_basic.BaseTableRenderer</classname> no generates columns correctly, and "
+"in order to achieve this the following files have been updated: "
+"<filename>BasetableRenderer.java</filename>, <filename>GridRenderer.java</"
+"filename> and <filename>TableRenderer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1150
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.MenuRenderer</classname> "
+"class did not correctly differentiate between <literal>Objects</literal>; "
+"for instance the different between <literal>Boolean</literal> and "
+"<literal>boolean</literal>, noting the capitalization of the first. The "
+"error was with the logic in <classname>UISelect</classname> and "
+"<classname>MenuRenderer</classname>. To correct this, proper use of the "
+"converter for these classes has been implemented to deal with Objects "
+"correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1155
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.lifecycle.RestoreViewPhase</classname> called "
+"<methodname>DebugUtil.printTree</methodname> after restoring the view if "
+"debugging was enabled, causing incorrect initialization of calls when a "
+"listbox is being used and returning an incorrect value in the "
+"<classname>RenderResponse</classname> phase. Method calls have been "
+"restructured with the removal of references to the <methodname>DebugUtil."
+"printTree()</methodname> method from <filename>ViewHandlerImpl.java</"
+"filename> and <filename>RestoreViewPhase.java</filename> and "
+"<filename>RenderResponsePhase.java</filename> has been modified to call "
+"<methodname>DebugUtil.printTree</methodname> (if <varname>FINEST</varname> "
+"logging is enabled) at the end of the <classname>RenderResponse</classname> "
+"phase, fixing the issue (with the above changes also) and providing a more "
+"accurate view of the tree."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1159
+#, no-c-format
+msgid ""
+"<literal>CGLIB Enhanced UIComponents</literal> in a component tree would "
+"return a value of null for their class when calling <methodname>getPackage()"
+"</methodname> causing <classname>HtmlInputText.handleAttribute</classname> "
+"to fail as it relies on a not-nulll value. This issue has been corrected by "
+"ignoring a returned value of null from the <methodname>getPackage()</"
+"methodname> method for every instance in the codebase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1164
+#, no-c-format
+msgid ""
+"The <classname>UIComponentBase</classname> did not allow for the children of "
+"a tree to be iterated through in reverse order using a list iterator as it "
+"would produce an <exceptionname>IndexOutOfBoundsException</exceptionname> "
+"when the execution tries to calculate the size of the children. "
+"<methodname>ChildrenListIterator</methodname> method has been modified "
+"within the <classname>UIComponentBase</classname> class by changing the line "
+"of code <code>if ((index &lt; 0) || (index &gt;= list.size())) { </code> to "
+"<code>if ((index &lt; 0) || (index &gt; list.size())) {</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1169
+#, no-c-format
+msgid ""
+"Renderer kits for <filename>faces-config.xml</filename> were processed out "
+"of order depending on if <literal>ICEfaces</literal> or <literal>Mojara "
+"1.2_09</literal> is in use. This occurred due to containing all renderer DOM "
+"nods in a list associated with a namespace. This was done so that the "
+"renderer nodes could then be processed prior to the <literal>RenderKits</"
+"literal> being created and the nodes could be processed using the proper "
+"namespace. However, by placing all the renderers into this list, we lost the "
+"document ordering. The issue has been fixed by associating the renderer "
+"nodes with their owning document and processed in the parsing order."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1175
+#, no-c-format
+msgid ""
+"The <methodname>Class.getPackage()</methodname> method calls to synchronized "
+"methods, inhibiting scalability if the method has to be repeatedly executed. "
+"Use of the <methodname>Class.getPackage()</methodname> method has now been "
+"removed from <filename>UIComponent.java</filename>, <filename>RenderKitUtils."
+"java</filename> and <filename>HtmlComponentGenerator.java</filename>. "
+"Instead, the class name is now checked if it starts with the package name "
+"that is of interest, <classname>javax.faces.component.</classname>. This "
+"includes the components that are generated by the "
+"<classname>HtmlComponentGenerator</classname> since they are packaged in "
+"<classname>javax.faces.component.html</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1180
+#, no-c-format
+msgid ""
+"A bug presented itself in the <classname>RenderKitUtils</classname> class "
+"when a semicolon (<code>;</code>) followed a forward-slash (<code>/</code>) "
+"in a header Accept value (for instance: <code>text/;q=0.5</code>). To "
+"rectify this issue the <classname>RenderKitUtils</classname> class has been "
+"updated to assume <code>*</code> as the subtype for an Accept header that "
+"contains no subtype."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1187
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1224\">JBPAPP-1224</"
+"ulink>: Attribute default values in EJB were not set when in use with "
+"<literal>@Service</literal> and <literal>XMBean XML</literal> . In order to "
+"correct this the behavior has been re-written to improve the mimicking of "
+"<classname>ServerCreator</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1192
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1170\">JBPAPP-1170</"
+"ulink>: When the <methodname>getMBeanInfo</methodname> method is called "
+"within <classname>MBeanServerImpl</classname> and "
+"<classname>RawDynamicInvoker</classname>, the underlying exception to "
+"<exceptionname>NotCompliantMBeanException</exceptionname> is not expressed "
+"to the user. <filename>RawDynamicInvoker.java</filename> has now been "
+"updated to provide this useful information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1197
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1099\">JBPAPP-1099</"
+"ulink>: The <filename>commons-beanutils.jar</filename> file within the "
+"Enterprise Application Platform had the incorrect version in the "
+"<filename>manifest.mf</filename> file. Through the course of correcting this "
+"bug, it was found that the <literal>beanutils</literal> component was "
+"outdated and a newer version contained many advantages. In this update to "
+"the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, "
+"which sees the significant improvement that fixes a memory leak caused by a "
+"circular reference concerning the <classname>WeakHashMap</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1202
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1002\">JBPAPP-1002</"
+"ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be "
+"logged when transactions were not completed between invocations. However "
+"this was an error as BMT Stateful Session Beans are allowed to have this "
+"occurrence and so this logging measure has been removed in this Enterprise "
+"Application Platform update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1207
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
+"ulink>: Discrepancies existed between the port schemes within the "
+"<filename>sample-bindings.xml</filename> file. These include:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-961\">JBPAPP-961</"
+"ulink>: JBoss Web a été mis à niveau à la version 2.0.0.GA CP06."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1212
+#, no-c-format
+msgid ""
+"The remoting connectors were inserted in different places within the ports "
+"definition sections, making the comparison of the sections more difficult "
+"than was necessary."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1217
+#, no-c-format
+msgid ""
+"The <literal>ports-03</literal> section was missing the <literal>EJB "
+"remoting connector</literal> and the <literal>remoting connector</literal> "
+"sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1222
+#, no-c-format
+msgid ""
+"<literal>mq</literal> was used in the name property of the "
+"<varname>HAJNDIJMSProvider</varname> instead of <literal>jms</literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1227
+#, no-c-format
+msgid ""
+"The <literal>ports-01</literal>, <literal>ports-02</literal>, and "
+"<literal>ports-03</literal> schemes defined the <varname>timeout</varname> "
+"attribute twice in the <literal>JBoss Messaging</literal> section:"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1233
+#, no-c-format
+msgid "The above issues have been fixed appropriately in this update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1238
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-713\">JBPAPP-713</"
+"ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: "
+"PermGen</errorname> error. To correct this issue the Enterprise Application "
+"Platform now uses <filename>beanutils 1.8.0</filename> which fixes this "
+"<errorname>OutOfMemoryError</errorname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1243
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
+"ulink>: JMX source code was being exposed to the user when a "
+"<exceptionname>HTTP Status 500</exceptionname> exception would occur. To "
+"correct this, an error page <filename>genericError.jsp</filename> has been "
+"created and is now displayed whenever a <exceptionname>HTTP Status 500</"
+"exceptionname> exception occurs."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1252
+#, no-c-format
+msgid "Known Issues with this release"
+msgstr "Problèmes connus dans cette version"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1255
+#, no-c-format
+msgid "Following is a list of known issues at the time of release."
+msgstr ""
+"Vous trouverez ci-dessous une liste des problèmes connus au moment de la "
+"parution de cette version."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1259
+#, no-c-format
+msgid "General Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1263
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>: Footnotes within documentation tables and lists do not appear within "
+"PDFs. This issue resides within FOP and currently no workaround exists. "
+"Where possible footnotes are not used in the circumstances mentioned, "
+"however in documents such as the Release Notes the web address of a JIRA is "
+"automatically generated as a footnote and places a number beside that of the "
+"JIRA, referencing a footnote that does not appear."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1268
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-885\">JBPAPP-885</"
+"ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</"
+"methodname> or <methodname>RedeliveryDelay</methodname> is set to a value "
+"apart from zero, messages will not be redelivered even though the method "
+"<methodname>session.rollback()</methodname> had been called. This issue will "
+"not be fixed because redelivery delay is handled on the server side and the "
+"message is already acknowledged before delivery of the message with a non "
+"durable subscription. For the Enterprise Application Platform, this means "
+"that redelivery delays with non durable subscriptions cannot be supported."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1276
+#, no-c-format
+msgid "Hibernate Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1280
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1613\">JBPAPP-1613</"
+"ulink>: Null values for columns mapped as boolean in Hibernate, are "
+"persisted as zero instead of null. When the <methodname>PreparedStatement."
+"setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the "
+"Sybase environment, Sybase JDBC converts the null value to a zero because "
+"Sybase does not allow null bit columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1285
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
+"ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it "
+"should be set up to use image and text. Tests attaining to this currently "
+"fail with the message:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Permet à des instances multiples d'être installées dans une machine "
+"qui utilise une méthode de sous-package. Cette fonctionnalité a été rajoutée "
+"à cette version avec les fichiers -bin."
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1288
+#, no-c-format
+msgid ""
+"The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not "
+"supported and should not be called."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1291
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1554\">JBPAPP-1554</"
+"ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</"
+"methodname> method within Hibernate fails since Sybase currently only allows "
+"one column in a subquery select list, with the only exception to this being "
+"that a subquery in an <code>EXISTS()</code> predicate can have <code>*</"
+"code> as the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1294
+#, no-c-format
+msgid ""
+"The current workaround for this is to not use the HQL <methodname>elements()"
+"</methodname> method if the elements have a composite key. Instead the HQL "
+"should be reformatted to ensure there is no subquery with more than one item "
+"in the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1299
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1546\">JBPAPP-1546</"
+"ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be "
+"used to create stored procedures while in chained transaction mode. The "
+"suggested workaround for this case is to add the following code follwing the "
+"defining of the new stored procedure:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:1302
+#, no-c-format
+msgid ""
+"&lt;database-object&gt;\n"
+"        &lt;create&gt;\n"
+"                sp_procxmode paramHandling, 'chained'\n"
+"        &lt;/create&gt;\n"
+"        &lt;drop/&gt;\n"
+"&lt;/database-object&gt;"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1305
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
+"ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase "
+"environment and there are three or more joins where at least one of the "
+"joins involves a union."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Permet à des instances multiples d'être installées dans une machine "
+"qui utilise une méthode de sous-package. Cette fonctionnalité a été rajoutée "
+"à cette version avec les fichiers -bin."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1308
+#, no-c-format
+msgid ""
+"A workaround for this issue exists where it is reconmended that a user does "
+"not use <literal>join fetches</literal> involving <literal>union subclasses</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1313
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1230\">JBPAPP-1230</"
+"ulink>: In the Sybase environment when creating a subquery with an alias in "
+"use, the query will be incorrectly generated and cause an "
+"<exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. "
+"This bug impacts the following tests such that at present they are expected "
+"to fail: <classname>CriteriaQueryTest.testSubselect</classname>, "
+"<classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, "
+"<classname>DynamicFilterTest.testCriteriaControl</classname> and "
+"<classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1316
+#, no-c-format
+msgid ""
+"The known workaround is to use a HQL query instead of using a "
+"<methodname>DetachedCriteria</methodname> method in a subquery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1321
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1082\">JBPAPP-1082</"
+"ulink>: A limitation in the PostgreSQL JDBC driver causes a "
+"<exceptionname>javax.persistence.RollbackException</exceptionname>. This "
+"occurs when the <code>char</code> property is used without a value set as "
+"Hibernate then persists a string containing the character <code>\\u0000</"
+"code>, which causes PostgreSQL to generate an exception as it does not allow "
+"this character to be embedded in a string."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1324
+#, no-c-format
+msgid ""
+"Currently a workaround for persisting the <code>\\u0000</code> character in "
+"a <code>char</code> column using PostgreSQL does not exist. Instead it is "
+"reconmended that to persist a null value for the <code>char</code> property "
+"when it is uninitialized, the <methodname>java.lang.Character</methodname> "
+"method should be used."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1329
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1081\">JBPAPP-1081</"
+"ulink>: In the Entity Manager documentation it is stated that table aliases "
+"are supported in <code>update</code> clauses, however at present this is not "
+"the case. To fix this, the code has to be modified to remove the "
+"identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1334
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1068\">JBPAPP-1068</"
+"ulink>: When using Microsoft SQL and <code>@Type(type=\"text\")</code> in "
+"creating a table, the field is correctly created as <code>\"text\"</code> "
+"however when a delete operation is issued the field becomes set as a "
+"<varname>varchar</varname>, forcing the Microsoft SQL driver to return the "
+"error:"
+msgstr ""
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1337
+#, no-c-format
+msgid ""
+"The data types text and nvarchar are incompatible in the equal to operator."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1340
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1063\">JBPAPP-1063</"
+"ulink>: Currently MySQL does not support millisecond and microsecond "
+"measurements when returning database values such as <code>TIME</code> and "
+"<code>TIMESTAMP</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1345
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-953\">JBPAPP-953</"
+"ulink>: Hibernate Core and Annotations do not currently support the "
+"Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the "
+"Hypersonic database is planned for future releases."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1350
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-946\">JBPAPP-946</"
+"ulink>: Within the Hibernate Entity Manager three different "
+"<exceptionname>NullPointerExceptions</exceptionname> are being investigated "
+"in relation to the EJB3 configuration, transaction operations when they are "
+"extended and packaging."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1355
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-906\">JBPAPP-906</"
+"ulink>: A bug exists within the Hibernate Core whereby the unstable "
+"synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is "
+"utilized creating a deserialized String. This causes a problem where if "
+"multiple threads are loading database rows containing arrays of strings, one "
+"thread is forced to undertake all the procedure while the other threads are "
+"left dormant."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1358
+#, no-c-format
+msgid ""
+"The implemented workaround for this issue is to use <code>-Dsun.lang."
+"ClassLoader.allowArraySyntax=true</code>, which can be a default setting "
+"within the <filename>run.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1363
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Within the Hibernate component of the Enterprise Application "
+"Platform the HashMap and HashSet iteration order changed from past releases "
+"because of support for JDK 1.6. However this has meant that the order of "
+"columns in union clauses and union-subclasses has changed, generating a "
+"slight impact on the components performance."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Au sein du  composant Hibernate d'EAP, l'ordre d'itération de "
+"HashMap et de HashSet a changé par rapport aux versions antérieures à cause "
+"de la prise en charge de JDK 1.6. Ceci impliquait que l'ordre des colonnes "
+"des clauses-union et des sous-classes-union a changé, générant un léger "
+"impact au niveau de la performance des composants."

Added: projects/docs/enterprise/4.3.4/readme/fr-FR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/fr-FR/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/fr-FR/Revision_History.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,29 @@
+# translation of readme.po to French
+# Language fr-FR translations for readme package.
+#
+# Automatically generated, 2008.
+# Corina Roe <croe at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-05 14:14+1000\n"
+"Last-Translator: Corina Roe <croe at redhat.com>\n"
+"Language-Team: French <i18 at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/fr-FR/readme.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/fr-FR/readme.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/fr-FR/readme.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -31,7 +31,9 @@
 "resources, and other current issues are addressed here."
 msgstr ""
 "Ces notes de mise à jour contiennent des informations importantes sur  JBoss "
-"Enterprise Application Platform &VERSION;. On y traite de nouvelles fonctionnalités, de nouveaux problèmes, ressources, et autres sujets d'actualité."
+"Enterprise Application Platform &VERSION;. On y traite de nouvelles "
+"fonctionnalités, de nouveaux problèmes, ressources, et autres sujets "
+"d'actualité."
 
 #. Tag: title
 #: readme.xml:16
@@ -46,7 +48,11 @@
 "JBoss Enterprise Application Platform is the next evolutionary step in open "
 "source enterprise software. It is a powerful tool for developing rich, high "
 "performance, Web 2.0 applications on a pure Java Platform."
-msgstr "JBoss Enterprise Application Platform est la nouvelle étape de l'évolution en matière de logiciels d'entreprise en source ouverte. C'est un outil puissant pour développer les applications de haute performance Web 2.0, sur une Plateforme Java pure."
+msgstr ""
+"JBoss Enterprise Application Platform est la nouvelle étape de l'évolution "
+"en matière de logiciels d'entreprise en source ouverte. C'est un outil "
+"puissant pour développer les applications de haute performance Web 2.0, sur "
+"une Plateforme Java pure."
 
 #. Tag: para
 #: readme.xml:20
@@ -58,7 +64,13 @@
 "supported. So your new enterprise Java applications can take immediate "
 "advantage of the Java EE 5.0's significantly simpler POJO-based programming "
 "model."
-msgstr "JBoss Enterprise Application Platform est totalement compatible avec les applications J2EE 1.4 enterprise Java. En même temps, presque tous les composants et fonctions clé définis dans les spécifications Java EE 5.0 sont pris en charge. Donc, vos applications Java new enterprise peuvent peuvent bénéficier immédiatement du modèle de programmation basé-POJO Java EE 5.0, bien plus simple."
+msgstr ""
+"JBoss Enterprise Application Platform est totalement compatible avec les "
+"applications J2EE 1.4 enterprise Java. En même temps, presque tous les "
+"composants et fonctions clé définis dans les spécifications Java EE 5.0 sont "
+"pris en charge. Donc, vos applications Java new enterprise peuvent peuvent "
+"bénéficier immédiatement du modèle de programmation basé-POJO Java EE 5.0, "
+"bien plus simple."
 
 #. Tag: para
 #: readme.xml:23
@@ -70,8 +82,12 @@
 "Application Platform is fully tested and supported by Red Hat, and is "
 "certified to work on many leading enterprise hardware and software products."
 msgstr ""
-"De plus, en intégrant des infrastructures SO prestigieuses comme JBoss Seam, Hibernate, Tomcat, et JBoss Cache, la plate-forme tire avantage des innovations émanant de la communauté en source ouverte. De plus, JBoss Enterprise Application Platform est entièrement testée, supportée par Red Hat, et est certifiée pour opérer sur du matériel varié et sur des logiciels enterprise principaux. "
-" "
+"De plus, en intégrant des infrastructures SO prestigieuses comme JBoss Seam, "
+"Hibernate, Tomcat, et JBoss Cache, la plate-forme tire avantage des "
+"innovations émanant de la communauté en source ouverte. De plus, JBoss "
+"Enterprise Application Platform est entièrement testée, supportée par Red "
+"Hat, et est certifiée pour opérer sur du matériel varié et sur des logiciels "
+"enterprise principaux.  "
 
 #. Tag: para
 #: readme.xml:26
@@ -80,7 +96,10 @@
 "All of which means you can develop your new application taking advantage of "
 "Java EE 5.0 technologies immediately and with the confidence of knowing it "
 "will remain forward-compatible with future versions of the JBoss Platform."
-msgstr "Tout cela signifie que vous pouvez développer votre nouvelle application en bénéficiant immédiatement des technologies Java EE 5.0 dans la certitude qu'elle demeurera compatible avec les versions futures de JBoss Platform."
+msgstr ""
+"Tout cela signifie que vous pouvez développer votre nouvelle application en "
+"bénéficiant immédiatement des technologies Java EE 5.0 dans la certitude "
+"qu'elle demeurera compatible avec les versions futures de JBoss Platform."
 
 #. Tag: title
 #: readme.xml:32
@@ -101,7 +120,11 @@
 "In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
 "with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
 "messaging infrastructure for JBoss Enterprise Application Platform."
-msgstr "Dans JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 est remplacé par JBoss Messaging 1.4. JBoss Messaging propose une infrastructure de messagerie de haut niveau pour la plate-forme JBoss Enterprise Application Platform."
+msgstr ""
+"Dans JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 est remplacé "
+"par JBoss Messaging 1.4. JBoss Messaging propose une infrastructure de "
+"messagerie de haut niveau pour la plate-forme JBoss Enterprise Application "
+"Platform."
 
 #. Tag: title
 #: readme.xml:40
@@ -116,8 +139,9 @@
 "JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
 "Platform 4.3 and will now provide a complete implementation of JAX-WS."
 msgstr ""
-"JBoss Web Services sont mis à niveau à la version 2.0.1 dans JBoss Enterprise Application "
-"Platform 4.3 et vont maintenant procurer une implémentation complète de JAX-WS."
+"JBoss Web Services sont mis à niveau à la version 2.0.1 dans JBoss "
+"Enterprise Application Platform 4.3 et vont maintenant procurer une "
+"implémentation complète de JAX-WS."
 
 #. Tag: title
 #: readme.xml:48
@@ -132,7 +156,10 @@
 "This section contains information related to installing or upgrading to "
 "JBoss Enterprise Application Platform version &VERSION;, including hardware "
 "and platform requirements and prerequisites."
-msgstr "Cette section contient des informations relatives à l'installation et à la mise à niveau de JBoss Enterprise Application Platform version &VERSION;, y compris les prérequis et les exigences de la plate-forme et du matériel."
+msgstr ""
+"Cette section contient des informations relatives à l'installation et à la "
+"mise à niveau de JBoss Enterprise Application Platform version &VERSION;, y "
+"compris les prérequis et les exigences de la plate-forme et du matériel."
 
 #. Tag: title
 #: readme.xml:53
@@ -157,17 +184,28 @@
 "docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
 "instructions to install and verify JBoss Enterprise Application Platform."
 msgstr ""
-"Vous devez posséder suffisamment d'espace disque pour installer la plate-forme JDK et JBoss Enterprise Application Platform tout en provisionnant de l'espace pour vos applications. Vous devez posséder une installation opérante JDK 1.5. Pour les dernières informations sur les combinaisons JMW/Systèmes d'exploitation supportés, plate-formes Database et informations courantes sur le niveau de révision des composants inclus, veuillez vous référer au lien <ulink url=\"http://www.jboss.com/products/"
-"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
-"platforms/application/testedconfigurations</ulink>. Référez-vous au guide d'installation disponible en ligne sur le lien suivant <ulink url=\"http://www.redhat.com/"
-"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
-"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> pour des instructions détaillées pour installer et vérifier JBoss Enterprise Application Platform."
+"Vous devez posséder suffisamment d'espace disque pour installer la plate-"
+"forme JDK et JBoss Enterprise Application Platform tout en provisionnant de "
+"l'espace pour vos applications. Vous devez posséder une installation "
+"opérante JDK 1.5. Pour les dernières informations sur les combinaisons JMW/"
+"Systèmes d'exploitation supportés, plate-formes Database et informations "
+"courantes sur le niveau de révision des composants inclus, veuillez vous "
+"référer au lien <ulink url=\"http://www.jboss.com/products/platforms/"
+"application/testedconfigurations\">http://www.jboss.com/products/platforms/"
+"application/testedconfigurations</ulink>. Référez-vous au guide "
+"d'installation disponible en ligne sur le lien suivant <ulink url=\"http://"
+"www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://"
+"www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> "
+"pour des instructions détaillées pour installer et vérifier JBoss Enterprise "
+"Application Platform."
 
 #. Tag: title
 #: readme.xml:59
 #, no-c-format
 msgid "Upgrading from JBoss Enterprise Application Platform 4.3"
-msgstr "Mise à niveau à partir de la plate-forme JBoss Enterprise Application Platform 4.3"
+msgstr ""
+"Mise à niveau à partir de la plate-forme JBoss Enterprise Application "
+"Platform 4.3"
 
 #. Tag: title
 #: readme.xml:61
@@ -183,9 +221,10 @@
 "Installing+a+Patch\">https://network.jboss.com/confluence/display/DOC/"
 "Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
 msgstr ""
-"Voir <ulink url=\"https://network.jboss.com/confluence/display/DOC/"
-"Installing+a+Patch\">https://network.jboss.com/confluence/display/DOC/"
-"Installing+a+Patch</ulink> pour les instructions sur la manière d'installer un Patch Cumulatif."
+"Voir <ulink url=\"https://network.jboss.com/confluence/display/DOC/Installing"
+"+a+Patch\">https://network.jboss.com/confluence/display/DOC/Installing+a"
+"+Patch</ulink> pour les instructions sur la manière d'installer un Patch "
+"Cumulatif."
 
 #. Tag: title
 #: readme.xml:72
@@ -208,7 +247,13 @@
 "configuration may result in memory issues. Note that the default "
 "configuration for the server to start with, if no other configuration is "
 "specified, is the production configuration."
-msgstr "Il est recommandé d'exécuter les exemples Seam applications qui sont inclus dans la documentation, en utilisant la configuration de production. L'utilisation d'une autre configuration peut résulter par des problèmes au niveau de la mémoire. Notez que la configuration par défaut du serveur au départ est la configuration de production, si aucune autre configuration n'est spécifiée."
+msgstr ""
+"Il est recommandé d'exécuter les exemples Seam applications qui sont inclus "
+"dans la documentation, en utilisant la configuration de production. "
+"L'utilisation d'une autre configuration peut résulter par des problèmes au "
+"niveau de la mémoire. Notez que la configuration par défaut du serveur au "
+"départ est la configuration de production, si aucune autre configuration "
+"n'est spécifiée."
 
 #. Tag: para
 #: readme.xml:81
@@ -219,8 +264,11 @@
 "settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
 "conf</filename> with these recommended values:"
 msgstr ""
-"Pour éviter les problèmes de mémoire, ajuster les paramètres de mémoire avant de déployer les applications. Vous pouvez effectuer cela en mettant à jour les paramètres <literal>JAVA_OPTS</literal> dans le fichier <filename>JBOSS_DIST/jboss-as/server/production/run."
-"conf</filename> avec les valeurs recommandées:"
+"Pour éviter les problèmes de mémoire, ajuster les paramètres de mémoire "
+"avant de déployer les applications. Vous pouvez effectuer cela en mettant à "
+"jour les paramètres <literal>JAVA_OPTS</literal> dans le fichier "
+"<filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> avec les "
+"valeurs recommandées:"
 
 #. Tag: programlisting
 #: readme.xml:83
@@ -238,7 +286,9 @@
 "information on developing applications using Seam."
 msgstr ""
 "Voir le \"Guide de référence Seam\" inclus dans la documentation "
-"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) pour les informations principales pour le déploiement des exemples Seam et les informations détaillées sur les applications de développement utilisant Seam."
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) pour les "
+"informations principales pour le déploiement des exemples Seam et les "
+"informations détaillées sur les applications de développement utilisant Seam."
 
 #. Tag: title
 #: readme.xml:94
@@ -257,9 +307,13 @@
 "faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
 "ulink> for information on how to make the services accessible again."
 msgstr ""
-"Si vous utilisez le rpm, ou la distribution zip, veuillez noter que par défaut, l'authentification est activée et qu'aucun compte utilisateur n'est mis en place. Ceci est conçu pour éviter tout accès non autorisé aux divers services JBoss AS. Veuillez consulter le guide d'installation, ou bien voir <ulink url=\"http://kbase.redhat.com/"
-"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
-"ulink> pour accéder aux informations sur la façon de rendre ces services accessibles à nouveau."
+"Si vous utilisez le rpm, ou la distribution zip, veuillez noter que par "
+"défaut, l'authentification est activée et qu'aucun compte utilisateur n'est "
+"mis en place. Ceci est conçu pour éviter tout accès non autorisé aux divers "
+"services JBoss AS. Veuillez consulter le guide d'installation, ou bien voir "
+"<ulink url=\"http://kbase.redhat.com/faq/FAQ_107_9963.shtm\">http://kbase."
+"redhat.com/faq/FAQ_107_9963.shtm</ulink> pour accéder aux informations sur "
+"la façon de rendre ces services accessibles à nouveau."
 
 #. Tag: title
 #: readme.xml:102
@@ -277,7 +331,13 @@
 "component, and while we are happy to accept bugs filed against this "
 "component, we do not make any commitment to fix them within a specific "
 "timeframe."
-msgstr "Hypersonic SQL propose une fonctionnalité de base de données pour l'évaluation et pour le développement uniquement. N'est PAS recommandé ou supporté en tant que base de données utilisable en production. Le support technique n'est pas disponible pour ce composant, et malgré que nous soyons heureux d'accepter des bogues se rapportant à ce composant, nous ne nous engageons pas à les réparer sous une période fixe."
+msgstr ""
+"Hypersonic SQL propose une fonctionnalité de base de données pour "
+"l'évaluation et pour le développement uniquement. N'est PAS recommandé ou "
+"supporté en tant que base de données utilisable en production. Le support "
+"technique n'est pas disponible pour ce composant, et malgré que nous soyons "
+"heureux d'accepter des bogues se rapportant à ce composant, nous ne nous "
+"engageons pas à les réparer sous une période fixe."
 
 #. Tag: title
 #: readme.xml:110
@@ -294,20 +354,25 @@
 #. Tag: ulink
 #: readme.xml:116
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:120
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:124
 #, no-c-format
 msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
 
 #. Tag: title
 #: readme.xml:131
@@ -427,7 +492,9 @@
 msgid ""
 "Refer to the index.html file in the documentation directory for a list of "
 "included documentation."
-msgstr "Voir le fichier index.html dans le répertoire documentation pour une liste couvrant la documentation incluse."
+msgstr ""
+"Voir le fichier index.html dans le répertoire documentation pour une liste "
+"couvrant la documentation incluse."
 
 #. Tag: para
 #: readme.xml:223
@@ -437,8 +504,9 @@
 "components is distributed in a separate zip file, <filename>jboss-eap-docs-"
 "&lt;version&gt;.zip</filename>."
 msgstr ""
-"Dans la distribution zip, la documentation pour le plate-forme et pour ses composants individuels, est distribuée dans un fichier zip séparé, <filename>jboss-eap-docs-"
-"&lt;version&gt;.zip</filename>."
+"Dans la distribution zip, la documentation pour le plate-forme et pour ses "
+"composants individuels, est distribuée dans un fichier zip séparé, "
+"<filename>jboss-eap-docs-&lt;version&gt;.zip</filename>."
 
 #. Tag: para
 #: readme.xml:227
@@ -452,10 +520,13 @@
 "at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
 "redhat.com/faq/FAQ_35_198.shtm</ulink>"
 msgstr ""
-"Dans le système Linux, la documentation se trouve dans deux rpm qui devront être installés manuellement. Ces rpm sont <filename>jboss-seam-docs-&lt;"
+"Dans le système Linux, la documentation se trouve dans deux rpm qui devront "
+"être installés manuellement. Ces rpm sont <filename>jboss-seam-docs-&lt;"
 "version&gt;.noarch.rpm</filename>, et <filename>rh-eap-docs-&lt;version&gt;."
-"noarch.rpm</filename>. Pour obtenir de l'aide sur l'installation des packages rpm sur Red Hat Enterprise Linux, veuillez vous référer à l'article de base Red Hat Knowledge qui se situe  <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
-"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+"noarch.rpm</filename>. Pour obtenir de l'aide sur l'installation des "
+"packages rpm sur Red Hat Enterprise Linux, veuillez vous référer à l'article "
+"de base Red Hat Knowledge qui se situe  <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_35_198.shtm\">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>"
 
 #. Tag: para
 #: readme.xml:234
@@ -464,7 +535,10 @@
 "<filename>Installation Guide</filename> explains how to install and verify "
 "the installation of JBoss Enteprise Application Platform using different "
 "installation modes."
-msgstr "<filename>Installation Guide</filename> explique comment installer et comment vérifier l'installation de JBoss Enteprise Application Platform en utilisant les différents modes d'installation."
+msgstr ""
+"<filename>Installation Guide</filename> explique comment installer et "
+"comment vérifier l'installation de JBoss Enteprise Application Platform en "
+"utilisant les différents modes d'installation."
 
 #. Tag: para
 #: readme.xml:239
@@ -475,7 +549,12 @@
 "configuration sets and services. Using a simple web application it "
 "illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
 "the JSF and EJB3 components."
-msgstr "<filename>Getting Started</filename> décrit la structure du répertoire de la plateforme et donne un aperçu rapide du serveur d'application et des différents services et cas de configurations. Par l'utilisation d'une simple application web, il illustre l'utilisation des composants JSF-EJB3 et comment Seam intègre les composants JSF et EJB3."
+msgstr ""
+"<filename>Getting Started</filename> décrit la structure du répertoire de la "
+"plateforme et donne un aperçu rapide du serveur d'application et des "
+"différents services et cas de configurations. Par l'utilisation d'une simple "
+"application web, il illustre l'utilisation des composants JSF-EJB3 et "
+"comment Seam intègre les composants JSF et EJB3."
 
 #. Tag: para
 #: readme.xml:244
@@ -483,7 +562,9 @@
 msgid ""
 "<filename>Server Configuration Guide</filename> explains all administrative "
 "and configuration functions in detail."
-msgstr "<filename>Le guide de configuration du serveur</filename> explique toutes les fonctions administratives et de configuration en détails."
+msgstr ""
+"<filename>Le guide de configuration du serveur</filename> explique toutes "
+"les fonctions administratives et de configuration en détails."
 
 #. Tag: para
 #: readme.xml:250
@@ -495,9 +576,12 @@
 "redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
 "redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
 msgstr ""
-"Les versions mises à jour de la documentation comprenant les errata et les informations supplémentaires, comme le code d'application, ainsi que la dernière version des notes de mise à jour, sont disponible sur internet par le lien suivant <ulink url=\"http://www."
-"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
-"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+"Les versions mises à jour de la documentation comprenant les errata et les "
+"informations supplémentaires, comme le code d'application, ainsi que la "
+"dernière version des notes de mise à jour, sont disponible sur internet par "
+"le lien suivant <ulink url=\"http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/</ulink>."
 
 #. Tag: title
 #: readme.xml:265
@@ -520,7 +604,9 @@
 "update includes numerious bug fixes that improves the overall component."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-925\">JBPAPP-925</"
-"ulink>: JBoss Messaging a été mis à jour à la version 1.4.0.SP3_CP03. Cette mise à jour comprend de nombreuses résolutions de bogues qui améliorent le composant en général."
+"ulink>: JBoss Messaging a été mis à jour à la version 1.4.0.SP3_CP03. Cette "
+"mise à jour comprend de nombreuses résolutions de bogues qui améliorent le "
+"composant en général."
 
 #. Tag: para
 #: readme.xml:282
@@ -531,7 +617,8 @@
 "contains the JBoss Messaging 1.4.0.SP3_CP03 User Guide."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-920\">JBPAPP-920</"
-"ulink>: La documentation JBoss Messaging n'était plus à jour. Cette version CP comprend le guide d'utilisation JBoss Messaging 1.4.0.SP3_CP03 User Guide."
+"ulink>: La documentation JBoss Messaging n'était plus à jour. Cette version "
+"CP comprend le guide d'utilisation JBoss Messaging 1.4.0.SP3_CP03 User Guide."
 
 #. Tag: para
 #: readme.xml:287
@@ -543,7 +630,9 @@
 "configuration has now been corrected."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
-"ulink>: La configuration SQL par défaut contient des erreurs, ce qui pose un problème dans hsqldb qui utilise cette configuration. Ce problème a été résolu avec la configuration par défaut."
+"ulink>: La configuration SQL par défaut contient des erreurs, ce qui pose un "
+"problème dans hsqldb qui utilise cette configuration. Ce problème a été "
+"résolu avec la configuration par défaut."
 
 #. Tag: para
 #: readme.xml:292
@@ -556,7 +645,10 @@
 "creating a more stable Messaging component."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-813\">JBPAPP-813</"
-"ulink>: Le client Messaging inclut un bogue qui pourrait l'interrompre indéfiniement, créant un échec <code>ClusteredConnectionFactory</code>, issu d'une interruption socket. Ce problème a été maintenant rectifié dans la dernière version EAP, créant un composant Messaging plus stable."
+"ulink>: Le client Messaging inclut un bogue qui pourrait l'interrompre "
+"indéfiniement, créant un échec <code>ClusteredConnectionFactory</code>, issu "
+"d'une interruption socket. Ce problème a été maintenant rectifié dans la "
+"dernière version EAP, créant un composant Messaging plus stable."
 
 #. Tag: title
 #: readme.xml:311
@@ -573,7 +665,8 @@
 "2.2.2.SP8. This upgrade includes numerious bug fixes."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
-"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version 2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
+"ulink>: Le composant JBoss Remoting EAP a été mis à niveau à la version "
+"2.2.2.SP8. Cette mise à niveau comprend de nouvelles résolutions de bogues."
 
 #. Tag: title
 #: readme.xml:323
@@ -590,7 +683,8 @@
 "CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-930\">JBPAPP-930</"
-"ulink>: La mise à niveau de JBossWS Common 1.0.0.GA_CP01 est comprise dans cette version CP."
+"ulink>: La mise à niveau de JBossWS Common 1.0.0.GA_CP01 est comprise dans "
+"cette version CP."
 
 #. Tag: para
 #: readme.xml:332
@@ -613,8 +707,9 @@
 "SP2_CP02. This upgrade incorporates various bug fixes and enhancements."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
-"ulink>: Le composant JBoss Web Services a été mis à niveau à la version 2.0.1."
-"SP2_CP02. Cette mise à niveau comprend de nombreuses résolutions de bogues et des améliorations."
+"ulink>: Le composant JBoss Web Services a été mis à niveau à la version "
+"2.0.1.SP2_CP02. Cette mise à niveau comprend de nombreuses résolutions de "
+"bogues et des améliorations."
 
 #. Tag: title
 #: readme.xml:345
@@ -632,7 +727,10 @@
 "been updated with the above changes for this release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-755\">JBPAPP-755</"
-"ulink>: Le fichier source Seam readme.txt corrige les liens de mise à jour vers seamwork.org. Aussi, les mentions de EAP à la place de JBoss AS sont également corrigées. Ce fichier a été mis à jour avec les changements mentionnés ci-dessus pour cette version."
+"ulink>: Le fichier source Seam readme.txt corrige les liens de mise à jour "
+"vers seamwork.org. Aussi, les mentions de EAP à la place de JBoss AS sont "
+"également corrigées. Ce fichier a été mis à jour avec les changements "
+"mentionnés ci-dessus pour cette version."
 
 #. Tag: title
 #: readme.xml:357
@@ -653,8 +751,13 @@
 "()</methodname> to <filename>MergeTest.java</filename>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-938\">JBPAPP-938</"
-"ulink>: Une entité parent inchangée comprenait une valeur de sa version incrémentée par erreur lorsqu'impliquée dans une relation de trop. Cette erreur a été rectifiée dans cette dernière version CP, grâce à la correction du fichier <filename>CollectionType.java</filename>et en ajoutant la nouvelle méthode intitulée <methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection"
-"()</methodname> dans <filename>MergeTest.java</filename>."
+"ulink>: Une entité parent inchangée comprenait une valeur de sa version "
+"incrémentée par erreur lorsqu'impliquée dans une relation de trop. Cette "
+"erreur a été rectifiée dans cette dernière version CP, grâce à la correction "
+"du fichier <filename>CollectionType.java</filename>et en ajoutant la "
+"nouvelle méthode intitulée "
+"<methodname>testNoExtraUpdatesOnPersistentMergeVersionedWithCollection()</"
+"methodname> dans <filename>MergeTest.java</filename>."
 
 #. Tag: para
 #: readme.xml:366
@@ -671,10 +774,15 @@
 "<emphasis>junitinstrument</emphasis> test now runs successfully."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-936\">JBPAPP-936</"
-"ulink>: La méthode <methodname>AnnotationBinder.mustBeSkipped</methodname> comprend une référence-chaîne de caractères incorrectement codée (code fixe) dans la classe <classname>org.hibernate."
-"tool.instrument.javassist.FieldHandler</classname>. Cette erreur signifie que le test <emphasis>junitinstrument</emphasis> n'était pas exécuté correctement. Ce problème a été réglé, et la location de la classe du package qui convient a été référencée par le nom de classe <classname>org.hibernate."
-"bytecode.javassist.FieldHandler</classname> et le test "
-"<emphasis>junitinstrument</emphasis> peut maintenant être exécuté sans problèmes."
+"ulink>: La méthode <methodname>AnnotationBinder.mustBeSkipped</methodname> "
+"comprend une référence-chaîne de caractères incorrectement codée (code fixe) "
+"dans la classe <classname>org.hibernate.tool.instrument.javassist."
+"FieldHandler</classname>. Cette erreur signifie que le test "
+"<emphasis>junitinstrument</emphasis> n'était pas exécuté correctement. Ce "
+"problème a été réglé, et la location de la classe du package qui convient a "
+"été référencée par le nom de classe <classname>org.hibernate.bytecode."
+"javassist.FieldHandler</classname> et le test <emphasis>junitinstrument</"
+"emphasis> peut maintenant être exécuté sans problèmes."
 
 #. Tag: para
 #: readme.xml:371
@@ -687,7 +795,10 @@
 "supporting JDK 6."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-915\">JBPAPP-915</"
-"ulink>: Une opération de fusion pourrait échouer s'il y avait un entité transitoire accessible par de nombreux chemins et qu'un de ces chemins au moins ne cascadait pas au moment de la fusion. Ce problème est réglé maintenant que EAP 4.3 prend en charge JDK 6."
+"ulink>: Une opération de fusion pourrait échouer s'il y avait un entité "
+"transitoire accessible par de nombreux chemins et qu'un de ces chemins au "
+"moins ne cascadait pas au moment de la fusion. Ce problème est réglé "
+"maintenant que EAP 4.3 prend en charge JDK 6."
 
 #. Tag: para
 #: readme.xml:376
@@ -700,8 +811,8 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-908\">JBPAPP-908</"
 "ulink>: La sérialization proxy Hibernate était endommagée car la classe "
-"<classname>AbstractLazyInitializer</classname> n'était pas sérialisable. "
-"Ce problème est maintenant réglé dans cette version CP."
+"<classname>AbstractLazyInitializer</classname> n'était pas sérialisable. Ce "
+"problème est maintenant réglé dans cette version CP."
 
 #. Tag: para
 #: readme.xml:381
@@ -714,9 +825,11 @@
 "elements were now unique. This issue has been corrected with this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-899\">JBPAPP-899</"
-"ulink>: Il y avait une erreur dans le gestionnaire d'entités quand les méthodes"
-"<methodname>getSingleResult()</methodname> et <methodname>fetch()</"
-"methodname> retournaient un <code>NonUniqueResultException</code> car les éléments étaient dorénavant uniques. Ce problème a maintenant été corrigé dans cette version CP."
+"ulink>: Il y avait une erreur dans le gestionnaire d'entités quand les "
+"méthodes<methodname>getSingleResult()</methodname> et <methodname>fetch()</"
+"methodname> retournaient un <code>NonUniqueResultException</code> car les "
+"éléments étaient dorénavant uniques. Ce problème a maintenant été corrigé "
+"dans cette version CP."
 
 #. Tag: para
 #: readme.xml:386
@@ -728,8 +841,10 @@
 "on error</option>, <option>format</option> options now avaliable."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-859\">JBPAPP-859</"
-"ulink>: La classe <classname>SchemaUpdate</classname> a été améliorée grâce aux options <option>output file name</option>, <option>delimiter</option>, <option>halt "
-"on error</option>, <option>format</option> maintenant disponibles."
+"ulink>: La classe <classname>SchemaUpdate</classname> a été améliorée grâce "
+"aux options <option>output file name</option>, <option>delimiter</option>, "
+"<option>halt on error</option>, <option>format</option> maintenant "
+"disponibles."
 
 #. Tag: para
 #: readme.xml:391
@@ -742,7 +857,10 @@
 "EAP and Oracle. This issue has now been rectified in this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-782\">JBPAPP-782</"
-"ulink>: La classe <classname>MapBinder</classname> permet la production de relevés SQL qui n'étaient pas supportés par la base de données Oracle 10g. C'était surtout un problème pour certains utilisateurs EJB3 Persistence sur EAP et Oracle. Ce problème a maintenant été réglé dans cette version CP."
+"ulink>: La classe <classname>MapBinder</classname> permet la production de "
+"relevés SQL qui n'étaient pas supportés par la base de données Oracle 10g. "
+"C'était surtout un problème pour certains utilisateurs EJB3 Persistence sur "
+"EAP et Oracle. Ce problème a maintenant été réglé dans cette version CP."
 
 #. Tag: title
 #: readme.xml:410
@@ -773,7 +891,10 @@
 "number is included with this release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1004\">JBPAPP-1004</"
-"ulink>: Les versions précédentes de EAP contiennent un nombre <property>serialVersionUID</property> incorrect, qui interfère avec la comptabilité vers le bas. Le nombre correct <property>serialVersionUID</property> est inclus dans cette version."
+"ulink>: Les versions précédentes de EAP contiennent un nombre "
+"<property>serialVersionUID</property> incorrect, qui interfère avec la "
+"comptabilité vers le bas. Le nombre correct <property>serialVersionUID</"
+"property> est inclus dans cette version."
 
 #. Tag: title
 #: readme.xml:428
@@ -790,8 +911,8 @@
 "1.5.GA_CP02."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-972\">JBPAPP-972</"
-"ulink>: JBoss Aspect-Oriented Programming (AOP) a été mis à niveau à la version "
-"1.5.GA_CP02."
+"ulink>: JBoss Aspect-Oriented Programming (AOP) a été mis à niveau à la "
+"version 1.5.GA_CP02."
 
 #. Tag: title
 #: readme.xml:434
@@ -808,7 +929,8 @@
 "issues related to this class library."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-971\">JBPAPP-971</"
-"ulink>: Javassist a été mis à niveau à la version 3.8.0.GA, réglant de nombreux problèmes relatifs à cette bibliothèque de classes."
+"ulink>: Javassist a été mis à niveau à la version 3.8.0.GA, réglant de "
+"nombreux problèmes relatifs à cette bibliothèque de classes."
 
 #. Tag: title
 #: readme.xml:440
@@ -847,9 +969,15 @@
 "attribute&gt;</programlisting>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-944\">JBPAPP-944</"
-"ulink>: <classname>ClusteredSession</classname> incluait une logique qui passait outre la reproduction de sessions de métadonnées si l'unique changement était au niveau de l'heure système. Ce problème a été réglé en changeant l'interval maximum par défaut entre les demandes. Cet interval est maintenant de 60 secondes et cette valeur est maintenant configurable. Cet attribut peut être modifié par le rajout d'un attribut dans le fichier <filename>jboss-service.xml</filename> qui ressemble à "
-"<programlisting>&lt;attribute name=\"MaxUnreplicatedInterval\"&gt;30&lt;/"
-"attribute&gt;</programlisting>."
+"ulink>: <classname>ClusteredSession</classname> incluait une logique qui "
+"passait outre la reproduction de sessions de métadonnées si l'unique "
+"changement était au niveau de l'heure système. Ce problème a été réglé en "
+"changeant l'interval maximum par défaut entre les demandes. Cet interval est "
+"maintenant de 60 secondes et cette valeur est maintenant configurable. Cet "
+"attribut peut être modifié par le rajout d'un attribut dans le fichier "
+"<filename>jboss-service.xml</filename> qui ressemble à <programlisting>&lt;"
+"attribute name=\"MaxUnreplicatedInterval\"&gt;30&lt;/attribute&gt;</"
+"programlisting>."
 
 #. Tag: title
 #: readme.xml:452
@@ -870,7 +998,10 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-926\">JBPAPP-926</"
 "ulink>: Une section du guide de configuration du serveur intitulé "
-"<emphasis>Existing Entity Commands</emphasis> précise les mauvais packages pour certaines classes. Cette version mise à jour du guide de configuration du serveur inclus dans ce CP contient les informations correctes du package pour les classes affectées. "
+"<emphasis>Existing Entity Commands</emphasis> précise les mauvais packages "
+"pour certaines classes. Cette version mise à jour du guide de configuration "
+"du serveur inclus dans ce CP contient les informations correctes du package "
+"pour les classes affectées. "
 
 #. Tag: title
 #: readme.xml:458
@@ -889,7 +1020,9 @@
 "ClassLoader.allowArraySyntax=true</programlisting>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-907\">JBPAPP-907</"
-"ulink>: Il y avait un problème de congestionnement au niveau de la désérialisation des arrays pour JDK 1.6. Pour régler ce problème, on a rajouté <filename>run.conf</filename> file: <programlisting>-Dsun.lang."
+"ulink>: Il y avait un problème de congestionnement au niveau de la "
+"désérialisation des arrays pour JDK 1.6. Pour régler ce problème, on a "
+"rajouté <filename>run.conf</filename> file: <programlisting>-Dsun.lang."
 "ClassLoader.allowArraySyntax=true</programlisting>."
 
 #. Tag: title
@@ -907,8 +1040,8 @@
 "CP02."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-897\">JBPAPP-897</"
-"ulink>: JBoss Transaction Services ont été mis à niveau vers la version 4.2.3 SP5 "
-"CP02."
+"ulink>: JBoss Transaction Services ont été mis à niveau vers la version "
+"4.2.3 SP5 CP02."
 
 #. Tag: title
 #: readme.xml:470
@@ -926,8 +1059,10 @@
 "These connections are now always closed to restrict exceptions."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-895\">JBPAPP-895</"
-"ulink>: Les connexions Java Messaging Service (JMS) devaient être constamment fermées en référence au JCA (J2EE Connector Architecture). "
-"Ces connexions sont maintenant fermées pour les exceptions particulières uniquement."
+"ulink>: Les connexions Java Messaging Service (JMS) devaient être "
+"constamment fermées en référence au JCA (J2EE Connector Architecture). Ces "
+"connexions sont maintenant fermées pour les exceptions particulières "
+"uniquement."
 
 #. Tag: title
 #: readme.xml:476
@@ -947,9 +1082,11 @@
 "returned objects when there is no property editor found."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-891\">JBPAPP-891</"
-"ulink>: L'outil de contrôle <emphasis>Twiddle</emphasis> n'a pas publié des résultats d'"
-"<code>invoke</code>, même en l'absence d'un éditeur de propriété pour l'objet retourné. Corrigé dans la version CP, <emphasis>Twiddle</"
-"emphasis> invoque maintenant la méthode <methodname>toString()</methodname> sur les objets retournés quand aucun éditeur de propriété n'est trouvé."
+"ulink>: L'outil de contrôle <emphasis>Twiddle</emphasis> n'a pas publié des "
+"résultats d'<code>invoke</code>, même en l'absence d'un éditeur de propriété "
+"pour l'objet retourné. Corrigé dans la version CP, <emphasis>Twiddle</"
+"emphasis> invoque maintenant la méthode <methodname>toString()</methodname> "
+"sur les objets retournés quand aucun éditeur de propriété n'est trouvé."
 
 #. Tag: title
 #: readme.xml:488
@@ -967,8 +1104,10 @@
 "issue so that serialization functions correctly."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-877\">JBPAPP-877</"
-"ulink>: La version JBoss Serialization 1.0.3GA rencontrerait"
-"<code>ClassCastExceptions</code> en cours d'utilisation. Cette mise à jour corrige ce problème de façon à ce que la sérialisation fonctionne correctement. "
+"ulink>: La version JBoss Serialization 1.0.3GA "
+"rencontrerait<code>ClassCastExceptions</code> en cours d'utilisation. Cette "
+"mise à jour corrige ce problème de façon à ce que la sérialisation "
+"fonctionne correctement. "
 
 #. Tag: title
 #: readme.xml:494
@@ -986,7 +1125,9 @@
 "enhancement to the EAP is included within this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-867\">JBPAPP-867</"
-"ulink>: Une implémentation de l'interface <interfacename>ExceptionSorter</interfacename> devrait être proposée aux utilisateurs du serveur IBM DB2 Data Server. Cette amélioration du EAP est comprise dans cette version CP."
+"ulink>: Une implémentation de l'interface <interfacename>ExceptionSorter</"
+"interfacename> devrait être proposée aux utilisateurs du serveur IBM DB2 "
+"Data Server. Cette amélioration du EAP est comprise dans cette version CP."
 
 #. Tag: title
 #: readme.xml:500
@@ -1006,7 +1147,13 @@
 "default policy for EJB2 home proxies."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-864\">JBPAPP-864</"
-"ulink>: Les fabriques proxy clusterisées ne se reliaient pas aux proxies utilisateurs. Ce problème a maintenant été rectifié par la prise en charge des proxies utilisateur clusterisés pour les beans EJB3. Cependant, pour éviter les problèmes de compatibilité par le bas, la politique d'équilibrage des charges de travail des proxies utilisateur ont été codés (codes fixes) en circuit cyclique. C'est également la politique par défaut des proxies utilisateurs EJB2."
+"ulink>: Les fabriques proxy clusterisées ne se reliaient pas aux proxies "
+"utilisateurs. Ce problème a maintenant été rectifié par la prise en charge "
+"des proxies utilisateur clusterisés pour les beans EJB3. Cependant, pour "
+"éviter les problèmes de compatibilité par le bas, la politique d'équilibrage "
+"des charges de travail des proxies utilisateur ont été codés (codes fixes) "
+"en circuit cyclique. C'est également la politique par défaut des proxies "
+"utilisateurs EJB2."
 
 #. Tag: title
 #: readme.xml:508
@@ -1024,7 +1171,9 @@
 "bin files."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>: Permet à des instances multiples d'être installées dans une machine qui utilise une méthode de sous-package. Cette fonctionnalité a été rajoutée à cette version avec les fichiers -bin."
+"ulink>: Permet à des instances multiples d'être installées dans une machine "
+"qui utilise une méthode de sous-package. Cette fonctionnalité a été rajoutée "
+"à cette version avec les fichiers -bin."
 
 #. Tag: para
 #: readme.xml:513
@@ -1035,7 +1184,13 @@
 "additional installation only and cannot be used in place of a regular RPM "
 "jbossas installation. If you only have one version of the AS, it will have "
 "to be the regular RPM installation (or ZIP or installer for older versions)."
-msgstr "Il est important de noter que l'installation conventionnelle de jbossas est préalable à l'installation de -bin. -bin est une installation additionnelle uniquement et ne peut pas être utilisée à la place d'une installation jbossas RPM conventionnelle. Si vous ne possédez qu'une seule version de AS, cela devra être l'installation RPM conventionnelle (ou bien ZIP ou bien le programme d'installation des anciennes versions)."
+msgstr ""
+"Il est important de noter que l'installation conventionnelle de jbossas est "
+"préalable à l'installation de -bin. -bin est une installation additionnelle "
+"uniquement et ne peut pas être utilisée à la place d'une installation "
+"jbossas RPM conventionnelle. Si vous ne possédez qu'une seule version de AS, "
+"cela devra être l'installation RPM conventionnelle (ou bien ZIP ou bien le "
+"programme d'installation des anciennes versions)."
 
 #. Tag: title
 #: readme.xml:517
@@ -1053,7 +1208,9 @@
 "from the distribution. This missing file has now been re-included."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-857\">JBPAPP-857</"
-"ulink>: Le fichier .rar <filename>mail-ra.rar</filename> utilisé dans le serveur d'application pour recevoir des emails avec JavaMail API, était manquant de la distribution. Ce fichier manquant a été inclus."
+"ulink>: Le fichier .rar <filename>mail-ra.rar</filename> utilisé dans le "
+"serveur d'application pour recevoir des emails avec JavaMail API, était "
+"manquant de la distribution. Ce fichier manquant a été inclus."
 
 #. Tag: title
 #: readme.xml:523
@@ -1071,7 +1228,10 @@
 "consumption of Messages during deployment and is supported with this release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-856\">JBPAPP-856</"
-"ulink>: Le support de la propriété de configuration d'activation de DeliveryActive MDB en cours de déploiement. Ce mécanisme permet de démarrer ou d'arrêter la consommation de messages pendant le déploiement et est supporté par cette version."
+"ulink>: Le support de la propriété de configuration d'activation de "
+"DeliveryActive MDB en cours de déploiement. Ce mécanisme permet de démarrer "
+"ou d'arrêter la consommation de messages pendant le déploiement et est "
+"supporté par cette version."
 
 #. Tag: title
 #: readme.xml:529
@@ -1092,8 +1252,13 @@
 "With these changes the example now functions correctly under SQL Server 2005."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-844\">JBPAPP-844</"
-"ulink>: L'exemple de la source de données MSSQL était incompatible avec le serveur SQL Server 2005. Pour régler ce problème de compatibilité, <code>driver-class</code> a été mis à jour de <code>com.microsoft.jdbc.sqlserver.SQLServerDriver</code> vers "
-"<code>com.microsoft.sqlserver.jdbc.SQLServerDriver</code> et le port par défaut de <code>connection-url</code>a été changé de 1433 à 3918. Avec ces changements, l'exemple fonctionne maintenant correctement dans le serveur SQL Server 2005."
+"ulink>: L'exemple de la source de données MSSQL était incompatible avec le "
+"serveur SQL Server 2005. Pour régler ce problème de compatibilité, "
+"<code>driver-class</code> a été mis à jour de <code>com.microsoft.jdbc."
+"sqlserver.SQLServerDriver</code> vers <code>com.microsoft.sqlserver.jdbc."
+"SQLServerDriver</code> et le port par défaut de <code>connection-url</code>a "
+"été changé de 1433 à 3918. Avec ces changements, l'exemple fonctionne "
+"maintenant correctement dans le serveur SQL Server 2005."
 
 #. Tag: title
 #: readme.xml:535
@@ -1114,11 +1279,12 @@
 "which has since been fixed."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-815\">JBPAPP-815</"
-"ulink>: Il y avait un problème quand DOCTYPE était ajouté au fichier <filename>-"
-"ds.xml</filename> et quand l'option <option>ValidateDTDs</option> était fixée à 'true' (vrai)  <filename>jbossjca-services.xml</filename>, entraînant alors des erreurs de validation."
-"Ceci était dû à un problème dans l'élément <property>tx-"
-"connection-factory</property> du fichier <filename>jms-ds.xml</filename> "
-"qui a été réglé maintenant."
+"ulink>: Il y avait un problème quand DOCTYPE était ajouté au fichier "
+"<filename>-ds.xml</filename> et quand l'option <option>ValidateDTDs</option> "
+"était fixée à 'true' (vrai)  <filename>jbossjca-services.xml</filename>, "
+"entraînant alors des erreurs de validation.Ceci était dû à un problème dans "
+"l'élément <property>tx-connection-factory</property> du fichier "
+"<filename>jms-ds.xml</filename> qui a été réglé maintenant."
 
 #. Tag: title
 #: readme.xml:541
@@ -1137,7 +1303,11 @@
 "has now been restored, enabling the example to be run correctly."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-805\">JBPAPP-805</"
-"ulink>: Un fichier Java manquait dans le premier exemple sécurité du guide de configuration du serveur, empêchant ainsi que l'exemple puisse être exécuté correctement. Le fichier manquant <filename>EchoSecurityProxy.java</filename> a maintenant été restauré, permettant ainsi à l'exemple d'être exécuté correctement."
+"ulink>: Un fichier Java manquait dans le premier exemple sécurité du guide "
+"de configuration du serveur, empêchant ainsi que l'exemple puisse être "
+"exécuté correctement. Le fichier manquant <filename>EchoSecurityProxy.java</"
+"filename> a maintenant été restauré, permettant ainsi à l'exemple d'être "
+"exécuté correctement."
 
 #. Tag: title
 #: readme.xml:547
@@ -1156,7 +1326,11 @@
 "issue and allowing the example to execute correctly."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-799\">JBPAPP-799</"
-"ulink>: l'exemple seamejb3 générait une ereur<code>FaceletException</code>. Ce problème était dû à l'inclusion de fichiers .jar incorrects dans l'exemple. Cette mise à jour CP incorpore les fichiers .jar qui conviennent, réglant ainsi ce problème et permettant que l'exemple soit exécuté correctement."
+"ulink>: l'exemple seamejb3 générait une ereur<code>FaceletException</code>. "
+"Ce problème était dû à l'inclusion de fichiers .jar incorrects dans "
+"l'exemple. Cette mise à jour CP incorpore les fichiers .jar qui conviennent, "
+"réglant ainsi ce problème et permettant que l'exemple soit exécuté "
+"correctement."
 
 #. Tag: title
 #: readme.xml:553
@@ -1174,7 +1348,9 @@
 "ability to accomplish this is now included."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-783\">JBPAPP-783</"
-"ulink>: Il n'existait pas de mécanisme de fermeture des connexions JMS quand MDB rencontrait une <code>RuntimeException</code>. Ce problème a maintenant été résolu."
+"ulink>: Il n'existait pas de mécanisme de fermeture des connexions JMS quand "
+"MDB rencontrait une <code>RuntimeException</code>. Ce problème a maintenant "
+"été résolu."
 
 #. Tag: title
 #: readme.xml:559
@@ -1193,7 +1369,10 @@
 "included within this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-746\">JBPAPP-746</"
-"ulink>: Il y avait un bogue dans le compilateur JavaServer Pages (JSP) affectant Tomcat quand le contenu de la méthode doTag() était vide, ce qui impliquait qu'aucun html me pouvait être émis. Une solution pour ce problème relatif à Tomcat a été trouvée dans cette version CP."
+"ulink>: Il y avait un bogue dans le compilateur JavaServer Pages (JSP) "
+"affectant Tomcat quand le contenu de la méthode doTag() était vide, ce qui "
+"impliquait qu'aucun html me pouvait être émis. Une solution pour ce problème "
+"relatif à Tomcat a été trouvée dans cette version CP."
 
 #. Tag: title
 #: readme.xml:565
@@ -1211,7 +1390,9 @@
 "URLs are decoded correctly after servelt redirects."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-729\">JBPAPP-729</"
-"ulink>: Un mauvais groupe de caractères a été utilisé pour décoder les paramètres URL après une redirection servlet. Réglé maintenant dans ce CP, les URLs sont décodés correctement après redirection du servlet."
+"ulink>: Un mauvais groupe de caractères a été utilisé pour décoder les "
+"paramètres URL après une redirection servlet. Réglé maintenant dans ce CP, "
+"les URLs sont décodés correctement après redirection du servlet."
 
 #. Tag: title
 #: readme.xml:571
@@ -1231,7 +1412,12 @@
 "the user is redirected to the displayMbeans page."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
-"ulink>: Le code source JavaServer Pages (JSP) a été exposé au niveau de la console-jmx quand on tombait sur une page d'erreur. On a réglé ce problème en vérifiant si la classe utilisait bien un Bean existant issu de la gamme requise ou bien s'il en instanciait un nouveau. Si le Bean provenant de la gamme requise est nul, l'utilisateur est alors redirigé vers la page displayMbeans."
+"ulink>: Le code source JavaServer Pages (JSP) a été exposé au niveau de la "
+"console-jmx quand on tombait sur une page d'erreur. On a réglé ce problème "
+"en vérifiant si la classe utilisait bien un Bean existant issu de la gamme "
+"requise ou bien s'il en instanciait un nouveau. Si le Bean provenant de la "
+"gamme requise est nul, l'utilisateur est alors redirigé vers la page "
+"displayMbeans."
 
 #. Tag: title
 #: readme.xml:577
@@ -1249,7 +1435,10 @@
 "optimization required is now included within this CP release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-295\">JBPAPP-295</"
-"ulink>: Stateful Session Bean (SFSB) répliqué requiert l'optimisation pour pouvoir être utilisé avec Buddy Replication. Après une période de tests extensive et plusieurs réparations, l'optimisation requise est maintenant incluse dans cette version CP."
+"ulink>: Stateful Session Bean (SFSB) répliqué requiert l'optimisation pour "
+"pouvoir être utilisé avec Buddy Replication. Après une période de tests "
+"extensive et plusieurs réparations, l'optimisation requise est maintenant "
+"incluse dans cette version CP."
 
 #. Tag: title
 #: readme.xml:593
@@ -1261,7 +1450,9 @@
 #: readme.xml:596
 #, no-c-format
 msgid "Following is a list of known issues at the time of release."
-msgstr "Vous trouverez ci-dessous une liste des problèmes connus au moment de la parution de cette version."
+msgstr ""
+"Vous trouverez ci-dessous une liste des problèmes connus au moment de la "
+"parution de cette version."
 
 #. Tag: para
 #: readme.xml:601
@@ -1275,7 +1466,8 @@
 "performance."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
-"ulink>: Au sein du  composant Hibernate d'EAP, l'ordre d'itération de HashMap et de HashSet "
-"a changé par rapport aux versions antérieures à cause de la prise en charge de JDK 1.6. "
-"Ceci impliquait que l'ordre des colonnes des clauses-union et des sous-classes-union a changé, générant un léger impact au niveau de la performance des composants."
-
+"ulink>: Au sein du  composant Hibernate d'EAP, l'ordre d'itération de "
+"HashMap et de HashSet a changé par rapport aux versions antérieures à cause "
+"de la prise en charge de JDK 1.6. Ceci impliquait que l'ordre des colonnes "
+"des clauses-union et des sous-classes-union a changé, générant un léger "
+"impact au niveau de la performance des composants."

Modified: projects/docs/enterprise/4.3.4/readme/pot/Author_Group.pot
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pot/Author_Group.pot	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/pot/Author_Group.pot	2009-03-12 00:45:10 UTC (rev 85753)
@@ -6,7 +6,7 @@
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-30 01:07+0000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
 "Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -14,8 +14,10 @@
 "Content-Type: application/x-xml2pot; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#. Tag: corpauthor
-#: Author_Group.xml:5
+#. Tag: author
+#: Author_Group.xml:6
 #, no-c-format
-msgid "Red Hat Documentation Group"
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
 msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/pot/Book_Info.pot
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pot/Book_Info.pot	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/pot/Book_Info.pot	2009-03-12 00:45:10 UTC (rev 85753)
@@ -6,7 +6,7 @@
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-30 01:07+0000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
 "Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -17,28 +17,29 @@
 #. Tag: title
 #: Book_Info.xml:6
 #, no-c-format
-msgid "Release Notes"
+msgid "Release Notes CP04"
 msgstr ""
 
 #. Tag: subtitle
 #: Book_Info.xml:7
 #, no-c-format
-msgid "JBoss Enterprise Application Platform 4.3.0.CP02"
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
 msgstr ""
 
 #. Tag: para
-#: Book_Info.xml:11
+#: Book_Info.xml:13
 #, no-c-format
 msgid ""
 "These release notes contain important information related to JBoss "
-"Enterprise Application Platform 4.3.0.CP02 that may not be currently "
+"Enterprise Application Platform 4.3.0.CP04 that may not be currently "
 "available in the Product Manuals. You should read these Release Notes in "
 "their entirety before installing JBoss Enterprise Application Platform 4.3.0."
-"CP02."
+"CP04."
 msgstr ""
 
 #. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
 #, no-c-format
 msgid "&HOLDER;"
 msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/pot/messages.mo
===================================================================
(Binary files differ)

Modified: projects/docs/enterprise/4.3.4/readme/pt-BR/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pt-BR/Author_Group.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/pt-BR/Author_Group.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,14 +1,14 @@
-# translation of Author_Group.po to Brazilian Portuguese
+# translation of readme.po to Brazilian Portuguese
 # Language pt-BR translations for readme package.
 #
 # Automatically generated, 2008.
 # Leticia de Lima <ldelima at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-07-29 12:17+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 12:19+1000\n"
 "Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
 "Language-Team: Brazilian Portuguese <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -16,9 +16,10 @@
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.11.4\n"
 
-#. Tag: corpauthor
-#: Author_Group.xml:5
+#. Tag: author
+#: Author_Group.xml:6
 #, no-c-format
-msgid "Red Hat Documentation Group"
-msgstr "Grupo de Documentação da Red Hat"
-
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/pt-BR/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pt-BR/Book_Info.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/pt-BR/Book_Info.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,14 +1,14 @@
-# translation of Book_Info.po to Brazilian Portuguese
+# translation of readme.po to Brazilian Portuguese
 # Language pt-BR translations for readme package.
 #
 # Automatically generated, 2008.
 # Leticia de Lima <ldelima at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Book_Info\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-07-30 12:02+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 12:19+1000\n"
 "Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
 "Language-Team: Brazilian Portuguese <en at li.org>\n"
 "MIME-Version: 1.0\n"
@@ -18,32 +18,35 @@
 
 #. Tag: title
 #: Book_Info.xml:6
-#, no-c-format
-msgid "Release Notes"
+#, fuzzy, no-c-format
+msgid "Release Notes CP04"
 msgstr "Notas de Versão "
 
 #. Tag: subtitle
 #: Book_Info.xml:7
-#, no-c-format
-msgid "JBoss Enterprise Application Platform 4.3.0.CP02"
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
 msgstr "Plataforma de Aplicativo JBoss Enterprise 4.3.0.CP02"
 
 #. Tag: para
-#: Book_Info.xml:11
-#, no-c-format
+#: Book_Info.xml:13
+#, fuzzy, no-c-format
 msgid ""
 "These release notes contain important information related to JBoss "
-"Enterprise Application Platform 4.3.0.CP02 that may not be currently "
+"Enterprise Application Platform 4.3.0.CP04 that may not be currently "
 "available in the Product Manuals. You should read these Release Notes in "
 "their entirety before installing JBoss Enterprise Application Platform 4.3.0."
-"CP02."
+"CP04."
 msgstr ""
-"As notas de versão contém informações importantes relacionadas à Plataforma de Aplicativo JBoss Enterprise 4.3.0.CP02, das quais podem não estar disponíveis nos Manuais do Produto. É recomendável ler por completo estas Notas de Versão antes de instalar a Plataforma de Aplicativo do JBoss Enterprise 4.3.0."
-"CP02."
+"As notas de versão contém informações importantes relacionadas à Plataforma "
+"de Aplicativo JBoss Enterprise 4.3.0.CP02, das quais podem não estar "
+"disponíveis nos Manuais do Produto. É recomendável ler por completo estas "
+"Notas de Versão antes de instalar a Plataforma de Aplicativo do JBoss "
+"Enterprise 4.3.0.CP02."
 
 #. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
 #, no-c-format
 msgid "&HOLDER;"
 msgstr "&HOLDER;"
-

Added: projects/docs/enterprise/4.3.4/readme/pt-BR/Release_Notes_CP04.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pt-BR/Release_Notes_CP04.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/pt-BR/Release_Notes_CP04.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,3077 @@
+# translation of readme.po to Brazilian Portuguese
+# Language pt-BR translations for readme package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 12:19+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:9
+#, no-c-format
+msgid "Introduction"
+msgstr "Introdução "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:12
+#, no-c-format
+msgid ""
+"These release notes contain important information related to JBoss "
+"Enterprise Application Platform &VERSION;. New features, known problems, "
+"resources, and other current issues are addressed here."
+msgstr ""
+"Estas notas de versão contém informações importantes relacionadas à "
+"Plataforma de Aplicativo do JBoss Enterprise &VERSION;. Novos recursos, "
+"problemas conhecidos e outros problemas são demonstrados aqui."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:16
+#, no-c-format
+msgid "Overview"
+msgstr "Visão Geral"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:17
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform is the next evolutionary step in open "
+"source enterprise software. It is a powerful tool for developing rich, high "
+"performance, Web 2.0 applications on a pure Java Platform."
+msgstr ""
+"A Plataforma de Aplicativo do JBoss Enterprise é o próximo passo "
+"evolucionário em software empresarial de código aberto. É uma ferramenta "
+"poderosa para o desenvolvimento rico, alto desempenho e aplicativo da Web "
+"2.0 numa Plataforma Java Pura. "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:20
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform provides complete compatibility with "
+"existing J2EE 1.4 enterprise Java applications. At the same time, almost all "
+"the key features and components defined in the Java EE 5.0 specification are "
+"supported. So your new enterprise Java applications can take immediate "
+"advantage of the Java EE 5.0's significantly simpler POJO-based programming "
+"model."
+msgstr ""
+"A Plataforma de Aplicativo do JBoss Enterprise fornece uma completa "
+"compatibilidade com os aplicativos Java empresariais J2EE 1.4 existentes. Ao "
+"mesmo tempo, quase todos os recursos chaves e componentes definidos na "
+"especificação Java EE 5.0 são suportados. Desta forma, seus aplicativos Java "
+"empresariais podem tirar proveito imediato do Java EE 5.0 de modelo de "
+"programação de POJO-baseado simples, de forma significativa."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:23
+#, no-c-format
+msgid ""
+"Further, by integrating best-of-breed open source frameworks such as JBoss "
+"Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of "
+"innovations in the open source community. As well, JBoss Enterprise "
+"Application Platform is fully tested and supported by Red Hat, and is "
+"certified to work on many leading enterprise hardware and software products."
+msgstr ""
+"Além disso, a Plataforma tira vantagem das inovações da comunidade de código "
+"aberto pela integração dos frameworks de código aberto best-of-breed, como "
+"por exemplo: JBoss Seam, Hibernate, Tomcat e JBoss Cache. Assim como, a "
+"Plataforma de Aplicativo do JBoss Enterprise é inteiramente testada e "
+"suportada pela Red Hat, além de ser certificada para trabalhar em muitos "
+"hardware empresariais e produtos de software líderes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:26
+#, no-c-format
+msgid ""
+"All of which means you can develop your new application taking advantage of "
+"Java EE 5.0 technologies immediately and with the confidence of knowing it "
+"will remain forward-compatible with future versions of the JBoss Platform."
+msgstr ""
+"Tudo isto significa que você pode desenvolver seu novo aplicativo tirando "
+"vantagens imediatas das tecnologias Java EE 5.0, mantendo a transferência de "
+"compatibilidade nas versões futuras da Plataforma JBoss."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:32
+#, no-c-format
+msgid "New Features in JBoss Enterprise Application Platform 4.3"
+msgstr "Novos Recursos na Plataforma de Aplicativo do JBoss Enterprise 4.3"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:34 Release_Notes_CP04.xml:365
+#, no-c-format
+msgid "JBoss Messaging"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:35
+#, no-c-format
+msgid ""
+"In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
+"with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
+"messaging infrastructure for JBoss Enterprise Application Platform."
+msgstr ""
+"Na Plataforma de Aplicativo JBoss Enterprise 4.3, o JBoss MQ foi substituído "
+"pelo JBoss Messaging 1.4. O JBoss Messaging fornece uma infra-estrutura "
+"messaging de alto desempenho para a Plataforma de Aplicativo JBoss "
+"Enterprise."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:40
+#, no-c-format
+msgid "JBoss Web Services 2.0.1"
+msgstr "Serviços da Web do JBoss 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:41
+#, no-c-format
+msgid ""
+"JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
+"Platform 4.3 and will now provide a complete implementation of JAX-WS."
+msgstr ""
+"Os Serviços da Web do JBoss estão atualizados para 2.0.1 na Plataforma de "
+"Aplicativo JBoss Enterprise 4.3 e fornecerão, agora, uma implementação "
+"completa do JAX-WS."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:47
+#, no-c-format
+msgid "Component Versions"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:48
+#, no-c-format
+msgid ""
+"This section details the versions of the components which create the "
+"Enterprise Application Platform 4.3 that can be found in this Cumulative "
+"Patch release."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:53
+#, no-c-format
+msgid "JBoss Application Server 4.2.z"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:58
+#, no-c-format
+msgid "Hibernate Core 3.2.4.SP1.CP07"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:63
+#, no-c-format
+msgid "Hibernate Annotations 3.2.1.GA.CP03"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:68
+#, no-c-format
+msgid "Hibernate Entity Manager 3.2.1.GA_CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:73
+#, no-c-format
+msgid "JAF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:78
+#, no-c-format
+msgid "JBoss Cache 1.4.1.SP11"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:83
+#, no-c-format
+msgid "JBoss JAXR 1.2.0.SP2"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:88
+#, fuzzy, no-c-format
+msgid "JBoss Messaging 1.4.0.SP3-CP07"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:93
+#, fuzzy, no-c-format
+msgid "JBoss Remoting 2.2.2.SP11"
+msgstr "JBoss Remoting"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:98
+#, no-c-format
+msgid "JBoss Transactions 4.2.3.SP5.CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:103
+#, fuzzy, no-c-format
+msgid "JBoss Web 2.0.0-6.CP09"
+msgstr "Serviços da Web do JBoss 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:108
+#, fuzzy, no-c-format
+msgid "JBoss Web Services 2.0.1.SP2_CP05"
+msgstr "Serviços da Web do JBoss 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:113
+#, no-c-format
+msgid "JGroups 2.4.5"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:118
+#, no-c-format
+msgid "JSF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:123
+#, no-c-format
+msgid "Seam 1.2.1.AP"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:128
+#, no-c-format
+msgid "Xalan 2.7.0.patch02"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:134
+#, no-c-format
+msgid ""
+"The Enterprise Application Platform Server has been redefined for the "
+"enterprise market to a level where direct association to a community release "
+"can no longer be drawn."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:140
+#, no-c-format
+msgid "Installation and Migration Notes"
+msgstr "Instalação e Notas de Migração"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:141
+#, no-c-format
+msgid ""
+"This section contains information related to installing or upgrading to "
+"JBoss Enterprise Application Platform version &VERSION;, including hardware "
+"and platform requirements and prerequisites."
+msgstr ""
+"Esta seção contém informações relacionadas à instalação ou atualização à "
+"versão da Plataforma de Aplicativo do JBoss Enterprise &VERSION;, incluindo "
+"hardware, além de solicitações e pré-requisitos da plataforma."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:145
+#, no-c-format
+msgid "Installation Notes"
+msgstr "Notas de Instalação"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:146
+#, fuzzy, no-c-format
+msgid ""
+"You must have adequate disk space to install JDK and JBoss Enterprise "
+"Application Platform while also allowing enough space for your applications. "
+"You must have a working installation of JDK 1.5 or 1.6. For the latest "
+"information on supported Operating System / JVM combinations, supported "
+"Database platforms and current information on the revision level of included "
+"components, please refer to <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>. Refer to the "
+"installation guide available online from <ulink url=\"http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
+"instructions to install and verify JBoss Enterprise Application Platform."
+msgstr ""
+"Você deverá possuir o espaço de disco adequado para instalar o JDK e a "
+"Plataforma de Aplicativo JBoss Enterprise, enquanto permitindo espaço "
+"suficiente para seus aplicativos. Você deverá ter uma instalação de trabalho "
+"de JDK 1.5. Por favor consulte: <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>, para informações mais "
+"recentes do nível de revisão de componentes inclusos. Adicionado a isto, "
+"consulte o guia de instalação disponível online, a partir da página: <ulink "
+"url=\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"
+"\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</"
+"ulink>, para instruções mais detalhadas sobre instalação e verificação da "
+"Plataforma de Aplicativo JBoss Enterprise. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:151
+#, fuzzy, no-c-format
+msgid "Upgrading from JBoss Enterprise Application Platform 4.3.0.CP03"
+msgstr "Atualização a partir da Plataforma de Aplicativo JBoss Enterprise 4.3 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:153
+#, no-c-format
+msgid "Using CSP/JON"
+msgstr "Usando CSP/JON"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:154
+#, fuzzy, no-c-format
+msgid ""
+"Refer to <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
+"Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
+msgstr ""
+"Consulte <ulink url=\"https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> para instruções sobre instalação de um Patch "
+"Cumulativo."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:164
+#, no-c-format
+msgid "Important Notes"
+msgstr "Notas Importantes"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:166
+#, no-c-format
+msgid "Running the example Seam Applications"
+msgstr "Rodando o exemplo dos Aplicativos Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:169
+#, no-c-format
+msgid ""
+"It is recommended to run the example Seam applications that are included "
+"with the documentation using the production configuration. Using another "
+"configuration may result in memory issues. Note that the default "
+"configuration for the server to start with, if no other configuration is "
+"specified, is the production configuration."
+msgstr ""
+"É recomendável rodar o exemplo dos aplicativos Seam, que estão incluídos na "
+"documentação, usando a configuração de produção. O uso de outra configuração "
+"poderá resultar em problemas de memória. Perceba que a configuração padrão "
+"para o servidor inicializar, caso não haja outra configuração especificada, "
+"é a configuração de produção."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:173
+#, no-c-format
+msgid ""
+"To avoid memory issues, adjust the memory settings before deploying the "
+"applications. You can do this by updating <literal>JAVA_OPTS</literal> "
+"settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
+"conf</filename> with these recommended values:"
+msgstr ""
+"Para evitar problemas de memória, ajuste as configurações de memória antes "
+"de implementar os aplicativos. Você pode realizar isto atualizando as "
+"configurações <literal>JAVA_OPTS</literal>  no arquivo <filename>JBOSS_DIST/"
+"jboss-as/server/production/run.conf</filename>, com estes valores "
+"recomendados:"
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:175
+#, no-c-format
+msgid "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+msgstr "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:178
+#, no-c-format
+msgid ""
+"Refer to the \"Seam Reference Guide\" included in the documentation set "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for "
+"important information regarding the deployment of Seam examples and detailed "
+"information on developing applications using Seam."
+msgstr ""
+"Consulte o \"Guia de Referência Seam\" incluído no conjunto de documentação "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>), para "
+"informações importantes a respeito da implementação de exemplos Seam e "
+"informações detalhadas no desenvolvimento dos aplicativos usando Seam."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:186
+#, no-c-format
+msgid "Default Security Settings"
+msgstr "Configurações de Segurança Padrão"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:189
+#, no-c-format
+msgid ""
+"If you are using the rpm, or the zip distribution, please note that by "
+"default, authentication is enabled and no user accounts are set up. This is "
+"done to prevent unauthorized access to various services of JBoss AS. Please "
+"refer to the Installation Guide, or see <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
+"ulink> for information on how to make the services accessible again."
+msgstr ""
+"Caso você esteja usando o rpm ou a distribuição comprimida, note que pelo "
+"padrão, a autenticação é ativada e nenhuma conta de usuário é criada. Isto é "
+"feito para prevenir o acesso não autorizado a vários serviços do JBoss AS. "
+"Por favor, refira-se ao Guia de Instalação , ou consulte: <ulink url="
+"\"http://kbase.redhat.com/faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/"
+"faq/FAQ_107_9963.shtm</ulink>, para informações de como realizar os serviços "
+"acessíveis novamente."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:194
+#, no-c-format
+msgid "Embedded Hypersonic Database"
+msgstr "Banco de Dados Hypersonic Incorporado"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:197
+#, no-c-format
+msgid ""
+"Hypersonic SQL provides default \"out of the box\" database functionality "
+"for evaluation and development use only. It is NOT recommended or supported "
+"as a production-use database. Technical support is not available for this "
+"component, and while we are happy to accept bugs filed against this "
+"component, we do not make any commitment to fix them within a specific "
+"timeframe."
+msgstr ""
+"O Hypersonic SQL fornece a função de banco de dados \"fora da caixa\" "
+"padrão, apenas para o uso de desenvolvimento e avaliação. Ele NÃO é "
+"recomendável ou suportado como um banco de dados de uso de produção. O "
+"suporte técnico não é disponível para este componente, e enquanto estamos "
+"felizes em aceitar bugs arquivadas em referência a este componente, não nos "
+"responsabilizamos em corrigí-las, em um determinado período de tempo. "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:202
+#, no-c-format
+msgid "Source Files"
+msgstr "Fonte de Arquivos"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:204
+#, no-c-format
+msgid "SRPMs"
+msgstr "SRPMs"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:208
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:212
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:216
+#, no-c-format
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:223
+#, no-c-format
+msgid "Source ZIP"
+msgstr "Fonte Comprimida"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:228
+#, fuzzy, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP04.zip"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP02.zip"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:237
+#, no-c-format
+msgid "Product Support and License Website Links"
+msgstr "Suporte do Produto e Licença de Links do Website"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:241
+#, no-c-format
+msgid "Support Processes"
+msgstr "Processos de Suporte"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:243
+#, no-c-format
+msgid "http://www.redhat.com/support/process/"
+msgstr "http://www.redhat.com/support/process/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:248
+#, no-c-format
+msgid "Production Support Scope of Coverage"
+msgstr "Escopo de Suporte de Produção de Cobertura"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:252
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/production"
+msgstr "http://www.redhat.com/support/policy/soc/production"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:258
+#, no-c-format
+msgid "Production Support Service Level Agreement"
+msgstr "Acordo do Nível de Serviço de Suporte de Produção"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:263
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/production/"
+msgstr "http://www.redhat.com/support/policy/sla/production/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:268
+#, no-c-format
+msgid "Developer Support Scope of Coverage"
+msgstr "Escopo do Suporte do Desenvolvedor de Cobertura"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:273
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/developer/"
+msgstr "http://www.redhat.com/support/policy/soc/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:278
+#, no-c-format
+msgid "Developer Support Service Level Agreement"
+msgstr "Acordo do Nível do Serviço de Suporte do Desenvolvedor"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:283
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/developer/"
+msgstr "http://www.redhat.com/support/policy/sla/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:288
+#, no-c-format
+msgid "Product Update and Support Policy by Product"
+msgstr "Atualização do Produto e Política de Suporte pelo Produto"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:293
+#, no-c-format
+msgid "http://www.redhat.com/security/updates/jboss_notes/"
+msgstr "http://www.redhat.com/security/updates/jboss_notes/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:298
+#, no-c-format
+msgid "JBoss End User License Agreement"
+msgstr "Acordo da Licença do Usuário Final do JBoss"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:303
+#, no-c-format
+msgid "http://www.redhat.com/licenses/jboss_eula.html"
+msgstr "http://www.redhat.com/licenses/jboss_eula.html"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:309 Release_Notes_CP04.xml:904
+#, no-c-format
+msgid "Documentation"
+msgstr "Documentação"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:312
+#, no-c-format
+msgid ""
+"Refer to the index.html file in the documentation directory for a list of "
+"included documentation."
+msgstr ""
+"Consulte o arquivo index.html no diretório da documentação, para a obtenção "
+"da lista dedocumentação inclusa."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:315
+#, no-c-format
+msgid ""
+"In the zip distribution, documentation for the Platform and its individual "
+"components is distributed in a separate zip file, <filename>jboss-eap-docs-"
+"&lt;version&gt;.zip</filename>."
+msgstr ""
+"Numa distribuição comprimida, a documentação para a Plataforma e seus "
+"componentes individuais é distribuída num arquivo comprimido separado: "
+"<filename>jboss-eap-docs-&lt;version&gt;.zip</filename>."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:319
+#, no-c-format
+msgid ""
+"On a Linux system, the documentation is found in two rpms that will need to "
+"be installed manually. These rpms are <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename>, and <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. For help with installing rpm packages on Red Hat "
+"Enterprise Linux, please refer to the Red Hat Knowledge base article located "
+"at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+msgstr ""
+"Num sistema Linux, a documentação é encontrada em dois rpms que precisarão "
+"ser instalados manualmente. Estes rpms são <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename> e <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. Por favor refira-se ao <ulink url=\"http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm\">http://kbase.redhat.com/faq/FAQ_35_198."
+"shtm</ulink>, para auxílio na instalação dos pacotes rpm, na Red Hat "
+"Enterprise Linux."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:326
+#, fuzzy, no-c-format
+msgid ""
+"<filename>Installation Guide</filename> explains how to install and verify "
+"the installation of JBoss Enterprise Application Platform using different "
+"installation modes."
+msgstr ""
+"<filename>Installation Guide</filename>: explica como instalar e verificar a "
+"instalação da Plataforma de Aplicativo JBoss Enterprise, usando os modos de "
+"instalação diferente."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:331
+#, no-c-format
+msgid ""
+"<filename>Getting Started</filename> details the directory structure of the "
+"platform and a quick tour of the Application Server and different "
+"configuration sets and services. Using a simple web application it "
+"illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
+"the JSF and EJB3 components."
+msgstr ""
+"<filename>Getting Started</filename>: detalha a estrutura do diretório de "
+"uma plataforma e uma descrição resumida do servidor do Aplicativo, além dos "
+"conjuntos e serviços de configurações diferentes. Usando um aplicativo da "
+"web simples, isto ilustra o uso dos componentes e como usar o Seam para "
+"integração do JSF e dos componentes EJB3."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:336
+#, no-c-format
+msgid ""
+"<filename>Server Configuration Guide</filename> explains all administrative "
+"and configuration functions in detail."
+msgstr ""
+"<filename>Server Configuration Guide</filename>: explica todas as funções "
+"administrativas e de configuração detalhadamente."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:342
+#, no-c-format
+msgid ""
+"Updated versions of the documentation with errata and additional "
+"information, example application code, as well as the most recent version of "
+"the release notes may be accessed via the web from <ulink url=\"http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+msgstr ""
+"As versões atualizadas da documentação com errata e informação adicional, o "
+"exemplo do código do aplicativo, assim como a versão mais recente das notas "
+"de versão poderão ser acessadas através da web, a partir do <ulink url="
+"\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"
+"\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</"
+"ulink>."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:357
+#, no-c-format
+msgid "Issues fixed in this release"
+msgstr "Problemas solucionados nesta versão"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:361
+#, no-c-format
+msgid "Following is a list of issues fixed in this release:"
+msgstr "Segue abaixo, a lista de problemas solucionados nesta versão:"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:369
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1615\">JBPAPP-1615</"
+"ulink>: The JBoss Messaging component of the Enterprise Application Platform "
+"has been upgraded to version 1.4.0.SP3-CP07. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:374
+#, no-c-format
+msgid ""
+"There was an issue with the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method whereby the method delegates checking to "
+"the <classname>ResourceManager</classname> <varname>serverID</varname>. This "
+"instigates the case where the <methodname>xasess2.start(xid, TMJOIN)</"
+"methodname> method is called and the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method returns true but the resource manager does "
+"not hold the transaction state required to perform a <code>TMJOIN</code>. "
+"Further to this when a session is closed the <methodname>SessionAspect."
+"handleClose()</methodname> method is called, yet the <code>tx</code> was "
+"removed from the transaction manager meaning it is no longer in the "
+"<code>conn1</code> resource manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:377
+#, no-c-format
+msgid ""
+"To correct this both the <methodname>MessagingXAResource.isSameRM</"
+"methodname> method and <classname>ResourceManager</classname> have the same "
+"<code>serverID</code> and the same map of transactions, ensuring that if the "
+"<classname>ResourceManager</classname> was to ever return true, the call to "
+"<methodname>start(TMJOIN)</methodname> would correctly succeed. To note is "
+"that the transaction will rollback at completion time and any message "
+"delivered in the <code>tx</code> will be redelivered."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:382
+#, no-c-format
+msgid ""
+"Client connection parameters were not being passed to the JBoss Remoting "
+"layer, leaving parameters such as <varname>validatorPingPeriod</varname> and "
+"<varname>validatorTimeout</varname> to be used with default values within "
+"Remoting instead of the configured values. In correcting this issue, the "
+"<filename>JMSRemotingConnection.java</filename> file has been updated so "
+"that when the <methodname> client.addConnectionListener</methodname> method "
+"is called within the <methodname>addConnectionListener</methodname> and "
+"<methodname>addPlainConnectionListener</methodname> methods, it also passes "
+"the configured parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:387
+#, no-c-format
+msgid ""
+"The <literal>default</literal> profile for JBoss without any reconfiguration "
+"uses the <classname>ClusteredConnectionFactory</classname> with a non-"
+"clustered post-office, however warnings would be logged about this behavior "
+"when the log messages should be reduced from a <varname>WARN</varname> level "
+"to an <varname>INFO</varname> level. The upgrade to this version of JBoss "
+"Messaging sees this implemented within the log."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:392
+#, no-c-format
+msgid ""
+"<classname>ClusterViewUpdateTest</classname> was broken and did not work "
+"correctly in previous releases with the cause being that the expected time "
+"until failure detection for some clustering tests was too long. In order to "
+"correct this the values for <varname>validatorPingPeriod</varname> and "
+"<varname>validatorPingTimeout</varname> have been changed to be 2 seconds "
+"each, combining to 4 seconds as the total time until expected failure "
+"detection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:397
+#, no-c-format
+msgid ""
+"Client connection parameters were not passed to the JBoss Remoting layer, "
+"forcing Remoting to use default values instead of user configured values. In "
+"order to use the correct values, <filename>JMSRemotingConnection.java</"
+"filename> has been updated so that the <methodname>Client."
+"addConnectionListener</methodname> method is used with <varname>listener</"
+"varname> and <varname>serverLocator.gerParameters()</varname> as parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:402
+#, no-c-format
+msgid ""
+"Messages which are scheduled for delivery in the future were not being "
+"removed correctly when the <methodname>removeAllMessages()</methodname> "
+"method was being called, causing the messages to be re-queued as soon as the "
+"application server or queue is restarted. <filename>ChannelSupport.java</"
+"filename> has been updated to import the <filename>TimeoutExt</filename> "
+"library in order to cast the timeout value to <filename>TimeoutExt</"
+"filename> in order to obtain the reference value via the <methodname>get "
+"TimeoutTarget()</methodname> method. With this new reference value "
+"information, the scheduled messages can be correctly removed from the queue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:407
+#, no-c-format
+msgid ""
+"There was an occurrence where a user may deploy a clustered queue in a "
+"single node instead of in all the nodes and the failover process would not "
+"work because of this. When this occurred an <exceptionname>Illegal "
+"StateException</exceptionname> would be generated, however this was not "
+"considered enough of a prominent warning about not deploying clustered "
+"queues correctly. <filename>Messaging PostOffice.java</filename> has now "
+"been updated to log a warning which outlies that clustered destinations must "
+"be deployed on all nodes of a cluster, instead of generating an "
+"<exceptionname>Illegal StateException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:412
+#, no-c-format
+msgid ""
+"The <classname>Client</classname>, <classname>SecurityAspect.check()</"
+"classname> and <classname>ServerConnection FactoryEndpoint</classname> "
+"needed to be able to obtain TLC within a privileged block, otherwise an "
+"<exceptionname>Access ControlException</exceptionname> is produced. To fix "
+"this bug, the <methodname>settle</methodname>, <methodname>gettable</"
+"methodname> and other TLC methods have been set within security blocks; this "
+"prevents access denied exceptions from <classname>Client</classname>, "
+"<classname>SecurityAspect.check()</classname> and "
+"<classname>ServerConnection FactoryEndpoint</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:417
+#, no-c-format
+msgid ""
+"The logging of actions within JBoss Messaging did not include the logging of "
+"messages when they are moved to the expiry or dead letter queues as this was "
+"only logged at trace level. In order to add this enhanced level of logging, "
+"the <filename>ClientConsumer.java</filename> file has been updated to log "
+"warning messages and debug information pertaining to the move of messages to "
+"the expiry or dead letter queues; <filename>Server SessionEndpoint.java</"
+"filename> has also been updated in the same mannor."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:422
+#, no-c-format
+msgid ""
+"There was an error when a message was received under a X tx and the JBoss "
+"Messaging XAResource is prepared but not committed, a message could be "
+"received by another consumer in another transaction while the first is still "
+"in progress. The correct behavior is for JBoss Messaging to hold the message "
+"until the associated transaction is committed or rolled back, enabling "
+"duplication of message deliveries to be avoided. In the <filename>Delivery."
+"java</filename> file, messages are now marked with a boolean value detailing "
+"if they are for delivery with a X transaction and if this transaction is "
+"prepared and <filename>SimpleDelivery.java</filename> now implements this "
+"new information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:427
+#, no-c-format
+msgid ""
+"The <methodname>shutdownNow()</methodname> method was not synchronized and "
+"may cause a <exceptionname>NoSuchElementException</exceptionname> during "
+"runtime as a result. A synchronization block has been placed around the "
+"<methodname>shutdownNow()</methodname> code within "
+"<filename>OrderedExecutorFactory.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:432
+#, no-c-format
+msgid ""
+"There was an issue with the <classname>org.jboss.jms.server.messagecounter."
+"MessageCounter</classname> class not being able to be serialized as it "
+"caused an <exceptionname>UndeclaredThrowableException</exceptionname>. "
+"<filename>MessageCounter.java</filename> has been updated to now import and "
+"implement the <literal>Serializable</literal> library and be given a "
+"<varname>serialVersionUID</varname>, allowing the <classname>org.jboss.jms."
+"server.messagecounter.MessageCounter</classname> class to be serializable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:437
+#, no-c-format
+msgid ""
+"When the methods <methodname>unregisterSucker()</methodname> or "
+"<methodname>registerSucker()</methodname> was called a "
+"<exceptionname>ConcurrentModificationException</exceptionname> would be "
+"generated by the time the <literal>HashSet</literal> containing the "
+"<literal>suckers</literal> was iterated. The issue would present itself on "
+"clusters with a magnitude of nodes (for instance it appeared on a 8 node "
+"cluster but not a 4 node cluster). This bug was corrected by creating an "
+"iterator that used a private set of <literal>suckers</literal> for iteration "
+"through the <literal>HashSet</literal> of <literal>suckers</literal> in "
+"order to avoid the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:442
+#, no-c-format
+msgid ""
+"The bridge within JBoss Messaging would only retry connection creation to a "
+"remote destination after startup and if the remote provider was not "
+"available at startup, the bridge would fail to start. The <filename>Bridge."
+"java</filename> and <filename>BridgeService.java</filename> files have "
+"undergone extensive modification and now the <literal>factory</literal> is "
+"set to the <literal>bridge</literal> which undertakes the lookup itself "
+"instead of looking up the destinations."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:452
+#, fuzzy, no-c-format
+msgid "JBoss Cache"
+msgstr "Jboss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:456
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
+"ulink>: The JBoss Cache component of the Enterprise Application Platform has "
+"been upgraded to version 1.4.1.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:461
+#, no-c-format
+msgid ""
+"The <classname>JDBCCacheLoader</classname> implementation did not work with "
+"Sybase as it would try to set a null <varname>BLOB</varname> column which is "
+"unsupported within Sybase. To correct this the <filename>JDBCCacheLoader."
+"java</filename> file has been updated so that the Sybase Driver sets a null "
+"<varname>LONGVARBINARY</varname> value, allowing the "
+"<classname>JDBCCacheLoader</classname> implementation to work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:466
+#, no-c-format
+msgid ""
+"The <classname>JDBCExtCacheLoader</classname> did not handle persistent "
+"state transfer correctly since the <methodname>JDBCExtCacheLoader.storeState"
+"()</methodname> method would use available bytes on the "
+"<classname>MarshalledValueInputStream</classname> rather than on the "
+"<classname>ByteArrayInputStream</classname> when storing the persistent "
+"state. This was an issue because the <classname>MarshalledValueInputStream</"
+"classname> always returns a null value, meaning the persistent state was "
+"never written. In fixing this issue the <filename>JDBCExtendedCacheLoader."
+"java</filename> file has been modified so that it specifies to check for "
+"available space on the <classname>ByteArrayInputStream</classname>."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:476
+#, no-c-format
+msgid "JBoss Remoting"
+msgstr "JBoss Remoting"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:480
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
+"ulink>: The JBoss Remoting component of the Enterprise Application Platform "
+"has been upgraded to version 2.2.2.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:485
+#, no-c-format
+msgid ""
+"The <methodname>ConnectionValidator.run()</methodname> method had the "
+"ability to be called by a user before the private method "
+"<methodname>ConnectionValidator.start()</methodname> was called, resulting "
+"in the <varname>clientInvoker</varname> and <varname>timer</varname> fields "
+"being set to null and generating a <exceptionname>NullPointerException</"
+"exceptionname>. Within the <filename>ConnectionValidator.java</filename> "
+"file the fields are now checked to see if they are null upon execution of "
+"the <methodname>ConnectionValidator.run()</methodname> method, one or both "
+"are then an <exceptionname>IllegalStateException</exceptionname> is "
+"displayed to the user outlining that <methodname>ConnectionValidator.run()</"
+"methodname> should not be called directly but "
+"<methodname>addConnectionListener()</methodname> should be used instead."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:490
+#, no-c-format
+msgid ""
+"Two bugs existed within the <methodname>org.jboss.remoting.marshal."
+"MarshallerLoaderHandler.loadClassBytes()</methodname> method that prohibited "
+"remote classloading to work correctly with isolated EARs. The first was that "
+"a while loop in the code needed a break and the second was that the call to "
+"the <methodname>org.jboss.mx.loading.LoaderRepository.getCachedClass()</"
+"methodname> method should have been a general call to "
+"<methodname>LoaderRepository.loadClass()</methodname>. These two issues have "
+"been rectified with this Remoting update, allowing remote classloading to "
+"function correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:495
+#, no-c-format
+msgid ""
+"A bug existed within the Remoting component by which the RemotingClassLoader "
+"would always attempt to load a class over the network first if remote "
+"classloading was enabled, leading to conflicts if the class was available "
+"locally before. The code has been corrected to check locally first before "
+"looking remotely."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:500
+#, no-c-format
+msgid ""
+"The <classname>ServerInvokerCallbackHandler</classname> class would become "
+"unresponsive when calling the <methodname>BlockingCallbackStore.add()</"
+"methodname> method after locking the callback field with a true responce "
+"from the <methodname>persistCallback()</methodname> method. This would occur "
+"because the <methodname>BlockingCallbackStore.getNext()</methodname> needed "
+"to control the lock on the callback field to break the waiting period, "
+"however this could not be achieved because of the wait period. To fix this "
+"issue the call to the <methodname>BlockingCallbackStore.add()</methodname> "
+"method has been removed as it was an unnecessary step."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:505
+#, no-c-format
+msgid ""
+"The <classname>HTTPClientInvoker</classname> did not support Beginner's All-"
+"purpose Symbolic Instruction Code (BASIC) authentication for proxies when "
+"the proxy was configured through system property options of <methodname>http."
+"proxyHost</methodname> and <methodname>http.proxyPort</methodname>. The "
+"issue appears because the <classname>HTTPClientInvoker</classname> would not "
+"check for the existence of these options and in tern it would never create a "
+"<methodname>Proxy-Authorization</methodname> request header, which is "
+"necessary for normal operation. To fix this the "
+"<classname>HTTPClientInvoker</classname> has been modified to check for the "
+"existence of the <methodname>http.proxyHost</methodname> option and if it "
+"detects its use, creates a <methodname>Proxy-Authorization</methodname> "
+"request header."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:510
+#, no-c-format
+msgid ""
+"<classname>HTTPClientInvoker</classname> would generate a "
+"<exceptionname>NullPointerException</exceptionname> when the HTTP server "
+"returned an error code without any content and then the <methodname>java.net."
+"HttpUrlConnection.getInputStream()</methodname> method returned a null "
+"value. In order to improve control over this behavior, the new variable "
+"<varname>UNMARSHAL_NULL_STREAM</varname> has been added to the "
+"<classname>HTTPClientInvoker</classname>. If this variable is set to true "
+"(the default value) the default behavior is executed, however if it is set "
+"to false the call to the <methodname>UnMarshaller.read()</methodname> is "
+"skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:515
+#, no-c-format
+msgid ""
+"Within the <classname>InvokerRegistry</classname> an error existed "
+"associated with the sequencing of events and <classname>serverLocators</"
+"classname> would return a null on occasion. To correct this race condition, "
+"the sequencing of events within the <classname>InvokerRegistry</classname> "
+"has been rearranged so that references to "
+"<classname>transportClientFactoryClasses</classname> and "
+"<classname>clientLocators</classname> are governed by <classname>clientLock</"
+"classname> and references to <classname>transportServerFactoryClasses</"
+"classname>, <classname>serverLocators</classname>, and "
+"<classname>registeredLocators</classname> are governed by "
+"<classname>serverLock</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:520
+#, no-c-format
+msgid ""
+"A bug existed where the value in the client configuration map of the "
+"<classname>ConnectionValidator</classname> would be ignored when the "
+"overloaded <methodname>org.jboss.remoting.Client</methodname> method was "
+"called and the <varname>DEFAULT_PING_PERIOD</varname> variable value was "
+"placed into the metadata map passed to the <classname>ConnectionValidator</"
+"classname>. This has been corrected by updating <classname>org.jboss."
+"remoting.Client.addConnectionListener</classname> so that "
+"<varname>DEFAULT_PING_PERIOD</varname> is only passed if the value of "
+"<varname>VALIDATOR_PING_PERIOD</varname> within the client's configuration "
+"map has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:525
+#, no-c-format
+msgid ""
+"<classname>ConnectionValidator</classname> may become unresponsive then the "
+"<methodname>run()</methodname> method is executed and utilizes the "
+"<varname>lock</varname> variable. The methods within the <methodname>run()</"
+"methodname> method are meant to time out so that the <varname>lock</varname> "
+"variable can become available to the <methodname>notifyListeners()</"
+"methodname> in the event of a network failure; however <methodname>run()</"
+"methodname> may execute again before <methodname>notifyListeners()</"
+"methodname> can. The synchronization on the <varname>lock</varname> variable "
+"has been modified to avoid this issue to enable correct operation."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:530
+#, no-c-format
+msgid ""
+"During occurrences of the server being under heavy load, an "
+"<exceptionname>IllegalStateException</exceptionname> would occur within the "
+"<methodname>ConnectorValidator.run()</methodname> method because further "
+"synchronization on the <varname>lock</varname> variable was necessary. This "
+"issue was fixed during the rectification of the above problem."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:535
+#, no-c-format
+msgid ""
+"A synchronization error within the <classname>MarshalFactory</classname> was "
+"allowing a subsystem to add a marshaller at the same time as EJB3 was trying "
+"to extract one causing users to receive an "
+"<exceptionname>InvalidMarshallingResource</exceptionname> exception; this "
+"also applied to unmarshallers. The error has been fixed by updating the "
+"<filename>jboss-remoting.jar</filename> file to include synchronized static "
+"Maps within the <classname>MarshalFactory</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:540
+#, no-c-format
+msgid ""
+"The <classname>SocketServerInvoker</classname> had an issue when shutting "
+"down <varname>ServerThreads</varname> causing a user to possibly receive an "
+"invocation to a closed <classname>SocketServerInvoker</classname> on the "
+"client side, causing an <exceptionname>InvalidStateException</"
+"exceptionname>. Allowing this exception would cause a clustered EJB3 system "
+"to generate a <exceptionname>UndeclaredThrowableException</exceptionname> "
+"instead of trying alternative servers. To allow for alternatives to be "
+"attempted, an optional behavior of allowing the "
+"<classname>MicroRemoteClientInvoker</classname> to interpret an "
+"<exceptionname>InvalidStateException</exceptionname> as a "
+"<exceptionname>CannotConnectException</exceptionname>, allowing for other "
+"servers to be attempted."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:550
+#, fuzzy, no-c-format
+msgid "JBoss Web"
+msgstr "Jboss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:554
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1493\">JBPAPP-1493</"
+"ulink>: An error would be shown on occasion by <emphasis>Internet Explorer</"
+"emphasis> because xml content would not be sent when <emphasis>PROPFIND</"
+"emphasis> requests were being used. This has been fixed by creating a new "
+"method within <filename>WebdavServlet.java</filename> that overrides the "
+"<methodname>DefaultServlet</methodname> implementation for servlet request "
+"processing and testing for input before launching the "
+"<methodname>DocumentBuilder</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:559
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1470\">JBPAPP-1470</"
+"ulink>: When using APR (Apache Portable Runtime) on any operating system "
+"other than those which use the Linux Kernal 2.4 or newer, the "
+"<parameter>deferAccept</parameter> option would be set to false in the "
+"<methodname>AprEndpoint</methodname>. This may lead to a "
+"<exceptionname>NullPointerException</exceptionname> as the "
+"<methodname>accepter</methodname> thread starts to process a request while "
+"also calling for a <methodname>poller</methodname> before initialization. "
+"The issue has been resolved by moving the <methodname>acceptor</methodname> "
+"threads to being executed last when starting the <methodname>AprEndpoint</"
+"methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:564
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1334\">JBPAPP-1334</"
+"ulink>: The JBoss Web component of the Enterprise Application Platform has "
+"been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:569
+#, no-c-format
+msgid ""
+"If a war deployment included its own version of <filename>xalan.jar</"
+"filename> and <filename>xercesImpl.jar</filename> in <filename>WEB-INF/lib</"
+"filename>, the JBossWeb servlet container classloader returns JBoss provided "
+"version of the <literal>SAXParser</literal> from "
+"<methodname>SAXParserFactory.newInstance().newSAXParser()</methodname> "
+"rather than the version provided in the war deployment. To fix this bug the "
+"<filename>WebAppClassLoader.java</filename> has been updated to ensure the "
+"correct parser is used."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:579
+#, no-c-format
+msgid "JBoss Web Services"
+msgstr "Serviços da Web do JBoss"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:583
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1560\">JBPAPP-1560</"
+"ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component "
+"of the Enterprise Application Platform has been upgraded to version 2.1.4."
+"patch01. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:588
+#, no-c-format
+msgid ""
+"The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package "
+"contains classes to optimize field and method access by dynamically "
+"generating classes. Within the <classname>Injector</classname> class there "
+"is a <literal>HashMap</literal> value that is wrapped within a "
+"<literal>WeakReference</literal> however since there is only a "
+"<literal>WeakReference</literal> to the <classname>Injector</classname> "
+"class within this, the <literal>HashMap</literal> is garbage collected. To "
+"fix this the reference has been changed to a <literal>StrongReference</"
+"literal> and in order to maintain the original requirements, the "
+"<classname>Injector</classname> is now passed a reference to the ClassLoader "
+"instead of containing one specifically."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:595
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1210\">JBPAPP-1210</"
+"ulink>: The JBoss Web Services component of the Enterprise Application "
+"Platform has been upgraded to version 2.0.1.SP2_CP05. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:600
+#, no-c-format
+msgid ""
+"When deploying JBoss Web Services within Enterprise Application Platform "
+"without internet access, <classname>JBossWSEntityResolver</classname> would "
+"not resolve any schemas causing Web Services for Remote Portlets (WSRP) to "
+"produce an error. This issue has been fixed by modifying "
+"<classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader."
+"java</filename> to resolve schemas locally when an internet connection is "
+"unavailable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:605
+#, no-c-format
+msgid ""
+"WSProvide would ignore a <literal>SOAPBinding</literal> declaration "
+"specified in the EJB3 stateless session bean. To correct this and allow "
+"<literal>SOAPBinding</literal> to work as expected the following files have "
+"been modified: <filename>WSDLGenerator.java</filename>, "
+"<filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, "
+"<filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</"
+"filename> and <filename>WSDL11Writer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:610
+#, no-c-format
+msgid ""
+"The component <emphasis>Xerces</emphasis> of JBoss Web Services has a "
+"feature that optimizes the parsing of messages called <methodname>Deffered "
+"Node Expansion</methodname>.This defers node expansion until the nodes are "
+"accessed, improving performance where not all nodes need to be visited. "
+"However memory overheads are increased, which can be considerable for large "
+"messages."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:613
+#, no-c-format
+msgid ""
+"This release grants the user an option to disable the <methodname>Deffered "
+"Node Expansion</methodname> feature and have all nodes expand. To achieve "
+"this the following system property needs to be set:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:616
+#, no-c-format
+msgid "-Dorg.jboss.ws.disable_deferred_node_expansion=true"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:619
+#, no-c-format
+msgid ""
+"A regression with <literal>TCK5 SAAJ</literal> in the <classname>SOAPBody</"
+"classname> class was introduced with a fix to a previous bug and this has "
+"now been rectified by modifying the <filename>SOAPBodyImpl.java</filename> "
+"file to perform a <code>break</code> after assigning the "
+"<varname>childElement</varname> property."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:624
+#, no-c-format
+msgid ""
+"The end points for a <literal>transport-guarantee</literal> that is set to "
+"be confidential would see an attempt to exactly map the URL pattern in the "
+"WSDL. However since the servlet and security constraints will not be defined "
+"exactly the same a bug occurred whereby JBoss Web Services would assume the "
+"<literal>transport-guarantee</literal> was not confidential when generating "
+"the address, causing the WSDL to be generated with a http address. The "
+"<literal>transport-guarantee</literal> would still be enforced by JBoss Web "
+"Services as confidential but the WSDL would contain the wrong address, "
+"leading to clients attempting to connect to an incorrect address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:627
+#, no-c-format
+msgid ""
+"In order to rectify this occurrence, the <filename>MetaDataBuilder.java</"
+"filename> file has been modified so that when testing the servlet pattern it "
+"also tests correctly for the security constraint instead of assuming both "
+"with be of the same value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:632
+#, no-c-format
+msgid ""
+"When creating messages in SOAP 1.2 without attachments, the "
+"<classname>SOAPMessageImpl</classname> class sets the <varname>contentType</"
+"varname> variable to <literal>text/xml</literal>, which was incorrect. This "
+"has now been rectified by amending <varname>contentType</varname> to use the "
+"value <literal>application/soap+xml</literal> by adding the "
+"<methodname>getSAPContentType()</methodname> method to "
+"<filename>SOAPMessageImpl.java</filename> and updating "
+"<filename>DispatchImpl.java</filename> to correctly reference the SOAP "
+"message context."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:638
+#, no-c-format
+msgid ""
+"Deployments of JAX-WS nature would fail for JBoss AOP instrumented "
+"endpoints, generating an <exceptionname>IllegalAnnotationsException</"
+"exceptionname> as JBoss Web Services attempted to process the JBoss AOP "
+"methods. <filename>JAXWSMetaDataBuilder.java</filename> has been updated to "
+"mark JBoss AOP methods as synthetic which allows them to be skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:643
+#, no-c-format
+msgid ""
+"WSDL dynamic address replacement was not working correctly in previous "
+"versions of the Enterprise Application Platform since port and protocol "
+"numbers were not being considered. The <filename>WSDLRequestHandler.java</"
+"filename> file has been modified to use a new URL and protocol instead of "
+"the original URL and protocol in order to use the dynamically generated port "
+"and protocol numbers."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:648
+#, no-c-format
+msgid ""
+"In converting WSDL to Java, anonymous types that are nested within anonymous "
+"types generated a JAX-RPC mapping that did not match the source. The "
+"<filename>MappingFileGeneratorHelper.java</filename> file has been corrected "
+"to ensure that the generated mapping matches the source of the information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:653
+#, no-c-format
+msgid ""
+"JAAS certificate authentication support was not supported in the JBoss Web "
+"Services Security implementation, meaning that authentication via this "
+"method could not take place based on the certificate the client used to sign "
+"the message. Support for this has been added to JBoss Web Services and in "
+"tern the Enterprise Application Platform with this component upgrade."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:658
+#, no-c-format
+msgid ""
+"When the default port for a protocol was being used within JBoss Web "
+"Services, the port number still appeared at the end of the URL even though "
+"this was unnecessary. In order to remove the port number from the end of the "
+"URL, the <filename>MetaDataBuilder.java</filename> has been modified for "
+"each individual service that uses the default port."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:663
+#, no-c-format
+msgid ""
+"When JBoss Web Services is being used as a client, the information within "
+"the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not "
+"cleared for incoming client calls. In order to fix this the call to "
+"<methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the "
+"<classname>MessageContextAssociation</classname> class and is executed once "
+"the last message has been processed. The files that have been updated in "
+"order to incorporate the fix are: <filename>DOMUtils.java</filename>, "
+"<filename>XMLContent.java</filename>, <filename>ProviderImpl.java</"
+"filename>, <filename>MessageContextAssociation.java</filename>, "
+"<filename>MessageContextJAXWS.java</filename> and "
+"<filename>RequestHandlerImpl.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:668
+#, no-c-format
+msgid ""
+"When the <varname>webServiceHost</varname> property was not set, the <ulink "
+"url=\"http://localhost:8080/jbossws/services \">http://localhost:8080/"
+"jbossws/services</ulink> page presented the host name as "
+"<exceptionname>jbossws.undefined.host</exceptionname>. A "
+"<methodname>createAddress</methodname> method has been added to "
+"<filename>ContextServlet.java</filename> which dynamically updates the WSDL "
+"and XSD files with the address from the request URL before displaying "
+"information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:674
+#, no-c-format
+msgid ""
+"The JBoss Web Services upgrade 2.0.1.SP2_CP05 also includes the security fix "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>, discussed in the Security Issue section."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:683
+#, no-c-format
+msgid "JBoss Seam"
+msgstr "Jboss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:687
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1553\">JBPAPP-1553</"
+"ulink>: When the <methodname>parseRequest()</methodname> method of the "
+"<classname>org.jboss.seam.web.MultipartRequest</classname> class uploaded a "
+"large file, there were occurrences when this would cause an endless loop and "
+"use 100% of the computers CPU. In order to break out of the loop, a "
+"<varname>loopCounter</varname> has been implemented within the "
+"<filename>MultipartRequest.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:692
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1494\">JBPAPP-1494</"
+"ulink>: The portal example that was previously included with the Seam "
+"Enterprise Application Platform distribution has been removed in order to "
+"avoid confusion that Seam 1.2.1 included with the EAP supports portal."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:697
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1044\">JBPAPP-1044</"
+"ulink>: After basic interaction with the Seam examples <filename>chatroom</"
+"filename>, <filename>mail</filename>, <filename>registration</filename>, "
+"<filename>booking</filename> and <filename>dvdstore</filename> would "
+"generate a <exceptionname>NullPointerException</exceptionname> during "
+"undeployment. In correcting this issue, the <filename>RootInterceptor.java</"
+"filename> file was updated to check if an applications context still active "
+"upon undeployment and deal with this appropriately."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:705
+#, no-c-format
+msgid "JBoss Hibernate"
+msgstr "JBoss Hibernate"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:709
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1580\">JBPAPP-1580</"
+"ulink>: The JBoss Hibernate Core component of the Enterprise Application "
+"Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:714
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1628\">JBPAPP-1628</"
+"ulink>: In an earlier fix to Hibernate the <methodname>org.hibernate.jdbc."
+"AbstractBatcher#closeQueryStatement()</methodname> method was changed to "
+"check for the existence of the prepared statement in the "
+"<classname>statementsToClose</classname> collection instead of closing it "
+"unconditionally. This has now caused a properties leak as the "
+"<methodname>org.hibernate.persister.entity."
+"AbstractEntityPersister#processGeneratedProperties()</methodname> used "
+"<methodname>org.hibernate.jdbc.AbstractBatcher#closeQueryStatement()</"
+"methodname> and the statement within <methodname>org.hibernate.persister."
+"entity.AbstractEntityPersister#processGeneratedProperties()</methodname> is "
+"not added to the <classname>statementsToClose</classname> collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:717
+#, no-c-format
+msgid ""
+"<filename>AbstractEntityPersister.java</filename> has been updated to "
+"execute a prepared statement on the result set and after calculating the "
+"<varname>propValue</varname> the result set is closed if it is not null; "
+"ensuring that no leak can occur."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:722
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1582\">JBPAPP-1582</"
+"ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</"
+"classname> is included with this CP release to support Sybase ASE 15 and "
+"this dialect now becomes apart of the Enterprise Application Platform "
+"certified configuration. Previous Sybase dialects are now considered "
+"deprecated and may be removed from future releases; however support will "
+"still be maintained for users who do not wish to move to the new dialect."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:742
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1524\">JBPAPP-1524</"
+"ulink>: The Sybase functions <methodname>second()</methodname>, "
+"<methodname>minute()</methodname>, <methodname>hour()</methodname> and "
+"<methodname>extract()</methodname> caused a "
+"<exceptionname>GenericJDBCException</exceptionname> when used. Moving these "
+"functions from the <filename>SQLServerDialect.java</filename> file to the "
+"<filename>SybaseDialect.java</filename> file allows for these functions to "
+"work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:757
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1519\">JBPAPP-1519</"
+"ulink>: Sybase does not support the operation <emphasis>on cascade delete</"
+"emphasis> while SQL Server does. To make sure that both operate correctly "
+"the <filename>SQLServerDialect.java</filename> file has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns true and <filename>SybaseDialect.java</filename> has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns false."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:762
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1496\">JBPAPP-1496</"
+"ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</"
+"emphasis> when using the <emphasis>Identity</emphasis> generator option. To "
+"close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make "
+"sure it is closed before returning the generated identity value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:767
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1480\">JBPAPP-1480</"
+"ulink>: Hibernate would attempt to read from an invalid column in the "
+"collection result set when the following conditions were present:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
+"ulink>: A configuração padrão SQL possuia erros, causando um problema com o "
+"hsqldb, do qual usa esta configuração. O problema com a configuração padrão "
+"foi corrigida corretamente agora."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:772
+#, no-c-format
+msgid "Instances of a subclass were contained in a collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:777
+#, no-c-format
+msgid ""
+"The subclasses were single-table and used a &lt;join&gt; (table-per-subclass "
+"with discriminator)."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:782
+#, no-c-format
+msgid ""
+"The &lt;join&gt; portion of the subclass contained at least 3 of its own "
+"columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:787
+#, no-c-format
+msgid ""
+"The &lt;join&gt; tables were fetched by select and not the default method "
+"for this task."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:792
+#, no-c-format
+msgid ""
+"To fix this issue the <filename>AbstractEntityPersister.java</filename> file "
+"was updated so that the <varname>columnNumber</varname> variable is passed "
+"to the <methodname>subclassColumnSelectableClosure</methodname> method "
+"instead of an increment of the for loop variable <varname>i</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:795
+#, no-c-format
+msgid ""
+"<filename>CollectionTest.java</filename> has also been updated and "
+"<filename>Animal.java</filename>, <filename>Mammal.java</filename>, "
+"<filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been "
+"added for testing purposes."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:800
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1467\">JBPAPP-1467</"
+"ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur "
+"when merging a detached instance of a <classname>One</classname> class that "
+"contains a new <classname>Many</classname> class instance and if and only if "
+"the <classname>One</classname> class was previously loaded as a proxy during "
+"the same transaction. The files <filename>StatefulPersistenceContext.java</"
+"filename>, <filename>BackrefPropertyAccessor.java</filename>, "
+"<filename>BackrefTest.java</filename> and <filename>Child.java</filename> "
+"have been updated to check for the proxy issue in the merging and once the "
+"proxy entity is found the <methodname>mergeMap</methodname> is updated to "
+"deal with this eventuality."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:805
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1365\">JBPAPP-1365</"
+"ulink>: A bug existed within Hibernate Core where the "
+"<methodname>addDuplicateAlias</methodname> method would include an entry "
+"into the hash map even when the <varname>classAlias</varname> variable was "
+"set to null; causing a <exceptionname>NullPointerException</exceptionname> "
+"when the <methodname>CrazyJPARRequirements()</methodname> method is called. "
+"To correct this issue the <filename>FromClause.java</filename> file has been "
+"modified to correct the <methodname>addDuplicateAlias</methodname> method by "
+"testing if the <varname>alias</varname> variable is null and if it is not "
+"null then the <methodname>fromElementByClassAlias.put</methodname> is now "
+"called, instead of this method being called even if <varname>alias</varname> "
+"contained a null value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:810
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1259\">JBPAPP-1259</"
+"ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL "
+"and the version field is specified by the user to not be updated, the "
+"<methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method "
+"would still update the field causing exceptions to appear in certain cases. "
+"Within this Enterprise Application Platform update "
+"<filename>AbstractEntityPersister.java</filename> has been corrected to "
+"check if the user has explicitly said that the version field should not be "
+"updated and does not update the field if this is the case."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:815
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1251\">JBPAPP-1251</"
+"ulink>: Filters that were enabled for Hibernate did not apply to update and "
+"delete Hibernate Query Language (HQL) statements. In correcting this bug "
+"numerous files have been updated to ensure that the filters work correctly. "
+"This fix is related to JBPAPP-1250 below."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:820
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1250\">JBPAPP-1250</"
+"ulink>: When creating queries with subqueries in Hibernate, any added "
+"filters would only apply to the top-level of the query and not to any "
+"subquery component or beneath. The Criteria code and HQL code associated "
+"with this has undergone significant re-tooling to allow filters to work "
+"appropriately with subqueries and extent as far as the Hibernate Query "
+"Language does."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:823
+#, no-c-format
+msgid ""
+"Though this is a significant fix to Hibernate, it has been included within "
+"this CP release because of its undeniable advantage to all users and ensures "
+"that filters on queries operate how a user would expect them to."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:833
+#, no-c-format
+msgid "JBoss Transaction Service (JBossTS)"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:837
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1510\">JBPAPP-1510</"
+"ulink>: The JBoss Transaction Service component of the Enterprise "
+"Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of "
+"the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:842
+#, no-c-format
+msgid ""
+"The <classname>AppServerJDBCXARecovery</classname> class was using the Java "
+"1.5 syntax when it should compile with Java 1.4. This error has been "
+"rectified with this release by modifying the "
+"<filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:847
+#, no-c-format
+msgid ""
+"When the Application Server started, the transaction manager may have "
+"deployed before the datasources, starting a recovery pass and causing "
+"exceptions. This issue has been rectified by modifying the "
+"<classname>AppServerJDBCXARecovery</classname> class and adding the "
+"<methodname>createConnection() throws SQLException</methodname> method which "
+"makes sure a connection exists before deploying the transaction manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:852
+#, no-c-format
+msgid ""
+"There were occurrences when the <classname>AppServerJDBCXARecovery</"
+"classname> class would contain information to an invalid connection because "
+"of database failure. This bug was fixed with the same correction as the "
+"above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</"
+"classname> class and adding the <methodname>createConnection() throws "
+"SQLException</methodname> method which makes sure a connection exists."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:857
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method would be run even when "
+"the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, "
+"when this method should only be executed before commit attempts and not "
+"rollbacks. In order to correct this and make sure the "
+"<methodname>beforeCompletion</methodname> method does not get executed for "
+"rollback events the <filename>SubordinateAtomicAction.java</filename> file "
+"has been modified."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:862
+#, no-c-format
+msgid ""
+"<methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a "
+"<exceptionname>HeuristicRollbackException</exceptionname> when the commit "
+"was aborted. This meant that <methodname>XATerminatorImple.commit</"
+"methodname> was unable to distinguish between a successful rollback and one "
+"in error. Fixed in this CP release, the <filename>TransactionImple.java</"
+"filename> file has been modified so that the <methodname>TransactionImple."
+"doOnePhaseCommit</methodname> method now generates a "
+"<exceptionname>RollbackException</exceptionname> instead of a heuristic when "
+"a successful rollback is performed."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:867
+#, no-c-format
+msgid ""
+"When the <literal>tx</literal> had been set to <varname>rollbackOnly</"
+"varname> and the <methodname>XATerminatorImple.prepare</methodname> method "
+"was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would "
+"be generated and yet the rollback would not be undertaken and the "
+"<literal>tx</literal> reference would be removed meaning no cleanup via the "
+"<methodname>commit</methodname> or <methodname>rollback</methodname> methods "
+"were possible. The <filename>XATerminatorImple.java</filename> file has been "
+"updated to correct this by improving the cleanup and exception reporting for "
+"rollbacks in <methodname>XATerminatorImple.prepare</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:872
+#, no-c-format
+msgid ""
+"The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called "
+"<methodname>beforeCompletion</methodname> but did not call "
+"<methodname>afterCompletion</methodname> when the return status was "
+"<literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</"
+"filename> now has corrected synchronization handling for transaction "
+"termination."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:877
+#, no-c-format
+msgid ""
+"The JCA coordinator did not call synchronizations during the phase commit "
+"cycle (1PC). Synchronization has been added to the JCA coordinator through "
+"the modification of the <filename>SubordinateAtomicAction.java</filename> "
+"file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:882
+#, no-c-format
+msgid ""
+"Coordinator methods would not perform a cleanup correctly. In order to "
+"rectify this cleanup routines have been added to the "
+"<methodname>phase2Commit</methodname> and <methodname>phase2Abort</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:892
+#, no-c-format
+msgid "Security Issues"
+msgstr "Problemas de Segurança"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:896
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>: An exploit existed within the JBoss Web Services component of the "
+"Enterprise Application Platform that would allow anyone to view any xml file "
+"from any location if <literal>&amp;resource=path/of/an/xmlfile.xml</literal> "
+"was applied to the end of any WSDL (Web Services Definition Language) access "
+"URL. The <filename>WSDLRequestHandler.java</filename> file has been updated "
+"to only allow the parent of a WSDL file, a servers data or WSDL or "
+"overridden WSDL publish directories access to xml file resources. Additional "
+"test files are also included which were created to ensure proper operation "
+"was being undertaken. (CVE-2009-0027 )"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:908
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1649\">JBPAPP-1649</"
+"ulink>: The documentation on the isolation of JGroup channels within the "
+"Server Configuration Guide was missing two parameters specific to the "
+"Enterprise Application Platform 4.3 distribution. The parameters of "
+"<varname>-Djboss.messaging.controlchanneludpport</varname> and <varname>-"
+"Djboss.messaging.datachanneludpport</varname> have been includedin section "
+"19.7.10 with example ports and the text addressing the concern of "
+"<emphasis>Why do I need to change the multicast port if I change the address?"
+"</emphasis> has been updated to reflect what is happening in an improved way."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:914
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1498\">JBPAPP-1498</"
+"ulink>: File set information within the Getting Started Guide (sections "
+"2.2.2 and 2.2.3) was outdated and required new information added and old "
+"information removed from the <literal>default</literal> server configuration "
+"file set and the contents of the <literal>conf</literal>, <literal>deploy</"
+"literal> and <literal>all</literal> directory sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:919
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1472\">JBPAPP-1472</"
+"ulink>: The instructions for adding SSL to EJB 2.1 in the Server "
+"Configuration Guide were incorrect as they did not include code pertaining "
+"to marshalling. The appropriate code has now been added to the instructions "
+"in section 9.8.2.3."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:924
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1362\">JBPAPP-1362</"
+"ulink>: The Getting Started Guide section 2.3 has been updated to include "
+"information about the <code>-b</code> option (and equivalents) that can be "
+"used on the command line to change the binding addresses of the Enterprise "
+"Application Platform for remote connectivity."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:929
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1346\">JBPAPP-1346</"
+"ulink>: Confusion existed when starting and stopping a <code>ZIP</code> "
+"installation of the server locally or remotely because a different username "
+"and password may be used. The Getting Started Guide has now been updated to "
+"explain that user credentials for the operating system will be used for "
+"local authentication and JBoss server credentials for remote authentication."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:937
+#, no-c-format
+msgid "Core Server"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:941
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1670\">JBPAPP-1670</"
+"ulink>: The JacORB component of the Enterprise Application Platform has been "
+"upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:946
+#, no-c-format
+msgid ""
+"A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to "
+"become unresponsive during shutdown. In rectifying this issue, the "
+"<filename>POA.java</filename> file has been modified so that instead of "
+"executing:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:949
+#, no-c-format
+msgid "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:950
+#, no-c-format
+msgid "the following is now executed:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:953
+#, no-c-format
+msgid "throw new ObjectNotActive();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:958
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1636\">JBPAPP-1636</"
+"ulink>: Affecting only third party adapters was an issue when one of these "
+"adapters handled the scheduling of work to be performed. The "
+"<classname>ExecutionContext</classname> class contained a value in seconds, "
+"from which the <methodname>getCompletionTimeout</methodname> method of "
+"<classname>org.jboss.resource.work.WorkWrapper</classname> obtains its "
+"information. An issue arises with <methodname>getCompletionTimeout</"
+"methodname> expecting the value to be in milliseconds, creating an error "
+"where the initially set timeout value may be 6 seconds but be passed to the "
+"thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> "
+"file has been updated and correctly converts the timeout value from seconds "
+"to milliseconds."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:963
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1635\">JBPAPP-1635</"
+"ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced "
+"for this release with new error codes of 17002 (connection reset) and 17008 "
+"(connection closed) now able to be handled. These enhancements have been "
+"applied to the <filename>OracleExceptionSorter.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:968
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1602\">JBPAPP-1602</"
+"ulink>: A <exceptionname>ConcurrentModificationException </exceptionname> "
+"would occur when a classloader would be undeployed while another user was "
+"attempting to load a class from the package. This error arose because the "
+"<classname>packagesMap</classname> within "
+"<classname>UnifiedLoaderRepository3</classname> had a <classname>TreeSet</"
+"classname> that was not correctly synchronized with changes. In order to "
+"rectify this, the <filename>ClassLoaderUtils.java</filename> file has been "
+"updated to import the <classname>Collections</classname> library and use the "
+"<methodname>synchronizedSet</methodname> method of the library in returning "
+"the <methodname>TreeSet</methodname> of the <methodname>newPackageSet</"
+"methodname> method."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:973
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1540\">JBPAPP-1540</"
+"ulink>: Within the cluster section of the Enterprise Application Platform, "
+"the <classname>GossipRouter</classname> and <classname>GossipClient</"
+"classname> (TCPGOSSIP) did not have socket read timeouts, socket linger "
+"timeouts and backlog set to provide the best behavior when heavily utilized "
+"or under network situations in need of improvement. This fix provides "
+"default values and configuration options for these in order to avoid "
+"problematic situations."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:978
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1539\">JBPAPP-1539</"
+"ulink>: When running parallel instances of the Enterprise Application "
+"Platform on Linux a bug existed where messages between the JGroups component "
+"of each instance would be picked up by both because all messages sent to the "
+"port number for Multicast Sockets would be picked up by both instances. The "
+"issue has been fixed by re-writing the code for Multicast Sockets so that "
+"the constructor uses a group address along with the port number as "
+"identifiers. This ensures that an instance of the EAP only receives messages "
+"pertaining to its specific group and thus inhibits channel crosstalk."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:983
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1538\">JBPAPP-1538</"
+"ulink>:The Probe Client had not been updated to use the same address as the "
+"Probe Listener does which is now 224.0.75.75. Correcting this issue, the "
+"Proble Client now uses 224.0.75.75 instead of 224.0.0.75 which allows the "
+"client and the listener to work together correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:988
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1535\">JBPAPP-1535</"
+"ulink>: The JDBCExtCacheLoader didn't handle persistent state transfer "
+"correctly since the <methodname>storeState</methodname> method would use "
+"available space on the <classname>MarshalledValueInputStream</classname> "
+"instead of on the <classname>ByteArrayInputStream</classname>. To correct "
+"the stream usage, <filename>JDBCExtendedCacheLoader.java</filename> has been "
+"updated to store the new state using the <varname>in_stream</varname> value "
+"as long as there is space available."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:993
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1534\">JBPAPP-1534</"
+"ulink>: The JDBCCacheLoader didn't work with Sybase as it tried to set a "
+"null <varname>BLOB</varname> (Binary Large OBject) column which is "
+"unsupported in Sybase. To correct this the <filename>JDBCCacheLoader.java</"
+"filename> and <filename>AdjListJDBCCacheLoader.java</filename> files have "
+"been updated to select the Sybase Driver if Sybase is to be used, ensuring "
+"that null values are set as <varname>LONGVARBINARY</varname> rather than "
+"<varname>BLOB</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:998
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1532\">JBPAPP-1532</"
+"ulink>: The JGroups clustering component of the Enterprise Application "
+"Platform has been upgraded to version 2.4.5. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1003
+#, no-c-format
+msgid ""
+"The probe listener within JGroups still used the old default address of "
+"224.0.0.75 instead of the new address of 224.0.75.75. The probe listener "
+"within JGroups has been updated with this release to use the correct default "
+"address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1008
+#, no-c-format
+msgid ""
+"The MPING protocol which sends a multicast ping over TCP contained cross-"
+"talk in Linux. the MPING protocol has since been corrected to eliminate "
+"cross-talk on the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1013
+#, no-c-format
+msgid ""
+"A problem was encountered within JGroups when two distinct processes were "
+"setup on the same machine, each using a different stack with different UDP "
+"multicast addresses. The issue was that each process would not work "
+"correctly because of the other, as each process would receive incorrect "
+"datagrams in reference to the groups each joined. To correct this the "
+"<classname>MulticastSocket</classname> constructor is now used in "
+"combination with a <varname>SocketAddress</varname> when JGroups is used on "
+"the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1018
+#, no-c-format
+msgid ""
+"The <literal>Gossip Router</literal> component of JGroups provided options "
+"to set <literal>backlog</literal>, <literal>socket read timeout</literal> "
+"and <literal>socket linger timeout</literal> within the code, however these "
+"options are not available via the command line. This update of the JGroups "
+"component, now includes the availability of these options to be set through "
+"the command line."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1023
+#, no-c-format
+msgid ""
+"Within the <literal>Gossip Router</literal> component of JGroups "
+"<methodname>Math.min</methodname> was used in calculating the socket linger "
+"timeout which caused incorrect results since this meant that the socket "
+"linger timeout would always be 1. <literal>Gossip Router</literal> has been "
+"updated to instead use <methodname>Math.max</methodname> in the calculation "
+"of the socket linger timeout."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1028
+#, no-c-format
+msgid ""
+"The <classname>RouterStub</classname> and <classname>GossipRouter</"
+"classname> classes have the <varname>setSoLinger</varname> value set "
+"incorrectly to use a seconds value when <varname>setSoLinger</varname> uses "
+"millisecond values. This meant that a value of 500 was 500 seconds rather "
+"than 500 milliseconds. The <classname>RouterStub</classname> class has had "
+"its <varname>setSoLinger</varname> corrected and the "
+"<classname>GossipRouter</classname> class has had the <varname>setSoLinger</"
+"varname> value corrected and timouts configurable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1035
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1530\">JBPAPP-1530</"
+"ulink>: The JCA adapter inflow did not roll back messages if a non-xa "
+"connection factory was being used within the JNDIProviderAdapter. In order "
+"to fix this issue the <filename>JmsServerSession.java</filename> file has "
+"been updated with added logic to the local transaction separation strategy "
+"as to allow for non-xa sessions to be rolled back using transaction session."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1040
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1521\">JBPAPP-1521</"
+"ulink>: The <classname>CleanShutdownInterceptor</classname> class would log "
+"a <exceptionname>GenericClusteringException</exceptionname> when the "
+"container had failed to shut down correctly or failed to start correctly and "
+"because of this behavior the error message displayed because of the "
+"exception should be updated to indicate that it may be an issue with the "
+"container failing to start instead of only failing to shut down. In this "
+"latest Enterprise Application Platform update, the error message has been "
+"updated to reflect both situations which may be the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1045
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1458\">JBPAPP-1458</"
+"ulink>: The JTA recovery configuration did not contain a line to enable "
+"JBoss Messaging (JBM) <classname>XAResourceRecovery</classname> even though "
+"it is stated in the JBM user guide. This CP release modifies the "
+"<filename>build-distr.xml</filename> file to all "
+"<classname>XAResourceRecovery</classname> to be enabled for JTA recovery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1050
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1479\">JBPAPP-1479</"
+"ulink>: Within the different distributions of the Enterprise Application "
+"Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and "
+"<filename>JBoss Messaging</filename> application policies have been present "
+"within the <filename>login-config.xml</filename> file, when "
+"<filename>JBossMQ</filename> is only included in the 4.2 distribution and "
+"<filename>JBoss Messaging</filename> is similarly only included in the 4.3 "
+"distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1053
+#, no-c-format
+msgid ""
+"This has been rectified in this release by modifying <filename>build.xml</"
+"filename> and <filename>login-config.xml</filename> to differentiate between "
+"requirements for each individual distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1058
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1473\">JBPAPP-1473</"
+"ulink>: The "
+"<classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</"
+"classname> within clustering didn't correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>, which would "
+"lead to the repeated calling of itself and eventually "
+"<exceptionname>StackOverflow</exceptionname> errors. In order to correct "
+"this the <filename>IgnoreUndeployLegacyClusteredSessionNotificationPolicy."
+"java</filename> file has been modified to correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1063
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1460\">JBPAPP-1460</"
+"ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for "
+"this Enterprise Application Platform release. This update corrects numerous "
+"bugs and details on these fixes can be found at <ulink url=\"https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html\">https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1068
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1366\">JBPAPP-1366</"
+"ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the "
+"<option>Oracle</option> schema is specified. To correct this the "
+"<filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has "
+"been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</"
+"methodname> function which changes all dots in a constraint name to "
+"underscores. This ensures that constraint names are compatible with Oracle."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1073
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1307\">JBPAPP-1307</"
+"ulink>: The Persistence Unit (PU) root was incorrectly detected within "
+"deployments that contained nested <filename>.jar</filename> files. The root "
+"PU was being detected as the first nested <filename>.jar</filename> "
+"encountered instead of being the deployment which contains the "
+"<filename>persistence.xml</filename> file. To make sure that the PU root is "
+"always set correctly, the <filename>JmxDeploymentUnit.java</filename> file "
+"has been updated with the removal of testing for the url being null and the "
+"<parameter>deploymentInfo.parent</parameter> not being null. This means that "
+"the url is now always taken straight from the "
+"<parameter>extractDescriptorUrl</parameter> of <filename>META-INF/"
+"persistence.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1078
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1289\">JBPAPP-1289</"
+"ulink>: The JBoss JAXR component of the Enterprise Application Platform has "
+"been upgraded to version 1.2.0.SP2. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1083
+#, no-c-format
+msgid ""
+"In the <filename>org.jboss.jaxr.juddi.JUDDIServlet</filename> and "
+"<filename>org.jboss.jaxr.juddi.transport.SaajTransport</filename> files the "
+"namespace value for <varname>xml:lang</varname> contained <literal>http://"
+"www.w3.org/TR/REC-xml/</literal>, which caused an exception within the metro "
+"stack. The namespace value should instead be null and this has been applied "
+"for this JAXR update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1090
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1275\">JBPAPP-1275</"
+"ulink>: The Xalan part of the Enterprise Application Platform has been "
+"upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the "
+"circumstance where an application which heavily used Xalan within large "
+"multi-threaded environments would encounter blocking situations."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
+"ulink>: O Componente de Serviços da Web do JBoss foi atualizado para a "
+"versão 2.0.1.SP2_CP02. Esta atualização incorpora diversos correções de bug "
+"e aprimoramentos."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1095
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1267\">JBPAPP-1267</"
+"ulink>: <classname>UserTransaction</classname> (UT) was not able to be "
+"deployed with a clustered proxy that supported sticky transactions "
+"correctly. This has been fixed by modifying numerous files which make "
+"<classname>UserTransaction</classname> deployable with transaction sticky "
+"load balance policies."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1100
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1249\">JBPAPP-1249</"
+"ulink>: The JSF component of the Enterprise Application Platform has been "
+"upgraded to version 1.2_10. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1105
+#, no-c-format
+msgid ""
+"A mixed EL expression ending with a literal failed to parse as a managed "
+"bean property value. The <filename>BeanBuilder.java</filename> file was "
+"updated with the removal of <code>ELUtils.getScope(this.expressionString, "
+"segment);</code> in order to fix this issue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1110
+#, no-c-format
+msgid ""
+"<methodname>LifecycleImpl</methodname> and <methodname>RestoreViewPhase</"
+"methodname> forced the <methodname>responseComplete()</methodname> method "
+"for the status of an existing view. To correct this problem the "
+"<filename>RestoreViewPhase.java</filename> file has been edited with the "
+"code <code>facesContext.responseComplete();</code> removed and replaced with "
+"<code>facesContext.renderResponse();</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1115
+#, no-c-format
+msgid ""
+"For a &lt;h:dataTable&gt; tag which does not set the <varname>var</varname> "
+"attribute, if the UIData component is created using a binding and calls the "
+"<methodname>setVar()</methodname> method to set the <varname>var</varname> "
+"attribute, it would be overwritten as a null value by the &lt;h:"
+"dataTable&gt; tag. This bug has been fixed by modifying the "
+"<filename>HtmlTaglib21Generator.java</filename> file so that component "
+"properties are not set if the tag attribute has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1120
+#, no-c-format
+msgid ""
+"The <classname>BindingValidator</classname> would generate a "
+"<exceptionname>ConverterException</exceptionname> instead of a "
+"<exceptionname>ValidatorException</exceptionname>. For this update, "
+"<classname>BindingValidator</classname> has been modified to generate the "
+"correct exception; <exceptionname>ValidatorException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1125
+#, no-c-format
+msgid ""
+"The cause of a <classname>PostConstruct</classname> exception within the "
+"<classname>BeanBuilder</classname> was not communicated to the user "
+"correctly. To correct the issue so that no information is hidden from the "
+"user, the <exceptionname>ManagedBeanCreationException</exceptionname> has "
+"been updated to provide more information about the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1130
+#, no-c-format
+msgid ""
+"An issue was present that would cause majarra to execute <filename>faces-"
+"config.xml </filename> initialization files twice, creating duplicate "
+"operations. This was caused since a record was not kept of which files had "
+"been initialized and which had not. File initialization tracking has been "
+"implemented to correct this issue and this has seen the modification of the "
+"following files: <filename>ConfigManager.java</filename>, "
+"<filename>ConfigureListener.java</filename>, <filename>WebConfiguration."
+"java</filename>, <filename>ConfigurationResourceProvider.java</filename>, "
+"<filename>MetaInfResourceProvider.java</filename>, "
+"<filename>RIConfigResourceProvider.java</filename> and "
+"<filename>WebResourceProvider.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1135
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.ApplicationObjectInputStream</"
+"classname> extends the functionality of <classname>java.io."
+"ObjectInputStream</classname> but failed to preserve the functionality as "
+"<classname>com.sun.faces.renderkit.ApplicationObjectInputStream</classname> "
+"would fail when primitives were used, unlike the <classname>java.io."
+"ObjectInputStream</classname> class which contains a special case to handle "
+"such a case. This would cause problems for <literal>UIComponents</literal>. "
+"<filename>ApplicationObjectInputStream.java</filename> has been updated to "
+"explicitly handle primitive cases and catch the "
+"<exceptionname>ClassNotFoundException</exceptionname> which may be generated."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1140
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.renderkit.html_basic.OutputLinkRenderer</classname> "
+"did not encode parameters correctly, missing the <literal>URLEncoding</"
+"literal>. <literal>URLEncoding</literal> has been added, correcting this "
+"bug, along with the parameter names."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1145
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.BaseTableRenderer</"
+"classname> did not allow for empty <varname>columnClasses</varname> when "
+"generating columns from user input. The issue was realizing when to create "
+"numerous columns rather just one; for instance if the user input "
+"<literal>foo, </literal> with a trailing space then the expected output "
+"would be one column with the name <literal>foo</literal> and another empty "
+"column. This was not the case though, as <literal>foo, </literal> would "
+"generate just one column with <literal>foo, </literal> in its entirety as "
+"the column name, instead of splitting the columns on the comma. This "
+"behavior has now been corrected so that <classname>com.sun.faces.renderkit."
+"html_basic.BaseTableRenderer</classname> no generates columns correctly, and "
+"in order to achieve this the following files have been updated: "
+"<filename>BasetableRenderer.java</filename>, <filename>GridRenderer.java</"
+"filename> and <filename>TableRenderer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1150
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.MenuRenderer</classname> "
+"class did not correctly differentiate between <literal>Objects</literal>; "
+"for instance the different between <literal>Boolean</literal> and "
+"<literal>boolean</literal>, noting the capitalization of the first. The "
+"error was with the logic in <classname>UISelect</classname> and "
+"<classname>MenuRenderer</classname>. To correct this, proper use of the "
+"converter for these classes has been implemented to deal with Objects "
+"correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1155
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.lifecycle.RestoreViewPhase</classname> called "
+"<methodname>DebugUtil.printTree</methodname> after restoring the view if "
+"debugging was enabled, causing incorrect initialization of calls when a "
+"listbox is being used and returning an incorrect value in the "
+"<classname>RenderResponse</classname> phase. Method calls have been "
+"restructured with the removal of references to the <methodname>DebugUtil."
+"printTree()</methodname> method from <filename>ViewHandlerImpl.java</"
+"filename> and <filename>RestoreViewPhase.java</filename> and "
+"<filename>RenderResponsePhase.java</filename> has been modified to call "
+"<methodname>DebugUtil.printTree</methodname> (if <varname>FINEST</varname> "
+"logging is enabled) at the end of the <classname>RenderResponse</classname> "
+"phase, fixing the issue (with the above changes also) and providing a more "
+"accurate view of the tree."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1159
+#, no-c-format
+msgid ""
+"<literal>CGLIB Enhanced UIComponents</literal> in a component tree would "
+"return a value of null for their class when calling <methodname>getPackage()"
+"</methodname> causing <classname>HtmlInputText.handleAttribute</classname> "
+"to fail as it relies on a not-nulll value. This issue has been corrected by "
+"ignoring a returned value of null from the <methodname>getPackage()</"
+"methodname> method for every instance in the codebase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1164
+#, no-c-format
+msgid ""
+"The <classname>UIComponentBase</classname> did not allow for the children of "
+"a tree to be iterated through in reverse order using a list iterator as it "
+"would produce an <exceptionname>IndexOutOfBoundsException</exceptionname> "
+"when the execution tries to calculate the size of the children. "
+"<methodname>ChildrenListIterator</methodname> method has been modified "
+"within the <classname>UIComponentBase</classname> class by changing the line "
+"of code <code>if ((index &lt; 0) || (index &gt;= list.size())) { </code> to "
+"<code>if ((index &lt; 0) || (index &gt; list.size())) {</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1169
+#, no-c-format
+msgid ""
+"Renderer kits for <filename>faces-config.xml</filename> were processed out "
+"of order depending on if <literal>ICEfaces</literal> or <literal>Mojara "
+"1.2_09</literal> is in use. This occurred due to containing all renderer DOM "
+"nods in a list associated with a namespace. This was done so that the "
+"renderer nodes could then be processed prior to the <literal>RenderKits</"
+"literal> being created and the nodes could be processed using the proper "
+"namespace. However, by placing all the renderers into this list, we lost the "
+"document ordering. The issue has been fixed by associating the renderer "
+"nodes with their owning document and processed in the parsing order."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1175
+#, no-c-format
+msgid ""
+"The <methodname>Class.getPackage()</methodname> method calls to synchronized "
+"methods, inhibiting scalability if the method has to be repeatedly executed. "
+"Use of the <methodname>Class.getPackage()</methodname> method has now been "
+"removed from <filename>UIComponent.java</filename>, <filename>RenderKitUtils."
+"java</filename> and <filename>HtmlComponentGenerator.java</filename>. "
+"Instead, the class name is now checked if it starts with the package name "
+"that is of interest, <classname>javax.faces.component.</classname>. This "
+"includes the components that are generated by the "
+"<classname>HtmlComponentGenerator</classname> since they are packaged in "
+"<classname>javax.faces.component.html</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1180
+#, no-c-format
+msgid ""
+"A bug presented itself in the <classname>RenderKitUtils</classname> class "
+"when a semicolon (<code>;</code>) followed a forward-slash (<code>/</code>) "
+"in a header Accept value (for instance: <code>text/;q=0.5</code>). To "
+"rectify this issue the <classname>RenderKitUtils</classname> class has been "
+"updated to assume <code>*</code> as the subtype for an Accept header that "
+"contains no subtype."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1187
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1224\">JBPAPP-1224</"
+"ulink>: Attribute default values in EJB were not set when in use with "
+"<literal>@Service</literal> and <literal>XMBean XML</literal> . In order to "
+"correct this the behavior has been re-written to improve the mimicking of "
+"<classname>ServerCreator</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1192
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1170\">JBPAPP-1170</"
+"ulink>: When the <methodname>getMBeanInfo</methodname> method is called "
+"within <classname>MBeanServerImpl</classname> and "
+"<classname>RawDynamicInvoker</classname>, the underlying exception to "
+"<exceptionname>NotCompliantMBeanException</exceptionname> is not expressed "
+"to the user. <filename>RawDynamicInvoker.java</filename> has now been "
+"updated to provide this useful information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1197
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1099\">JBPAPP-1099</"
+"ulink>: The <filename>commons-beanutils.jar</filename> file within the "
+"Enterprise Application Platform had the incorrect version in the "
+"<filename>manifest.mf</filename> file. Through the course of correcting this "
+"bug, it was found that the <literal>beanutils</literal> component was "
+"outdated and a newer version contained many advantages. In this update to "
+"the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, "
+"which sees the significant improvement that fixes a memory leak caused by a "
+"circular reference concerning the <classname>WeakHashMap</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1202
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1002\">JBPAPP-1002</"
+"ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be "
+"logged when transactions were not completed between invocations. However "
+"this was an error as BMT Stateful Session Beans are allowed to have this "
+"occurrence and so this logging measure has been removed in this Enterprise "
+"Application Platform update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1207
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
+"ulink>: Discrepancies existed between the port schemes within the "
+"<filename>sample-bindings.xml</filename> file. These include:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-961\">JBPAPP-961</"
+"ulink>: O JBoss Web foi atualizado à versão 2.0.0GA CP06."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1212
+#, no-c-format
+msgid ""
+"The remoting connectors were inserted in different places within the ports "
+"definition sections, making the comparison of the sections more difficult "
+"than was necessary."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1217
+#, no-c-format
+msgid ""
+"The <literal>ports-03</literal> section was missing the <literal>EJB "
+"remoting connector</literal> and the <literal>remoting connector</literal> "
+"sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1222
+#, no-c-format
+msgid ""
+"<literal>mq</literal> was used in the name property of the "
+"<varname>HAJNDIJMSProvider</varname> instead of <literal>jms</literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1227
+#, no-c-format
+msgid ""
+"The <literal>ports-01</literal>, <literal>ports-02</literal>, and "
+"<literal>ports-03</literal> schemes defined the <varname>timeout</varname> "
+"attribute twice in the <literal>JBoss Messaging</literal> section:"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1233
+#, no-c-format
+msgid "The above issues have been fixed appropriately in this update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1238
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-713\">JBPAPP-713</"
+"ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: "
+"PermGen</errorname> error. To correct this issue the Enterprise Application "
+"Platform now uses <filename>beanutils 1.8.0</filename> which fixes this "
+"<errorname>OutOfMemoryError</errorname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1243
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
+"ulink>: JMX source code was being exposed to the user when a "
+"<exceptionname>HTTP Status 500</exceptionname> exception would occur. To "
+"correct this, an error page <filename>genericError.jsp</filename> has been "
+"created and is now displayed whenever a <exceptionname>HTTP Status 500</"
+"exceptionname> exception occurs."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1252
+#, no-c-format
+msgid "Known Issues with this release"
+msgstr "Problemas Conhecidos nesta versão"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1255
+#, no-c-format
+msgid "Following is a list of known issues at the time of release."
+msgstr ""
+"Segue abaixo, uma lista dos problemas conhecidos no período desta versão."
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1259
+#, no-c-format
+msgid "General Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1263
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>: Footnotes within documentation tables and lists do not appear within "
+"PDFs. This issue resides within FOP and currently no workaround exists. "
+"Where possible footnotes are not used in the circumstances mentioned, "
+"however in documents such as the Release Notes the web address of a JIRA is "
+"automatically generated as a footnote and places a number beside that of the "
+"JIRA, referencing a footnote that does not appear."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1268
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-885\">JBPAPP-885</"
+"ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</"
+"methodname> or <methodname>RedeliveryDelay</methodname> is set to a value "
+"apart from zero, messages will not be redelivered even though the method "
+"<methodname>session.rollback()</methodname> had been called. This issue will "
+"not be fixed because redelivery delay is handled on the server side and the "
+"message is already acknowledged before delivery of the message with a non "
+"durable subscription. For the Enterprise Application Platform, this means "
+"that redelivery delays with non durable subscriptions cannot be supported."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1276
+#, no-c-format
+msgid "Hibernate Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1280
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1613\">JBPAPP-1613</"
+"ulink>: Null values for columns mapped as boolean in Hibernate, are "
+"persisted as zero instead of null. When the <methodname>PreparedStatement."
+"setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the "
+"Sybase environment, Sybase JDBC converts the null value to a zero because "
+"Sybase does not allow null bit columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1285
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
+"ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it "
+"should be set up to use image and text. Tests attaining to this currently "
+"fail with the message:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Permite que instâncias múltiplas sejam montadas em uma máquina "
+"usando um método de sub-pacote. Esta funcionalidade foi adicionada nesta "
+"versão com os arquivos -bin."
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1288
+#, no-c-format
+msgid ""
+"The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not "
+"supported and should not be called."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1291
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1554\">JBPAPP-1554</"
+"ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</"
+"methodname> method within Hibernate fails since Sybase currently only allows "
+"one column in a subquery select list, with the only exception to this being "
+"that a subquery in an <code>EXISTS()</code> predicate can have <code>*</"
+"code> as the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1294
+#, no-c-format
+msgid ""
+"The current workaround for this is to not use the HQL <methodname>elements()"
+"</methodname> method if the elements have a composite key. Instead the HQL "
+"should be reformatted to ensure there is no subquery with more than one item "
+"in the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1299
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1546\">JBPAPP-1546</"
+"ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be "
+"used to create stored procedures while in chained transaction mode. The "
+"suggested workaround for this case is to add the following code follwing the "
+"defining of the new stored procedure:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:1302
+#, no-c-format
+msgid ""
+"&lt;database-object&gt;\n"
+"        &lt;create&gt;\n"
+"                sp_procxmode paramHandling, 'chained'\n"
+"        &lt;/create&gt;\n"
+"        &lt;drop/&gt;\n"
+"&lt;/database-object&gt;"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1305
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
+"ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase "
+"environment and there are three or more joins where at least one of the "
+"joins involves a union."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>: Permite que instâncias múltiplas sejam montadas em uma máquina "
+"usando um método de sub-pacote. Esta funcionalidade foi adicionada nesta "
+"versão com os arquivos -bin."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1308
+#, no-c-format
+msgid ""
+"A workaround for this issue exists where it is reconmended that a user does "
+"not use <literal>join fetches</literal> involving <literal>union subclasses</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1313
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1230\">JBPAPP-1230</"
+"ulink>: In the Sybase environment when creating a subquery with an alias in "
+"use, the query will be incorrectly generated and cause an "
+"<exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. "
+"This bug impacts the following tests such that at present they are expected "
+"to fail: <classname>CriteriaQueryTest.testSubselect</classname>, "
+"<classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, "
+"<classname>DynamicFilterTest.testCriteriaControl</classname> and "
+"<classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1316
+#, no-c-format
+msgid ""
+"The known workaround is to use a HQL query instead of using a "
+"<methodname>DetachedCriteria</methodname> method in a subquery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1321
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1082\">JBPAPP-1082</"
+"ulink>: A limitation in the PostgreSQL JDBC driver causes a "
+"<exceptionname>javax.persistence.RollbackException</exceptionname>. This "
+"occurs when the <code>char</code> property is used without a value set as "
+"Hibernate then persists a string containing the character <code>\\u0000</"
+"code>, which causes PostgreSQL to generate an exception as it does not allow "
+"this character to be embedded in a string."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1324
+#, no-c-format
+msgid ""
+"Currently a workaround for persisting the <code>\\u0000</code> character in "
+"a <code>char</code> column using PostgreSQL does not exist. Instead it is "
+"reconmended that to persist a null value for the <code>char</code> property "
+"when it is uninitialized, the <methodname>java.lang.Character</methodname> "
+"method should be used."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1329
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1081\">JBPAPP-1081</"
+"ulink>: In the Entity Manager documentation it is stated that table aliases "
+"are supported in <code>update</code> clauses, however at present this is not "
+"the case. To fix this, the code has to be modified to remove the "
+"identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1334
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1068\">JBPAPP-1068</"
+"ulink>: When using Microsoft SQL and <code>@Type(type=\"text\")</code> in "
+"creating a table, the field is correctly created as <code>\"text\"</code> "
+"however when a delete operation is issued the field becomes set as a "
+"<varname>varchar</varname>, forcing the Microsoft SQL driver to return the "
+"error:"
+msgstr ""
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1337
+#, no-c-format
+msgid ""
+"The data types text and nvarchar are incompatible in the equal to operator."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1340
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1063\">JBPAPP-1063</"
+"ulink>: Currently MySQL does not support millisecond and microsecond "
+"measurements when returning database values such as <code>TIME</code> and "
+"<code>TIMESTAMP</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1345
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-953\">JBPAPP-953</"
+"ulink>: Hibernate Core and Annotations do not currently support the "
+"Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the "
+"Hypersonic database is planned for future releases."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: O componente JBoss Remoting do EAP foi atualizado para a versão "
+"2.2.2.SP8. Esta atualização inclui as inúmeras correções de bugs."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1350
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-946\">JBPAPP-946</"
+"ulink>: Within the Hibernate Entity Manager three different "
+"<exceptionname>NullPointerExceptions</exceptionname> are being investigated "
+"in relation to the EJB3 configuration, transaction operations when they are "
+"extended and packaging."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1355
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-906\">JBPAPP-906</"
+"ulink>: A bug exists within the Hibernate Core whereby the unstable "
+"synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is "
+"utilized creating a deserialized String. This causes a problem where if "
+"multiple threads are loading database rows containing arrays of strings, one "
+"thread is forced to undertake all the procedure while the other threads are "
+"left dormant."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1358
+#, no-c-format
+msgid ""
+"The implemented workaround for this issue is to use <code>-Dsun.lang."
+"ClassLoader.allowArraySyntax=true</code>, which can be a default setting "
+"within the <filename>run.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1363
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Within the Hibernate component of the Enterprise Application "
+"Platform the HashMap and HashSet iteration order changed from past releases "
+"because of support for JDK 1.6. However this has meant that the order of "
+"columns in union clauses and union-subclasses has changed, generating a "
+"slight impact on the components performance."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: A ordem de interação do HAshMap e HashSet foram modificadas a partir "
+"das liberações antigas, devido ao suporte para o JDK 1.6, com o componente "
+"Hibernate do EAP. No entanto, isto significa que a ordem de colunas nas "
+"clausulas de união e união de sub-classes foram modificadas, gerando um "
+"pequeno impacto no desempenho dos componentes."

Added: projects/docs/enterprise/4.3.4/readme/pt-BR/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pt-BR/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/pt-BR/Revision_History.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,29 @@
+# translation of readme.po to Brazilian Portuguese
+# Language pt-BR translations for readme package.
+#
+# Automatically generated, 2008.
+# Leticia de Lima <ldelima at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-08-01 12:19+1000\n"
+"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
+"Language-Team: Brazilian Portuguese <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/pt-BR/readme.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/pt-BR/readme.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/pt-BR/readme.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -85,8 +85,8 @@
 "aberto pela integração dos frameworks de código aberto best-of-breed, como "
 "por exemplo: JBoss Seam, Hibernate, Tomcat e JBoss Cache. Assim como, a "
 "Plataforma de Aplicativo do JBoss Enterprise é inteiramente testada e "
-"suportada pela Red Hat, além de ser certificada para trabalhar em muitos hardware "
-"empresariais e produtos de software líderes."
+"suportada pela Red Hat, além de ser certificada para trabalhar em muitos "
+"hardware empresariais e produtos de software líderes."
 
 #. Tag: para
 #: readme.xml:26
@@ -119,7 +119,11 @@
 "In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
 "with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
 "messaging infrastructure for JBoss Enterprise Application Platform."
-msgstr "Na Plataforma de Aplicativo JBoss Enterprise 4.3, o JBoss MQ foi substituído pelo JBoss Messaging 1.4. O JBoss Messaging fornece uma infra-estrutura messaging de alto desempenho para a Plataforma de Aplicativo JBoss Enterprise."
+msgstr ""
+"Na Plataforma de Aplicativo JBoss Enterprise 4.3, o JBoss MQ foi substituído "
+"pelo JBoss Messaging 1.4. O JBoss Messaging fornece uma infra-estrutura "
+"messaging de alto desempenho para a Plataforma de Aplicativo JBoss "
+"Enterprise."
 
 #. Tag: title
 #: readme.xml:40
@@ -133,7 +137,10 @@
 msgid ""
 "JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
 "Platform 4.3 and will now provide a complete implementation of JAX-WS."
-msgstr "Os Serviços da Web do JBoss estão atualizados para 2.0.1 na Plataforma de Aplicativo JBoss Enterprise 4.3 e fornecerão, agora, uma implementação completa do JAX-WS."
+msgstr ""
+"Os Serviços da Web do JBoss estão atualizados para 2.0.1 na Plataforma de "
+"Aplicativo JBoss Enterprise 4.3 e fornecerão, agora, uma implementação "
+"completa do JAX-WS."
 
 #. Tag: title
 #: readme.xml:48
@@ -148,7 +155,10 @@
 "This section contains information related to installing or upgrading to "
 "JBoss Enterprise Application Platform version &VERSION;, including hardware "
 "and platform requirements and prerequisites."
-msgstr "Esta seção contém informações relacionadas à instalação ou atualização à versão da Plataforma de Aplicativo do JBoss Enterprise &VERSION;, incluindo hardware, além de solicitações e pré-requisitos da plataforma."
+msgstr ""
+"Esta seção contém informações relacionadas à instalação ou atualização à "
+"versão da Plataforma de Aplicativo do JBoss Enterprise &VERSION;, incluindo "
+"hardware, além de solicitações e pré-requisitos da plataforma."
 
 #. Tag: title
 #: readme.xml:53
@@ -316,12 +326,12 @@
 "component, we do not make any commitment to fix them within a specific "
 "timeframe."
 msgstr ""
-"O Hypersonic SQL fornece a função de banco de dados \"fora da caixa\" padrão, apenas "
-"para o uso de desenvolvimento e avaliação. Ele NÃO é recomendável ou "
-"suportado como um banco de dados de uso de produção. O suporte técnico não é "
-"disponível para este componente, e enquanto estamos felizes em aceitar bugs "
-"arquivadas em referência a este componente, não nos responsabilizamos em "
-"corrigí-las, em um determinado período de tempo. "
+"O Hypersonic SQL fornece a função de banco de dados \"fora da caixa\" "
+"padrão, apenas para o uso de desenvolvimento e avaliação. Ele NÃO é "
+"recomendável ou suportado como um banco de dados de uso de produção. O "
+"suporte técnico não é disponível para este componente, e enquanto estamos "
+"felizes em aceitar bugs arquivadas em referência a este componente, não nos "
+"responsabilizamos em corrigí-las, em um determinado período de tempo. "
 
 #. Tag: title
 #: readme.xml:110
@@ -338,20 +348,25 @@
 #. Tag: ulink
 #: readme.xml:116
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:120
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:124
 #, no-c-format
 msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
 
 #. Tag: title
 #: readme.xml:131
@@ -472,8 +487,8 @@
 "Refer to the index.html file in the documentation directory for a list of "
 "included documentation."
 msgstr ""
-"Consulte o arquivo index.html no diretório da documentação, para a obtenção da lista de"
-"documentação inclusa."
+"Consulte o arquivo index.html no diretório da documentação, para a obtenção "
+"da lista dedocumentação inclusa."
 
 #. Tag: para
 #: readme.xml:223
@@ -501,10 +516,11 @@
 msgstr ""
 "Num sistema Linux, a documentação é encontrada em dois rpms que precisarão "
 "ser instalados manualmente. Estes rpms são <filename>jboss-seam-docs-&lt;"
-"version&gt;.noarch.rpm</filename> e <filename>rh-eap-docs-&lt;version&gt;.noarch.rpm</filename>. "
-"Por favor refira-se ao <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198."
-"shtm\">http://kbase.redhat.com/faq/FAQ_35_198.shtm</ulink>, para auxílio na "
-"instalação dos pacotes rpm, na Red Hat Enterprise Linux."
+"version&gt;.noarch.rpm</filename> e <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. Por favor refira-se ao <ulink url=\"http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm\">http://kbase.redhat.com/faq/FAQ_35_198."
+"shtm</ulink>, para auxílio na instalação dos pacotes rpm, na Red Hat "
+"Enterprise Linux."
 
 #. Tag: para
 #: readme.xml:234
@@ -515,8 +531,8 @@
 "installation modes."
 msgstr ""
 "<filename>Installation Guide</filename>: explica como instalar e verificar a "
-"instalação da Plataforma de Aplicativo JBoss Enterprise, usando os modos "
-"de instalação diferente."
+"instalação da Plataforma de Aplicativo JBoss Enterprise, usando os modos de "
+"instalação diferente."
 
 #. Tag: para
 #: readme.xml:239
@@ -528,11 +544,11 @@
 "illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
 "the JSF and EJB3 components."
 msgstr ""
-"<filename>Getting Started</filename>: detalha a estrutura do diretório de uma "
-"plataforma e uma descrição resumida do servidor do Aplicativo, além dos conjuntos "
-"e serviços de configurações diferentes. Usando um aplicativo da web simples, "
-"isto ilustra o uso dos componentes e como usar o Seam para integração do JSF e "
-"dos componentes EJB3."
+"<filename>Getting Started</filename>: detalha a estrutura do diretório de "
+"uma plataforma e uma descrição resumida do servidor do Aplicativo, além dos "
+"conjuntos e serviços de configurações diferentes. Usando um aplicativo da "
+"web simples, isto ilustra o uso dos componentes e como usar o Seam para "
+"integração do JSF e dos componentes EJB3."
 
 #. Tag: para
 #: readme.xml:244
@@ -554,11 +570,12 @@
 "redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
 "redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
 msgstr ""
-"As versões atualizadas da documentação com errata e informação adicional, "
-"o exemplo do código do aplicativo, assim como a versão mais recente das notas "
-"de versão poderão ser acessadas através da web, a partir do <ulink url=\"http://"
-"www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://"
-"www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+"As versões atualizadas da documentação com errata e informação adicional, o "
+"exemplo do código do aplicativo, assim como a versão mais recente das notas "
+"de versão poderão ser acessadas através da web, a partir do <ulink url="
+"\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"
+"\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</"
+"ulink>."
 
 #. Tag: title
 #: readme.xml:265
@@ -705,8 +722,8 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-755\">JBPAPP-755</"
 "ulink>: O arquivo readme.txt de recurso Seam solicitado, atualizou os links "
-"para seamframework.org e mencionou o EAP, ao invés do JBoss AS. Este "
-"arquivo foi atualizado com as mudanças acima, para esta versão."
+"para seamframework.org e mencionou o EAP, ao invés do JBoss AS. Este arquivo "
+"foi atualizado com as mudanças acima, para esta versão."
 
 #. Tag: title
 #: readme.xml:357
@@ -867,7 +884,10 @@
 "number is included with this release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1004\">JBPAPP-1004</"
-"ulink>: As versões prévias do EAP possuiam um número <property>serialVersionUID</property> incorreto, do qual interferiu na compatibilidade de versões anteriores. O número <property>serialVersionUID</property> correto está incluído nesta versão."
+"ulink>: As versões prévias do EAP possuiam um número "
+"<property>serialVersionUID</property> incorreto, do qual interferiu na "
+"compatibilidade de versões anteriores. O número <property>serialVersionUID</"
+"property> correto está incluído nesta versão."
 
 #. Tag: title
 #: readme.xml:428
@@ -942,14 +962,14 @@
 "attribute&gt;</programlisting>."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-944\">JBPAPP-944</"
-"ulink>: A <classname>ClusteredSession</classname> incluída na lógica que poderia "
-"pular a sessão de replicação de metadados, caso a única mudança fosse a data/"
-"hora. Este problema foi corrigido pela mudança do intervalo máximo padrão "
-"entre solicitações. O intervalo padrão é agora 60 segundos e o valor poderá "
-"ser configurável agora. Este atributo pode ser mudado adicionando um "
-"atributo ao arquivo <filename>jboss-service.xml</filename>, do qual parece-"
-"se com: <programlisting>&lt;attribute name=\"MaxUnreplicatedInterval"
-"\"&gt;30&lt;/attribute&gt;</programlisting>."
+"ulink>: A <classname>ClusteredSession</classname> incluída na lógica que "
+"poderia pular a sessão de replicação de metadados, caso a única mudança "
+"fosse a data/hora. Este problema foi corrigido pela mudança do intervalo "
+"máximo padrão entre solicitações. O intervalo padrão é agora 60 segundos e o "
+"valor poderá ser configurável agora. Este atributo pode ser mudado "
+"adicionando um atributo ao arquivo <filename>jboss-service.xml</filename>, "
+"do qual parece-se com: <programlisting>&lt;attribute name="
+"\"MaxUnreplicatedInterval\"&gt;30&lt;/attribute&gt;</programlisting>."
 
 #. Tag: title
 #: readme.xml:452
@@ -995,8 +1015,9 @@
 "ulink>: Ocorreu um problema onde o afunilamento sem serialização poderia "
 "ocorrer sem arrays para o JDK 1.6. Com o objetivo de solucionar este "
 "problema, o <programlisting>-Dsun.lang.ClassLoader.allowArraySyntax=true</"
-"programlisting> foi adicionado ao arquivo <filename>run.conf</filename>: <programlisting>-Dsun.lang."
-"ClassLoader.allowArraySyntax=true</programlisting>."
+"programlisting> foi adicionado ao arquivo <filename>run.conf</filename>: "
+"<programlisting>-Dsun.lang.ClassLoader.allowArraySyntax=true</"
+"programlisting>."
 
 #. Tag: title
 #: readme.xml:464
@@ -1143,7 +1164,9 @@
 "bin files."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>: Permite que instâncias múltiplas sejam montadas em uma máquina usando um método de sub-pacote. Esta funcionalidade foi adicionada nesta versão com os arquivos -bin."
+"ulink>: Permite que instâncias múltiplas sejam montadas em uma máquina "
+"usando um método de sub-pacote. Esta funcionalidade foi adicionada nesta "
+"versão com os arquivos -bin."
 
 #. Tag: para
 #: readme.xml:513
@@ -1154,7 +1177,13 @@
 "additional installation only and cannot be used in place of a regular RPM "
 "jbossas installation. If you only have one version of the AS, it will have "
 "to be the regular RPM installation (or ZIP or installer for older versions)."
-msgstr "É importante notar que a instalação jbossas regular é solicitada primeiramente no servidor, antes da instalação do -bin. O -bin é para uma instalação adicional apenas, e não pode ser usado no lugar de uma instalação jbossas RPM regular. Caso você possua apenas uma versão do AS, isto terá que ser a instalação RPM regular (ou COMPRIMIDA ou, ainda, instalador para versões mais antigas). "
+msgstr ""
+"É importante notar que a instalação jbossas regular é solicitada "
+"primeiramente no servidor, antes da instalação do -bin. O -bin é para uma "
+"instalação adicional apenas, e não pode ser usado no lugar de uma instalação "
+"jbossas RPM regular. Caso você possua apenas uma versão do AS, isto terá que "
+"ser a instalação RPM regular (ou COMPRIMIDA ou, ainda, instalador para "
+"versões mais antigas). "
 
 #. Tag: title
 #: readme.xml:517
@@ -1192,10 +1221,10 @@
 "consumption of Messages during deployment and is supported with this release."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-856\">JBPAPP-856</"
-"ulink>: O suporte da propriedade de configuração de ativação do DeliveryActive "
-"MDB, quando implementada. Este mecanismo permite a habilidade de inicializar "
-"e interromper o consumo de Mensagens durante a implementação, além de ser "
-"suportado nesta versão. "
+"ulink>: O suporte da propriedade de configuração de ativação do "
+"DeliveryActive MDB, quando implementada. Este mecanismo permite a habilidade "
+"de inicializar e interromper o consumo de Mensagens durante a implementação, "
+"além de ser suportado nesta versão. "
 
 #. Tag: title
 #: readme.xml:529
@@ -1220,9 +1249,9 @@
 "SQL 2005. Para corrigir este problema de compatibilidade, o <code>driver-"
 "class</code> foi atualizado a partir do <code>com.microsoft.jdbc.sqlserver."
 "SQLServerDriver</code> para <code>com.microsoft.sqlserver.jdbc."
-"SQLServerDriver</code>, além do portal padrão para a <code>connection-url</code> "
-"ter sido modificado de 1433 para 3918. O exemplo funciona corretamente agora, "
-"sob o Servidor SQL 2005, com estas alterações."
+"SQLServerDriver</code>, além do portal padrão para a <code>connection-url</"
+"code> ter sido modificado de 1433 para 3918. O exemplo funciona corretamente "
+"agora, sob o Servidor SQL 2005, com estas alterações."
 
 #. Tag: title
 #: readme.xml:535
@@ -1243,13 +1272,12 @@
 "which has since been fixed."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-815\">JBPAPP-815</"
-"ulink>: Existiu um problema onde caso um DOCTYPE fosse "
-"adicionado ao arquivo <filename>-ds.xml</filename> e a opção de "
-"<option>ValidateDTDs</option> fosse configurada para verdadeiro em "
-"<filename>jbossjca-services.xml</filename>, os erros de validação poderiam "
-"ocorrer. Isto foi encontrado devido um problema com o elemento <property>tx-"
-"connection-factory</property> em <filename>jms-ds.xml</filename>, do qual "
-"tem sido corrigido desde então."
+"ulink>: Existiu um problema onde caso um DOCTYPE fosse adicionado ao arquivo "
+"<filename>-ds.xml</filename> e a opção de <option>ValidateDTDs</option> "
+"fosse configurada para verdadeiro em <filename>jbossjca-services.xml</"
+"filename>, os erros de validação poderiam ocorrer. Isto foi encontrado "
+"devido um problema com o elemento <property>tx-connection-factory</property> "
+"em <filename>jms-ds.xml</filename>, do qual tem sido corrigido desde então."
 
 #. Tag: title
 #: readme.xml:541
@@ -1355,9 +1383,9 @@
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-729\">JBPAPP-729</"
 "ulink>: Uma configuração de caracter errado foi utilizada para decodificação "
-"dos parâmetros URL, após o redirecionamento do servlet ter ocorrido. Os "
-"URLs são decodificados corretamente após os redirecionamentos do servlet, "
-"uma vez corrigidos com este CP."
+"dos parâmetros URL, após o redirecionamento do servlet ter ocorrido. Os URLs "
+"são decodificados corretamente após os redirecionamentos do servlet, uma vez "
+"corrigidos com este CP."
 
 #. Tag: title
 #: readme.xml:571
@@ -1377,8 +1405,8 @@
 "the user is redirected to the displayMbeans page."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
-"ulink>: O código de recurso das Páginas JavaServer (JSP) foi exibido com "
-"o jmx-console, quando uma página de erro foi encontrada. Este problema é "
+"ulink>: O código de recurso das Páginas JavaServer (JSP) foi exibido com o "
+"jmx-console, quando uma página de erro foi encontrada. Este problema é "
 "endereçado pela checagem se é que a classe está usando um Bean existente, a "
 "partir do solicitado escopo, ou se ela está sendo instanciada para um outro "
 "novo. Caso aquele de escopo de solicitação for nulo, o usuário será "
@@ -1415,7 +1443,8 @@
 #: readme.xml:596
 #, no-c-format
 msgid "Following is a list of known issues at the time of release."
-msgstr "Segue abaixo, uma lista dos problemas conhecidos no período desta versão."
+msgstr ""
+"Segue abaixo, uma lista dos problemas conhecidos no período desta versão."
 
 #. Tag: para
 #: readme.xml:601
@@ -1429,9 +1458,8 @@
 "performance."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
-"ulink>: A ordem de interação do HAshMap e "
-"HashSet foram modificadas a partir das liberações antigas, devido ao suporte "
-"para o JDK 1.6, com o componente Hibernate do EAP. No entanto, isto significa que a ordem de colunas nas "
+"ulink>: A ordem de interação do HAshMap e HashSet foram modificadas a partir "
+"das liberações antigas, devido ao suporte para o JDK 1.6, com o componente "
+"Hibernate do EAP. No entanto, isto significa que a ordem de colunas nas "
 "clausulas de união e união de sub-classes foram modificadas, gerando um "
 "pequeno impacto no desempenho dos componentes."
-

Modified: projects/docs/enterprise/4.3.4/readme/zh-CN/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/zh-CN/Author_Group.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/zh-CN/Author_Group.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,24 +1,26 @@
-# translation of Author_Group.po to
+# translation of readme.po to
 # Language zh-CN translations for readme package.
 #
 # Automatically generated, 2008.
 # Xi HUANG <xhuang at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: Author_Group\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-07-29 11:01+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-07-31 10:40+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
 "Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: KBabel 1.11.4\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
 
-#. Tag: corpauthor
-#: Author_Group.xml:5
+#. Tag: author
+#: Author_Group.xml:6
 #, no-c-format
-msgid "Red Hat Documentation Group"
-msgstr "Red Hat Documentation Group"
-
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/zh-CN/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/zh-CN/Book_Info.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/zh-CN/Book_Info.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -1,3 +1,4 @@
+# translation of readme.po to
 # Language zh-CN translations for readme package.
 #
 # Automatically generated, 2008.
@@ -4,46 +5,47 @@
 # Xi HUANG <xhuang at redhat.com>, 2008.
 msgid ""
 msgstr ""
-"Project-Id-Version: readme 4.3.2\n"
+"Project-Id-Version: readme\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-07-27 23:50+0000\n"
-"PO-Revision-Date: 2008-07-28 15:18+1000\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-07-31 10:40+1000\n"
 "Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: Chinese Simplified <kde-i18n-doc at lists.kde.org>\n"
+"Language-Team:  <en at li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KAider 0.1\n"
+"X-Generator: KBabel 1.11.4\n"
 "Plural-Forms: nplurals=2; plural=n != 1;\n"
 
 #. Tag: title
 #: Book_Info.xml:6
-#, no-c-format
-msgid "Release Notes"
+#, fuzzy, no-c-format
+msgid "Release Notes CP04"
 msgstr "发行注记"
 
 #. Tag: subtitle
 #: Book_Info.xml:7
-#, no-c-format
-msgid "JBoss Enterprise Application Platform 4.3.0.CP02"
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
 msgstr "JBoss 企业级应用程序平台 4.3.0.CP02"
 
 #. Tag: para
-#: Book_Info.xml:11
-#, no-c-format
+#: Book_Info.xml:13
+#, fuzzy, no-c-format
 msgid ""
 "These release notes contain important information related to JBoss "
-"Enterprise Application Platform 4.3.0.CP02 that may not be currently "
+"Enterprise Application Platform 4.3.0.CP04 that may not be currently "
 "available in the Product Manuals. You should read these Release Notes in "
 "their entirety before installing JBoss Enterprise Application Platform 4.3.0."
-"CP02."
+"CP04."
 msgstr ""
-"本发行注记包含和 JBoss 企业级应用程序平台 4.3.0.CP02 相关但未在产品手册里的重要信息。在安装 JBoss 企业级应用程序平台 4.3."
-"0.CP02 之前，你应该完整地阅读这些信息。"
+"本发行注记包含和 JBoss 企业级应用程序平台 4.3.0.CP02 相关但未在产品手册里的重"
+"要信息。在安装 JBoss 企业级应用程序平台 4.3.0.CP02 之前，你应该完整地阅读这些"
+"信息。"
 
 #. Tag: holder
-#: Book_Info.xml:25
+#: Book_Info.xml:27
 #, no-c-format
 msgid "&HOLDER;"
 msgstr "&HOLDER;"
-

Added: projects/docs/enterprise/4.3.4/readme/zh-CN/Release_Notes_CP04.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/zh-CN/Release_Notes_CP04.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/zh-CN/Release_Notes_CP04.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,3034 @@
+# translation of readme.po to
+# Language zh-CN translations for readme package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-07-31 10:40+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:9
+#, no-c-format
+msgid "Introduction"
+msgstr "介绍"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:12
+#, no-c-format
+msgid ""
+"These release notes contain important information related to JBoss "
+"Enterprise Application Platform &VERSION;. New features, known problems, "
+"resources, and other current issues are addressed here."
+msgstr ""
+"本注记包含了和 JBoss 企业级应用程序平台 &VERSION; 相关的重要信息。新的功能、"
+"已知的问题、资源和其他问题都会在这里提及或解决。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:16
+#, no-c-format
+msgid "Overview"
+msgstr "概述"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:17
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform is the next evolutionary step in open "
+"source enterprise software. It is a powerful tool for developing rich, high "
+"performance, Web 2.0 applications on a pure Java Platform."
+msgstr ""
+"JBoss 企业级应用程序平台是开源企业级软件的革命性的下一步。它是一个在纯 Java "
+"平台上开发功能丰富、高性能的 Web 2.0 应用程序的强大的工具。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:20
+#, no-c-format
+msgid ""
+"JBoss Enterprise Application Platform provides complete compatibility with "
+"existing J2EE 1.4 enterprise Java applications. At the same time, almost all "
+"the key features and components defined in the Java EE 5.0 specification are "
+"supported. So your new enterprise Java applications can take immediate "
+"advantage of the Java EE 5.0's significantly simpler POJO-based programming "
+"model."
+msgstr ""
+"JBoss 企业级应用程序平台完全兼容现有的 J2EE 1.4 企业级 Java 程序。同时，它支"
+"持 Java EE 5.0 规格里定义的几乎所有的关键特征和组件。所以您新的企业级 Java 应"
+"用程序可以马上利用 Java EE 5.0 里大大简化的基于 POJO 的编程模式。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:23
+#, no-c-format
+msgid ""
+"Further, by integrating best-of-breed open source frameworks such as JBoss "
+"Seam, Hibernate, Tomcat, and JBoss Cache the Platform takes advantage of "
+"innovations in the open source community. As well, JBoss Enterprise "
+"Application Platform is fully tested and supported by Red Hat, and is "
+"certified to work on many leading enterprise hardware and software products."
+msgstr ""
+"而且，通过集成最好的开源框架 - 如 JBoss Seam、Hibernate、Tomcat 和 JBoss "
+"Cache  - JBoss 企业级应用程序平台充分利用了开源社区的技术创新。而且，红帽对它"
+"进行了完备的测试和支持，证明它可以运行在许多主要的企业级硬件和软件上。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:26
+#, no-c-format
+msgid ""
+"All of which means you can develop your new application taking advantage of "
+"Java EE 5.0 technologies immediately and with the confidence of knowing it "
+"will remain forward-compatible with future versions of the JBoss Platform."
+msgstr ""
+"这都意味着您可以马上使用 Java EE 5.0 技术开发您新的应用程序，并坚信它将和将"
+"来 JBoss 平台的新版本兼容。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:32
+#, no-c-format
+msgid "New Features in JBoss Enterprise Application Platform 4.3"
+msgstr "JBoss 企业级应用程序平台 4.3 里的新特征"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:34 Release_Notes_CP04.xml:365
+#, no-c-format
+msgid "JBoss Messaging"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:35
+#, no-c-format
+msgid ""
+"In JBoss Enterprise Application Platform 4.3, JBoss MQ 1.3 has been replaced "
+"with JBoss Messaging 1.4. JBoss Messaging provides a high performance "
+"messaging infrastructure for JBoss Enterprise Application Platform."
+msgstr ""
+"在这个版本里，JBoss MQ 1.3 已经被 JBoss Messaging 1.4 取代。JBoss Messaging "
+"为 JBoss 企业级应用程序平台提供了高性能的消息基础结构。 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:40
+#, no-c-format
+msgid "JBoss Web Services 2.0.1"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:41
+#, no-c-format
+msgid ""
+"JBoss Web Services is upgraded to 2.0.1 in JBoss Enterprise Application "
+"Platform 4.3 and will now provide a complete implementation of JAX-WS."
+msgstr ""
+"在本发行版本里，JBoss Web Services 升级至 2.0.1，现在它提供了对 JAX-WS 的完整"
+"的实现。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:47
+#, no-c-format
+msgid "Component Versions"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:48
+#, no-c-format
+msgid ""
+"This section details the versions of the components which create the "
+"Enterprise Application Platform 4.3 that can be found in this Cumulative "
+"Patch release."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:53
+#, no-c-format
+msgid "JBoss Application Server 4.2.z"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:58
+#, no-c-format
+msgid "Hibernate Core 3.2.4.SP1.CP07"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:63
+#, no-c-format
+msgid "Hibernate Annotations 3.2.1.GA.CP03"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:68
+#, no-c-format
+msgid "Hibernate Entity Manager 3.2.1.GA_CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:73
+#, no-c-format
+msgid "JAF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:78
+#, no-c-format
+msgid "JBoss Cache 1.4.1.SP11"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:83
+#, no-c-format
+msgid "JBoss JAXR 1.2.0.SP2"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:88
+#, fuzzy, no-c-format
+msgid "JBoss Messaging 1.4.0.SP3-CP07"
+msgstr "JBoss Messaging"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:93
+#, fuzzy, no-c-format
+msgid "JBoss Remoting 2.2.2.SP11"
+msgstr "JBoss Remoting "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:98
+#, no-c-format
+msgid "JBoss Transactions 4.2.3.SP5.CP04"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:103
+#, fuzzy, no-c-format
+msgid "JBoss Web 2.0.0-6.CP09"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:108
+#, fuzzy, no-c-format
+msgid "JBoss Web Services 2.0.1.SP2_CP05"
+msgstr "JBoss Web Services 2.0.1"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:113
+#, no-c-format
+msgid "JGroups 2.4.5"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:118
+#, no-c-format
+msgid "JSF 1.2_10"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:123
+#, no-c-format
+msgid "Seam 1.2.1.AP"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:128
+#, no-c-format
+msgid "Xalan 2.7.0.patch02"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:134
+#, no-c-format
+msgid ""
+"The Enterprise Application Platform Server has been redefined for the "
+"enterprise market to a level where direct association to a community release "
+"can no longer be drawn."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:140
+#, no-c-format
+msgid "Installation and Migration Notes"
+msgstr "安装和移植注记"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:141
+#, no-c-format
+msgid ""
+"This section contains information related to installing or upgrading to "
+"JBoss Enterprise Application Platform version &VERSION;, including hardware "
+"and platform requirements and prerequisites."
+msgstr ""
+"本节包含和安装和升级至 JBoss 企业级应用程序平台 &VERSION; 相关的信息，其中包"
+"括对硬件和平台的要求和预备条件。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:145
+#, no-c-format
+msgid "Installation Notes"
+msgstr "安装注记"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:146
+#, fuzzy, no-c-format
+msgid ""
+"You must have adequate disk space to install JDK and JBoss Enterprise "
+"Application Platform while also allowing enough space for your applications. "
+"You must have a working installation of JDK 1.5 or 1.6. For the latest "
+"information on supported Operating System / JVM combinations, supported "
+"Database platforms and current information on the revision level of included "
+"components, please refer to <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>. Refer to the "
+"installation guide available online from <ulink url=\"http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/"
+"docs/en-US/JBoss_Enterprise_Application_Platform/</ulink> for detailed "
+"instructions to install and verify JBoss Enterprise Application Platform."
+msgstr ""
+"你必须有足够的空间来安装 JDK 和 JBoss 企业级应用程序平台以及你自己的应用程"
+"序。JDK 1.5 是必须安装的。关于所支持的操作系统/JVM 组合、数据库平台和所含组件"
+"的版本的最新信息，请参考 <ulink url=\"http://www.jboss.com/products/"
+"platforms/application/testedconfigurations\">http://www.jboss.com/products/"
+"platforms/application/testedconfigurations</ulink>。关于安装和验证 JBoss 企业"
+"级应用程序平台的详细说明，清参考 <ulink url=\"http://www.redhat.com/docs/en-"
+"US/JBoss_Enterprise_Application_Platform/\">http://www.redhat.com/docs/en-US/"
+"JBoss_Enterprise_Application_Platform/</ulink> 上的在线安装指南。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:151
+#, fuzzy, no-c-format
+msgid "Upgrading from JBoss Enterprise Application Platform 4.3.0.CP03"
+msgstr "从 JBoss 企业级应用程序平台 4.3 进行升级"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:153
+#, no-c-format
+msgid "Using CSP/JON"
+msgstr "使用 CSP/JON"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:154
+#, fuzzy, no-c-format
+msgid ""
+"Refer to <ulink url=\"https://network.jboss.com/confluence/display/JON2/"
+"Applying+JBoss+Patches\">https://network.jboss.com/confluence/display/DOC/"
+"Installing+a+Patch</ulink> for instructions on installing a Cumulative Patch."
+msgstr ""
+"关于安装 Cumulative Patch 的说明，请参考 <ulink url=\"https://network.jboss."
+"com/confluence/display/DOC/Installing+a+Patch\">https://network.jboss.com/"
+"confluence/display/DOC/Installing+a+Patch</ulink>。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:164
+#, no-c-format
+msgid "Important Notes"
+msgstr "重要注记"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:166
+#, no-c-format
+msgid "Running the example Seam Applications"
+msgstr "运行 Seam 应用程序示例"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:169
+#, no-c-format
+msgid ""
+"It is recommended to run the example Seam applications that are included "
+"with the documentation using the production configuration. Using another "
+"configuration may result in memory issues. Note that the default "
+"configuration for the server to start with, if no other configuration is "
+"specified, is the production configuration."
+msgstr ""
+"我们推荐您使用 production 配置来运行文档里包含的 Seam 应用程序示例。使用其他"
+"的配置可能会导致内存问题。注意，如果没有指定使用哪个配置，服务器将缺省使用 "
+"production 配置启动。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:173
+#, no-c-format
+msgid ""
+"To avoid memory issues, adjust the memory settings before deploying the "
+"applications. You can do this by updating <literal>JAVA_OPTS</literal> "
+"settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run."
+"conf</filename> with these recommended values:"
+msgstr ""
+"为了避免内存问题，请在部署程序前调整内存设置。你可以用这些推荐值来更新 "
+"<filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> 文件里的 "
+"<literal>JAVA_OPTS</literal> 设置："
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:175
+#, no-c-format
+msgid "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+msgstr "-Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:178
+#, no-c-format
+msgid ""
+"Refer to the \"Seam Reference Guide\" included in the documentation set "
+"(<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</filename>) for "
+"important information regarding the deployment of Seam examples and detailed "
+"information on developing applications using Seam."
+msgstr ""
+"关于 Seam 示例程序和用 Seam 开发应用程序的详细信息，请参考文档集里包括的"
+"《Seam 参考指南》（<filename>JBOSS_DIST/doc/seam/Seam_Reference_Guide.pdf</"
+"filename>）。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:186
+#, no-c-format
+msgid "Default Security Settings"
+msgstr "缺省的安全设置"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:189
+#, no-c-format
+msgid ""
+"If you are using the rpm, or the zip distribution, please note that by "
+"default, authentication is enabled and no user accounts are set up. This is "
+"done to prevent unauthorized access to various services of JBoss AS. Please "
+"refer to the Installation Guide, or see <ulink url=\"http://kbase.redhat.com/"
+"faq/FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</"
+"ulink> for information on how to make the services accessible again."
+msgstr ""
+"如果您正在使用 rpm，或是 zip 分发版本，请注意在缺省情况下，验证会被启用且没有"
+"设立用户帐号。这是为了阻止对 JBoss AS 各种服务的未授权的访问。要获得如何使服"
+"务可以被访问的信息，请参考 <ulink url=\"http://kbase.redhat.com/faq/"
+"FAQ_107_9963.shtm\">http://kbase.redhat.com/faq/FAQ_107_9963.shtm</ulink>。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:194
+#, no-c-format
+msgid "Embedded Hypersonic Database"
+msgstr "内嵌的 Hypersonic 数据库 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:197
+#, no-c-format
+msgid ""
+"Hypersonic SQL provides default \"out of the box\" database functionality "
+"for evaluation and development use only. It is NOT recommended or supported "
+"as a production-use database. Technical support is not available for this "
+"component, and while we are happy to accept bugs filed against this "
+"component, we do not make any commitment to fix them within a specific "
+"timeframe."
+msgstr ""
+"Hypersonic SQL 为评估和开发提供缺省的数据库功能。我们不推荐或支持它在产品环境"
+"里使用。虽然没有对它的技术支持，我们很高兴收到关于该组件的程序错误报告，不过"
+"我们不承诺在明确时间范围内修复这些错误。 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:202
+#, no-c-format
+msgid "Source Files"
+msgstr "源码文件 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:204
+#, no-c-format
+msgid "SRPMs"
+msgstr "SRPMs "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:208
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:212
+#, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:216
+#, no-c-format
+msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:223
+#, no-c-format
+msgid "Source ZIP"
+msgstr "源码的 ZIP 文件 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:228
+#, fuzzy, no-c-format
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP04.zip"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/jbeap/4.3.0/en/source/jboss-eap-src-4.3.0-"
+"CP02.zip"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:237
+#, no-c-format
+msgid "Product Support and License Website Links"
+msgstr "产品支持和许可证网站链接 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:241
+#, no-c-format
+msgid "Support Processes"
+msgstr "支持过程 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:243
+#, no-c-format
+msgid "http://www.redhat.com/support/process/"
+msgstr "http://www.redhat.com/support/process/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:248
+#, no-c-format
+msgid "Production Support Scope of Coverage"
+msgstr "产品支持范围 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:252
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/production"
+msgstr "http://www.redhat.com/support/policy/soc/production"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:258
+#, no-c-format
+msgid "Production Support Service Level Agreement"
+msgstr "产品支持服务级别协议 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:263
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/production/"
+msgstr "http://www.redhat.com/support/policy/sla/production/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:268
+#, no-c-format
+msgid "Developer Support Scope of Coverage"
+msgstr "开发人员支持范围 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:273
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/soc/developer/"
+msgstr "http://www.redhat.com/support/policy/soc/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:278
+#, no-c-format
+msgid "Developer Support Service Level Agreement"
+msgstr "开发人员支持服务级别协议 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:283
+#, no-c-format
+msgid "http://www.redhat.com/support/policy/sla/developer/"
+msgstr "http://www.redhat.com/support/policy/sla/developer/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:288
+#, no-c-format
+msgid "Product Update and Support Policy by Product"
+msgstr "产品更新和支持策略 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:293
+#, no-c-format
+msgid "http://www.redhat.com/security/updates/jboss_notes/"
+msgstr "http://www.redhat.com/security/updates/jboss_notes/"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:298
+#, no-c-format
+msgid "JBoss End User License Agreement"
+msgstr "JBoss 最终用户许可证协议 "
+
+#. Tag: ulink
+#: Release_Notes_CP04.xml:303
+#, no-c-format
+msgid "http://www.redhat.com/licenses/jboss_eula.html"
+msgstr "http://www.redhat.com/licenses/jboss_eula.html"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:309 Release_Notes_CP04.xml:904
+#, no-c-format
+msgid "Documentation"
+msgstr "文档 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:312
+#, no-c-format
+msgid ""
+"Refer to the index.html file in the documentation directory for a list of "
+"included documentation."
+msgstr "请阅读文档目录里的 index.html 文件来获得文档列表。 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:315
+#, no-c-format
+msgid ""
+"In the zip distribution, documentation for the Platform and its individual "
+"components is distributed in a separate zip file, <filename>jboss-eap-docs-"
+"&lt;version&gt;.zip</filename>."
+msgstr ""
+"在此 zip 分发版本里，本平台及其单个组件的文档在单独的 zip 文件里分发： "
+"<filename>jboss-eap-docs-&lt;version&gt;.zip</filename>。 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:319
+#, no-c-format
+msgid ""
+"On a Linux system, the documentation is found in two rpms that will need to "
+"be installed manually. These rpms are <filename>jboss-seam-docs-&lt;"
+"version&gt;.noarch.rpm</filename>, and <filename>rh-eap-docs-&lt;version&gt;."
+"noarch.rpm</filename>. For help with installing rpm packages on Red Hat "
+"Enterprise Linux, please refer to the Red Hat Knowledge base article located "
+"at <ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase."
+"redhat.com/faq/FAQ_35_198.shtm</ulink>"
+msgstr ""
+"在 Linux 系统里，你需要手工安装两个关于文档的 rpm 软件包。它们是 "
+"<filename>jboss-seam-docs-&lt;version&gt;.noarch.rpm</filename> 和 "
+"<filename>rh-eap-docs-&lt;version&gt;.noarch.rpm</filename>。关于在红帽企业"
+"版 Linux 上安装 rpm 软件包，请参考红帽知识库里的文章： <ulink url=\"http://"
+"kbase.redhat.com/faq/FAQ_35_198.shtm\">http://kbase.redhat.com/faq/"
+"FAQ_35_198.shtm</ulink>。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:326
+#, fuzzy, no-c-format
+msgid ""
+"<filename>Installation Guide</filename> explains how to install and verify "
+"the installation of JBoss Enterprise Application Platform using different "
+"installation modes."
+msgstr ""
+"<filename>《安装指南》</filename>解释了如何用不同的安装模式安装和验证 JBoss "
+"企业级应用程序平台。 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:331
+#, no-c-format
+msgid ""
+"<filename>Getting Started</filename> details the directory structure of the "
+"platform and a quick tour of the Application Server and different "
+"configuration sets and services. Using a simple web application it "
+"illustrates the use of JSF-EJB3 components and how to use Seam to integrate "
+"the JSF and EJB3 components."
+msgstr ""
+"<filename>《起步指南》</filename>详细描述了本平台的目录结构、提供了关于应用服"
+"务器和不同配置集和服务的快速教程。利用一个简单的 web 程序，它演示了对 JSF-"
+"EJB3 组件的使用和如何把 Seam 集成 JSF 和 EJB3 组件。 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:336
+#, no-c-format
+msgid ""
+"<filename>Server Configuration Guide</filename> explains all administrative "
+"and configuration functions in detail."
+msgstr ""
+"<filename>《服务器配置指南》</filename>详细解释了所有的管理和配置功能。 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:342
+#, no-c-format
+msgid ""
+"Updated versions of the documentation with errata and additional "
+"information, example application code, as well as the most recent version of "
+"the release notes may be accessed via the web from <ulink url=\"http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/\">http://www."
+"redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</ulink>."
+msgstr ""
+"关于带有勘误、其他信息、例程源代码以及最新注记的文档，请访问 <ulink url="
+"\"http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/"
+"\">http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/</"
+"ulink>。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:357
+#, no-c-format
+msgid "Issues fixed in this release"
+msgstr "在本发行版本里修复的问题 "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:361
+#, no-c-format
+msgid "Following is a list of issues fixed in this release:"
+msgstr "下面是在本发行版本里修复的问题的列表： "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:369
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1615\">JBPAPP-1615</"
+"ulink>: The JBoss Messaging component of the Enterprise Application Platform "
+"has been upgraded to version 1.4.0.SP3-CP07. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:374
+#, no-c-format
+msgid ""
+"There was an issue with the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method whereby the method delegates checking to "
+"the <classname>ResourceManager</classname> <varname>serverID</varname>. This "
+"instigates the case where the <methodname>xasess2.start(xid, TMJOIN)</"
+"methodname> method is called and the <methodname>MessagingXAResource.isSameRM"
+"(XAResource)</methodname> method returns true but the resource manager does "
+"not hold the transaction state required to perform a <code>TMJOIN</code>. "
+"Further to this when a session is closed the <methodname>SessionAspect."
+"handleClose()</methodname> method is called, yet the <code>tx</code> was "
+"removed from the transaction manager meaning it is no longer in the "
+"<code>conn1</code> resource manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:377
+#, no-c-format
+msgid ""
+"To correct this both the <methodname>MessagingXAResource.isSameRM</"
+"methodname> method and <classname>ResourceManager</classname> have the same "
+"<code>serverID</code> and the same map of transactions, ensuring that if the "
+"<classname>ResourceManager</classname> was to ever return true, the call to "
+"<methodname>start(TMJOIN)</methodname> would correctly succeed. To note is "
+"that the transaction will rollback at completion time and any message "
+"delivered in the <code>tx</code> will be redelivered."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:382
+#, no-c-format
+msgid ""
+"Client connection parameters were not being passed to the JBoss Remoting "
+"layer, leaving parameters such as <varname>validatorPingPeriod</varname> and "
+"<varname>validatorTimeout</varname> to be used with default values within "
+"Remoting instead of the configured values. In correcting this issue, the "
+"<filename>JMSRemotingConnection.java</filename> file has been updated so "
+"that when the <methodname> client.addConnectionListener</methodname> method "
+"is called within the <methodname>addConnectionListener</methodname> and "
+"<methodname>addPlainConnectionListener</methodname> methods, it also passes "
+"the configured parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:387
+#, no-c-format
+msgid ""
+"The <literal>default</literal> profile for JBoss without any reconfiguration "
+"uses the <classname>ClusteredConnectionFactory</classname> with a non-"
+"clustered post-office, however warnings would be logged about this behavior "
+"when the log messages should be reduced from a <varname>WARN</varname> level "
+"to an <varname>INFO</varname> level. The upgrade to this version of JBoss "
+"Messaging sees this implemented within the log."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:392
+#, no-c-format
+msgid ""
+"<classname>ClusterViewUpdateTest</classname> was broken and did not work "
+"correctly in previous releases with the cause being that the expected time "
+"until failure detection for some clustering tests was too long. In order to "
+"correct this the values for <varname>validatorPingPeriod</varname> and "
+"<varname>validatorPingTimeout</varname> have been changed to be 2 seconds "
+"each, combining to 4 seconds as the total time until expected failure "
+"detection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:397
+#, no-c-format
+msgid ""
+"Client connection parameters were not passed to the JBoss Remoting layer, "
+"forcing Remoting to use default values instead of user configured values. In "
+"order to use the correct values, <filename>JMSRemotingConnection.java</"
+"filename> has been updated so that the <methodname>Client."
+"addConnectionListener</methodname> method is used with <varname>listener</"
+"varname> and <varname>serverLocator.gerParameters()</varname> as parameters."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:402
+#, no-c-format
+msgid ""
+"Messages which are scheduled for delivery in the future were not being "
+"removed correctly when the <methodname>removeAllMessages()</methodname> "
+"method was being called, causing the messages to be re-queued as soon as the "
+"application server or queue is restarted. <filename>ChannelSupport.java</"
+"filename> has been updated to import the <filename>TimeoutExt</filename> "
+"library in order to cast the timeout value to <filename>TimeoutExt</"
+"filename> in order to obtain the reference value via the <methodname>get "
+"TimeoutTarget()</methodname> method. With this new reference value "
+"information, the scheduled messages can be correctly removed from the queue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:407
+#, no-c-format
+msgid ""
+"There was an occurrence where a user may deploy a clustered queue in a "
+"single node instead of in all the nodes and the failover process would not "
+"work because of this. When this occurred an <exceptionname>Illegal "
+"StateException</exceptionname> would be generated, however this was not "
+"considered enough of a prominent warning about not deploying clustered "
+"queues correctly. <filename>Messaging PostOffice.java</filename> has now "
+"been updated to log a warning which outlies that clustered destinations must "
+"be deployed on all nodes of a cluster, instead of generating an "
+"<exceptionname>Illegal StateException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:412
+#, no-c-format
+msgid ""
+"The <classname>Client</classname>, <classname>SecurityAspect.check()</"
+"classname> and <classname>ServerConnection FactoryEndpoint</classname> "
+"needed to be able to obtain TLC within a privileged block, otherwise an "
+"<exceptionname>Access ControlException</exceptionname> is produced. To fix "
+"this bug, the <methodname>settle</methodname>, <methodname>gettable</"
+"methodname> and other TLC methods have been set within security blocks; this "
+"prevents access denied exceptions from <classname>Client</classname>, "
+"<classname>SecurityAspect.check()</classname> and "
+"<classname>ServerConnection FactoryEndpoint</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:417
+#, no-c-format
+msgid ""
+"The logging of actions within JBoss Messaging did not include the logging of "
+"messages when they are moved to the expiry or dead letter queues as this was "
+"only logged at trace level. In order to add this enhanced level of logging, "
+"the <filename>ClientConsumer.java</filename> file has been updated to log "
+"warning messages and debug information pertaining to the move of messages to "
+"the expiry or dead letter queues; <filename>Server SessionEndpoint.java</"
+"filename> has also been updated in the same mannor."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:422
+#, no-c-format
+msgid ""
+"There was an error when a message was received under a X tx and the JBoss "
+"Messaging XAResource is prepared but not committed, a message could be "
+"received by another consumer in another transaction while the first is still "
+"in progress. The correct behavior is for JBoss Messaging to hold the message "
+"until the associated transaction is committed or rolled back, enabling "
+"duplication of message deliveries to be avoided. In the <filename>Delivery."
+"java</filename> file, messages are now marked with a boolean value detailing "
+"if they are for delivery with a X transaction and if this transaction is "
+"prepared and <filename>SimpleDelivery.java</filename> now implements this "
+"new information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:427
+#, no-c-format
+msgid ""
+"The <methodname>shutdownNow()</methodname> method was not synchronized and "
+"may cause a <exceptionname>NoSuchElementException</exceptionname> during "
+"runtime as a result. A synchronization block has been placed around the "
+"<methodname>shutdownNow()</methodname> code within "
+"<filename>OrderedExecutorFactory.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:432
+#, no-c-format
+msgid ""
+"There was an issue with the <classname>org.jboss.jms.server.messagecounter."
+"MessageCounter</classname> class not being able to be serialized as it "
+"caused an <exceptionname>UndeclaredThrowableException</exceptionname>. "
+"<filename>MessageCounter.java</filename> has been updated to now import and "
+"implement the <literal>Serializable</literal> library and be given a "
+"<varname>serialVersionUID</varname>, allowing the <classname>org.jboss.jms."
+"server.messagecounter.MessageCounter</classname> class to be serializable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:437
+#, no-c-format
+msgid ""
+"When the methods <methodname>unregisterSucker()</methodname> or "
+"<methodname>registerSucker()</methodname> was called a "
+"<exceptionname>ConcurrentModificationException</exceptionname> would be "
+"generated by the time the <literal>HashSet</literal> containing the "
+"<literal>suckers</literal> was iterated. The issue would present itself on "
+"clusters with a magnitude of nodes (for instance it appeared on a 8 node "
+"cluster but not a 4 node cluster). This bug was corrected by creating an "
+"iterator that used a private set of <literal>suckers</literal> for iteration "
+"through the <literal>HashSet</literal> of <literal>suckers</literal> in "
+"order to avoid the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:442
+#, no-c-format
+msgid ""
+"The bridge within JBoss Messaging would only retry connection creation to a "
+"remote destination after startup and if the remote provider was not "
+"available at startup, the bridge would fail to start. The <filename>Bridge."
+"java</filename> and <filename>BridgeService.java</filename> files have "
+"undergone extensive modification and now the <literal>factory</literal> is "
+"set to the <literal>bridge</literal> which undertakes the lookup itself "
+"instead of looking up the destinations."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:452
+#, fuzzy, no-c-format
+msgid "JBoss Cache"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:456
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1533\">JBPAPP-1533</"
+"ulink>: The JBoss Cache component of the Enterprise Application Platform has "
+"been upgraded to version 1.4.1.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:461
+#, no-c-format
+msgid ""
+"The <classname>JDBCCacheLoader</classname> implementation did not work with "
+"Sybase as it would try to set a null <varname>BLOB</varname> column which is "
+"unsupported within Sybase. To correct this the <filename>JDBCCacheLoader."
+"java</filename> file has been updated so that the Sybase Driver sets a null "
+"<varname>LONGVARBINARY</varname> value, allowing the "
+"<classname>JDBCCacheLoader</classname> implementation to work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:466
+#, no-c-format
+msgid ""
+"The <classname>JDBCExtCacheLoader</classname> did not handle persistent "
+"state transfer correctly since the <methodname>JDBCExtCacheLoader.storeState"
+"()</methodname> method would use available bytes on the "
+"<classname>MarshalledValueInputStream</classname> rather than on the "
+"<classname>ByteArrayInputStream</classname> when storing the persistent "
+"state. This was an issue because the <classname>MarshalledValueInputStream</"
+"classname> always returns a null value, meaning the persistent state was "
+"never written. In fixing this issue the <filename>JDBCExtendedCacheLoader."
+"java</filename> file has been modified so that it specifies to check for "
+"available space on the <classname>ByteArrayInputStream</classname>."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:476
+#, no-c-format
+msgid "JBoss Remoting"
+msgstr "JBoss Remoting "
+
+#. Tag: para
+#: Release_Notes_CP04.xml:480
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1531\">JBPAPP-1531</"
+"ulink>: The JBoss Remoting component of the Enterprise Application Platform "
+"has been upgraded to version 2.2.2.SP11. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:485
+#, no-c-format
+msgid ""
+"The <methodname>ConnectionValidator.run()</methodname> method had the "
+"ability to be called by a user before the private method "
+"<methodname>ConnectionValidator.start()</methodname> was called, resulting "
+"in the <varname>clientInvoker</varname> and <varname>timer</varname> fields "
+"being set to null and generating a <exceptionname>NullPointerException</"
+"exceptionname>. Within the <filename>ConnectionValidator.java</filename> "
+"file the fields are now checked to see if they are null upon execution of "
+"the <methodname>ConnectionValidator.run()</methodname> method, one or both "
+"are then an <exceptionname>IllegalStateException</exceptionname> is "
+"displayed to the user outlining that <methodname>ConnectionValidator.run()</"
+"methodname> should not be called directly but "
+"<methodname>addConnectionListener()</methodname> should be used instead."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:490
+#, no-c-format
+msgid ""
+"Two bugs existed within the <methodname>org.jboss.remoting.marshal."
+"MarshallerLoaderHandler.loadClassBytes()</methodname> method that prohibited "
+"remote classloading to work correctly with isolated EARs. The first was that "
+"a while loop in the code needed a break and the second was that the call to "
+"the <methodname>org.jboss.mx.loading.LoaderRepository.getCachedClass()</"
+"methodname> method should have been a general call to "
+"<methodname>LoaderRepository.loadClass()</methodname>. These two issues have "
+"been rectified with this Remoting update, allowing remote classloading to "
+"function correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:495
+#, no-c-format
+msgid ""
+"A bug existed within the Remoting component by which the RemotingClassLoader "
+"would always attempt to load a class over the network first if remote "
+"classloading was enabled, leading to conflicts if the class was available "
+"locally before. The code has been corrected to check locally first before "
+"looking remotely."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:500
+#, no-c-format
+msgid ""
+"The <classname>ServerInvokerCallbackHandler</classname> class would become "
+"unresponsive when calling the <methodname>BlockingCallbackStore.add()</"
+"methodname> method after locking the callback field with a true responce "
+"from the <methodname>persistCallback()</methodname> method. This would occur "
+"because the <methodname>BlockingCallbackStore.getNext()</methodname> needed "
+"to control the lock on the callback field to break the waiting period, "
+"however this could not be achieved because of the wait period. To fix this "
+"issue the call to the <methodname>BlockingCallbackStore.add()</methodname> "
+"method has been removed as it was an unnecessary step."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:505
+#, no-c-format
+msgid ""
+"The <classname>HTTPClientInvoker</classname> did not support Beginner's All-"
+"purpose Symbolic Instruction Code (BASIC) authentication for proxies when "
+"the proxy was configured through system property options of <methodname>http."
+"proxyHost</methodname> and <methodname>http.proxyPort</methodname>. The "
+"issue appears because the <classname>HTTPClientInvoker</classname> would not "
+"check for the existence of these options and in tern it would never create a "
+"<methodname>Proxy-Authorization</methodname> request header, which is "
+"necessary for normal operation. To fix this the "
+"<classname>HTTPClientInvoker</classname> has been modified to check for the "
+"existence of the <methodname>http.proxyHost</methodname> option and if it "
+"detects its use, creates a <methodname>Proxy-Authorization</methodname> "
+"request header."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:510
+#, no-c-format
+msgid ""
+"<classname>HTTPClientInvoker</classname> would generate a "
+"<exceptionname>NullPointerException</exceptionname> when the HTTP server "
+"returned an error code without any content and then the <methodname>java.net."
+"HttpUrlConnection.getInputStream()</methodname> method returned a null "
+"value. In order to improve control over this behavior, the new variable "
+"<varname>UNMARSHAL_NULL_STREAM</varname> has been added to the "
+"<classname>HTTPClientInvoker</classname>. If this variable is set to true "
+"(the default value) the default behavior is executed, however if it is set "
+"to false the call to the <methodname>UnMarshaller.read()</methodname> is "
+"skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:515
+#, no-c-format
+msgid ""
+"Within the <classname>InvokerRegistry</classname> an error existed "
+"associated with the sequencing of events and <classname>serverLocators</"
+"classname> would return a null on occasion. To correct this race condition, "
+"the sequencing of events within the <classname>InvokerRegistry</classname> "
+"has been rearranged so that references to "
+"<classname>transportClientFactoryClasses</classname> and "
+"<classname>clientLocators</classname> are governed by <classname>clientLock</"
+"classname> and references to <classname>transportServerFactoryClasses</"
+"classname>, <classname>serverLocators</classname>, and "
+"<classname>registeredLocators</classname> are governed by "
+"<classname>serverLock</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:520
+#, no-c-format
+msgid ""
+"A bug existed where the value in the client configuration map of the "
+"<classname>ConnectionValidator</classname> would be ignored when the "
+"overloaded <methodname>org.jboss.remoting.Client</methodname> method was "
+"called and the <varname>DEFAULT_PING_PERIOD</varname> variable value was "
+"placed into the metadata map passed to the <classname>ConnectionValidator</"
+"classname>. This has been corrected by updating <classname>org.jboss."
+"remoting.Client.addConnectionListener</classname> so that "
+"<varname>DEFAULT_PING_PERIOD</varname> is only passed if the value of "
+"<varname>VALIDATOR_PING_PERIOD</varname> within the client's configuration "
+"map has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:525
+#, no-c-format
+msgid ""
+"<classname>ConnectionValidator</classname> may become unresponsive then the "
+"<methodname>run()</methodname> method is executed and utilizes the "
+"<varname>lock</varname> variable. The methods within the <methodname>run()</"
+"methodname> method are meant to time out so that the <varname>lock</varname> "
+"variable can become available to the <methodname>notifyListeners()</"
+"methodname> in the event of a network failure; however <methodname>run()</"
+"methodname> may execute again before <methodname>notifyListeners()</"
+"methodname> can. The synchronization on the <varname>lock</varname> variable "
+"has been modified to avoid this issue to enable correct operation."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:530
+#, no-c-format
+msgid ""
+"During occurrences of the server being under heavy load, an "
+"<exceptionname>IllegalStateException</exceptionname> would occur within the "
+"<methodname>ConnectorValidator.run()</methodname> method because further "
+"synchronization on the <varname>lock</varname> variable was necessary. This "
+"issue was fixed during the rectification of the above problem."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:535
+#, no-c-format
+msgid ""
+"A synchronization error within the <classname>MarshalFactory</classname> was "
+"allowing a subsystem to add a marshaller at the same time as EJB3 was trying "
+"to extract one causing users to receive an "
+"<exceptionname>InvalidMarshallingResource</exceptionname> exception; this "
+"also applied to unmarshallers. The error has been fixed by updating the "
+"<filename>jboss-remoting.jar</filename> file to include synchronized static "
+"Maps within the <classname>MarshalFactory</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:540
+#, no-c-format
+msgid ""
+"The <classname>SocketServerInvoker</classname> had an issue when shutting "
+"down <varname>ServerThreads</varname> causing a user to possibly receive an "
+"invocation to a closed <classname>SocketServerInvoker</classname> on the "
+"client side, causing an <exceptionname>InvalidStateException</"
+"exceptionname>. Allowing this exception would cause a clustered EJB3 system "
+"to generate a <exceptionname>UndeclaredThrowableException</exceptionname> "
+"instead of trying alternative servers. To allow for alternatives to be "
+"attempted, an optional behavior of allowing the "
+"<classname>MicroRemoteClientInvoker</classname> to interpret an "
+"<exceptionname>InvalidStateException</exceptionname> as a "
+"<exceptionname>CannotConnectException</exceptionname>, allowing for other "
+"servers to be attempted."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:550
+#, fuzzy, no-c-format
+msgid "JBoss Web"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:554
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1493\">JBPAPP-1493</"
+"ulink>: An error would be shown on occasion by <emphasis>Internet Explorer</"
+"emphasis> because xml content would not be sent when <emphasis>PROPFIND</"
+"emphasis> requests were being used. This has been fixed by creating a new "
+"method within <filename>WebdavServlet.java</filename> that overrides the "
+"<methodname>DefaultServlet</methodname> implementation for servlet request "
+"processing and testing for input before launching the "
+"<methodname>DocumentBuilder</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:559
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1470\">JBPAPP-1470</"
+"ulink>: When using APR (Apache Portable Runtime) on any operating system "
+"other than those which use the Linux Kernal 2.4 or newer, the "
+"<parameter>deferAccept</parameter> option would be set to false in the "
+"<methodname>AprEndpoint</methodname>. This may lead to a "
+"<exceptionname>NullPointerException</exceptionname> as the "
+"<methodname>accepter</methodname> thread starts to process a request while "
+"also calling for a <methodname>poller</methodname> before initialization. "
+"The issue has been resolved by moving the <methodname>acceptor</methodname> "
+"threads to being executed last when starting the <methodname>AprEndpoint</"
+"methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:564
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1334\">JBPAPP-1334</"
+"ulink>: The JBoss Web component of the Enterprise Application Platform has "
+"been upgraded to version 2.0.0-6.CP09. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:569
+#, no-c-format
+msgid ""
+"If a war deployment included its own version of <filename>xalan.jar</"
+"filename> and <filename>xercesImpl.jar</filename> in <filename>WEB-INF/lib</"
+"filename>, the JBossWeb servlet container classloader returns JBoss provided "
+"version of the <literal>SAXParser</literal> from "
+"<methodname>SAXParserFactory.newInstance().newSAXParser()</methodname> "
+"rather than the version provided in the war deployment. To fix this bug the "
+"<filename>WebAppClassLoader.java</filename> has been updated to ensure the "
+"correct parser is used."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:579
+#, no-c-format
+msgid "JBoss Web Services"
+msgstr "JBoss Web Services"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:583
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1560\">JBPAPP-1560</"
+"ulink>: The JBoss Web Services <filename>glassfigh-jaxb</filename> component "
+"of the Enterprise Application Platform has been upgraded to version 2.1.4."
+"patch01. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:588
+#, no-c-format
+msgid ""
+"The <literal>com.sun.xml.bind.v2.runtime.reflect.opt</literal> package "
+"contains classes to optimize field and method access by dynamically "
+"generating classes. Within the <classname>Injector</classname> class there "
+"is a <literal>HashMap</literal> value that is wrapped within a "
+"<literal>WeakReference</literal> however since there is only a "
+"<literal>WeakReference</literal> to the <classname>Injector</classname> "
+"class within this, the <literal>HashMap</literal> is garbage collected. To "
+"fix this the reference has been changed to a <literal>StrongReference</"
+"literal> and in order to maintain the original requirements, the "
+"<classname>Injector</classname> is now passed a reference to the ClassLoader "
+"instead of containing one specifically."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:595
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1210\">JBPAPP-1210</"
+"ulink>: The JBoss Web Services component of the Enterprise Application "
+"Platform has been upgraded to version 2.0.1.SP2_CP05. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:600
+#, no-c-format
+msgid ""
+"When deploying JBoss Web Services within Enterprise Application Platform "
+"without internet access, <classname>JBossWSEntityResolver</classname> would "
+"not resolve any schemas causing Web Services for Remote Portlets (WSRP) to "
+"produce an error. This issue has been fixed by modifying "
+"<classname>JBossWSEntityResolver</classname> within <filename>WSDL11Reader."
+"java</filename> to resolve schemas locally when an internet connection is "
+"unavailable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:605
+#, no-c-format
+msgid ""
+"WSProvide would ignore a <literal>SOAPBinding</literal> declaration "
+"specified in the EJB3 stateless session bean. To correct this and allow "
+"<literal>SOAPBinding</literal> to work as expected the following files have "
+"been modified: <filename>WSDLGenerator.java</filename>, "
+"<filename>SOAPEndpoint.java</filename>, <filename>Constants.java</filename>, "
+"<filename>WSDLWriter.java</filename>, <filename>SOAPBindingTestCase.java</"
+"filename> and <filename>WSDL11Writer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:610
+#, no-c-format
+msgid ""
+"The component <emphasis>Xerces</emphasis> of JBoss Web Services has a "
+"feature that optimizes the parsing of messages called <methodname>Deffered "
+"Node Expansion</methodname>.This defers node expansion until the nodes are "
+"accessed, improving performance where not all nodes need to be visited. "
+"However memory overheads are increased, which can be considerable for large "
+"messages."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:613
+#, no-c-format
+msgid ""
+"This release grants the user an option to disable the <methodname>Deffered "
+"Node Expansion</methodname> feature and have all nodes expand. To achieve "
+"this the following system property needs to be set:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:616
+#, no-c-format
+msgid "-Dorg.jboss.ws.disable_deferred_node_expansion=true"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:619
+#, no-c-format
+msgid ""
+"A regression with <literal>TCK5 SAAJ</literal> in the <classname>SOAPBody</"
+"classname> class was introduced with a fix to a previous bug and this has "
+"now been rectified by modifying the <filename>SOAPBodyImpl.java</filename> "
+"file to perform a <code>break</code> after assigning the "
+"<varname>childElement</varname> property."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:624
+#, no-c-format
+msgid ""
+"The end points for a <literal>transport-guarantee</literal> that is set to "
+"be confidential would see an attempt to exactly map the URL pattern in the "
+"WSDL. However since the servlet and security constraints will not be defined "
+"exactly the same a bug occurred whereby JBoss Web Services would assume the "
+"<literal>transport-guarantee</literal> was not confidential when generating "
+"the address, causing the WSDL to be generated with a http address. The "
+"<literal>transport-guarantee</literal> would still be enforced by JBoss Web "
+"Services as confidential but the WSDL would contain the wrong address, "
+"leading to clients attempting to connect to an incorrect address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:627
+#, no-c-format
+msgid ""
+"In order to rectify this occurrence, the <filename>MetaDataBuilder.java</"
+"filename> file has been modified so that when testing the servlet pattern it "
+"also tests correctly for the security constraint instead of assuming both "
+"with be of the same value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:632
+#, no-c-format
+msgid ""
+"When creating messages in SOAP 1.2 without attachments, the "
+"<classname>SOAPMessageImpl</classname> class sets the <varname>contentType</"
+"varname> variable to <literal>text/xml</literal>, which was incorrect. This "
+"has now been rectified by amending <varname>contentType</varname> to use the "
+"value <literal>application/soap+xml</literal> by adding the "
+"<methodname>getSAPContentType()</methodname> method to "
+"<filename>SOAPMessageImpl.java</filename> and updating "
+"<filename>DispatchImpl.java</filename> to correctly reference the SOAP "
+"message context."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:638
+#, no-c-format
+msgid ""
+"Deployments of JAX-WS nature would fail for JBoss AOP instrumented "
+"endpoints, generating an <exceptionname>IllegalAnnotationsException</"
+"exceptionname> as JBoss Web Services attempted to process the JBoss AOP "
+"methods. <filename>JAXWSMetaDataBuilder.java</filename> has been updated to "
+"mark JBoss AOP methods as synthetic which allows them to be skipped."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:643
+#, no-c-format
+msgid ""
+"WSDL dynamic address replacement was not working correctly in previous "
+"versions of the Enterprise Application Platform since port and protocol "
+"numbers were not being considered. The <filename>WSDLRequestHandler.java</"
+"filename> file has been modified to use a new URL and protocol instead of "
+"the original URL and protocol in order to use the dynamically generated port "
+"and protocol numbers."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:648
+#, no-c-format
+msgid ""
+"In converting WSDL to Java, anonymous types that are nested within anonymous "
+"types generated a JAX-RPC mapping that did not match the source. The "
+"<filename>MappingFileGeneratorHelper.java</filename> file has been corrected "
+"to ensure that the generated mapping matches the source of the information."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:653
+#, no-c-format
+msgid ""
+"JAAS certificate authentication support was not supported in the JBoss Web "
+"Services Security implementation, meaning that authentication via this "
+"method could not take place based on the certificate the client used to sign "
+"the message. Support for this has been added to JBoss Web Services and in "
+"tern the Enterprise Application Platform with this component upgrade."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:658
+#, no-c-format
+msgid ""
+"When the default port for a protocol was being used within JBoss Web "
+"Services, the port number still appeared at the end of the URL even though "
+"this was unnecessary. In order to remove the port number from the end of the "
+"URL, the <filename>MetaDataBuilder.java</filename> has been modified for "
+"each individual service that uses the default port."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:663
+#, no-c-format
+msgid ""
+"When JBoss Web Services is being used as a client, the information within "
+"the <methodname>DOMUtils.clearThreadLocals()</methodname> method was not "
+"cleared for incoming client calls. In order to fix this the call to "
+"<methodname>DOMUtils.clearThreadLocals()</methodname> has been moved to the "
+"<classname>MessageContextAssociation</classname> class and is executed once "
+"the last message has been processed. The files that have been updated in "
+"order to incorporate the fix are: <filename>DOMUtils.java</filename>, "
+"<filename>XMLContent.java</filename>, <filename>ProviderImpl.java</"
+"filename>, <filename>MessageContextAssociation.java</filename>, "
+"<filename>MessageContextJAXWS.java</filename> and "
+"<filename>RequestHandlerImpl.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:668
+#, no-c-format
+msgid ""
+"When the <varname>webServiceHost</varname> property was not set, the <ulink "
+"url=\"http://localhost:8080/jbossws/services \">http://localhost:8080/"
+"jbossws/services</ulink> page presented the host name as "
+"<exceptionname>jbossws.undefined.host</exceptionname>. A "
+"<methodname>createAddress</methodname> method has been added to "
+"<filename>ContextServlet.java</filename> which dynamically updates the WSDL "
+"and XSD files with the address from the request URL before displaying "
+"information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:674
+#, no-c-format
+msgid ""
+"The JBoss Web Services upgrade 2.0.1.SP2_CP05 also includes the security fix "
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>, discussed in the Security Issue section."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:683
+#, no-c-format
+msgid "JBoss Seam"
+msgstr "JBoss Seam"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:687
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1553\">JBPAPP-1553</"
+"ulink>: When the <methodname>parseRequest()</methodname> method of the "
+"<classname>org.jboss.seam.web.MultipartRequest</classname> class uploaded a "
+"large file, there were occurrences when this would cause an endless loop and "
+"use 100% of the computers CPU. In order to break out of the loop, a "
+"<varname>loopCounter</varname> has been implemented within the "
+"<filename>MultipartRequest.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:692
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1494\">JBPAPP-1494</"
+"ulink>: The portal example that was previously included with the Seam "
+"Enterprise Application Platform distribution has been removed in order to "
+"avoid confusion that Seam 1.2.1 included with the EAP supports portal."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:697
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1044\">JBPAPP-1044</"
+"ulink>: After basic interaction with the Seam examples <filename>chatroom</"
+"filename>, <filename>mail</filename>, <filename>registration</filename>, "
+"<filename>booking</filename> and <filename>dvdstore</filename> would "
+"generate a <exceptionname>NullPointerException</exceptionname> during "
+"undeployment. In correcting this issue, the <filename>RootInterceptor.java</"
+"filename> file was updated to check if an applications context still active "
+"upon undeployment and deal with this appropriately."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:705
+#, no-c-format
+msgid "JBoss Hibernate"
+msgstr "JBoss Hibernate"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:709
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1580\">JBPAPP-1580</"
+"ulink>: The JBoss Hibernate Core component of the Enterprise Application "
+"Platform has been upgraded to version 3.2.4.SP1.CP07. A list of the included "
+"fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:714
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1628\">JBPAPP-1628</"
+"ulink>: In an earlier fix to Hibernate the <methodname>org.hibernate.jdbc."
+"AbstractBatcher#closeQueryStatement()</methodname> method was changed to "
+"check for the existence of the prepared statement in the "
+"<classname>statementsToClose</classname> collection instead of closing it "
+"unconditionally. This has now caused a properties leak as the "
+"<methodname>org.hibernate.persister.entity."
+"AbstractEntityPersister#processGeneratedProperties()</methodname> used "
+"<methodname>org.hibernate.jdbc.AbstractBatcher#closeQueryStatement()</"
+"methodname> and the statement within <methodname>org.hibernate.persister."
+"entity.AbstractEntityPersister#processGeneratedProperties()</methodname> is "
+"not added to the <classname>statementsToClose</classname> collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:717
+#, no-c-format
+msgid ""
+"<filename>AbstractEntityPersister.java</filename> has been updated to "
+"execute a prepared statement on the result set and after calculating the "
+"<varname>propValue</varname> the result set is closed if it is not null; "
+"ensuring that no leak can occur."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:722
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1582\">JBPAPP-1582</"
+"ulink>: A new Sybase dialect called <classname>SybaseASE15Dialect</"
+"classname> is included with this CP release to support Sybase ASE 15 and "
+"this dialect now becomes apart of the Enterprise Application Platform "
+"certified configuration. Previous Sybase dialects are now considered "
+"deprecated and may be removed from future releases; however support will "
+"still be maintained for users who do not wish to move to the new dialect."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:742
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1524\">JBPAPP-1524</"
+"ulink>: The Sybase functions <methodname>second()</methodname>, "
+"<methodname>minute()</methodname>, <methodname>hour()</methodname> and "
+"<methodname>extract()</methodname> caused a "
+"<exceptionname>GenericJDBCException</exceptionname> when used. Moving these "
+"functions from the <filename>SQLServerDialect.java</filename> file to the "
+"<filename>SybaseDialect.java</filename> file allows for these functions to "
+"work correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:757
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1519\">JBPAPP-1519</"
+"ulink>: Sybase does not support the operation <emphasis>on cascade delete</"
+"emphasis> while SQL Server does. To make sure that both operate correctly "
+"the <filename>SQLServerDialect.java</filename> file has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns true and <filename>SybaseDialect.java</filename> has been updated to "
+"include a new <methodname>supportsCascadeDelete()</methodname> method which "
+"returns false."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:762
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1496\">JBPAPP-1496</"
+"ulink>: A memory leak existed because of an unclosed <emphasis>ResultSet</"
+"emphasis> when using the <emphasis>Identity</emphasis> generator option. To "
+"close the memory leak, the <emphasis>ResultSet</emphasis> is checked to make "
+"sure it is closed before returning the generated identity value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:767
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1480\">JBPAPP-1480</"
+"ulink>: Hibernate would attempt to read from an invalid column in the "
+"collection result set when the following conditions were present:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-900\">JBPAPP-900</"
+"ulink>: The SQL default configuration had errors, causing an issue within "
+"hsqldb which uses this configuration. The issue with the default "
+"configuration has now been corrected."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:772
+#, no-c-format
+msgid "Instances of a subclass were contained in a collection."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:777
+#, no-c-format
+msgid ""
+"The subclasses were single-table and used a &lt;join&gt; (table-per-subclass "
+"with discriminator)."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:782
+#, no-c-format
+msgid ""
+"The &lt;join&gt; portion of the subclass contained at least 3 of its own "
+"columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:787
+#, no-c-format
+msgid ""
+"The &lt;join&gt; tables were fetched by select and not the default method "
+"for this task."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:792
+#, no-c-format
+msgid ""
+"To fix this issue the <filename>AbstractEntityPersister.java</filename> file "
+"was updated so that the <varname>columnNumber</varname> variable is passed "
+"to the <methodname>subclassColumnSelectableClosure</methodname> method "
+"instead of an increment of the for loop variable <varname>i</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:795
+#, no-c-format
+msgid ""
+"<filename>CollectionTest.java</filename> has also been updated and "
+"<filename>Animal.java</filename>, <filename>Mammal.java</filename>, "
+"<filename>Zoo.hbm.xml</filename> and <filename>Zoo.java</filename> have been "
+"added for testing purposes."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:800
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1467\">JBPAPP-1467</"
+"ulink>: A <exceptionname>PropertyValueException</exceptionname> would occur "
+"when merging a detached instance of a <classname>One</classname> class that "
+"contains a new <classname>Many</classname> class instance and if and only if "
+"the <classname>One</classname> class was previously loaded as a proxy during "
+"the same transaction. The files <filename>StatefulPersistenceContext.java</"
+"filename>, <filename>BackrefPropertyAccessor.java</filename>, "
+"<filename>BackrefTest.java</filename> and <filename>Child.java</filename> "
+"have been updated to check for the proxy issue in the merging and once the "
+"proxy entity is found the <methodname>mergeMap</methodname> is updated to "
+"deal with this eventuality."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:805
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1365\">JBPAPP-1365</"
+"ulink>: A bug existed within Hibernate Core where the "
+"<methodname>addDuplicateAlias</methodname> method would include an entry "
+"into the hash map even when the <varname>classAlias</varname> variable was "
+"set to null; causing a <exceptionname>NullPointerException</exceptionname> "
+"when the <methodname>CrazyJPARRequirements()</methodname> method is called. "
+"To correct this issue the <filename>FromClause.java</filename> file has been "
+"modified to correct the <methodname>addDuplicateAlias</methodname> method by "
+"testing if the <varname>alias</varname> variable is null and if it is not "
+"null then the <methodname>fromElementByClassAlias.put</methodname> is now "
+"called, instead of this method being called even if <varname>alias</varname> "
+"contained a null value."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:810
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1259\">JBPAPP-1259</"
+"ulink>: When using <methodname>dynamicUpdate</methodname> to generate SQL "
+"and the version field is specified by the user to not be updated, the "
+"<methodname>AbstractEntityPersiter.getPropertiesToUpdate</methodname> method "
+"would still update the field causing exceptions to appear in certain cases. "
+"Within this Enterprise Application Platform update "
+"<filename>AbstractEntityPersister.java</filename> has been corrected to "
+"check if the user has explicitly said that the version field should not be "
+"updated and does not update the field if this is the case."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:815
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1251\">JBPAPP-1251</"
+"ulink>: Filters that were enabled for Hibernate did not apply to update and "
+"delete Hibernate Query Language (HQL) statements. In correcting this bug "
+"numerous files have been updated to ensure that the filters work correctly. "
+"This fix is related to JBPAPP-1250 below."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:820
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1250\">JBPAPP-1250</"
+"ulink>: When creating queries with subqueries in Hibernate, any added "
+"filters would only apply to the top-level of the query and not to any "
+"subquery component or beneath. The Criteria code and HQL code associated "
+"with this has undergone significant re-tooling to allow filters to work "
+"appropriately with subqueries and extent as far as the Hibernate Query "
+"Language does."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:823
+#, no-c-format
+msgid ""
+"Though this is a significant fix to Hibernate, it has been included within "
+"this CP release because of its undeniable advantage to all users and ensures "
+"that filters on queries operate how a user would expect them to."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:833
+#, no-c-format
+msgid "JBoss Transaction Service (JBossTS)"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:837
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1510\">JBPAPP-1510</"
+"ulink>: The JBoss Transaction Service component of the Enterprise "
+"Application Platform has been upgraded to version 4.2.3.SP5.CP04. A list of "
+"the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:842
+#, no-c-format
+msgid ""
+"The <classname>AppServerJDBCXARecovery</classname> class was using the Java "
+"1.5 syntax when it should compile with Java 1.4. This error has been "
+"rectified with this release by modifying the "
+"<filename>AppServerJDBCXARecovery.java</filename> file to use Java 1.4."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:847
+#, no-c-format
+msgid ""
+"When the Application Server started, the transaction manager may have "
+"deployed before the datasources, starting a recovery pass and causing "
+"exceptions. This issue has been rectified by modifying the "
+"<classname>AppServerJDBCXARecovery</classname> class and adding the "
+"<methodname>createConnection() throws SQLException</methodname> method which "
+"makes sure a connection exists before deploying the transaction manager."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:852
+#, no-c-format
+msgid ""
+"There were occurrences when the <classname>AppServerJDBCXARecovery</"
+"classname> class would contain information to an invalid connection because "
+"of database failure. This bug was fixed with the same correction as the "
+"above issue, which is, by modifying the <classname>AppServerJDBCXARecovery</"
+"classname> class and adding the <methodname>createConnection() throws "
+"SQLException</methodname> method which makes sure a connection exists."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:857
+#, no-c-format
+msgid ""
+"The <methodname>beforeCompletion</methodname> method would be run even when "
+"the <literal>tx</literal> state was set to <varname>ABORT_ONLY</varname>, "
+"when this method should only be executed before commit attempts and not "
+"rollbacks. In order to correct this and make sure the "
+"<methodname>beforeCompletion</methodname> method does not get executed for "
+"rollback events the <filename>SubordinateAtomicAction.java</filename> file "
+"has been modified."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:862
+#, no-c-format
+msgid ""
+"<methodname>TransactionImple.doOnePhaseCommit</methodname> would generate a "
+"<exceptionname>HeuristicRollbackException</exceptionname> when the commit "
+"was aborted. This meant that <methodname>XATerminatorImple.commit</"
+"methodname> was unable to distinguish between a successful rollback and one "
+"in error. Fixed in this CP release, the <filename>TransactionImple.java</"
+"filename> file has been modified so that the <methodname>TransactionImple."
+"doOnePhaseCommit</methodname> method now generates a "
+"<exceptionname>RollbackException</exceptionname> instead of a heuristic when "
+"a successful rollback is performed."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:867
+#, no-c-format
+msgid ""
+"When the <literal>tx</literal> had been set to <varname>rollbackOnly</"
+"varname> and the <methodname>XATerminatorImple.prepare</methodname> method "
+"was called, a <exceptionname>XA_RBROLLBACK</exceptionname> exception would "
+"be generated and yet the rollback would not be undertaken and the "
+"<literal>tx</literal> reference would be removed meaning no cleanup via the "
+"<methodname>commit</methodname> or <methodname>rollback</methodname> methods "
+"were possible. The <filename>XATerminatorImple.java</filename> file has been "
+"updated to correct this by improving the cleanup and exception reporting for "
+"rollbacks in <methodname>XATerminatorImple.prepare</methodname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:872
+#, no-c-format
+msgid ""
+"The <methodname>SubordinateAtomicAction.doPrepare</methodname> method called "
+"<methodname>beforeCompletion</methodname> but did not call "
+"<methodname>afterCompletion</methodname> when the return status was "
+"<literal>Read Only</literal>. <filename>SubordinateAtomicAction.java</"
+"filename> now has corrected synchronization handling for transaction "
+"termination."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:877
+#, no-c-format
+msgid ""
+"The JCA coordinator did not call synchronizations during the phase commit "
+"cycle (1PC). Synchronization has been added to the JCA coordinator through "
+"the modification of the <filename>SubordinateAtomicAction.java</filename> "
+"file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:882
+#, no-c-format
+msgid ""
+"Coordinator methods would not perform a cleanup correctly. In order to "
+"rectify this cleanup routines have been added to the "
+"<methodname>phase2Commit</methodname> and <methodname>phase2Abort</"
+"methodname> methods."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:892
+#, no-c-format
+msgid "Security Issues"
+msgstr "安全问题"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:896
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1548\">JBPAPP-1548</"
+"ulink>: An exploit existed within the JBoss Web Services component of the "
+"Enterprise Application Platform that would allow anyone to view any xml file "
+"from any location if <literal>&amp;resource=path/of/an/xmlfile.xml</literal> "
+"was applied to the end of any WSDL (Web Services Definition Language) access "
+"URL. The <filename>WSDLRequestHandler.java</filename> file has been updated "
+"to only allow the parent of a WSDL file, a servers data or WSDL or "
+"overridden WSDL publish directories access to xml file resources. Additional "
+"test files are also included which were created to ensure proper operation "
+"was being undertaken. (CVE-2009-0027 )"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:908
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1649\">JBPAPP-1649</"
+"ulink>: The documentation on the isolation of JGroup channels within the "
+"Server Configuration Guide was missing two parameters specific to the "
+"Enterprise Application Platform 4.3 distribution. The parameters of "
+"<varname>-Djboss.messaging.controlchanneludpport</varname> and <varname>-"
+"Djboss.messaging.datachanneludpport</varname> have been includedin section "
+"19.7.10 with example ports and the text addressing the concern of "
+"<emphasis>Why do I need to change the multicast port if I change the address?"
+"</emphasis> has been updated to reflect what is happening in an improved way."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:914
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1498\">JBPAPP-1498</"
+"ulink>: File set information within the Getting Started Guide (sections "
+"2.2.2 and 2.2.3) was outdated and required new information added and old "
+"information removed from the <literal>default</literal> server configuration "
+"file set and the contents of the <literal>conf</literal>, <literal>deploy</"
+"literal> and <literal>all</literal> directory sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:919
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1472\">JBPAPP-1472</"
+"ulink>: The instructions for adding SSL to EJB 2.1 in the Server "
+"Configuration Guide were incorrect as they did not include code pertaining "
+"to marshalling. The appropriate code has now been added to the instructions "
+"in section 9.8.2.3."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:924
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1362\">JBPAPP-1362</"
+"ulink>: The Getting Started Guide section 2.3 has been updated to include "
+"information about the <code>-b</code> option (and equivalents) that can be "
+"used on the command line to change the binding addresses of the Enterprise "
+"Application Platform for remote connectivity."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:929
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1346\">JBPAPP-1346</"
+"ulink>: Confusion existed when starting and stopping a <code>ZIP</code> "
+"installation of the server locally or remotely because a different username "
+"and password may be used. The Getting Started Guide has now been updated to "
+"explain that user credentials for the operating system will be used for "
+"local authentication and JBoss server credentials for remote authentication."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:937
+#, no-c-format
+msgid "Core Server"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:941
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1670\">JBPAPP-1670</"
+"ulink>: The JacORB component of the Enterprise Application Platform has been "
+"upgraded to version 2.3.0jboss.patch6-brew. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:946
+#, no-c-format
+msgid ""
+"A bug existed that would cause <filename>JacORB 2.3.0.jboss5</filename> to "
+"become unresponsive during shutdown. In rectifying this issue, the "
+"<filename>POA.java</filename> file has been modified so that instead of "
+"executing:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:949
+#, no-c-format
+msgid "throw new org.omg.CORBA.OBJECT_NOT_EXIST();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:950
+#, no-c-format
+msgid "the following is now executed:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:953
+#, no-c-format
+msgid "throw new ObjectNotActive();"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:958
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1636\">JBPAPP-1636</"
+"ulink>: Affecting only third party adapters was an issue when one of these "
+"adapters handled the scheduling of work to be performed. The "
+"<classname>ExecutionContext</classname> class contained a value in seconds, "
+"from which the <methodname>getCompletionTimeout</methodname> method of "
+"<classname>org.jboss.resource.work.WorkWrapper</classname> obtains its "
+"information. An issue arises with <methodname>getCompletionTimeout</"
+"methodname> expecting the value to be in milliseconds, creating an error "
+"where the initially set timeout value may be 6 seconds but be passed to the "
+"thread pool as 6 milliseconds. The <filename>WorkWrapper.java</filename> "
+"file has been updated and correctly converts the timeout value from seconds "
+"to milliseconds."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:963
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1635\">JBPAPP-1635</"
+"ulink>: The <classname>OracleExceptionSorter</classname> has been enhanced "
+"for this release with new error codes of 17002 (connection reset) and 17008 "
+"(connection closed) now able to be handled. These enhancements have been "
+"applied to the <filename>OracleExceptionSorter.java</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:968
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1602\">JBPAPP-1602</"
+"ulink>: A <exceptionname>ConcurrentModificationException </exceptionname> "
+"would occur when a classloader would be undeployed while another user was "
+"attempting to load a class from the package. This error arose because the "
+"<classname>packagesMap</classname> within "
+"<classname>UnifiedLoaderRepository3</classname> had a <classname>TreeSet</"
+"classname> that was not correctly synchronized with changes. In order to "
+"rectify this, the <filename>ClassLoaderUtils.java</filename> file has been "
+"updated to import the <classname>Collections</classname> library and use the "
+"<methodname>synchronizedSet</methodname> method of the library in returning "
+"the <methodname>TreeSet</methodname> of the <methodname>newPackageSet</"
+"methodname> method."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:973
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1540\">JBPAPP-1540</"
+"ulink>: Within the cluster section of the Enterprise Application Platform, "
+"the <classname>GossipRouter</classname> and <classname>GossipClient</"
+"classname> (TCPGOSSIP) did not have socket read timeouts, socket linger "
+"timeouts and backlog set to provide the best behavior when heavily utilized "
+"or under network situations in need of improvement. This fix provides "
+"default values and configuration options for these in order to avoid "
+"problematic situations."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:978
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1539\">JBPAPP-1539</"
+"ulink>: When running parallel instances of the Enterprise Application "
+"Platform on Linux a bug existed where messages between the JGroups component "
+"of each instance would be picked up by both because all messages sent to the "
+"port number for Multicast Sockets would be picked up by both instances. The "
+"issue has been fixed by re-writing the code for Multicast Sockets so that "
+"the constructor uses a group address along with the port number as "
+"identifiers. This ensures that an instance of the EAP only receives messages "
+"pertaining to its specific group and thus inhibits channel crosstalk."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:983
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1538\">JBPAPP-1538</"
+"ulink>:The Probe Client had not been updated to use the same address as the "
+"Probe Listener does which is now 224.0.75.75. Correcting this issue, the "
+"Proble Client now uses 224.0.75.75 instead of 224.0.0.75 which allows the "
+"client and the listener to work together correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:988
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1535\">JBPAPP-1535</"
+"ulink>: The JDBCExtCacheLoader didn't handle persistent state transfer "
+"correctly since the <methodname>storeState</methodname> method would use "
+"available space on the <classname>MarshalledValueInputStream</classname> "
+"instead of on the <classname>ByteArrayInputStream</classname>. To correct "
+"the stream usage, <filename>JDBCExtendedCacheLoader.java</filename> has been "
+"updated to store the new state using the <varname>in_stream</varname> value "
+"as long as there is space available."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:993
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1534\">JBPAPP-1534</"
+"ulink>: The JDBCCacheLoader didn't work with Sybase as it tried to set a "
+"null <varname>BLOB</varname> (Binary Large OBject) column which is "
+"unsupported in Sybase. To correct this the <filename>JDBCCacheLoader.java</"
+"filename> and <filename>AdjListJDBCCacheLoader.java</filename> files have "
+"been updated to select the Sybase Driver if Sybase is to be used, ensuring "
+"that null values are set as <varname>LONGVARBINARY</varname> rather than "
+"<varname>BLOB</varname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:998
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1532\">JBPAPP-1532</"
+"ulink>: The JGroups clustering component of the Enterprise Application "
+"Platform has been upgraded to version 2.4.5. A list of the included fixes is "
+"as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1003
+#, no-c-format
+msgid ""
+"The probe listener within JGroups still used the old default address of "
+"224.0.0.75 instead of the new address of 224.0.75.75. The probe listener "
+"within JGroups has been updated with this release to use the correct default "
+"address."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1008
+#, no-c-format
+msgid ""
+"The MPING protocol which sends a multicast ping over TCP contained cross-"
+"talk in Linux. the MPING protocol has since been corrected to eliminate "
+"cross-talk on the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1013
+#, no-c-format
+msgid ""
+"A problem was encountered within JGroups when two distinct processes were "
+"setup on the same machine, each using a different stack with different UDP "
+"multicast addresses. The issue was that each process would not work "
+"correctly because of the other, as each process would receive incorrect "
+"datagrams in reference to the groups each joined. To correct this the "
+"<classname>MulticastSocket</classname> constructor is now used in "
+"combination with a <varname>SocketAddress</varname> when JGroups is used on "
+"the Linux platform."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1018
+#, no-c-format
+msgid ""
+"The <literal>Gossip Router</literal> component of JGroups provided options "
+"to set <literal>backlog</literal>, <literal>socket read timeout</literal> "
+"and <literal>socket linger timeout</literal> within the code, however these "
+"options are not available via the command line. This update of the JGroups "
+"component, now includes the availability of these options to be set through "
+"the command line."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1023
+#, no-c-format
+msgid ""
+"Within the <literal>Gossip Router</literal> component of JGroups "
+"<methodname>Math.min</methodname> was used in calculating the socket linger "
+"timeout which caused incorrect results since this meant that the socket "
+"linger timeout would always be 1. <literal>Gossip Router</literal> has been "
+"updated to instead use <methodname>Math.max</methodname> in the calculation "
+"of the socket linger timeout."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1028
+#, no-c-format
+msgid ""
+"The <classname>RouterStub</classname> and <classname>GossipRouter</"
+"classname> classes have the <varname>setSoLinger</varname> value set "
+"incorrectly to use a seconds value when <varname>setSoLinger</varname> uses "
+"millisecond values. This meant that a value of 500 was 500 seconds rather "
+"than 500 milliseconds. The <classname>RouterStub</classname> class has had "
+"its <varname>setSoLinger</varname> corrected and the "
+"<classname>GossipRouter</classname> class has had the <varname>setSoLinger</"
+"varname> value corrected and timouts configurable."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1035
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1530\">JBPAPP-1530</"
+"ulink>: The JCA adapter inflow did not roll back messages if a non-xa "
+"connection factory was being used within the JNDIProviderAdapter. In order "
+"to fix this issue the <filename>JmsServerSession.java</filename> file has "
+"been updated with added logic to the local transaction separation strategy "
+"as to allow for non-xa sessions to be rolled back using transaction session."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1040
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1521\">JBPAPP-1521</"
+"ulink>: The <classname>CleanShutdownInterceptor</classname> class would log "
+"a <exceptionname>GenericClusteringException</exceptionname> when the "
+"container had failed to shut down correctly or failed to start correctly and "
+"because of this behavior the error message displayed because of the "
+"exception should be updated to indicate that it may be an issue with the "
+"container failing to start instead of only failing to shut down. In this "
+"latest Enterprise Application Platform update, the error message has been "
+"updated to reflect both situations which may be the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1045
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1458\">JBPAPP-1458</"
+"ulink>: The JTA recovery configuration did not contain a line to enable "
+"JBoss Messaging (JBM) <classname>XAResourceRecovery</classname> even though "
+"it is stated in the JBM user guide. This CP release modifies the "
+"<filename>build-distr.xml</filename> file to all "
+"<classname>XAResourceRecovery</classname> to be enabled for JTA recovery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1050
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1479\">JBPAPP-1479</"
+"ulink>: Within the different distributions of the Enterprise Application "
+"Platform that are 4.2 and 4.3, both the <filename>JBossMQ</filename> and "
+"<filename>JBoss Messaging</filename> application policies have been present "
+"within the <filename>login-config.xml</filename> file, when "
+"<filename>JBossMQ</filename> is only included in the 4.2 distribution and "
+"<filename>JBoss Messaging</filename> is similarly only included in the 4.3 "
+"distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1053
+#, no-c-format
+msgid ""
+"This has been rectified in this release by modifying <filename>build.xml</"
+"filename> and <filename>login-config.xml</filename> to differentiate between "
+"requirements for each individual distribution."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1058
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1473\">JBPAPP-1473</"
+"ulink>: The "
+"<classname>IgnoreUndeployLegacyClusteredSessionNotificationPolicy</"
+"classname> within clustering didn't correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>, which would "
+"lead to the repeated calling of itself and eventually "
+"<exceptionname>StackOverflow</exceptionname> errors. In order to correct "
+"this the <filename>IgnoreUndeployLegacyClusteredSessionNotificationPolicy."
+"java</filename> file has been modified to correctly call "
+"<classname>isHttpSessionListenerInvocationAllowed</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1063
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1460\">JBPAPP-1460</"
+"ulink>: The JavaServer Faces (JSF) has been updated to version 1.2_10 for "
+"this Enterprise Application Platform release. This update corrects numerous "
+"bugs and details on these fixes can be found at <ulink url=\"https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html\">https://"
+"javaserverfaces.dev.java.net/nonav/rlnotes/1.2_10/changelog.html</ulink>"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1068
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1366\">JBPAPP-1366</"
+"ulink>: Creation of the EJB <filename>TIMERS</filename> table fails when the "
+"<option>Oracle</option> schema is specified. To correct this the "
+"<filename>GeneralPurposeDatabasePersistencePlugin.java</filename> file has "
+"been updated with a calling to an new <methodname>SQLUtil.fixConstraintName</"
+"methodname> function which changes all dots in a constraint name to "
+"underscores. This ensures that constraint names are compatible with Oracle."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1073
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1307\">JBPAPP-1307</"
+"ulink>: The Persistence Unit (PU) root was incorrectly detected within "
+"deployments that contained nested <filename>.jar</filename> files. The root "
+"PU was being detected as the first nested <filename>.jar</filename> "
+"encountered instead of being the deployment which contains the "
+"<filename>persistence.xml</filename> file. To make sure that the PU root is "
+"always set correctly, the <filename>JmxDeploymentUnit.java</filename> file "
+"has been updated with the removal of testing for the url being null and the "
+"<parameter>deploymentInfo.parent</parameter> not being null. This means that "
+"the url is now always taken straight from the "
+"<parameter>extractDescriptorUrl</parameter> of <filename>META-INF/"
+"persistence.xml</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1078
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1289\">JBPAPP-1289</"
+"ulink>: The JBoss JAXR component of the Enterprise Application Platform has "
+"been upgraded to version 1.2.0.SP2. A list of the included fixes is as "
+"follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1083
+#, no-c-format
+msgid ""
+"In the <filename>org.jboss.jaxr.juddi.JUDDIServlet</filename> and "
+"<filename>org.jboss.jaxr.juddi.transport.SaajTransport</filename> files the "
+"namespace value for <varname>xml:lang</varname> contained <literal>http://"
+"www.w3.org/TR/REC-xml/</literal>, which caused an exception within the metro "
+"stack. The namespace value should instead be null and this has been applied "
+"for this JAXR update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1090
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1275\">JBPAPP-1275</"
+"ulink>: The Xalan part of the Enterprise Application Platform has been "
+"upgraded from version 2.7.0 to 2.7.0.patch02. This upgrade removes the "
+"circumstance where an application which heavily used Xalan within large "
+"multi-threaded environments would encounter blocking situations."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-791\">JBPAPP-791</"
+"ulink>: The JBoss Web Services Component has been upgraded to version 2.0.1."
+"SP2_CP02. This upgrade incorporates various bug fixes and enhancements."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1095
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1267\">JBPAPP-1267</"
+"ulink>: <classname>UserTransaction</classname> (UT) was not able to be "
+"deployed with a clustered proxy that supported sticky transactions "
+"correctly. This has been fixed by modifying numerous files which make "
+"<classname>UserTransaction</classname> deployable with transaction sticky "
+"load balance policies."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1100
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1249\">JBPAPP-1249</"
+"ulink>: The JSF component of the Enterprise Application Platform has been "
+"upgraded to version 1.2_10. A list of the included fixes is as follows:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1105
+#, no-c-format
+msgid ""
+"A mixed EL expression ending with a literal failed to parse as a managed "
+"bean property value. The <filename>BeanBuilder.java</filename> file was "
+"updated with the removal of <code>ELUtils.getScope(this.expressionString, "
+"segment);</code> in order to fix this issue."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1110
+#, no-c-format
+msgid ""
+"<methodname>LifecycleImpl</methodname> and <methodname>RestoreViewPhase</"
+"methodname> forced the <methodname>responseComplete()</methodname> method "
+"for the status of an existing view. To correct this problem the "
+"<filename>RestoreViewPhase.java</filename> file has been edited with the "
+"code <code>facesContext.responseComplete();</code> removed and replaced with "
+"<code>facesContext.renderResponse();</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1115
+#, no-c-format
+msgid ""
+"For a &lt;h:dataTable&gt; tag which does not set the <varname>var</varname> "
+"attribute, if the UIData component is created using a binding and calls the "
+"<methodname>setVar()</methodname> method to set the <varname>var</varname> "
+"attribute, it would be overwritten as a null value by the &lt;h:"
+"dataTable&gt; tag. This bug has been fixed by modifying the "
+"<filename>HtmlTaglib21Generator.java</filename> file so that component "
+"properties are not set if the tag attribute has not been set."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1120
+#, no-c-format
+msgid ""
+"The <classname>BindingValidator</classname> would generate a "
+"<exceptionname>ConverterException</exceptionname> instead of a "
+"<exceptionname>ValidatorException</exceptionname>. For this update, "
+"<classname>BindingValidator</classname> has been modified to generate the "
+"correct exception; <exceptionname>ValidatorException</exceptionname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1125
+#, no-c-format
+msgid ""
+"The cause of a <classname>PostConstruct</classname> exception within the "
+"<classname>BeanBuilder</classname> was not communicated to the user "
+"correctly. To correct the issue so that no information is hidden from the "
+"user, the <exceptionname>ManagedBeanCreationException</exceptionname> has "
+"been updated to provide more information about the cause of the exception."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1130
+#, no-c-format
+msgid ""
+"An issue was present that would cause majarra to execute <filename>faces-"
+"config.xml </filename> initialization files twice, creating duplicate "
+"operations. This was caused since a record was not kept of which files had "
+"been initialized and which had not. File initialization tracking has been "
+"implemented to correct this issue and this has seen the modification of the "
+"following files: <filename>ConfigManager.java</filename>, "
+"<filename>ConfigureListener.java</filename>, <filename>WebConfiguration."
+"java</filename>, <filename>ConfigurationResourceProvider.java</filename>, "
+"<filename>MetaInfResourceProvider.java</filename>, "
+"<filename>RIConfigResourceProvider.java</filename> and "
+"<filename>WebResourceProvider.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1135
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.ApplicationObjectInputStream</"
+"classname> extends the functionality of <classname>java.io."
+"ObjectInputStream</classname> but failed to preserve the functionality as "
+"<classname>com.sun.faces.renderkit.ApplicationObjectInputStream</classname> "
+"would fail when primitives were used, unlike the <classname>java.io."
+"ObjectInputStream</classname> class which contains a special case to handle "
+"such a case. This would cause problems for <literal>UIComponents</literal>. "
+"<filename>ApplicationObjectInputStream.java</filename> has been updated to "
+"explicitly handle primitive cases and catch the "
+"<exceptionname>ClassNotFoundException</exceptionname> which may be generated."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1140
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.renderkit.html_basic.OutputLinkRenderer</classname> "
+"did not encode parameters correctly, missing the <literal>URLEncoding</"
+"literal>. <literal>URLEncoding</literal> has been added, correcting this "
+"bug, along with the parameter names."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1145
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.BaseTableRenderer</"
+"classname> did not allow for empty <varname>columnClasses</varname> when "
+"generating columns from user input. The issue was realizing when to create "
+"numerous columns rather just one; for instance if the user input "
+"<literal>foo, </literal> with a trailing space then the expected output "
+"would be one column with the name <literal>foo</literal> and another empty "
+"column. This was not the case though, as <literal>foo, </literal> would "
+"generate just one column with <literal>foo, </literal> in its entirety as "
+"the column name, instead of splitting the columns on the comma. This "
+"behavior has now been corrected so that <classname>com.sun.faces.renderkit."
+"html_basic.BaseTableRenderer</classname> no generates columns correctly, and "
+"in order to achieve this the following files have been updated: "
+"<filename>BasetableRenderer.java</filename>, <filename>GridRenderer.java</"
+"filename> and <filename>TableRenderer.java</filename>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1150
+#, no-c-format
+msgid ""
+"The <classname>com.sun.faces.renderkit.html_basic.MenuRenderer</classname> "
+"class did not correctly differentiate between <literal>Objects</literal>; "
+"for instance the different between <literal>Boolean</literal> and "
+"<literal>boolean</literal>, noting the capitalization of the first. The "
+"error was with the logic in <classname>UISelect</classname> and "
+"<classname>MenuRenderer</classname>. To correct this, proper use of the "
+"converter for these classes has been implemented to deal with Objects "
+"correctly."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1155
+#, no-c-format
+msgid ""
+"<classname>com.sun.faces.lifecycle.RestoreViewPhase</classname> called "
+"<methodname>DebugUtil.printTree</methodname> after restoring the view if "
+"debugging was enabled, causing incorrect initialization of calls when a "
+"listbox is being used and returning an incorrect value in the "
+"<classname>RenderResponse</classname> phase. Method calls have been "
+"restructured with the removal of references to the <methodname>DebugUtil."
+"printTree()</methodname> method from <filename>ViewHandlerImpl.java</"
+"filename> and <filename>RestoreViewPhase.java</filename> and "
+"<filename>RenderResponsePhase.java</filename> has been modified to call "
+"<methodname>DebugUtil.printTree</methodname> (if <varname>FINEST</varname> "
+"logging is enabled) at the end of the <classname>RenderResponse</classname> "
+"phase, fixing the issue (with the above changes also) and providing a more "
+"accurate view of the tree."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1159
+#, no-c-format
+msgid ""
+"<literal>CGLIB Enhanced UIComponents</literal> in a component tree would "
+"return a value of null for their class when calling <methodname>getPackage()"
+"</methodname> causing <classname>HtmlInputText.handleAttribute</classname> "
+"to fail as it relies on a not-nulll value. This issue has been corrected by "
+"ignoring a returned value of null from the <methodname>getPackage()</"
+"methodname> method for every instance in the codebase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1164
+#, no-c-format
+msgid ""
+"The <classname>UIComponentBase</classname> did not allow for the children of "
+"a tree to be iterated through in reverse order using a list iterator as it "
+"would produce an <exceptionname>IndexOutOfBoundsException</exceptionname> "
+"when the execution tries to calculate the size of the children. "
+"<methodname>ChildrenListIterator</methodname> method has been modified "
+"within the <classname>UIComponentBase</classname> class by changing the line "
+"of code <code>if ((index &lt; 0) || (index &gt;= list.size())) { </code> to "
+"<code>if ((index &lt; 0) || (index &gt; list.size())) {</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1169
+#, no-c-format
+msgid ""
+"Renderer kits for <filename>faces-config.xml</filename> were processed out "
+"of order depending on if <literal>ICEfaces</literal> or <literal>Mojara "
+"1.2_09</literal> is in use. This occurred due to containing all renderer DOM "
+"nods in a list associated with a namespace. This was done so that the "
+"renderer nodes could then be processed prior to the <literal>RenderKits</"
+"literal> being created and the nodes could be processed using the proper "
+"namespace. However, by placing all the renderers into this list, we lost the "
+"document ordering. The issue has been fixed by associating the renderer "
+"nodes with their owning document and processed in the parsing order."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1175
+#, no-c-format
+msgid ""
+"The <methodname>Class.getPackage()</methodname> method calls to synchronized "
+"methods, inhibiting scalability if the method has to be repeatedly executed. "
+"Use of the <methodname>Class.getPackage()</methodname> method has now been "
+"removed from <filename>UIComponent.java</filename>, <filename>RenderKitUtils."
+"java</filename> and <filename>HtmlComponentGenerator.java</filename>. "
+"Instead, the class name is now checked if it starts with the package name "
+"that is of interest, <classname>javax.faces.component.</classname>. This "
+"includes the components that are generated by the "
+"<classname>HtmlComponentGenerator</classname> since they are packaged in "
+"<classname>javax.faces.component.html</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1180
+#, no-c-format
+msgid ""
+"A bug presented itself in the <classname>RenderKitUtils</classname> class "
+"when a semicolon (<code>;</code>) followed a forward-slash (<code>/</code>) "
+"in a header Accept value (for instance: <code>text/;q=0.5</code>). To "
+"rectify this issue the <classname>RenderKitUtils</classname> class has been "
+"updated to assume <code>*</code> as the subtype for an Accept header that "
+"contains no subtype."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1187
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1224\">JBPAPP-1224</"
+"ulink>: Attribute default values in EJB were not set when in use with "
+"<literal>@Service</literal> and <literal>XMBean XML</literal> . In order to "
+"correct this the behavior has been re-written to improve the mimicking of "
+"<classname>ServerCreator</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1192
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1170\">JBPAPP-1170</"
+"ulink>: When the <methodname>getMBeanInfo</methodname> method is called "
+"within <classname>MBeanServerImpl</classname> and "
+"<classname>RawDynamicInvoker</classname>, the underlying exception to "
+"<exceptionname>NotCompliantMBeanException</exceptionname> is not expressed "
+"to the user. <filename>RawDynamicInvoker.java</filename> has now been "
+"updated to provide this useful information to the user."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1197
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1099\">JBPAPP-1099</"
+"ulink>: The <filename>commons-beanutils.jar</filename> file within the "
+"Enterprise Application Platform had the incorrect version in the "
+"<filename>manifest.mf</filename> file. Through the course of correcting this "
+"bug, it was found that the <literal>beanutils</literal> component was "
+"outdated and a newer version contained many advantages. In this update to "
+"the EAP <literal>beanutils</literal> has been upgraded to version 1.8.0, "
+"which sees the significant improvement that fixes a memory leak caused by a "
+"circular reference concerning the <classname>WeakHashMap</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1202
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1002\">JBPAPP-1002</"
+"ulink>: Bean Managed Transactions (BMT) Stateful Session Beans used to be "
+"logged when transactions were not completed between invocations. However "
+"this was an error as BMT Stateful Session Beans are allowed to have this "
+"occurrence and so this logging measure has been removed in this Enterprise "
+"Application Platform update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1207
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-996\">JBPAPP-996</"
+"ulink>: Discrepancies existed between the port schemes within the "
+"<filename>sample-bindings.xml</filename> file. These include:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-961\">JBPAPP-961</"
+"ulink>: JBoss Web has been upgraded to version 2.0.0.GA CP06."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1212
+#, no-c-format
+msgid ""
+"The remoting connectors were inserted in different places within the ports "
+"definition sections, making the comparison of the sections more difficult "
+"than was necessary."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1217
+#, no-c-format
+msgid ""
+"The <literal>ports-03</literal> section was missing the <literal>EJB "
+"remoting connector</literal> and the <literal>remoting connector</literal> "
+"sections."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1222
+#, no-c-format
+msgid ""
+"<literal>mq</literal> was used in the name property of the "
+"<varname>HAJNDIJMSProvider</varname> instead of <literal>jms</literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1227
+#, no-c-format
+msgid ""
+"The <literal>ports-01</literal>, <literal>ports-02</literal>, and "
+"<literal>ports-03</literal> schemes defined the <varname>timeout</varname> "
+"attribute twice in the <literal>JBoss Messaging</literal> section:"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1233
+#, no-c-format
+msgid "The above issues have been fixed appropriately in this update."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1238
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-713\">JBPAPP-713</"
+"ulink>: A Classloader leak existed causing a <errorname>OutOfMemoryError: "
+"PermGen</errorname> error. To correct this issue the Enterprise Application "
+"Platform now uses <filename>beanutils 1.8.0</filename> which fixes this "
+"<errorname>OutOfMemoryError</errorname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1243
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-529\">JBPAPP-529</"
+"ulink>: JMX source code was being exposed to the user when a "
+"<exceptionname>HTTP Status 500</exceptionname> exception would occur. To "
+"correct this, an error page <filename>genericError.jsp</filename> has been "
+"created and is now displayed whenever a <exceptionname>HTTP Status 500</"
+"exceptionname> exception occurs."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1252
+#, no-c-format
+msgid "Known Issues with this release"
+msgstr "本发行版本的已知问题"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1255
+#, no-c-format
+msgid "Following is a list of known issues at the time of release."
+msgstr "下面是发行时的已知问题列表。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1259
+#, no-c-format
+msgid "General Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1263
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>: Footnotes within documentation tables and lists do not appear within "
+"PDFs. This issue resides within FOP and currently no workaround exists. "
+"Where possible footnotes are not used in the circumstances mentioned, "
+"however in documents such as the Release Notes the web address of a JIRA is "
+"automatically generated as a footnote and places a number beside that of the "
+"JIRA, referencing a footnote that does not appear."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1268
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-885\">JBPAPP-885</"
+"ulink>: An issue exists where if <methodname>DefaultRedeliveryDelay</"
+"methodname> or <methodname>RedeliveryDelay</methodname> is set to a value "
+"apart from zero, messages will not be redelivered even though the method "
+"<methodname>session.rollback()</methodname> had been called. This issue will "
+"not be fixed because redelivery delay is handled on the server side and the "
+"message is already acknowledged before delivery of the message with a non "
+"durable subscription. For the Enterprise Application Platform, this means "
+"that redelivery delays with non durable subscriptions cannot be supported."
+msgstr ""
+
+#. Tag: title
+#: Release_Notes_CP04.xml:1276
+#, no-c-format
+msgid "Hibernate Known Issues"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1280
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1613\">JBPAPP-1613</"
+"ulink>: Null values for columns mapped as boolean in Hibernate, are "
+"persisted as zero instead of null. When the <methodname>PreparedStatement."
+"setNull( index, java.sql.Types.BIT ) </methodname> method is executed in the "
+"Sybase environment, Sybase JDBC converts the null value to a zero because "
+"Sybase does not allow null bit columns."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1285
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1555\">JBPAPP-1555</"
+"ulink>: Currently in Hibernate the SybaseDialect uses Blob and Clob where it "
+"should be set up to use image and text. Tests attaining to this currently "
+"fail with the message:"
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>：允许用子软件包的方式在同一台机器上设立多个实例。本发行版本里的 -bin "
+"文>件带有这个功能。"
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1288
+#, no-c-format
+msgid ""
+"The method com.sybase.jdbc2.jdbc.SybResultSet.getBlob(String) is not "
+"supported and should not be called."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1291
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1554\">JBPAPP-1554</"
+"ulink>: The <methodname>FumTest.testCompositeKeyPathExpressions()</"
+"methodname> method within Hibernate fails since Sybase currently only allows "
+"one column in a subquery select list, with the only exception to this being "
+"that a subquery in an <code>EXISTS()</code> predicate can have <code>*</"
+"code> as the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1294
+#, no-c-format
+msgid ""
+"The current workaround for this is to not use the HQL <methodname>elements()"
+"</methodname> method if the elements have a composite key. Instead the HQL "
+"should be reformatted to ensure there is no subquery with more than one item "
+"in the select list."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1299
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1546\">JBPAPP-1546</"
+"ulink>: When using Sybase, <methodname>SchemaExport</methodname> cannot be "
+"used to create stored procedures while in chained transaction mode. The "
+"suggested workaround for this case is to add the following code follwing the "
+"defining of the new stored procedure:"
+msgstr ""
+
+#. Tag: programlisting
+#: Release_Notes_CP04.xml:1302
+#, no-c-format
+msgid ""
+"&lt;database-object&gt;\n"
+"        &lt;create&gt;\n"
+"                sp_procxmode paramHandling, 'chained'\n"
+"        &lt;/create&gt;\n"
+"        &lt;drop/&gt;\n"
+"&lt;/database-object&gt;"
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1305
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1545\">JBPAPP-1545</"
+"ulink>: Currently ANSI joins fail when Hibernate is run in a Sybase "
+"environment and there are three or more joins where at least one of the "
+"joins involves a union."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
+"ulink>：允许用子软件包的方式在同一台机器上设立多个实例。本发行版本里的 -bin "
+"文>件带有这个功能。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1308
+#, no-c-format
+msgid ""
+"A workaround for this issue exists where it is reconmended that a user does "
+"not use <literal>join fetches</literal> involving <literal>union subclasses</"
+"literal>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1313
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1230\">JBPAPP-1230</"
+"ulink>: In the Sybase environment when creating a subquery with an alias in "
+"use, the query will be incorrectly generated and cause an "
+"<exceptionname>Incorrect syntax near the keyword 'as'</exceptionname> error. "
+"This bug impacts the following tests such that at present they are expected "
+"to fail: <classname>CriteriaQueryTest.testSubselect</classname>, "
+"<classname>CriteriaQueryTest.testDetachedCriteriaAsSubQuery</classname>, "
+"<classname>DynamicFilterTest.testCriteriaControl</classname> and "
+"<classname>DynamicFilterTest.testCriteriaSubqueryWithFilters</classname>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1316
+#, no-c-format
+msgid ""
+"The known workaround is to use a HQL query instead of using a "
+"<methodname>DetachedCriteria</methodname> method in a subquery."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1321
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1082\">JBPAPP-1082</"
+"ulink>: A limitation in the PostgreSQL JDBC driver causes a "
+"<exceptionname>javax.persistence.RollbackException</exceptionname>. This "
+"occurs when the <code>char</code> property is used without a value set as "
+"Hibernate then persists a string containing the character <code>\\u0000</"
+"code>, which causes PostgreSQL to generate an exception as it does not allow "
+"this character to be embedded in a string."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1324
+#, no-c-format
+msgid ""
+"Currently a workaround for persisting the <code>\\u0000</code> character in "
+"a <code>char</code> column using PostgreSQL does not exist. Instead it is "
+"reconmended that to persist a null value for the <code>char</code> property "
+"when it is uninitialized, the <methodname>java.lang.Character</methodname> "
+"method should be used."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1329
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1081\">JBPAPP-1081</"
+"ulink>: In the Entity Manager documentation it is stated that table aliases "
+"are supported in <code>update</code> clauses, however at present this is not "
+"the case. To fix this, the code has to be modified to remove the "
+"identification variable in SQL for PostgreSQL, Microsoft SQL 2005 and Sybase."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1334
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1068\">JBPAPP-1068</"
+"ulink>: When using Microsoft SQL and <code>@Type(type=\"text\")</code> in "
+"creating a table, the field is correctly created as <code>\"text\"</code> "
+"however when a delete operation is issued the field becomes set as a "
+"<varname>varchar</varname>, forcing the Microsoft SQL driver to return the "
+"error:"
+msgstr ""
+
+#. Tag: screen
+#: Release_Notes_CP04.xml:1337
+#, no-c-format
+msgid ""
+"The data types text and nvarchar are incompatible in the equal to operator."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1340
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1063\">JBPAPP-1063</"
+"ulink>: Currently MySQL does not support millisecond and microsecond "
+"measurements when returning database values such as <code>TIME</code> and "
+"<code>TIMESTAMP</code>."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1345
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-953\">JBPAPP-953</"
+"ulink>: Hibernate Core and Annotations do not currently support the "
+"Hypersonic 1.8.0.8 database. Support for the version 1.8.0.8 of the "
+"Hypersonic database is planned for future releases."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-735\">JBPAPP-735</"
+"ulink>: The JBoss Remoting component of the EAP has been upgraded to version "
+"2.2.2.SP8. This upgrade includes numerious bug fixes."
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1350
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-946\">JBPAPP-946</"
+"ulink>: Within the Hibernate Entity Manager three different "
+"<exceptionname>NullPointerExceptions</exceptionname> are being investigated "
+"in relation to the EJB3 configuration, transaction operations when they are "
+"extended and packaging."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1355
+#, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-906\">JBPAPP-906</"
+"ulink>: A bug exists within the Hibernate Core whereby the unstable "
+"synchronized Java6 <methodname>ClassLoader.loadClass</methodname> method is "
+"utilized creating a deserialized String. This causes a problem where if "
+"multiple threads are loading database rows containing arrays of strings, one "
+"thread is forced to undertake all the procedure while the other threads are "
+"left dormant."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1358
+#, no-c-format
+msgid ""
+"The implemented workaround for this issue is to use <code>-Dsun.lang."
+"ClassLoader.allowArraySyntax=true</code>, which can be a default setting "
+"within the <filename>run.conf</filename> file."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:1363
+#, fuzzy, no-c-format
+msgid ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Within the Hibernate component of the Enterprise Application "
+"Platform the HashMap and HashSet iteration order changed from past releases "
+"because of support for JDK 1.6. However this has meant that the order of "
+"columns in union clauses and union-subclasses has changed, generating a "
+"slight impact on the components performance."
+msgstr ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-909\">JBPAPP-909</"
+"ulink>: Within the Hibernate component of the EAP the HashMap and HashSet "
+"iteration order changed from past releases because of support for JDK 1.6. "
+"However this has meant that the order of columns in union clauses and union-"
+"subclasses has changed, generating a slight impact on the components "
+"performance."

Added: projects/docs/enterprise/4.3.4/readme/zh-CN/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/zh-CN/Revision_History.po	                        (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/zh-CN/Revision_History.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -0,0 +1,30 @@
+# translation of readme.po to
+# Language zh-CN translations for readme package.
+#
+# Automatically generated, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: readme\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"PO-Revision-Date: 2008-07-31 10:40+1000\n"
+"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
+"Language-Team:  <en at li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Generator: KBabel 1.11.4\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
+
+#. Tag: title
+#: Revision_History.xml:6
+#, no-c-format
+msgid "Revision History"
+msgstr ""
+
+#. Tag: author
+#: Revision_History.xml:12
+#, no-c-format
+msgid "<firstname></firstname> <surname></surname> <email></email>"
+msgstr ""

Modified: projects/docs/enterprise/4.3.4/readme/zh-CN/readme.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/zh-CN/readme.po	2009-03-12 00:10:16 UTC (rev 85752)
+++ projects/docs/enterprise/4.3.4/readme/zh-CN/readme.po	2009-03-12 00:45:10 UTC (rev 85753)
@@ -31,8 +31,8 @@
 "Enterprise Application Platform &VERSION;. New features, known problems, "
 "resources, and other current issues are addressed here."
 msgstr ""
-"本注记包含了和 JBoss 企业级应用程序平台 &VERSION; 相关的重要信息。新的功能、已"
-"知的问题、资源和其他问题都会在这里提及或解决。"
+"本注记包含了和 JBoss 企业级应用程序平台 &VERSION; 相关的重要信息。新的功能、"
+"已知的问题、资源和其他问题都会在这里提及或解决。"
 
 #. Tag: title
 #: readme.xml:16
@@ -144,8 +144,8 @@
 "JBoss Enterprise Application Platform version &VERSION;, including hardware "
 "and platform requirements and prerequisites."
 msgstr ""
-"本节包含和安装和升级至 JBoss 企业级应用程序平台 &VERSION; 相关的信息，其中包括"
-"对硬件和平台的要求和预备条件。"
+"本节包含和安装和升级至 JBoss 企业级应用程序平台 &VERSION; 相关的信息，其中包"
+"括对硬件和平台的要求和预备条件。"
 
 #. Tag: title
 #: readme.xml:53
@@ -319,20 +319,25 @@
 #. Tag: ulink
 #: readme.xml:116
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4AS/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:120
 #, no-c-format
-msgid "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgid ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/JBEAP/SRPMS"
 
 #. Tag: ulink
 #: readme.xml:124
 #, no-c-format
 msgid "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
-msgstr "ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
+msgstr ""
+"ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS"
 
 #. Tag: title
 #: readme.xml:131
@@ -515,7 +520,8 @@
 msgid ""
 "<filename>Server Configuration Guide</filename> explains all administrative "
 "and configuration functions in detail."
-msgstr "<filename>《服务器配置指南》</filename>详细解释了所有的管理和配置功能。 "
+msgstr ""
+"<filename>《服务器配置指南》</filename>详细解释了所有的管理和配置功能。 "
 
 #. Tag: para
 #: readme.xml:250
@@ -1108,7 +1114,8 @@
 "bin files."
 msgstr ""
 "<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-858\">JBPAPP-858</"
-"ulink>：允许用子软件包的方式在同一台机器上设立多个实例。本发行版本里的 -bin 文>件带有这个功能。"
+"ulink>：允许用子软件包的方式在同一台机器上设立多个实例。本发行版本里的 -bin "
+"文>件带有这个功能。"
 
 #. Tag: para
 #: readme.xml:513
@@ -1119,7 +1126,10 @@
 "additional installation only and cannot be used in place of a regular RPM "
 "jbossas installation. If you only have one version of the AS, it will have "
 "to be the regular RPM installation (or ZIP or installer for older versions)."
-msgstr "请注意，安装 -bn 文件之前首先必须进行常规的 jbossas 安装。-bin 方式仅用>于额外的安装，它不能代替常规的 PRM 安装。如果你只有一个 AS 版本，那就必须使用常>规的 PRM 安装（也可以是 ZIP 文件方式或旧版本的安装程序）。"
+msgstr ""
+"请注意，安装 -bn 文件之前首先必须进行常规的 jbossas 安装。-bin 方式仅用>于额"
+"外的安装，它不能代替常规的 PRM 安装。如果你只有一个 AS 版本，那就必须使用常>"
+"规的 PRM 安装（也可以是 ZIP 文件方式或旧版本的安装程序）。"
 
 #. Tag: title
 #: readme.xml:517
@@ -1392,4 +1402,3 @@
 "However this has meant that the order of columns in union clauses and union-"
 "subclasses has changed, generating a slight impact on the components "
 "performance."
-