[
https://issues.apache.org/jira/browse/CXF-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616713#comment-14616713
]
Justin Reock commented on CXF-6481:
-----------------------------------
>From what I can tell, Karaf actually uses the HTTPJettyTransportActivator when
>httpj parameters are set in the context, it's just that there's no setter code
>for session support in HTTPJettyTransportActivator. You can see where it
>picks up the TLS parameters, but nothing for picking up a session. Further,
>if you configure TLS inside the httpj:engine setup, it *does* work and you get
>an SSL context. I tried that as part of my initial debugging, I set a TLS
>context to see if the httpj settings were just being ignored, and my TLS
>config worked fine. Just my 2 cents. Thanks!
> 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)
