[jboss-dev-forums] [Tomcat Integration Development] New message: "Re: Deployment of on-demand web applications"

JBoss development, A new message was posted in the thread "Deployment of on-demand web applications": http://community.jboss.org/message/524929#524929 Author : Brian Stansberry Profile : http://community.jboss.org/people/bstansberry@jboss.com Message: -------------------------------------------------------------- JIRA for the basics of this is http://community.jboss.org/thread/147220   AS trunk currently has admin-console, jmx-console and jbossws-console starting this way. For now I left the http-invoker alone, as it's a bit of a different beast from a console.   https://jira.jboss.org/jira/browse/JBAS-7714 is to firm up how to easily enable/disable this behavior. For M2, adding -Djboss.as.deployment.ondemand=false turns it off (i.e. causes the WARs to deploy during normal startup). I think that's OK for M2, which isn't meant to be used in production.   Jaikiran, sorry for the slow reply. I'll think about combining in one file. The advantage of multiple files is the instructions for how to deploy the war normally is simple -- copy the war from common/deploy/ to deploy/ and delete the -activator-jboss-beans.xml. "Delete the file" is easier than "edit the file". But since each activator bean exposes a boolean property to disable the on-demand behavior, I suppose it's even easier to tell people to leave the war where it is and edit the appropriate bean in a single file.   Re: putting all these in one special location and scanning rather than requiring config, that would be quite a bit of effort; it's not just a matter of looking at the name of a deployment archive and figuring everything out. For example, the context path for jbossws-console.war is jbossws, not jbossws-console, so we'd have to find and parse jboss-web.xml to know that.   The admin console uses the ServletContextListener trick you mentioned. Even with that it takes a long time to deploy. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/524929#524929