[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Concurrent deployments

[alesj]

"adrian at jboss.org" wrote : A simple mechansim that I can think of would to have a new ControllerMode
  | http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jboss-dependency/src/main/org/jboss/dependency/spi/ControllerMode.java?revision=31727&view=markup&pathrev=31727
  | which you could add to your deployment.
  | 
  | 
  |   | <deployment mode="asynchronous">
  |   |    <!-- beans here -->
  |   | </deployment>
  |   | 
  | 
  | which would work like the "automatic" mode, except it submits the work
  | to a background thread pool.
  | 
  | In this scenario, it would largely be "self-optimizing" since
  | it would automatically advance related dependencies that are eligible once
  | these beans reach the relevant stages.
  | 
How would this relate with KernelDeploymentDeployer, meaning that we need to 'convince' it not to split up the deployment into separate non-related beans.
Or how do you plan to group all beans from a deployment marked with 'asynch' and install them in the same background thread?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139276#4139276

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139276