You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2014/09/08 21:39:28 UTC
[jira] [Resolved] (XMLSCHEMA-34) Attach Schema Target Namespace to
XmlSchemaAny
[ https://issues.apache.org/jira/browse/XMLSCHEMA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved XMLSCHEMA-34.
----------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
Patch applied!
Thanks!
> 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
> Assignee: Daniel Kulp
> 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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org