Tim McConnell wrote: > 3. For JEE 5 compliance, JSF 1.2 must now be part of the server runtime > stack. So, a GBean will be implemented for a JSF service (to start > necessary listeners, process JSF configuration parameters, etc, whatever > is required for JSF to function correctly), but that service will only > be started under two conditions: during server startup when a web > application is detected that uses JSF (via deployment descriptors), or > when a web application is deployed that uses JSF (again via deployment > descriptors). It seems prudent to only start the service when its > needed rather than simply starting it at server startup (even if its not > needed) especially with the single-JVM Geronimo architecture.
I think the service (if it is one) should be implemented on web deployment, and maybe even a part of the geronimo web deployer itself. Just for interest, can you explain the areas that need starting/configuring that fall outside how normal JSF works (i.e. you drop in the jars and set up your web.xml to use the API)? More specifically, what needs starting or deploying that is not handled by the standard web deployers outside of a web.xml? Jeff
