[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Controller's execution env

[alesj]

"adrian at jboss.org" wrote : You just use the kernel as a factory to create a seperate context
  | that references the controller. Then you change whatever parameters you like
  | (subject to security).
  | 
  | 
  |   | <bean name="ReferenceToController">
  |   |    <constructor>
  |   |       <factory bean="jboss.kernel:service=Kernel"
  |   |                     method="getController"/>
  |   |    </constructor>
  |   |    <property name="executor"><inject bean="CustomExecutor"/></property>
  |   | ...
  |   | </bean>
  |   | 
  | 
That's what I said:
"alesj" wrote : 
  | looks like we might even inject something into the entry
  | via some factory
  | 
;-)

But this wasn't doable until we added BeanKernelRegistryEntry and
actually made it implement InvokeDispatchContext. 

"adrian at jboss.org" wrote : 
  | That's why I said that it is probably not required to be on the interface,
  | except that it would make programmatic config easier (e.g. testing)
  | if you don't have to cast/know the implementation detail.
I'll leave it on the interface - as you said, programmatic usage is much simpler - while it also makes sense as a spi contract.
e.g. Controller has an execution environment ~ executor

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

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