assuming you have a copy of the deployment descriptor
(otherwise how will you know which methods to call?),
you have a list of all the service's published methods
(the only problem is - you don't have their
signatures).
from this you could generate an interface in which
every method took parameters (Params).
then you could implement this interface via a proxy
which just called the equivalent method on a SOAP
service (to which you had previously bound it
somehow).
Obviously you'd get a better proxy if the service
declared a separate interface that was to be it's SOAP
API, then distributed a copy of it (complete with
signatures), but beggars can't be choosers. If the
compiler could check everything, it would take all the
fun out of it !
Sound crazy ?
Jules
P.S.
Let me know if you go this way, I'd be interested in
getting a copy of the code....
--- Neelesh Gurnani <[EMAIL PROTECTED]> wrote:
> 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/
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
