ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Narayanan, Gopalakrishnan" <gna...@exchange.ml.com>
Subject RE: Making 20 ejb jars....
Date Fri, 08 Nov 2002 22:08:13 GMT
This seems to be a classpath problem.
Try setting the required classes/libraries in classpath of ejb-jar.
ejb-jar will find the deployment descriptors as long u give the root dir in descriptordir.The
xml files must be named as BeanName-ejb-jar.xml.

-----Original Message-----
From: Ciramella, E.J. [mailto:EJ.Ciramella@workscape.com]
Sent: Friday, November 08, 2002 4:59 PM
To: Ant Users List
Subject: RE: Making 20 ejb jars....


Ok let me get this straight, this task won't find the ejb-jar.xml files if they are in source/com/company/product/ejb/package/metainf,
but if all the xml files are named after the package, and all put
together in one directory, this is supposed to work?

I get "could not load.... for super class check..."  what did I miss?

-----Original Message-----
From: Narayanan, Gopalakrishnan [mailto:gnaray@exchange.ml.com]
Sent: Thursday, November 07, 2002 2:17 PM
To: 'Ant Users List'
Subject: RE: Making 20 ejb jars....


Try putting all the deployment-descriptors under a root directory(ofcourse with the ejb-jar
naming convention) and invoke ejb-jar.
ejb-jar task is supposed to automatically discover classes(as long as you provide a source
root )and build ejb-jars according to the descriptors found.
By this way, u can add as many beans as you want but u donot have to modify the build file.

-----Original Message-----
From: Ciramella, E.J. [mailto:EJ.Ciramella@workscape.com]
Sent: Thursday, November 07, 2002 2:12 PM
To: ant-user@jakarta.apache.org
Subject: Making 20 ejb jars....


Has anyone had to jar up multiple ( > 20) ejb's into individual jars?  Currently, we have
a jar task in a separate build, and then we call that task from within another build file
(one ant task for
each ejb, passing in the name of each ejb).  That's right, at each stage of the build process
(there are three), the hard coded list of ejb's grows (and they are slightly redundant).

Any clever ways to avoid this and build ejb jars sort of "blindly", without hard coding the
ejb's into the ant scripts?


--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>



--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>



--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message