[
https://issues.apache.org/jira/browse/CXF-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278984#comment-14278984
]
Sergey Beryozkin edited comment on CXF-6196 at 1/16/15 1:36 PM:
----------------------------------------------------------------
Note CXFBlueprintServlet has been tested with blueprint.webosgi with all of CXF
Blueprint NamespaceHandlers (cxf:, jaxrs: namespace handlers) loaded
sucessfully.
Alex Telesh has confirmed CXFBlueprintServlet works with blueprint.noosgi and
blueprint.web if the Blueprint context uses CXF beans directly (example,
JAXRSServerFactoryBean instead of jaxrs:server).
Therefore this issue is indeed down to getting CXF Blueprint NamespaceHandlers
registered somehow with the blueprint.noosgi BlueprintContainerImpl
was (Author: sergey_beryozkin):
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)
