[jboss-cvs] JBossAS SVN: r101103 - projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 17 20:10:31 EST 2010
Author: mospina
Date: 2010-02-17 20:10:30 -0500 (Wed, 17 Feb 2010)
New Revision: 101103
Removed:
projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Glassfish.po
projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Revision_History.po
projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Rss.po
projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Weblogic.po
projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Websphere.po
projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Wicket.po
Log:
PO automatic cleaning for ja-JP
Deleted: projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Glassfish.po
===================================================================
--- projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Glassfish.po 2010-02-18 01:08:36 UTC (rev 101102)
+++ projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Glassfish.po 2010-02-18 01:10:30 UTC (rev 101103)
@@ -1,454 +0,0 @@
-#
-# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-02-18T01:02:59\n"
-"PO-Revision-Date: 2010-02-18T01:02:59\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Seam on GlassFish application server"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<application>GlassFish</application> is an open source application server which fully implements Java EE 5. The latest stable release is v2 UR2."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This chapter will discuss the GlassFish environment. You will learn how to deploy the JEE5 and JPA example applications, and to deploy a <application>seam-gen</application>-created application on GlassFish."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "GlassFish environment and deployment information"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Installation"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "All examples and information in this chapter are based on GlassFish v2 UR2, available from the <ulink url=\"https://glassfish.dev.java.net/downloads/v2ur2-b04.html\">Download page</ulink>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Download GlassFish and install it like so:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Set up GlassFish with the following command:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This creates a domain named <literal>domain1</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Next, start the embedded JavaDB server:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "JavaDB is an embedded database that is included with GlassFish, just as HSQLDB is included in JBoss AS."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Next, start the GlassFish server:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The web administration console is available at <literal>http://localhost:4848/</literal>. You can access the web admin console with the default username and password (<literal>admin</literal> and <literal>adminadmin</literal> respectively). This chapter shows you how to deploy the example applications in the web admin console. Alternatively, you can deploy applications by copying <filename>EAR</filename> or <filename>WAR</filename> files to the <literal>glassfish/domains/domain1/autodeploy</literal> directory."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can stop the server and database with the following command:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> example is based on the Hotel Booking example. This example runs on JBoss AS, but it is designed to work on GlassFish out of the box. The example is located in <literal>$SEAM_DIST/examples/jee5/booking</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building the <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To build the example, simply execute the default <literal>ant</literal> target from the <literal>examples/jee5/booking</literal> directory:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This creates the <literal>dist</literal> and <literal>exploded-archives</literal> directories."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying the application to GlassFish"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Deploy the application to GlassFish by using the GlassFish web administration console."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in to the admin console at <literal>http://localhost:4848</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Access the <literal>Enterprise Applications</literal> from the <guilabel>Applications</guilabel> item on the left hand side menu."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click <guilabel>Deploy</guilabel>, at the top of the <literal>Enterprise Application</literal> table. Make the following changes to the listed wizard screens:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Preparing to install the application</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Use the file upload widget to browse to <filename>examples/jee5/booking/dist/jboss-seam-jee5.ear</filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guibutton>OK</guibutton> button to upload."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can now access the application at <literal>http://localhost:8081/seam-jee5/</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>jpa</literal> booking example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This version of the Hotel Booking example is implemented in Seam POJOs rather than EJB3 beans, and uses Hibernate JPA for JPA transactions. The application already contains configuration and build script options for the GlassFish application server."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building the <literal>jpa</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To build the example, use the <literal>glassfish</literal> target with <application>Ant</application>:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This creates container-specific <literal>dist-glassfish</literal> and <literal>exploded-archives-glassfish</literal> directories."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying the <literal>jpa</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This is similar to the JEE5 example found at <xref linkend=\"jee5-glassfish-deploy\" />, except that it is a <filename>WAR</filename> and not an <filename>EAR</filename> deployment."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in to the administration console:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Access <literal>Web Applications</literal> from the <guilabel>Applications</guilabel> item on the left hand side menu."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal> Preparing to install the application </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Use the file upload widget to browse to <filename>examples/jpa/dist-glassfish/jboss-seam-jpa.war</filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guibutton>OK</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can now access the application at <literal>http://localhost:8081/jboss-seam-jpa/</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Using Derby instead of Hypersonic SQL DB"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "We have used the JavaDB (Derby) database so that the example application works with GlassFish out of the box. However, we strongly recommend using a different database, such as HSQL —to do so, you must use <filename>examples/jpa/resources-glassfish/WEB-INF/classes/ GlassfishDerbyDialect.class</filename> as your Hibernate dialect to circumvent a Derby bug in GlassFish."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Changes for GlassFish v2 UR2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Configuration file changes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>META-INF/persistence.xml</literal> —the data source JNDI changes to the GlassFish transaction manager lookup class, and the Hibernate dialect changes to <literal>GlassfishDerbyDialect</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/classes/GlassfishDerbyDialect.class</literal> —This class is required to apply the change in Hibernate dialect correctly."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>import.sql</literal> —removes the <literal>ID</literal> column, which cannot be populated with the current dialect or the Derby database."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying <application>seam-gen</application>-created application on GlassFish v2 UR2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<application>seam-gen</application> is useful for swift application development. Out of the box, it produces applications configured to run on JBoss AS. This section shows you how to configure <application>seam-gen</application> so that your applications will run on GlassFish."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Running <application>seam-gen</application> Setup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "First, run <literal>./seam setup</literal> in the base directory of your Seam distribution to tell <application>seam-gen</application> about your project. The paths in the following example can be altered to fit your own environment:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Type <command>./seam new-project</command> to create your project and then <command>cd /projects/seamgen_example</command> to view the newly created structure."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Changes required for GlassFish deployment"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Before deployment, we must update and remove some configuration files, and update the libraries deployed with the application."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/META-INF/persistence-dev.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>jta-data-source</literal> to <literal>jdbc/__default</literal>. We will use the integrated GlassFish Derby database."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Replace all properties with the following: (The differences are described in <xref linkend=\"glassfish_jpa_diff\" />.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To deploy GlassFish using the prod profile, you must also make these changes in <filename>persistence-prod.xml</filename>."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/GlassfishDerbyDialect.class</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy this class from the <literal>jpa</literal> example into the <literal>seamgen_example/resources</literal> directory for database support, like so:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/META-INF/jboss-app.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This file is used to enable class loading in JBoss AS —you can delete this file."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/*-ds.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "These files define data sources in JBoss AS —since we use GlassFish's default data source, you can delete these files."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/WEB-INF/components.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Enable container-managed transaction integration by adding the <literal><transaction:ejb-transaction /></literal> component and its namespace declaration (<literal>xmlns:transaction=\"http://jboss.com/products/seam/transaction\"</literal>) to this file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>jndi-pattern</literal> to <literal>java:comp/env/seamgen_example/#{ejbName}</literal>"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/WEB-INF/web.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add EJB references to <filename>web.xml</filename>. Remember that these references also require an empty <literal>local-home</literal> element to remain compatible with a JBoss AS 4.x deployment."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you deploy to JBoss AS 4.x, you will also need to define local JNDI names for each of these references in <filename>jboss-web.xml</filename>, as shown in the following example. (This step is not required for GlassFish-only deployment, or for JBoss AS 5.)"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Creating the <literal>AuthenticatorAction</literal> EJB"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To create an EJB3 version of the <literal>Authenticator</literal> Seam POJO:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Rename the class \"<literal>AuthenticatorAction</literal>\"."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add the <literal>@Stateless</literal> annotation to the new <literal>AuthenticatorAction</literal> class."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Create an interface called <literal>Authenticator</literal>, implemented by <literal>AuthenticatorAction</literal>. (EJB3 requires that session beans have a local interface.) Annotate the interface with <literal>@Local</literal>, and add a single method with the same signature as the <literal>authenticate</literal> in <literal>AuthenticatorAction</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Since a reference to this class has already been added to <filename>web.xml</filename>, the new EJB3 is ready for deployment."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Extra <filename>JAR</filename> dependencies and other changes to <filename>build.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This application has similar requirements to the <literal>jee5/booking</literal> example."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the default target to \"<literal>archive</literal>\". (We will not cover automatic deployment to GlassFish.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>GlassfishDerbyDialect.class</filename> must be included in our application <filename>JAR</filename> —add the <filename>GlassfishDerbyDialect.class</filename> line like so:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add Hibernate dependencies"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add third party dependencies."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You should end up with something like:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building and deploying the seam-gen'd application to GlassFish"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Build your application by calling <literal>ant</literal> in the base directory of your project (for example <literal>/projects/seamgen-example</literal>). The target of the build will be <literal>dist/seamgen-example.ear</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To deploy the application follow the instructions here <xref linkend=\"jee5-glassfish-deploy\" /> but use references to this project <literal>seamgen-example</literal> instead of <literal>jboss-seam-jee5</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Checkout the app at <literal>http://localhost:8081/seamgen_example/</literal>"
-msgstr ""
-
Deleted: projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Revision_History.po
===================================================================
--- projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Revision_History.po 2010-02-18 01:08:36 UTC (rev 101102)
+++ projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Revision_History.po 2010-02-18 01:10:30 UTC (rev 101103)
@@ -1,24 +0,0 @@
-#
-# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-02-18T01:03:00\n"
-"PO-Revision-Date: 2010-02-18T01:03:00\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: firstname
-#, no-c-format
-msgid "Laura"
-msgstr ""
-
-#. Tag: member
-#, no-c-format
-msgid "Initial draft."
-msgstr ""
-
Deleted: projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Rss.po
===================================================================
--- projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Rss.po 2010-02-18 01:08:36 UTC (rev 101102)
+++ projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Rss.po 2010-02-18 01:10:30 UTC (rev 101103)
@@ -1,194 +0,0 @@
-#
-# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-02-18T01:03:00\n"
-"PO-Revision-Date: 2010-02-18T01:03:00\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "RSS support"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can integrate RSS feeds with Seam by using the <ulink url=\"http://yarfraw.sourceforge.net/\">YARFRAW</ulink> library. RSS support is \"tech preview\" only in the current release."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Installation"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To enable RSS support, include the <filename>jboss-seam-rss.jar</filename> in your application's <literal>WEB-INF/lib</literal> directory. The RSS library also has some dependent libraries that should be placed in the same directory. See <xref linkend=\"dependencies.rss\" /> for a list of libraries to include."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Seam RSS support requires that Facelets be used as the view technology."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Generating feeds"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "See the <literal>examples/rss</literal> project for an example of RSS support. This demonstrates the exposed functionality and proper deployment packaging."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "An RSS feed is an XHTML page consisting of a feed and a list of nested entry items."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Feeds"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Feeds are top-level entities that describe the properties of the information source. They contain zero or more nested entries."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal><r:feed></literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Attributes</emphasis>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>uid</literal> — An optional unique feed ID. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>title</literal> — The title of the feed. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>subtitle</literal> — The subtitle of the feed. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>updated</literal> — A date value representing the feed's laste update."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>link</literal> — The link to the source of the information. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>feedFormat</literal> — The feed format. The value is a string and defaults to <literal>ATOM1</literal>. Valid values are <literal>RSS10</literal>, <literal>RSS20</literal>, <literal>ATOM03</literal> and <literal>ATOM10</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Child elements</emphasis>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Zero or more feed entries</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Facets</emphasis>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>none</literal>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Entries"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Entries are the \"headlines\" in the feed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>uid</literal> — An optional unique entry ID. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>title</literal> — The title of the entry. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>link</literal> — A link to the item. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>author</literal> — The author of the story. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>summary</literal> — The body of the story. The value is a string."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>textFormat</literal> — The format of the body and title of the story. The value is a string and valid values are <literal>text</literal> and <literal>html</literal>. Defaults to <literal>html</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>published</literal> — A date value representing the story's first publish date."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>updated</literal> — A date value representing the story's last update."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Links and further documentation"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The RSS functionality found in Seam is based on the YARFRAW library, which can be found on which can be found on <ulink url=\"http://yarfraw.sourceforge.net/\">http://yarfraw.sourceforge.net/</ulink>. Most features and limitations are inherited from here."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For details on the ATOM 1.0 format, visit <ulink url=\"http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html\">the specifications</ulink>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For details on the RSS 2.0 format, visit <ulink url=\"http://cyber.law.harvard.edu/rss/rss.html\">the specifications</ulink>."
-msgstr ""
-
Deleted: projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Weblogic.po
===================================================================
--- projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Weblogic.po 2010-02-18 01:08:36 UTC (rev 101102)
+++ projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Weblogic.po 2010-02-18 01:10:30 UTC (rev 101103)
@@ -1,979 +0,0 @@
-#
-# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-02-18T01:03:02\n"
-"PO-Revision-Date: 2010-02-18T01:03:02\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Seam on BEA's Weblogic"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Weblogic 10.3 is the latest stable Java EE 5 (JEE5) server offering from BEA. This chapter shows you how to deploy and develop Seam applications on Weblogic servers, including Weblogic-specific configuration changes and workarounds for known Weblogic server issues. The first step is to download and install Weblogic. This chapter shows you some of the obstacles involved in running Seam's JEE5 example. We will also show you how to deploy the JPA example to the server, and how to create and run a <literal>seam-gen</literal> application as an example for your own applications."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Installation and operation of Weblogic"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "First, you must install the server. Weblogic 10.3 resolves some of the issues discussed below without requiring BEA patches. The previous release, 10.0.MP1, remains available, but requires some BEA patches to function correctly."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Weblogic 10.0.MP1</literal> —<ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main .html\"> Download page </ulink>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are two known issues with Enterprise JavaBean (EJB) compilation in 10.0.MP1. EJBs that use variable arguments fail to deploy because Weblogic mistakes these arguments for transient methods. Other EJB methods are also omitted from Weblogic's internally-generated stubs. Patches are available to fix both of these issues —see <xref linkend=\"weblogic-ejb-issues\" /> for full details about these issues and their workarounds."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Weblogic 10.3</literal> —<ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main .html\"> Download page </ulink>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Weblogic 10.3 is the latest stable release of the Weblogic server. In this version, the variable argument issue mentioned in 10.0.MP1 has been fixed, but other EJB methods are still omitted when Weblogic generates internal stubs. A special Seam <filename>jar</filename>, replacing <literal>jboss-seam.jar</literal>, provides a workaround for this issue by removing the <literal>TimerServiceDispatcher</literal> in which the exceptions occur. We use this <filename>jar</filename> with Weblogic 10.3 for the <literal>jee5/booking</literal> example later this chapter, but for full details on both the issue and its workaround, see <xref linkend=\"weblogic-ejb-issues\" />."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Installing 10.3"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This is a quick guide to installing Weblogic 10.3 for Red Hat Enterprise Linux 5 using the graphical installer. If you require further information, or experience any difficulty, you can check the BEA documentation at the <ulink url=\"http://edocs.bea.com/wls/docs103/\">Weblogic 10.3 Doc Center</ulink>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Go to the <ulink url=\"http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html\">10.3 download page</ulink> and download the correct version for your environment. (To do this, you will need an Oracle account.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You may need to make the <literal>server103_XX.bin</literal> file executable, like so:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Execute the install:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When the graphical install loads, set the BEA home location. This is where all BEA applications will be installed. We will refer to this location as <literal>$BEA_HOME</literal> in this document. You may set your <literal>$BEA_HOME</literal> to the following location:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Select your installation type. We recommend a <literal>Complete</literal> installation."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Accept the default components selected for installation on the next page."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Creating your Weblogic domain"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "A Weblogic domain is similar to a JBoss server configuration —it is a self-contained server instance. There are some example domains available to the Weblogic server we just installed, but we want to create a specific domain for the Seam examples. If you want to use the existing domains, modify the following instructions accordingly."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the Weblogic configuration wizard:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Choose to create a new domain configured to support <literal>Weblogic Server</literal>. (This is the default domain option.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Set a username and password for this domain."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Next, choose <literal>Development Mode</literal> and the default JDK when given the option."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The next screen asks if you want to customize any setting. Select <literal>No</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Finally, set the name of the domain to <literal>seam_examples</literal> and accept the default domain location."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "How to Start/Stop/Access your domain"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Once the server is installed and the domain has been created, you must learn to start and stop it, and to access its configuration console."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Start the domain</emphasis> by going to the <literal>$BEA_HOME/user_projects/domains/seam_examples/bin</literal> directory and running the <literal>./startWeblogic.sh</literal> script."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Access the configuration console</emphasis> by launching <literal>http://127.0.0.1:7001/console</literal> in your web browser. You will be prompted for the username and password that you set while creating your Weblogic domain. (This is the starting point for most Weblogic configuration.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<emphasis>Stop the domain</emphasis> by:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "using the configuration console (recommended):"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Select <literal>seam_examples</literal> on the left hand side of the console."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click on the <literal>Control</literal> tab in the middle of the page."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Check the <literal>AdminServer</literal> checkbox in the table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click on <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
-#, no-c-format
-msgid "pressing <keycombo action=\"press\"><keycap>Ctrl</keycap><keycap>C</keycap></keycombo> in the terminal where you started the domain."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "No negative effects have been observed, but we do not recommend doing this while making configuration changes in the console."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Weblogic classloading"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You may see <literal>NoClassDefFound</literal> exceptions during redeployment when you use the <literal>/autodeploy</literal> directory as described in this chapter. If this occurs, restart the Weblogic server. If you still see the exception, remove the automatically deployed EAR or WAR files before restarting the server and redeploying."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Setting up Weblogic's JSF Support"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This section tells you how to deploy and configure Weblogic's JSF 1.2 libraries. For complete details see <ulink url=\"http://edocs.bea.com/wls/docs103/webapp/configurejsfandjtsl.html\"> Weblogic 10.3 Configuring JSF and JSTL Libraries</ulink>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "From the administration console, navigate to the <literal>Deployments</literal> page using the left hand menu."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <literal>Install</literal> button at the top of the deployments table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Using the directory browser navigate to the <literal>$BEA_HOME/wlserver_10.3/common/deployable-libraries</literal> directory. Then select the <literal>jsf-1.2.war</literal> archive, and click the <literal>Next</literal> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Make sure that the <literal>Install this deployment as a library</literal> option is selected. Click the <literal>Next</literal> button on the <literal>Install Application Assistant</literal> page."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <literal>Next</literal> button on the <literal>Optional Settings</literal> page."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Make sure that the <literal>Yes, take me to the deployment's configuration screen</literal> option is selected. Then, click the <literal>Finish</literal> button on the <literal>Review your choices and click Finish</literal> page."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On the <literal>Settings for jsf(1.2,1.2.3.1)</literal> page, set the <literal>Deployment Order</literal> to <literal>99</literal> so that it is deployed prior to automatically-deployed applications. Then, click the <literal>Save</literal> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The final step is to add the <literal>javax.jsf_1.2.0.0.jar</literal> from <literal>jsf-1.2.war</literal> to the domain's shared library. You will need to restart the server to implement this change."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> Example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are several obstacles to running Seam EJBs on Weblogic. This section describes those obstacles and the changes you will need to make to the <literal>jee5/booking</literal> example so that it deploys and functions correctly."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "EJB3 Issues with Weblogic"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Several releases of Weblogic (9.X, 10.0.MP1, and 10.3) have problems generating stubs and compiling EJBs that use variable arguments in their methods. These issues have been patched in Weblogic 10.0.MP1, but only partially addressed in Weblogic 10.3."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>varargs</literal> Issue"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The Weblogic EJB compiler mistakes methods using <literal>varargs</literal> (variable arguments) as having the <literal>transient</literal> modifier. When, during deployment, Weblogic generates its own stub classes from EJBs with <literal>varargs</literal>, the stubs do not generate correctly, and the deployment fails. This is a problem for Seam users who want to use the internal EJB <literal>TimerServiceDispatcher</literal> in their deployments."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The unpatched version of Weblogic 10.1.MP1 displays exceptions as follows when attempting to generate stubs for EJBs with <literal>varargs</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This issue has been corrected in Weblogic 10.3, and Weblogic 10.0.MP1 users can request the <literal>CR327275</literal> patch from BEA Support to correct the problem."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Missing EJB Methods Issue"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The fix for the <literal>varargs</literal> problem exposed a second issue that causes certain EJB methods to be omitted from Weblogic's internally-generated stub classes. This results in the following error messages during deployment:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This issue has been addressed in Weblogic 10.0.MP1. The patch (referred to as both <literal>CR370259</literal> and <literal>CR363182</literal>) can be requested through BEA Support."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "However, the issue has not been corrected in Weblogic 10.3. Not all users experience this problem, but there is a special Seam <filename>jar</filename> available for Seam users who want to deploy an EJB application to WebLogic."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The special <filename>jar</filename>, <literal>jboss-seam-wls-compatible.jar</literal> is available for Seam 2.0.2.CR2 onward, and is located in the <literal>$SEAM/lib/interop</literal> directory. This <filename>jar</filename> replaces <literal>jboss-seam.jar</literal>. The only change to the <filename>jar</filename> is that <literal>TimerServiceDispatcher</literal> (the EJB for which the problems occurred) has been removed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To use the <filename>jar</filename>, rename the <literal>jboss-seam-wls-compatible.jar</literal> as \"<literal>jboss-seam.jar</literal>\" and replace the original <literal>jboss-seam.jar</literal> in your application's <filename>EAR</filename> file. This is demonstrated in the <literal>jee5/booking</literal> example. With this <filename>jar</filename>, you will not be unable to use the <literal>TimerServiceDispatcher</literal> EJB."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Getting the <literal>jee5/booking</literal> Working"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This section takes you through the steps required to set up and run the <literal>jee5/booking</literal> example."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Setting up the HSQL data source"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This example application uses the in-memory Hypersonic database, so the first step is to set up the correct data source. You can do this using a set of wizard-like pages in the administration console."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy <literal>hsqldb.jar</literal> to the WebLogic domain's shared library directory: <literal> cp $SEAM_HOME/lib/hsqldb.jar $BEA_HOME/user_projects/domains/seam_examples/lib </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the server and navigate to the administration console by following the instructions under <xref linkend=\"bea_start_stop_access\" />"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On the left hand tree, navigate <guilabel>seam_examples</guilabel>→<guilabel>Services</guilabel>→<guilabel>JDBC</guilabel>→<guilabel>Data Sources</guilabel>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Then select the <guibutton>New</guibutton> button at the top of the data source table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fill in the following:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "DataSource Name: <literal>seam-jee5-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "JNDI Name: <literal>seam-jee5-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Database Type and Driver: <literal>other</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guibutton>Next</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "On the <literal>Transaction Options</literal> page, click the <guibutton>Next</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Fill in the following on the <literal>Connection Properties</literal> page:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Database Name: <literal>hsqldb</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Host Name: <literal>127.0.0.1</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Port: <literal>9001</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Username: <literal>sa</literal> (empties password fields)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Password: leave empty."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Driver Class Name: <literal>org.hsqldb.jdbcDriver</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "URL: <literal>jdbc:hsqldb:.</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Username: <literal>sa</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Do not alter any other fields."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Choose the target domain for the data source —in this case, <literal>AdminServer</literal>. Click the <guibutton>Next</guibutton> button."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Configuration and Build changes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When your data source has been set, you can begin to prepare your Seam application for deployment to the WebLogic server."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal> resources/META-INF/persistence.xml </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>jta-data-source</literal> to match what you entered previously:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Then use comment tags to hide the Glassfish properties."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Then add these two properties for weblogic support."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal> resources/META-INF/weblogic-application.xml </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You will need to create this file. It should contain the following:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "These changes serve two purposes. The first element, <literal>library-ref</literal>, tells WebLogic that this application will use the deployed JSF libraries. The second element, <literal>prefer-application-packages</literal>, tells WebLogic that the <literal>antlr</literal> <filename>JAR</filename>s take precedence. This prevents confliction with Hibernate."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/META-INF/ejb-jar.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "These changes work around problems caused by WebLogic using a single instance of the <literal>sessionBeanInterceptor</literal> for all session beans. Seam's interceptor caches and stores some component-specific attributes. When a single instance is used for multiple session beans, the interceptor can become primed for an unintended bean, which causes errors. Solve this problem by defining a separate interceptor binding for each EJB you wish to use —this forces WebLogic to use a separate instance for each EJB."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Modify the <literal>assembly-descriptor</literal> element to resemble the following:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/WEB-INF/weblogic.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This file and the element <literal>library-ref</literal> tell WebLogic that this application uses the deployed JSF libraries. Because both applications require access, you must make this change both in this file and in the <literal>weblogic-application.xml</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building and Deploying the Application"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are some final changes to the build script and the <literal>jboss-seam.jar</literal> before you can deploy the application."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>build.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add the following so that the <literal>weblogic-application.xml</literal> will be packaged:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal> $SEAM/lib/interop/jboss-seam-wls-compatible.jar </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This change is discussed previously in <xref linkend=\"weblogic-ejb-issues\" />. There are two options:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The first option is to rename this <filename>JAR</filename> and use it to replace the original <literal>$SEAM/lib/jboss-seam.jar</literal> file. This approach requires no changes to the packaged <filename>EAR</filename>, but overwrites the original <literal>jboss-seam.jar</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The second option is to modify the packaged <filename>EAR</filename> archive and replace the <literal>jboss-seam.jar</literal> in the archive manually. This leaves the original <filename>JAR</filename> intact, but requires a manual step whenever the archive is packaged."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Assuming that you choose the first option to handle <literal>jboss-seam-wls-compatible.jar</literal>, you can build the application by running <literal>ant archive</literal> at the base of the <literal>jee5/booking</literal> example directory."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Because we created our WebLogic domain in development mode, we can deploy the application by adding the <filename>EAR</filename> archive to the domain's <literal>autodeploy</literal> directory. <programlisting> cp ./dist/jboss-seam-jee5.ear $BEA_HOME/user_projects/domains/seam_examples/autodeploy </programlisting>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can then view the application at: <literal>http://localhost:7001/seam-jee5/</literal>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>jpa</literal> booking example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This version of the Hotel Booking example has been implemented with Seam POJOs and the Hibernate JPA, so it does not require EJB3 support. The application already contains configuration and build script options for use with WebLogic 10.x."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "First, we will build and deploy the example for WebLogic 10.x. Then we will take you through the differences between the WebLogic and JBoss AS versions."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This example assumes that WebLogic's JSF libraries are configured as described in <xref linkend=\"weblogic-jsf-deploy\" />."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building and deploying the <literal>jpa</literal> Booking example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are three steps involved in building and deploying the example: setting up the data source, building the application, and deploying the application."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Setting up the datasource"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The WebLogic 10.x version will use the in-memory HSQL database instead of the built-in PointBase database. If you want to use the PointBase database, you must set up a PointBase data source, and alter <literal>persistence.xml</literal> such that Hibernate uses the PointBase dialect. (The <literal>jpa/weblogic92</literal> example uses PointBase, and can be used as a reference.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The data source configuration process is similar to that in <xref linkend=\"weblogic-hsql-jee5-ds\" />. You can follow the steps listed in that section and make the following replacement entries where required:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "DataSource Name: <literal>seam-jpa-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "JNDI Name: <literal>seam-jpa-ds</literal>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building the example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Building the example only requires the correct Ant command: <programlisting>ant weblogic10 </programlisting>. This creates a container-specific distribution and exploded archive directories."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying the example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When you installed WebLogic by following the steps in <xref linkend=\"weblogic-domain\" />, you chose to create the domain in development mode. Therefore, to deploy the example, copy the <filename>WAR</filename> archive into the <literal>autodeploy</literal> directory:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can then view the application at: <literal>http://localhost:7001/jboss-seam-jpa/</literal> ."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Changes between WebLogic 10.x and 9.2"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are several differences between the WebLogic 10.x and 9.2 versions of the example applications:"
-msgstr ""
-
-#. Tag: para
-#, 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 data source. The 10.x version uses the <literal>HSQL</literal> database and a custom data source."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/weblogic.xml</literal> —This file solves an issue with an older version of the <literal>ANTLR</literal> libraries used internally by WebLogic 10.x, and configures the application to use the shared JSF libraries installed above."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This forces WebLogic to use classes and libraries in the application before libraries in the classpath. Without this change, Hibernate must use an older, less efficient query factory by setting the following property in the <literal>META-INF/persistence.xml</literal> file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/components.xml</literal> —In WebLogic 10.x examples, you can enable JPA entity transactions by adding:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/web.xml</literal> —The <literal>jsf-impl.jar</literal> is not included in the <filename>WAR</filename>, so this listener must be configured like so:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "There are further changes between the WebLogic 10.x and JBoss versions of the example applications:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>META-INF/persistence.xml</literal> —to use the pre-installed database in WebLogic 10.x, you must update the location of WebLogic's transaction manager by setting the following JPA property:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/lib</literal> —The WebLogic versions require several library packages that are not included with the JBoss AS, in order to fulfil Hibernate dependencies:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You need the following <filename>JAR</filename>s to use Hibernate as your JPA provider:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-annotations.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-entitymanager.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-validator.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>jboss-common-core.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>commons-logging.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>commons-collections.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "WebLogic also requires the following third-party <filename>JAR</filename>s:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>antlr.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>cglib.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>asm.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>dom4j.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>el-ri.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>javassist.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>concurrent.jar</filename>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying a <literal>seam-gen</literal>-created application on WebLogic 10.x"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<application>seam-gen</application> is useful for swift application development. Out of the box, it produces applications configured to run on JBoss AS. This section shows you how to configure <application>seam-gen</application> so that your applications will run on WebLogic. This involves updating or removing configuration files, and adding <filename>JAR</filename>s that are not shipped as part of WebLogic."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This example configuration covers basic <application>seam-gen</application> <filename>WAR</filename> deployment. It demonstrates Seam POJO components, Hibernate JPA, Facelets, Drools security, RichFaces, and a configurable data source."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Running <literal>seam-gen</literal> setup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "First, run <literal>./seam setup</literal> in the base directory of your Seam distribution to tell <application>seam-gen</application> about your project. The paths in the following example can be altered to fit your own environment:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Type <literal>./seam new-project</literal> to create your project. In the above environment, you would type <literal>cd /home/jbalunas/workspace/weblogic_example</literal> to view the newly created project."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Changes required for WebLogic 10.x deployment"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Before deployment, we must update and remove some configuration files, and update the libraries deployed with the application."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Configuration file changes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the default target to <literal>archive</literal>, like so:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/META-INF/persistence-dev.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>jta-data-source</literal> to <literal>seam-gen-ds</literal>\", and use this as the <literal>jndi-name</literal> when creating the data source in WebLogic's administration console."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the transaction type to <literal>RESOURCE_LOCAL</literal> so that you can use JPA transactions."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For WebLogic support, add or modify the following properties:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To deploy WebLogic using the prod profile, you must also apply these changes to <literal>persistence-prod.xml</literal>."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resource/WEB-INF/weblogic.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You will need to create and populate this file by this file and populate it with the following:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal> resource/WEB-INF/components.xml </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add the following to tell Seam to use JPA transactions:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You must also add the transaction namespace and schema location to the file header:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resource/WEB-INF/web.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/web.xml</literal> —The <literal>jsf-impl.jar</literal> is not included in the <filename>WAR</filename>, so you must configure a listener as follows:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal> resources/WEB-INF/jboss-web.xml </literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This is used to enable classloading isolation in the JBoss AS. Since we are not deploying to the JBoss AS, this file can be deleted."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/*-ds.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "These files define data sources in the JBoss AS. Since we are not deploying to the JBoss AS, these files can be deleted."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Library changes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<application>seam-gen</application> has similar library dependencies to those in the previous <literal>jpa</literal> example. (See <xref linkend=\"weblogic-jpa-diff\" />.) The changes required to fulfil these dependencies are:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "build.xml —Append the following to the target <filename>WAR</filename>:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building and Deploying your application"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The final step is deployment."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Setting up the data source"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Configure your data source by following the instructions listed in <xref linkend=\"weblogic-hsql-jee5-ds\" />, making the following replacements:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "DataSource Name: <literal>seam-gen-ds</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "JNDI Name: <literal>seam-gen-ds</literal>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building the application"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Run <literal>ant</literal> in the project's base directory to build the application."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When we installed WebLogic by following the steps outlined in <xref linkend=\"weblogic-domain\" />, we chose to place the domain in development mode, so to deploy the application, copy the <filename>WAR</filename> into the <literal>autodeploy</literal> directory."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can then view the deployed application at: <literal>http://localhost:7001/weblogic_example/</literal>."
-msgstr ""
-
Deleted: projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Websphere.po
===================================================================
--- projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Websphere.po 2010-02-18 01:08:36 UTC (rev 101102)
+++ projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Websphere.po 2010-02-18 01:10:30 UTC (rev 101103)
@@ -1,769 +0,0 @@
-#
-# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-02-18T01:03:03\n"
-"PO-Revision-Date: 2010-02-18T01:03:03\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Seam on IBM's Websphere AS"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<trademark class=\"registered\">WebSphere</trademark> Application Server V7 (hereafter WebSphere AS) is IBM's latest stable application server offering, and is fully Java EE 5 (JEE5) certified."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This chapter contains basic information about using the WebSphere AS to deploy both the JEE5 Booking example, and the JPA example application."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "WebSphere AS environment and deployment information"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Since WebSphere AS is a commercial product, we recommend following the directions provided by IBM for your particular installation and license type. This section details several versions of the server, installation tips, and some property configurations required to deploy all example applications."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Installation versions"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "All examples and information in this chapter are based on WebSphere AS V7. Follow the WebSphere AS installation instructions to install the WebSphere AS."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<ulink url=\"http://www.ibm.com/developerworks/downloads/ws/was\">WebSphere Application Server V7</ulink>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Create a server profile with the Profile Management Tool if you did not create a profile during installation."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The Hotel Booking example, which runs on JBoss AS, is designed to run on GlassFish out of the box. Follow the steps below to deploy it to the WebSphere AS. You can find this example in the <literal>$SEAM_DIST/examples/jee5/booking</literal> directory."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Configuration file changes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You will need to configure the following files as described to run the booking example correctly on WebSphere AS:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/WEB-INF/components.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Remove the <literal>/local</literal> string from the <literal>jndi-pattern</literal>, like so:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/META-INF/ejb-jar.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Remove the <literal>/local</literal> string from <literal>ejb-ref-name</literal>, as follows:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/WEB-INF/web.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You will also need to alter the EJB reference in <filename>web.xml</filename> so that WebSphere AS can automatically bind EJB3 references in the web module to EJB3 beans in the EAR module. Replace all <literal>/local</literal> strings in <literal>ejb-local-refs</literal> with the values shown here:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>EjbSynchronizations</literal> is a built-in Seam EJB, not part of the Hotel Booking example. If your application specifies <literal>transaction:ejb-transaction</literal> in <filename>components.xml</filename>, you must also include the following in your <filename>web.xml</filename>:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you do not include this, you will encounter the following error:"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/META-INF/persistence.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This example requires the WebSphere AS's default data source. To use it, change the <literal>jta-data-source</literal> element like so:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "We must also adjust some Hibernate properties. First, use comment tags to omit the GlassFish properties and include the following changes:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>hibernate.transaction.manager_lookup_class</literal> —A standard Hibernate transaction manager property for WebSphere AS V6.x and V7."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>hibernate.transaction.flush_before_completion</literal> —This has been commented out so that transactions are managed by the container. If this is set to <parameter>true</parameter>, an exception will occur when the WebSphere AS looks up the EJBContext."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>hibernate.dialect</literal> —the GlassFish V2 Derby database has replaced the embedded database from WebSphere AS 6.1.0.9 onward."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>src/GlassfishDerbyDialect.java</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy <filename>GlassfishDerbyDialect.java</filename> from the JPA example source directory into the <literal>/src</literal> directory with the following command (executed from within the <literal>jee5/booking</literal> directory):"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This class will be added to the <filename>jboss-seam-jee5.jar</filename> file."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/import.sql</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Copy this file from the JPA example so that changes to the <literal>ID</literal> column are supported. (Column support is the only difference between the files.) Use the following command: <programlisting> cp ../../jpa/resources-websphere7/import.sql ./resources </programlisting>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building the <literal>jee5/booking</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To apply these changes to the application, we must edit the <filename>build.xml</filename> file, and add several <filename>JAR</filename>s to make the application compatible with WebSphere AS."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Library dependency changes"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Remove the <filename>log4j.jar</filename> so that all application log output will be added to the WebSphere AS log. Additional steps are required to fully configure <filename>log4j.jar</filename> —these steps are outside the scope of this document."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Updating the <literal>build.xml</literal> file"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Append the following to <filename>build.xml</filename> to override the default fileset that populates <filename>jboss-seam-jee5.jar</filename>:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Now execute the <command>ant archive</command> task to add the built application to the <literal>jee5/booking/dist</literal> directory."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying the application to Websphere"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "We will use WebSphere AS's administration console to deploy the application. The steps outlined here are for WebSphere AS V7. The ports are default values —if your ports have changed, substitute your own correct values."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Log in to the administration console through <programlisting>https://localhost:9043/admin </programlisting> or <programlisting>http://localhost:9060/admin </programlisting> ."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Access <guimenu>Websphere enterprise applications</guimenu> under the left hand side menu: <guimenu>Applications</guimenu>→<guimenu>Application Type</guimenu>→<guimenu>Websphere enterprise applications</guimenu>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click <guilabel>Install</guilabel> at the top of the <literal>Enterprise Applications</literal> table. Perform the following steps on the listed pages of the installation wizard:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Preparing for the application installation</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Use the file upload widget to browse to the <filename>examples/jee5/booking/dist/jboss-seam-jee5.ear</filename> file."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guibutton>Next</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guibutton>Fast Path</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Select installation options</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Check the <guilabel>Deploy enterprise beans</guilabel> and <guilabel>Allow EJB reference targets to resolve automatically</guilabel> checkboxes. (Required, unless you use a WebSphere AS tool to package the application.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Map modules to servers</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Because we are only using one server, no changes are required. Click the <guibutton>Next</guibutton>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Summary</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "No changes are required. Click the <guibutton>Finish</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Installation</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The wizard installs and deploy your application."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When the wizard finishes, click <guilabel>Save</guilabel> to return to the <literal>Enterprise Applications</literal> table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Once the application is installed, make the following adjustments so that it can be run:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click <guilabel>Seam Booking</guilabel> from the <literal>Enterprise Applications</literal> table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guilabel>Manage Modules</guilabel>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click the <guilabel>jboss-seam-jee5-booking.war</guilabel> link."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>Class loader order</literal> combo box to <literal>Classes loaded with application class loader first (parent last)</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click <guilabel>Apply</guilabel>, and then <guilabel>Save</guilabel>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Return to the <literal>Seam Booking</literal> page."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click on the <guilabel>Class loading and update detection</guilabel> link."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Select the radio button for <guilabel>Classes loaded with application class loader first</guilabel>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click <guilabel>Apply</guilabel> and then <guilabel>Save</guilabel>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Start the application by returning to the <literal>Enterprise Applications</literal> table and selecting your application from the list. Then click the <guibutton>Start</guibutton> at the top of the table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can now access the application at <literal>http://localhost:9080/seam-jee5-booking/index.html</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "The <literal>jpa</literal> booking example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This version of the Hotel Booking example is implemented in Seam POJOs rather than EJB3 beans, and uses Hibernate JPA for JPA transactions. The application already contains configuration and build script options for WebSphere AS. This section shows you how to build and deploy the example, and the changes required to run it."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building the <literal>jpa</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Build the example by running <command>ant websphere7</command>. This creates a container-specific distribution, and exploded archive directories with the <literal>websphere7</literal> label."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying the <literal>jpa</literal> example"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Deploying this example is very similar to deploying the <literal>jee5</literal> example at <xref linkend=\"jee5-websphere-deploy\" />:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Click on <guibutton>Install</guibutton> in the <literal>Enterprise Applications</literal> table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Preparing to install the application</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Use the file upload widget to browse to <filename>examples/jpa/dist-websphere7/jboss-seam-jpa.war</filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The next three screens do not require any changes —click <guibutton>Next</guibutton> to pass them."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Map context roots for Web modules</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Enter <literal>jboss-seam-jpa</literal> in the <guilabel>Context root</guilabel> text box."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>Summary</literal> page"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Review your settings and click the <guibutton>Finish</guibutton> button to install the application. When installation completes, click <guilabel>Save</guilabel> to return to the <literal>Enterprise Applications</literal> table."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You will need to make some changes to the class loader before you start the application. Follow the instructions at <xref linkend=\"websphere-app-adj-after-install\" /> for <filename>jboss-seam-jpa.war</filename> instead of <literal>Seam Booking</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To start the application, select it in the <literal>Enterprise Applications</literal> table and click the <guibutton>Start</guibutton> button."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can now access the application at <literal>http://localhost:9080/jboss-seam-jpa/index.html</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Changes in Websphere AS V7"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "JBoss AS 4.2 deployments and WebSphere AS V7 deployments differ in therms of their library and configuration files."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>META-INF/persistence.xml</literal> —the data source JNDI path changes to the WebSphere transaction manager lookup class, and the Hibernate dialect is changed to <literal>GlassfishDerbyDialect</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>WEB-INF/components.xml</literal> —the <literal>/local</literal> string is removed from <literal>jndi-pattern</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>META-INF/ejb-jar.xml</literal> —in <literal>ejb-ref-name</literal>, the <literal>/local</literal> string has been removed from <literal>jboss-seam-jee5/AuthenticatorAction</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>src/GlassfishDerbyDialect.java</literal> —this class has been added to change the Hibernate dialect to <literal>GlassfishDerbyDialect</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<literal>import.sql</literal> —this file cannot populate the <literal>ID</literal> column when the correct dialect and Derby database are used for this application. This file has been removed."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Changes for dependent libraries"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The WebSphere version of this application requires several library packages that are not included in the standard distribution, to fulfil Hibernate dependencies. The <filename>JAR</filename>s listed below are required for examples other than the JBoss <literal>JPA</literal> example."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You require the following <filename>JAR</filename>s to use Hibernate as your JPA provider:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-annotations.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-commons-annotations.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-entitymanager.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>hibernate-validator.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>commons-collections.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>jboss-common-core.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "WebSphere requires the following third-party <filename>JAR</filename>s:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>antlr.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>cglib.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>asm.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>dom4j.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>javassist.jar</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>concurrent.jar</filename>"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Deploying a <literal>seam-gen</literal>-created application on Websphere V7"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<application>seam-gen</application> is useful for swift application development. Out of the box, it produces applications configured to run on JBoss AS. This section shows you how to configure <application>seam-gen</application> so that your applications will run on WebSphere AS. This involves updating or removing configuration files, and adding <filename>JAR</filename>s that are not shipped as part of WebSphere AS."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Running <literal>seam-gen</literal> Setup"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "First, run <literal>./seam setup</literal> in the base directory of your Seam distribution to tell <application>seam-gen</application> about your project. The paths in the following example can be altered to fit your own environment:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Type <command>./seam new-project</command> to create your project. In the above environment, you would type <literal>cd /home/jbalunas/workspace/websphere_example</literal> to view the newly created structure."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Changes required for WebSphere AS deployment"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Before deployment, we must update and remove some configuration files, and update the libraries deployed with the application."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/META-INF/persistence-dev.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>jta-data-source</literal> to <literal>DefaultDatasource</literal>. We will use the integrated WebSphere database."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add the following properties, or edit existing properties to resemble the following: (Detailed descriptions are available at <xref linkend=\"jee5-websphere-section\" />.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Remove the JBoss AS-specific method of exposing the <literal>EntityManagerFactory</literal>:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To deploy your application to WebSphere AS using the prod profile, you will also need to alter this setting in <filename>persistence-prod.xml</filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Required for database support. This file can be copied from the <literal>JPA</literal> example into the <literal>websphere_example/src</literal> directory. <programlisting>cp $SEAM/examples/jpa/src/GlassfishDerbyDialect.java ./src </programlisting>"
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<filename>resources/META-INF/jboss-app.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Used to enable class loading isolation in JBoss AS deployments —you can delete this file."
-msgstr ""
-
-#. Tag: term
-#, no-c-format
-msgid "<literal>resources/*-ds.xml</literal>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Used to define datasources in JBoss AS deployments —you can delete these files."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Enable container-managed transaction integration by adding the <literal><transaction:ejb-transaction></transaction:ejb-transaction> </literal> component and its namespace declaration <literal>xmlns:transaction=\"http://jboss.com/products/seam/transaction\"</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the <literal>jndi-pattern</literal> to <literal>java:comp/env/websphere_example/#{ejbName}</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This example does not require <literal>managed-persistence-context</literal>, so you can delete its entry."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Remove the <literal>/local</literal> string in <literal>ejb-ref-name</literal> to mark your EJBs for binding by WebSphere AS."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Creating the <literal>AuthenticatorAction</literal> EJB"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To create an EJB3 version of the <literal>Authenticator</literal> Seam POJO:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the generated <literal>Authenticator</literal> class"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Rename the class \"<literal>AuthenticatorAction</literal>\"."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Add the <literal>@Stateless</literal> annotation to the new <literal>AuthenticatorAction</literal> class."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Create an interface called <literal>Authenticator</literal>, implemented by <literal>AuthenticatorAction</literal>. (EJB3 requires that session beans have a local interface.) Annotate the interface with <literal>@Local</literal>, and add a single method with the same signature as the <literal>authenticate</literal> in <literal>AuthenticatorAction</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Since a reference to this class has already been added to <filename>web.xml</filename>, the new EJB3 is ready for deployment."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Extra <filename>JAR</filename> dependencies and other changes to <filename>build.xml</filename>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "This application has similar requirements to the <literal>jee5/booking</literal> example."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Change the default target to \"<literal>archive</literal>\". (We will not cover automatic deployment to WebSphere AS.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Instead of searching in the root of the <filename>websphere_example.jar</filename> for the Drools <filename>/security.drl</filename>, WebSphere searches in the root of the <filename>WAR</filename>. Add the following to the top of the <literal> <target name=\"war\" depends=\"compile\" description=\"Build the distribution.war file\"> </literal> target in <filename>build.xml</filename> to move <filename>/security.drl</filename> to the searched location at build time:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Now, add the <filename>JAR</filename>s to <filename>build.xml</filename> by placing them in <literal>include</literal> tags in the task's <literal><fileset dir=\"${basedir}\"></literal> section:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Hibernate dependencies"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Third party dependencies."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "<filename>jboss-seam.jar</filename> must be added to the <filename>EAR</filename> base directory."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Your changes should result in a list similar to the following:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Building and deploying the <application>seam-gen</application>-compliant application to Websphere"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Call <command>ant</command> in your project's base directory to build your application. The build target will be <filename>dist/websphere_example.ear</filename>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Follow the instructions in <xref linkend=\"jee5-websphere-deploy\" /> to deploy your application, using references to the <literal>websphere_example</literal> project instead of <literal>jboss-seam-jee5</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can then view the application at <literal>http://localhost:9080/websphere_example/index.html</literal>"
-msgstr ""
-
Deleted: projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Wicket.po
===================================================================
--- projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Wicket.po 2010-02-18 01:08:36 UTC (rev 101102)
+++ projects/docs/enterprise/5.0/Seam_Reference_Guide/ja-JP/Wicket.po 2010-02-18 01:10:30 UTC (rev 101103)
@@ -1,154 +0,0 @@
-#
-# AUTHOR <EMAIL at ADDRESS>, YEAR.
-#
-msgid ""
-msgstr ""
-"Project-Id-Version: 0\n"
-"POT-Creation-Date: 2010-02-18T01:03:03\n"
-"PO-Revision-Date: 2010-02-18T01:03:03\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: None\n"
-"MIME-Version: 1.0\n"
-"Content-Type: application/x-publican; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-
-#. Tag: title
-#, no-c-format
-msgid "Writing your presentation layer using Apache Wicket"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Seam supports Wicket as an alternative presentation layer to JSF. Some JSF features, like pageflows, are not yet available in Wicket, but you can see it in practice in the Seam example <code>wicket</code> — a Wicket-ported Booking example."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Adding Seam to your wicket application"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Wicket application features can be categorized as either bijection, or orchestration — these are detailed in the sections following."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Seam provides full support for annotation-based control in inner classes and constructors. However, since annotations are processed after any call to a superclass, injected attributes cannot be passed as arguments in calls to <code>this()</code> or <code>super()</code>. (We are working to improve this.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "When a method is called in an inner class, bijection occurs for any enclosing class. You can therefore place bijected variables in the outer class, and refer to them in any inner class."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Bijection"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "A Seam-enabled Wicket application has full access to the all standard Seam contexts: <literal>EVENT</literal>, <literal>CONVERSATION</literal>, <literal>SESSION</literal>, <literal>APPLICATION</literal> and <literal>BUSINESS_PROCESS</literal>. To access a Seam component from Wicket, inject the component with <literal>@In</literal>:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Your Wicket class is not a full Seam component, so you need not annotate it <literal>@Name</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can also outject an object into the Seam contexts from a Wicket component:"
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Orchestration"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Secure a Wicket component with the <literal>@Restrict</literal> annotation. This annotation restricts component access to logged in users. It can be placed on the outer component, or any inner components, and is automatically applied to nested classes."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can specify a particular restriction with an EL expression in the <literal>value</literal> attribute. (For more detailed information, refer to <xref linkend=\"security\" />.)"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Conversations can be demarcated from within a Wicket component by using <literal>@Begin</literal> and <literal>@End</literal>. For example:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The semantics here match those in a Seam component. Although the deprecated <literal>ifOutcome</literal> attribute is not supported, <literal>@Begin</literal> and <literal>@End</literal> can be placed on any method."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Your application may contain pages that can only be accessed if the user has a long-running conversation active. To enforce this, use the <literal>@NoConversationPage</literal> annotation:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you want to decouple your application classes further, you can use Seam events. You can raise an event with <literal>Events.instance().raiseEvent(\"foo\")</literal>, or annotate a method <literal>@RaiseEvent(\"foo\")</literal> — if the method returns a non-null outcome without exception, the event will be raised."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You can also control tasks and processes in Wicket classes with <literal>@CreateProcess</literal>, <literal>@ResumeTask</literal>, <literal>@BeginTask</literal>, <literal>@EndTask</literal>, <literal>@StartTask</literal> and <literal>@Transition</literal>."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Setting up your project"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "To intercept your annotations, Seam must instrument the bytecode of your Wicket classes. There are two possible methods: either place your classes in <literal>WEB-INF/wicket</literal>, so that Seam finds and instruments them at startup, or instrument via the ant task provided in <filename>jboss-seam-wicket-ant.jar</filename> like so:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Have ant copy the instrumented classes in <literal>${build.instrumented}</literal> to <literal>WEB-INF/classes</literal>. To hot deploy the Wicket components, copy the instrumented classes to <literal>WEB-INF/dev</literal>. (Your <literal>WicketApplication</literal> class must also be hot deployed.) When hot deployed classes are reloaded, the entire wicketApplication instance must be reinitialized for it to pick up new references to mounted page classes."
-msgstr ""
-
-#. Tag: title
-#, no-c-format
-msgid "Defining the Application"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Seam-based Wicket applications should use <literal>SeamWebApplication</literal> as the base class. This creates hooks into the Wicket lifecycle, allowing Seam to automatically propagate the conversation as required. It also adds status messages to the page."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "For example, <literal>SeamAuthorizationStrategy</literal> delegates authorization to Seam Security, allowing the use of <code>@Restrict</code> on Wicket components. <literal>SeamWebApplication</literal> installs the authorization strategy for you. You can specify the login page with <literal>getLoginPage()</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "You will also need to set the home page of the application with <literal>getHomePage()</literal>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Seam installs the Wicket filter automatically, but you need to tell Wicket which <literal>WebApplication</literal> class to use."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "If you plan to use JSF-based pages in the same application as Wicket pages, you will need to enable the JSF exception filter for JSF URLs:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "See the Wicket documentation for more on authorization strategies and other methods you can override on the <literal>Application</literal> class."
-msgstr ""
-
More information about the jboss-cvs-commits
mailing list