[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Lifecycle aspects revisited

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : 
  | Really what I'm suggesting is that the aop:xxx lifecycle elements populate the list of orthogonal behaviors that should be applied during that phase.

Ok so the aop:xxx lifecycle callbacks would implictly define the pointcuts?
I wasn't involved in the design of this part so we'll have see what Kabir thinks.

But it would make sense from my point of view if you could add an action
for deployment time processing without having to add an introduction into the POJO.

e.g. @JMX or @JNDI on the target bean would lead to lifecycle events on
the context but you don't have to go through the proxy at runtime
(although I know at least for the pure AOP this was almost a no-op anyway :-).

The other reason why this would be useful is because I want to have the ability
to see the MBean in the JMX-console even when the target doesn't exist for
the "on-demand" behaviour.
e.g. You would still a skeleton MBean with a single operation to start it.
I don't know how far Kabir got with this using an Introduction and a "hollow proxy"?

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

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