Assembling applications that use concurrency
Resource environment references to managed executors, thread factories, and context services must be bound to a physical work manager by using an assembly tool.
Before you begin
Optionally, your administrator can configure at least one work manager or adjust the settings of the default work manager by using the administrative console.
About this task
If your application references one or more logical managed executors, thread factories, context services, or work managers, they must be bound to one or more physical work managers by using an assembly tool.
The Asynchronous Beans and CommonJ 1.1 interfaces are deprecated. Concurrency Utilities for Java EE, asynchronous beans, and CommonJ interfaces can use one configuration work manager object. The type of interface that is implemented is resolved during the JNDI lookup time. The type of interface used is determined by the one specified in the resource-env-reference or resource-reference, instead of the one specified in the configuration object. Each resource-env-reference or resource-reference lookup returns the appropriate type of instance. For example, wm/MyWorkManager has two resource-references defined: concurrent/MyExecutor and wm/CommonJWorkMgr. The product run time returns the correct interface for each resource-env-reference or resource-reference lookup.