I am having some issues with mappings in embeddables and I think this is because of bugs.
The test in eclipselink-embeddable-map-mapping-issue.zip shows that when having a ManyToMany map mapped in an embeddable, a NPE is raised during EntityManagerFactory building. Since mapping other relations works in embeddables I suppose this is a bug.
The test in eclipselink-tpc-mapping-issue.zip shows a bug regarding table per class inheritance. The base class(Person) contains an embeddable(Contact) and has 2 subclasses(Employee, Manager). A ManyToOne in the embeddable is correctly interpreted as the column gets added to the subclass tables in the generated sql. The problem now is the inverse OneToMany relation in the embeddable which should use the same column. I tried to map it via mappedBy="contact.alertContact" as well as via a JoinColumn but I couldn't get it to work. EclipseLink always assumes that there is a table person which contains the join column. I would expect EclipseLink to use the union over all subclass tables to join the relation.
Can anyone confirm these bugs? I'd like them fixed as I need such kinds of mappings.
You might be better off filing each as bugs, and then posting separate threads detailing the issues and linking to the bugs. Presenting two zip files as bugs requires a bit more involvement than many might be willing to give on a forum.