Originally posted by Mike Thomson:
1. Usually the service provider will have the interface and implementation in their own language like Java (Fibonacci.java and FibonacciImpl.java) or C++.
On the other hand, the WSDL-to-Java approach gives you a powerful way to expose a stable service interface that you can evolve with relative ease. Not only does it give you greater design flexibility, the WSDL-to-Java approach also provides an ideal way for you to finalize all service details--from method call types and fault types to the schemas representing exchanged business documents--before you even start a service or client implementation. Although a good knowledge of WSDL and the WS-I Basic Profile is required to properly describe these Web services details, using available tools helps address these issues.
Then why the service provider itself again generating the Java from WSDL (WSDL2Java)?
After generating the WSDL2Java, why we are modifying the FibonacciSoapBindingImpl.java
The client can get the details like service and other details from the WSDL, but how knows the package structure like fibonacci.ws.FibonacciService. In wsdl the service name is given as FibonacciService, but the below coding is using complete package..how it is possible?
What this URL is meant for?
How Can I see the SOAP Messages in this example?
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton