You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (JIRA)" <ji...@apache.org> on 2009/10/30 05:01:59 UTC

[jira] Commented: (OPENJPA-1306) Extended lock scope support

    [ https://issues.apache.org/jira/browse/OPENJPA-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771761#action_12771761 ] 

Albert Lee commented on OPENJPA-1306:
-------------------------------------

Outstanding issues resolved and clarified in the current level of the spec.

The current mixed lock manager is a super set implementation of the required extended lock scope semantics, meaning requested pessimistic mode locks more than required by the extended lock scope definition. There are a few usage cases require additional locking to the join table in order to meet the extended lock scope requirement. In other use cases, optimization can be performed to minimize "un-needed" locks on relationship and collection elements to improve concurrency. The later case is not required in order to be spec compliance but can be considered as improvement in the future. All these additional semantics will only be applied iff mixed lock manager (JPA2) is used and extended lock scope is specified.


> Extended lock scope support
> ---------------------------
>
>                 Key: OPENJPA-1306
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1306
>             Project: OpenJPA
>          Issue Type: Sub-task
>            Reporter: Albert Lee
>            Assignee: Albert Lee
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.