The last six months I have been developing a container that extracts all metadata from attributes/javadoc tags (similar to commons-attributes, dot.net attributes or the various interceptor frameworks). So it would end up being specified by something like
/** * @fortress.lifecycle name="ThreadSafe" */ public class MyComponent {}
Sounds cool.
What about specifying a different comment namespace rather than the javadoc one and use an xml syntax instead of the soon-to-be-too-simple-for-the-purpose javadoc one?
/*+ | <avalon:metadata xmlns="http://apache.org/avalon/matadata/1.0";> | <avalon:lifecycle name="ThreadSafe"/> | </avalon:metadata> +*/
That gives you:
1) complete Soc between javadoc comments
2) complete SoC between code and attributes
3) versioning of the metadata schema (thru namespace URI identify) that will ease transition in the future
4) complete visual separation between javadocs and object metadata
5) easier to automate in editors (due to #5)
what do you think?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
