You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Gurkan Erdogdu (JIRA)" <ji...@apache.org> on 2010/01/20 23:52:54 UTC
[jira] Updated: (OWB-243) Ensure serialized access to conversation
scope by blocking or rejecting concurrent requests
[ https://issues.apache.org/jira/browse/OWB-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gurkan Erdogdu updated OWB-243:
-------------------------------
Affects Version/s: M3
Fix Version/s: M4
> Ensure serialized access to conversation scope by blocking or rejecting concurrent requests
> -------------------------------------------------------------------------------------------
>
> Key: OWB-243
> URL: https://issues.apache.org/jira/browse/OWB-243
> Project: OpenWebBeans
> Issue Type: Task
> Components: Context and Scopes
> Affects Versions: M3
> Reporter: Sven Linstaedt
> Assignee: Gurkan Erdogdu
> Fix For: M4
>
>
> According to the spec, section 6.7.4:
> The container ensures that a long-running conversation may be associated with at most one request at a time, by blocking
> or rejecting concurrent requests. If the container rejects a request, it must associate the request with a new transient conversation
> and throw an exception of type javax.enterprise.context.BusyConversationException from the restore view
> phase of the JSF lifecycle. The application may handle this exception using the JSF ExceptionHandler.
> As far as I digged into the code, this is not implemented yet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.