[jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-3991) Asynchronous HTTP support in Seam+RESTeasy

[Christian Bauer (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Bauer reassigned JBSEAM-3991:
---------------------------------------

    Assignee: Christian Bauer


> Asynchronous HTTP support in Seam+RESTeasy
> ------------------------------------------
>
>                 Key: JBSEAM-3991
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3991
>             Project: Seam
>          Issue Type: Feature Request
>          Components: WS
>    Affects Versions: 2.1.1.GA
>            Reporter: Balazs Pataki
>            Assignee: Christian Bauer
>             Fix For: 2.2.0.CR1
>
>
> There should be support for handling asynchronous HTTP connections in a way similar to the plain RESTeasy solution:
> http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.0.2.GA/userguide/html/Asynchronous_HTTP_Request_Processing.html
> It actually seems very straightforward to implement it in Seam, the only problem is that there needs to be 3 different implementations for Tomcat6+JBoss 4.2.x, JBoss 5, and Servlet 3. At least, in RESTeasy it is implemented this way.
> For me I took the Tomcat6+JBoss 4.2.x implementation of org.jboss.resteasy.plugins.server.servlet.Tomcat6CometDispatcherServlet and based on this I added "implements CometProcessor" to ResteasyDispatcher + copied the event() and createHttpRequest() methods over from Tomcat6CometDispatcherServlet . Then I also added ResteasyAsyncHttpRequest, which is a clone of org.jboss.resteasy.plugins.server.servlet.Tomcat6AsyncHttpRequest. With this setup plus adding the
> <Connector port="8080" address="${jboss.bind.address}"
>    emptySessionPath="true" protocol="org.apache.coyote.http11.Http11NioProtocol"
>    enableLookups="false" redirectPort="6443" acceptorThreadCount="2" pollerThreadCount="10"
> />
> connector instead of the vanilla one to JBOSS_HOME/server/default/deploy/jboss-web.deployer/server.xml seem to make it all work form me.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira