Using the EJB provider, WSIF clients can invoke enterprise beans.
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 using JAX-RPC.Why and when to perform this task
The EJB client JAR file must be available in the client run-time environment with the current provider. The enterprise bean is invoked using normal EJB invocation methods, using Remote Method Invocation over Internet Inter-ORB Protocol (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.
What to do next
For examples of the code changes that need to be made in the WSDL file, see The EJB provider - Writing the WSDL.
Related tasks
Using
the SOAP provider
Using the JMS providers
Using
the Java provider
Using
the WSIF providers