>>>Do you think it's possible to re-use an InterceptorHandler instead of
>>>having the ejb-common code know so much detail of
>>>interceptors/decorators?
Hımm, the first reason is that in EJB scenario, target bean method is called by
the EJB container. Second is that InterceptorHandler is a Javassist method
handler, the other is interceptor. But it is reasonable to define common
methods that are used by both of them.
>>>I wasn't able to rebase my workspace yet, but who is calling the
>>>BaseEJBBean.setThreadLocal() ?
It is called by the EjbBeanProxyHandler#invoke
>>>Finally, does this work whether or not the EJB itself was contextual?
This is written to work with contextual EJB beans. If the EJB bean is not
contextual, then it does not support decorators but supports JSR299 style
interceptors. We could create a new EJB interceptor/utility for returning
interceptors for non-contextual ejbs.
Thanks;
--Gurkan
________________________________
From: Eric Covener <cove...@gmail.com>
To: dev@openwebbeans.apache.org
Sent: Sun, April 11, 2010 2:35:11 PM
Subject: Re: svn commit: r932843 - in
/openwebbeans/trunk/webbeans-ejb/src/main/java/org/apache/webbeans/ejb/common:
component/BaseEjbBean.java interceptor/OpenWebBeansEjbInterceptor.java
proxy/EjbBeanProxyHandler.java util/EjbDefinitionUtility.java
> + private Object callInterceptorsAndDecorators(Method method, Object
> instance, Object[] arguments) throws Exception
Do you think it's possible to re-use an InterceptorHandler instead of
having the ejb-common code know so much detail of
interceptors/decorators?
I wasn't able to rebase my workspace yet, but who is calling the
BaseEJBBean.setThreadLocal() ?
Finally, does this work whether or not the EJB itself was contextual?
--
Eric Covener
cove...@gmail.com
___________________________________________________________________
Yahoo! Türkiye açıldı! http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
