Tim, i was under the same impression, but then read a couple of IBM comparison articles and a WSO2 blog and it seemed that the WSDL 2.0 was gaining ground. Further, the tooling for WSDL, with integration into all the major IDE's, has been significantly more developed than the WADL tooling. However, yesterday i tried a simple example with a schema-valid WSDL 2.0 xml document for a simple service with 1 operation and the Apache Axis2 tool barfed on the fact that the schema pointed to in the document was for WSDL 2.0 and not WSDL 1.1 -- despite the fact that they claim on their home page to support WSDL 2.0.
For the record, WSDL -- as much as i hate it -- was not meant to be tied to a transport. As a matter of fact, neither was SOAP. You should be able to effect these over any transport, HTTP included, and presumably in more than one way. WADL is tied to HTTP. This means its scope is considerably more limited. Best wishes, --greg On Tue, Aug 11, 2009 at 12:55 AM, Timothy Perrett <timo...@getintheloop.eu>wrote: > > Hey Greg, > > Im not sure about WSDL2.0, but my understanding was that WADL > ( https://wadl.dev.java.net/ ) was making the most ground in the REST > service description arena. > > Cheers, Tim > > On Aug 10, 10:58 pm, Meredith Gregory <lgreg.mered...@gmail.com> > wrote: > > Lifted RESTafarians, > > > > Has anyone tried the Apache Axis 2 WSDL 2.0 support? i'm looking at this > > page< > http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-wsdl2code-pl.. > .>and > > it claims they have a maven plugin to generate the stubs for a WSDL > > 2.0 > > REST binding. i'm going to play around with it to wrap BNF Converter in a > > RESTful service; but, i was wondering if anyone else had experience with > it. > > > > Best wishes, > > > > --greg > > > > On Fri, Aug 7, 2009 at 12:31 AM, Viktor Klang <viktor.kl...@gmail.com > >wrote: > > > > > > > > > > > > > Hello Jacek, > > > > > actually, if I were you I'd consider implementing your webservices as > REST > > > services and then just have your SOAP stubs call your rest services. > (If > > > you're not using anything voodooesque) > > > > > Then you have the benefit of using the existing plumbing as much as > > > possible, while still maintaining your SOAP interface as well as a > potential > > > migration path to something non-WSDL. > > > > > (I am severely biased by having to work with SOAP, which has scarred me > for > > > life) > > > > > On Thu, Aug 6, 2009 at 5:26 PM, Jacek Furmankiewicz <jace...@gmail.com > >wrote: > > > > >> I was reading through the Lift book PDF and it mentions only REST- > > >> style web services. > > > > >> In our case, we need to look at re-implementing a set of existing SOAP > > >> web services (is there anything like 'wsdl2scala' anywhere?). > > > > >> I would appreciate any best practices and suggestions for implementing > > >> SOAP web services in the context of a larger Lift app (and Scala in > > >> general). > > > > > -- > > > Viktor Klang > > > > > Rogue Scala-head > > > > > Blog: klangism.blogspot.com > > > Twttr: viktorklang > > > > -- > > L.G. Meredith > > Managing Partner > > Biosimilarity LLC > > 1219 NW 83rd St > > Seattle, WA 98117 > > > > +1 206.650.3740 > > > > http://biosimilarity.blogspot.com > > > -- L.G. Meredith Managing Partner Biosimilarity LLC 1219 NW 83rd St Seattle, WA 98117 +1 206.650.3740 http://biosimilarity.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
