[
https://issues.apache.org/jira/browse/FELIX-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476863#comment-16476863
]
Carsten Ziegeler edited comment on FELIX-5853 at 5/16/18 5:34 AM:
------------------------------------------------------------------
If the whiteboard is used to register the servlet for JAX-RS, you could simply
register it within the same context as Sling does (or the other way round)
Alternatively we could think about a configuration which allows to configure
http context names that should share the same session space
was (Author: cziegeler):
If the whiteboard is used to register the servlet for JAX-RS, you could simply
register it within the same context as Sling does (or the other way round)
> Add HttpContext sharing support
> -------------------------------
>
> Key: FELIX-5853
> URL: https://issues.apache.org/jira/browse/FELIX-5853
> Project: Felix
> Issue Type: Improvement
> Reporter: Tony McCrary
> Priority: Major
>
> Since the switch to HTTP whiteboard, HttpContexts are no longer shareable
> within a Felix instance. This causes problems for Sling, when using
> technologies other than SlingServlet (e.g. JAX-RS), because session state is
> no longer accessible between the two technologies.
> Would it be possible to add a feature to enable HttpContext sharing like the
> older Felix versions? Or make it possible to register technologies on the
> same HttpContext everywhere?
> Right now, with Sling there are a handful of HttpContexts created and they
> all seem isolated, so state from one is not accessible in the other.
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
