|
Greg,
Getting a remote interface and invoking methods on a stateless session bean has been stable for me. My first inclination would be that perhaps you have a mismatch with method signatures. I would suggest you validate the method signature between your client, the remote interface and the implementation. My guess would be that the problem is most probably a mismatch between the method signature the remote interface is publishing and what the implementation is expecting. Just my $0.02 worth. Remember, you get what you pay for .... Hitesh PS: 'javap -s <classname>' shows the fully resolved method
signature. Very valuable in cases where a particular classname was
used in multiple packages.
Greg Matthews wrote: Dear all, I've build an ejb jar, deployed it, and then tried to call one of the methods in one of the stateless session beans. It doesn't work. I can get a reference to the stateless session bean but can't work out why i can compile client code to call an ejb method, but then get a NoSuchMethodException when i try to run it. The line below is from a System.out.println call, showing that i've got a remote object reference. testing server = TestingServer stateless session |
- NoSuchMethodException Greg Matthews
- RE: NoSuchMethodException Hitesh Jasani
- RE: NoSuchMethodException Magnus Rydin
