This sounds like <antlib> descriptor...
This is why I keep on saying that we should provide a real good descriptor
and not just property files.
Run the build in proposal/xdocs and let me know what you think. Feedback being begged for!!!! :)
Certainly what you have is good, and perhaps something you'd want to have even if you had this descriptor stuff there too, just in case a task library is not using an official deployment descriptor.
We probably do not want users having the explicitly describe every attribute
of a task or datatype, I guess introspection or some other mechanism should be used for that.
Well, this is where XDoclet comes into play. I'm envisioning an out-of-the-box XDoclet installation being used to generate these descriptors. I've already gotten in into XDoclet's CVS, so the next release build of it will include what I've done so far.
XDoclet would automate the generation of the descriptors, but they could be written by hand if so desired. But XDoclet does the "introspection" thing for you.
Erik
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
