|
Let me clarify the use case once again
Here are the relevant deployment parameters
-
Application name (runtime deployment name) Ex: mywebapp..20150101-prod
-
WAR name (mywebapp.war)
-
Context name (/my-web-app) so you can get to it with http://www.example.com/my-web-app
-
Clustered Session name (keyed off the context name)
In Payara/GlassFish, clustered session is keyed off of the context name,
this is why you can have any runtime name you want and the clustered session will still work.
All I want is for Weld is to support this use case.
|
