[
https://issues.jboss.org/browse/JBAS-8294?page=com.atlassian.jira.plugin....
]
William Draï updated JBAS-8294:
--------------------------------
Attachment: weld-deployer.patch
weld-int-deployer.jar
Here is a very trivial patch to apply to jbossas/weld-int that marks the weld servlet
ConversationPropagationFilter as async supported.
It works with my example project. I don't have enough time right now to extract a
simple test project but maybe Richard can check if it works for him. I've also
attached the modified weld-int-deployer.jar that shoud be put in
deployers/weld.deployer/.
Weld & Asynchronous servlets on JBoss 6.0 M2
--------------------------------------------
Key: JBAS-8294
URL:
https://issues.jboss.org/browse/JBAS-8294
Project: JBoss Application Server
Issue Type: Bug
Components: Weld/CDI
Reporter: William Draï
Fix For: TBD
Attachments: weld-deployer.patch, weld-int-deployer.jar
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.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira