RE: service references (was: Re: WSA diffs from REST)

Systinet WASP has supported service references for more than a year. It
references a Web service by its WSDL port. To pass a service by reference,
you return the URI of the WSDL port, and you return an instance ID of the
service instance in a SOAP header. You can reconnect to the same instance by
dynamically connecting to the service (using a dynamic proxy or a DDI) and
specifying the instance ID in the SOAP header. The WSDL file for the service
indicates what types and headers are used in the service.

It would be nice to define a standard SOAP extension to accomplish services
by reference, but I don't view it as a top priority. We had a discussion
about service references on Apache axis-dev a while back, but it didn't go
anywhere.

Anne

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Sanjiva Weerawarana
> Sent: Monday, September 23, 2002 2:32 PM
> To: Paul Prescod; Mark Baker
> Cc: www-ws-arch@w3.org
> Subject: service references (was: Re: WSA diffs from REST)
>
>
>
> "Paul Prescod" <paul@prescod.net> writes:
> >
> > As an example, I am willing to bet a substantial amount of
> money (but in
> > Canadian dollars) that [1] will also be an issue that will require TAG
> > intervention if it is not fixed by the relevant working group:
> >
> >   * http://www.blogstream.com/pauls/1032521623
>
> All that's needed is a notion of service references and the ability
> for a WSDL part to say its of a certain reference type. That's it.
>
> BPEL4WS already introduces a version of service ref. An improved,
> cleaned up, separated version is of that concept will undoubtedly
> be proposed.
>
> With that, the next step is to be able to put a service ref as
> a WSDL part. I'm quite certain that'll come too - without that
> one cannot do pub-sub style stuff and lots of others.
>
> I'm surprised your article takes the tone that the people doing
> WS stuff are so dumb as to not want or understand the need for
> certain functionality. This is just a simple feature and a
> solution to half of it was already published in the BPEL spec.
> The rest will come too - soon.
>
> Sanjiva.
>
>

Received on Monday, 23 September 2002 16:40:14 UTC