[jboss-jira] [JBoss JIRA] Commented: (JBAS-9264) BoundedQueueThreadPoolService provides Executor instead of ExecutorService

[David Lloyd (JIRA)]

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

David Lloyd commented on JBAS-9264:
-----------------------------------

It's just the way the services shook out.  Really none of them *should* provide a service, unless it's locked down (in which case all of them *could*).  If however you want to change it so they all expose ExecutorService (or BlockingExecutorService as the case may be) via the delegate methods in Executors, I'd accept that patch.

> BoundedQueueThreadPoolService provides Executor instead of ExecutorService
> --------------------------------------------------------------------------
>
>                 Key: JBAS-9264
>                 URL: https://issues.jboss.org/browse/JBAS-9264
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 7.0.0.Beta2
>            Reporter: Paul Ferraro
>
> Currently, there is no thread service that provides a j.u.c.ExecutorService using a bounded queue thread pool.
> The existing BoundedQueueThreadPoolService only provides a j.u.c.Executor, instead of the far more useful j.u.c.ExecutorService.  The exposed j.u.c.Executor cannot even be cast to an j.u.c.ExecutorService, since the underlying QueueExecutor is wrapped by a decorator that does not implement j.u.c.ExecutorService.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira