We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having this part of xsd:
<xsd:element name="EMAILS"> <xsd:complexType> <xsd:sequence maxOccurs="unbounded"> <xsd:element ref="EMAIL"/> <xsd:element ref="PUBLIC_KEY" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element>
my problem currently is about <xsd:sequence maxOccurs="unbounded">
<xsd:sequence maxOccurs="unbounded">
because of this, wouldn't that make this valid?
<EMAILS> <EMAIL>A</EMAIL> <PUBLIC_KEY>K1A</PUBLIC_KEY> <EMAIL>B</EMAIL> <PUBLIC_KEY>K1B</PUBLIC_KEY> </EMAILS>
and wouldn't that cause problems when serializing, and de-serializing? because currently, it would be serialized as this which isn't valid:
<EMAILS> <EMAIL>A</EMAIL> <EMAIL>B</EMAIL> <PUBLIC_KEY>K1A</PUBLIC_KEY> <PUBLIC_KEY>K1B</PUBLIC_KEY> </EMAILS>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Having this part of xsd:
my problem currently is about
<xsd:sequence maxOccurs="unbounded">
because of this, wouldn't that make this valid?
and wouldn't that cause problems when serializing, and de-serializing?
because currently, it would be serialized as this which isn't valid:
The text was updated successfully, but these errors were encountered: