A wise old hermit known only as Ara Abrahamian <[EMAIL PROTECTED]> once
said:
> 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).
> 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...
Andrew.
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel
