]
Antoine Sabot-Durand updated CDI-489:
-------------------------------------
Sprint: Sprint 1
NonexistentConversationException thrown at restore view or not?
---------------------------------------------------------------
Key: CDI-489
URL:
https://issues.jboss.org/browse/CDI-489
Project: CDI Specification Issues
Issue Type: Clarification
Components: Javadoc and API
Affects Versions: 1.2.Final
Reporter: Vsevolod Golovanov
Fix For: 2.0 .Final
The 1.0 spec says in 6.7.4:
{quote}If the propagated conversation cannot be restored, the container must associate
the request with a new transient conversation and throw an exception of type
javax.enterprise.context.NonexistentConversationException from the restore
view phase of the JSF lifecycle. The application may handle this exception using the JSF
ExceptionHandler.{quote}
1.1 and 1.2 just say:
{quote}
If the propagated conversation cannot be restored, the container must associate the
request with a new transient conversation and
throw an exception of type javax.enterprise.context.NonexistentConversationException.
{quote}
Yet the javadoc of NonexistentConversationException for both 1.1 and 1.2 says:
{quote}
If the propagated conversation cannot be restored, the container must associate the
request with a new transient conversation and throw an exception of type
NonexistentConversationException from the restore view phase of the JSF lifecycle.
{quote}
So is it supposed to be thrown from restore view or not? I assume not. Probably javadoc
should be amended.
I'm curious about reasoning behind the change. I tried searching for an explanation
but didn't find anything.