[jboss-cvs] JBossAS SVN: r85754 - in projects/docs/enterprise/4.3.4/readme: ja-JP and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Mar 11 21:00:59 EDT 2009
Author: mospina
Date: 2009-03-11 21:00:59 -0400 (Wed, 11 Mar 2009)
New Revision: 85754
Added:
projects/docs/enterprise/4.3.4/readme/ja-JP/
projects/docs/enterprise/4.3.4/readme/ja-JP/Author_Group.po
projects/docs/enterprise/4.3.4/readme/ja-JP/Book_Info.po
projects/docs/enterprise/4.3.4/readme/ja-JP/Release_Notes_CP04.po
projects/docs/enterprise/4.3.4/readme/ja-JP/Revision_History.po
Modified:
projects/docs/enterprise/4.3.4/readme/Makefile
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
Log:
PO files updated for all languages
Modified: projects/docs/enterprise/4.3.4/readme/Makefile
===================================================================
--- projects/docs/enterprise/4.3.4/readme/Makefile 2009-03-12 00:45:10 UTC (rev 85753)
+++ projects/docs/enterprise/4.3.4/readme/Makefile 2009-03-12 01:00:59 UTC (rev 85754)
@@ -5,7 +5,7 @@
BRAND = JBoss
#OTHER_LANGS = as-IN bn-IN de-DE es-ES fr-FR gu-IN hi-IN it-IT ja-JP kn-IN ko-KR ml-IN mr-IN or-IN pa-IN pt-BR ru-RU si-LK ta-IN te-IN zh-CN zh-TW
-OTHER_LANGS = de-DE es-ES fr-FR pt-BR zh-CN
+OTHER_LANGS = de-DE es-ES fr-FR pt-BR zh-CN ja-JP
COMMON_CONFIG = /usr/share/publican
include $(COMMON_CONFIG)/make/Makefile.common
Added: projects/docs/enterprise/4.3.4/readme/ja-JP/Author_Group.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/ja-JP/Author_Group.po (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/ja-JP/Author_Group.po 2009-03-12 01:00:59 UTC (rev 85754)
@@ -0,0 +1,25 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Release_Notes_CP03 package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:57+0000\n"
+"PO-Revision-Date: 2008-11-20 08:38+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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: author
+#: Author_Group.xml:6
+#, fuzzy, no-c-format
+msgid ""
+"<firstname>Isaac</firstname> <surname>Rooskov</surname> "
+"<email>irooskov at redhat.com</email>"
+msgstr "<firstname></firstname> <surname></surname> <email></email>"
Added: projects/docs/enterprise/4.3.4/readme/ja-JP/Book_Info.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/ja-JP/Book_Info.po (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/ja-JP/Book_Info.po 2009-03-12 01:00:59 UTC (rev 85754)
@@ -0,0 +1,51 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Release_Notes_CP03 package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:57+0000\n"
+"PO-Revision-Date: 2008-11-20 08:38+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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
+#: Book_Info.xml:6
+#, fuzzy, no-c-format
+msgid "Release Notes CP04"
+msgstr "リリースノート CP03"
+
+#. Tag: subtitle
+#: Book_Info.xml:7
+#, fuzzy, no-c-format
+msgid ""
+"for Use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 4"
+msgstr "JBoss Enterprise Application Platform 4.3 Cumulative Patch 3 向け"
+
+#. Tag: para
+#: Book_Info.xml:13
+#, fuzzy, no-c-format
+msgid ""
+"These release notes contain important information related to JBoss "
+"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."
+"CP04."
+msgstr ""
+"本リリースノートには、現在の製品マニュアルには記載されていない JBoss "
+"Enterprise Application Platform 4.3.0.CP03 関連の重要な情報が含まれている可能"
+"性があります。本リリースノートを読んでから JBoss Enterprise Application "
+"Platform 4.3.0.CP03 をインストールするようにしてください。"
+
+#. Tag: holder
+#: Book_Info.xml:27
+#, no-c-format
+msgid "&HOLDER;"
+msgstr "&HOLDER;"
Added: projects/docs/enterprise/4.3.4/readme/ja-JP/Release_Notes_CP04.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/ja-JP/Release_Notes_CP04.po (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/ja-JP/Release_Notes_CP04.po 2009-03-12 01:00:59 UTC (rev 85754)
@@ -0,0 +1,3085 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Release_Notes_CP03 package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:57+0000\n"
+"PO-Revision-Date: 2008-11-20 08:38+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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 "はじめに"
+
+#. 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 Enterprise Application Platform &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 Enterprise Application Platform は次世代のオープンソースなエンタープラ"
+"イズソフトウェアです。純粋な 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 Enterprise Application Platform は既存の 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 Enterprise "
+"Application Platform は Red Hat により完全に検査された上でサポートされるた"
+"め、多くの最先端エンタープライズハードウェアやソフトウェア製品で動作すること"
+"が保証されています。"
+
+#. 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 ""
+"このような利点により、JBoss Platform の今後のバージョンに対する前方互換を維持"
+"しながら Java EE 5.0 のテクノロジーを利用して新しいアプリケーションの開発を行"
+"うことができるようになります。 "
+
+#. Tag: title
+#: Release_Notes_CP04.xml:32
+#, no-c-format
+msgid "New Features in JBoss Enterprise Application Platform 4.3"
+msgstr "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 ""
+"JBoss Enterprise Application Platform 4.3 では、JBoss MQ 1.3 に代わる JBoss "
+"Messaging 1.4 が導入されました。JBoss Messaging は 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 Enterprise Application Platform 4.3 では 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
+#, fuzzy, no-c-format
+msgid "JBoss Cache 1.4.1.SP11"
+msgstr "JBoss Cache"
+
+#. 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 "
+"Enterprise Application Platform バージョン &VERSION; のインストールならびに "
+"JBoss Enterprise Application Platform バージョン &VERSION;へのアップグレード"
+"に関する情報が含まれています。"
+
+#. Tag: title
+#: Release_Notes_CP04.xml:145
+#, no-c-format
+msgid "Installation Notes"
+msgstr "インストールに関する注意点"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:146
+#, 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 Enterprise Application Platform のインストールには適切なディ"
+"スク領域が必要となる他、使用するアプリケーションにも十分な領域をとっておく必"
+"要があります。正常に動作する JDK 1.5 または 1.6 がインストールされていなけれ"
+"ばなりません。サポートされるオペレーティングシステム／JVM の組み合わせ、サ"
+"ポートされるデータベースプラットフォーム、含まれるコンポーネントのリビジョン"
+"レベルに関する現在の情報についての最新情報は、<ulink url=\"http://www.jboss."
+"com/products/platforms/application/testedconfigurations\">http://www.jboss."
+"com/products/platforms/application/testedconfigurations</ulink> を参照してく"
+"ださい。JBoss Enterprise Application Platform のインストール方法および検証方"
+"法についての詳細は、オンラインにて <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 Enterprise Application Platform 4.3.0.CP02 からのアップグレード"
+
+#. 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 Reference Guide"
+"\" (<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 は評価および開発を目的とした使用に対してのみデフォルトの "
+"\"out of the box\" データベース機能を提供します。実稼働で使用するデータベース"
+"としては推奨しておらず、サポートもされません。このコンポーネントに対する技術"
+"サポートはありません。このコンポーネントに関するバグ報告は歓迎いたしますが、"
+"特定の期間枠内における修正を確約するものではありません。"
+
+#. 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 "SRPM"
+
+#. 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-"
+"CP03.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-"
+"<version>.zip</filename>."
+msgstr ""
+"zip ディストリビューションでは、プラットフォーム用のドキュメントとその個別コ"
+"ンポーネントは別途に zip ファイル <filename>jboss-eap-docs-<version>."
+"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-<"
+"version>.noarch.rpm</filename>, and <filename>rh-eap-docs-<version>."
+"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 システムの場合、ドキュメントは手作業でインストールを行う必要がある 2 つ"
+"の RPM、<filename>jboss-seam-docs-<version>.noarch.rpm</filename> およ"
+"び <filename>rh-eap-docs-<version>.noarch.rpm</filename> に収録されてい"
+"ます。Red Hat Enterprise Linux に RPM パッケージをインストールする方法につい"
+"ては、<ulink url=\"http://kbase.redhat.com/faq/FAQ_35_198.shtm\">http://"
+"kbase.redhat.com/faq/FAQ_35_198.shtm</ulink> にある Red Hat ナレッジベースの"
+"記載を参照してください。"
+
+#. Tag: para
+#: Release_Notes_CP04.xml:326
+#, 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> では、異なるインストールモードによる "
+"JBoss Enteprise Application Platform のインストール方法および正常なインストー"
+"ルの検証方法について説明しています。"
+
+#. 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> ではプラットフォームのディレクトリ構造"
+"や Application Server のクィックツアー、異なる設定セットやサービスについて説"
+"明しています。シンプルなウェブアプリケーションを使って JSF-EJB3 コンポーネン"
+"トの使用例および JSF と EJB3 コンポーネントの統合に Seam を使用する方法につい"
+"て示します。"
+
+#. 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> では管理および設定の全機能に"
+"ついて詳しく説明しています。 "
+
+#. 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-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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
+#, no-c-format
+msgid "JBoss Cache"
+msgstr "JBoss Cache"
+
+#. 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-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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-1212\">JBPAPP-1212</"
+"ulink>: JBoss Remoting がバージョン 2.2.2.SP10 にアップグレードされたため、5 "
+"つの主要なバグが修正されました。"
+
+#. 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
+#, no-c-format
+msgid "JBoss Web"
+msgstr "JBoss Web"
+
+#. 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-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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-1199\">JBPAPP-1199</"
+"ulink>: <filename>jboss-aop.xml</filename> 内のシステムプロパティがアップグ"
+"レードされ、環境変数が使用できるようになりました。"
+
+#. 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-1270\">JBPAPP-1270</"
+"ulink>: 今回の EAP CP リリースでは、Hibernate Entity Manager がバージョン "
+"3.2.1-2.GA_CP04 にアップグレードされました。"
+
+#. 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
+#, fuzzy, 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 ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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-1270\">JBPAPP-1270</"
+"ulink>: 今回の EAP CP リリースでは、Hibernate Entity Manager がバージョン "
+"3.2.1-2.GA_CP04 にアップグレードされました。"
+
+#. 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-1214\">JBPAPP-1214</"
+"ulink>: Hibernate のコアバージョンが 3.2.4.SP1_CP06 にアップグレードされ、多"
+"くの修正や改良が加えられました。"
+
+#. 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 <join> (table-per-subclass "
+"with discriminator)."
+msgstr ""
+
+#. Tag: para
+#: Release_Notes_CP04.xml:782
+#, no-c-format
+msgid ""
+"The <join> 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 <join> 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-1270\">JBPAPP-1270</"
+"ulink>: 今回の EAP CP リリースでは、Hibernate Entity Manager がバージョン "
+"3.2.1-2.GA_CP04 にアップグレードされました。"
+
+#. 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>&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
+#, fuzzy, 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 ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1111\">JBPAPP-1111</"
+"ulink>: 日本語訳があいまいになるため、サーバー設定ガイド内の max-bean-life の"
+"セクションを改訂する必要があった。日本語訳を明確にするため、問題のあった英文"
+"を書き直しました。"
+
+#. 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-1270\">JBPAPP-1270</"
+"ulink>: 今回の EAP CP リリースでは、Hibernate Entity Manager がバージョン "
+"3.2.1-2.GA_CP04 にアップグレードされました。"
+
+#. 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-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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
+#, 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 ""
+
+#. 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-983\">JBPAPP-983</"
+"ulink>: DB2 のバージョン 8.2 および 9.1 にて JBoss Enterprise Application "
+"Platform 4.3 が動作することが確認されました。"
+
+#. 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 <h:dataTable> 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 <h:"
+"dataTable> 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 < 0) || (index >= list.size())) { </code> to "
+"<code>if ((index < 0) || (index > 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-1199\">JBPAPP-1199</"
+"ulink>: <filename>jboss-aop.xml</filename> 内のシステムプロパティがアップグ"
+"レードされ、環境変数が使用できるようになりました。"
+
+#. 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
+#, fuzzy, 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 ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-1286\">JBPAPP-1286</"
+"ulink>: ドキュメント上の表やリストの中にある脚注が PDF では表示されない。この"
+"問題の原因は FOP にあり、現在対処法が存在しない。ドキュメントの表やリストの中"
+"ではできる限り脚注を使用しないようにしているが、リリースノートなどのドキュメ"
+"ントでは JIRA のウェブアドレスが脚注として自動的に生成され、その横に表示され"
+"ない脚注を参照する番号が付けられてしまう。"
+
+#. 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 ""
+"<ulink url=\"http://jira.jboss.com/jira/browse/JBPAPP-885\">JBPAPP-885</"
+"ulink>: <methodname>DefaultRedeliveryDelay</methodname> または "
+"<methodname>RedeliveryDelay</methodname> がゼロ以外の値に設定されると、"
+"<methodname>session.rollback()</methodname> メソッドが呼び出されてもメッセー"
+"ジが再送信されない。再送信の遅延はサーバー側で処理され、メッセージは送信前に"
+"非永続サブスクリプションによって確認応答されるため、この問題は修正されていな"
+"い。よって、Enterprise Application Platform では非永続サブスクリプションによ"
+"る再送信の遅延はサポートできないことになる。"
+
+#. 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-1270\">JBPAPP-1270</"
+"ulink>: 今回の EAP CP リリースでは、Hibernate Entity Manager がバージョン "
+"3.2.1-2.GA_CP04 にアップグレードされました。"
+
+#. 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 ""
+"<database-object>\n"
+" <create>\n"
+" sp_procxmode paramHandling, 'chained'\n"
+" </create>\n"
+" <drop/>\n"
+"</database-object>"
+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-1214\">JBPAPP-1214</"
+"ulink>: Hibernate のコアバージョンが 3.2.4.SP1_CP06 にアップグレードされ、多"
+"くの修正や改良が加えられました。"
+
+#. 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-1269\">JBPAPP-1269</"
+"ulink>: 今回の EAP CP リリースでは、Hibernate Annotations がバージョン 3.2.1-"
+"4.GA_CP03 にアップグレードされました。"
+
+#. 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>: JDK 1.6 をサポートするため、EAP の Hibernate コンポーネント内で "
+"HashMap と HashSet の繰り返し順序の変更があったが、union 節と union サブクラ"
+"スの列の順番が変更になり、コンポーネントのパフォーマンスに若干影響があった。"
Added: projects/docs/enterprise/4.3.4/readme/ja-JP/Revision_History.po
===================================================================
--- projects/docs/enterprise/4.3.4/readme/ja-JP/Revision_History.po (rev 0)
+++ projects/docs/enterprise/4.3.4/readme/ja-JP/Revision_History.po 2009-03-12 01:00:59 UTC (rev 85754)
@@ -0,0 +1,29 @@
+# translation of Author_Group.po to Japanese
+# Language ja-JP translations for Release_Notes_CP03 package.
+#
+# Automatically generated, 2008.
+# Junko Ito <junko.ito at rehdat.com>, 2008.
+msgid ""
+msgstr ""
+"Project-Id-Version: Author_Group\n"
+"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
+"POT-Creation-Date: 2009-03-12 00:57+0000\n"
+"PO-Revision-Date: 2008-11-20 08:38+1000\n"
+"Last-Translator: Junko Ito <junko.ito at rehdat.com>\n"
+"Language-Team: Japanese <ja 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 "<firstname></firstname> <surname></surname> <email></email>"
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:45:10 UTC (rev 85753)
+++ projects/docs/enterprise/4.3.4/readme/pot/Author_Group.pot 2009-03-12 01:00:59 UTC (rev 85754)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"POT-Creation-Date: 2009-03-12 00:57+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"
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:45:10 UTC (rev 85753)
+++ projects/docs/enterprise/4.3.4/readme/pot/Book_Info.pot 2009-03-12 01:00:59 UTC (rev 85754)
@@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-03-12 00:39+0000\n"
+"POT-Creation-Date: 2009-03-12 00:57+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"
Modified: projects/docs/enterprise/4.3.4/readme/pot/messages.mo
===================================================================
(Binary files differ)
More information about the jboss-cvs-commits
mailing list