Internal Website Search

could be valid if TCStep would be defined as @Embeddable rather than as @

of their type. If you mean that declaring the embeddable class as transient causes problems

an embeddable object that is references twice.   support Support >

as entity again (just for the query) and then back to embeddable. Alternatively, probably

;  em.getMetamodel().embeddable(FileNameDTO.class);        

Hi! I have the following persistence.xml. The problem is that ObjectDB loads all the classes in P1 (+ their embeddable classes). P2 is created properly, but P1 gets all entity classes (from P2 also). How can this be avoided, so that both P1 and P2 get just the classes

TempPhysicalPartDetails physicalPartDetails; }   @Embeddable

Hi there, The upgrade to 2.4.1_02 fixed the initial problem, however there still seems to be an issue. To me it appears that Embeddable might be being lazy loaded, but I cannot be sure. I have attached a testcase demonstrating this issue. Its failing on the merge.

; ... } @Embeddable public class LocalizedValues implements Serializable { ... @ElementCollection // lazy

Added an option to exclude inherited @Id fields in embeddable classes.