"[EMAIL PROTECTED]" wrote : 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.
It depends on what API you looked at. For the latest API (sunday package), I would be interested to see a use-case that is not supported. "[EMAIL PROTECTED]" wrote : 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? The aim is to have as little binding customizations (ideally to not have at all) as possible. This is the responsibility of the default binding rules. The real (e.g. Adrian's) world is full of exceptions. You could minimize customizations when you write your Java object model by keeping in mind the XML schema the Java model is going to be bound to. I am actually not suggesting this approach and am sure that that's not what you want. Let's create a real testcase and I'll work on it. You could create an XML and Java object model and I'll then take care of the binding. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870742#3870742 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870742 ------------------------------------------------------- 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
