[jboss-jira] [JBoss JIRA] (WFLY-238) Thread pool configuration in EE subsystem

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780677#comment-12780677 ] 

David Lloyd commented on WFLY-238:
----------------------------------

So are you proposing that the configuration be associated with the JNDI binding of the thread pool, rather than the pool itself?  If so I think that wherever the thread pools are defined, the JNDI bindings with their associated configurations should be defined as nested resources within the thread pool definition.

I remind you again that the threads subsystem is slated for removal as soon as I can possibly get away with it, so I don't really like the idea of adding more dependents on it, nor do I like the idea of enhancing it any further.  Also, I'm not really sure we want to expose all the types of thread pools that the threads subsystem can provide; I'd rather limit it to just types that make sense.  Finally the threads subsystem defines a name for each thread pool in a way that is probably misleading in the context of EE thread pools, where the only name the user cares about is the JNDI name.
                
> 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