JBoss development, A new message was posted in the thread "Deployment of on-demand web applications": http://community.jboss.org/message/522073#522073 Author : Brian Stansberry Profile : http://community.jboss.org/people/bstansberry@jboss.com Message: -------------------------------------------------------------- Re: the general approach to slimming -- on-demand vs. just keeping stuff out of profiles...   That's really the core discussion. I like the on-demand approach, and felt like actually coding after 1.5 months of mostly discussing, so I went for it. But if another general solution is better, that's what we should do.   Stan, the thing I don't like about the multiple config approach is it somewhat mixes apples and oranges -- whether I want something included in the initial boot of the server vs whether I want it at all are two slightly different things. For example,   1) I'm developing with the "cluster" profile. Now I have to wait 18 seconds on every boot for the admin-console. Ugh. (Believe me, I'm very conscious of the added boot time from the current "all profile. )   2) I'm developing with the "development" profile. But now I want to look at the jmx-console or admin-console. I have to switch profiles or create a custom profile to get that. Ugh.   Rémy, I 100% agree that on-demand on a production server is a terrible idea. So if the basic approach to making on-demand work is sound, a next step is to figure out a simple mechanism to allow the on-demand applications to be deployed immediately. The "activator" bean I describe above could easily be enhanced to add some logic to check an overall server state, and actually activate the profile at server start. For example,   public enum ServerBootMode {    FAST, SOME_MIDDLING_TERM, FULL; }   The "activator" bean then has a config property added   <property name="onDemandBootMode">FAST</property>   In start() it checks the server's boot mode against its "onDemandBootMode" and if the server is greater, it activates the profile immediately, not as on-demand.   A startup switch could control the server-wide boot mode. For certain profiles, we could add a bean that sets the boot mode to an appropriate default if the user hadn't done it via a startup switch. Production sets it to FULL, "development" to FAST etc. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/522073#522073