A FetchInvokeEJB 3.0 service combines the functionality of the FetchEJB 3.0 and InvokeEJB 3.0 adapter services into one service. Services configured with this template fetch one or more instances of a single 3.0 EJB class and invoke a single method on those instances. Unlike FetchEJB 3.0, the remote EJB instances are not returned to the caller.

Use the FetchInvokeEJB 3.0 template when you want to create an adapter service that will retrieve an EJB, run a method on that bean, then release it. Because it does not return any Handle objects in its output, the lifecycle of the EJB is entirely contained within the bounds of the adapter service: the EJB is created, a single method is invoked and its output is captured. For this reason, a FetchInvokeEJB 3.0 service is not particularly useful with stateful session beans.

At design time, a FetchInvokeEJB 3.0 service requires the JNDI lookup name of the EJB to fetch and the identity the bean method to invoke. As with the other service templates, you may override the default names of any parameter used in remote method. See Configuring FetchInvokeEJB 3.0 Services for more information about the parameters.

In a FetchInvokeEJB 3.0 service's input signature, the document names used to contain EJB method arguments are pre-configured and localized. The input document name of the bean method is EJBObject_Args. The documents appear in the input signature only if the corresponding methods have any arguments.