Re: [Xdoclet-user] webdoclet problems with 1.2.3

[Daniel L. <Dan...@br...>]

I discovered a work-around.  I had been doing

<target ..>
    <taskdef name=3D"webdoclet" ...>
    <webdoclet ...>
    <webdoclet ...>
</target>

But when I did this instead it worked:

<target ..>
    <taskdef name=3D"webdocletA" ...>
    <taskdef name=3D"webdocletB" ...>
    <webdocletA ...>
    <webdocletB ...>
</target>

Also it worked to do 2 different targets, or
one target called multiple times - as long as
there was only one webdoclet call per taskdef.

(a note on my original problem: I discovered if
you used the force flag or touched the files the
second webdoclet call would generate files but it
still generated to the destdir specified by the first
webdoclet call, and the contextparam and taglib
declarations accumulated over both calls.  So lots of
ugly bugs but they all seem to be solved by the above
work-around)

- Dan

> -----Original Message-----
> From: xdo...@li...=20
> [mailto:xdo...@li...] On Behalf=20
> Of Anthony Roy
> Sent: Monday, October 30, 2006 2:35 AM
>=20
> =20
> > > And is there websphere support?  1.2.3 had minimal=20
> > websphere support=20
> > > (it's why we upgraded from 1.2.2), but it would be really=20
> > nice to have=20
> > > good websphere support.
> >=20
> > Websphere what? If you mean EJB, there is not much usable for=20
> > properitary containers.  We still lack of commiters in this=20
> > field ( it happens that nobody of actual commiters has use=20
> > case for it )
>=20
> So is there a workaround for this problem? I encountered the same
> problem on Friday, and now seem to be stuck between a rock and a hard
> place regarding XDoclet:
>=20
> 1) I need to upgrade to XDoclet 1.2.3 in order to fix the=20
> websphere xmi
> file generation.
> 2) But XDoclet 1.2.3 is broken regarding running more than=20
> one webdoclet
> task in an ant build sequence.
> 3) The wisdom is to upgrade to XDoclet2
> 4) But XDoclet2 doesn't have (usable) websphere support.
>=20
> Cheers,
>=20
> --=20
> Anthony Roy
>