[
https://issues.apache.org/jira/browse/ARIES-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013711#comment-13013711
]
Guillaume Nodet commented on ARIES-626:
---------------------------------------
Why not having the blueprint extender calling
nshandler.getSchemaLocation("http://cxf.apache.org/configuration/beans";)
in such a case ?
This way, each namespace handler could implement its own logic ?
Especially as most of the namespace handlers i've seen use simple (i.e. self
contained) schemas, I'm not really sure that complicating the logic is a good
idea.
Thoughts ?
> 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
