HTTP is a widely-used protocol for transferring information on the Web. Though originally designed to publish and retrieve HTML pages, it has now become a standard request/response protocol between clients and server.
When working with an external application using the HTTP protocol, an HTTP binding is necessary.
Comparing the HTTP binding to the Web services binding :
When working with an external application using the HTTP protocol, an HTTP binding is necessary.
- The HTTP binding handles the transformation of data passed in as a message in a native format to a business object in a SCA application.
- The HTTP binding also can transform data passed out as a business object to the native format expected by the external application.
Comparing the HTTP binding to the Web services binding :
- The Web Services binding only supports the SOAP (and JMS) protocols.
- The Web Services binding assumes that it is working with Web Services-based applications and so exposes the same model. In contrast, the HTTP binding assumes that it is working with native HTTP applications and exposes a model more familiar to this audience.
- Therefore, the Web Services binding provides first class support within the SCA architecture for Web Services applications communicating with the HTTP protocol and other protocols; whereas the HTTP binding allows WPS & WESB to mediate between, and communicate with, any HTTP application thus bringing any HTTP application into the Service Oriented Architecture framework.
Link for a working PI :
UI based application, involves Ajax call to the Http Export binding & display the response in the UI.
Web Project (Html page)------> AJAX HTTP CALL-----> HTTP Export---> Business Process----->Show AJAX HTTP Response
Web Project (Html page)------> AJAX HTTP CALL-----> HTTP Export---> Business Process----->Show AJAX HTTP Response
No comments:
Post a Comment