Dennis Sosnoski <[EMAIL PROTECTED]> writes: > You're assuming that the <choice> has minOccurs='1', but it's > equally valid for a choice to have minOccurs='0' (or maxOccurs > 1, > but that equates to a collection).
Oh, you're right. I never considered a choice particle with minOccurs=0, but that could make sense for some documents. > I suppose what I should really do is see if the binding <structure> > with choice='true' is optional or required, and if it's optional use > the current handling but if required throw an exception when no > element matching the <choice> values is found. Yes, that sounds like the right behavior. > So the small issue is not as small as it first looked, but I'll at > least look into implementing this part of the choice handling to do > what users would expect. Thank you for following up. In the meantime, I'm working around the problem, but would like to get it solved before it's time to actually deploy the system. -- Steven E. Harris ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
