-
What is the difference between a Top-Down and Bottom-Up approach in SOAP Web Services?
What is the difference between a Top-Down and Bottom-Up approach in SOAP Web Services?
-
3 Replies
-
Top Down approach in SOAP-
- Top Down approach involves creating a WSDL and then creating the Web service using the WSDL file.
- In top-down approach, first you design the implementation of the Web service by creating a WSDL file. You can then create the Web service skeleton Java classes from the wsdl, and add the required code.
Bottom Up approach in SOAP-
- When creating a web service using Bottom Up approach, first you write the java classes for the web service and then create the WSDL file and publish the web service.
- Although bottom-up Web service development may be faster and easier, the top-down approach is the recommended way of creating a Web service.
- [adinserter block='9']
-
In a top-down approach, we create the WSDL first and then generate the web service artifact using the tool available in JDK.
Example scenarios:
- Users will be responsible for developing their own clients using different frameworks, based on a published WSDL.
- By creating the WSDL file first you will ultimately have more control over the web service, and can eliminate interoperability issues that may arise when creating a web service using the bottom-up method.
When creating a Web service using a bottom-up approach, first you write the java classes for the web service and then create the WSDL file and publish the web service.
Example scenarios:
- Situations which need quick and faster completion may prefer Java approach
- Java first approach is often the fastest and easiest approach.
Thanks.
-
Hi,
To make it more simple-
Top-down means you start with a WSDL and then create all the necessary scaffolding all the way down.
Bottom-up means you start with a your method, and generate the WSDL from it.
Hope this helps.
Log In to reply.
