ILOG JRules User Guide > Integrating Application Data > Concepts > Web Service Binding > WSDL File Processing

WSDL File Processing

PREVIOUS NEXT

In JRules, Web service binding is carried out in two stages:

  1. At compile time, the Web Service Description Language (WSDL) specification file is converted to an Execution Object Model (XOM) using IlrWsDefaultDataDriver.
  2. At runtime, a connection is made to a Web service implementation to create XML objects, using SOAP (Simple Object Access Protocol) messaging.

Note
The use of WSDL files in the XOM is now deprecated. We recommend you use the JAX-WS API instead.

At runtime, the rule engine references the XOM, not the WSDL.

images/wsbinding1.png

In the WSDL, the port type is converted to an IlrWSObject. The XSD type is converted to an IlrXmlObject). An IlrXMLObject is created for each XSD type.

images/wsbinding2.png

Once the WSDL has been processed, the rule engine uses the XOM to perform operations on the WSDL-related Java types.

The following code shows how to pass XML data as a string: 

params.setParameter("paramXml", getXmlString () );)

In a standard Web service framework such as Axis, the mapping from WSDL to Java requires a class generation and compilation stage. JRules uses a XOM dynamic class, so the WSDL binding does not need to generate Java classes. The process of reading a WSDL document, mapping it on Java, and using it at runtime is completely dynamic.

Related Concepts

XML Binding
Third Party Data Access
Execution Object Model (XOM)

Related Tasks

Defining the Execution Object Model

Related Reference

Mapping Between Web Service Data and Dynamic Classes
Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. PREVIOUS NEXT