[
https://issues.jboss.org/browse/WELD-1070?page=com.atlassian.jira.plugin....
]
Lincoln Baxter III commented on WELD-1070:
------------------------------------------
The proper JSF order is to change the specification to use a Servlet Filter instead of a
Phase Listener. Otherwise, if Seam Catch is using a Phase Listener or Filter to handle
these things, we're out of luck because if it's a:
1. PhaseListener - we could maybe use the <order> tag in faces-config.xml to change
order relative to Weld ... but, well... Weld is provided by the container, and I'm not
sure it works in that case.
2. ServletFilter - this is just flat out of reach of the JSF lifecycle, and the
WeldPhaseListener has no choice but to close early.
This is a defective / poorly thought out piece of the specification. I believe it's
being addressed in 1.1.
WeldPhaseListener destroys conversation too soon
------------------------------------------------
Key: WELD-1070
URL:
https://issues.jboss.org/browse/WELD-1070
Project: Weld
Issue Type: Bug
Components: Conversations
Affects Versions: 1.1.4.Final
Environment: gentoo, java 1.6, AS7.1.0.Beta1, Seam 3.1.0.Final
Reporter: Bernard Labno
In JSF app when exception is thrown during RenderResponse phase then firstly there is a
call to afterPhase and later to exception handlers.
WeldPhaseListener.afterPhase is invoked before error handler (Seam Catch in my case). My
error handler wants to promote conversation to long-running and do redirect to error page,
but conversation context is not active anymore now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira