This content has been marked as final.
Show 4 replies
-
1. Re: Looking up a @Stateful Bean fails cause of AOP Intercept
cwulf Dec 27, 2006 11:11 AM (in response to cwulf)Solved it myself using JDK 1.5 instead of JDK 1.6 for client and JBoss.
Are there known problems with JBoss and Java 6? My remote clients run on the Eclipse Rich Client Platform and i think, i cant hope that no one of my users will upgrade to Java 6... -
2. Re: Looking up a @Stateful Bean fails cause of AOP Intercept
nicarran Jan 19, 2007 6:01 PM (in response to cwulf)"cwulf" wrote:
Solved it myself using JDK 1.5 instead of JDK 1.6 for client and JBoss.
Are there known problems with JBoss and Java 6? My remote clients run on the Eclipse Rich Client Platform and i think, i cant hope that no one of my users will upgrade to Java 6...
Related issue: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=98575 -
3. Re: Looking up a @Stateful Bean fails cause of AOP Intercept
htran_888 Feb 28, 2007 4:07 PM (in response to cwulf)Hi,
Sounds like it is a JBoss 4.0.4/4.0.5 issue since I have had no problem when using SJASA PE 9.0 with the same Netbeans on the same JDK 6.0.
Anyway, I will try it with JDK 1.5 to see whether it makes any difference.
Cheers,
Henry -
4. Re: Looking up a @Stateful Bean fails cause of AOP Intercept
htran_888 Feb 28, 2007 8:25 PM (in response to cwulf)Hi cwulf,
Your recommendation was correct.
By running only the Client program (EJB3ex512) using SDK 1.5 solved this issue.
All session beans and other clients are still using SDK 1.6 without a problem.
Thanks again,
Henry