----- Original Message -----
> >From the points there, it is exactly XDoclet isn't it.... afaik, no other
'code annotation tools' provide the framework that XDoclet
> does - includeing the 'Definition of a runtime delivery format for
metadata and of runtime APIs so that tools and libraries can
> accesss metadata information at deployment time and at runtime'.
Speaking of which.... it would be fairly straightforward to have XDoclet
create an XML file (or some other metadata format, perhaps even serialized
objects generated from post processing of the XML?) for each class processed
and create a utility to make all that information available to the class at
runtime.
Anyone ever considered this? Done it?
Its not really necessary, generally speaking, since XDoclet builds the
pieces we need at runtime anyhow, except in a more narrow/specific way. A
generalized mechanism could be an interesting addition, and beat this JSR
release for sure, and compete head-to-head with .NET's capabilities.
What kinds of suggestions do folks have for how such a mechanism would work?
Via Castor maybe (? I don't know Castor's details)?
Erik
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
