I'm running the standard <ejbjar> and <weblogic> tasks. IOW?
I have weblogic.jar and j2ee12.jar in my classpath for the build, but those jars aren't in the ANT classpath. I found that if I set a CLASSPATH env var, and put those two jars in it, everything works fine. No network connection needed. Can I update ANT's classpath from within the build.xml file? Or is there another way to say "look within the weblogic.jar file for your dtds" even if the dtd mentioned in the deployment descriptors don't have the same name as those within the two jars I mentioned above? -----Original Message----- From: Conor MacNeill [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 8:21 PM To: Ant Users List Subject: Re: EJBC question... On Tue, 9 Sep 2003 07:46 am, Ciramella, EJ wrote: > Ok, I'm having a crisis with a weblogic ejbc task. > > If our network has an issue with connecting to Sun's or Bea's site, the > build hangs and then never completes. This only happens for WL 6.1 > ejbc-ing. For WL5.1, I can unplug my network cable and things work fine. > What's so different between the two that I can't do the same thing for > WL6.1 ejb building? If I create a classpath environment variable and put > in the j2ee12.jar and the weblogic.jar files, things work fine with no > network connection. > > Any suggestions? Can you tell us what Ant task you are running to get this problem? I presume it is <java> and you are directly invoking weblogic.ejbc. Both weblogic.ejbc and Ant's <ejbjar> task try to find DTDs locally rather than having to go to the net to get them. IOW, they supply an entity resolver to resolve the DTDs. weblogic.ejbc maps the required DTDs to resources on the classpath. <ejbjar> also knows about these DTDs but lets you map arbitrary public IDs to files or resources that you specify with the <dtd> tag. This is similar to <xmlcatalog> but <ejbjar> does not use xmlcatalog instances as yet. Conor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
