-
15. Re: Why does jbossall-client.jar cause
I read it, I believe the solution in that post is to deploy war as part of ear for ejb interface internal referencing with packaging them in the war file 'coz war can share the context with ear after deployed.
I don't understand why with JBOSS 4.0.2 and onwards, having EJB interfaces included in war will cause problems, probably it's because it will lead JBOSS server in referencing some different stub class which is used when comipiling the EJB interfaces but not valid on the server-side context.
But in my case, we may deploy the war and ear seperately for some reason. so I cannot put the war in the ear, and the EJB interfaces stay in the war file. -
16. Re: Why does jbossall-client.jar cause
the only other thing i can think of is replacing the home lookup with a bean interface lookup (ejb home is not required in ejb3)
MyRemote bean = (MyRemote)ctx.lookup("the jndi name");
-
17. Re: Why does jbossall-client.jar cause
if I replace the home lookup with a remote lookup, then a "java.lang.ClassCastException" occurs.
why is it all fine with JBOSS4.0.4.GA. I don't know what's changed internally in JBOSS 4.2.1.GA. -
18. Re: Why does jbossall-client.jar cause
I am interested in solving this problem as well - I have worked on this for the last 1.5 days, and searched the forums for a solution, but can't find any? Has anyone been able to get a REMOTE EJB3 client working with jboss? If so please explain the steps...
If I include my jar file that has the EJBs in my client's classpath, I get class cast exceptions.
If I dont' then I get rmi security exceptions ("no security manager: RMI class loader disabled") - If someone knows how to get past the security problem, that would be great to know..
Thanks! -
19. Re: Why does jbossall-client.jar cause
I figured out the problem I was having, and hopefully this may help you...
Make sure to put a try-catch around the entire body of code for your EJB interfaces. Basically I was having a problem with the SLSB.method, when it tried to invoke a SFSB.method2.
I my body of code for "SLSB.method" I had
lookup("SFSB"), and in Oracle this works fine, but for Jboss, I had to put "SFSB/local", and forgot to change the interface to Local as well, hense my SLSB.method was getting a ClassCastException, which propogated to the CLIENT as a null exception or ClassCastException with some sort of $Proxy cause...
Anyway once I straightened this out, my Client worked OK.