[
https://issues.apache.org/jira/browse/ARIES-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156942#comment-13156942
]
Aki Yoshida commented on ARIES-626:
-----------------------------------
Hi Dan,
I found out the reason why the one-liner fix (i.e. part 1 fix) was working for
0.3.x but not in 0.4.1-SNAPSHOT.
Unlike in 0.3.x, the 0.4.1-SNAPSHOT version uses its own LRResourceResolver and
this is returning a schema resource per namespace.
This is not working when you have schema "includes" because you have a single
namespace trying to load several schema resources.
I added this handling by checking whether systemId is relative and if so,
transforming it relative to the resource path. I am attaching this patch. Could
you check the patch?
I think the whole thing could have be done simpler using for the cases when
baseURI is already a non remote URI. But for now, I think it's okay.
regards, aki
> 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
> Attachments: relpath-patch2.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
