This content has been marked as final.
Show 2 replies
-
1. Re: Contract ejb3-interceptors and bean-factory
alesj Mar 31, 2008 10:10 AM (in response to wolfc)"wolfc" wrote:
Maybe we need an InstanceContext / BeanContext from the StatelessObjectFactory:Factory<T> { BeanContext<T> create(); }; BeanContext<T> { T getInstance(); <A> A getAttachment(Object key, Class<A> attachmentType); }
Does MC have such a thing?
What exactly are you looking for?
You can now change the underlying BeanFactory class.
Previous versions always used GenericBeanFactory.
Now you can set factoryClass attribute.
What your factory impl does is your thing. ;-)
e.g. CarlosBF::createBean() would always return BeanContext -
2. Re: Contract ejb3-interceptors and bean-factory
adrian.brock Mar 31, 2008 10:16 AM (in response to wolfc)"wolfc" wrote:
If we want to move more AOP then the real fix is to have a proper instance advisor.)
Sounds to me like you know where the real problem lies?
Maybe we need an InstanceContext / BeanContext from the StatelessObjectFactory:Factory<T> { BeanContext<T> create(); }; BeanContext<T> { T getInstance(); <A> A getAttachment(Object key, Class<A> attachmentType); }
Does MC have such a thing?
I don't know what you mean? Why would the MC know anything about
the BeanContext instances? The only thing it manages is the factory.
It's like saying if you deploy the TransactionManager using the MC
does it know anything about the transactions? :-)