cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7183) CXF Blueprint namespace don't work well with blueprint-core 1.7.x
Date Thu, 15 Dec 2016 09:22:59 GMT

    [ https://issues.apache.org/jira/browse/CXF-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750881#comment-15750881
] 

ASF GitHub Bot commented on CXF-7183:
-------------------------------------

GitHub user grgrzybek opened a pull request:

    https://github.com/apache/cxf/pull/215

    [CXF-7183] Adjust CXF namespace handlers to aries-blueprint-core 1.7.x

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/grgrzybek/cxf master-CXF-7183

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cxf/pull/215.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 #215
    
----
commit 0344b6bc0d1e61a3d3b5194f5ae3ebcdf62e8d56
Author: Grzegorz Grzybek <gr.grzybek@gmail.com>
Date:   2016-12-15T08:33:15Z

    [CXF-7183] Adjust CXF namespace handlers to aries-blueprint-core 1.7.x

----


> 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
>
> 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)

Mime
View raw message