I don't know comparisation for that matter. But I can give a hind to a major subject.
A WSDL can have different styles RPC or DOCUMENT, encoded or litereral, wrapped or unwrapped. Only rpc/enc, rpc/lit, doc/lit and doc/lit-wrapped are importand. xFire can not handle rpc/encoded! Since Axis 1 uses rpc/enc as default style, most of the older SOAP with Axis 1 created services will not work. Fortunately the future belongs to doc/lit (wrapped) and thats xFires default style. Alternative ways are rare. Axis 2 does't support rpc/enc and even rpc/lit seems to not work. They say it is working, but I could not use it with my WSDL. Axis 1 support all styles but there are some comments that mean that it handles doc/lit not full. I hope that helped a little bit. > We already have the gui built on SWT for previous functionality. It works > very well and looks pretty good. Do you know the answer to the last part > of my question - processing WSDL's generated by non-XFire based services. > > Karl Palsson wrote: > > So do let us know when you have a nice gui with the source :) > > > > We love web service studio around here, but it's got a few bugs, no > > source, and no support. It's an old microsoft release. > > > > Cheers, > > Karl P > > > >> -----Original Message----- > >> From: Phil Gibbs [mailto:[EMAIL PROTECTED] > >> Sent: Wednesday, January 24, 2007 7:40 PM > >> To: [email protected] > >> Subject: Re: [xfire-user] Introspecting a WSDL > >> > >> > >> Sorry guys - should have searched past questions. Got the answer! > >> > >> Phil Gibbs wrote: > >> > I need to determine the operation parameters and associated > >> > >> parameter > >> > >> > data types by parsing the XFire-based service WSDL. So > >> > >> far, I've been > >> > >> > able to get a list of operations. Now I want the > >> > >> parameters etc, if > >> > >> > any, for each operation. The idea is to populate an SWT > >> > >> gui with this > >> > >> > information so that a user can invoke a specific method on > >> > >> a service, > >> > >> > and specify a value for each parameter, then call Client.invoke > >> > passing in these parameter values. > >> > So far getting these parameters and types has eluded me. > >> > >> Can anyone > >> > >> > tell me how to do this? Should I use the XFire API, or some other? > >> > I know WSDL is supposed to be standardized, but can a WSDL > >> > >> generated > >> > >> > from any web service API be parsed using the XFire API? I've > >> > experienced some problems when I've got a 'Definition' using XFire, > >> > and then using this definition instance in the WSIF API to > >> > >> get a Service. > >> > >> > Any help greatly appreciated... > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Introspecting-a-WSDL-tf3083625.html#a8570912 > >> Sent from the XFire - User mailing list archive at Nabble.com. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list please visit: > >> > >> http://xircles.codehaus.org/manage_email > > > > --------------------------------------------------------------------- > > To unsubscribe from this list please visit: > > > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
