GlassFish services and components to conform with configuration modularity
[GLASSFISH-19412] Web container configuration to conform with configuration modularity Created: 06/Dec/12 Updated: 21/Sep/15
|Reporter:||Masoud Kalali||Assignee:||Amy Roh|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
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.
|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.