[
https://issues.apache.org/jira/browse/XMLSCHEMA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated XMLSCHEMA-34:
---------------------------------
Fix Version/s: 2.1.1
> Attach Schema Target Namespace to XmlSchemaAny
> ----------------------------------------------
>
> Key: XMLSCHEMA-34
> URL: https://issues.apache.org/jira/browse/XMLSCHEMA-34
> Project: XmlSchema
> Issue Type: Improvement
> Affects Versions: 2.1.0
> Reporter: Michael Pigott
> Priority: Minor
> Labels: PatchAvailable
> Fix For: 2.1.1
>
> Attachments: diff_any.zip
>
>
> While I was working on AVRO-457, I found it was difficult to determine the
> XML Schema's target namespace when I encountered an XmlSchemaAny. This is
> needed because the XmlSchemaAny's namespace could be ##targetNamespace (the
> element must match the target namespace) or ##other (the element must be in
> any namespace other than the target namespace), so it was difficult to
> confirm whether the element matched the wildcard.
> This change adds a "targetNamespace" field to XmlSchemaAny, and has
> XmlSchemaBuilder attach XmlSchema.getLogicalTargetNamespace() to it. I
> believe that is the best fit.
> Thanks!
> Mike
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
