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

[alesj]

"kabir.khan at jboss.com" wrote : 
  | I could add the setExecutor() method to the Controller interface, but maybe it belongs better in an AsynchController interface (similarly to what was done for GraphController)?
No and no. :-)

I don't we should expose Executor on Controller, as this is impl detail.
The Controller should only expose "state machine" API.

Afaic AsynchController doesn't have any proper value,
to only exist to expose setter/getter doesn't make sense.

I guess what you could do is to create proper KernelConfig/Initializer,
which knows how to supply proper Executor to new Controller instance.
Or, I actually don't mind if you do a cast to AbstractContorller, as long as you do the check before.

I'll think about this some more ... if there is any nicer way to handle this.

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

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