[
https://issues.apache.org/jira/browse/CXF-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773133#comment-15773133
]
ASF GitHub Bot commented on CXF-7183:
-------------------------------------
GitHub user grgrzybek opened a pull request:
https://github.com/apache/cxf/pull/217
[CXF-7183] Fix systests/jaxrs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/grgrzybek/cxf master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/217.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #217
----
commit e7bb0c09bfb312f01b0b48c3fe4dfa0add1a55d1
Author: Grzegorz Grzybek <[email protected]>
Date: 2016-12-23T15:43:14Z
[CXF-7183] Fix systests/jaxrs
----
> CXF Blueprint namespace don't work well with blueprint-core 1.7.x
> -----------------------------------------------------------------
>
> Key: CXF-7183
> URL: https://issues.apache.org/jira/browse/CXF-7183
> Project: CXF
> Issue Type: Bug
> Components: OSGi
> Affects Versions: 3.1.9, 3.0.12
> Reporter: Grzegorz Grzybek
> Assignee: Guillaume Nodet
> Fix For: 3.2.0, 3.1.10, 3.0.13
>
>
> Aries blueprint-core 1.7.1 changes (improves) the way namespace handlers
> (classes implementing {{org.apache.aries.blueprint.NamespaceHandler}}
> interface) resolve namespaces to URIs.
> The problem is when XSD behind a handler imports other XSDs that may be
> resolved by other handlers.
> Around Aries blueprint-core 1.4.x, imported XSDs where looked up in all
> currently registered handlers, but this was prone to race conditions, because
> handler that could resolve given imported XSD might've not been registered
> yet.
> The clean solution is to delegate at code level to correct handler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
