[jira] [Commented] (OPENJPA-2439) Improving compliance to Java 5+

2013-10-24 Thread Guillaume Chauvet (JIRA)
[ https://issues.apache.org/jira/browse/OPENJPA-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804036#comment-13804036 ] Guillaume Chauvet commented on OPENJPA-2439: My only(paranoid) concern with

[jira] [Updated] (OPENJPA-2443) InvalidStateException while merging a new Entity with a GeneratedValue id

2013-10-24 Thread Rick Curtis (JIRA)
[ https://issues.apache.org/jira/browse/OPENJPA-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Curtis updated OPENJPA-2443: - Fix Version/s: 2.4.0 2.3.0 InvalidStateException while merging a new

[jira] [Commented] (OPENJPA-2443) InvalidStateException while merging a new Entity with a GeneratedValue id

2013-10-24 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/OPENJPA-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804184#comment-13804184 ] ASF subversion and git services commented on OPENJPA-2443: --

[jira] [Commented] (OPENJPA-2443) InvalidStateException while merging a new Entity with a GeneratedValue id

2013-10-24 Thread Rick Curtis (JIRA)
[ https://issues.apache.org/jira/browse/OPENJPA-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804186#comment-13804186 ] Rick Curtis commented on OPENJPA-2443: -- I merged the changes back to 2.3.x.

[jira] [Resolved] (OPENJPA-2443) InvalidStateException while merging a new Entity with a GeneratedValue id

2013-10-24 Thread Rick Curtis (JIRA)
[ https://issues.apache.org/jira/browse/OPENJPA-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Curtis resolved OPENJPA-2443. -- Resolution: Fixed InvalidStateException while merging a new Entity with a GeneratedValue id

Question about orm.xml

2013-10-24 Thread Mark Struberg
Looking at really old stuff atm which kind of randomly breaks tests. In this case it's the openjpa-persistence-jdbc TestUseSchemaElement which recently got added. This leaves a file 'orm.xml' on the root or openjpa-persistence-jdbc. And if you run the tests a second time, then the test above

PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Dear OpenJPA Dev Team, I am getting this exception https://raw.github.com/kwrobel/OpenJPA-IntExceptionTest/master/OpenJPA-IntExceptionTest/DiscountCode-Exception.txt while reading a simple entity DiscountCode from a Derby database called SAMPLE (ships with Glassfish/NetBeans) called

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Mark Struberg
My finding so far is that the DerbyDictionary doesn't overwrite storeCharsAsNumbers, so it's still defaulted to true. This code is exactly which trashes in the sample Caused by: java.sql.SQLDataException: Invalid character string format for type int.         at

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
I have to make a correction to the last statement in my original post: The content values of DISCOUNT_CODE field are /*not*/ of numeric value, but actual characters, such as 'H' or 'M'. Sorry for causing confusion. On 10/24/2013 03:17 PM, Mark Struberg wrote: My finding so far is that the

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Rick Curtis
As I suggested on IRC earlier this week, try setting the following property to see if it makes things work... property name=openjpa.jdbc.DBDictionary value=derby(storeCharsAsNumbers=false/ If it doesn't work, enable trace and let us take a peek. property name=openjpa.Log value=DefaultLevel=trace/

Re: Question about orm.xml

2013-10-24 Thread Rick Curtis
I just came across this same problem earlier this week, but haven't gotten annoyed enough yet to dig into it. My uneducated gut feeling is that the problem is in the ReverseMappingTool. On Thu, Oct 24, 2013 at 2:43 PM, Mark Struberg strub...@yahoo.de wrote: Looking at really old stuff atm

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Hi Curtis. In that same IRC, I had set the property as you requested and still received the same error. But I will try again to be double-sure. Kay On 10/24/2013 03:42 PM, Rick Curtis wrote: As I suggested on IRC earlier this week, try setting the following property to see if it makes

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Are you sure value is derby(storeCharsAsNumbers=false??? That looks wrong somehow. The ( in there. On 10/24/2013 03:42 PM, Rick Curtis wrote: As I suggested on IRC earlier this week, try setting the following property to see if it makes things work... property name=openjpa.jdbc.DBDictionary

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Ahhh. Ok, so that line should read: property name=openjpa.jdbc.DBDictionary value=storeCharsAsNumbers=false/ Now that got rid of the exception and the program continues without errors. That now begs the question Mark raised earlier about assuming Chars to be of numeric content. I would say,

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Rick Curtis
Sorry, I wrote that quickly yes it was missing a ')'. If that doesn't work, please collect trace. property name=openjpa.jdbc.DBDictionary value=derby( storeCharsAsNumbers=false)/ On Thu, Oct 24, 2013 at 3:50 PM, Kay Wrobel kay.wro...@gmx.net wrote: Are you sure value is

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
I just confirmed the problem also had existing using MySQL. I recreated the table and records for DISCOUNT_CODE in a MySQL database and had the same exception and the property setting (both versions) got rid of the error. Still, this should default to false imho. On 10/24/2013 04:17 PM, Kay

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Mark Struberg
I agree. Can you please create a JIRA? LieGrue, strub - Original Message - From: Kay Wrobel kay.wro...@gmx.net To: dev@openjpa.apache.org Cc: Sent: Thursday, 24 October 2013, 23:20 Subject: Re: PersistenceException: Invalid character string format for type int I just

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Ja, I actually used: property name=openjpa.jdbc.DBDictionary value=storeCharsAsNumbers=false/ and that works as well. On 10/24/2013 03:54 PM, Rick Curtis wrote: Sorry, I wrote that quickly yes it was missing a ')'. If that doesn't work, please collect trace. property

[jira] [Commented] (OPENJPA-2444) ReverseMappingTool creates orm.xml files in the current working directory

2013-10-24 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/OPENJPA-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804699#comment-13804699 ] ASF subversion and git services commented on OPENJPA-2444: --

[jira] [Created] (OPENJPA-2444) ReverseMappingTool creates orm.xml files in the current working directory

2013-10-24 Thread Mark Struberg (JIRA)
Mark Struberg created OPENJPA-2444: -- Summary: ReverseMappingTool creates orm.xml files in the current working directory Key: OPENJPA-2444 URL: https://issues.apache.org/jira/browse/OPENJPA-2444

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Rick Curtis
I agree. Can you please create a JIRA? -1 Unless there is a very compelling reason, I don't like changing a default value that has been that way since the beginning of time. On Thu, Oct 24, 2013 at 4:20 PM, Mark Struberg strub...@yahoo.de wrote: I agree. Can you please create a JIRA?

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Albert Lee
I would hesitate to change the default since nothing is broken. This DB property default has been around for a long time and if the default is changed, very likely it will break compatibility with application migrating to the changed release. Albert Lee. On Thu, Oct 24, 2013 at 4:20 PM, Mark

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Alright. I see everybody's predicament and understand the argument behind it. I myself have seen code that's 15+ years old and would feel the same way. That said, it would then be something that should maybe be pointed out somewhere in clear terms that this is the default behavior, and the

Re: PersistenceException: Invalid character string format for type int

2013-10-24 Thread Kay Wrobel
Opened my mouth too early. Pulled up the openjpa single-html manual and it's there, though tucked away in a list of properties and their explanations. I know it because I was looking for it. But it's like something you wouldn't normally assume. On 10/24/2013 04:53 PM, Kay Wrobel wrote: