The complexity possible in the nesting of bean properties is not evident from the current testcases, and it did not jump out at me that the java configuration of the jbossxb factory supports this. We should define a schema for the xml deployer's supported document syntax. The question to Alexey is the suggested document model going to be drivable from the schema or the schema + a jbossxb/jaxb metadata document?
Ultimately that is the preferred state of affairs as this let's us get past the current fact that the DTDs are at best approximations of the actual xml parsing done via hand-coded java. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870616#3870616 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870616 ------------------------------------------------------- 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
