+

Search Tips   |   Advanced Search

Writing the WSDL extension that lets the WSIF service 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 EJB provider does not support the WSIF synchronous timeout. The EJB provider will not time out waiting for a Java method to complete.

Your WSIF client can invoke an enterprise bean 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 WSDL extension that enables the WSIF service to invoke an enterprise bean.


Tasks


Related:

  • WSIF and WSDL
  • Linking a WSIF service to a SOAP over HTTP service
  • Linking a WSIF service to a JMS-provided service
  • Writing the WSDL extension that lets the WSIF service invoke a method on a local Java object
  • WSIFOperation - Synchronous and asynchronous timeouts reference