The other use of the featuremetadata is to provide metadata to each context. But I need to discuss this with Bill because he has two mechanisms for this:
1) getMetaData(...) 2) resolveAnnotation(...) The annotation approach is obviously superior because it is type checked, but we also need the mechanism to work in java1.4 Use cases, detyped approach: 1) ModelMBean descriptor | <attribute name="Blah">InitialValue | <metadata domain="modelmbean" type="cache-timeout">NEVER</metadata> | </attribute> | 2) Aspect context configuration | <attribute name="Blah">InitialValue | <metadata domain="transaction" type="demarcation">Required</metadata> | <metadata domain="authorization" type="roles">admin</metadata> | </attribute> | NOTE: The above xml is intended to express the idea, not specify how we are actually going to do it/use it. Remember, what we are configuring here using XML with be done programmatically by the other deployers (sar, aop, ejb, etc.). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855750#3855750 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855750 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
