Hi,
One point, we use local copies of out DTDs to speed up deployment as well.
So the DTD location in the XML file is tagged with a filter @dtd.dir@ which
is substituted during our build process.
Upshot? I don't need to use the <dtd> element, our stuff deploys quicker and
I can quickly run the xmlvalidate task to syntax check the DD's before I get
that annoying WLS 'Unable to deploy' message half an hour later....
Bye,
Les
P.S. I'm still touting for ideas from other Ant EJBer's for a DrDobbs
article covering all of this stuff.....
> -----Original Message-----
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]]
> Sent: 02 May 2001 10:45
> To: [EMAIL PROTECTED]
> Subject: Re: Anyone got the <dtd> element for <ejbjar> to work with
> weblogic 6?
>
>
> Andrew,
>
> From: "Andrew Thompson" <[EMAIL PROTECTED]>
> > Yeah, I had a file path originally, but I was
> experimenting. It would be
> > good if the documentation, if not the syntax could reflect what was
> expected
> > where. eg, Name / Required / Type in those handy tables. I
> know it says
> its
> > a "file" but that's still ambiguous enough. Its like most
> things, when
> its
> > working, you don't care how good the docs are (overall I'd
> say they're
> > pretty good) when it isn't you need all the help you can get :)
> >
> > Anyway, I think I figured out what's up:
>
> This was a bug which has been fixed after 1.3 was released. If you are
> trying EJB2.0 stuff it is worth getting a snapshot of the optional jar
> since it will call the correct ejbc compiler. (ejbc20) for 2.0 jars.
>
> I'm about to post a new optional jar which you may want to grab.
>
> I think the documentation is OK especially in light of the
> bug fix. If you
> still think it needs to be updated, you could submit a patch
> with improved
> wording.
>
> Conor
>
>
>
