This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I'm studying for the JPA certification and while reading a book I encountered the following:
If instead of a many-to-many relationship we had an @ElementCollection of some embeddable type in a Map, we would have to differentiate between the key and the value. We would do this by prefixing the attribute name with "key." or "value.", depending upon which of the embeddable types we were overriding. An element collection of embedded EmployeeInfo types, with the same key overrides as those in the relationship in Listing 5-17, would use the key prefixes:
But I could not understand how a relationship with a real entity could be replaced by this kind of relationship with embeddable types id there is no information about any collection table or any table within the embeddable. I'm kind confused about element collections, I don't know if it's the book that I've bought but it sounds weird sometimes. Does anyone know what the quote above could mean?
Feel free to ask me anything!
www.BlackBeltFactory.com/ui#!/ref=jmotta, SCJP 6, OCWCD JEE5, OCE EJB JEE6
It is trying to convey (only) that if an ElementCollection has both a key and a value that is an Embeddable, then the AttributeOverride is ambiguous, does it apply to the key or the value?
So, it is saying that if you had this (odd) situation, you would use the "key" prefix to override the key, and "value." apply to the value. Actually this is news to me, I assume it is defined this way in the Spec though if this book mentions it.