If you can't do it let me know, should take me <1h
amrc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
> Sent: Monday, August 07, 2000 12:05 PM
> To: jBoss Developer
> Subject: RE: [jBoss-Dev] Proxy - can't do toString!
>
>
> Ok just checked this stuff...
>
> what is wrong is simple. Check the EntityProxy.java,
> StatelessSessionProxy.java and StatefulSessionProxy.
>
> The entityProxy does map all the local Object methods (and the
> EJB stuff it
> can do) but StatelessSessionProxy does only toString and
> StatefulSessionProxy does nothing. These need to be done on the client as
> you point out.
>
> Can you open a bug for this? and can you add the necessary code? I am sure
> some factoring can go in GenericProxy.java... your call,
>
> regards
>
> marc
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> > Sent: Monday, August 07, 2000 11:34 AM
> > To: JBoss Developers
> > Subject: [jBoss-Dev] Proxy - can't do toString!
> >
> >
> > Okay, I finally tracked down the cause of the problem I was having
> > late last week. You can't call toString on a client stub! I had a
> > println("result was: "+result) and it causes the problem where the stub
> > calls back to the server but the Method parameter comes through as null.
> > Perhaps because toString is not declared in the remote
> interface? I'm not
> > really sure.
> > So, can someone give me some pointers on where the client stub
> > "Proxy" objects are generated, so we can figure out why they're
> going back
> > to the server for toString, and why they're blowing up when they get
> > there?
> >
> > Thanks,
> > Aaron
> >
> >
> >
>
>
>
