You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/04/08 18:06:12 UTC
[jira] Created: (WSCOMMONS-460) targetNamespace in schema without a
prefixed namespace also defined can cause empty namespace to be overwritten
targetNamespace in schema without a prefixed namespace also defined can cause empty namespace to be overwritten
---------------------------------------------------------------------------------------------------------------
Key: WSCOMMONS-460
URL: https://issues.apache.org/jira/browse/WSCOMMONS-460
Project: WS-Commons
Issue Type: Bug
Components: XmlSchema
Affects Versions: XmlSchema 1.4.4
Reporter: Daniel Kulp
Assignee: Daniel Kulp
Fix For: XmlSchema 1.4.5
If a schema does NOT have a namespace defined that is equal to the targetNamespace, when that schema is written out, the default namespace is reset to the targetNamespace. If the schema already has a default namespace set, then anything using the default ns may no longer be valid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WSCOMMONS-460) targetNamespace in schema without
a prefixed namespace also defined can cause empty namespace to be
overwritten
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved WSCOMMONS-460.
-----------------------------------
Resolution: Fixed
> targetNamespace in schema without a prefixed namespace also defined can cause empty namespace to be overwritten
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WSCOMMONS-460
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-460
> Project: WS-Commons
> Issue Type: Bug
> Components: XmlSchema
> Affects Versions: XmlSchema 1.4.4
> Reporter: Daniel Kulp
> Assignee: Daniel Kulp
> Fix For: XmlSchema 1.4.5
>
>
> If a schema does NOT have a namespace defined that is equal to the targetNamespace, when that schema is written out, the default namespace is reset to the targetNamespace. If the schema already has a default namespace set, then anything using the default ns may no longer be valid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WSCOMMONS-460) targetNamespace in schema without a
prefixed namespace also defined can cause empty namespace to be overwritten
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies updated WSCOMMONS-460:
---------------------------------------
Fix Version/s: XmlSchema 2.0
> targetNamespace in schema without a prefixed namespace also defined can cause empty namespace to be overwritten
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WSCOMMONS-460
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-460
> Project: WS-Commons
> Issue Type: Bug
> Components: XmlSchema
> Affects Versions: XmlSchema 1.4.4
> Reporter: Daniel Kulp
> Assignee: Daniel Kulp
> Fix For: XmlSchema 1.4.5, XmlSchema 2.0
>
>
> If a schema does NOT have a namespace defined that is equal to the targetNamespace, when that schema is written out, the default namespace is reset to the targetNamespace. If the schema already has a default namespace set, then anything using the default ns may no longer be valid.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.