Writing the WSDL extension that lets your WSIF service invoke an enterprise bean

Using 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 Web Services Description Language (WSDL) extension that links your WSIF service to a service implemented as an enterprise bean.

Before you begin

Although you can use the EJB provider for EJB(IIOP)-based web service invocation, it is recommended that you instead invoke RMI-IIOP web services by using JAX-RPC.

The EJB client JAR file must be available in the client runtime environment with the current provider.

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

About this task

Your WSIF client can invoke an enterprise bean by 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, for transactions, the bean deployer must specify TX_REQUIRES_NEW to force a new transaction.

Use the following procedure, and associated code fragments, to help you to write the Web Services Description Language (WSDL) extension that enables your WSIF service to invoke an enterprise bean.

Procedure


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:29
File name: twsf_prewe.html