cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-6196) Investigate how CXFBlueprintServlet can work with blueprint-no-osgi and blueprint.web
Date Wed, 20 May 2015 13:37:00 GMT

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

Sergey Beryozkin resolved CXF-6196.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.1.1
         Assignee: Sergey Beryozkin

> Investigate how CXFBlueprintServlet can work with blueprint-no-osgi and blueprint.web

> --------------------------------------------------------------------------------------
>
>                 Key: CXF-6196
>                 URL: https://issues.apache.org/jira/browse/CXF-6196
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>             Fix For: 3.1.1
>
>
> Aries Blueprint No Osgi module does not support custom namespaces. Most likely a blueprint.web
module should be updated to auto-discover custom NamespaceHandler on the classpath, but it
can be tricky and besides Aries NamespaceHandler does not even report what namespaces it supports.
A hack at the CXF level, possibly with some fixes at the Aries level is needed 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message