Absolutely.

It's pretty easy if you have a human to interpret the semantics of the
interface. It's much harder to make an application do it all by itself.

Anne

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 26, 2003 10:06 AM
> To: [EMAIL PROTECTED]
> Subject: RE: How to dynamically invoke a webservice provided just WSDL?
>
>
>
> So it is conceivable that a Web Service client could:
>
> 1.  Use a UDDI registry to present a user with a list of available web
> services
> 2. Allow the user to choose one
> 3. Present the user with a list of methods the web service provides
> 4. Allow the user to choose one
> 5. Present the user with a list of arguments the method requires
> 6. Allow the user to enter the argument values
> 7. Allow the user to invoke the method and display the results
>
> without ever having known about the web service beforehand ?
>
> Jim Jackson
> SunGard EBS
>
>
>
>
>                     Tom Jordahl
>
>                     <[EMAIL PROTECTED]       To:
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>                     ia.com>              cc:
>
>                                          Subject:     RE: How to
> dynamically invoke a webservice provided
>                     03/26/2003            just WSDL?
>
>                     08:57 AM
>
>                     Please respond
>
>                     to axis-user
>
>
>
>
>
>
>
>
>
>
> Yes, this is exactly what the DII interface does - parse the WSDL
> and build
> a Call object.  We do the work so you don't have to!
>
> --
> Tom Jordahl
> Macromedia Server Development
>
> -----Original Message-----
> From: Doug Davis [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 26, 2003 8:50 AM
> To: [EMAIL PROTECTED]
> Subject: Re: How to dynamically invoke a webservice provided just WSDL?
>
>
>
>
>
>
> I'm surprised you had to build up the Call object yourself.
> If you look at the getQuote code in the stock quote sample (I think its
> getQuote2) he lets Axis parse the WSDL for him and Axis builds up the
> Call object - no direct calls to wsdl4j.� All you have to do is tell it
> which
> operation you want.
> -Dug
>
> <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > An identical situation still troubles me :) Anyway, my approach was a
> > bit more primitive than the getCalls method you're describing. I wrote
> > a lot of code to parse the WSDL doc using classes in the wsdl4j.jar
> > distributed along with axis (in \lib folder) and then build up my Call
> > object. In the end it works. If you're interested in this approach,
> > you'll find very useful the following article in IBM's dW:
> > "Dynamic Discovery and Invocation", by Damian Hagge (August 2001).
> > It sure showed me the ropes.
> >
> > Regards,
> > Costas
> >
> >
> >
>
>
>
>
> Copyright � 2003 by SunGard Data Systems Inc. (or its subsidiaries,
> ''SunGard'').  All rights reserved.  No parts of this document may be
> reproduced or transmitted without SunGard's prior written permission.
>
> This document contains SunGard's confidential or proprietary information.
> By accepting this document, you agree that:  (A)(1) if a pre-existing
> contract containing disclosure and use restrictions exists between your
> company and SunGard, you and your company will use this
> information subject
> to the terms of the pre-existing contract; or (2) if no such pre-existing
> contract exists, you and your Company agree to protect this
> information and
> not reproduce or disclose the information in any way; and (B)
> SunGard makes
> no warranties, express or implied, in this document, and SunGard shall not
> be liable for damages of any kind arising out of use of this document.
>
>
>
>
>
> Copyright � 2003 by SunGard Data Systems Inc. (or its subsidiaries,
> ''SunGard'').  All rights reserved.  No parts of this document may be
> reproduced or transmitted without SunGard's prior written permission.
>
> This document contains SunGard's confidential or proprietary information.
> By accepting this document, you agree that:  (A)(1) if a pre-existing
> contract containing disclosure and use restrictions exists between your
> company and SunGard, you and your company will use this
> information subject
> to the terms of the pre-existing contract; or (2) if no such pre-existing
> contract exists, you and your Company agree to protect this
> information and
> not reproduce or disclose the information in any way; and (B)
> SunGard makes
> no warranties, express or implied, in this document, and SunGard shall not
> be liable for damages of any kind arising out of use of this document.
>

Reply via email to