In a standard Web service framework such as Axis, the WSDL/Java mapping requires a class generation and compilation stage. However, ILOG JRules uses a XOM dynamic class mechanism, 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.

The following points outline the ILOG JRules Web service mapping with respect to the JAX-RPC specification:

ILOG JRules mapping diverges from the JAX-RPC specification in that the services themselves are not represented in the XOM.

WSDL to XOM Mapping

The following table lists the different root components that may be encountered in a WSDL document, and details their mapping on a XOM.

* These WSDL components are not neglected in the XOM. They are just not transformed into separate and distinct XOM components.

WSDL Document Loading

The following code shows how to create a WSDL driver and transform a WSDL document into a dynamic model--a XOM.

// Create the driver and connect it to a XOM ruleset.
IlrRuleset aRuleset =...;
IlrWSDataDriver driver = 
new IlrWSDefaultDataDriver ( aRuleset.getReflect() );
 
// Load the WSDL file.
String wsdlFileName = "myFile.wsdl";
String serviceName = "myService";
driver.loadModel ( wsdlFileName, serviceName );
 
// In J2SE
System.setProperty(ServiceFactory.SERVICEFACTORY_PROPERTY,"org.apache.axis.client.ServiceFactory");
// Create the driver and connect it to the XOM of the ruleset.
IlrRuleset aRuleset = ... ;
IlrWSDataDriver driver = new IlrWSDefaultDataDriver ( aRuleset.getReflect() );
...

Port Type Operation Mapping

A port type is mapped to a dynamic class composed of two constructors:

ILOG JRules Web service operations can either be synchronous request-response or asynchronous one-way. This behavior is determined by the <message> and <operation> elements in the WSDL file.

Synchronous request-response means that every time a client application invokes a Web service operation, it receives a SOAP response, even if the method that implements the operation returns void. Asynchronous one-way means that the client never receives a SOAP response, not even a fault or exception.

The <operation> element describes how the public operations of a Web service are implemented. The public operations are those listed in the Web service WSDL and are executed by a client application that invokes the Web service:

The following example shows an <operation> declaration:

<operation name="getRate"> 
// If a part name appears in only the input message, it is an in parameter.
    <input message="tns:getRateRequest" name="getRate" /> 
// If a part name appears in only the output message, it is an out parameter.
    <output message="tns:getRateResponse" name="getRateResponse"/> 
</operation>

Out and in-out parameters enable an operation to return more than one return value. An in-out parameter acts as both an input and output parameter. To specify that a parameter is an in-out parameter, a part name appears in both the input and output message with the same type. You must always specify the parameter's XML Schema data type using the type attribute, as highlighted in the following <message> sample.

<message name="getRateRequest">
     <part name="country1" type="xsd:string" /> 
     <part name="country2" type="xsd:string" /> 
</message>
<message name="getRateResponse">
     <part name="Result" type="xsd:float" /> 
</message>

Thus, the port type maps to a XOM dynamic class, and the operation maps to XOM dynamic methods. The following table shows how the different parts of an operation are mapped.

Related Concepts

Related Tasks