You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Matthieu Riou (JIRA)" <ji...@apache.org> on 2007/11/20 19:28:43 UTC
[jira] Created: (ODE-208) Schemas with several imports for the same
namespace fail to load
Schemas with several imports for the same namespace fail to load
----------------------------------------------------------------
Key: ODE-208
URL: https://issues.apache.org/jira/browse/ODE-208
Project: ODE
Issue Type: Improvement
Components: BPEL Compilation/Parsing
Affects Versions: 1.2
Reporter: Matthieu Riou
Assignee: Matthieu Riou
Fix For: 1.2
When a process relies on a lot of different schemas it oftens happens that 2 different schema files get imported under the same namespace from two different locations:
<xs:import namespace="urn:SMPTE:Groups:MXF" schemaLocation="../groups/s377m_packs.xsd"/>
<xs:import namespace="urn:SMPTE:Groups:MXF" schemaLocation="./s377m_metadata.xsd"/>
Depending on the order of loading Xerces ignores one of the imports as it already know the namespace. Remember in the XSD spec the schema location is just a hint, so parsers discriminate schemas based on the namespace (which also gives some performance improvements as stuff is cached). Strictly, such schemas are none valid but somehow users fail to see it that way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-208) Schemas with several imports for the
same namespace fail to load
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544015 ]
Assaf Arkin commented on ODE-208:
---------------------------------
IMO this should result in an error preventing the process from loading, a warning would be too easily ignored, and loading both schemas could lead to all sort of nasty surprises.
> Schemas with several imports for the same namespace fail to load
> ----------------------------------------------------------------
>
> Key: ODE-208
> URL: https://issues.apache.org/jira/browse/ODE-208
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2
> Reporter: Matthieu Riou
> Assignee: Matthieu Riou
> Fix For: 1.2
>
>
> When a process relies on a lot of different schemas it oftens happens that 2 different schema files get imported under the same namespace from two different locations:
> <xs:import namespace="urn:SMPTE:Groups:MXF" schemaLocation="../groups/s377m_packs.xsd"/>
> <xs:import namespace="urn:SMPTE:Groups:MXF" schemaLocation="./s377m_metadata.xsd"/>
> Depending on the order of loading Xerces ignores one of the imports as it already know the namespace. Remember in the XSD spec the schema location is just a hint, so parsers discriminate schemas based on the namespace (which also gives some performance improvements as stuff is cached). Strictly, such schemas are none valid but somehow users fail to see it that way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-208) Schemas with several imports for the
same namespace fail to load
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou resolved ODE-208.
-------------------------------
Resolution: Fixed
Resolved some time ago.
> Schemas with several imports for the same namespace fail to load
> ----------------------------------------------------------------
>
> Key: ODE-208
> URL: https://issues.apache.org/jira/browse/ODE-208
> Project: ODE
> Issue Type: Improvement
> Components: BPEL Compilation/Parsing
> Affects Versions: 1.2
> Reporter: Matthieu Riou
> Assignee: Matthieu Riou
> Fix For: 1.2
>
>
> When a process relies on a lot of different schemas it oftens happens that 2 different schema files get imported under the same namespace from two different locations:
> <xs:import namespace="urn:SMPTE:Groups:MXF" schemaLocation="../groups/s377m_packs.xsd"/>
> <xs:import namespace="urn:SMPTE:Groups:MXF" schemaLocation="./s377m_metadata.xsd"/>
> Depending on the order of loading Xerces ignores one of the imports as it already know the namespace. Remember in the XSD spec the schema location is just a hint, so parsers discriminate schemas based on the namespace (which also gives some performance improvements as stuff is cached). Strictly, such schemas are none valid but somehow users fail to see it that way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.