Hi Pinaki,
We use the maven downloaded jar release 422266:935683 from 22-Apr-2010,
so we don't have the patch for the MappedSuperClass.
I didn't find a recent 2.0.0-SNAPSHOT on
http://people.apache.org/maven-snapshot-repository/ nor on
https://repository.apache.org/index.html.
Will try with 2.1.0-SNAPSHOT.
The entites can be found here:
[1] AbstractJPAMessage
http://svn.apache.org/viewvc/james/imap/trunk/jpa/src/main/java/org/apache/james/imap/jpa/mail/model/AbstractJPAMessage.java?view=markup
[2] JPAHeader
http://svn.apache.org/viewvc/james/imap/trunk/jpa/src/main/java/org/apache/james/imap/jpa/mail/model/JPAHeader.java?view=markup
[3] JPAProperty
http://svn.apache.org/viewvc/james/imap/trunk/jpa/src/main/java/org/apache/james/imap/jpa/mail/model/JPAProperty.java?view=markup
[4] JPAMessage
http://svn.apache.org/viewvc/james/imap/trunk/jpa/src/main/java/org/apache/james/imap/jpa/mail/model/JPAMessage.java?view=markup
[5] JPAStreamingMessage
http://svn.apache.org/viewvc/james/imap/trunk/jpa/src/main/java/org/apache/james/imap/jpa/mail/model/openjpa/JPAStreamingMessage.java?view=markup
Tks,
Eric
On 06/23/2010 07:04 PM, Pinaki Poddar wrote:
Hi,
The "mappedBy" mapping on abstract class should work and the relations need
not be redefined in the concrete subclass.
But a critical bug on MappedSuperclass had been found recently -- which *may
be* impacting the mapping.
1. Which OpenJPA revision being used?
$ java -jar /path/to/openjpa.jar
shows the revision number.
2. If the used revision is prior to 952893 (dated June 8,2010), is it
possible to switch to a post-952893 version and see if that resolves the
issue?
3. Can you please post the relevant entity classes (JPAMesaage etc.) for
further analysis?
-----
Pinaki
