You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2016/12/15 10:24:59 UTC

[jira] [Assigned] (CXF-7183) CXF Blueprint namespace don't work well with blueprint-core 1.7.x

     [ https://issues.apache.org/jira/browse/CXF-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet reassigned CXF-7183:
------------------------------------

    Assignee: Guillaume Nodet

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