Resolving endpoints
Kevin Benson
kmb at mssl.ucl.ac.uk
Mon Jun 28 04:04:27 PDT 2004
Hello Guy,
The registry much like cgi services will just return back the enpoint
loated in the <AccessURL> element. Astrogrid added a small change
recently where if the endpoint/url ends in a "?wsdl" then it will look up
the endpoint from the WSDL (currently still on the client). But the
standard and preferred way is just to grab the text inside the <AccessURL>
element.
Cheers,
Kevin
On Mon, 28 Jun 2004, Guy Rixon wrote:
> Hi,
>
> currently, CGI services store direct-access URLs in the registry and SOAP
> services store URLs that produce their WSDL. To use a SOAP service via the
> registry a client has to look up its WSDL URL, download the WSDL and parse out
> the endpoint address.
>
> Can someone remind me whether this situation is supposed to continue, or ware
> we going to allow direct-access URLs for SOAP services with WSDL URLs moved to
> a separate metadatum?
>
> If we're not supporting direct-access URLs for SOAP services, can we add a
> registry function to obtain such a URL from an IVORN by handling the WSDL
> inside the registry service? It seems wasteful to put the WSDL-handling code
> in every registry client instead of in a handful of registry
> service-implementations.
>
> Cheers,
> Guy
>
> Guy Rixon gtr at ast.cam.ac.uk
> Institute of Astronomy Tel: +44-1223-337542
> Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
>
More information about the registry
mailing list