[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:comment-tabpanel&focusedCommentId=13646555#comment-13646555 ] 

Paul Ferraro commented on WFLY-5550:
------------------------------------

[~tommaso-borgato] Re: jboss-web.xml options:
The link you pasted is documentation from a very old JBoss AS 4.2.2.

* replication-trigger has dropped from version 8.0 of the jboss-web.xml schema and has been ignored since EAP 7.0, following the redesign/reimplementation of the distributed session manager
* FIELD granularity was dropped since EAP5.
* replication-field-batch-mode is specific to FIELD granularity, and was has also dropped in EAP5.

Re: missing options from jboss-web.xml
I do not intend to add any new options to jboss-web.xml.  In fact, the entire <replication-config/> is being dropped from the jboss-web.xml schema.  Configuration of the distributed session manager will no longer be done via this deployment descriptor, unless a legacy application is deployed (i.e. containing an old version of jboss-web.xml).

> 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
>            Priority: Major
>
> 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
(v7.12.1#712002)