[
https://issues.apache.org/jira/browse/ARIES-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029862#comment-13029862
]
Valentin Mahrwald commented on ARIES-626:
-----------------------------------------
Calling nshandler.getSchemaLocation(...) for missing external schemas would be
nice in not complicating the logic. Trying this out in code I have found two
snags though (that may be due to my limited understanding):
- Without adding the namespaces to the NamespaceHandler namespaces service
property (or adding a new property) the code has to query every namespace
handler to see if it can supply a schema for a given URI.
- xsd:include would only work if the schemaLocation is treated as a schema URI,
which seems like a subversion of the API to me.
> Aries blueprint namaspace handler schema with includes
> ------------------------------------------------------
>
> Key: ARIES-626
> URL: https://issues.apache.org/jira/browse/ARIES-626
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: 0.4
> Reporter: Edstrom Johan
>
> If you have a NamespaceHandler implementation where the schema contains
> xsd:includes, the schema will fail to resolve if you do not have connectivity.
> There is also no way to attach a CatalogResolver or xml-resolver.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
