[
https://jira.jboss.org/jira/browse/JBAS-6746?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-6746:
--------------------------------------
Easy answer: you cannot do that, and implementing it would take quite some development
effort, so it is not doable for 5.1.
Personally, I never liked delayed initialization, since: a) you will only know if the
feature is working once you need it b) it will put a large amount of load on the server
while it is otherwise user accessible, which means QoS issues. So even if it is
implemented someday, plese never enable it on a production config. But it does make sense
for development, where the two issues mentioned are not a real problem.
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: Sub-task
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Reporter: Ian Springer
Assignee: Remy Maucherat
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