geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From geronimo-...@incubator.apache.org
Subject [Apache Geronimo Wiki] Updated: PetStore
Date Sat, 07 Aug 2004 12:19:19 GMT
   Date: 2004-08-07T05:19:19
   Editor: GiannyDamour <gdamour@apache.org>
   Wiki: Apache Geronimo Wiki
   Page: PetStore
   URL: http://wiki.apache.org/geronimo/PetStore

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -32,6 +32,9 @@
 <application xmlns="http://java.sun.com/xml/ns/j2ee">
 }}}
 
+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}}}:
 
  {{{
@@ -46,6 +49,8 @@
 </application>
 }}}
 
+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}}}:
 
  {{{
@@ -98,6 +103,8 @@
 jar -uf <ejb-jar> META-INF/ejb-jar.xml
 }}}
 
+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.
 
  The affected files are:
@@ -137,6 +144,8 @@
   </env-entry>
 }}}
 
+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}}}:
 
  {{{
@@ -158,11 +167,16 @@
 
  Once it's done, delete WEB-INF directory.
 
- 1. Only RARs and WARs are currently supported in an unpacked EAR, so jar up /petstore/ear
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 -cf ../petstore.ear *
 }}}
+
+Note: Geronimo supports deployment of unpacked J2EE modules. This is intended to remove the
 development overhead of packaging your modules. Actually, this is not an overhead "as such"
as the task is pretty simple and not really time consuming. Having said that, the "ultimate"
goal is to support development against unpacked module  and especially "in place".
+In the current case, you can unpack the ''ear'' and its nested modules. Then, you just have
to update the ''application.xml'' file with the directory in which you have unpacked the nested
modules.
 
  1. Go to the home directory of Geronimo (i.e. ''/geronimo/target/geronimo-1.0-SNAPSHOT''
assuming that as above it's decided to place Geronimo sources to /geronimo directory).
 

Mime
View raw message