Re: PCEnhancer and MappedSuperclass problem???

FWIW, if I remove the inheritance of the MappedSuperclass, the enhancer has no trouble with my application and things operate as they should. This seems to indicate that there is a problem with enhancing inheritance heirarchies, and certainly looks to have something to do with cycle detection,

Re: Doing without Persistence.xml

bdh wrote: > > first question I have: is it possible to run without the persistence.xml > file? > I have the same question. I have had great success using JPA with my web apps where I can easily control the backend. However, for the swing app I am writing now the user needs to be able to sp

Re: OutOfmemory Error

I have similar issue with openjpa 1.0.2, so i'm using 1.0.1. B. [EMAIL PROTECTED] wrote: I just switch to OpenJPA from the kodo version (0.9.6). I am enhancing the class using the open jpa enhancer now and I get an OutOfMemory Exception. This is the exact same code as before with kodo. What i

equals and hashCode methods

I put a superclass on all my entities for a couple of general properties that they all share, and now I'm considering putting my equals() and hashCode() methods into the superclass as well, with reflection to loop over the array of child methods, calling whatever POJO getters are present. The

OutOfmemory Error

I just switch to OpenJPA from the kodo version (0.9.6). I am enhancing the class using the open jpa enhancer now and I get an OutOfMemory Exception. This is the exact same code as before with kodo. What is going on - am I missing some parameters? Here is my new target...

Re: JPA update entities every (even empty) commit

Hi Georgi, openJPA 1.0.1 does this, but I'm not sure if it is right behaviour. Toplink doesn't call update on unchanged entities, on the other hand it calls update on entity planned to be removed. Bardolf Georgi Naplatanov wrote: Hello, everybody. Is the update on unchanged entities within

Re: Is INNER JOIN necessary with ORDER BY?

Hi Ognjen, As I understand the JPA specification, your analysis and solution are correct. By the specification, navigating a relationship uses inner join semantics. By the way, JDO uses outer join semantics in query navigation. With JDO, you would get Persons with null id_place_of_birth u

Doing without Persistence.xml

I'm new to OpenJPA and have looked in the docs and have searched this forum. Apologies if I missed other posting on this. I'm working on an Eclipse RCP application and would like to not bother with the persistence.xml file and provide all the configuration through the properties provided to the e

Is INNER JOIN necessary with ORDER BY?

Hi all, How can I avoid INNER JOINs to be generated for tables stated in ORDER BY clause? For instance, EJB QL select p from Person p order by p.idPlaceOfBirth.name results in SQL which INNER JOINS Person and Place, and the persons without known place of birth (id_place_of_birth ==

Re: JPA update entities every (even empty) commit

Hello, everybody. Is the update on unchanged entities within transaction the right behavior ? It's very important for my applications. I wrote the following example and all selected entities were updated : factory = Persistence.createEntityManagerFactory("",System.getProperties()) ; em =