Thank you for your answer, but maintaining two entities graph just for some GeneratedValue annotations is an huge workload. We have a fallback solution, but not very user friendly; Instead of writing this : @Id @GeneratedValue // with <property name="openjpa.Sequence" value="aaaa.bbbb.MyTimestampGenerator"/> private long id;
We wrote : @Id private long id = MyTimestampGenerator.next(); // Synchronized statical method to get a new Id. However, a most proper solution will may be to provide an new OpenJPA property that allows to bypass or not the presence of an existing ID value for an annoted field with GeneratedValue. We can reflect on this option, except if there is another way. Regards
