Need a little more info, but that exception is usually thrown when the object being
invoked upon (on the server side) is no longer available. If using remoting,
shouldn't matter that the client actually resides within JEE code. Might want to try
to debug by just running the remoting client standalone and call on server.
If can produce a test case that demonstrates the behavior, would be even better.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963881#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...