xml-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@watson.ibm.com>
Subject Re: Decoupling rpcrouter.jsp
Date Mon, 07 Aug 2000 10:35:27 GMT
Hi a tired KH,

Can you please give a few more details of the problem you're having?
The coupling between rpcrouter.jsp and the deployment stuff is the 
necessary one where rpcrouter.jsp uses the deployment registry to
find the object on which to target the call. No way around that as
far as I can tell.

There's no coupling on the client side with this stuff as far as I

Sorry its been so frustrating .. lack of docs is still a major bug.


----- Original Message ----- 
From: "Kartheek Hirode" <kartheek_hirode@centegy.com>
To: <soap-dev@xml.apache.org>
Sent: Monday, August 07, 2000 4:34 AM
Subject: Decoupling rpcrouter.jsp 

> Is there any way to decouple the client and server-side from
> the 'rpcrouter.jsp' and the Deployment stuff?
> I just need a client (GetAddress-like) talking with a server
> which recieves the SOAP-encoded message, decodes it, processes it
> and sends it back to the client in SOAP-encoded form.
> The client will know how to decode it and take it from there.
> The payload will be 'String's which I presume have built-in
> encoding and hence do need explicit serializers/de-serializers.
> Frankly, this email is at the end of a cathartic 50+ hrs of
> trying to do the above. Just realized that I was fighting 
> against a 'design'.
> (There probably is vey few things I haven't tried already
> in terms of playing around with the code, so I might be missing
> something more profound)
> Tired,
> KH

View raw message