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
When adding a second Document element to a MsgHead element defined in the following schema:
Document
MsgHead
<element name="MsgHead"> <complexType> <sequence> <element ref="mh:MsgInfo"/> <choice> <element ref="mh:Document" maxOccurs="unbounded"/> <element ref="mh:PatientReport" maxOccurs="unbounded"> <annotation> <documentation>xxx</documentation> </annotation> </element> </choice> <element ref="ds:Signature" minOccurs="0"/> </sequence> </complexType> </element>
the previous entry is removed.
This is happening in .\LinqToXsdCore\XObjectsCore\API\ChoiceContentModelEntity.cs when a call is made to this.RemoveChoices (line 20).
.\LinqToXsdCore\XObjectsCore\API\ChoiceContentModelEntity.cs
this.RemoveChoices
The maxOccurs="unbounded" does not seem to be respected.
maxOccurs="unbounded"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When adding a second
Document
element to aMsgHead
element defined in the following schema:the previous entry is removed.
This is happening in
.\LinqToXsdCore\XObjectsCore\API\ChoiceContentModelEntity.cs
when a call is made tothis.RemoveChoices
(line 20).The
maxOccurs="unbounded"
does not seem to be respected.The text was updated successfully, but these errors were encountered: