Community
Participate
Working Groups
To be consistent with bottom-up support, and also using the best practice for compound key classes... @Embeddable needs to be used.
That makes sense, but it might be too late to make this change for 2.0. Copying Dimiter so he can take a look.
I thought about embeddable ID class generation, but leave it because it generation seems to be separated process. EmbeddedId class consists of fields/properties, not introduced in entity itself, so in my opinion there are (mainly) two approaches to provide support for it generation: 1. Different wizard for the creation of Embeddable object intended to be EmbeddedId. After this generation, it could be allowed to be set as PK in the entity wizard 2. Additional page in entity wizard, for EmbeddedId settings. This approach seems to be clearer, but my fear is that Entity wizard will become very intricate with all these settings However I agree that the request make sense and it would be fine to be implemented for the next release. In this context every comments/notes above my thoughts, as well as every new proposal for support of Embeddable objects as PK will be appreciated
Moving JPA specific bugs to new JPA component in bugzilla.
