GlassFish services and components to conform with configuration modularity (GLASSFISH-19408)

[GLASSFISH-19412] Web container configuration to conform with configuration modularity Created: 06/Dec/12  Updated: 19/Sep/14

Status: Open
Project: glassfish
Component/s: web_container
Affects Version/s: None
Fix Version/s: 4.1

Type: Sub-task Priority: Major
Reporter: Masoud Kalali Assignee: Amy Roh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Different modules requires to conform with configuration modularity. This is a parent task for all the issue being filed for this project. More details at the internal wiki page: http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Config+Modularity+One+Pager This ticket is to track this change for web container.



 Comments   
Comment by Amy Roh [ 14/Mar/13 ]

Grizzly service starts before web container service which is only started after web deployment. Grizzly start up service currently requires some of web related configs to exist in domain.xml.  Since Grizzly requires web configuration to be available, config modularity divides web container configurations to multiple modules (some will go to grizzly service module to satisfy its dependency and some remain in the gf-web-connector.  Need to decide what is the optimal solution.

Comment by Amy Roh [ 27/Mar/13 ]

Configuration modularity will be addressed in 4.0.1.

Generated at Sat Aug 29 00:39:40 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.