problem with bulk update and @Version annotation

Hello, I'm facing a strange problem with the @Version Annotation with field property as Timestamp. With a bulk update I'll get the following error: javax.ejb.EJBException: The bean encountered a non-application exception; nSign outested exception is: org.apache.openjpa.persistence.ArgumentExcepti

Re: SAP MaxDB not supported?

Hi, I've committed the code changes and a section to the user manual. Could use the class name for the JDBC driver, and some version information for the manual, but function wise you should be good to go once we publish a new SNAPSHOT build. I downloaded the 2.1.0 snapshot and found the added

Re: SAP MaxDB not supported?

Hi, I think (haven't verified it) that you can use the base DBDictionary class - this might be closer to MaxDB than Oracle or HSQL. Which value i have to set for using the base DBDictionary class? One other thing you / we can do is open a JIRA for supporting MaxDB, and we can add a MaxDB di

Re: SAP MaxDB not supported?

Hi Michael/Rick, Minor clarification. OpenJPA does not include any support for MaxDB, regardless of whether you're generating tables or reading / updating data. Args. That doesn't mean that it won't work, but you are off the beaten path. ok, lets see. OpenJPA uses different DBDictionary

SAP MaxDB not supported?

Hi, i use OpenJPA(1.2.1) with OpenEJB(3.1.2). I know OpenJPA does not support automatic table creation from entities for SAP MaxDB. So i create the tables manually before using JPA. Using JPA for reading/manipulating table content works here perfectly even for SAP MaxDB many times. But yesterd

Re: updating a many to many relationship

Hi, This might be a bit late, but did you try the openjpa.InverseManagerproperty? thanks for the hint, but it doesn't work, totally. Assigning some groups to the user the first time works, but then after removing some groups, all groups are removed from the user during the update. public void

Re: updating a many to many relationship

Hi, The good news is i solved my problem, the bad one is its still much code needed to update a bi-directional ManyToMany relationship correctly. But it's in the nature of things. http://en.wikibooks.org/wiki/Java_Persistence/Relationships#Object_corruption.2C_one_side_of_the_relationship_is_

Re: updating a many to many relationship

Hi, Thanks for your reply, i am sorry about my failed discription of the problem. > Can you help clarify this usage and the expected behavior? I do my best. Yes its an EJB-method, but its called from a Swing GUI client application. In the GUI there is a dialog where an operator can edit a

updating a many to many relationship

Hi, I try to update a many to many relationship between a User and Group entity. Lets say the user is member of an additional group. A simple entityManager.merge(user) does not work cause in my case the User entity is not the owner-side. Ok, so i coded this: EJB method: // the user entity come

Re: MaxDB and OpenJPA

Hi, Joe I am not sure exactly what your question is, is it the "SchemaAction" or is it more generally the SynchronizeMappings property? Hm, i think the SchemaAction. If i understand it correctly it leads to a dropping of all tables, and after it to a recreation of the tables ba

MaxDB and OpenJPA

Hi, For unit tests i like to set the following property in the persistence.xml file: value="buildSchema(SchemaAction='dropDB,add')" /> This works for Derby and Oracle but it doesn't work for MaxDB. I looked at: http://openjpa.apache.org/builds/1.0.2/apache-openjpa-1.0.2/docs/manual/ref_g