You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2015/01/15 18:29:34 UTC

[jira] [Commented] (CXF-6196) Investigate how CXFBlueprintServlet can work with blueprint-no-osgi and blueprint.web

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

Sergey Beryozkin commented on CXF-6196:
---------------------------------------

Note CXFBlueprintServlet currently works with blueprint.webosgi only.

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