MappedSuperclass goes only 1 level deep.
Key: OPENJPA-768
URL: https://issues.apache.org/jira/browse/OPENJPA-768
Project: OpenJPA
Issue Type: Bug
Affects Versions: 1.2.0
Environment: JBos
[
https://issues.apache.org/jira/browse/OPENJPA-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646724#action_12646724
]
Ignacio Andreu commented on OPENJPA-599:
Kevin,
Thnaks for your feedback and sorr
Thanks, David, for populating the repository and for your willingness to
handle commits.
The naming issue is quite a quandary. Would this approach (or derivation
of) work? a) Add a JPA 1.0 spec to the repo - this is not necessary, but
may be good for the sake of completeness. b) Use the new 2.0
Hello Milozs,
thanks for your reply. Maybe you are right, anyway, pls comment on my
scenario. There is nothing preventing T2 from commiting with a dirty read;
the lock() call doesen't even get the chance to be called.
Waiting for your opinion.
Miłosz Tylenda wrote:
>
> Vlad,
>
> Maybe the ci
we have to use 2.0-EA-SNAPSHOT!
At least '-SNAPSHOT' has to be at the end, because maven does handle snapshot
releases completely different than tagged final releases.
See [1], [2] + many more internal maven-details you do not want to know about ;)
LieGrue,
strub
[1] http://maven.apache.org/gl
On Nov 11, 2008, at 10:07 AM, Craig L Russell wrote:
On Nov 11, 2008, at 2:28 AM, Mark Struberg wrote:
--- David Jencks <[EMAIL PROTECTED]> schrieb am Di, 11.11.2008:
This points out the possible problem that the jpa 1.0 spec
appeared to be part of the ejb 3.0 spec so I gave it a spec
versi
On Tue, Nov 11, 2008 at 12:07 PM, Craig L Russell <[EMAIL PROTECTED]>wrote:
>
> On Nov 11, 2008, at 2:28 AM, Mark Struberg wrote:
>
> --- David Jencks <[EMAIL PROTECTED]> schrieb am Di, 11.11.2008:
>>
>>> This points out the possible problem that the jpa 1.0 spec
>>> appeared to be part of the ej
Hi Abe,
Is there a unit test that demonstrates what you fixed?
On Mon, Nov 3, 2008 at 12:36 AM, <[EMAIL PROTECTED]> wrote:
> Author: awhite
> Date: Sun Nov 2 22:36:49 2008
> New Revision: 710015
>
> URL: http://svn.apache.org/viewvc?rev=710015&view=rev
> Log:
> Use full table name according to
Hi Pinaki, do you have any unit tests for this change?
On Mon, Nov 10, 2008 at 3:35 PM, <[EMAIL PROTECTED]> wrote:
> Author: ppoddar
> Date: Mon Nov 10 13:35:35 2008
> New Revision: 712842
>
> URL: http://svn.apache.org/viewvc?rev=712842&view=rev
> Log:
> OPENJPA-764: Parse IN expressions with st
Better OSGi Integration
---
Key: OPENJPA-767
URL: https://issues.apache.org/jira/browse/OPENJPA-767
Project: OpenJPA
Issue Type: New Feature
Components: third-party
Affects Versions: 1.3.0
Report
On Nov 11, 2008, at 2:28 AM, Mark Struberg wrote:
--- David Jencks <[EMAIL PROTECTED]> schrieb am Di, 11.11.2008:
This points out the possible problem that the jpa 1.0 spec
appeared to be part of the ejb 3.0 spec so I gave it a spec
version number of 3.0. Any suggestions about what to do
abou
Vlad,
Maybe the cited sentence is not correct? It says:
> The lock() API acquires an optimistic lock, not a pessimistic lock. It means
> that the version will be checked, or updated on commit, it does not matter
> when it is called in the transaction, as the check occurs on commit
But if you re
[
https://issues.apache.org/jira/browse/OPENJPA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar reassigned OPENJPA-766:
-
Assignee: Pinaki Poddar
> Tests that currently fail should be committed to the repositor
[
https://issues.apache.org/jira/browse/OPENJPA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pinaki Poddar resolved OPENJPA-766.
---
Resolution: Fixed
The current commit fulfills the basic purpose. Further enhancement can be
[
https://issues.apache.org/jira/browse/OPENJPA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646598#action_12646598
]
Pinaki Poddar commented on OPENJPA-766:
---
The tests can now be annotated with followi
Tests that currently fail should be committed to the repository
---
Key: OPENJPA-766
URL: https://issues.apache.org/jira/browse/OPENJPA-766
Project: OpenJPA
Issue Type: Test
[
https://issues.apache.org/jira/browse/OPENJPA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-765:
-
Fix Version/s: (was: 1.2.0)
> Check for insertable or updateable before checking value for n
[
https://issues.apache.org/jira/browse/OPENJPA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-765:
-
Fix Version/s: 2.0.0
1.3.0
> Check for insertable or updateable before checki
[
https://issues.apache.org/jira/browse/OPENJPA-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-245:
-
Fix Version/s: 1.0.3
> Attach NEW and auto-increment identity
>
[
https://issues.apache.org/jira/browse/OPENJPA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick closed OPENJPA-765.
Resolution: Fixed
> Check for insertable or updateable before checking value for null
> --
right. When we do get to Jpa-3.0, we would just publish against a
version number that is late than what is currently there.. :)
And the reason you're seeing two directories for geronimo-spec is
probably because they changed the groupId of the artifacts. For
whatever reason.
So you might se
--- David Jencks <[EMAIL PROTECTED]> schrieb am Di, 11.11.2008:
> This points out the possible problem that the jpa 1.0 spec
> appeared to be part of the ejb 3.0 spec so I gave it a spec
> version number of 3.0. Any suggestions about what to do
> about this would be appreciated.
Do we really nee
On Nov 10, 2008, at 7:42 PM, Michael Dick wrote:
On Mon, Nov 10, 2008 at 6:34 PM, David Jencks
<[EMAIL PROTECTED]>wrote:
On Nov 10, 2008, at 1:13 PM, Craig L Russell wrote:
Hi Jeremy,
On Nov 10, 2008, at 12:12 PM, Jeremy Bauer wrote:
OpenJPA & Geronimo devs,
Efforts are underway to beg
23 matches
Mail list logo
