[jira] [Comment Edited] (FELIX-5853) Add HttpContext sharing support
[ 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)
[jira] [Commented] (FELIX-5853) Add HttpContext sharing support
[ https://issues.apache.org/jira/browse/FELIX-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476863#comment-16476863 ] Carsten Ziegeler commented on FELIX-5853: - 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)
[jira] [Resolved] (FELIX-5850) ResourceBuilder should do deal with null bundle manifest version
[
https://issues.apache.org/jira/browse/FELIX-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved FELIX-5850.
-
Resolution: Not A Problem
Fix Version/s: (was: utils-1.11.2)
There's no problem with the current source. Sorry for the noise.
> ResourceBuilder should do deal with null bundle manifest version
>
>
> Key: FELIX-5850
> URL: https://issues.apache.org/jira/browse/FELIX-5850
> Project: Felix
> Issue Type: Bug
> Components: Utils
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> The {{ResourceBuilder#doBuild}} should deal with empty (null) bundle manifest
> version.
> We should do:
> {code}
> private static String getBundleManifestVersion(Map
> headerMap) {
> return headerMap.get(Constants.BUNDLE_MANIFESTVERSION);
> }
>...
>// Verify that only manifest version 2 is specified.
> String manifestVersion = getBundleManifestVersion(headerMap);
> if (!"2".equals(manifestVersion)) {
> throw new BundleException("Bundle-ManifestVersion must be 2 but
> is: " + manifestVersion);
> }
> {code}
> I will provide a PR (and test with Karaf itest).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] felix pull request #137: [FELIX-5850] Deal with non present Bundle-ManifestV...
Github user jbonofre closed the pull request at: https://github.com/apache/felix/pull/137 ---
[jira] [Commented] (FELIX-5850) ResourceBuilder should do deal with null bundle manifest version
[
https://issues.apache.org/jira/browse/FELIX-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476379#comment-16476379
]
ASF GitHub Bot commented on FELIX-5850:
---
Github user jbonofre closed the pull request at:
https://github.com/apache/felix/pull/137
> ResourceBuilder should do deal with null bundle manifest version
>
>
> Key: FELIX-5850
> URL: https://issues.apache.org/jira/browse/FELIX-5850
> Project: Felix
> Issue Type: Bug
> Components: Utils
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: utils-1.11.2
>
>
> The {{ResourceBuilder#doBuild}} should deal with empty (null) bundle manifest
> version.
> We should do:
> {code}
> private static String getBundleManifestVersion(Map
> headerMap) {
> return headerMap.get(Constants.BUNDLE_MANIFESTVERSION);
> }
>...
>// Verify that only manifest version 2 is specified.
> String manifestVersion = getBundleManifestVersion(headerMap);
> if (!"2".equals(manifestVersion)) {
> throw new BundleException("Bundle-ManifestVersion must be 2 but
> is: " + manifestVersion);
> }
> {code}
> I will provide a PR (and test with Karaf itest).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FELIX-5853) Add HttpContext sharing support
Tony McCrary created FELIX-5853: --- Summary: Add HttpContext sharing support Key: FELIX-5853 URL: https://issues.apache.org/jira/browse/FELIX-5853 Project: Felix Issue Type: Improvement Reporter: Tony McCrary 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)
