[jboss-cvs] JBossAS SVN: r105620 - projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Jun 3 02:55:35 EDT 2010
Author: misty at redhat.com
Date: 2010-06-03 02:55:34 -0400 (Thu, 03 Jun 2010)
New Revision: 105620
Modified:
projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Weblogic.xml
Log:
JBPAPP-4387
Modified: projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Weblogic.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Weblogic.xml 2010-06-03 06:47:46 UTC (rev 105619)
+++ projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Weblogic.xml 2010-06-03 06:55:34 UTC (rev 105620)
@@ -46,24 +46,21 @@
You may need to make the <literal>server103_XX.bin</literal> file executable, like so:
</para>
-<programlisting>chmod a+x server103_XX.bin
-</programlisting>
+<screen><command>chmod a+x server103_XX.bin</command></screen>
+
</listitem>
<listitem>
<para>
Execute the install:
</para>
-<programlisting>./server103_XX.bin
-</programlisting>
+<screen><command>./server103_XX.bin</command></screen>
+
</listitem>
<listitem>
<para>
- 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:
+ 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: <filename>/jboss/apps/bea</filename>
</para>
-
-<programlisting>/jboss/apps/bea
-</programlisting>
</listitem>
<listitem>
<para>
@@ -86,11 +83,9 @@
<orderedlist>
<listitem>
<para>
- Start the Weblogic configuration wizard:
+ Start the Weblogic configuration wizard: <command><replaceable>$BEA_HOME</replaceable>/wlserver_10.3/common/bin/config.sh</command>
</para>
-
-<programlisting>$BEA_HOME/wlserver_10.3/common/bin/config.sh
-</programlisting>
+
</listitem>
<listitem>
<para>
@@ -261,7 +256,7 @@
The unpatched version of Weblogic 10.1.MP1 displays exceptions as follows when attempting to generate stubs for EJBs with <literal>varargs</literal>.
</para>
-<programlisting><![CDATA[
+<screen>
java.io.IOException: Compiler failed executable.exec:
/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/AdminServer/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/
TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:194: modifier transient not allowed here
@@ -269,8 +264,8 @@
^
/jboss/apps/bea/wlserver_10.0/user_projects/domains/seam_examples/servers/AdminServer/cache/EJBCompilerCache/5yo5dk9ti3yo/org/jboss/seam/async/
TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:275: modifier transient not allowed here
- public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String arg0, org.jboss.seam.async.TimerSchedule arg1, java.lang.Object[] arg2)]]>
-</programlisting>
+ public transient javax.ejb.Timer scheduleTimedEvent(java.lang.String arg0, org.jboss.seam.async.TimerSchedule arg1, java.lang.Object[] arg2)
+</screen>
<para>
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.
</para>
@@ -282,15 +277,15 @@
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:
</para>
-<programlisting><![CDATA[
-<<Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
-<Compilation Error> TimerServiceDispatcher_qzt5w2_Impl.java: The type TimerServiceDispatcher_qzt5w2_Impl must implement the inherited abstract method TimerServiceDispatcher_qzt5w2_Intf.scheduleTimedEvent(String, Schedule, Object[])
-<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:
+<screen>
+<<Error> <EJB> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
+<Compilation Error> TimerServiceDispatcher_qzt5w2_Impl.java: The type TimerServiceDispatcher_qzt5w2_Impl must implement the inherited abstract method TimerServiceDispatcher_qzt5w2_Intf.scheduleTimedEvent(String, Schedule, Object[])
+<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:
Type mismatch: cannot convert from Object to Timer
-<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:
- Type mismatch: cannot convert from Object to Timer>
-<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1223409267344' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(jboss-seam.jar)]]>
-</programlisting>
+<Compilation Error> TimerServiceDispatcher_qzt5w2_LocalTimerServiceDispatcherImpl.java:
+ Type mismatch: cannot convert from Object to Timer>
+<Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID &#39;1223409267344&#39; for task &#39;0&#39;. Error is: &#39;weblogic.application.ModuleException: Exception preparing module: EJBModule(jboss-seam.jar)
+</screen>
<para>
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.
</para>
@@ -467,7 +462,7 @@
Change the <literal>jta-data-source</literal> to match what you entered previously:
</para>
-<programlisting role="XML"><![CDATA[<jta-data-source>seam-jee5-ds</jta-data-source>]]>
+<programlisting language="XML" role="XML"><![CDATA[<jta-data-source>seam-jee5-ds</jta-data-source>]]>
</programlisting>
</listitem>
<listitem>
@@ -480,7 +475,7 @@
Then add these two properties for weblogic support.
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<property name="hibernate.dialect"
value="org.hibernate.dialect.HSQLDialect"/>
<property name="hibernate.transaction.manager_lookup_class"
@@ -500,7 +495,7 @@
You will need to create this file. It should contain the following:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<?xml version="1.0" encoding="ISO-8859-1"?>
<weblogic-application>
@@ -538,7 +533,7 @@
Modify the <literal>assembly-descriptor</literal> element to resemble the following:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<assembly-descriptor>
<interceptor-binding>
@@ -602,7 +597,7 @@
You will need to create this file. It should contain the following:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app>
@@ -642,7 +637,7 @@
Add the following so that the <literal>weblogic-application.xml</literal> will be packaged:
</para>
-<programlisting role="XML"><![CDATA[ <!-- Resources to go in the ear --> <fileset id="ear.resources" dir="${resources.dir}"> <include name="META-INF/application.xml" /> <include name="META-INF/weblogic-application.xml" /> <include name="META-INF/*-service.xml" /> <include name="META-INF/*-xmbean.xml" /> <include name="treecache.xml" /> <include name="*.jpdl.xml" /> <exclude name=".gpd.*" /> <include name="*.cfg.xml" /> <include name="*.xsd" /> </fileset>]]>
+<programlisting language="XML" role="XML"><![CDATA[ <!-- Resources to go in the ear --> <fileset id="ear.resources" dir="${resources.dir}"> <include name="META-INF/application.xml" /> <include name="META-INF/weblogic-application.xml" /> <include name="META-INF/*-service.xml" /> <include name="META-INF/*-xmbean.xml" /> <include name="treecache.xml" /> <include name="*.jpdl.xml" /> <exclude name=".gpd.*" /> <include name="*.cfg.xml" /> <include name="*.xsd" /> </fileset>]]>
</programlisting>
</listitem>
</itemizedlist>
@@ -676,9 +671,10 @@
</para>
<para>
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>
+<command>
cp ./dist/jboss-seam-jee5.ear $BEA_HOME/user_projects/domains/seam_examples/autodeploy
-</programlisting>
+</command>
+
</para>
<para>
You can then view the application at: <literal>http://localhost:7001/seam-jee5/</literal>
@@ -731,8 +727,7 @@
<title>Building the example</title>
<para>
Building the example only requires the correct Ant command:
-<programlisting>ant weblogic10
-</programlisting>. This creates a container-specific distribution and exploded archive directories.
+<command>ant weblogic10</command> This creates a container-specific distribution and exploded archive directories.
</para>
</section>
@@ -740,10 +735,9 @@
<title>Deploying the example</title>
<para>
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:
- </para>
-
-<programlisting>cp ./dist-weblogic10/jboss-seam-jpa.war $BEA_HOME/user_projects/domains/seam_examples/autodeploy
-</programlisting>
+<command>cp ./dist-weblogic10/jboss-seam-jpa.war $BEA_HOME/user_projects/domains/seam_examples/autodeploy</command>
+ </para>
+
<para>
You can then view the application at: <literal>http://localhost:7001/jboss-seam-jpa/</literal> .
</para>
@@ -769,7 +763,7 @@
<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.
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -793,7 +787,7 @@
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.
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<property name="hibernate.query.factory_class"
value="org.hibernate.hql.classic.ClassicQueryTranslatorFactory"/>]]>
</programlisting>
@@ -803,7 +797,7 @@
<literal>WEB-INF/components.xml</literal> —In WebLogic 10.x examples, you can enable JPA entity transactions by adding:
</para>
-<programlisting role="XML"><![CDATA[<transaction:entity-transaction entity-manager="#{em}"/>]]>
+<programlisting language="XML" role="XML"><![CDATA[<transaction:entity-transaction entity-manager="#{em}"/>]]>
</programlisting>
</listitem>
<listitem>
@@ -811,7 +805,7 @@
<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:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>]]>
@@ -829,7 +823,7 @@
<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:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<property name="hibernate.transaction.manager_lookup_class"
value="org.hibernate.transaction
.WeblogicTransactionManagerLookup"/>]]>
@@ -952,8 +946,8 @@
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:
</para>
-<programlisting><![CDATA[./seam setup Buildfile: build.xml init: setup: [echo] Welcome to seam-gen :-) [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects] /home/jbalunas/workspace [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA] /jboss/apps/jboss-4.2.3.GA [input] Enter the project name [myproject] [myproject] weblogic-example [echo] Accepted project name as: weblogic_example [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT) [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, ) war [input] Enter the Java package name for your session beans [org.jboss.seam. tutorial.weblogic.action] [org.jboss.seam.tutorial.weblogic.action] org.jboss.seam.tutorial.weblogic.action [input] Enter the Java pac!
kage name for your entity beans [org.jboss.seam. tutorial.weblogic.model] [org.jboss.seam.tutorial.weblogic.model] org.jboss.seam.tutorial.weblogic.model [input] Enter the Java package name for your test cases [org.jboss.seam. tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action.test] org.jboss.seam.tutorial.weblogic.test [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2) [input] Enter the Hibernate dialect for your database [org.hibernate. dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect] [input] Enter the filesystem path to the JDBC driver jar [/tmp/seamlib/hsqldb.jar] [/tmp/seam/lib/hsqldb.jar] [input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver] [org.hsqldb.jdbcDriver] [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:hsqldb:.] [input] Enter database username [sa] [sa] [input] Enter database password [] [] [input] Enter the database s!
chema name (it is OK to leave this blank) [] [] [input] Enter !
the data
base catalog name (it is OK to leave this blank) [] [] [input] Are you working with tables that already exist in the database? [n] (y, [n], ) [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], ) [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] [] [propertyfile] Creating new property file: /rhdev/projects/jboss-seam/cvs-head/jboss-seam/seam-gen/build.properties [echo] Installing JDBC driver jar to JBoss server [copy] Copying 1 file to /jboss/apps/jboss-4.2.3.GA/server/default/lib [echo] Type 'seam create-project' to create the new project BUILD SUCCESSFUL]]>
-</programlisting>
+<screen><![CDATA[./seam setup Buildfile: build.xml init: setup: [echo] Welcome to seam-gen :-) [input] Enter your Java project workspace (the directory that contains your Seam projects) [C:/Projects] [C:/Projects] /home/jbalunas/workspace [input] Enter your JBoss home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA] /jboss/apps/jboss-4.2.3.GA [input] Enter the project name [myproject] [myproject] weblogic-example [echo] Accepted project name as: weblogic_example [input] Select a RichFaces skin (not applicable if using ICEFaces) [blueSky] ([blueSky], classic, ruby, wine, deepMarine, emeraldTown, sakura, DEFAULT) [input] Is this project deployed as an EAR (with EJB components) or a WAR (with no EJB support) [ear] ([ear], war, ) war [input] Enter the Java package name for your session beans [org.jboss.seam. tutorial.weblogic.action] [org.jboss.seam.tutorial.weblogic.action] org.jboss.seam.tutorial.weblogic.action [input] Enter the Java package nam!
e for your entity beans [org.jboss.seam. tutorial.weblogic.model] [org.jboss.seam.tutorial.weblogic.model] org.jboss.seam.tutorial.weblogic.model [input] Enter the Java package name for your test cases [org.jboss.seam. tutorial.weblogic.action.test] [org.jboss.seam.tutorial.weblogic.action.test] org.jboss.seam.tutorial.weblogic.test [input] What kind of database are you using? [hsql] ([hsql], mysql, oracle, postgres, mssql, db2, sybase, enterprisedb, h2) [input] Enter the Hibernate dialect for your database [org.hibernate. dialect.HSQLDialect] [org.hibernate.dialect.HSQLDialect] [input] Enter the filesystem path to the JDBC driver jar [/tmp/seamlib/hsqldb.jar] [/tmp/seam/lib/hsqldb.jar] [input] Enter JDBC driver class for your database [org.hsqldb.jdbcDriver] [org.hsqldb.jdbcDriver] [input] Enter the JDBC URL for your database [jdbc:hsqldb:.] [jdbc:hsqldb:.] [input] Enter database username [sa] [sa] [input] Enter database password [] [] [input] Enter the database schema na!
me (it is OK to leave this blank) [] [] [input] Enter the data!
base cat
alog name (it is OK to leave this blank) [] [] [input] Are you working with tables that already exist in the database? [n] (y, [n], ) [input] Do you want to drop and recreate the database tables and data in import.sql each time you deploy? [n] (y, [n], ) [input] Enter your ICEfaces home directory (leave blank to omit ICEfaces) [] [] [propertyfile] Creating new property file: /rhdev/projects/jboss-seam/cvs-head/jboss-seam/seam-gen/build.properties [echo] Installing JDBC driver jar to JBoss server [copy] Copying 1 file to /jboss/apps/jboss-4.2.3.GA/server/default/lib [echo] Type 'seam create-project' to create the new project BUILD SUCCESSFUL]]>
+</screen>
<para>
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.
</para>
@@ -976,7 +970,7 @@
Change the default target to <literal>archive</literal>, like so:
</para>
-<programlisting role="XML"> <![CDATA[<project name="weblogic_example" default="archive" basedir=".">]]>
+<programlisting language="XML" role="XML"> <![CDATA[<project name="weblogic_example" default="archive" basedir=".">]]>
</programlisting>
</listitem>
</itemizedlist>
@@ -996,7 +990,7 @@
Change the transaction type to <literal>RESOURCE_LOCAL</literal> so that you can use JPA transactions.
</para>
-<programlisting role="XML"> <![CDATA[<persistence-unit name="weblogic_example" transaction-type="RESOURCE_LOCAL">]]>
+<programlisting language="XML" role="XML"> <![CDATA[<persistence-unit name="weblogic_example" transaction-type="RESOURCE_LOCAL">]]>
</programlisting>
</listitem>
<listitem>
@@ -1004,7 +998,7 @@
For WebLogic support, add or modify the following properties:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<property name="hibernate.cache.provider_class"
value="org.hibernate.cache.HashtableCacheProvider"/>
<property name="hibernate.transaction.manager_lookup_class"
@@ -1027,7 +1021,7 @@
You will need to create and populate this file by this file and populate it with the following: <!-- #modify: please check, this step originally referred readers elsewhere without clarifying what to include... -->
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app>
@@ -1049,16 +1043,16 @@
Add the following to tell Seam to use JPA transactions:
</para>
-<programlisting role="XML"><![CDATA[<transaction:entity-transaction entity-manager="#{entityManager}"/>]]>
+<programlisting language="XML" role="XML"><![CDATA[<transaction:entity-transaction entity-manager="#{entityManager}"/>]]>
</programlisting>
<para>
You must also add the transaction namespace and schema location to the file header:
</para>
-<programlisting role="XML"><![CDATA[xmlns:transaction="http://jboss.com/products/seam/ transaction"]]>
+<programlisting language="XML" role="XML"><![CDATA[xmlns:transaction="http://jboss.com/products/seam/ transaction"]]>
</programlisting>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
http://jboss.com/products/seam/transaction
http://jboss.com/products/seam/transaction-2.1.xsd]]>
</programlisting>
@@ -1071,7 +1065,7 @@
<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:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>]]>
@@ -1108,7 +1102,7 @@
build.xml —Append the following to the target <filename>WAR</filename>:
</para>
-<programlisting role="XML"><![CDATA[
+<programlisting language="XML" role="XML"><![CDATA[
<copy todir="${war.dir}/WEB-INF/lib">
<fileset dir="${lib.dir}">
@@ -1175,7 +1169,7 @@
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.
</para>
-<programlisting role="XML">
+<programlisting language="XML" role="XML">
cp ./dist/weblogic_example.war /jboss/apps/bea/user_projects/domains/seam_examples/autodeploy
</programlisting>
<para>
More information about the jboss-cvs-commits
mailing list