Hi David,
On Jan 27, 2009, at 4:30 PM, David Jencks wrote:
If you guys are happy with the current state of the 2.0 persistence
api jar I'll see about starting a release vote tomorrow.
My reading of the spec leads me to think we're supposed to make it
very clear anything based on it is earl
If you guys are happy with the current state of the 2.0 persistence
api jar I'll see about starting a release vote tomorrow.
My reading of the spec leads me to think we're supposed to make it
very clear anything based on it is early access so I plan to use a
version number of 1.0-EA-1. Sug
Hi Hantone,
Could you post the nested exception from inside the RollbackException? There
should be a SQLException as the innermost nested exception that will shed
some light on the problem.
Thanks,
-mike
On Tue, Jan 27, 2009 at 11:16 AM, hantone wrote:
>
> Thanks in advance! I'm having a hard
Hi all,
There are two (AFAIK) outstanding questions regarding the new release.
1. Do we want / need a formal JIRA release for 2.0.0-M1. Jeremy and I
created one earlier today, but we'd have to manually reassign each JIRA
issue to the new release. Bulk updates overwrite the "fixed in" and
"afftect
OpenJPA committers,
An 2.0.0-M1 branch has been created (Thanks, Mike!) for the M1 release.
Commits can now resume on trunk.
Happy committing,
-Jeremy
On Mon, Jan 26, 2009 at 2:15 PM, Jeremy Bauer wrote:
> OpenJPA committers,
> OpenJPA 2.0 iteration 2 is wrapping up and preparations are beginn
[
https://issues.apache.org/jira/browse/OPENJPA-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-765:
-
Affects Version/s: 1.3.0
1.2.1
Fix Version/s: 2.0.0
[
https://issues.apache.org/jira/browse/OPENJPA-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick closed OPENJPA-831.
Resolution: Fixed
Closing on Jeremy's behalf
> OpenJPA 2.0 iteration 1.5 (holiday) primary task
>
[
https://issues.apache.org/jira/browse/OPENJPA-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick closed OPENJPA-800.
Resolution: Fixed
Closing on Jeremy's behalf.
> OpenJPA 2.0 iteration 1 primary task
>
[
https://issues.apache.org/jira/browse/OPENJPA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-807:
-
Affects Version/s: 2.0.0-M1
Fix Version/s: 2.0.0
2.0.0-M1
> OpenJ
[
https://issues.apache.org/jira/browse/OPENJPA-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick closed OPENJPA-807.
Resolution: Fixed
Closing on Jeremy's behalf
> OpenJPA 2.0 iteration 2 primary task
> ---
[
https://issues.apache.org/jira/browse/OPENJPA-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-831:
-
Affects Version/s: 2.0.0-M1
Fix Version/s: 2.0.0
2.0.0-M1
> OpenJ
[
https://issues.apache.org/jira/browse/OPENJPA-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-800:
-
Affects Version/s: 2.0.0-M1
Fix Version/s: 2.0.0
2.0.0-M1
> OpenJ
OpenJPA 2.0 iteration 4 primary task
Key: OPENJPA-875
URL: https://issues.apache.org/jira/browse/OPENJPA-875
Project: OpenJPA
Issue Type: New Feature
Affects Versions: 2.0.0
Reporter: Jere
[
https://issues.apache.org/jira/browse/OPENJPA-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667732#action_12667732
]
Catalina Wei commented on OPENJPA-846:
--
No additional test cases are needed for MySQL
Thanks in advance! I'm having a hard time with this so I would really
appreciate your help!
I'm having problems to commit a transaction
public class Main {
public static void main(String[] args) {
try {
EntityManager entityManager =
Persistence.cr
Thanks Kevin and Jeremy for helping to resolve OPENJPA-872.
Is there an outlook for an OpenJPA 1.2.1 release? Geronimo is going to
need a release prior to releasing Geronimo 2.1.4 and 2.2. I guess we
could consider using openjpa.jdbc.QuerySQLCache=false as a work-
around, but I'd rather avo
[
https://issues.apache.org/jira/browse/OPENJPA-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667719#action_12667719
]
Michael Dick commented on OPENJPA-846:
--
Do we need additional test cases for this iss
[
https://issues.apache.org/jira/browse/OPENJPA-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667718#action_12667718
]
Fay Wang commented on OPENJPA-838:
--
Test cases are checked in openjpa 1.2.x (r-738137) an
[
https://issues.apache.org/jira/browse/OPENJPA-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick reopened OPENJPA-873:
--
Assignee: Fay Wang
Reopening. Testcase needed.
> @MappedSuperClass Cause Null Pointer Exce
[
https://issues.apache.org/jira/browse/OPENJPA-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Kulik updated OPENJPA-874:
---
Description:
The mapping tool find tables in all available schemas if oracle user has DBA
privilege
Table generator uses incorrect schema name
--
Key: OPENJPA-874
URL: https://issues.apache.org/jira/browse/OPENJPA-874
Project: OpenJPA
Issue Type: Bug
Affects Versions: 1.1.0
Reporter:
[
https://issues.apache.org/jira/browse/OPENJPA-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Hardy resolved OPENJPA-496.
Resolution: Invalid
After investigation I discovered that it is in fact the JDBC SQL logging
pack
22 matches
Mail list logo
