Hi Christopher,
"Simple" as opposed to "non-composite" identity in JPA sense. Simply
speaking, it's a primary key that corresponds to single persistent field or
property of the entity class. So what I was asking was does the following
work:
public class A {
@Id
private long id;
}
or
public class B {
@Id
private BigDecimal id;
}
Thank you for the stack trace.
Few things to note
1. at
...ReflectingPersistenceCapable.pcNewObjectIdInstance(ReflectingPersistenceCapable.java:277)
at
org.apache.openjpa.util.ApplicationIds.create(ApplicationIds.java:421)
Apparently the Java persistent domain classes are being "enhanced" at
runtime. If the environment permits, I will highly recommend to switch to
build-time enhancement [1].
OpenJPA manages user domain objects by "enhancing" their bytecode. While
this bytecode enhancement can be triggered via different means and at
different time points -- the reliable/stable means is to run a
post-compilation command on the normally compiled classes to "enhance" them.
Build-time enhancement will help to focus on the "real" Scala-JPA
integration issues rather than chasing OpenJPA problems introduced by
non-build-time enhancement techniques.
If switching to build-time enhancement does not resolve the problem, (or
even otherwise) please post further outcome/progress of your interesting
project.
[1]
http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_pc_enhance_build
-----
Pinaki
--
View this message in context:
http://openjpa.208410.n2.nabble.com/identity-class-IllegalArgumentException-tp5159262p5160183.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
