> 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 would you want out of this? or rather, what does .NET offer? is it an API, or specifically XML that is 'exported'? is ut just reflection that is done at compile time? cheers dim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
