[jboss-jira] [JBoss JIRA] Updated: (JBAS-6746) provide jboss-web.xml option that tells JBAS to not initialize the webapp until the first request is received to its context, rather than the default of at webapp deploy/start time

[Remy Maucherat (JIRA)]

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

Remy Maucherat updated JBAS-6746:
---------------------------------

        Fix Version/s: JBossAS-6.0.0.M2
    Affects Version/s:     (was: JBossAS-6.0.0.M3)


> provide jboss-web.xml option that tells JBAS to not initialize the webapp until the first request is received to its context, rather than the default of at webapp deploy/start time
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6746
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6746
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>            Reporter: Ian Springer
>            Assignee: Remy Maucherat
>             Fix For: JBossAS-6.0.0.M2
>
>
> The Admin Console WAR includes Seam, and will be shipped as part of JBAS 5.1. When JBAS starts up, it deploys and starts the Admin Console WAR. The WAR takes 8-10 seconds to start up (95% of which is Seam initialization). We would like to avoid adding an additional 8-10 to the out-of-box overall JBAS startup time, which is why I'm looking for a way to put off the webapp init until the first time someone actually tries to hit it (which in some cases, may be never).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira