cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CXF-7183) CXF Blueprint namespace don't work well with blueprint-core 1.7.x
Date Mon, 27 Feb 2017 15:08:47 GMT

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

Colm O hEigeartaigh closed CXF-7183.
------------------------------------

> 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.15#6346)

Mime
View raw message