I was unable to get past the warnings in my ejbjar task unfortunately. In fact, I also use the nowarn flag and it does not remove the warnings. To get around this problem before we used the ejbjar task, we actually moved code around in different jars, so that we pointed the ejbc classpath in the right place... It was a hassle and while the warnings from ejbjar are annoying, they are not a failure. We're just living with that problem for now... If anyone has a good solution - that doesn't require me to move class files and jar files around, I'm all ears.
-Ryan -----Original Message----- From: Jepp, Daniel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 11, 2001 10:23 AM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: RE: ejbjar and issues with class loading? Hi Ryan, I just wondered if you managed to solve the Ant ejbjar problem that you had? I am surrering from exactly the same problem Heres my target: <target name="ejb" description="Builds the EJB's" depends="compile"> <ejbjar srcdir="${classes}" descriptordir="${src}" destdir="${build}" flatdestdir="true"> <include name="**/*-ejb-jar.xml"/> <exclude name="**/weblogic*.xml"/> <weblogic destdir="${build}"> <classpath refid="classpath"/> </weblogic> <dtd publicId="-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" location="ejb-jar_2_0.dtd"/> <dtd publicId="-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" location="weblogic-ejb-jar.dtd"/> </ejbjar> </target> where the classpath i have set up as a property is simply all the compiled source, plus the j2ee.jar and weblogic.jar. This works fine but i get the warnings you mentioned with regard to having the ejb interfaces on the classpath. I have tried using the <wlclasspath> element and just placing the weblogic.jar on it but then i get the 'could not load superclases' error. I have even tried the following classpath to pass to <wlclasspath> <path id="ejbcClasspath"> <path refid="libs"/> <fileset dir="${classes}"> <include name="**/*.*"/> <exclude name="${ejb}/**.*"/> </fileset> </path> which hopefully is all the source with the exception of the ejb packages (which of course contain the ejb interfaces that ejbc complains about) but this was no help either as any dependencies cannot the be found.... This is my last resort before i send the 'nowarn' flag to ejbc.... Any help much appreciated Dan Dan Jepp Dresdner Kleinwort Wasserstein *email: [EMAIL PROTECTED] * Voice: +44 (0) 20 7475 1005 ---------------------------------------------------------------------- If you have received this e-mail in error or wish to read our e-mail disclaimer statement and monitoring policy, please refer to http://www.drkw.com/disc/email/ or contact the sender. ---------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
