[
https://issues.jboss.org/browse/WFLY-4283?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on WFLY-4283:
------------------------------------
What we'll expose to users is a ManagedDistributedExecutorService which extends both
DistributedExecutorService and javax.enterprise.concurrent.ManagedExecutorService. This
will reside within a separate public org.wildfly.clustering.infinispan.api module. We
need to ensure that the proper contexts are propagated to the remote node on which the
executor will execute. Presumably, this is as simple as creating contextual proxies via
the ContextService, which the specification says should be serializable.
Expose DistributedExecutorService per cache to deployments
----------------------------------------------------------
Key: WFLY-4283
URL:
https://issues.jboss.org/browse/WFLY-4283
Project: WildFly
Issue Type: Feature Request
Components: Clustering
Affects Versions: 9.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
The general idea is to automatically install a service per cache that exposes a
DistributedExecutorService and expose it to users via jndi. Usage should be as simple
as:
{code}
@Resource(lookup = "java:jboss/infinispan/executor/server/default")
private DistributedExecutorService executor;
{code}
or
{code}
@Resource(lookup = "java:jboss/infinispan/executor/server/default")
private ExecutorService executor;
{code}
the latter does not require the user to export any modules to their deployment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)