Hi,
there is no code portability (like in the CORBA world) supported among SOAP
runtimes.
It is unclear to me, what is your exact motivation for this. Anyway, I think
that you should use javax.wsdl.* package (Java API for WSDL) that allows you
to use "stadartized reflections" on WSDL and then you can use (proprietary!)
APIs to call appropriate WSDL operations.
For example, Idoox WASP (http://www.idoox.com/eap/wasp/index.html) offers
the implementation of javax.wsdl.* packages as well as DII style of web
services invocation, so you should be able to achieve the goal you have
described.
I'm not sure I understood your question correctly...
Radovan
> -----Original Message-----
> From: Neelesh Gurnani [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 07, 2001 1:40 AM
> To: [EMAIL PROTECTED]
> Subject: generic way of invoking web services.
>
>
> Hi,
>
> I am new to the soap world. I have a question
> regarding writing clients
> Given a web service definition i.e the wsdl for a
> particular service, has anybody implemented a generic
> java utility to invoke the service methods.
> I looked at the dynamic proxy article in javaworld but
> that also requires you to write and distribute the
> java interface for your web service which would mean
> changes on client side.
> Suggestions would be welcome.
>
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
