-
1. Re: Entity Bean: $Proxy<nn> cannot be cast to ...
peterj Jan 24, 2009 5:54 PM (in response to speedo2k)Sounds like you are including the interface definition in your WAR file, remove it.
The problem is that if both your EJB JAR file and the WAR file contain the interface definition, each has its own classloader. Then the interface in the EJB JAR will be used to create the $Proxy126, but then in the WAR file the cast will be attempted with the interface in the WAT file, which is in the other classloader, and thus not the same.
I'm not sure what steps you would have to take in Eclipse to get it to not package the interface in the WAR file (I do all my packaging using Ant or Maven). -
2. Re: Entity Bean: $Proxy<nn> cannot be cast to ...
speedo2k Jan 25, 2009 5:52 AM (in response to speedo2k)Great, it works. But I try to understand what was wrong.
Previously I had in Dynamic Web Application i ndependencies:
- use EJB client jar and have checkbox on ejb client jar
Now I have
- Allow both and checkbox on ejb jar
Now works, when all is on one machine JBoss and Client on the same JVM.
Does this configuration will work also on distributed configuration? -
3. Re: Entity Bean: $Proxy<nn> cannot be cast to ...
mikecyl Mar 5, 2009 11:38 AM (in response to speedo2k)"speedo2k" wrote:
Great, it works. But I try to understand what was wrong.
Previously I had in Dynamic Web Application i ndependencies:
- use EJB client jar and have checkbox on ejb client jar
Now I have
- Allow both and checkbox on ejb jar
Now works, when all is on one machine JBoss and Client on the same JVM.
Does this configuration will work also on distributed configuration?
hi, speedo2k, I have the same problem as you. Could you please tell me how you reached to make it work in Eclipse? Thanks a lot!