Donal- I had the same problem for the longest time using 1.4.1 and followed the same steps you took as well with no results.
In the end, upgrading to 1.5 actually rectified the problem altogether as Conot et al made some significant changes (and improvements) in the behavior of the EJB tasks. So, my recommendation is to upgrade Ant 1.5. Cheers! Eddie -----Original Message----- From: Donal Quinlan [mailto:[EMAIL PROTECTED]] Sent: Friday, August 30, 2002 12:08 PM To: Ant Users List Subject: <weblogic>, <classpath>, and <wlclasspath> Hi, I'm using Ant 1.4.1 and attempting to use the weblogic task. I get warnings about the home and remote interfaces of a bean on the system classpath. According to the 1.4.1 javadoc I simply need to use <wlclasspath> to set the standard weblogic classes. But whenever I do this and run ant -verbose I get NoClassDefFound exceptions. I only see jar's in the <wlclasspath> in the log output. Anything in <classpath> gets ignored as soon as I start using <wlclasspath>. So what eventually happens is I put all the jars in <wlclasspath> and end up back at square one. Has anybody experienced this before or better yet, know of a solution? Perhaps this is why our buildfile is using the java task to fork weblogic.ejbc. Thanks Donal -- 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]>
