Here's a message I sent a week or so ago (this is actually the 3rd posting of it):
================================================= I use Ant to build a weblogic ejb.jar file; however, I do not use the ejbjar optional task (or whatever it's called) from Ant. I found the docs for that set of tasks unhelpful; and, if the docs are accurate, the tasks are overly complicated. Here's what I have: 1) An "app.compile" target which builds all my .java sources except the remote, home, and bean-impl classes. These are jarred into an "app.jar" file. 2) An "ejb.compile" target builds the remote, home, and bean-impl classes for all my beans. 3) An "ejb.jar" target uses a <jar> task to put just the .class files from step 2, along with the ejb-jar.xml, weblogic-ejb-jar.xml, etc. into an "ejb.jar" file. 4) An "ejb.ejbc" target uses a <java> task to run ejbc against the .jar file from step 3, explicitly placing the "app.jar" file from step 1 in the classpath. I name the output of that "ejb-depl.jar" to indicate that it's a deployable .jar file. Voila! That's it, and it works perfectly for me every time. I separate out "app.jar" stuff from "ejb.jar" stuff because it prevents the warning about the EJB .class files already being in the classpath. BTW, this is with WebLogic 6.1. ================================================= Donnie >>> [EMAIL PROTECTED] 01/10/02 01:07AM >>> Could you post a snippet of your targets, if they're not proprietary? -----Original Message----- From: Donnie Hale [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 6:03 PM To: Ant Users List Subject: RE: Adding/extending a manifest using <ejbjar> I don't have 75 beans, but I have 6 and build them all with one target (not <ejbjar> - actually 2, one for the vanilla ejb.jar and one to put that into ejbc) and won't have to change that if/when we add more beans. Don't know what to say about the manifest problem. Sorry... Donnie > -----Original Message----- > From: Eddie Bernard [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 7:54 PM > To: '[EMAIL PROTECTED]' > Subject: Adding/extending a manifest using <ejbjar> > > > OK, I've haven't completely given up on using <ejbjar> for my WebLogic 6.1 > project. > > The reason I want to use it is that I have approximately 75 EJBs > that I want > to build and the target I've created that uses <ejbjar> neatly > creates each > EJB with only one target. Using some of the other suggested methods > (which, again, I appreciate the responses) would require me to > have a target > for virutally every bean and even worst add more targets if more beans are > added to the project. > > Now with all tht said, I'm in the process of creating an > Enterprise Archive, > but I'm having a deployment problem -- again unrelated to Ant itself. > However, after reading some BEA white papers and the J2EE > specifications for > Application Deployment, it allows the addition of the name:value pair: > > Class-Path: list-of-jars-separated-by-spaces > > Example: > > Class-Path: lib/my_support_classes.jar > > Now the Ant-related problem... It seems that <ejbjar> extends the > <jar> task > meaning that it inherits the "manifest" attribute. If I use <jar> with my > manifest addition it works just fine. However, with <ejbjar> it > generates a > "near empty" file (actually, it has a set of cr/lf). > > Has anybody else come across this problem or have any ideas what I can do? > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
