[jboss-dev-forums] [Design of EJB 3.0] - Re: EJBTHREE-1173 and Beta4

[scott.stark@jboss.org]

As documented in EJBTHREE-1173, I added a hack to introduce a dependency on the timer service mbean in trunk as a temp fix. Carlo notes:

anonymous wrote : 
  | I still want to see the injection of the timer service into the deployer explored. It should create an implicit dependency.
  | 
  | Besides that way we properly establish which timer service are to be used by the containers.
  | 
  | Hmm, I'm missing a piece of the puzzle. I want EJB containers to become EJB Stateful, while this problem suggests EJB containers to become proper MC beans. In the end I want to have this code:
  | 
  | @Stateful // the container is a (level 1) bootstrap stateful session
  | public class StatefulContainer
  | {
  |    @Resource TimerServiceFactory timerServiceFactory;     // Injected
  | }
  | 
  | Level 1: EJB with injection & interception (there is chicken egg problem here)
  | Level 2: EJB with timers
  | Level 3: EJB with passivation
  | Level 4: Full EJB
  | (there will be more, or less)
  | 
  | So I'm catching up to the notion of MC control. That would mean an extra layer on top of MC for EJB functionality. And an EJB instance would actually be a MC bean instance (with EJB component meta data). That would leave interceptors in a void again. 
  | 



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

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