AJAX WebService Component architecture
The basic architecture is illustrated on the following picture:
Our component auto-detects which way needs be used for invoke: RPC or document-style, and provides proper parameter conversion and envelope encapsulation if needed.
The typical use case is based upon few sequential calls:
The usage of AJAX WebService Component is pretty simple (see tutorial and examples), but with additional part with code generation, all WebService operations are encapsulated with objects, and you does not need to make even few steps above; the generated stubs will be used as any other AJAX component.
In details, AJAX WebService Component can be represented as
RPC style calls
The AJAX WebService Component isolates all details of underlying transport; so you don't need to understand the differences and provide any additional code to operate with RPC-style calls. The AJAX WebService Component provides full support for that kind of calls, without any limitations.
Document style calls
The AJAX WebService Component isolates all details of underlying transport; so you don't need to understand the differences and provide any additional code to operate with document-style calls. The AJAX WebService Component provides full support for that kind of calls, without any limitations.
By the way, in such WSDL definitions you can find type "xsd:any"; it means AJAX WebService Component have no any information about request/response structure; in this way AJAX WebService Component provides ability to create user-specific XML requests, and does not provide any handling of response; there is one case you'll need to operate with XML elements and operate with requests and responses at low level.
Meta-information from Web Services
The AJAX WebService Component provides full support of WSDL definitions recognition, and this information is available through AJAX WebService Component API; so you can use it in all your applications as you need without any manual parsing of WSDL and XSD elements.
The WebService Explorer application also added to AJAX WebService Component illustrates the complete way to operate with this meta-information, including in appliance to dynamic method invocation (see below).
Dynamic WebService invocation
The AJAX WebService Component provides way to recognize all operations, ports, parameters and their types in run-time; it means you able to use WebServices without code generation and without even any knowledge about this web service before calling.
Also, it means you able to track any 3rd party web services compliance in run time to your offerings; and not change in that service may break your application; for reasonable changes you able to use new changes without re-programming in your application.
And the WebService Explorer, the development tool to explore any 3rd party WebServices, illustrates it in details.
Static WebService invocation
In practice, the dynamic method invocation is suitable to call any web service; but for the following typical but not complete cases it may not so comfortable:
So AJAX WebService Component provides separate tool to generate code base based upon to WSDL definitions; all web service operations will be available as separate objects with encapsulated parameters. All complex structures and sequences are also encapsulated to auto-generated objects; so instead of filling nested named arrays, you able to use simple objects with their named properties.
AJAX WebService Component:
WebService Explorer Overview Download License Guide Support
|Copyright © SCAND LLC, 2007. All Rights Reserved.|