[jira] [Created] (FELIX-5916) Felix Framework - dependency on org.apache.felix.resolver

Tom Rutchik created FELIX-5916: -- Summary: Felix Framework - dependency on org.apache.felix.resolver Key: FELIX-5916 URL: https://issues.apache.org/jira/browse/FELIX-5916 Project: Felix Issue Typ

[jira] [Commented] (FELIX-5913) Support Android

[ https://issues.apache.org/jira/browse/FELIX-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590700#comment-16590700 ] Tom Rutchik commented on FELIX-5913: Karl, thanks for your quick response. Yeah, I di

[jira] [Updated] (FELIX-5915) Ignoring resolution:optional by mavenbundleplugin

[ https://issues.apache.org/jira/browse/FELIX-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subrahmanyam Sistha updated FELIX-5915: --- Priority: Major (was: Critical) > Ignoring resolution:optional by mavenbundleplugin

[jira] [Updated] (FELIX-5915) Ignoring resolution:optional by mavenbundleplugin

[ https://issues.apache.org/jira/browse/FELIX-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subrahmanyam Sistha updated FELIX-5915: --- Description: HI Team, We are working on wicket-8 migration, In wicket 8 pom.xml on I

[jira] [Created] (FELIX-5915) Ignoring resolution:optional by mavenbundleplugin

Subrahmanyam Sistha created FELIX-5915: -- Summary: Ignoring resolution:optional by mavenbundleplugin Key: FELIX-5915 URL: https://issues.apache.org/jira/browse/FELIX-5915 Project: Felix I

Re: Session invalidation

My thought was that by hooking into the Jetty handlers it wouldn’t be necessary to do any work with the session cookie, effectively making the SessionIdManager “OSGi HttpContext aware” so that different contexts create and/or get different sessions back. It’s possible that this isn’t sufficient

Re: Session invalidation

Hi, potentially yes, as mentioned we could do this in the Jetty case. However, it might require a little bit more like ensuring that the virtual id is correctly used for rewriting urls/managing the session cookie. Regards Carsten Timothy Ward wrote > Would it not be sufficient to generate a v

Re: Session invalidation

Would it not be sufficient to generate a virtual session id for each session in the whiteboard? This should be possible by customising the Whiteboard’s SessionIdManager and SessionCache