[jboss-dev-forums] [Design of JBossXB] - Re: Referencing the bean-deployer namespace from a custom me

[david.lloyd@jboss.com]

"alex.loubyansky at jboss.com" wrote : anonymous wrote : So maybe it's treating the outer choice as maxOccurs=1 or something?
  | 
  | Yes, of course. And IMO that's how it should be. Otherwise, the structures of the bound components/types in Java and XSD are inconsistent. Why don't you use a sequence? What problem does it cause in this case?

The problem is that it prevents the user from putting the element in any order.  In the schema, all the elements listed in this class are in one "choice"; the only reason they're grouped as they are here is because that's how they're mapped in terms of Java types.  So the effect I'm really going for is to have XB take all the XmlElement instances in the class and make one big "choice" out of it with maxOccurs=unbounded.

anonymous wrote : I have my root element set up to be propOrder={} and modelgroup=CHOICE.
If you bind to a choice then propOrder should be removed. propOrder={} is supposed to bind to all.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242733#4242733

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242733