Re: [Springframework-developer] Should JaxRpcPortClientInterceptor implement RemoteAccessor?

[<jue...@we...>]

JaxRpcPortClientInterceptor is indeed a "remote accessor", but it has a =
different base class, therefore it doesn't extend the convenience base =
class org.springframework.remoting.support.RemoteAccessor.
=20
For a working example, have a look at our JPetStore sample app: It =
exports its OrderService via 4 different remoting protocols, namely =
Hessian, Burlap, JAX-RPC and RMI invoker. It also includes a sample =
OrderServiceClient that accesses the service via all of those protocols.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Hunter Kelly
Gesendet: Do 08.04.2004 20:52
An: spr...@li...
Betreff: [Springframework-developer] Should JaxRpcPortClientInterceptor =
implement RemoteAccessor?



I was looking at the various classes and packages in
org.springframework.remoting, and I was looking that JaxRpc stuff.

It seems like JaxRpcPortClientInterceptor has the methods to be =
considered a
"RemoteAccessor"?  Is it a remote accessor?=20

I'll admit that I'm not completely au fait with JaxRPC and whatnot
(I was kinda hoping Spring can help me out :)  and I was just trying
to figure out which classes do what, and how they can help,
when I came across what looks like the above mentioned oversight.

Thanks,

H

P.S.  If anyone has any useful examples of the JaxRpc stuff, I'd be
very appreciative!



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer