I created the following jira issue that I want to discuss how to best achieve here http://jira.jboss.com/jira/browse/JBAS-1461
The problem is that services are still embedding xml parsing of attribute configuration document fragments in the service code itself. The example jboss-service.xml doc in the JBAS-1461 is one step, but its still not ideal since its essentially just moving the xml parsing to the custom org.jboss.test.jmx.complexattrs.JavaBeanObjectModelFactory. That is better than embedding this in the service itself, but I'm sure we have better solutions. In that regard, what is our state of support for: - Parsing a JavaBean with no schema/dtd and property editors for the non-String types - Parsing a JavaBean with a dtd for the attribute document fragment - Parsing a JavaBean with a schema for the attribute document fragment View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866396#3866396 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866396 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
