In case of strict, all elements must be present in the SchemaBinding.
In case of lax, if element binding is found in the SchemaBinding then it
is used. If not then
- if there is unresolvedElementHandler set on the WildcardBinding then
it will be used to process the element
- if unresolvedElementHandler is null then the element will be skipped.
Scott M Stark wrote:
So how does this:
<xs:any minOccurs="0" maxOccurs="unbounded" processContents="lax"/>
compare to the previous:
<xs:any minOccurs="0" maxOccurs="unbounded" />
which should be processContents="strict"?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Alexey Loubyansky
Sent: Monday, March 06, 2006 3:27 AM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] minOccurs=0 not being used
It's fixed now. Thanks.
Scott M Stark wrote:
http://jira.jboss.com/jira/browse/JBXB-56 is an issue that
describes a
simple testcase in head that shows this behavior.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
