I am trying to implement a very simple AsyncCallback RPC system, and I
believe I have 99% of it correct. I have the UserService and
UserServiceAsync on the client side, and the UserServiceImpl on the
server side. Through debugging, it appears that the only current
issue is the error message I
0 arg constructor? Return value of the RPC uses generics ala
ListUser? All I can think of, you might also look in the rpc log
file which is sometimes slightly more helpful. If you can't figure
out, post the UserService and UserServiceAsync calls and maybe the
constructors as well.
BTW no need
So it appears that the issue is User did not have a 0 argument
constructor. I removed the constructor and everything appears to be
working. I guess I will just have to set all of the members manually
with the setters. Not a problem, just several more lines of code.
Thanks!
On Apr 22, 8:24 pm,
You can still keep your multi-argument constructor, you just also must
have a zero arg.
On Apr 22, 7:53 pm, Adam35413 adam.ham...@gmail.com wrote:
So it appears that the issue is User did not have a 0 argument
constructor. I removed the constructor and everything appears to be
working. I
