Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
Win a copy of Machine Learning Systems: Designs that scale this week in the Scala forum
or Xamarin in Action: Creating native cross-platform mobile apps in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

java2WSDL and WDL2java  RSS feed

 
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What are the pros and cons?
Thanks
 
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
java2wsdl:
The benefit is that you don't need to understand WSDL in order to deploy a web service. The downside is that the generated WSDL may be less than optimal in terms of interoperability, for example.
wsdl2java:
The benefits and downsides are the same as for java2wsdl, really.
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Could you please more on interoperability problems?
 
author
Ranch Hand
Posts: 92
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For the most part if you stick to the restriction enumerated in the WS-I Basic Profile 1.0a with regard to the generated WSDL, or the source WSDL, you should be fine.
A while back most wonks recommended always starting with WSDL, because that was the easiest way to get interoperability. That's still true to some extent, but the javaToWsdl tools are better now so you can pretty much go either way. Just make sure you examine the generated WSDL to make sure that it complies with the WS-I BP. This will require that you understand WSDL - but that's the expectation for anyone who is taking the test.
 
Gold Digger
Sheriff
Posts: 7610
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From Chapter 3 - Service Endpoint Design of the blueprints:


  • The WSDL to Java approach is the more powerful of the two approaches, but

  • it does require more of the developer. In particular, a developer must have
    more knowledge of WSDL and WS-I interoperability requirements. As a result,
    this approach is more difficult for a developer to use correctly and the potential for interoperability failure is much greater.Chapter 6 explains where this
    approach makes sense.
  • The Java to WSDL approach is easier for developers to use. If the proper tools are used, this approach almost always guarantees interoperability. However, its ease of use and guaranteed interoperability comes with the cost of less flexibility.

  •  
    I can't renounce my name. It's on all my stationery! And hinted in this tiny ad:
    Rocket Oven Kickstarter - from the trailboss
    https://coderanch.com/t/695773/Rocket-Oven-Kickstarter-trailboss
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!