Example: Writing the WSDL extension that enables the WSIF service to invoke an enterprise bean

Use the EJB provider, WSIF clients can invoke enterprise beans through Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP). Use this information, and associated code fragments, to help you to write the WSDL extension that links the WSIF service to a service implemented as an enterprise bean.

Although we can use the EJB provider for EJB(IIOP)-based Web service invocation, IBM recommends that you instead invoke RMI-IIOP Web services using JAX-RPC.

The EJB client JAR file must be available in the client runtime environment with the current provider. The enterprise bean is invoked using typical EJB invocation methods, using RMI-IIOP, with the current security and transaction contexts. If the EJB provider is invoked within a transaction, the transaction is passed to the onward service and the standard EJB transaction attribute applies.

If there are multiple implementations of the service, it is up to the service providers to make sure that every implementation offers the same semantics. For example, in the case of transactions, the bean deployer must specify TX_REQUIRES_NEW to force a new transaction.

The EJB provider does not support the WSIF synchronous timeout. The EJB provider will not time out waiting for a Java method to complete.

To use the EJB provider, we need the following binding specified in the WSDL file:

 

Example

    <!-- EJB binding --> 
    <binding .... > 
        <ejb:binding /> 
        <format:typeMapping style="Java " encoding="Java "/>? 
            <format:typeMap name="qname" formatType="nmtoken"/>* 
        </format:typeMapping> 
        <operation>* 
            <ejb:operation 
                methodName="nmtoken" 
                parameterOrder="nmtoken"
                returnPart="nmtoken"? 
                interface="remote|home" /> 
            <input name="nmtoken"? />? 
            <output name="nmtoken"? />? 
            <fault name="nmtoken"? />? 
        </operation> 
    </binding>

In this example:

• A question mark (?) means optional, and an asterisk (*) means 0 or more.

• The name attribute of the <format:typeMap> element is a qualified name of a simple or complex type used by one of the EJB operations.

• The formatType attribute of the <format:typeMap> element is the fully qualified class name for the Java class to which the element specified by name maps.

• The methodName attribute of the <ejb:operation> element is the name of the method on the enterprise bean that is called by the operation.

• The parameterOrder attribute of the <ejb:operation> element contains a white space-separated list of part names that define the order in which they are passed to the EJB method.

• The interface attribute of the <ejb:operation> element must be set to either remote or home. The value specifies the interface of the enterprise bean on which the method named by the methodName attribute is accessible.

In the next example:

• The className attribute of the <ejb:address> element specifies the fully qualified class name of the home interface class of the enterprise bean.

• The jndiName attribute of the <ejb:address> element specifies the full Java Naming and Directory Interface (JNDI) name used to look up the enterprise bean.

• The initialContextFactory attribute of the <ejb:address> element is optional and specifies the initial context factory class.

• The jndiProviderURL attribute of the <ejb:address> element is optional and specifies the JNDI provider Web address.

    <service ... > 
        <port>* 
            <ejb:address 
                className="nmtoken" 
                jndiName="nmtoken"
                initialContextFactory="nmtoken" ?
                jndiProviderURL="nmtoken" ? /> 
        </port> 
   </service> 

---

 

Related concepts

WSIF and WSDL

 

Related tasks

Linking a WSIF service to a SOAP over HTTP service
Linking a WSIF service to a JMS-provided service
Linking a WSIF service to the underlying implementation of the service

 

Related

Example: Writing the WSDL extension that enables the WSIF service to invoke a method on a local Java object
WSIFOperation - Synchronous and asynchronous timeouts reference