> > Maybe the best thing to do is put toplink/soap stuff in ejbdoclet
and be
> > more tolerant in ejbdoclet's impl. I mean smartly include <session/>
if
> > <deploymentdescriptor/> specified, otherwise don't. So, it'll be
> > possible for user to define something like this:
> > <ejbdoclet>
> > <toplink/>
> > </ejbdoclet>
>
> Remind me again, why is the session task mandatory anyway when the
entity
> bean ones aren't? If I want to generate a package of only BMP beans,
the
> session subtask is just wasting time. I'd have thought either they
should
> all be mandatory (since there are other ways to stop the various
subtasks
> doing anything for particular classes), or all optional (particularly
if
> there's others being added like Soap and Toplink, which probably
should be
> optional).
You're right. Essential ejb sub-tasks should be mandatory. They won't
slow down the build really. Vendor-specific stuff, including toplink and
apachesoap should be optional. People will normally use ejbdoclet for
ejb and toplink and soap, not toplink and soap without ejbdoclet when
they have ejbs. Anyway, even if toplink can be used without ejbs but the
norm is to use it with ejbs or in app servers, so I think ejbdoclet is a
safe home for it :-)
> > Anyway, maybe the best thing to do is a xdoclet task with
> > ejbdoclet/webdoclet/classdoclet elements?! No, it'll be ugly :-)
>
> But you'd only need to document one version of the Ant taskdef
entry...
Yeah but imagine this:
<xdoclet blabal=""....>
<ejbdoclet>
<entitypk/>
...
</ejbdoclet>
<webdoclet>
<deploymentdescriptor>
<contextparam dfsdfsd>
</webdoclet>
And so on. It'll be too much nested. Webdoclet/ejbdoclet is a more
layered approach.
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel
