I think I can start with the jbossXB mapping and a subset of the existing -service.xml and enhance this gradually? Something like: <bean name="bla" class="org.jboss.bla.Bla"> | <constructor> | <arg type="java.lang.String">value</arg> | ... | </constructor> | | <attribute name="yada">value</attribute> | ... | <demands> ??? | </demands> | ... | <supplies/> | ... | </bean>
1) Do we need to create subclasses of the org.jboss.metadata.pluings.AbstractXXX classes? If yes what's a suitable package for them? 2) What goes in Supplies? 3) Instead of Supplies/Demands wouldn't Provides/Depends be more consistent with what we have now? 4) What are we supposed to store in the AbstractFeatureMetadata map 5) Is the AbstractValueMetadata 'Object getValue()/setValue(Object)' really needed? Wouldn't be better for derived classes to provide a typed version, e.g. 'String getValue()' for StringValueMetadata 6) Do we need an .xsd or .dtd for the parsed xml? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855706#3855706 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855706 ------------------------------------------------------- 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
