[jboss-jira] [JBoss JIRA] (WFLY-5550) Formalize web session clustering modules into a proper subsystem

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated WFLY-5550:
-------------------------------
    Description: 
Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose.

Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation.

The subsystem would define the requisite cache-container, exposed as a capability.

This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name).  jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile.

  was:
Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose.

Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation.

The subsystem would define the requisite cache-container, exposed as a capability.



> Formalize web session clustering modules into a proper subsystem
> ----------------------------------------------------------------
>
>                 Key: WFLY-5550
>                 URL: https://issues.jboss.org/browse/WFLY-5550
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Clustering
>    Affects Versions: 10.0.0.CR3
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 11.0.0.Alpha1
>
>
> Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose.
> Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation.
> The subsystem would define the requisite cache-container, exposed as a capability.
> This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name).  jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)