[jira] Updated: (OWB-369) Static ContextsService in ContextFactory causes wrong webContextService used for multiple applications

[ https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG updated OWB-369: -- Attachment: ContextFactory.patch Thanks Gurkan, Joe. With Gurkan's recent changes, my second app still fails. Ho

Need to switch to subclassing?

Hi! There is a subtle difference between implementing interceptors via proxy or via subclasses. I have the following service which imports data from a legacy system into my db. Since commits are very performance intense, they should get imported in packages of 100. So I'll get 100 'Employees'

RE: Need to switch to subclassing?

Hi! I'd definitely would go the subclassing route. The problem you describe here is one of my biggest concerns of how Spring's AOP works. This is just not real AOP - it is dynamic proxy creation - not more, not less. An average developer will never be able to figure out what is going wrong here

Re: Need to switch to subclassing?

Not expected to work. For interceptor working, you have to call method on bean instance. So, move your method into other class (this must not be hard!) Spec. does not talk about anything about proxied or subclassing. It is leaved to implementation choice. Thanks; --Gurkan __

Re: Need to switch to subclassing?

Gurkan, I obviously DO call a method of a bean instance. So this scenario is perfectly valid from the spec perspective. LieGrue, strub --- Gurkan Erdogdu schrieb am Di, 11.5.2010: > Von: Gurkan Erdogdu > Betreff: Re: Need to switch to subclassing? > An: dev@openwebbeans.apache.org > Datum: Di

Re: Need to switch to subclassing?

This will also not work on EJB containers. For example, in EJB Hello @Interceptors(MyInterceptor.class) public Hello implemenet IHello{ public void method1(){ method2(); } public void method2(){ ... } } @Local public interface IHello{ publi

Re: Need to switch to subclassing?

Call on proxy instance not actual bean instance. From: Mark Struberg To: dev@openwebbeans.apache.org Sent: Tue, May 11, 2010 9:07:20 AM Subject: Re: Need to switch to subclassing? Gurkan, I obviously DO call a method of a bean instance. So this scenario is per

Re: Need to switch to subclassing?

I could not find this explicitly stated in the EJB spec neither - so maybe OpenEJB needs a fix too? :D Nah, just like to know what the 299 spec intends. Such things should work the same in Weld, CanDI, OWB and all other JSR-299 containers. I bet there are only very few developers (users!) out t

Re: Need to switch to subclassing?

http://openejb.979440.n4.nabble.com/Possible-OPENEJB-Bug-with-Interceptors-td982087.html From: Mark Struberg To: dev@openwebbeans.apache.org Sent: Tue, May 11, 2010 9:22:11 AM Subject: Re: Need to switch to subclassing? I could not find this explicitly stated

Re: Need to switch to subclassing?

One point; What is the role of TCK then? OpenEJB is TCK certified EJB container. When you pass TCK, then you are compatible. Thanks; --Gurkan From: Mark Struberg To: dev@openwebbeans.apache.org Sent: Tue, May 11, 2010 9:22:11 AM Subject: Re: Need to switch

Re: Need to switch to subclassing?

Such things should work the same in Weld, CanDI, OWB and all other JSR-299 containers Mmmm, I am not the same. Java EE specifications do not explicitly define some behaviors. Containers could implement those areas with their own way but they are all required to pass the "Java EE TCK". Theref

Re: Need to switch to subclassing?

Oki let me rephrase: I'd like to know if the spec (or Gavin) intends to define this behaviour or if it is 'intentionally left undefined'. LieGrue, strub --- On Tue, 5/11/10, Gurkan Erdogdu wrote: > From: Gurkan Erdogdu > Subject: Re: Need to switch to subclassing? > To: dev@openwebbeans.apach