[
https://issues.apache.org/jira/browse/CXF-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614965#comment-14614965
]
Sergey Beryozkin commented on CXF-6481:
---------------------------------------
I spent some time on Friday and reproduced this issue with Karaf, CXF 3.1.1. It
does work in a plain servlet container, and it was obvious it was somehow OSGI
related. I poked a bit today and I see that CXF rt-transports-http-jetty has an
empty Blueprint JettyServerEngineParser implementation, i.e, an httpj:engine
element is ignored, unless I'm missing something.
And the way to configure an individual engine is to use OSGI Config manager to
set up a "org.apache.cxf.http.jetty" process, see
https://github.com/apache/cxf/blob/master/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/osgi/HTTPJettyTransportActivator.java
So I guess it makes it obvious now why no session is enabled when an
httpj:engine is setup in a blueprint context.
Generally speaking using an OSGI HttpService is indeed should be preferred, and
avoid setting up the endpoints with the absolute HTTP addresses in contexts;
that said, it seems like we should still support httpj:engine if they are set
directly in the context ?
Dan, what do you think ?
Cheers, Sergey
> Jetty HTTPJ session manager configuration is not effective
> ----------------------------------------------------------
>
> Key: CXF-6481
> URL: https://issues.apache.org/jira/browse/CXF-6481
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Reporter: Sergey Beryozkin
> Fix For: 3.1.2
>
> Attachments: camel-context.xml, cxf-httpj-test.zip
>
>
> It appears a session manager is not available if activated from the httpj
> configuration starting from Jetty 8
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
