[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1281) Support setting executor in CoyoteInvoker

[Ron Sigal (JIRA)]

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

Ron Sigal commented on JBREM-1281:
----------------------------------

Unit test: org.jboss.test.remoting.transport.coyote.SetAttributeTestCase.

> Support setting executor in CoyoteInvoker
> -----------------------------------------
>
>                 Key: JBREM-1281
>                 URL: https://issues.jboss.org/browse/JBREM-1281
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.4
>            Reporter: Justin Bertram
>            Assignee: Ron Sigal
>             Fix For: 2.2.4.SP1
>
>
> In Tomcat 5.5 org.apache.coyote.http11.Http11Protocol [1] inherited its getters and setters from org.apache.coyote.http11.Http11BaseProtocol [2] and one could set "minSpareThreads" and "maxSpareThreads" directly.  However, in Tomcat 6.0 [3] there is a new setExecutor method which takes a java.util.concurrent.Executor (i.e. not a String or a primitive like the other setters).  The org.jboss.remoting.transport.coyote.CoyoteInvoker.setProperty(..) method doesn't support this.
> [1] http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/coyote/http11/Http11Protocol.html
> [2] http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/coyote/http11/Http11BaseProtocol.html
> [3] http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/coyote/http11/Http11Protocol.html

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