You need more info, and hence an openejb-jar section in your plan, for
mdbs, cmp mapping, corba, and usually ejb web services.
Packing the vendor specific plan in the application is not really
recommended with j2ee 1.4: for an ear usually it is clearer to have a
single external plan with a section for each ejb module, or for a
standalone ejb module an external plan following the openejb-jar.xsd.
Some people have talked about writing an xdoclet 1 plugin but AFAIK
there is nothing available yet.
david jencks
On Jul 18, 2005, at 12:40 PM, Bruce Snyder wrote:
On 7/16/05, Nicholas Irving <nirving-PXlglK8T5uaakBO8gow8eQ@xxxxxxxxxxxxxxxx>
wrote:
I am trying the WTP from eclipse, but that is not complete and only
performs
the basics, i.e does not auto generate the openejb-jar.xml file, but
does
the ejb-jar.xml through xdoclets. So I thought I would try the maven
approach, as this is a technology I am learning as I am in the
process of
porting a large number of ant files for another project. I have
figured out
the process for generating all the necessary wars, jars and ears, but
not
found a way to generate the openejb-jar file, other than using ant,
but
since I cannot find any documentation of how to use the ant version I
thought I would ask around to see if anybody has done anything
similair.
I may be wrong, but IIRC, as long as the EJB jar file is spec
compliant (i.e., contains an ejb-jar.xml), the Geronimo J2EE deployer
will handle it. Please, someone correct me if I'm wrong.
Bruce
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
| 