> It will also be nice that EjbDocletTask itself would be/have a
container
> of subtasks, etc...
> This will avoid to change it when adding new vendors ;)
Not possible currently because of the way Ant's introspection works.
Erik came up with a good solution for this limitation for Ant2, but Pete
didn't like it :o) I'm sure we'll anyway have this feature of being
ultra-dynamic in Ant2.
> EjbDocletTask extends DocletTask extends Task (the Ant one)
> EjbDocletTask has ONE SubTaskContainer called
> EjbDocletSubTask that
> has many SubTaskContainer (extends SubTask) : jboss,
> orion, ...
> and many SubTask : session, entitycmp, ...
> JBossSubTask extends SubTaskContainer
> JawsSubTask extends SubTask
> JBossSubTask has many SubTask : jaws, jbosscmp, jboss
Looks good but again we hit the wall of Ant. What you're describing
means:
<ejbdoclet>
<subtaskcontainer>
<session/>
<blabla/>
</subtaskcontainer>
</ejbdoclet>
So to Ant can configure the subtasks this way.
Of course your solution is great, we don't want to have EjbDocletTask
and AntlessEjbDocletTask, etc. I think the best solution for now is to
have an GenericEjbDocletTask which is not dependent on Ant and derives
from GenericDocletTask (or whatever you call it) and define
EjbDocletTask which derives from GenericDocletTask but works with Ant
and then maybe a CommandLineDocletTask or stuff like that. Anyway, I
know it's ugly :o) that's why we need a better more pluggable
introspection code in Ant.
Ara.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
