The Bean Invoker Factory consists of three parts: the bean invoker pool, the bean proxy cache, and the bean invoker registry. The bean invoker pool caches the invokers, the bean proxy cache caches the bean proxies, and the bean invoker registry provides paths to the resource bundles that are critical to the creation of invokers. For information on how these three parts work together, see How the Bean Invoker Factory works.
Invokers are what the Bean Invoker Factory returns to the requester so that the requester can invoke the business processes or Single Action EJBs in the application logic layer. Each invoker is associated with a request ID to indicate what kind of transaction this invoker can invoke. An invoker can only invoke one specific Single Action EJB to perform a specific activity.
The bean invoker pool caches invokers that the Bean Invoker Factory created for earlier requests. When a requester asks for an invoker that is already in the bean invoker pool, the Bean Invoker Factory simply retrieves this invoker from the pool instead of creating a new one.
The bean invoker pool empties when you restart the WebSphere(R) Application Server on which you deploy the Bean Invoker Factory.
You must set a bean proxy for your invoker before the Bean Invoker Factory returns the invoker to the requester. Each bean proxy is associated with a request ID and a session ID. One bean proxy can only serve invokers with the same request ID.
The bean proxy cache caches bean proxies that the Bean Invoker Factory created for earlier requests. Since bean proxies are associated with session IDs, requests of different sessions cannot reuse the same bean proxy. When a request asks for a bean proxy that is already in the bean proxy cache, the Bean Invoker Factory simply retrieves this bean proxy from the Cache instead of creating a new one.
The bean proxy cache empties when you restart the WebSphere Application Server on which you deploy the Bean Invoker Factory.
The bean invoker registry provides a mapping between the request IDs and resource bundles containing information for bean invoker creation. When it needs to create an invoker for a request, the Bean Invoker Factory finds the corresponding resource bundle through the Registry to create the invoker.