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

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : there should be an AOPInstallUnistallAction that pulls the the behaviors to apply from the metadata.
  | 

Doesn't that suffers from the same problem?
e.g. What if somebody else wants to an XXXInstallUninstallAction as well
as a the AOP one?

In general the MC actions are defined by the person that installs the context
so they can add/remove/override the actions.
e.g. Think about the what we want to do in the profile service where we "null out"
the instantiate/configure lifecycle actions.

At least with the AOP introductions/advices you can define what they are in the AOP config.

Of course, we could go to a more "fundamental" full AOP advice chain in the MC actions
where you could add abritrary behaviour to the actions chosen by the person
that created the context?

But I think this would be even harder to configure since you don't really have
a "target" on which you define pointcuts? That is unless the pointcuts were
just the MC lifecycle events and we had some custom pointcut language
to identify where the advices are applied.

It does have the advantage that you don't need to wrap the target in a proxy
just to add an introduction for deployment time (rather than runtime) behaviour
performed during the MC lifecycle events.

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

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