[
https://jira.jboss.org/jira/browse/WELDINT-44?page=com.atlassian.jira.plu...
]
William Draï commented on WELDINT-44:
-------------------------------------
Just to confirm that asynchronous servlet 3 do work correctly when the
ConversationPropagationFilter filter is commented out from
org.jboss.weld.integration.deployer.metadata.PostWebMetadataDeployer.
Weld & Asynchronous servlets on JBoss 6.0 M2
--------------------------------------------
Key: WELDINT-44
URL:
https://jira.jboss.org/jira/browse/WELDINT-44
Project: Weld Integration
Issue Type: Bug
Reporter: William Draï
Assignee: Pete Muir
Weld seems to break asynchronous servlets 3 (new in JBossWeb). I think it's because
the Weld/JBoss integration maps all requests to the ConversationPropagationFilter that is
not marked async-supported .
Strangely this filter is not applied to servlets implementing HttpEventServlet but
it's probably a normal JBossWeb behaviour.
Besides that I'm not in a JSF environment so I don't need this conversation
propagation, is there any way to disable this filter ?
--
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