[
https://issues.jboss.org/browse/WFLY-238?page=com.atlassian.jira.plugin.s...
]
Eduardo Martins commented on WFLY-238:
--------------------------------------
I think it's better to have thread pools configuration on threads subsystem, and only
have jsr 236 very specifics on EE, i.e. what kind of invocation contexts to propagate,
allow setting more than the specs required default resources, which btw the spec
recommended to stay on specific jndi names.
IMHO we should not even waste time right now with anything to configure on EE, and only
provide the default resources, using shared specific thread pools (these are configurable
on threads).
Thread pool configuration in EE subsystem
-----------------------------------------
Key: WFLY-238
URL:
https://issues.jboss.org/browse/WFLY-238
Project: WildFly
Issue Type: Sub-task
Components: EE
Reporter: David Lloyd
Assignee: Eduardo Martins
Fix For: 8.0.0.Alpha2
The EE subsystem should allow for thread pool configurations which are named and bound
into JNDI.
By default the binding name should probably not impinge upon standard namespaces. A good
default name would be {{java:jboss/threadpool/xxx}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira