You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2010/06/30 22:55:49 UTC
[jira] Created: (OPENJPA-1714) Consider openjpa.Optimistic setting
when calculating the default lock mode to apply to a named query
Consider openjpa.Optimistic setting when calculating the default lock mode to apply to a named query
----------------------------------------------------------------------------------------------------
Key: OPENJPA-1714
URL: https://issues.apache.org/jira/browse/OPENJPA-1714
Project: OpenJPA
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Rick Curtis
Assignee: Jeremy Bauer
Fix For: 2.0.1, 2.0.0
See OPENJPA-1604 for background.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1714) Consider openjpa.Optimistic setting
when calculating the default lock mode to apply to a named query
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1714:
----------------------------------
Fix Version/s: 2.1.0
(was: 2.0.0)
> Consider openjpa.Optimistic setting when calculating the default lock mode to apply to a named query
> ----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1714
> URL: https://issues.apache.org/jira/browse/OPENJPA-1714
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Rick Curtis
> Assignee: Jeremy Bauer
> Fix For: 2.0.1, 2.1.0
>
> Attachments: OPENJPA-1714_2.0.x.patch
>
>
> See OPENJPA-1604 for background.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1714) Consider openjpa.Optimistic setting
when calculating the default lock mode to apply to a named query
Posted by "Michael Dick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick updated OPENJPA-1714:
----------------------------------
Attachment: OPENJPA-1714_2.0.x.patch
Attaching (renamed) patch from Jeremy Bauer. Jeremy originally granted a license to the ASF for inclusion in ASF works.
> Consider openjpa.Optimistic setting when calculating the default lock mode to apply to a named query
> ----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1714
> URL: https://issues.apache.org/jira/browse/OPENJPA-1714
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Rick Curtis
> Assignee: Jeremy Bauer
> Fix For: 2.0.0, 2.0.1
>
> Attachments: OPENJPA-1714_2.0.x.patch
>
>
> See OPENJPA-1604 for background.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1714) Consider openjpa.Optimistic setting
when calculating the default lock mode to apply to a named query
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1714.
-----------------------------------
Resolution: Fixed
> Consider openjpa.Optimistic setting when calculating the default lock mode to apply to a named query
> ----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1714
> URL: https://issues.apache.org/jira/browse/OPENJPA-1714
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Rick Curtis
> Assignee: Jeremy Bauer
> Fix For: 2.0.1
>
> Attachments: OPENJPA-1714_2.0.x.patch
>
>
> See OPENJPA-1604 for background.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1714) Consider openjpa.Optimistic setting
when calculating the default lock mode to apply to a named query
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1714:
----------------------------------
Fix Version/s: (was: 2.1.0)
> Consider openjpa.Optimistic setting when calculating the default lock mode to apply to a named query
> ----------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1714
> URL: https://issues.apache.org/jira/browse/OPENJPA-1714
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Rick Curtis
> Assignee: Jeremy Bauer
> Fix For: 2.0.1
>
> Attachments: OPENJPA-1714_2.0.x.patch
>
>
> See OPENJPA-1604 for background.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.