JBoss development, A new message was posted in the thread "Deployment of on-demand web applications": http://community.jboss.org/message/522117#522117 Author : Brian Stansberry Profile : http://community.jboss.org/people/bstansberry@jboss.com Message: -------------------------------------------------------------- I don't mind continuing to debate the overall approach a bit; it's mostly a discussion of priorities. But IMHO the hooks in the Mapper class are a useful feature, whether or not we prioritize using them in M2. Having them in a JBoss Web release this week lets us go either way for M2. The rest of the implementation is in AS trunk itself, where the cutoff is 2 weeks later.   Bela's point about 2 mechanisms for delayed deployment is a good one. The critical thing is getting the server ready to handle requests ASAP; you can offload heavy non-critical stuff off the main thread. But if you do that, JBoss Web needs to know about the webapps that will be coming on later, otherwise the server isn't really "ready to handle requests". The Mapper stuff I did provides the hooks to make that doable. A user request triggers the deploy if the background thread hasn't gotten to it yet. Some simple coordination logic in the "activator" ensures it the activation only happens once. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/522117#522117