-
1. Re: Wildfly 10: cannot share the same JSessionID between two different applications
mchoma Nov 10, 2017 3:53 PM (in response to dk_efiport)You can share session between wars in ear
Web (Undertow) Reference Guide - WildFly 10 - Project Documentation Editor
-
2. Re: Wildfly 10: cannot share the same JSessionID between two different applications
dk_efiport Nov 16, 2017 12:15 PM (in response to mchoma)I will give it a try, but for me it would be sufficient or even better to share just the JSessionID and not to share the session itself.
In JBoss 4 (from where I have to migrate the applications) both applications were using the same JSessionID. They should not have access to data of the other application's session. But I am not sure if this is possible in WF10.
Another issue with the EAR configuration you suggested seems to be that every object in the session has to be serializable. So without code changes the application currently doesn't work.
-
3. Re: Wildfly 10: cannot share the same JSessionID between two different applications
pferraro Nov 16, 2017 2:37 PM (in response to dk_efiport)I will give it a try, but for me it would be sufficient or even better to share just the JSessionID and not to share the session itself.
I don't fully understand your use case. If your sessions are specific to their respective web applications, what need would you have to reuse session IDs?
Another issue with the EAR configuration you suggested seems to be that every object in the session has to be serializable. So without code changes the application currently doesn't work.
The distributed session manager only requires that session attributes are serializable if the backing Infinispan cache configuration requires it. This has been the case since WF10. See: WFLY-5502 Don't require marshallable session attributes if the cache … · wildfly/wildfly@b254e50 · GitHub