Re: [Springframework-developer] remote invocation

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

Hi Vladimir,
=20
Good point. HTTP-based protocols like Hessian and Burlap can use =
additional HTTP headers here, and already support basic authentication =
out-of-the-box. Our RMI support does not yet support such additional =
parameters, as we haven't focussed on providing full-fledged remoting =
yet. However, this should be easy to incorporate, so I'll consider quick =
adoption of the approach you suggested!
=20
BTW, as of the upcoming 1.0 RC2, RmiServiceExporter supports custom =
socket factories (a recent feature request). This enables SSL-based RMI =
socket factories and the like; we might even provide own pre-built =
socket factories within the Spring 1.1 timeframe.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Vladimir Blagojevic
Gesendet: Mo 23.02.2004 16:31
An: spr...@li...
Betreff: [Springframework-developer] remote invocation



Hi,

I posted this question on help forum but maybe this list is a more
appropriate venue for the discussion.

It seems that there is no current built-in API to specify additional
invocation parameters. Here is why. RemoteInvocationWrapper is an object
that accepts remote calls and tunnels them to a wrapped service object.
RemoteInvocationWrapper is bound to Registry and has a specific =
signature
- public Object invokeRemote(String methodName, Class[] paramTypes,
Object[] params) - that is matched by RemoteInvocationHandler.
RemoteInvocationhandler on a client side is in turn wrapped by
RmiClientInterceptor which directs calls from client intereface to the
RemoteInvocationHandler. Very nice, except that invokeRemote signature.

I remember that in Jboss days the problem of additional invocation
parameters was solved by an abstract Invocation interface that had a
couple of predefined properties (method,paramTypes, params)as well as a
map for custom properties. So instead of the above mentioned method
signature you would pass a more abstract Invocation object from client =
to
server.

Then you can add custom interceptors on both client and server and
customize invocation with additional parameters. For example, a client
interceptor prior to marshalling invocation could strap on user's
Principal and a server interceptor could access that principal in a
matching interceptor on the server?

Any comments?

Regards,
Vladimir


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer