[
Lists Home |
Date Index |
Thread Index
]
See the Apache Axis WSIF project paper
http://www.research.ibm.com/people/b/bth/OOWS2001/duftler.pdf
You can dynamically parse the WSDL file and access a web service dynamically
(with no generation of dynamic Java classes etc). You can imagine a single
piece of code acting as the guts of a client that can access any web service
described by WSDL. (It's not a reality yet, but there's a significant part
of it working.) A client program can be directed to a WSDL file which is
very similar to the one published by the owner of the Web service in
question, but has changes. This is actually useful in development when the
original wsdl file is broken, or uses constructs that the consuming software
cannot grok, and you can work around the difficulties, but clearly it can be
used maliciously as well.
Jeff
----- Original Message -----
From: "Joe English" <jenglish@flightlab.com>
To: <xml-dev@lists.xml.org>
Sent: Friday, September 27, 2002 12:52 PM
Subject: Re: [xml-dev] Rethinking namespaces, attribute remapping (was
Re:[xml-dev] TAG on HLink)
> I was under the impression that developers download
> WSDL documents from service providers, feed them to
> some kind of WSDL toolkit, point, click, drag, drop,
> and out pops a working application that can access
> the service; at that point the original Web Service
> Description document is no longer needed.
>
> Is that not the case? Does the end user need the WSDL
> file at runtime as well?
|
