You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Steve Graham <sg...@us.ibm.com> on 2001/02/07 04:29:19 UTC
Re: Some form of soap rpc call broker
In the latest draft of the WSDD, there is the possibility to have the
service described using a V2 style deployment descriptor or reference the
WSDL for the description of the service. There is alot of information like
this that we can generate from WSDL.
Of course the agreement in Axis is that we do not prereq any service
description mechanism. The reference from WSDD to WSDL is not required
(can use V2 style deployment descriptor).
There are some scenarios we need to walk through to validate this approach.
This walkthrough has not to date been done.
sgg
++++++++
Steve Graham
sggraham@us.ibm.com
(919)254-0615 (T/L 444)
<<Pithecanthropus Erectus>>
Emerging Internet Technologies
++++++++
"Sanjiva Weerawarana" <sa...@watson.ibm.com> on 02/05/2001 11:25:13 PM
Please respond to soap-dev@xml.apache.org
To: <so...@xml.apache.org>
cc:
Subject: Re: Some form of soap rpc call broker
What you've done is akin to a dynamic invocation interface vs. the
static invocation interface approach that generated proxies take.
Both are perfectly valid and perfectly useful (there are cases
where the static one cannot be done for example). As such, it'll
be nice for a WSDL-aware SOAP infrastructure (Axis folks?) to support
such a dynamic invocation interface!
Sanjiva.
----- Original Message -----
From: "David Bartle" <Da...@whn.com>
To: <so...@xml.apache.org>
Sent: Monday, February 05, 2001 4:57 PM
Subject: Some form of soap rpc call broker
> I was mulling over the way a Call must be made - lots of setting of
values
> that
> can be discovered via WSDL - and was thinking, "why can't this be easier
> without
> loosing flexibility?"
>
> So I have been working on a broker that autodetermines types and the
service
> URI
> as well as the names of the parameters.
>
> A typical call looks like this:
>
>
> URL wsdlURL = new URL("serviceInfo.wsdl");
>
> SoapCall myCall = new SoapCall( wsdlURL );
>
>
> Vector parameters = new Vector();
>
> parameters.add( new String("data for parameter one") );
> parameters.add( new Integer(14) );
>
> try {
>
> String returnValue =
> (String)myCall.invoke("serviceName","methodName",parameters);
> }
> catch( WSDLException ) {}
> catch( IllegalArgumentException e ) {}
> catch( SOAPException e ) {}
> catch( ClassCastException e ) {}
>
> This is just a quick example of what could be. Of course the
> "SimpleSoapCall"
> makes use of some sort of WsdlDocument class and uses reflection for
> determining
> the class types of the parameters.
>
> Parameter names are provided by WSDL
> Return value is provided by WSDL
> Soap Action is provided by WSDL
> Soap URI is provided by WSDL
> Method names and Services are provided by WSDL
>
> I put together a test client that automatically builds appropriate soap
> mapping registriy
> (with the aid of a properties file) and makes the appropriate rpc call
using
> Call.invoke(...)
> I also threw together a quick little WSDL class as a proof of concept...
It
> makes calling
> a method very very easy.. Is anyone else working on this or have any
> suggestions or comments?
>
> I am fairly new to the soap spec so I may be overlooking something.
>
>
> David Bartle
> Developer
> Whats Hot Now (whn.com)
> david.bartle@whn.com
> (310) 754-2685