Date: 2004-10-29T03:53:24
Editor: RalfBarkow <[EMAIL PROTECTED]>
Wiki: Apache Geronimo Wiki
Page: PetStore
URL: http://wiki.apache.org/geronimo/PetStore
We shouldn't need the ejb-link section anymore
Change Log:
------------------------------------------------------------------------------
@@ -25,9 +25,9 @@
1. Unpack petstore.ear (one of the files that constitute the application) to
a directory, say ''/petstore/ear'' (on Windows it'd be ''c:/petstore/ear'')
- 1. Change the current working directory to /petstore/ear.
+ 2. Change the current working directory to /petstore/ear.
- 1. Edit {{{META-INF/application.xml}}} and change the root tag
''application'' to:
+ 3. Edit {{{META-INF/application.xml}}} and change the root tag
''application'' to:
{{{
<application xmlns="http://java.sun.com/xml/ns/j2ee";>
@@ -36,7 +36,7 @@
Note: this is an optional task. Indeed, Deployment Descriptors, namely
''application.xml'', ''web.xml'', ''ra.xml'' and ''ejb-jar.xml'', are
transparently upgraded upon deployment. In other words, if you have an old
deployment descriptor based on a ''.dtd'' (''e.g.'' ''application_1_3.dtd'')
then it will be turned into a deployment descriptor compliant with the
corresponding ''.xsd'' (''e.g.'' ''application_1_4.xsd'').
How does it work exactly? See
''org.apache.geronimo.schema.SchemaConversionUtils''.
- 1. Create {{{META-INF/geronimo-application.xml}}}:
+Create {{{META-INF/geronimo-application.xml}}}:
{{{
<?xml version="1.0" encoding="UTF-8"?>
@@ -52,7 +52,7 @@
Note: this is an optional task. Indeed, Geronimo specific Deployment
Descriptors are created on the fly if not present. The current implementation
is really basic and not really useful “as is” for some J2EE components. Indeed,
some logic needs to be added in order to infer the configuration of these
Geronimo specific Deployment Descriptor (''e.g.'' JNDI name of an EJB, CMP
mapping et cetera).
- 1. Create {{{META-INF/openejb-jar.xml}}}:
+Create {{{META-INF/openejb-jar.xml}}}:
{{{
<?xml version="1.0"?>
@@ -70,7 +70,7 @@
</openejb-jar>
}}}
- and add it to every EJB module:
+and add it to every EJB module:
* asyncsender-ejb.jar
* cart-ejb.jar
@@ -80,7 +80,7 @@
* signon-ejb.jar
* uidgen-ejb.jar
- using the following command:
+using the following command:
{{{
jar -uvf <ejb-module> META-INF/openejb-jar.xml
@@ -88,7 +88,7 @@
Once it's done, delete META-INF/openejb-jar.xml file.
- 1. Change the value of <reentrant> tag in META-INF/ejb-jar.xml from ''False''
to ''false''.
+ Change the value of <reentrant> tag in META-INF/ejb-jar.xml from ''False'' to
''false''.
The affected files are:
@@ -106,13 +106,13 @@
Note: this is an optional task as upon deployment this attribute is
transparently upgraded. For the records, the supported values of the
''reentrant'' element was either ''True'' or ''False''. Since 2.1, these values
must be either ''true'' or ''false''.
- 1. Change the value of <ejb-relation-name> tag in META-INF/ejb-jar.xml from
the empty string to a unique one within relationships.
+Change the value of <ejb-relation-name> tag in META-INF/ejb-jar.xml from the
empty string to a unique one within relationships.
- The affected files are:
+The affected files are:
* customer-ejb.jar
- For each EJB jar listed above do the following:
+For each EJB jar listed above do the following:
{{{
jar -xf <ejb-jar> META-INF/ejb-jar.xml
@@ -120,13 +120,13 @@
jar -uf <ejb-jar> META-INF/ejb-jar.xml
}}}
- 1. Change the position of <env-entry-type> tag in WEB-INF/web.xml so that it
occurs between <env-entry-name> and <env-entry-value>.
+Change the position of <env-entry-type> tag in WEB-INF/web.xml so that it
occurs between <env-entry-name> and <env-entry-value>.
- The affected files are:
+The affected files are:
* petstore.war
- For each WAR listed above do the following:
+For each WAR listed above do the following:
{{{
jar -xf <war> WEB-INF/web.xml
@@ -134,7 +134,7 @@
jar -uf <war> WEB-INF/web.xml
}}}
- The sample stanza looks like:
+The sample stanza looks like:
{{{
<env-entry>
@@ -147,7 +147,7 @@
Note: this is an optional task as elements of Deployment Descriptors are
transparently sorted upon deployment. This is part of the upgrade process from
''.dtd'' to ''.xsd''.
- 1. Create {{{WEB-INF/geronimo-jetty.xml}}}:
+Create {{{WEB-INF/geronimo-jetty.xml}}}:
{{{
<?xml version="1.0" encoding="UTF-8"?>
@@ -160,17 +160,17 @@
</web-app>
}}}
- and add it to petstore.war using the following command:
+and add it to petstore.war using the following command:
{{{
jar -uvf petstore.war WEB-INF/geronimo-jetty.xml
}}}
- Once it's done, delete WEB-INF directory.
+Once it's done, delete WEB-INF directory.
Note: this is an optional task as a ''geronimo-jetty.xml'' DD is transparently
created upon deployment.
- 1. jar up /petstore/ear directory.
+ jar up /petstore/ear directory.
{{{
jar -cf ../petstore.ear *
@@ -185,14 +185,14 @@
cd /geronimo/target/geronimo-1.0-SNAPSHOT
}}}
- 1. Create ''repository/petstore/jars'' directory underneath the home
directory of Geronimo and copy the ''servicelocator.jar'' jar to it.
+ 2. Create ''repository/petstore/jars'' directory underneath the home
directory of Geronimo and copy the ''servicelocator.jar'' jar to it.
{{{
mkdir repository/petstore/jars
cp /petstore/ear/servicelocator.jar repository/petstore/jars
}}}
- 1. Run the deploy tool (i.e. a executable jar)
+ 3. Run the deploy tool (i.e. a executable jar)
NOTE: It's done on Cygwin mounted directory /petstore so replace the magical
{{{cygpath --windows /petstore/petstore.ear}}} with the path to where PetStore
is.
@@ -284,6 +284,14 @@
<!----------------------------------------------------------------->
</ejb-ref>
}}}
+
+'''NOTE'''
+
+[David Blevins in a post to [EMAIL PROTECTED] on 2004-10-27]:
+(...) ''we shouldn't need the ejb-link section anymore as Geronimo
+will try and match the home and remote interfaces up with an ejb
+defined in the jar. This works fine unless there are two or more ejbs
+sharing the same interfaces.''
== You need to get ride of the Japanish screen definitions ... ==
