[jboss-cvs] JBossAS SVN: r82129 - projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Dec 9 01:56:13 EST 2008
Author: mospina
Date: 2008-12-09 01:56:13 -0500 (Tue, 09 Dec 2008)
New Revision: 82129
Removed:
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Gwt.po
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Oc4j.po
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Seam_Reference_Guide.po
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Version_Info.po
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Weblogic.po
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Websphere.po
projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/master.po
Log:
Deleting extra files in ja-JP
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Gwt.po
===================================================================
--- projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Gwt.po 2008-12-09 06:26:10 UTC (rev 82128)
+++ projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Gwt.po 2008-12-09 06:56:13 UTC (rev 82129)
@@ -1,355 +0,0 @@
-# Language ja-JP translations for PACKAGE package.
-# Automatically generated, 2008.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Gwt.xml:5
-#, no-c-format
-msgid "Seam and the Google Web Toolkit"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:7
-#, no-c-format
-msgid ""
-"For those that prefer to use the Google Web Toolkit (GWT) to develop dynamic "
-"AJAX applications, Seam provides an integration layer that allows GWT "
-"widgets to interact directly with Seam components."
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:12
-#, no-c-format
-msgid ""
-"To use GWT, we assume that you are already familiar with the GWT tools - "
-"more information can be found at <ulink url=\"http://code.google.com/"
-"webtoolkit/\">http://code.google.com/webtoolkit/</ulink>. This chapter does "
-"not attempt to explain how GWT works or how to use it."
-msgstr ""
-
-#. Tag: title
-#: Gwt.xml:19
-#, no-c-format
-msgid "Configuration"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:21
-#, no-c-format
-msgid ""
-"There is no special configuration required to use GWT in a Seam application, "
-"however the Seam resource servlet must be installed. See <xref linkend="
-"\"configuration\"/> for details."
-msgstr ""
-
-#. Tag: title
-#: Gwt.xml:29
-#, no-c-format
-msgid "Preparing your component"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:31
-#, no-c-format
-msgid ""
-"The first step in preparing a Seam component to be called via GWT, is to "
-"create both synchronous and asynchronous service interfaces for the methods "
-"you wish to call. Both of these interfaces should extend the GWT interface "
-"<literal>com.google.gwt.user.client.rpc.RemoteService</literal>:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:37
-#, no-c-format
-msgid ""
-"<![CDATA[public interface MyService extends RemoteService {\n"
-" public String askIt(String question); \n"
-" }]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:39
-#, no-c-format
-msgid ""
-"The asynchronous interface should be identical, except that it also contains "
-"an additional <literal>AsyncCallback</literal> parameter for each of the "
-"methods it declares:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:44
-#, no-c-format
-msgid ""
-"<![CDATA[public interface MyServiceAsync extends RemoteService {\n"
-" public void askIt(String question, AsyncCallback callback);\n"
-"}]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:46
-#, no-c-format
-msgid ""
-"The asynchronous interface, in this example <literal>MyServiceAsync</"
-"literal>, will be implemented by GWT and should never be implemented "
-"directly."
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:51
-#, no-c-format
-msgid ""
-"The next step, is to create a Seam component that implements the synchronous "
-"interface:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:55
-#, no-c-format
-msgid ""
-"<![CDATA[@Name(\"org.jboss.seam.example.remoting.gwt.client.MyService\")\n"
-"public class ServiceImpl implements MyService {\n"
-"\n"
-" @WebRemote\n"
-" public String askIt(String question) {\n"
-" \n"
-" if (!validate(question)) {\n"
-" throw new IllegalStateException(\"Hey, this shouldn't happen, I "
-"checked on the client, \" +\n"
-" \"but its always good to double check.\");\n"
-" }\n"
-" return \"42. Its the real question that you seek now.\";\n"
-" }\n"
-" \n"
-" public boolean validate(String q) {\n"
-" ValidationUtility util = new ValidationUtility();\n"
-" return util.isValid(q);\n"
-" }\n"
-"}]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:57
-#, no-c-format
-msgid ""
-"The methods that should be made accessible via GWT need to be annotated with "
-"the <literal>@WebRemote</literal> annotation, which is required for all web-"
-"remoteable methods."
-msgstr ""
-
-#. Tag: title
-#: Gwt.xml:64
-#, no-c-format
-msgid "Hooking up a GWT widget to the Seam component"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:66
-#, no-c-format
-msgid ""
-"The next step, is to write a method that returns the asynchronous interface "
-"to the component. This method can be located inside the widget class, and "
-"will be used by the widget to obtain a reference to the asynchronous client "
-"stub:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:72
-#, no-c-format
-msgid ""
-"<![CDATA[private MyServiceAsync getService() { \n"
-" String endpointURL = GWT.getModuleBaseURL() + \"seam/resource/gwt"
-"\"; \n"
-" \n"
-" MyServiceAsync svc = (MyServiceAsync) GWT.create(MyService.class);\n"
-" ((ServiceDefTarget) svc).setServiceEntryPoint(endpointURL);\n"
-" return svc; \n"
-"}]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:74
-#, no-c-format
-msgid ""
-"The final step is to write the widget code that invokes the method on the "
-"client stub. The following example creates a simple user interface with a "
-"label, text input and a button:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:79
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"public class AskQuestionWidget extends Composite {\n"
-" private AbsolutePanel panel = new AbsolutePanel();\n"
-" \n"
-" public AskQuestionWidget() { \n"
-" Label lbl = new Label(\"OK, what do you want to know?\");\n"
-" panel.add(lbl);\n"
-" final TextBox box = new TextBox();\n"
-" box.setText(\"What is the meaning of life?\");\n"
-" panel.add(box);\n"
-" Button ok = new Button(\"Ask\");\n"
-" ok.addClickListener(new ClickListener() {\n"
-" public void onClick(Widget w) {\n"
-" ValidationUtility valid = new ValidationUtility();\n"
-" if (!valid.isValid(box.getText())) {\n"
-" Window.alert(\"A question has to end with a '?'\");\n"
-" } else {\n"
-" askServer(box.getText());\n"
-" } \n"
-" }\n"
-" });\n"
-" panel.add(ok);\n"
-" \n"
-" initWidget(panel);\n"
-" }\n"
-"\n"
-" private void askServer(String text) {\n"
-" getService().askIt(text, new AsyncCallback() {\n"
-" public void onFailure(Throwable t) {\n"
-" Window.alert(t.getMessage());\n"
-" }\n"
-"\n"
-" public void onSuccess(Object data) {\n"
-" Window.alert((String) data);\n"
-" } \n"
-" }); \n"
-" }\n"
-" \n"
-" ...]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:82
-#, no-c-format
-msgid ""
-"When clicked, the button invokes the <literal>askServer()</literal> method "
-"passing the contents of the input text (in this example, validation is also "
-"performed to ensure that the input is a valid question). The "
-"<literal>askServer()</literal> method acquires a reference to the "
-"asynchronous client stub (returned by the <literal>getService()</literal> "
-"method) and invokes the <literal>askIt()</literal> method. The result (or "
-"error message if the call fails) is shown in an alert window."
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:99
-#, no-c-format
-msgid ""
-"The complete code for this example can be found in the Seam distribution in "
-"the <literal>examples/remoting/gwt</literal> directory."
-msgstr ""
-
-#. Tag: title
-#: Gwt.xml:106
-#, no-c-format
-msgid "GWT Ant Targets"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:108
-#, no-c-format
-msgid ""
-"For deployment of GWT apps, there is a compile-to-Javascript step (which "
-"compacts and obfuscates the code). There is an ant utility which can be used "
-"instead of the command line or GUI utility that GWT provides. To use this, "
-"you will need to have the ant task jar in your ant classpath, as well as GWT "
-"downloaded (which you will need for hosted mode anyway)."
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:114
-#, no-c-format
-msgid "Then, in your ant file, place (near the top of your ant file):"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:118
-#, no-c-format
-msgid ""
-"<![CDATA[<taskdef uri=\"antlib:de.samaflost.gwttasks\"\n"
-" resource=\"de/samaflost/gwttasks/antlib.xml\"\n"
-" classpath=\"./lib/gwttasks.jar\"/>\n"
-" \n"
-" <property file=\"build.properties\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:120
-#, no-c-format
-msgid ""
-"Create a <literal>build.properties</literal> file, which has the contents:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:124
-#, no-c-format
-msgid "<![CDATA[gwt.home=/gwt_home_dir]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:126
-#, no-c-format
-msgid ""
-"This of course should point to the directory where GWT is installed. Then to "
-"use it, create a target:"
-msgstr ""
-
-#. Tag: programlisting
-#: Gwt.xml:130
-#, no-c-format
-msgid ""
-"<![CDATA[<!-- the following are are handy utilities for doing GWT "
-"development.\n"
-" To use GWT, you will of course need to download GWT seperately -->\n"
-" <target name=\"gwt-compile\">\n"
-" <!-- in this case, we are \"re homing\" the gwt generated stuff, so in "
-"this case\n"
-" we can only have one GWT module - we are doing this deliberately to "
-"keep the URL short -->\n"
-" <delete>\n"
-" <fileset dir=\"view\"/>\n"
-" </delete>\n"
-" <gwt:compile outDir=\"build/gwt\"\n"
-" gwtHome=\"${gwt.home}\"\n"
-" classBase=\"${gwt.module.name}\"\n"
-" sourceclasspath=\"src\"/>\n"
-" <copy todir=\"view\">\n"
-" <fileset dir=\"build/gwt/${gwt.module.name}\"/>\n"
-" </copy>\n"
-" </target>]]>"
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:132
-#, no-c-format
-msgid ""
-"This target when called will compile the GWT application, and copy it to the "
-"specified directory (which would be in the <literal>webapp</literal> part of "
-"your war - remember GWT generates HTML and Javascript artifacts). You never "
-"edit the resulting code that <literal>gwt-compile</literal> generates - you "
-"always edit in the GWT source directory."
-msgstr ""
-
-#. Tag: para
-#: Gwt.xml:139
-#, no-c-format
-msgid ""
-"Remember that GWT comes with a hosted mode browser - you should be using "
-"that if you are developing with GWT. If you aren't using that, and are just "
-"compiling it each time, you aren't getting the most out of the toolkit (in "
-"fact, if you can't or won't use the hosted mode browser, I would go far as "
-"to say you should NOT be using GWT at all - it's that valuable!)."
-msgstr ""
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Oc4j.po
===================================================================
--- projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Oc4j.po 2008-12-09 06:26:10 UTC (rev 82128)
+++ projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Oc4j.po 2008-12-09 06:56:13 UTC (rev 82129)
@@ -1,1630 +0,0 @@
-# translation of Oc4j.po to Japanese
-# Language ja-JP translations for PACKAGE package.
-#
-# Automatically generated, 2008.
-# Noriko Mizumoto <noriko at redhat.com>, 2008.
-msgid ""
-msgstr ""
-"Project-Id-Version: Oc4j\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-12-01 14:25+1000\n"
-"Last-Translator: Noriko Mizumoto <noriko at redhat.com>\n"
-"Language-Team: Japanese <fedora-trans-ja at redhat.com>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.4\n"
-
-#. Tag: title
-#: Oc4j.xml:2
-#, no-c-format
-#, fuzzy
-msgid "Seam on OC4J"
-msgstr "OC4J での Seam"
-
-#. Tag: para
-#: Oc4j.xml:4
-#, no-c-format
-msgid ""
-"OC4J (Oracle Containers for Java) 11g (currently a \"Technology Preview\" "
-"release) is Oracle's JEE5 application server. Seam application can be "
-"deployed to OC4J, but require some additional configuration changes, and "
-"dependencies. This chapter will show you exactly what must be done. We will "
-"start by looking at the building and deploying the JEE5 Hotel Booking "
-"example application which comes with Seam. Then we will deploy a project "
-"generated by <literal>seam-gen</literal> . First a basic <literal>seam-gen</"
-"literal> application with RichFaces ajax components, and facelets. Then "
-"expand that application to include Seam security with Drools, JPA provided "
-"with hibernate, and automatic CRUD reverse engineering of a MySQL database."
-msgstr "OC4J (Oracle Containers for Java) 11g (現在テクノロジープレビューとしてのリリース) は Oracle の JEE5 アプリケーションサーバーになります。 Seam アプリケーションは OC4J にデプロイ可能ですが、 いくつか追加となる設定変更および依存性が要されます。 本章では実際に何を行わなければならないのかについて見ていきます。 まず Seam に同梱される JEE5 ホテル予約サンプルアプリケーションの構築とデプロイメントから見ていきます。 次に <literal>seam-gen</literal> で生成されるプロジェクトをデプロイしてみます。 RichFaces ajax コンポーネントを持つ基本的な <literal>seam-gen</literal> アプリケーションと facelets、 次にこのアプリケーションを拡張して Drools、 Hibernate で提供される JPA および MySQL データベースの自動 CRUD リバースエンジニアリ!
ングなどを備えた Seam セキュリティを含ませていくことにします。"
-
-#. Tag: title
-#: Oc4j.xml:17
-#, no-c-format
-msgid "Installation and operation of OC4J"
-msgstr "OC4J のインストールと操作"
-
-#. Tag: para
-#: Oc4j.xml:18
-#, no-c-format
-msgid ""
-"First we need to install the target container - OC4j. This chapter requires "
-"you to use OC4J 11g Technology Preview (not OC4J 10g). You can download OC4J "
-"11g from <ulink url=\"http://www.oracle.com/technology/tech/java/oc4j/11/\"> "
-"http://www.oracle.com/technology/tech/java/oc4j/11/ </ulink> Below are "
-"instructions to install. launch, access, and shutdown the 11g release. For "
-"further information on installing OC4J, consult the <literal>readme.txt</"
-"literal> distributed with OC4J, or the OC4J installation guide and release "
-"notes."
-msgstr ""
-"まず目的とのコンテナ OC4j をインストールする必要があります。 本章では OC4J 11g テクノロジープレビューを使用してください (OC4J 10g ではありません)。 <ulink url=\"http://www.oracle.com/technology/tech/java/oc4j/11/\"> "
-"http://www.oracle.com/technology/tech/java/oc4j/11/ </ulink> から OC4J 11g をダウンロードすることができます。 以下に 11g リリースのインストール、 起動、 アクセス、 シャットダウンなど方法について示します。 OC4J の詳しいインストール方法については OC4J に同梱される <literal>readme.txt</literal> をご覧頂くか、 OC4J インストールガイドおよびリリースノートを参照してください。"
-
-#. Tag: para
-#: Oc4j.xml:29
-#, no-c-format
-msgid "Download and unzip OC4J"
-msgstr "OC4J のダウンロードと解凍"
-
-#. Tag: para
-#: Oc4j.xml:32
-#, no-c-format
-msgid ""
-"Make sure you have <literal>$JAVA_HOME</literal> and <literal>$ORACLE_HOME</"
-"literal> set as environment variables ( <literal>$ORACLE_HOME</literal> is "
-"the directory to which you unzip OC4J). For further information on "
-"installing OC4J, consult the <literal>readme.txt</literal> distributed with "
-"OC4J"
-msgstr ""
-"<literal>$JAVA_HOME</literal> と <literal>$ORACLE_HOME</"
-"literal> のセットが環境変数としてあるか確認します (<literal>$ORACLE_HOME</literal> は OC4J の解凍先となるディレクトリ)。 OC4J の詳しいインストール方法については OC4J に同梱の <literal>readme.txt</literal> をご覧ください。"
-
-#. Tag: para
-#: Oc4j.xml:41
-#, no-c-format
-msgid ""
-"Applications (ear/war) are deployed to the <literal>$ORACLE_HOME/j2ee/home/"
-"applications</literal> directory."
-msgstr ""
-"アプリケーション (ear/war) は <literal>$ORACLE_HOME/j2ee/home/"
-"applications</literal> ディレクトリにデプロイされます。"
-
-#. Tag: para
-#: Oc4j.xml:44
-#, no-c-format
-msgid ""
-"Note that OC4J does not support hot deployment by default. This means every "
-"time you deploy the application you must restart the server."
-msgstr "OC4J はデフォルトではホットデプロイメントに対応しないので注意してください。 つまり、 アプリケーションをデプロイするたびにサーバーを再起動する必要があるということです。"
-
-#. Tag: para
-#: Oc4j.xml:49
-#, no-c-format
-msgid ""
-"Start OC4J: <literal> $ORACLE_HOME/j2ee/home/java -jar -XX:MaxPermSize=256M "
-"oc4j.jar </literal>"
-msgstr ""
-"OC4J の起動: <literal> $ORACLE_HOME/j2ee/home/java -jar -XX:MaxPermSize=256M "
-"oc4j.jar </literal>"
-
-#. Tag: para
-#: Oc4j.xml:51
-#, no-c-format
-msgid ""
-"You must override the default PermGen memory settings using above command. "
-"See <ulink url=\"http://www.oracle.com/technology/tech/java/oc4j/11/oc4j-"
-"relnotes.html\"> OC4J release notes </ulink> for details."
-msgstr ""
-"上記のコマンドを使ってデフォルトの PermGen メモリ設定を上書きしなければなりません。 詳細については <ulink url=\"http://www.oracle.com/technology/tech/java/oc4j/11/oc4j-"
-"relnotes.html\"> OC4J release notes </ulink> を参照してください。"
-
-#. Tag: para
-#: Oc4j.xml:55
-#, no-c-format
-msgid ""
-"You will be asked to set the admin password if this is the first time you "
-"have started OC4J"
-msgstr "初めて OC4J を起動する際は管理者パスワードを設定するよう求められます。"
-
-#. Tag: para
-#: Oc4j.xml:59
-#, no-c-format
-msgid ""
-"Once deployed you can check out your applications at <literal>http://"
-"localhost:8888/<your-app-path></literal>"
-msgstr ""
-"デプロイメントが完了したら <literal>http://"
-"localhost:8888/<your-app-path></literal> でアプリケーションをチェックアウトすることができます。"
-
-#. Tag: para
-#: Oc4j.xml:64
-#, no-c-format
-msgid ""
-"You can stop the server by pressing <literal>CTRL-C</literal> in the console "
-"on which the server is running."
-msgstr "サーバーが稼働しているコンソールで <literal>CTRL-C</literal> を押すとサーバーを停止することができます。"
-
-#. Tag: title
-#: Oc4j.xml:72
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> example"
-msgstr "<literal>jee5/booking</literal> サンプル"
-
-#. Tag: para
-#: Oc4j.xml:74
-#, no-c-format
-msgid ""
-"The <literal>jee5/booking</literal> example is based on the Hotel Booking "
-"example (which runs on JBoss AS). Out of the box it is designed to run on "
-"Glassfish, but it's easy to build it for OC4J. It is located in the <literal>"
-"$SEAM_DIST/examples/jee5/booking</literal> directory."
-msgstr ""
-"<literal>jee5/booking</literal> サンプルはホテル予約サンプルをベースとしています (JBoss AS で稼働)。 特に設定をしない状態では Glassfish で稼働するよう設計されていますが、 これを OC4J 用にビルドするのは簡単です。 <literal>"
-"$SEAM_DIST/examples/jee5/booking</literal> ディレクトリに配置されています。"
-
-#. Tag: title
-#: Oc4j.xml:81
-#, no-c-format
-msgid "Booking Example Dependencies"
-msgstr "予約サンプルの依存性"
-
-#. Tag: para
-#: Oc4j.xml:83
-#, no-c-format
-#, fuzzy
-msgid ""
-"First, lets look at the basic dependencies of the booking example. Armed "
-"with this knowledge we can look at the extra dependencies requirements that "
-"OC4J adds."
-msgstr ""
-"まず、 予約サンプルの基本的な依存性を見てみます。 こうした知識を理解した上で OC4J が追加する依存性要件を見ていくことができます。 "
-"we can look at the extra dependencies requirements that "
-"OC4J adds."
-
-#. Tag: para
-#: Oc4j.xml:87
-#, no-c-format
-msgid ""
-"We will show you how to get these dependencies into the application in <xref "
-"linkend=\"oc4j-build-jee5\"/> below."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:90
-#, no-c-format
-msgid "Core Seam dependencies"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:93
-#, no-c-format
-msgid ""
-"<literal>jboss-seam.jar</literal> — We declare this as an EJB3 module "
-"(why? well Seam needs to be able to interact with container managed "
-"transactions; this is implemented as an EJB3 Stateful Session Bean)"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:100
-#, no-c-format
-msgid "jboss-el.jar"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:103
-#, no-c-format
-msgid ""
-"<literal>jboss-seam-ui.jar</literal> — Seam's JSF controls depend on "
-"Apache's commons-beanutils"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:108
-#, no-c-format
-msgid "jboss-seam-debug.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:112
-#, no-c-format
-msgid "jsf-facelets.jar"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:116
-#, no-c-format
-msgid ""
-"<literal>richfaces-api.jar</literal> , <literal>richfaces-impl.jar</literal> "
-"and <literal>richfaces-ui.jar</literal> — which requires Apache "
-"commons-digester and commons-beanutils"
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:126
-#, no-c-format
-msgid "Extra dependencies"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:129
-#, no-c-format
-msgid ""
-"Hibernate — of course, we decided to use Hibernate as the JPA provider "
-"(rather than TopLink Essentials which ships with OC4J)."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:132
-#, no-c-format
-msgid "To use Hibernate as your JPA provider you need the following jars:"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:136
-#, no-c-format
-msgid "hibernate.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:141
-#, no-c-format
-msgid "hibernate-annotations.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:146
-#, no-c-format
-msgid "hibernate-entitymanager.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:151
-#, no-c-format
-msgid "hibernate-validator.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:156
-#, no-c-format
-msgid "jboss-common-core.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:161
-#, no-c-format
-msgid "commons-logging.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:166
-#, no-c-format
-msgid "commons-collections.jar"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:172
-#, no-c-format
-msgid ""
-"Third party jars — various jars needed for seam and this example to "
-"run."
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:176
-#, no-c-format
-msgid "javaasist.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:180
-#, no-c-format
-msgid "dom4j.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:184
-#, no-c-format
-msgid "cglib.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:188
-#, no-c-format
-msgid "asm.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:193
-#, no-c-format
-msgid "commons-beanutils.jar"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:198
-#, no-c-format
-msgid "commons-digester.jar"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:202
-#, no-c-format
-msgid ""
-"<literal>log4j.jar</literal> — This can be left out if you are not "
-"going to configure log4j. If it is packaged but not configured logging will "
-"be hidden in oc4j."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:211
-#, no-c-format
-msgid ""
-"Extra OC4J jars — Running Seam on most application servers (such as "
-"JBoss AS or Glassfish) you only need to include the dependencies for those "
-"bits of Seam you actually use (e.g. if you use Seam Text you need to include "
-"ANTLR); but, on OC4J, due to its \"interesting\" classloading you must "
-"always include them:"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:220
-#, no-c-format
-msgid "hibernate-search.jar"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:224
-#, no-c-format
-msgid ""
-"<literal>hibernate-common-annotations.jar</literal> — needed for "
-"hibernate search"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:230
-#, no-c-format
-msgid "<literal>lucene-core.jar</literal> — needed for hibernate search"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:235
-#, no-c-format
-msgid "<literal>antlr.jar</literal> — needed for Seam Text"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:239
-#, no-c-format
-msgid "<literal>jbpm-jpdl.jar</literal> — needed for Seam's JBPM"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:243
-#, no-c-format
-msgid "quartz.jar"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:247
-#, no-c-format
-msgid "<literal>dbunit.jar</literal> — needed for some testing classes"
-msgstr ""
-
-#. Tag: simpara
-#: Oc4j.xml:252
-#, no-c-format
-msgid ""
-"<literal>jboss-embedded-api.jar</literal> — needed for some testing "
-"classes"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:258
-#, no-c-format
-msgid ""
-"Drools — needed for Seam Security. We aren't using Seam security with "
-"Drools, but have to include it. Drools consists of 6 jars: <itemizedlist> "
-"<listitem> <simpara> <literal>drools-core.jar</literal> </simpara> </"
-"listitem> <listitem> <simpara> <literal>drools-compiler.jar</literal> </"
-"simpara> </listitem> <listitem> <simpara> <literal>janino.jar</literal> </"
-"simpara> </listitem> <listitem> <simpara> <literal>mvel141.jar</literal> </"
-"simpara> </listitem> <listitem> <simpara> <literal>core.jar</literal> </"
-"simpara> </listitem> <listitem> <simpara> <literal>antlr-runtime.jar</"
-"literal> </simpara> </listitem> </itemizedlist> Drools integration is not "
-"used in the example."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:302 Oc4j.xml:500
-#, no-c-format
-msgid "Configuration file changes"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:304
-#, no-c-format
-msgid "There are just a few changes to be made:"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:307
-#, no-c-format
-msgid "web.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:310
-#, no-c-format
-msgid ""
-"You need to declare all your ejb's in the <literal>web.xml</literal> . This "
-"is a silly requirement of a number of JEE5 application servers - for example "
-"OC4J and Glassfish."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:314
-#, no-c-format
-msgid "This is already done in the example's web.xml file, below is an example."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:318
-#, no-c-format
-msgid ""
-"<![CDATA[<ejb-local-ref>\n"
-" <ejb-ref-name>\n"
-" jboss-seam-jee5/AuthenticatorAction/local\n"
-" </ejb-ref-name>\n"
-" <ejb-ref-type>Session</ejb-ref-type>\n"
-" <local>\n"
-" org.jboss.seam.example.booking.Authenticator\n"
-" </local>\n"
-" <ejb-link>AuthenticatorAction</ejb-link>\n"
-"</ejb-local-ref>]]>"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:322
-#, no-c-format
-msgid "persistence.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:325
-#, no-c-format
-msgid ""
-"You need to provide the correct configuration for your JPA implementation. "
-"We are using Hibernate and due to OC4J bundling an old ANTLR, we need to use "
-"an alternative query factory, we also want to use the OC4J transaction "
-"manager:"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:330
-#, no-c-format
-msgid ""
-"For our example modify the <literal>resources/META-INF/persistence.xml</"
-"literal> file. Comment out the Glassfish properties and un-comment the OC4J "
-"properties."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:336
-#, no-c-format
-msgid ""
-"<![CDATA[<property name=\"hibernate.dialect\" \n"
-" value=\"org.hibernate.dialect.HSQLDialect\"/>\n"
-"<property name=\"hibernate.query.factory_class\" \n"
-" value=\"org.hibernate.hql.classic.ClassicQueryTranslatorFactory\"/>\n"
-"<property name=\"hibernate.transaction.manager_lookup_class\" \n"
-" value=\"org.hibernate.transaction.OrionTransactionManagerLookup\"/>]]>"
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:344
-#, no-c-format
-msgid "Building the <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:349
-#, no-c-format
-msgid "Modify the <literal>build.xml</literal> file in the example:"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:353
-#, no-c-format
-msgid ""
-"Un-comment the labeled OC4J-related library properties. This will include "
-"all the extra dependencies discussed above."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:356
-#, no-c-format
-msgid "It should look like the following:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:359
-#, no-c-format
-msgid ""
-"<![CDATA[<!-- add libs for oc4j (eager classloading) -->\n"
-"<property name=\"jbpm.lib\" value=\"true\"/>\n"
-"<property name=\"drools.lib\" value=\"true\"/>\n"
-"<property name=\"quartz.lib\" value=\"true\" />\n"
-"<property name=\"search.lib\" value=\"true\" />\n"
-"<property name=\"dbunit.lib\" value=\"true\" />\n"
-"<property name=\"jboss-embedded-api.lib\" value=\"true\" />\n"
-" ]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:364
-#, no-c-format
-msgid ""
-"Build the demo app by running <literal>ant</literal> in the "
-"<literal>examples/jee5/booking</literal> directory. The build target is "
-"<literal>dist/jboss-seam-jee5.ear</literal>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:370
-#, no-c-format
-msgid ""
-"Copy <literal>dist/jboss-seam-jee5.ear</literal> following the instructions "
-"below."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:378
-#, no-c-format
-msgid "Deploying the Seam application to OC4J"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:379
-#, no-c-format
-msgid ""
-"This mini-tutorial describes the (fairly tedious) steps required to deploy a "
-"JEE 5 application to OC4J. It assumes you have already downloaded and "
-"installed it following the instructions in <xref linkend=\"oc4j-install-"
-"operation\"/>. It also assumes you are deploying the <literal>jee5/booking</"
-"literal> example, using the embedded hsqldb database. To deploy another "
-"application you would need to alter the datasource and application name."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:388
-#, no-c-format
-msgid ""
-"Copy <literal>hsqldb.jar</literal> to OC4J shared library directory: "
-"<literal> cp ../../seam-gen/lib/hsqldb.jar $ORACLE_HOME/j2ee/home/applib/ </"
-"literal> (OC4J doesn't come with an embedded database so we decided to use "
-"HSQLDB)"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:395
-#, no-c-format
-msgid ""
-"Edit the OC4J datasource file <literal>$ORACLE_HOME/j2ee/home/config/data-"
-"sources.xml</literal> and, inside <literal><data-sources></literal> , "
-"add"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:401
-#, no-c-format
-msgid ""
-"<![CDATA[<managed-data-source\n"
-" connection-pool-name=\"jee5-connection-pool\"\n"
-" jndi-name=\"jdbc/__default\"\n"
-" name=\"jee5-managed-data-source\" />\n"
-"<connection-pool name=\"jee5-connection-pool\">\n"
-" <connection-factory\n"
-" factory-class=\"org.hsqldb.jdbcDriver\" \n"
-" user=\"sa\"\n"
-" password=\"\" \n"
-" url=\"jdbc:hsqldb:.\" />\n"
-"</connection-pool>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:403
-#, no-c-format
-msgid ""
-"The <literal>jndi-name</literal> is used as the <literal>jta-data-source</"
-"literal> in <literal>persistence.xml</literal> ."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:408
-#, no-c-format
-msgid ""
-"Edit <literal>$ORACLE_HOME/j2ee/home/config/server.xml</literal> and, inside "
-"<literal><application-server></literal> , add"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:414
-#, no-c-format
-msgid ""
-"<![CDATA[<application name=\"jboss-seam-jee5\"\n"
-" path=\"../../home/applications/jboss-seam-jee5.ear\"\n"
-" parent=\"default\" \n"
-" start=\"true\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:415
-#, no-c-format
-msgid "To keep things simple use the same names as you used for project."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:419
-#, no-c-format
-msgid ""
-"Edit <literal> $ORACLE_HOME/j2ee/home/config/default-web-site.xml </"
-"literal> , and, inside <literal><web-site></literal> , add"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:425
-#, no-c-format
-msgid ""
-"<![CDATA[<web-app application=\"jboss-seam-jee5\"\n"
-" name=\"jboss-seam-jee5\" \n"
-" load-on-startup=\"true\"\n"
-" root=\"/seam-jee5\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:426
-#, no-c-format
-msgid ""
-"The <literal>root</literal> is the context path you will put into your web "
-"browser to access the application."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:430
-#, no-c-format
-msgid ""
-"Copy the application to OC4J: <literal> cp dist/jboss-seam-jee5.ear "
-"$ORACLE_HOME/j2ee/home/applications/ </literal>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:435
-#, no-c-format
-msgid ""
-"Start/stop OC4J following instructions in <xref linkend=\"oc4j-install-"
-"operation\"/> above."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:439
-#, no-c-format
-msgid "Checkout the app at: <literal>http://localhost:8888/seam-jee5</literal>"
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:447
-#, no-c-format
-msgid "Deploying an application created using <literal>seam-gen</literal> to OC4J"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:450
-#, no-c-format
-msgid ""
-"<literal>seam-gen</literal> is a great tool for developers that can quickly "
-"get you up and running with a full Seam application. However the project "
-"that it created is configured to run on JBoss AS. This means there are some "
-"extra steps needed to have it execute on OC4j. The following explanation "
-"assumes you are using the command line and a simple text editor, but of "
-"course you can use your favorite IDE. <literal>seam-gen</literal> projects "
-"come with support for Eclipse and Netbeans."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:459
-#, no-c-format
-msgid ""
-"We will start by creating and deploying a pretty simple application using "
-"<literal>seam-gen</literal> . Then we'll show you how easy it is to use "
-"<literal>seam-gen</literal> and Hibernate Tools to reverse engineer a "
-"database schema into a functional CRUD application. <literal>seam-gen</"
-"literal> will create JPA entity beans, Seam Application Framework components "
-"and JSF views for you. We will also add Seam security using Drools."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:467
-#, no-c-format
-msgid ""
-"This tutorial uses MySQL (but of course you could use any database, altering "
-"the SQL and datasources as appropriate); install, configure and run MySQL, "
-"then create a database with some sample data. Don't forget to also download "
-"the <literal>mysql-connector-java-X.jar</literal> for jdbc support. When "
-"setting up Seam security this tutorial will assume there is a table named "
-"<literal>User</literal> with columns <literal>username</literal> and "
-"<literal>password</literal> with at least one entry. Beyond that you can set "
-"up any type of sample data and tables you would like."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:479
-#, no-c-format
-msgid "Generating a basic <literal>seam-gen</literal> application"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:481
-#, no-c-format
-msgid ""
-"First we need to tell the <literal>seam-gen</literal> what we want, run "
-"<literal>./seam setup</literal> in the seam distribution directory. Follow "
-"the settings example below based on your system and setup (ex. use your "
-"database name instead of <literal>oc4jexample</literal> )."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:488
-#, no-c-format
-msgid ""
-"<![CDATA[> ./seam setup\n"
-"Buildfile: build.xml\n"
-"\n"
-"init:\n"
-"\n"
-"setup:\n"
-" [echo] Welcome to seam-gen :-)\n"
-" [input] Enter your Java project workspace (the directory that contains "
-"your \n"
-"Seam projects) [C:/Projects] [C:/Projects]\n"
-"/home/jbalunas/workspace\n"
-" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2."
-"GA] \n"
-"[C:/Program Files/jboss-4.2.2.GA]\n"
-"/home/jbalunas/jboss/jboss-4.2.2.GA\n"
-" [input] Enter the project name [myproject] [myproject]\n"
-"oc4j_example\n"
-" [echo] Accepted project name as: oc4j_example\n"
-" [input] Select a RichFaces skin (not applicable if using ICEFaces) "
-"[blueSky]\n"
-" ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n"
-"\n"
-" [input] Is this project deployed as an EAR (with EJB components) or a "
-"WAR \n"
-"(with no EJB support) [ear] ([ear], war, )\n"
-"\n"
-" [input] Enter the Java package name for your session beans [com."
-"mydomain.\n"
-"oc4j_example] [com.mydomain.oc4j_example]\n"
-"org.jboss.seam.tutorial.oc4j.action\n"
-" [input] Enter the Java package name for your entity beans [org.jboss."
-"seam.\n"
-"tutorial.oc4j.action] [org.jboss.seam.tutorial.oc4j.action]\n"
-"org.jboss.seam.tutorial.oc4j.model\n"
-" [input] Enter the Java package name for your test cases [org.jboss."
-"seam.\n"
-"tutorial.oc4j.action.test] [org.jboss.seam.tutorial.oc4j.action.test]\n"
-"org.jboss.seam.tutorial.oc4j.test\n"
-" [input] What kind of database are you using? [hsql] ([hsql], mysql, "
-"oracle,\n"
-" postgres, mssql, db2, sybase, enterprisedb, h2)\n"
-"mysql\n"
-" [input] Enter the Hibernate dialect for your database [org.hibernate.\n"
-"dialect.MySQLDialect] [org.hibernate.dialect.MySQLDialect]\n"
-"\n"
-" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb."
-"jar] \n"
-"[lib/hsqldb.jar]\n"
-"lib/mysql-connector.jar\n"
-" [input] Enter JDBC driver class for your database [com.mysql.jdbc."
-"Driver] \n"
-"[com.mysql.jdbc.Driver]\n"
-"\n"
-" [input] Enter the JDBC URL for your database [jdbc:mysql:///test] \n"
-"[jdbc:mysql:///test]\n"
-"jdbc:mysql:///oc4jexample\n"
-" [input] Enter database username [sa] [sa]\n"
-"username\n"
-" [input] Enter database password [] []\n"
-"password\n"
-" [input] skipping input as property hibernate.default_schema.new has "
-"already \n"
-"been set.\n"
-" [input] Enter the database catalog name (it is OK to leave this blank) "
-"[] []\n"
-"\n"
-" [input] Are you working with tables that already exist in the database? "
-"[n] \n"
-" (y, [n], )\n"
-"y\n"
-" [input] Do you want to drop and recreate the database tables and data "
-"in \n"
-"import.sql each time you deploy? [n] (y, [n], )\n"
-"n\n"
-" [input] Enter your ICEfaces home directory (leave blank to omit "
-"ICEfaces) [] []\n"
-"\n"
-"[propertyfile] Creating new property file: \n"
-"/home/jbalunas/workspace/jboss-seam/seam-gen/build.properties\n"
-" [echo] Installing JDBC driver jar to JBoss server\n"
-" [copy] Copying 1 file to /home/jbalunas/jboss/jboss-4.2.2.GA/server/"
-"default/lib\n"
-" [echo] Type 'seam create-project' to create the new project\n"
-"\n"
-"BUILD SUCCESSFUL]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:490
-#, no-c-format
-msgid ""
-"Type <literal>./seam new-project</literal> to create your project and "
-"<literal>cd /home/jbalunas/workspace/oc4j_example</literal> to the newly "
-"created project."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:497
-#, no-c-format
-msgid "Changes needed for deployment to OC4J"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:498
-#, no-c-format
-msgid "We now need to make some changes to the generated project."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:501
-#, no-c-format
-msgid "Let's start with the configuration files:"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:504
-#, no-c-format
-msgid "build.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:509
-#, no-c-format
-msgid ""
-"Change the default target to archive (we aren't going to cover automatic "
-"deployment to OC4J)."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:513
-#, no-c-format
-msgid "<![CDATA[<project name=\"oc4j_example\" default=\"archive\" basedir=\".\">]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:516
-#, no-c-format
-msgid ""
-"OC4J looks for the drools file <literal>/security.drl</literal> file in the "
-"root of the <literal>war</literal> file instead of the root of the "
-"<literal>ear</literal> file so we need to have the <literal>build.xml</"
-"literal> move it to the correct location at build time. The following must "
-"be added at the top of the <literal> <target name=\"war\" depends="
-"\"compile\" description=\"Build the distribution .war file\"> </literal> "
-"target."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:530
-#, no-c-format
-msgid ""
-"<![CDATA[<copy todir=\"${war.dir}\">\n"
-" <fileset dir=\"${basedir}/resources\" >\n"
-" <include name=\"*.drl\" />\n"
-" </fileset>\n"
-" </copy>]]>"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:537
-#, no-c-format
-msgid "resources/META-INF/persistence-dev.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:542
-#, no-c-format
-msgid ""
-"Alter the <literal>jta-data-source</literal> to be <literal>jdbc/"
-"__oc4jexample</literal> (and use this as the <literal>jndi-name</literal> "
-"when creating the data source in <literal>data-sources.xml</literal> later "
-"during deployment)."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:552
-#, no-c-format
-msgid "Add the properties (described in <literal>jee5/booking</literal> example):"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:557
-#, no-c-format
-msgid ""
-"<![CDATA[<property name=\"hibernate.query.factory_class\"\n"
-" value=\"org.hibernate.hql.classic.ClassicQueryTranslatorFactory\" />\n"
-"<property name=\"hibernate.transaction.manager_lookup_class\"\n"
-" value=\"org.hibernate.transaction.OrionTransactionManagerLookup\" />\n"
-"<property name=\"hibernate.transaction.flush_before_completion\" \n"
-" value=\"true\"/>\n"
-"<property name=\"hibernate.cache.provider_class\" \n"
-" value=\"org.hibernate.cache.HashtableCacheProvider\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:560
-#, no-c-format
-msgid "Remove the JBoss AS specific method of exposing the EntityManagerFactory:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:564
-#, no-c-format
-msgid ""
-"<![CDATA[<property \n"
-" name=\"jboss.entity.manager.factory.jndi.name\" \n"
-" value=\"java:/oc4j_exampleEntityManagerFactory\">]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:567
-#, no-c-format
-msgid ""
-"You'll need to alter <literal>persistence-prod.xml</literal> as well if you "
-"want to deploy to OC4J using the prod profile."
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:577
-#, no-c-format
-msgid "resources/META-INF/jboss-app.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:580
-#, no-c-format
-msgid ""
-"You can delete this file as we aren't deploying to JBoss AS ( <literal>jboss-"
-"app.xml</literal> is used to enable classloading isolation in JBoss AS)"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:586
-#, no-c-format
-msgid "resources/*-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:589
-#, no-c-format
-msgid ""
-"You can delete these file as we aren't deploying to JBoss AS (these files "
-"define datasources in JBoss AS, in OC4J you have to edit the master "
-"<literal>data-sources.xml</literal> file)"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:598
-#, no-c-format
-msgid "resources/WEB-INF/components.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:603
-#, no-c-format
-msgid ""
-"Enable container managed transaction integration - add the <literal> <"
-"transaction:ejb-transaction /> </literal> component, and it's namespace "
-"declaration <literal> xmlns:transaction=\"http://jboss.com/products/seam/"
-"transaction\" </literal>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:612
-#, no-c-format
-msgid ""
-"Alter the <literal>jndi-pattern</literal> to <literal> java:comp/env/"
-"oc4j_example/#{ejbName}/local </literal>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:619
-#, no-c-format
-msgid ""
-"We want to use a Seam Managed Persistence Context in our application. "
-"Unfortunately OC4J doesn't expose the EntityManagerFactory in JNDI, but Seam "
-"provides a built-in manager component. To activate add the following entry:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:627
-#, no-c-format
-msgid ""
-"<![CDATA[<persistence:entity-manager-factory\n"
-" auto-create=\"true\" \n"
-" name=\"oc4jEntityManagerFactory\"\n"
-" persistence-unit-name=\"oc4j_example\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:628
-#, no-c-format
-msgid ""
-"We then need to tell Seam to use it, so we alter the <literal>managed-"
-"persistence-context</literal> injecting the Entity Manager Factory into the "
-"existing element:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:635
-#, no-c-format
-msgid ""
-"<![CDATA[<persistence:managed-persistence-context\n"
-" name=\"entityManager\"\n"
-" auto-create=\"true\"\n"
-" entity-manager-factory=\"#{oc4jEntityManagerFactory}\" />]]>"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:641
-#, no-c-format
-msgid "resources/WEB-INF/web.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:644
-#, no-c-format
-msgid ""
-"You must add the Seam container managed transaction integration EJB entry "
-"below. Remember for OC4j you need to declare all your EJBs here if you "
-"modify the application further."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:650
-#, no-c-format
-msgid ""
-"<![CDATA[<ejb-local-ref>\n"
-" <ejb-ref-name>\n"
-" oc4j_example/EjbSynchronizations/local\n"
-" </ejb-ref-name>\n"
-" <ejb-ref-type>Session</ejb-ref-type>\n"
-" <local>\n"
-" org.jboss.seam.transaction.LocalEjbSynchronizations\n"
-" </local>\n"
-" <ejb-link>EjbSynchronizations</ejb-link>\n"
-"</ejb-local-ref>]]>"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:655
-#, no-c-format
-msgid "resources/META-INF/orion-application.xml"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:660
-#, no-c-format
-msgid ""
-"This is a file that you must create so that RichFaces and Ajax4Jsf "
-"stylesheets will work with OC4J. This file basically tells OC4J not force "
-"its own inherited URL settings."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:666
-#, no-c-format
-msgid ""
-"<![CDATA[<?xml version = '1.0' encoding = 'utf-8'?>\n"
-"<orion-application\n"
-" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-" xsi:noNamespaceSchemaLocation=\"http://xmlns.oracle.com/oracleas/"
-"schema/\n"
-" orion-"
-"application-10_0.xsd\"\n"
-" schema-major-version=\"10\"\n"
-" schema-minor-version=\"0\"\n"
-" component-classification=\"internal\">\n"
-"\n"
-" <imported-shared-libraries>\n"
-" <remove-inherited name=\"oracle.xml\"/>\n"
-" </imported-shared-libraries>\n"
-"</orion-application>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:669
-#, no-c-format
-msgid ""
-"Now you need to tell the <literal>build.xml</literal> file that it needs to "
-"copy this file to the <literal>ear</literal> archive. Find the <literal> <"
-"target name=\"ear\" description=\"Build the EAR\"> </literal> target and "
-"modify the <literal> <copy todir=\"${ear.dir}/META-INF\"> </literal> "
-"section to look like the following:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:681
-#, no-c-format
-msgid ""
-"<![CDATA[<copy todir=\"${ear.dir}/META-INF\">\n"
-" <fileset dir=\"${basedir}/resources/META-INF\">\n"
-" <include name=\"application.xml\" />\n"
-" <include name=\"orion-application.xml\"/>\n"
-" <include name=\"jboss-app.xml\" />\n"
-" </fileset>\n"
-" </copy>]]>"
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:689
-#, no-c-format
-msgid "Extra jar dependencies"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:690
-#, no-c-format
-msgid ""
-"This application has similar requirements as the <literal>jee5/booking</"
-"literal> example above."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:692
-#, no-c-format
-msgid ""
-"The <literal>build.xml</literal> must be modified to add the jars listed "
-"below to the generated archive files. Look for the <literal><fileset dir="
-"\"${basedir}\"></literal> section below and add the imports underneath "
-"the other libraries being imported."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:699
-#, no-c-format
-msgid ""
-"<![CDATA[<target name=\"ear\" description=\"Build the EAR\">\n"
-" <copy todir=\"${ear.dir}\">\n"
-" <fileset dir=\"${basedir}/resources\">\n"
-" <include name=\"*jpdl.xml\" />\n"
-" <include name=\"*hibernate.cfg.xml\" />\n"
-" <include name=\"jbpm.cfg.xml\" />\n"
-" <include name=\"*.drl\" />\n"
-" </fileset>\n"
-" <fileset dir=\"${lib.dir}\">\n"
-" <include name=\"jboss-seam.jar\" />\n"
-" </fileset>\n"
-" <fileset dir=\"${basedir}\">\n"
-" <include name=\"lib/jbpm*.jar\" />\n"
-" <include name=\"lib/jboss-el.jar\" />\n"
-" <include name=\"lib/drools-*.jar\"/>\n"
-" <include name=\"lib/janino*.jar\"/>\n"
-" <include name=\"lib/antlr-*.jar\"/>\n"
-" <include name=\"lib/mvel*.jar\"/>\n"
-" <include name=\"lib/richfaces-api*.jar\" />\n"
-" </fileset>\n"
-" </copy>\n"
-" <copy todir=\"${ear.dir}/META-INF\">\n"
-" <fileset dir=\"${basedir}/resources/META-INF\">\n"
-" <include name=\"application.xml\" />\n"
-" <include name=\"jboss-app.xml\" />\n"
-" </fileset>\n"
-" </copy>\n"
-"</target>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:702
-#, no-c-format
-msgid "Hibernate:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:705
-#, no-c-format
-msgid ""
-"<![CDATA[<include name=\"lib/hibernate.jar\"/>\n"
-"<include name=\"lib/hibernate-annotations.jar\"/>\n"
-"<include name=\"lib/hibernate-commons-annotations.jar\"/>\n"
-"<include name=\"lib/hibernate-entitymanager.jar\"/>\n"
-"<include name=\"lib/hibernate-search.jar\"/>\n"
-"<include name=\"lib/hibernate-validator.jar\"/>\n"
-"<include name=\"lib/commons-logging.jar\"/>\n"
-"<include name=\"lib/commons-collections.jar\"/>\n"
-"<include name=\"lib/jboss-common-core.jar\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:708
-#, no-c-format
-msgid ""
-"Drools — because we are using Drools to provide Seam Security rules, "
-"we need to add in Eclipse JDT compiler (you don't need this on JBoss AS; "
-"again this is due to OC4J's classloading):"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:714
-#, no-c-format
-msgid "<![CDATA[<include name=\"lib/core.jar\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:717
-#, no-c-format
-msgid ""
-"Third party jars — most of these are only needed because of OC4J's "
-"classloading:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:721
-#, no-c-format
-msgid ""
-"<![CDATA[<include name=\"lib/javassist.jar\"/>\n"
-"<include name=\"lib/quartz.jar\"/>\n"
-"<include name=\"lib/dbunit.jar\"/>\n"
-"<include name=\"lib/jboss-embedded-api.jar\"/>\n"
-"<include name=\"lib/dom4j.jar\"/> \n"
-"<include name=\"lib/lucene-core.jar\"/>\n"
-"<include name=\"lib/cglib.jar\"/>\n"
-"<include name=\"lib/asm.jar\"/>\n"
-"<include name=\"lib/commons-beanutils.jar\"/>\n"
-"<include name=\"lib/commons-digester.jar\"/>\n"
-"<include name=\"lib/antlr.jar\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:725
-#, no-c-format
-msgid "You should end up with something like:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:728
-#, no-c-format
-msgid ""
-"<![CDATA[<fileset dir=\"${basedir}\">\n"
-" <include name=\"lib/jbpm*.jar\" />\n"
-" <include name=\"lib/jboss-el.jar\" />\n"
-" <include name=\"lib/drools-*.jar\"/>\n"
-" <include name=\"lib/janino*.jar\"/>\n"
-" <include name=\"lib/antlr-*.jar\"/>\n"
-" <include name=\"lib/mvel*.jar\"/>\n"
-" <include name=\"lib/richfaces-api*.jar\" />\n"
-" <include name=\"lib/hibernate.jar\"/>\n"
-" <include name=\"lib/hibernate-annotations.jar\"/>\n"
-" <include name=\"lib/hibernate-commons-annotations.jar\"/>\n"
-" <include name=\"lib/hibernate-entitymanager.jar\"/>\n"
-" <include name=\"lib/hibernate-search.jar\"/>\n"
-" <include name=\"lib/hibernate-validator.jar\"/>\n"
-" <include name=\"lib/commons-logging.jar\"/>\n"
-" <include name=\"lib/commons-collections.jar\"/>\n"
-" <include name=\"lib/jboss-common-core.jar\"/>\n"
-" <include name=\"lib/core.jar\"/>\n"
-" <include name=\"lib/javassist.jar\"/>\n"
-" <include name=\"lib/quartz.jar\"/>\n"
-" <include name=\"lib/dbunit.jar\"/>\n"
-" <include name=\"lib/jboss-embedded-api.jar\"/>\n"
-" <include name=\"lib/dom4j.jar\"/> \n"
-" <include name=\"lib/lucene-core.jar\"/>\n"
-" <include name=\"lib/cglib.jar\"/>\n"
-" <include name=\"lib/asm.jar\"/>\n"
-" <include name=\"lib/commons-beanutils.jar\"/>\n"
-" <include name=\"lib/commons-digester.jar\"/>\n"
-" <include name=\"lib/antlr.jar\"/>\n"
-"</fileset>]]>"
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:733
-#, no-c-format
-msgid "Building and deploying the seam-gen'd application to OC4J"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:735
-#, no-c-format
-msgid ""
-"These instructions are very similar to the ones in <xref linkend=\"oc4j-app-"
-"deploy\"/> but with the correct references for the <literal>oc4j_example</"
-"literal> application."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:741
-#, no-c-format
-msgid ""
-"Build your application by calling <literal>ant</literal> in the base "
-"directory of your project (ex. <literal>/home/jbalunas/workspace/"
-"oc4j_example</literal> ). The target of the build will be <literal>dist/"
-"oc4j_example.ear</literal> ."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:749
-#, no-c-format
-msgid ""
-"Copy the <literal>mysql-connector.jar</literal> file to the <literal>"
-"$ORACLE_HOME/j2ee/home/applib</literal> directory so that jdbc drivers are "
-"available."
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:756
-#, no-c-format
-msgid "$ORACLE_HOME/j2ee/home/config/data-sources.xml"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:761
-#, no-c-format
-msgid ""
-"<![CDATA[<managed-data-source\n"
-" connection-pool-name=\"oc4j-example-connection-pool\"\n"
-" jndi-name=\"jdbc/__oc4jexample\"\n"
-" name=\"oc4j-example-managed-data-source\" />\n"
-"<connection-pool\n"
-" name=\"oc4j-example-connection-pool\">\n"
-" <connection-factory\n"
-" factory-class=\"com.mysql.jdbc.Driver\"\n"
-" user=\"username\" \n"
-" password=\"password\"\n"
-" url=\"jdbc:mysql:///oc4j\" />\n"
-"</connection-pool>]]>"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:765
-#, no-c-format
-msgid "$ORACLE_HOME/j2ee/home/config/server.xml"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:769
-#, no-c-format
-msgid ""
-"<![CDATA[<application name=\"oc4j_example\"\n"
-" path=\"../../home/applications/oc4j_example.ear\"\n"
-" parent=\"default\"\n"
-" start=\"true\" />]]>"
-msgstr ""
-
-#. Tag: literal
-#: Oc4j.xml:772
-#, no-c-format
-msgid "$ORACLE_HOME/j2ee/home/config/default-web-site.xml"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:777
-#, no-c-format
-msgid ""
-"<![CDATA[<web-app application=\"oc4j_example\"\n"
-" name=\"oc4j_example\" \n"
-" load-on-startup=\"true\"\n"
-" root=\"/oc4j_example\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:781
-#, no-c-format
-msgid ""
-"Start/stop OC4J following instructions in the <literal>Installation and "
-"operation of OC4J</literal> section above."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:786
-#, no-c-format
-msgid "Checkout the app at: <literal>http://localhost:8888/oc4j_example</literal>"
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:795
-#, no-c-format
-msgid "Extending example with reverse engineered CRUD and Drools"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:797
-#, no-c-format
-msgid ""
-"In this section we extend the basic <literal>seam-gen</literal> application "
-"into a full blown CRUD application based on an existing database. Plus we "
-"will add <literal>Drools</literal> based security as well."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:802
-#, no-c-format
-msgid "Have <literal>seam-gen</literal> generate your CRUD applications"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:804
-#, no-c-format
-msgid ""
-"Type <literal>./seam generate-entities</literal> in the base directory of "
-"your seam distribution. This will create the entities, the Seam Application "
-"Framework classes and the relevant views for the CRUD application."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:809
-#, no-c-format
-msgid ""
-"That's it...no really...that's it. Build and deploy as before and see for "
-"yourself."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:814
-#, no-c-format
-msgid "Hook up drools authentication using your new CRUD application"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:816
-#, no-c-format
-msgid ""
-"As stated above this section assumes your database had a <literal>User</"
-"literal> table with <literal>username</literal> and <literal>password</"
-"literal> columns with at least one entry. If you don't have this you may "
-"need to modify the <literal>authenticate</literal> method below."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:822
-#, no-c-format
-msgid ""
-"Lets link our <literal>User</literal> entity into Seam Security by making "
-"our authenticator class a Stateless Session Bean (OC4J is a EJB3 container "
-"after all!):"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:830
-#, no-c-format
-msgid ""
-"Add the <literal>@Stateless</literal> annotation to the "
-"<literal>Authenticator</literal> class."
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:836
-#, no-c-format
-msgid "Rename the class to <literal>AuthenticatorAction</literal>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:841
-#, no-c-format
-msgid ""
-"Create an interface called <literal>Authenticator</literal> which "
-"<literal>AuthenticatorAction</literal> implements (EJB3 requires session "
-"beans to have a local interface). Annotate the interface with "
-"<literal>@Local</literal> , and add a single method with same signature as "
-"the <literal>authenticate</literal> in <literal>AuthenticatorAction</"
-"literal> ."
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:855
-#, no-c-format
-msgid ""
-"<![CDATA[@Name(\"authenticator\") @Stateless public class\n"
-" AuthenticatorAction implements Authenticator {]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:858
-#, no-c-format
-msgid ""
-"<![CDATA[@Local public interface Authenticator { \n"
-" public boolean authenticate(); \n"
-"}]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:861
-#, no-c-format
-msgid ""
-"Use <literal>@PersistenceContext</literal> to inject an EntityManager by "
-"adding this line the <literal>AuthenticatorAction</literal> class:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:867
-#, no-c-format
-msgid "<![CDATA[@PersistenceContext private EntityManager entityManager;]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:870
-#, no-c-format
-msgid "Implement authenticate:"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:873
-#, no-c-format
-msgid ""
-"<![CDATA[public boolean authenticate() {\n"
-" List <User> users = entityManager .createQuery(\"select u from User u "
-"where \n"
-" u.username = #{identity.username} and \n"
-" u.password = #{identity.password}\") .getResultList();\n"
-" if (users.size() == 1) {\n"
-" identity.addRole(\"admin\"); \n"
-" return true; \n"
-" } else {\n"
-" return false; \n"
-" } \n"
-"}]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:876
-#, no-c-format
-msgid "And then add the EJB3 reference to <literal>web.xml</literal> :"
-msgstr ""
-
-#. Tag: programlisting
-#: Oc4j.xml:880
-#, no-c-format
-msgid ""
-"<![CDATA[<ejb-local-ref>\n"
-" <ejb-ref-name>\n"
-" oc4j_example/AuthenticatorAction/local\n"
-" </ejb-ref-name>\n"
-" <ejb-ref-type>Session</ejb-ref-type>\n"
-" <local>\n"
-" org.jboss.seam.tutorial.oc4j.action.Authenticator\n"
-" </local>\n"
-" <ejb-link>AuthenticatorAction</ejb-link>\n"
-"</ejb-local-ref>]]>"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:884
-#, no-c-format
-msgid ""
-"Build and deploy as before and notice that now only actual username and "
-"passwords are accepted."
-msgstr ""
-
-#. Tag: title
-#: Oc4j.xml:892
-#, no-c-format
-msgid "Finishing up"
-msgstr ""
-
-#. Tag: para
-#: Oc4j.xml:893
-#, no-c-format
-msgid ""
-"That's it, we're through. You now have a great starting point for any Seam "
-"based application deployed to OC4J."
-msgstr ""
-
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Seam_Reference_Guide.po
===================================================================
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Version_Info.po
===================================================================
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Weblogic.po
===================================================================
--- projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Weblogic.po 2008-12-09 06:26:10 UTC (rev 82128)
+++ projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Weblogic.po 2008-12-09 06:56:13 UTC (rev 82129)
@@ -1,1748 +0,0 @@
-# Language ja-JP translations for PACKAGE package.
-# Automatically generated, 2008.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Weblogic.xml:2
-#, no-c-format
-msgid "Seam on BEA's Weblogic"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:4
-#, no-c-format
-msgid ""
-"Weblogic 10.X is BEA's JEE5 server offering, currently 10.0.MP1 is their "
-"stable release, and 10.3.TP is their latest tech preview release. Seam "
-"applications can be deployed and developed on Weblogic servers, and this "
-"chapter will show you how. There are some known issues with the Weblogic "
-"servers that will need to be worked around, and configuration changes that "
-"are needed."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:11
-#, no-c-format
-msgid ""
-"First step is to get Weblogic downloaded, installed and running (no small "
-"feat). Then we'll talk about Seam's JEE5 example and the hurdles to getting "
-"it running, and what blockers exist. After that the JPA example will be "
-"modified and deployed to the server. Then finally we will create "
-"<literal>seam-gen</literal> application and get it up and running to provide "
-"a jump start to your application."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:19
-#, no-c-format
-msgid "Installation and operation of Weblogic"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:20
-#, no-c-format
-msgid ""
-"First things first we need to get the server installed - and there is a "
-"choice to be made. Weblogic 10.0.MP1 is the most recent stable release, "
-"while 10.3.TP is a technical preview version that fixes some things and "
-"breaks others."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:26
-#, no-c-format
-msgid ""
-"<literal>Weblogic 10.0.MP1</literal> — <ulink url=\"http://commerce."
-"bea.com/showproduct.jsp?family=WLS&major=10&minor=1\"> Download page "
-"</ulink>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:30
-#, no-c-format
-msgid ""
-"10.0.MP1 has a known issue with EJBs that use <literal>varargs</literal> in "
-"their methods (it confuses them as <literal>transient</literal> ). This "
-"causes exceptions when Weblogic attempts to compile the Seam EJBs as "
-"<literal>varargs</literal> are used. There seems to be no work around to "
-"this issue in 10.0.MP1. Because of this only the <literal>jpa</literal> and "
-"WAR based <literal>seam-gen</literal> examples work with this version. See "
-"the <literal>jee5/booking</literal> example for more details."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:42
-#, no-c-format
-msgid ""
-"<literal>Weblogic 10.3.TP</literal> — <ulink url=\"http://commerce.bea."
-"com/showproduct.jsp?family=WLS&major=10.3Tech&minor=-1&"
-"DL=www_WLS_10-3TechPreview_icon&WT.ac=DL_www_WLS_10.3_TechPreviewicon\"> "
-"Download page </ulink>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:46
-#, no-c-format
-msgid ""
-"This version still has not fixed the <literal>varargs</literal> bug, and "
-"there is a new issue with EJBs that do not use <literal>kodo</literal> "
-"(BEA's implementation of JPA). See the <literal>jee5/booking</literal> "
-"example for more details. However if the <literal>varargs</literal> issue is "
-"going to get fixed it will most likely be an update to this version."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:56
-#, no-c-format
-msgid ""
-"For the reasons listed above, and the fact that 10.3.TP gets us closer to "
-"the goal of Seam EJB3 support on Weblogic, 10.3.TP will be used for the "
-"examples below."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:61
-#, no-c-format
-msgid "Installing 10.3.TP"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:63
-#, no-c-format
-msgid ""
-"Here are the quick steps to installing Weblogic 10.3.TP. For more details or "
-"if you are having any issues please check with the BEA docs at the <ulink "
-"url=\"http://edocs.bea.com/wls/essex/TechPreview/\"> Tech Preview Doc Center "
-"</ulink> . Here we install the RHEL 5 version using the graphical installer:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:72
-#, no-c-format
-msgid ""
-"Follow the link given above for 10.3.TP and download the correct version for "
-"your environment. You will need to sign up for an account with BEA in order "
-"to do this."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:77
-#, no-c-format
-msgid ""
-"You may need to change the the <literal>server103tp_XX.bin</literal> file to "
-"be executable:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:80
-#, no-c-format
-msgid "chmod a+x server103tp_XX.bin"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:83
-#, no-c-format
-msgid "Execute the install:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:84
-#, no-c-format
-msgid "./server103tp_XX.bin"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:87
-#, no-c-format
-msgid ""
-"When the graphical install loads, you need to set the BEA home location. "
-"This is where all BEA applications are installed. This location will be "
-"known as <literal>$BEA_HOME</literal> in this document e.g.:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:92
-#, no-c-format
-msgid "/home/jbalunas/bea"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:95
-#, no-c-format
-msgid ""
-"Select <literal>Complete</literal> as the installation type. You do not need "
-"all the extras of the complete install (such as struts and beehive "
-"libraries), but it will not hurt."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:101
-#, no-c-format
-msgid "Then you need to tell it where to install the server components:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:103
-#, no-c-format
-msgid "$BEA_HOME/wlserver_10.3tp"
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:108
-#, no-c-format
-msgid "Creating your Weblogic domain"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:109
-#, no-c-format
-msgid ""
-"A Weblogic domain is similar to a JBoss server configuration - it is a self "
-"contained server instance. The Weblogic server you just installed has some "
-"example domains, but we are going to create one just for the seam examples. "
-"You can use the existing domains if you wish (modify the instructions as "
-"needed)."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:117
-#, no-c-format
-msgid "Start up the Weblogic configuration wizard:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:118
-#, no-c-format
-msgid "$BEA_HOME/wlserver_10.3tp/common/bin/config.sh"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:121
-#, no-c-format
-msgid ""
-"Choose to create a new domain, configured to support <literal>Weblogic "
-"Server TP</literal>. Note that this is the default domain option."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:126
-#, no-c-format
-msgid "Set a username and password for this domain."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:129
-#, no-c-format
-msgid ""
-"Next choose <literal>Development Mode</literal> and the default JDK when "
-"given the option."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:133
-#, no-c-format
-msgid ""
-"The next screen asks if you want to customize any setting. Select "
-"<literal>No</literal>."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:137
-#, no-c-format
-msgid ""
-"Finally set the name of the domain to <literal>seam_examples</literal> and "
-"leave the default domain location."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:144
-#, no-c-format
-msgid "How to Start/Stop/Access your domain"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:145
-#, no-c-format
-msgid ""
-"Now that the server is installed and the domain is created you need to know "
-"how to start and stop it, plus how to access its configuration console."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:150
-#, no-c-format
-msgid "Starting the domain:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:151
-#, no-c-format
-msgid ""
-"This is the easy part - go to the <literal> $BEA_HOME/user_projects/domains/"
-"seam_examples/bin </literal> directory and run the <literal>./startWeblogic."
-"sh</literal> script."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:157
-#, no-c-format
-msgid "Accessing the configuration console:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:158
-#, no-c-format
-msgid ""
-"Launch <literal>http://127.0.0.1:7001/console</literal> in your web browser. "
-"It will ask for your username and password that you entered before. We won't "
-"get into this much now, but this is the starting point for a lot of the "
-"various configurations that are needed later."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:166
-#, no-c-format
-msgid "Stopping the domain:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:167
-#, no-c-format
-msgid "There are a couple of options here:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:170
-#, no-c-format
-msgid "The recommended way is through the configuration console:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:174
-#, no-c-format
-msgid ""
-"Select <literal>seam-examples</literal> on the left hand side of the console."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:179
-#, no-c-format
-msgid "Choose the <literal>Control</literal> tab in the middle of the page."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:184
-#, no-c-format
-msgid "Select the check box <literal>AdminServer</literal> in the table."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:189
-#, no-c-format
-msgid ""
-"Choose <literal>Shutdown</literal> just above the table, and select either "
-"<literal>When work completes</literal> or <literal>Force shutdown now</"
-"literal> as appropriate."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:196
-#, no-c-format
-msgid "Then finally confirm that you want to shut this server down."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:202
-#, no-c-format
-msgid ""
-"Hitting <literal>Ctrl-C</literal> in the terminal where you started the "
-"domain."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:204
-#, no-c-format
-msgid ""
-"No negative effects have been seen, but we would not recommend doing this "
-"while in the middle of configuration changes in the console."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:212
-#, no-c-format
-msgid "A note on Weblogic classloading"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:213
-#, no-c-format
-msgid ""
-"When using the <literal>@DOMAIN/autodeploy</literal> directory as described "
-"in this chapter you may see <literal>NoClassDefFound</literal> exceptions. "
-"If you see this try restarting the Weblogic server. If you still see it "
-"remove the auto-deployed EAR/WAR files, restart the server, and redeploy. We "
-"could not find a specific reason for this, but others seem to be having this "
-"issue as well."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:228 Weblogic.xml:300
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:230
-#, no-c-format
-msgid ""
-"Do you want to run Seam using EJB's on Weblogic? If so there are some "
-"blockers that keep it from working. This section describes what changes are "
-"needed to the <literal>jee5/booking</literal> example to get it as close to "
-"deploying as possible. First we'll talk about the blockers and what they "
-"effect."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:237
-#, no-c-format
-msgid "EJB Blockers with Weblogic"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:238
-#, no-c-format
-msgid ""
-"For several releases of Weblogic there has been an issue with compiling "
-"EJB's that use variable arguments in their methods. This is confirmed in the "
-"Weblogic 9.X and 10.X versions. We had hoped that the issue would be "
-"resolved in the tech preview release, but it is not. Seam uses variable "
-"arguments in its internal EJB's and so until this is fixed Seam with EJB's "
-"will not work."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:245
-#, no-c-format
-msgid ""
-"The gist of the issue is that the Weblogic EJB compiler believes that "
-"methods that use <literal>varargs</literal> are <literal>transient</literal> "
-"and the deployment will fail with exceptions like below: <programlisting><!"
-"[CDATA[java.io.IOException: Compiler failed executable.exec: \n"
-"/home/jbalunas/bea/wlserver_10.3tp/user_projects/domains/seam_examples/"
-"servers/AdminServer\n"
-"/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n"
-"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:194: "
-"modifier transient \n"
-"not allowed here\n"
-" public transient javax.ejb.Timer scheduleAsynchronousEvent(java.lang."
-"String arg0,\n"
-" java.lang.Object[] arg1)\n"
-" ^\n"
-"/home/jbalunas/bea/wlserver_10.3tp/user_projects/domains/seam_examples/"
-"servers/AdminServer\n"
-"/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n"
-"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:275: "
-"modifier transient\n"
-"not allowed here\n"
-" public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String "
-"arg0, \n"
-" org.jboss.seam.async.TimerSchedule arg1, java.lang.Object[] arg2)]]></"
-"programlisting> BEA says that this is a bug with Java specification. Sun "
-"admits the issue, and provides a work around, and will not fix the core "
-"issue. <itemizedlist> <listitem> <para><ulink url=\"http://forums.bea.com/"
-"thread.jspa?threadID=300002074\"> BEA forum</ulink> — Discusses the "
-"issue and suggests waiting for a new release of 10.X</para> </listitem> "
-"<listitem> <para><ulink url=\"http://forums.bea.com/thread.jspa?"
-"messageID=300006290\"> BEA forum</ulink> — Discusses response from BEA "
-"support and that BEA is saying it is an issue with the spec with links to "
-"the bug.</para> </listitem> <listitem> <para><ulink url=\"http://bugs.sun."
-"com/bugdatabase/view_bug.do?bug_id=6516895\"> Sun bug report </ulink> "
-"— Describes details of the issue, but says that it will not be fixed.</"
-"para> </listitem> </itemizedlist> So what does that mean to us? At least for "
-"now EJB's with variable arguments will not run on Weblogic."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:279
-#, no-c-format
-msgid "Secondary issue with the Tech Preview"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:280
-#, no-c-format
-msgid ""
-"A less severe issue is also present in the tech preview version of Weblogic. "
-"You can not use any JPA provider with EJB's except for the default "
-"<literal>kodo</literal> or <literal>openJPA</literal> implementation. As you "
-"set up this example you will run into this issue before the "
-"<literal>varargs</literal> problem. Unfortunately using <literal>kodo</"
-"literal> or <literal>openJPA</literal> does not help with the blocker "
-"described above but is important to know."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:290
-#, no-c-format
-msgid ""
-"Other users have seen this issue with the tech preview and I would hope/"
-"expect that it will be fixed in future releases ( <ulink url=\"http://forums."
-"bea.com/thread.jspa?threadID=300004403\"> BEA Forum</ulink>). The forum "
-"entry has the exact stack trace, and the response from BEA."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:301
-#, no-c-format
-msgid ""
-"In this section will will quickly go over the steps needed to get the "
-"<literal>jee5/booking</literal> example to the point that blocker shows "
-"itself."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:306
-#, no-c-format
-msgid "Setting up the hsql datasource"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:307
-#, no-c-format
-msgid ""
-"This example uses the in memory hypersonic database, and the correct data "
-"source needs to be set up. The admin console uses a wizard like set of pages "
-"to configure it."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:313
-#, no-c-format
-msgid ""
-"Copy <literal>hsqldb.jar</literal> to weblogic domain's shared library "
-"directory: <literal> cp ../../seam-gen/lib/hsqldb.jar /home/jbalunas/bea/"
-"user_projects/domains/seam_examples/lib</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:320
-#, no-c-format
-msgid ""
-"Start up the server and navigate to the administration console following"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:325
-#, no-c-format
-msgid ""
-"On the left side tree navigate <literal>seam_examples - Services- JDBC - "
-"Data Sources</literal>."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:330
-#, no-c-format
-msgid ""
-"You must lock the domain configuration using the button in the upper left "
-"box."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:334
-#, no-c-format
-msgid ""
-"Then select button <literal>New</literal> button at the top of the data "
-"source table"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:338
-#, no-c-format
-msgid "Fill in the following:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:341
-#, no-c-format
-msgid "Name: <literal>seam-jee5-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:346
-#, no-c-format
-msgid "JNDI Name: <literal>seam-jee5-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:351
-#, no-c-format
-msgid "Database Type and Driver: <literal>other</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:355 Weblogic.xml:386 Weblogic.xml:414
-#, no-c-format
-msgid "Select <literal>Next</literal> button"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:361
-#, no-c-format
-msgid ""
-"Select <literal>Next</literal> button on the <literal>Transaction Options</"
-"literal> page"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:366 Weblogic.xml:392
-#, no-c-format
-msgid ""
-"Fill in the following on the <literal>Connection Properties</literal> page:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:370
-#, no-c-format
-msgid "Database Name: <literal>hsqldb</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:374
-#, no-c-format
-msgid "Host Name: <literal>127.0.0.1</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:378
-#, no-c-format
-msgid "Port: <literal>9001</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:382 Weblogic.xml:406
-#, no-c-format
-msgid "Username: <literal>sa</literal> will empty password fields."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:396
-#, no-c-format
-msgid "Driver Class Name: <literal>org.hsqldb.jdbcDriver</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:401
-#, no-c-format
-msgid "URL: <literal>jdbc:hsqldb:.</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:410
-#, no-c-format
-msgid "Leave the rest of the fields empty."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:420
-#, no-c-format
-msgid ""
-"Choose the target domain for the data source in our case the only one "
-"<literal>AdminServer</literal>. Click <literal>Next</literal>."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:425
-#, no-c-format
-msgid ""
-"Finally - apply the changes by selecting the <literal>Apply Changes</"
-"literal> button in the upper left corner."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:432
-#, no-c-format
-msgid "Configuration and Build changes"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:436
-#, no-c-format
-msgid "resources/META-INF/persistence.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:441
-#, no-c-format
-msgid ""
-"Because the tech preview version will only work with <literal>kodo</literal> "
-"or <literal>openJPA</literal> as the JPA provider you must change the "
-"provider to :"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:446
-#, no-c-format
-msgid ""
-"<![CDATA[<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</"
-"provider>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:449
-#, no-c-format
-msgid ""
-"Next you need to change the <literal>jta-data-source</literal> to what you "
-"entered above :"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:453
-#, no-c-format
-msgid "<![CDATA[<jta-data-source>seam-jee5-ds</jta-data-source>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:456
-#, no-c-format
-msgid ""
-"The other properties in the file are hibernate specific and are not used by "
-"<literal>openJPA</literal> but can be left in."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:467
-#, no-c-format
-msgid "Deploying the Application"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:468
-#, no-c-format
-msgid ""
-"There are some changes needed to the build script and then we can attempt to "
-"deploy the app."
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:473 Weblogic.xml:828
-#, no-c-format
-msgid "build.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:476
-#, no-c-format
-msgid ""
-"Weblogic does not ship with a default JSF implementation so we need to add "
-"the JSF libraries to the WAR. Add the following to the <literal>build.xml</"
-"literal> and this will add the needed jars. Note that <literal>richfaces-api."
-"jar</literal> is only needed if using the admin console to deploy. For some "
-"reason Weblogic needs it in the <literal>WAR</literal> when it scans the "
-"application."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:485
-#, no-c-format
-msgid ""
-"<![CDATA[<fileset id=\"war.lib.extras\" dir=\"${seam.dir}\">\n"
-" <include name=\"lib/jsf-api.jar\" />\n"
-" <include name=\"lib/jsf-impl.jar\" />\n"
-" <include name=\"lib/richfaces-api.jar\" />\n"
-"</fileset>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:490
-#, no-c-format
-msgid ""
-"Now we can build the application by running <literal>ant archive</literal> "
-"at the base of the example directory."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:493
-#, no-c-format
-msgid ""
-"Because we chose to create our Weblogic domain in development mode we can "
-"deploy the application by putting the EAR file in the domains autodeploy "
-"directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:497
-#, no-c-format
-msgid ""
-"cp ./dist/jboss-seam-jee5.ear \n"
-" /home/jbalunas/bea/user_projects/domains/seam_examples/autodeploy"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:499
-#, no-c-format
-msgid ""
-"Here is where we see the <literal>varargs</literal> issue. In the console "
-"output you will some Kodo warnings, then exceptions and compile errors like "
-"the one below."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:504
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced \n"
-" the following Java compiler error message:\n"
-"\n"
-"/home/jbalunas/bea/user_projects/domains/seam_examples/servers/AdminServer/"
-"cache/\n"
-"EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n"
-"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:32:\n"
-" modifier transient not allowed here\n"
-" public transient void scheduleTransactionSuccessEvent(java.lang.String "
-"arg0,\n"
-" java.lang.Object[] arg1)\n"
-" ^\n"
-"/home/jbalunas/bea/user_projects/domains/seam_examples/servers/AdminServer/"
-"cache/\n"
-"EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/\n"
-"TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:113:\n"
-" modifier transient not allowed here\n"
-" public transient javax.ejb.Timer scheduleAsynchronousEvent(java.lang."
-"String arg0,\n"
-" java.lang.Object[] arg1)\n"
-"\n"
-"...\n"
-"]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:506
-#, no-c-format
-msgid ""
-"This is as far as we can go with Weblogic using EJB's with seam until the "
-"<literal>varargs</literal> issue is resolved."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:515
-#, no-c-format
-msgid "The <literal>jpa</literal> booking example"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:516
-#, no-c-format
-msgid ""
-"This is the Hotel Booking example implemented in Seam POJO and Hibernate JPA "
-"and does not require EJB3 support to run. The example already has a breakout "
-"of configurations and build scripts for many of the common containers "
-"including Weblogic 10.X"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:521
-#, no-c-format
-msgid ""
-"First we'll build the example for Weblogic 10.x and do the needed steps to "
-"deploy. Then we'll talk about what is different between the Weblogic "
-"versions, and with the JBoss AS version."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:526
-#, no-c-format
-msgid "Building and deploying <literal>jpa</literal> booking example"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:529
-#, no-c-format
-msgid ""
-"Step one setup the datasource, step two build the app, step three deploy."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:533
-#, no-c-format
-msgid "Setting up the datasource"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:535
-#, no-c-format
-msgid ""
-"The Weblogic 10.X version of the example uses the in memory hsql database "
-"instead of the built in PointBase database. If you wish to use the PointBase "
-"database you must setup a PointBase datasource, and adjust the hibernate "
-"setting in <literal>persistence.xml</literal> to use the PointBase dialect. "
-"For reference the <literal>jpa/weblogic92</literal> example uses PointBase."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:543
-#, no-c-format
-msgid ""
-"Configuring the datasource is very similar to the jee5 <xref linkend="
-"\"weblogic-hsql-jee5-ds\"/>. Follow the steps in that section, but use the "
-"following entries where needed."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:548
-#, no-c-format
-msgid "DataSource Name: <literal>seam-jpa-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:552
-#, no-c-format
-msgid "JNDI Name: <literal>seam-jpa-ds</literal>"
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:558
-#, no-c-format
-msgid "Building the example"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:560
-#, no-c-format
-msgid ""
-"Building it only requires running the correct ant command: "
-"<programlisting>ant -f build-weblogic10.xml</programlisting> This will "
-"create container specific distribution and exploded archive directories."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:568 Weblogic.xml:1027
-#, no-c-format
-msgid "Deploying the example"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:570 Weblogic.xml:1029
-#, no-c-format
-msgid ""
-"When we installed Weblogic following <xref linkend=\"weblogic-domain\"/> we "
-"chose to have the domain in development mode. This means to deploy the "
-"application all we need to do is copy it into the autodeploy directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:575
-#, no-c-format
-msgid ""
-"cp ./dist-weblogic10/jboss-seam-jpa.war \n"
-" /home/jbalunas/bea/user_projects/domains/seam_examples/autodeploy"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:577
-#, no-c-format
-msgid ""
-"Check out the application at the following <literal>http://localhost:7001/"
-"jboss-seam-jpa/</literal> ."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:583
-#, no-c-format
-msgid "What's different with Weblogic 10.x"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:586
-#, no-c-format
-msgid ""
-"Between the the Weblogic 10.x and 9.2 examples there are several differences:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:591
-#, no-c-format
-msgid ""
-"<literal>META-INF/persistence.xml</literal> — The 9.2 version is "
-"configured to use the <literal>PointBase</literal> database and a pre-"
-"installed datasource. The 10.x version uses the <literal>hsql</literal> "
-"database and a custom datasource."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:601
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/weblogic.xml</literal> — This file and its contents "
-"solve an issue with an older version of the <literal>ANTLR</literal> "
-"libraries that Weblogic 10.x uses internally. OC4J have the same issue as "
-"well."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:610
-#, no-c-format
-msgid ""
-"<![CDATA[<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
-"<weblogic-web-app\n"
-"xmlns=\"http://www.bea.com/ns/weblogic/90\"\n"
-"xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-"xsi:schemaLocation=\"http://www.bea.com/ns/weblogic/90 \n"
-" http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd"
-"\">\n"
-"\n"
-" <container-descriptor>\n"
-" <prefer-web-inf-classes>true</prefer-web-inf-classes>\n"
-" </container-descriptor>\n"
-"</weblogic-web-app>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:611
-#, no-c-format
-msgid ""
-"This file make Weblogic use classes and libraries in the web application "
-"before other libraries in the classpath. Without this change hibernate is "
-"required to use a older, slower query factory by setting the following "
-"property in the <literal>META-INF/persistence.xml</literal> file."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:620
-#, no-c-format
-msgid ""
-"<![CDATA[<property name=\"hibernate.query.factory_class\" \n"
-" value=\"org.hibernate.hql.classic.ClassicQueryTranslatorFactory\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:623
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/components.xml</literal> — In the Weblogic 10.x "
-"version JPA entity transactions is enabled by adding:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:629
-#, no-c-format
-msgid "<![CDATA[<transaction:entity-transaction entity-manager=\"#{em}\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:635
-#, no-c-format
-msgid ""
-"Between the Weblogic 10.x version and the JBoss version there are more "
-"changes. Here is the rundown:"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:640
-#, no-c-format
-msgid ""
-"<literal>META-INF/persistence.xml</literal> — Except for datasource "
-"name the WebLogic version sets:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:645
-#, no-c-format
-msgid ""
-"<![CDATA[<property \n"
-" name=\"hibernate.transaction.manager_lookup_class\" \n"
-" value=\"org.hibernate.transaction.WeblogicTransactionManagerLookup\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:648
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/jboss-web.xml</literal> — The JBoss version uses this "
-"instead of <literal>weblogic.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:653
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/lib</literal> — The Weblogic version requires several "
-"library packages because they are not included as they are with JBoss AS. "
-"These are primarily for hibernate, JSF-RI support and their dependencies."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:661
-#, no-c-format
-msgid "To use Hibernate as your JPA provider you need the following jars:"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:667
-#, no-c-format
-msgid "hibernate.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:672
-#, no-c-format
-msgid "hibernate-annotations.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:677
-#, no-c-format
-msgid "hibernate-entitymanager.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:682
-#, no-c-format
-msgid "hibernate-validator.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:687
-#, no-c-format
-msgid "jboss-common-core.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:692
-#, no-c-format
-msgid "commons-logging.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:697
-#, no-c-format
-msgid "commons-collections.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:702
-#, no-c-format
-msgid "jboss-archive-browsing.jar"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:708
-#, no-c-format
-msgid ""
-"Seam requires JSF 1.2 and these are jars needed for that. Weblogic 10.3.TP "
-"does not ship JSF libraries installed by default."
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:716
-#, no-c-format
-msgid "jsf-api.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:721
-#, no-c-format
-msgid "jsf-impl.jar"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:727
-#, no-c-format
-msgid "Various third party jars that Weblogic needs:"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:733
-#, no-c-format
-msgid "antlr.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:738
-#, no-c-format
-msgid "cglib.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:743
-#, no-c-format
-msgid "asm.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:748
-#, no-c-format
-msgid "dom4j.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:753
-#, no-c-format
-msgid "el-ri.jar"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:758
-#, no-c-format
-msgid "javassist.jar"
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:773
-#, no-c-format
-msgid ""
-"Deploying an application created using <literal>seam-gen</literal> on "
-"Weblogic 10.x"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:776
-#, no-c-format
-msgid ""
-"<literal>seam-gen</literal> is a very useful tool for developers to quickly "
-"get an application up and running, and provides a foundation to add your own "
-"functionality. Out of box <literal>seam-gen</literal> will produce "
-"applications configured to run on JBoss AS. These instructions will show the "
-"steps needed to get it to run on Weblogic."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:782
-#, no-c-format
-msgid ""
-"<literal>seam-gen</literal> was build for simplicity so, as you can imagine, "
-"deploying an application generated by <literal>seam-gen</literal> to "
-"Weblogic 10.x is not too hard. Basically it consists of updating or removing "
-"some configuration files, and adding dependent jars that Weblogic 10.x does "
-"not ship with."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:789
-#, no-c-format
-msgid ""
-"We still need to live within the constraints imposed to us by Weblogic, and "
-"because of that this example will generate a <literal>WAR</literal> based "
-"application instead of an <literal>EAR</literal>. See <xref linkend="
-"\"weblogic-ejb-blockers\"/> for details."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:795
-#, no-c-format
-msgid ""
-"This example will cover the basic <literal>seam-gen WAR</literal> "
-"deployment. This will demonstrate Seam POJO components, Hibernate JPA, "
-"Facelets, Drools security, RichFaces, and a configurable DataSource."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:801
-#, no-c-format
-msgid "Running <literal>seam-gen</literal> setup"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:803
-#, no-c-format
-msgid ""
-"The first thing we need to do it tell <literal>seam-gen</literal> about the "
-"project we want to make. This is done by running <literal>./seam setup</"
-"literal> in the base directory of the Seam distribution. Note the paths here "
-"are my own, feel free to change for you environment."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:810
-#, no-c-format
-msgid ""
-"<![CDATA[./seam setup\n"
-"Buildfile: build.xml\n"
-"\n"
-"init:\n"
-"\n"
-"setup:\n"
-" [echo] Welcome to seam-gen :-)\n"
-" [input] Enter your Java project workspace (the directory that contains "
-"your \n"
-"Seam projects) [C:/Projects] [C:/Projects]\n"
-"/home/jbalunas/workspace\n"
-" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2."
-"GA] \n"
-"[C:/Program Files/jboss-4.2.2.GA]\n"
-"/home/jbalunas/jboss/jboss-4.2.2.GA\n"
-" [input] Enter the project name [myproject] [myproject]\n"
-"weblogic-example\n"
-" [echo] Accepted project name as: weblogic_example\n"
-" [input] Select a RichFaces skin (not applicable if using ICEFaces) "
-"[blueSky]\n"
-" ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT)\n"
-"\n"
-" [input] Is this project deployed as an EAR (with EJB components) or a "
-"WAR \n"
-"(with no EJB support) [ear] ([ear], war, )\n"
-"war\n"
-" [input] Enter the Java package name for your session beans [org.jboss."
-"seam.\n"
-"tutorial.weblogic.action] [org.jboss.seam.tutorial.weblogic.action]\n"
-"org.jboss.seam.tutorial.weblogic.action\n"
-" [input] Enter the Java package name for your entity beans [org.jboss."
-"seam.\n"
-"tutorial.weblogic.model] [org.jboss.seam.tutorial.weblogic.model]\n"
-"org.jboss.seam.tutorial.weblogic.model\n"
-" [input] Enter the Java package name for your test cases [org.jboss."
-"seam.\n"
-"tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action."
-"test]\n"
-"org.jboss.seam.tutorial.weblogic.test\n"
-" [input] What kind of database are you using? [hsql] ([hsql], mysql, "
-"oracle,\n"
-" postgres, mssql, db2, sybase, enterprisedb, h2)\n"
-"\n"
-" [input] Enter the Hibernate dialect for your database [org.hibernate.\n"
-"dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect]\n"
-"\n"
-" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb."
-"jar] \n"
-"[lib/hsqldb.jar]\n"
-"\n"
-" [input] Enter JDBC driver class for your database [org.hsqldb."
-"jdbcDriver] \n"
-" [org.hsqldb.jdbcDriver]\n"
-"\n"
-" [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:"
-"hsqldb:.]\n"
-"\n"
-" [input] Enter database username [sa] [sa]\n"
-"\n"
-" [input] Enter database password [] []\n"
-"\n"
-" [input] Enter the database schema name (it is OK to leave this blank) [] "
-"[]\n"
-"\n"
-" [input] Enter the database catalog name (it is OK to leave this blank) "
-"[] []\n"
-"\n"
-" [input] Are you working with tables that already exist in the database? "
-"[n] \n"
-" (y, [n], )\n"
-"\n"
-" [input] Do you want to drop and recreate the database tables and data "
-"in \n"
-"import.sql each time you deploy? [n] (y, [n], )\n"
-"\n"
-" [input] Enter your ICEfaces home directory (leave blank to omit "
-"ICEfaces) [] []\n"
-"\n"
-"[propertyfile] Creating new property file: \n"
-"/rhdev/projects/jboss-seam/cvs-head/jboss-seam/seam-gen/build.properties\n"
-" [echo] Installing JDBC driver jar to JBoss server\n"
-" [copy] Copying 1 file to /home/jbalunas/jboss/jboss-4.2.2.GA/server/"
-"default/lib\n"
-" [echo] Type 'seam create-project' to create the new project\n"
-"\n"
-"BUILD SUCCESSFUL]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:812
-#, no-c-format
-msgid ""
-"Type <literal>./seam new-project</literal> to create your project and "
-"<literal>cd /home/jbalunas/workspace/weblogic_example</literal> to see the "
-"newly created project."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:819
-#, no-c-format
-msgid "What to change for Weblogic 10.X"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:820
-#, no-c-format
-msgid ""
-"First we change and delete some configuration files, then we update the "
-"libraries that are deployed with the application."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:825
-#, no-c-format
-msgid "Configuration file changes"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:833
-#, no-c-format
-msgid "Change the default target to <literal>archive</literal>."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:837
-#, no-c-format
-msgid ""
-"<![CDATA[<project name=\"weblogic_example\" default=\"archive\" basedir=\"."
-"\">]]>"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:844
-#, no-c-format
-msgid "resources/META-INF/persistence-dev.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:849
-#, no-c-format
-msgid ""
-"Alter the <literal>jta-data-source</literal> to be <literal>seam-gen-ds</"
-"literal> (and use this as the <literal>jndi-name</literal> when creating the "
-"data source in Weblogic's admin console)"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:858
-#, no-c-format
-msgid ""
-"Change the transaction type to <literal>RESOURCE_LOCAL</literal> so that we "
-"can use JPA transactions."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:861
-#, no-c-format
-msgid ""
-"<![CDATA[<persistence-unit name=\"weblogic_example\" transaction-type="
-"\"RESOURCE_LOCAL\">]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:864
-#, no-c-format
-msgid "Add/modify the properties below for Weblogic support:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:866
-#, no-c-format
-msgid ""
-"<![CDATA[<property name=\"hibernate.cache.provider_class\" \n"
-" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n"
-"<property name=\"hibernate.transaction.manager_lookup_class\" \n"
-" value=\"org.hibernate.transaction.WeblogicTransactionManagerLookup\"/>\n"
-"]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:869
-#, no-c-format
-msgid ""
-"Remove the JBoss AS specific method of exposing the EntityManagerFactory:"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:872
-#, no-c-format
-msgid ""
-"<![CDATA[<property \n"
-" name=\"jboss.entity.manager.factory.jndi.name\" \n"
-" value=\"java:/weblogic_exampleEntityManagerFactory\">]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:875
-#, no-c-format
-msgid ""
-"You'll need to alter <literal>persistence-prod.xml</literal> as well if you "
-"want to deploy to Weblogic using the prod profile."
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:885
-#, no-c-format
-msgid "resource/WEB-INF/weblogic.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:888
-#, no-c-format
-msgid ""
-"You will need to create this file and populate it following <xref linkend="
-"\"weblogic.xml\"/>."
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:895
-#, no-c-format
-msgid "resource/WEB-INF/components.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:898
-#, no-c-format
-msgid ""
-"We want to use JPA transactions so we need to add the following to let Seam "
-"know."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:900
-#, no-c-format
-msgid ""
-"<![CDATA[<transaction:entity-transaction entity-manager=\"#{entityManager}\"/"
-">]]>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:901
-#, no-c-format
-msgid ""
-"You will also need to add the transaction namespace and schema location to "
-"the top of the document."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:904
-#, no-c-format
-msgid ""
-"<![CDATA[xmlns:transaction=\"http://jboss.com/products/seam/transaction\"]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:905
-#, no-c-format
-msgid ""
-"<![CDATA[http://jboss.com/products/seam/transaction http://jboss.com/"
-"products/seam/transaction-2.1.xsd]]>"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:910
-#, no-c-format
-msgid "resources/WEB-INF/jboss-app.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:913
-#, no-c-format
-msgid ""
-"You can delete this file as we aren't deploying to JBoss AS ( <literal>jboss-"
-"app.xml</literal> is used to enable classloading isolation in JBoss AS)"
-msgstr ""
-
-#. Tag: literal
-#: Weblogic.xml:920
-#, no-c-format
-msgid "resources/*-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:923
-#, no-c-format
-msgid ""
-"You can delete these files as we aren't deploying to JBoss AS. These files "
-"define datasources in JBoss AS, in Weblogic we will use the administration "
-"console."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:932
-#, no-c-format
-msgid "Library changes"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:933
-#, no-c-format
-msgid ""
-"The <literal>seam-gen</literal> application has very similar library "
-"dependencies as the <literal>jpa</literal> example above. See <xref linkend="
-"\"weblogic-jpa-diff\"/>. Below is the changes that are needed to get them in "
-"this application."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:942
-#, no-c-format
-msgid ""
-"Missing jars — There are two libraries that <literal>seam-gen</"
-"literal> does not provide by default. These need to be copied into your "
-"projects <literal>lib</literal> directory manually."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:949
-#, no-c-format
-msgid ""
-"jboss-archive-browsing.jar — can be found in the <literal>@SEAM_DIST/"
-"examples/jpa/lib</literal> directory."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:955
-#, no-c-format
-msgid ""
-"el-ri.jar — is also found in the <literal>@SEAM_DIST/examples/jpa/lib</"
-"literal> directory."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:962
-#, no-c-format
-msgid ""
-"build.xml — Now we need to adjust the <literal>build.xml</literal>. "
-"Find the target <literal>war</literal> and add the following to the end of "
-"the target."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:968
-#, no-c-format
-msgid ""
-"<![CDATA[<copy todir=\"${war.dir}/WEB-INF/lib\">\n"
-" <fileset dir=\"${lib.dir}\">\n"
-" <!--JSF implementation -->\n"
-" <include name=\"jsf-api.jar\" />\n"
-" <include name=\"jsf-impl.jar\" />\n"
-" \n"
-" <!-- Misc 3rd party -->\n"
-" <include name=\"commons-logging.jar\" />\n"
-" <include name=\"dom4j.jar\" />\n"
-" <include name=\"javassist.jar\" />\n"
-" <include name=\"cglib.jar\" />\n"
-" <include name=\"antlr.jar\" />\n"
-" \n"
-" <!-- Hibernate --> \n"
-" <include name=\"hibernate.jar\" />\n"
-" <include name=\"hibernate-commons-annotations.jar\" />\n"
-" <include name=\"hibernate-annotations.jar\" />\n"
-" <include name=\"hibernate-entitymanager.jar\" />\n"
-" <include name=\"hibernate-validator.jar\" />\n"
-" <include name=\"jboss-archive-browsing.jar\" />\n"
-" \n"
-" <!-- Needed for Drools -->\n"
-" <include name=\"core.jar\"/>\n"
-" </fileset>\n"
-" </copy>]]>"
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:975
-#, no-c-format
-msgid "<literal>seam-gen</literal> development profile issue"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:977
-#, no-c-format
-msgid ""
-"There is currently an issue with the behavior of the <literal>seam-gen WAR</"
-"literal> application when built using the development profile (the default) "
-"and deployed to Weblogic. The symptom is that the login page of the "
-"application will always show a <literal>login failed</literal> message."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:983
-#, no-c-format
-msgid ""
-"When the application is built using the development profile the "
-"<literal>action</literal> class files are placed in the <literal>WEB-INF/"
-"dev</literal> directory. Normally these class files are hot deployable and "
-"managed by Seam. This does not happen on Weblogic (see <ulink url=\"http://"
-"jira.jboss.com/jira/browse/JBSEAM-2455\"> jira JBSEAM-2455</ulink> for "
-"details and status)."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:991
-#, no-c-format
-msgid ""
-"To workaround this you need to modify the <literal>build-dev.properties</"
-"literal> file. Simply remove the property <literal>action.dir=WEB-INF/dev</"
-"literal>."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:1000
-#, no-c-format
-msgid "Building and Deploying your application"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:1001
-#, no-c-format
-msgid ""
-"Finally all that's left is deploying the application. This involves setting "
-"up a data source, building the app, and deploying it."
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:1006
-#, no-c-format
-msgid "Setting up the data source"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:1007
-#, no-c-format
-msgid ""
-"Configuring the datasource is very similar to the jee5 <xref linkend="
-"\"weblogic-hsql-jee5-ds\"/>. Except for what is listed here follow that "
-"instruction from the link."
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:1012
-#, no-c-format
-msgid "DataSource Name: <literal>seam-gen-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:1016
-#, no-c-format
-msgid "JNDI Name: <literal>seam-gen-ds</literal>"
-msgstr ""
-
-#. Tag: title
-#: Weblogic.xml:1022
-#, no-c-format
-msgid "Building the application"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:1023
-#, no-c-format
-msgid ""
-"This is as easy as typing <literal>ant</literal> in the projects base "
-"directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Weblogic.xml:1036
-#, no-c-format
-msgid ""
-"cp ./dist/weblogic_example.war /home/jbalunas/bea/user_projects/domains/"
-"seam_examples/autodeploy"
-msgstr ""
-
-#. Tag: para
-#: Weblogic.xml:1037
-#, no-c-format
-msgid ""
-"Check out the application at the following <literal>http://localhost:7001/"
-"weblogic_example/</literal> ."
-msgstr ""
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Websphere.po
===================================================================
--- projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Websphere.po 2008-12-09 06:26:10 UTC (rev 82128)
+++ projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/Websphere.po 2008-12-09 06:56:13 UTC (rev 82129)
@@ -1,2085 +0,0 @@
-# Language ja-JP translations for PACKAGE package.
-# Automatically generated, 2008.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2008-04-04 01:24+0000\n"
-"PO-Revision-Date: 2008-04-04 01:24+0000\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#: Websphere.xml:2
-#, no-c-format
-msgid "Seam on IBM's Websphere"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:4
-#, no-c-format
-msgid ""
-"Websphere 6.1.x is IBM's application server offering. The latest release is "
-"6.1.0.13 which does not have <literal>EJB3</literal> or <literal>JEE5</"
-"literal> support. There is a recently released (Nov 07) <literal>EJB3</"
-"literal> feature pack which provides some support for <literal>EJB3</"
-"literal> and <literal>JPA</literal>. Currently there is no true "
-"<literal>JEE5</literal> offering from IBM. This causes some issues with Seam "
-"integration with applications that use EJB3."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:12
-#, no-c-format
-msgid ""
-"First we will go over some basic information about the Websphere environment "
-"that we used for these examples. After a good deal of research and work we "
-"were able to get EJB3 applications to function correctly. We will go over "
-"the details of those steps with the jee5 example. We will also deploy the "
-"the JPA example application."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:19
-#, no-c-format
-msgid "Websphere environment and deployment information"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:21
-#, no-c-format
-msgid ""
-"Websphere is a commercial product and so we will not discuss the details of "
-"its installation other than to say follow the directions provided by your "
-"particular installation type and license. This section will detail the exact "
-"server versions used, installation tips, and some custom properties that are "
-"needed for all of the examples."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:29
-#, no-c-format
-msgid "Installation versions and tips"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:30
-#, no-c-format
-msgid ""
-"All of the examples and information in this chapter are based on the the "
-"latest version of Websphere at the time of this writing."
-msgstr ""
-
-#. Tag: ulink
-#: Websphere.xml:35
-#, no-c-format
-msgid "Websphere Application Server 6.1.0.13"
-msgstr ""
-
-#. Tag: ulink
-#: Websphere.xml:40
-#, no-c-format
-msgid ""
-"Feature Pack for EJB 3.0 for Websphere Application Server V6.1 (3.0.6.1.0.13)"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:46
-#, no-c-format
-msgid ""
-"The EJB3 feature pack that we installed came with the 6.1.0.13 patch version "
-"of Websphere. Installing the feature pack does not ensure that your server "
-"will have the proper environment for EJB3 applications. Be sure that as part "
-"of the installation of the feature pack you follow the instructions to "
-"create a new server profile with the EJB3 feature pack enabled, or augment "
-"one of your existing ones. This can also be done after the installation by "
-"running the profile managment tool."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:55
-#, no-c-format
-msgid "A note about restarting the server"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:56
-#, no-c-format
-msgid ""
-"There are times that restarting the server will be required after deploying "
-"or changes the examples in this chapter. Its does not seem like every change "
-"requires a restart. If you get errors or exceptions after modifing a "
-"property or deploying an application try to restart the server."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:64
-#, no-c-format
-msgid "Required custom properties"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:65
-#, no-c-format
-msgid ""
-"There are a couple of Websphere custom properties that are required for Seam "
-"integration. These properties are not needed specifically for Seam, but work "
-"around some issues with Websphere. These are set following the instructions "
-"here : <ulink url=\"http://www-1.ibm.com/support/docview.wss?rss=180&"
-"uid=swg21284395\"> Setting web container custom properties</ulink>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:74
-#, no-c-format
-msgid ""
-"<literal>prependSlashToResource = \"true\"</literal> — This solves a "
-"fairly common issue with Websphere where applications are not using a "
-"leading \"/\" when attempting to access resources. If this is not set then a "
-"<literal>java.net.MalformedURLException</literal> will be thrown. With this "
-"property set you will still see warnings, but the resources will be "
-"retrieved as expected."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:82 Websphere.xml:100
-#, no-c-format
-msgid "Detailed can be found at:"
-msgstr ""
-
-#. Tag: ulink
-#: Websphere.xml:84
-#, no-c-format
-msgid "SRVE0238E: Resource paths must have a leading slash"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:89
-#, no-c-format
-msgid ""
-"<literal>com.ibm.ws.webcontainer.invokefilterscompatibility = \"true\"</"
-"literal> — This solves an issue with Websphere where it throws a "
-"<literal>FileNotFoundException</literal> when a web application attempts to "
-"access a file resource that does not actually exist on disk. This is a "
-"common practice in modern web applications where filters or servlets are "
-"used to process resource requests like these. This issue manifests itself as "
-"failures to retrieve JavaScript, CSS, images, etc... when requesting a web "
-"page."
-msgstr ""
-
-#. Tag: ulink
-#: Websphere.xml:102
-#, no-c-format
-msgid ""
-"PK33090; 6.1: A filter that serves a file does not pop-up an alert message"
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:111
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:113
-#, no-c-format
-msgid ""
-"The <literal>jee5/booking</literal> example is based on the Hotel Booking "
-"example (which runs on JBoss AS). Out of the box it is designed to run on "
-"Glassfish, but with the steps below it can be deployed to Websphere. It is "
-"located in the <literal>$SEAM_DIST/examples/jee5/booking</literal> directory."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:120
-#, no-c-format
-msgid ""
-"As stated before the <literal>EJB3</literal> feature pack does not provide a "
-"full <literal>jee5</literal> implementation. This means that there are some "
-"tricks to getting an application deployed and functioning."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:126 Websphere.xml:903
-#, no-c-format
-msgid "<title>Configuration file changes</title>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:128
-#, no-c-format
-msgid ""
-"Below are the configuration file changes that are need to the base example."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:134 Websphere.xml:977
-#, no-c-format
-msgid "resources/WEB-INF/components.xml"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:137
-#, no-c-format
-msgid ""
-"We need to change the way that we look up EJBs for Websphere. We need to "
-"remove the <literal>/local</literal> from the end of the <literal>jndi-"
-"pattern</literal> attribute. It should look like this:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:144
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<core:init jndi-pattern=\"java:comp/env/jboss-seam-jee5/#{ejbName}\" debug="
-"\"true\"/>\n"
-" ]]>"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:148 Websphere.xml:1009
-#, no-c-format
-msgid "resources/WEB-INF/web.xml"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:151
-#, no-c-format
-msgid ""
-"This is the first place that we notice an unexpected change because this is "
-"not full <literal>jee5</literal> implementation."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:154
-#, no-c-format
-msgid ""
-"Websphere does not support <literal>Servlet 2.5</literal>, it requires "
-"<literal>Servlet 2.4</literal>. For this change we need to adjust the top of "
-"the <literal>web.xml</literal> file to look like the following:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:161
-#, no-c-format
-msgid ""
-"<![CDATA[<xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
-"<web-app version=\"2.4\" \n"
-" xmlns=\"http://java.sun.com/xml/ns/j2ee\"\n"
-" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-" xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee \n"
-" http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
-"\">\n"
-" ]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:162
-#, no-c-format
-msgid ""
-"Next, we have to make some changes to the EJB references in the <literal>web."
-"xml</literal>. These changes are what will allow Websphere to bind the EJB2 "
-"references in the web module to the the actual EJB3 beans in the EAR module. "
-"Replace all of the <literal>ejb-local-refs</literal> when the values below."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:171
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <!-- JEE5 EJB3 names -->\n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>jboss-seam-jee5/AuthenticatorAction</ejb-ref-"
-"name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.example.booking.Authenticator</local> \n"
-" </ejb-local-ref> \n"
-" \n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>jboss-seam-jee5/BookingListAction</ejb-ref-name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.example.booking.BookingList</local> \n"
-" </ejb-local-ref> \n"
-" \n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>jboss-seam-jee5/RegisterAction</ejb-ref-name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.example.booking.Register</local> \n"
-" </ejb-local-ref> \n"
-" \n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>jboss-seam-jee5/ChangePasswordAction</ejb-ref-"
-"name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home> \n"
-" <local>org.jboss.seam.example.booking.ChangePassword</local> \n"
-" </ejb-local-ref> \n"
-" \n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>jboss-seam-jee5/HotelBookingAction</ejb-ref-name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.example.booking.HotelBooking</local> \n"
-" </ejb-local-ref> \n"
-" \n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>jboss-seam-jee5/HotelSearchingAction</ejb-ref-"
-"name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home> \n"
-" <local>org.jboss.seam.example.booking.HotelSAll of the examples and "
-"informaearching</local> \n"
-" </ejb-local-ref> \n"
-" \n"
-" <ejb-local-ref>\n"
-" <ejb-ref-name>jboss-seam-jee5/EjbSynchronizations</ejb-ref-name> \n"
-" <ejb-ref-type>Session</ejb-ref-type>\n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n"
-" </ejb-local-ref>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:172
-#, no-c-format
-msgid ""
-"The important change is that there is an empty <literal>local-home</literal> "
-"element for each EJB. This tells Websphere to make the correct bindings "
-"between the web module and the EJB3 beans. The <literal>ejb-link</literal> "
-"element is simply not used."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:178
-#, no-c-format
-msgid ""
-"Note also that <literal>EjbSynchronizations</literal> is a built-in Seam EJB "
-"and not part of the Hotel Booking example. This means that if your "
-"application's <literal>components.xml</literal> specifies "
-"<literal>transaction:ejb-transaction</literal> , then you must include:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:183
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <ejb-local-ref>\n"
-" <ejb-ref-name>myapp/EjbSynchronizations</ejb-ref-name>\n"
-" <ejb-ref-type>Session</ejb-ref-type>\n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n"
-" </ejb-local-ref>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:184
-#, no-c-format
-msgid ""
-"in your web.xml. If you don't include it, you'll get the following error:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:185
-#, no-c-format
-msgid "Name comp/env/myapp/EjbSynchronizations not found in context java:"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:190
-#, no-c-format
-msgid "resources/META-INF/persistence.xml"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:193
-#, no-c-format
-msgid ""
-"For this example we will be using the default datasource that comes with "
-"Websphere. To do this change the <literal>jta-data-source</literal> element:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:196
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<jta-data-source>DefaultDatasource</jta-data-source>\n"
-" ]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:197
-#, no-c-format
-msgid ""
-"Then we need to adjust some of the hibernate properties. First comment out "
-"the Glassfish properties. Next you need to add/change the properties:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:202
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<!--<property name=\"hibernate.transaction.flush_before_completion\" value="
-"\"true\"/>-->\n"
-"<property name=\"hibernate.cache.provider_class\" \n"
-" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n"
-"<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect\"/>\n"
-"<property name=\"hibernate.transaction.manager_lookup_class\" \n"
-" value=\"org.hibernate.transaction."
-"WebSphereExtendedJTATransactionLookup\"/>\n"
-" ]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:206
-#, no-c-format
-msgid ""
-"<literal>hibernate.transaction.manager_lookup_class</literal> — "
-"Standard Hibernate transaction manager property for Websphere 6.X"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:212
-#, no-c-format
-msgid ""
-"<literal>hibernate.transaction.flush_before_completion</literal> — "
-"This is commented out because we want the container to manage the "
-"transactions. Also if this is set to <literal>true</literal> an exception "
-"will be thrown by Websphere when the EJBContext is looked up."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:221
-#, no-c-format
-msgid ""
-"<![CDATA[com.ibm.wsspi.injectionengine.InjectionException: \n"
-" EJBContext may only be looked up by or injected into an "
-"EJB]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:224
-#, no-c-format
-msgid ""
-"<literal>hibernate.dialect</literal> — From WAS 6.1.0.9 on the "
-"embedded DB was switched to the same Derby DB in Glassfish."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:234 Websphere.xml:943
-#, no-c-format
-msgid "resources/GlassfishDerbyDialect.class"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:237
-#, no-c-format
-msgid ""
-"You will need to get the <literal>GlassfishDerbyDialect.class</literal> and "
-"copy it into the <literal>/resources</literal> directory. The class exists "
-"in the JPA example and can be copied using the command below assuming you "
-"are in <literal>jee5/booking</literal> directory:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:245
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"cp ../../jpa/resources-websphere61/WEB-INF/classes/GlassfishDerbyDialect."
-"class\n"
-" ./resources]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:246
-#, no-c-format
-msgid ""
-"This class will be put into the <literal>jboss-seam-jee5.jar</literal> file "
-"using changes to the build.xml discussed later."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:252
-#, no-c-format
-msgid "resources/import.sql"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:255
-#, no-c-format
-msgid ""
-"This file must also be copied from the JPA example because either the Derby "
-"DB or the dialect does not support changes to the <literal>ID</literal> "
-"column. The files are identical except for the column difference. Use the "
-"following command to make the copy"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:262
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"cp ../../jpa/resources-websphere61/import.sql ./resources]]>"
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:271
-#, no-c-format
-msgid "Building the <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:274
-#, no-c-format
-msgid ""
-"In order to get the changes we have made into our application we need to "
-"make some changes to the <literal>build.xml</literal>. There are also some "
-"additional jars that are required by our application in order to work with "
-"Websphere. This section will cover what changes are needed to the "
-"<literal>build.xml</literal>."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:281
-#, no-c-format
-msgid "New libraries dependencies"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:285
-#, no-c-format
-msgid ""
-"JSF libraries — Websphere 6.1 comes with its own version of JSF 1.1 "
-"(Seam requires JSF 1.2). So we must add these jars to our application:"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:290 Websphere.xml:817
-#, no-c-format
-msgid "jsf-api.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:294 Websphere.xml:822
-#, no-c-format
-msgid "jsf-impl.jar"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:300
-#, no-c-format
-msgid ""
-"Since Websphere is not a fully compliant <literal>JEE5</literal> "
-"implementation we need to add these EL libraries:"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:305 Websphere.xml:830
-#, no-c-format
-msgid "el-api.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:309 Websphere.xml:826
-#, no-c-format
-msgid "el-ri.jar"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:315
-#, no-c-format
-msgid ""
-"<literal>jboss-seam.jar</literal> — for some reason when deploying the "
-"application through the Websphere administration console it can not find the "
-"<literal>jboss-seam.jar</literal> at the base of the EAR archive. This means "
-"that we need to add it to the <literal>/lib</literal> of the EAR."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:323
-#, no-c-format
-msgid ""
-"Finally we remove the <literal>log4j.jar</literal> so that all of the log "
-"output from our application will be added to the Websphere log. Additional "
-"steps are required to fully configure log4j and those are outside of the "
-"scope of this document."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:334
-#, no-c-format
-msgid "Updating the <literal>build.xml</literal> file"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:336
-#, no-c-format
-msgid ""
-"Add the following entry to the bottom of the <literal>build.xml</literal> "
-"file. This overrides the default fileset that is used to populate the "
-"<literal>jboss-seam-jee5.jar</literal>. The primary change is the addition "
-"of the <literal>GlassfishDerbyDialect.class</literal>:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:345
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <fileset id=\"jar.resources\" dir=\"${resources.dir}\">\n"
-" <include name=\"import.sql\" />\n"
-" <include name=\"seam.properties\" />\n"
-" <include name=\"GlassfishDerbyDialect.class\" />\n"
-" <include name=\"META-INF/persistence.xml\" />\n"
-" <include name=\"META-INF/ejb-jar.xml\" />\n"
-" </fileset>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:348
-#, no-c-format
-msgid ""
-"Next we need to add the library dependencies discussed above. For this add "
-"the following to bottom of the <literal>ear.lib.extras</literal> fileset "
-"entry:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:354
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <!--<include name=\"lib/log4j.jar\" />-->\n"
-" <include name=\"lib/el-api.jar\" />\n"
-" <include name=\"examples/jpa/lib/el-ri.jar\" />\n"
-" <include name=\"lib/jsf-api.jar\" />\n"
-" <include name=\"lib/jsf-impl.jar\" />\n"
-" <include name=\"lib/jboss-seam.jar\" />\n"
-"</fileset>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:357
-#, no-c-format
-msgid ""
-"Now all that is left is to execute the <literal>ant archive</literal> task "
-"and the built application will be in the <literal>jee5/booking/dist</"
-"literal> directory."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:366
-#, no-c-format
-msgid "Deploying the application to Websphere"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:368
-#, no-c-format
-msgid ""
-"So now we have everything we need in place. All that is left is to deploy it "
-"- just a few steps more."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:370
-#, no-c-format
-msgid ""
-"For this we will use Websphere's administration console. As before there are "
-"some tricks and tips that must be followed."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:373
-#, no-c-format
-msgid ""
-"The steps below are for the Websphere version stated above, yours may be "
-"slightly different."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:377
-#, no-c-format
-msgid "Log in to the administration console"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:380
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"https://localhost:9043/ibm/console]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:384
-#, no-c-format
-msgid ""
-"Access the <literal>Enterprise Application</literal> menu option under the "
-"<literal>Applications</literal> top menu."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:389
-#, no-c-format
-msgid ""
-"At the top of the <literal>Enterprise Application</literal> table select "
-"<literal>Install</literal>. Below are installation wizard pages and what "
-"needs to done on each:"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:395 Websphere.xml:655
-#, no-c-format
-msgid "Preparing for the application installation"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:399
-#, no-c-format
-msgid ""
-"Browse to the <literal>examples/jee5/booking/dist/jboss-seam-jee5.ear</"
-"literal> file using the file upload widget."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:405 Websphere.xml:423 Websphere.xml:456 Websphere.xml:670
-#, no-c-format
-msgid "Select the <literal>Next</literal> button."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:412
-#, no-c-format
-msgid "Select installation options"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:416
-#, no-c-format
-msgid ""
-"Select the <literal>Deploy enterprise beans</literal> check box. This is "
-"needed unless you used a Websphere tool to package the application."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:430
-#, no-c-format
-msgid "Map modules to servers"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:434
-#, no-c-format
-msgid ""
-"No changes needed here as we only have one server. Select the <literal>Next</"
-"literal> button."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:442
-#, no-c-format
-msgid ""
-"<literal>Map EJB references to beans</literal> This page will list all of "
-"the beans that we entered in the web.xml."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:447
-#, no-c-format
-msgid ""
-"Make sure that <literal>Allow EJB reference targets to resolve "
-"automatically</literal> check box is selected. This will tell Websphere to "
-"bind our EJB3 beans to the EJB references in the web module."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:463
-#, no-c-format
-msgid "Map virtual hosts for Web modules"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:467
-#, no-c-format
-msgid "No changes needed here. Select the <literal>Next</literal> button."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:474
-#, no-c-format
-msgid "Summary"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:477
-#, no-c-format
-msgid "No changes needed here. Select the <literal>Finish</literal> button."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:484
-#, no-c-format
-msgid "Installation"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:487
-#, no-c-format
-msgid "Now you will see it installing and deploying your application."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:492
-#, no-c-format
-msgid ""
-"When if finishes select the <literal>Save</literal> link and you will be "
-"returned to the <literal>Enterprise Applications</literal> table."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:504
-#, no-c-format
-msgid ""
-"Now that we have our application installed we need to make some adjustments "
-"to it before we can start it:"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:508
-#, no-c-format
-msgid ""
-"Starting from the <literal>Enterprise Applications</literal> table select "
-"the <literal>Seam Booking</literal> link."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:514
-#, no-c-format
-msgid "Select the <literal>Manage Modules</literal> link."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:518
-#, no-c-format
-msgid "Select the <literal>jboss-seam-jee5.war</literal> link."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:523
-#, no-c-format
-msgid ""
-"Change the <literal>Class loader order</literal> combo box to "
-"<literal>Classes loaded with application class loader first</literal>."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:529 Websphere.xml:554
-#, no-c-format
-msgid ""
-"Select <literal>Apply</literal> and then <literal>Save</literal> options."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:533
-#, no-c-format
-msgid "Return the <literal>Seam Booking</literal> page."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:537
-#, no-c-format
-msgid ""
-"On this page select the <literal>Class loading and update detection</"
-"literal> link."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:542
-#, no-c-format
-msgid ""
-"Select the radio button for <literal>Classes loaded with application class "
-"loader first</literal>."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:547
-#, no-c-format
-msgid ""
-"Even though we are not enabling class reload you must also enter a valid "
-"number in the <literal>Polling interval for updated files</literal> text "
-"area (zero works fine)."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:558
-#, no-c-format
-msgid ""
-"You should verify that the change you just made has been remembered. We have "
-"had problems with the last class loader change not taking effect - even "
-"after a restart. If the change did not take you will need to do it manually, "
-"following these directions:"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:566
-#, no-c-format
-msgid "Open the following file in a text editor of your choice:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:570
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"$WebSphereInstall/$yourServerName/profiles/$yourProfileName/config/cells/\n"
-" $yourCellName/applications/Seam Booking.ear/deployments/\n"
-" Seam Booking/deployment.xml]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:574
-#, no-c-format
-msgid ""
-"Modify the following line so that <literal>PARENT_FIRST</literal> is now "
-"<literal>PARENT_LAST</literal>:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:580
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<classloader xmi:id=\"Classloader_#######\" mode=\"PARENT_FIRST\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:584
-#, no-c-format
-msgid ""
-"Save the file and now when go to the <literal>Class loading and update "
-"detection</literal> page you should see <literal>Classes loaded with "
-"application class loader first</literal> selected."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:596
-#, no-c-format
-msgid ""
-"To start the application return to the <literal>Enterprise Applications</"
-"literal> table and select our application in the list. Then choose the "
-"<literal>Start</literal> button at the top of the table."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:603
-#, no-c-format
-msgid ""
-"You can now access the application at <literal>http://localhost:9080/seam-"
-"jee5/</literal> ."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:609
-#, no-c-format
-msgid "A note about Websphere Stateful bean timeouts"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:610
-#, no-c-format
-msgid ""
-"The default timeout period for a Websphere 6.1 Stateful EJB is 10 minutes. "
-"This means that you may see some EJB timeout exceptions after some idle "
-"time. It is possible to adjust the timeout of the Stateful EJBs on an "
-"individual basis, but that is beyond the scope of this document. See the "
-"Websphere documentation for details."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:624
-#, no-c-format
-msgid "The <literal>jpa</literal> booking example"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:625
-#, no-c-format
-msgid ""
-"Thankfully getting the <literal>jpa</literal> example to work is much easier "
-"than the <literal>jee5</literal> example. This is the Hotel Booking example "
-"implemented in Seam POJOs and using Hibernate JPA with JPA transactions. It "
-"does not require EJB3 support to run."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:631
-#, no-c-format
-msgid ""
-"The example already has a breakout of configurations and build scripts for "
-"many of the common containers including Websphere."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:634
-#, no-c-format
-msgid ""
-"First thing we are going to do is build and deploy that example. Then we'll "
-"go over some key changes that we needed."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:638
-#, no-c-format
-msgid "Building the <literal>jpa</literal> example"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:639
-#, no-c-format
-msgid ""
-"Building it only requires running the correct ant command: "
-"<programlisting>ant websphere61</programlisting> This will create container "
-"specific distribution and exploded archive directories with the "
-"<literal>websphere61</literal> label."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:645
-#, no-c-format
-msgid "Deploying the <literal>jpa</literal> example"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:646
-#, no-c-format
-msgid ""
-"This is similar to the <literal>jee5</literal> example at <xref linkend="
-"\"jee5-websphere-deploy\"/>, but without so many steps."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:651
-#, no-c-format
-msgid ""
-"From the <literal>Enterprise Applications</literal> table select the "
-"<literal>Install</literal> button."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:659
-#, no-c-format
-msgid ""
-"Browse to the <literal>examples/jpa/dist-websphere61/jboss-seam-jpa.war</"
-"literal> file using the file upload widget."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:665
-#, no-c-format
-msgid ""
-"In the <literal>Context root</literal> text box enter <literal>jboss-seam-"
-"jpa</literal>."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:676
-#, no-c-format
-msgid ""
-"Select the <literal>Next</literal> button for the next three pages, no "
-"changes are needed."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:681
-#, no-c-format
-msgid "<literal>Summary</literal> page"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:684
-#, no-c-format
-msgid ""
-"Review the settings if you wish and select the <literal>Finish</literal> "
-"button to install the application. When installation finished select the "
-"<literal> Save</literal> link and you will be returned to the "
-"<literal>Enterprise Applications</literal> table."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:697
-#, no-c-format
-msgid ""
-"As with the <literal>jee5</literal> example there are some class loader "
-"changes needed before we start the application. Follow the instructions at "
-"<xref linkend=\"websphere-app-adj-after-install\"/> but exchange "
-"<literal>jboss-seam-jpa</literal> for <literal>Seam Booking</literal>."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:704
-#, no-c-format
-msgid ""
-"Finally start the application by selecting it in the <literal>Enterprise "
-"Applications</literal> table and clicking the <literal>Start</literal> "
-"button."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:710
-#, no-c-format
-msgid ""
-"You can now access the application at the <literal>http://localhost:9080/"
-"jboss-seam-jpa/index.html</literal>."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:718
-#, no-c-format
-msgid "Whats different for Websphere 6.1"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:719
-#, no-c-format
-msgid ""
-"The differences between the JPA examples that deploys to JBoss 4.2 and "
-"Websphere 6.1 are mostly expected; library and configuration file changes."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:724
-#, no-c-format
-msgid "<para>Configuration file changes</para>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:727
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/web.xml</literal> — the only significant change is "
-"that Websphere 6.1 only support <literal>Servlet 2.4</literal> so the top of "
-"this file was changed."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:734
-#, no-c-format
-msgid ""
-"<literal>META-INF/persistence.xml</literal> — the main changes here "
-"are for the datasource JNDI path, switching to the Websphere 6.1 transaction "
-"manager look up class, and changing the hibernate dialect to be "
-"<literal>GlassfishDerbyDialect</literal> ."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:744
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/classes/GlassfishDerbyDialect.class </literal> — this "
-"class is needed for the hibernate dialect change to "
-"<literal>GlassfishDerbyDialect</literal>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:752
-#, no-c-format
-msgid ""
-"<literal>import.sql</literal> — either for the dialect or Derby DB the "
-"<literal>ID</literal> column can not be populated by this file and was "
-"removed."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:761
-#, no-c-format
-msgid "Changes for dependent libraries"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:762
-#, no-c-format
-msgid ""
-"<literal>WEB-INF/lib</literal> — The Websphere version requires "
-"several library packages because they are not included as they are with "
-"JBoss AS. These are primarily for hibernate, JSF-RI support and their "
-"dependencies. Below are listed only the additional jars needed above and "
-"beyond the JBoss <literal>JPA</literal> example."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:770
-#, no-c-format
-msgid "To use Hibernate as your JPA provider you need the following jars:"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:775
-#, no-c-format
-msgid "hibernate.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:780
-#, no-c-format
-msgid "hibernate-annotations.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:785
-#, no-c-format
-msgid "hibernate-commons-annotations.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:790
-#, no-c-format
-msgid "hibernate-entitymanager.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:795
-#, no-c-format
-msgid "hibernate-validator.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:800
-#, no-c-format
-msgid "commons-collections.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:805
-#, no-c-format
-msgid "jboss-archive-browsing.jar"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:811
-#, no-c-format
-msgid ""
-"Seam requires JSF 1.2 and these are the jars needed for that. Websphere 6.1 "
-"ships with its own implementation of JSF 1.1."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:836
-#, no-c-format
-msgid "Various third party jars that Websphere needs:"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:839
-#, no-c-format
-msgid "antlr.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:843
-#, no-c-format
-msgid "cglib.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:847
-#, no-c-format
-msgid "asm.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:851
-#, no-c-format
-msgid "dom4j.jar"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:856
-#, no-c-format
-msgid "javassist.jar"
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:871
-#, no-c-format
-msgid ""
-"Deploying an application created using <literal>seam-gen</literal> on "
-"Websphere 6.1.0.13"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:874
-#, no-c-format
-msgid ""
-"<literal>seam-gen</literal> is a very useful tool for developers to quickly "
-"get an application up and running, and provides a foundation to add your own "
-"functionality. Out of box <literal>seam-gen</literal> will produce "
-"applications configured to run on JBoss AS. These instructions will show the "
-"steps needed to get it to run on Websphere. As stated above in <xref linkend="
-"\"jee5-websphere-section\"/> there are some tricky changes needed to get an "
-"EJB3 application running. This section will take you through the exact steps."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:884
-#, no-c-format
-msgid "Running <literal>seam-gen</literal> Setup"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:885
-#, no-c-format
-msgid ""
-"The first step is setting up <literal>seam-gen</literal> to construct the "
-"base project. There are several choices made below, specifically the "
-"datasource and hibernate values that we will adjust once the project is "
-"created."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:891
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"./seam setup\n"
-"Buildfile: build.xml\n"
-"\n"
-"init:\n"
-"\n"
-"setup:\n"
-" [echo] Welcome to seam-gen :-)\n"
-" [input] Enter your Java project workspace (the directory that contains "
-"your \n"
-"Seam projects) [C:/Projects] [C:/Projects]\n"
-"/home/jbalunas/workspace\n"
-" [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.2."
-"GA] \n"
-"[C:/Program Files/jboss-4.2.2.GA]\n"
-"/home/jbalunas/jboss/jboss-4.2.2.GA\n"
-" [input] Enter the project name [myproject] [myproject]\n"
-"websphere_example\n"
-" [echo] Accepted project name as: websphere_example\n"
-" [input] Do you want to use ICEFaces instead of RichFaces [n] (y, [n], )\n"
-"\n"
-" [input] skipping input as property icefaces.home.new has already been "
-"set.\n"
-" [input] Select a RichFaces skin [blueSky] ([blueSky], classic, ruby, "
-"wine, \n"
-"deepMarine, emeraldTown, sakura, DEFAULT)\n"
-"\n"
-" [input] Is this project deployed as an EAR (with EJB components) or a "
-"WAR \n"
-"(with no EJB support) [ear] ([ear], war, )\n"
-"\n"
-" [input] Enter the Java package name for your session beans [org.jboss."
-"seam.\n"
-"tutorial.websphere.action] [org.jboss.seam.tutorial.websphere.action]\n"
-"org.jboss.seam.tutorial.websphere.action \n"
-" [input] Enter the Java package name for your entity beans [org.jboss."
-"seam.\n"
-"tutorial.websphere.model] [org.jboss.seam.tutorial.websphere.model]\n"
-"org.jboss.seam.tutorial.websphere.model \n"
-" [input] Enter the Java package name for your test cases [org.jboss."
-"seam.\n"
-"tutorial.websphere.action.test] [org.jboss.seam.tutorial.websphere.action."
-"test]\n"
-"org.jboss.seam.tutorial.websphere.test\n"
-" [input] What kind of database are you using? [hsql] ([hsql], mysql, "
-"oracle,\n"
-" postgres, mssql, db2, sybase, enterprisedb, h2)\n"
-"\n"
-" [input] Enter the Hibernate dialect for your database [org.hibernate.\n"
-"dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect]\n"
-"\n"
-" [input] Enter the filesystem path to the JDBC driver jar [lib/hsqldb."
-"jar] \n"
-"[lib/hsqldb.jar]\n"
-"\n"
-" [input] Enter JDBC driver class for your database [org.hsqldb."
-"jdbcDriver] \n"
-"[org.hsqldb.jdbcDriver]\n"
-"\n"
-" [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] \n"
-"[jdbc:hsqldb:.]\n"
-"\n"
-" [input] Enter database username [sa] [sa]\n"
-"\n"
-" [input] Enter database password [] []\n"
-"\n"
-" [input] Enter the database schema name (it is OK to leave this blank) [] "
-"[]\n"
-"\n"
-" [input] Enter the database catalog name (it is OK to leave this blank) "
-"[] []\n"
-"\n"
-" [input] Are you working with tables that already exist in the database? "
-"[n]\n"
-" (y, [n], )\n"
-"\n"
-" [input] Do you want to drop and recreate the database tables and data "
-"in \n"
-"import.sql each time you deploy? [n] (y, [n], )\n"
-"\n"
-"[propertyfile] Creating new property file: \n"
-"/rhdev/projects/jboss-seam/svn-seam_2_0/jboss-seam-2_0/seam-gen/build."
-"properties\n"
-" [echo] Installing JDBC driver jar to JBoss server\n"
-" [copy] Copying 1 file to /home/jbalunas/jboss/jboss-4.2.2.GA/server/"
-"default/lib\n"
-" [echo] Type 'seam create-project' to create the new project\n"
-"\n"
-"BUILD SUCCESSFUL\n"
-"Total time: 3 minutes 5 seconds]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:893
-#, no-c-format
-msgid ""
-"Type <literal>./seam new-project</literal> to create your project and "
-"<literal>cd /home/jbalunas/workspace/websphere_example</literal> to the "
-"newly created structure."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:900
-#, no-c-format
-msgid "Changes needed for deployment to Websphere"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:901
-#, no-c-format
-msgid "We now need to make some changes to the generated project."
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:907
-#, no-c-format
-msgid "resources/META-INF/persistence-dev.xml"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:912
-#, no-c-format
-msgid ""
-"Alter the <literal>jta-data-source</literal> to be "
-"<literal>DefaultDatasource</literal>. We are going to be using the "
-"integrated Websphere DB."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:919
-#, no-c-format
-msgid ""
-"Add or change the properties below. These are described in detail at <xref "
-"linkend=\"jee5-websphere-section\"/>:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:924
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<property name=\"hibernate.dialect\" value=\"GlassfishDerbyDialect\"/>\n"
-"<property name=\"hibernate.hbm2ddl.auto\" value=\"update\"/>\n"
-"<property name=\"hibernate.show_sql\" value=\"true\"/>\n"
-"<property name=\"hibernate.format_sql\" value=\"true\"/>\n"
-"<property name=\"hibernate.cache.provider_class\" \n"
-" value=\"org.hibernate.cache.HashtableCacheProvider\"/>\n"
-"<property name=\"hibernate.transaction.manager_lookup_class\" \n"
-" value=\"org.hibernate.transaction."
-"WebSphereExtendedJTATransactionLookup\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:927
-#, no-c-format
-msgid ""
-"Remove the JBoss AS specific method of exposing the EntityManagerFactory:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:930
-#, no-c-format
-msgid ""
-"<![CDATA[<property \n"
-" name=\"jboss.entity.manager.factory.jndi.name\" \n"
-" value=\"java:/websphere_exampleEntityManagerFactory\">]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:933
-#, no-c-format
-msgid ""
-"You'll need to alter <literal>persistence-prod.xml</literal> as well if you "
-"want to deploy to Websphere using the prod profile."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:946
-#, no-c-format
-msgid ""
-"As with other examples we need to include this class for DB support. It can "
-"be copied from the <literal>jpa</literal> example into the "
-"<literal>websphere_example/resources</literal> directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:952
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"cp $SEAM/examples/jpa/resources-websphere61/WEB-INF/classes/"
-"GlassfishDerbyDialect.class\n"
-" ./resources]]>"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:958
-#, no-c-format
-msgid "resources/META-INF/jboss-app.xml"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:961
-#, no-c-format
-msgid ""
-"You can delete this file as we aren't deploying to JBoss AS ( <literal>jboss-"
-"app.xml</literal> is used to enable classloading isolation in JBoss AS)"
-msgstr ""
-
-#. Tag: literal
-#: Websphere.xml:967
-#, no-c-format
-msgid "resources/*-ds.xml"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:970
-#, no-c-format
-msgid ""
-"You can delete these file as we aren't deploying to JBoss AS (these files "
-"define datasources in JBoss AS, we are using Websphere's default datasource)"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:982
-#, no-c-format
-msgid ""
-"Enable container managed transaction integration - add the <literal> <"
-"transaction:ejb-transaction /> </literal> component, and it's namespace "
-"declaration <literal> xmlns:transaction=\"http://jboss.com/products/seam/"
-"transaction\" </literal>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:991
-#, no-c-format
-msgid ""
-"Alter the <literal>jndi-pattern</literal> to <literal> java:comp/env/"
-"websphere_example/#{ejbName} </literal>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:997
-#, no-c-format
-msgid ""
-"We do not need <literal>managed-persistence-context</literal> for this "
-"example and so can delete its entry."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1003
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<persistence:managed-persistence-context name=\"entityManager\"\n"
-" auto-create=\"true\"\n"
-" persistence-unit-jndi-name=\"java:/"
-"websphere_exampleEntityManagerFactory\"/> ]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1012
-#, no-c-format
-msgid ""
-"Websphere does not support <literal>Servlet 2.5</literal>, it required "
-"<literal>Servlet 2.4</literal>. For this change we need to adjust the top of "
-"the <literal>web.xml</literal> file to look like the following:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1018
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"
-"<web-app version=\"2.4\" \n"
-" xmlns=\"http://java.sun.com/xml/ns/j2ee\"\n"
-" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n"
-" xsi:schemaLocation=\"http://java.sun.com/xml/ns/j2ee \n"
-" http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
-"\">\n"
-" ]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1020
-#, no-c-format
-msgid ""
-"As with the <literal>jee5/booking</literal> example we need to add EJB "
-"references to the web.xml. These references require the empty <literal>local-"
-"home</literal> to flag them for Websphere to perform the proper binding."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1027
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <ejb-local-ref> \n"
-" <ejb-ref-name>websphere_example/AuthenticatorAction</ejb-ref-"
-"name> \n"
-" <ejb-ref-type>Session</ejb-ref-type> \n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.tutorial.websphere.action.Authenticator</local> \n"
-" </ejb-local-ref>\n"
-" \n"
-" <ejb-local-ref>\n"
-" <ejb-ref-name>websphere_example/EjbSynchronizations</ejb-ref-name> \n"
-" <ejb-ref-type>Session</ejb-ref-type>\n"
-" <local-home></local-home>\n"
-" <local>org.jboss.seam.transaction.LocalEjbSynchronizations</local>\n"
-" </ejb-local-ref>]]>"
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:1033
-#, no-c-format
-msgid "Creating the <literal>AuthenticatorAction</literal> EJB"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1035
-#, no-c-format
-msgid ""
-"We want to take the existing <literal>Authenticator</literal> Seam POJO "
-"component and create an EJB3 out of it."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1041
-#, no-c-format
-msgid "Rename the class to <literal>AuthenticatorAction</literal>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1045
-#, no-c-format
-msgid ""
-"Add the <literal>@Stateless</literal> annotation to the new "
-"<literal>AuthenticatorAction</literal> class."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1051
-#, no-c-format
-msgid ""
-"Create an interface called <literal>Authenticator</literal> which "
-"<literal>AuthenticatorAction</literal> implements (EJB3 requires session "
-"beans to have a local interface). Annotate the interface with "
-"<literal>@Local</literal> , and add a single method with same signature as "
-"the <literal>authenticate</literal> in <literal>AuthenticatorAction</"
-"literal> ."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1064
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"@Name(\"authenticator\") @Stateless public class\n"
-" AuthenticatorAction implements Authenticator {]]>"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1067
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"@Local public interface Authenticator { \n"
-" public boolean authenticate(); \n"
-"}]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1070
-#, no-c-format
-msgid ""
-"We've already added its reference to the <literal>web.xml</literal> file so "
-"are good to go."
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:1076
-#, no-c-format
-msgid ""
-"Extra jar dependencies and other changes to the <literal>build.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1078
-#, no-c-format
-msgid ""
-"This application has similar requirements as the <literal>jee5/booking</"
-"literal> example."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1083
-#, no-c-format
-msgid ""
-"Change the default target to <literal>archive</literal> (we aren't going to "
-"cover automatic deployment to Websphere)."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1089
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<project name=\"websphere_example\" default=\"archive\" basedir=\".\">]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1093
-#, no-c-format
-msgid ""
-"Websphere looks for the drools <literal>/security.drl</literal> file in the "
-"root of the <literal>war</literal> file instead of the root of the "
-"<literal>websphere_example.jar</literal> so we need to have the "
-"<literal>build.xml</literal> move it to the correct location at build time. "
-"The following must be added at the top of the <literal> <target name=\"war"
-"\" depends=\"compile\" description=\"Build the distribution .war file\"> "
-"</literal> target."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1104
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<copy todir=\"${war.dir}\">\n"
-" <fileset dir=\"${basedir}/resources\" >\n"
-" <include name=\"*.drl\" />\n"
-" </fileset>\n"
-"</copy>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1107
-#, no-c-format
-msgid ""
-"We need to ge the <literal>GlassfishDerbyDialect.class</literal> into our "
-"application jar. To do that find the <literal>jar</literal> task and modify "
-"the top of it so that it looks like this:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1115
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<target name=\"jar\" depends=\"compile,copyclasses\" \n"
-" description=\"Build the distribution .jar file\">\n"
-" <copy todir=\"${jar.dir}\">\n"
-" <fileset dir=\"${basedir}/resources\">\n"
-" <include name=\"seam.properties\" />\n"
-" <include name=\"*.drl\" />\n"
-" <include name=\"GlassfishDerbyDialect.class\" />\n"
-" </fileset>\n"
-" </copy>\n"
-"...]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1118
-#, no-c-format
-msgid ""
-"Next we need to get the <literal>jboss-seam.jar</literal> into the base of "
-"the <literal>EAR</literal> file. For deployment Websphere requires this jar "
-"to be in both the <literal>/lib</literal> directory and at the base of the "
-"<literal>EAR</literal>. You must add the following to the <literal>archive</"
-"literal> task:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1127
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<fileset dir=\"${lib.dir}\">\n"
-" <include name=\"jboss-seam.jar\" />\n"
-"</fileset>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1128
-#, no-c-format
-msgid "So that the whole <literal>archive</literal> task looks like:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1132
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<target name=\"archive\" depends=\"jar,war,ear\" \n"
-" description=\"Package the archives\">\n"
-" <jar jarfile=\"${dist.dir}/${project.name}.jar\" basedir=\"${jar.dir}\"/"
-">\n"
-" <jar jarfile=\"${dist.dir}/${project.name}.war\" basedir=\"${war.dir}\"/"
-">\n"
-" <jar jarfile=\"${dist.dir}/${project.name}.ear\">\n"
-" <fileset dir=\"${ear.dir}\"/>\n"
-" <fileset dir=\"${dist.dir}\">\n"
-" <include name=\"${project.name}.jar\"/>\n"
-" <include name=\"${project.name}.war\"/>\n"
-" </fileset>\n"
-" <fileset dir=\"${lib.dir}\">\n"
-" <include name=\"jboss-seam.jar\" />\n"
-" </fileset>\n"
-" </jar>\n"
-"</target>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1135
-#, no-c-format
-msgid ""
-"Now we need to get extra jars into the <literal>build.xml</literal>. Look "
-"for the <literal><fileset dir=\"${basedir}\"></literal> section of the "
-"task below. Add the new includes at the bottom of the fileset."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1143
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<target name=\"ear\" description=\"Build the EAR\">\n"
-" <copy todir=\"${ear.dir}\">\n"
-" <fileset dir=\"${basedir}/resources\">\n"
-" <include name=\"*jpdl.xml\" />\n"
-" <include name=\"*hibernate.cfg.xml\" />\n"
-" <include name=\"jbpm.cfg.xml\" />\n"
-" </fileset>\n"
-" <fileset dir=\"${lib.dir}\">\n"
-" <include name=\"jboss-seam.jar\" />\n"
-" </fileset>\n"
-" <fileset dir=\"${basedir}\">\n"
-" <include name=\"lib/jbpm*.jar\" />\n"
-" <include name=\"lib/jboss-el.jar\" />\n"
-" <include name=\"lib/drools-*.jar\"/>\n"
-" <include name=\"lib/core.jar\"/>\n"
-" <include name=\"lib/janino*.jar\"/>\n"
-" <include name=\"lib/antlr-*.jar\"/>\n"
-" <include name=\"lib/mvel*.jar\"/>\n"
-" <include name=\"lib/richfaces-api*.jar\" />\n"
-" </fileset>\n"
-" </copy>\n"
-" <copy todir=\"${ear.dir}/META-INF\">\n"
-" <fileset dir=\"${basedir}/resources/META-INF\">\n"
-" <include name=\"application.xml\" />\n"
-" <include name=\"jboss-app.xml\" />\n"
-" </fileset>\n"
-" </copy>\n"
-"</target>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1146
-#, no-c-format
-msgid "Hibernate dependencies"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1147
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <!-- Hibernate and deps -->\n"
-" <include name=\"lib/hibernate.jar\"/>\n"
-" <include name=\"lib/hibernate-commons-annotations.jar\"/>\n"
-" <include name=\"lib/hibernate-annotations.jar\"/>\n"
-" <include name=\"lib/hibernate-entitymanager.jar\"/>\n"
-" <include name=\"lib/hibernate-validator.jar\"/>\n"
-" <include name=\"lib/jboss-common-core.jar\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1150
-#, no-c-format
-msgid ""
-"JSF dependencies. You will need to copy the <literal>el-ri.jar</literal> "
-"from the <literal>$SEAM/examples/jpa/lib</literal> directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1153
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <!-- jsf libs -->\n"
-" <include name=\"lib/jsf-api.jar\" />\n"
-" <include name=\"lib/jsf-impl.jar\" />\n"
-" <include name=\"lib/el-api.jar\" />\n"
-" <include name=\"lib/el-ri.jar\"/>]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1156
-#, no-c-format
-msgid ""
-"Third party dependencies. You will need to copy the <literal>jboss-archive-"
-"browsing.jar</literal> from the <literal>$SEAM/examples/jpa/lib</literal> "
-"directory into the the projects <literal>/lib</literal> directory. You will "
-"also need to acquire the <literal>concurrent.jar</literal> and place it in "
-"the same directory. You can get this from any jboss distribution or just "
-"search for it."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1163
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <!-- 3rd party and supporting jars -->\n"
-" <!--<include name=\"lib/log4j.jar\" />-->\n"
-" <include name=\"lib/javassist.jar\"/>\n"
-" <include name=\"lib/dom4j.jar\" />\n"
-" <include name=\"lib/jboss-archive-browsing.jar\" />\n"
-" <include name=\"lib/concurrent.jar\" />\n"
-" <include name=\"lib/cglib.jar\"/>\n"
-" <include name=\"lib/asm.jar\"/>\n"
-" <include name=\"lib/antlr.jar\" />\n"
-" <include name=\"lib/commons-logging.jar\" />\n"
-" <include name=\"lib/commons-collections.jar\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1166
-#, no-c-format
-msgid ""
-"<literal>jboss-seam.jar</literal> - this is needed in both the <literal>ear</"
-"literal> base and <literal>/lib</literal> directory."
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1170
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-" <!-- seam jar -->\n"
-" <include name=\"lib/jboss-seam.jar\" />]]>"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1174
-#, no-c-format
-msgid "You should end up with something like:"
-msgstr ""
-
-#. Tag: programlisting
-#: Websphere.xml:1175
-#, no-c-format
-msgid ""
-"<![CDATA[\n"
-"<fileset dir=\"${basedir}\">\n"
-" <include name=\"lib/jbpm*.jar\" />\n"
-" <include name=\"lib/jboss-el.jar\" />\n"
-" <include name=\"lib/drools-*.jar\"/>\n"
-" <include name=\"lib/core.jar\"/>\n"
-" <include name=\"lib/janino*.jar\"/>\n"
-" <include name=\"lib/antlr-*.jar\"/>\n"
-" <include name=\"lib/mvel*.jar\"/>\n"
-" <include name=\"lib/richfaces-api*.jar\" />\n"
-" \n"
-" <!-- Hibernate and deps -->\n"
-" <include name=\"lib/hibernate.jar\"/>\n"
-" <include name=\"lib/hibernate-commons-annotations.jar\"/>\n"
-" <include name=\"lib/hibernate-annotations.jar\"/>\n"
-" <include name=\"lib/hibernate-entitymanager.jar\"/>\n"
-" <include name=\"lib/hibernate-validator.jar\"/>\n"
-" <include name=\"lib/jboss-common-core.jar\" />\n"
-" \n"
-" <!-- jsf libs -->\n"
-" <include name=\"lib/jsf-api.jar\" />\n"
-" <include name=\"lib/jsf-impl.jar\" />\n"
-" <include name=\"lib/el-api.jar\" />\n"
-" <include name=\"lib/el-ri.jar\"/>\n"
-" \n"
-" <!-- 3rd party and supporting jars -->\n"
-" <!--<include name=\"lib/log4j.jar\" />-->\n"
-" <include name=\"lib/javassist.jar\"/>\n"
-" <include name=\"lib/dom4j.jar\" />\n"
-" <include name=\"lib/jboss-archive-browsing.jar\" />\n"
-" <include name=\"lib/concurrent.jar\" />\n"
-" <include name=\"lib/cglib.jar\"/>\n"
-" <include name=\"lib/asm.jar\"/>\n"
-" <include name=\"lib/antlr.jar\" />\n"
-" <include name=\"lib/commons-logging.jar\" />\n"
-" <include name=\"lib/commons-collections.jar\" />\n"
-" \n"
-" <!-- seam jar -->\n"
-" <include name=\"lib/jboss-seam.jar\" />\n"
-" \n"
-"</fileset>]]>"
-msgstr ""
-
-#. Tag: title
-#: Websphere.xml:1181
-#, no-c-format
-msgid "Building and deploying the seam-gen'd application to Websphere"
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1187
-#, no-c-format
-msgid ""
-"Build your application by calling <literal>ant</literal> in the base "
-"directory of your project (ex. <literal>/home/jbalunas/workspace/"
-"websphere_example</literal> ). The target of the build will be <literal>dist/"
-"websphere_example.ear</literal> ."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1196
-#, no-c-format
-msgid ""
-"To deploy the application follow the instructions here : <xref linkend="
-"\"jee5-websphere-deploy\"/> but use references to this project "
-"<literal>websphere_example</literal> instead of <literal>jboss-seam-jee5</"
-"literal>."
-msgstr ""
-
-#. Tag: para
-#: Websphere.xml:1202
-#, no-c-format
-msgid ""
-"Checkout the app at: <literal>http://localhost:9080/websphere_example/index."
-"html</literal>"
-msgstr ""
Deleted: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/ja-JP/master.po
===================================================================
More information about the jboss-cvs-commits
mailing list