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
            Reporter: Sven Linstaedt
            Assignee: Gurkan Erdogdu


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.

Reply via email to