[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: onDemand handling and aspects

[adrian@jboss.org]

The issue is more to do with the current KernelAware interface
not being rich enough because it only deals with the instance.

The callbacks are done on whether the instance (which could implement it
via an interceptor) has to be constructed.

What we really want is for all controller contexts to be acted upon
regardless of whether the real instance exists.

Such an api exists, it is the [Instance]ClassAdapter which was originally designed
to represent the instance regardless of whether it exists.

But the current code does not use the ClassAdapter exclusively so there is no
consistency. This was a deliberate decision in the AOP integration to
"get something working" without modifying AOP too much.

P.S. An alternative approach would be treat the JMX registration as a new deployer
that acts after the bean metadata. But this has no integration with the real AOP.

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

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