Re: [hibernate-dev] overriding target through annotations

I agree with your analysis, but @MapKeyTarget vs @o.h.a.MapKey / @o.h.a.MapKeyManyToMany enhancement with target is not influenced by the @j.p.MapKey design flaws. Pros of each solution are 1. @MapKeyTarget SoC (Relational descriptions are split from Object descriptions in annotations) @Target and @MapKeyTarget are consistent 2. no @MapKeyTarget No extra @MapKeyTarget annotation Christian Bauer wrote: > > On Nov 29, 2006, at 9:23 PM, Emmanuel Bernard wrote: > >> Note that I hope the future spec will hopefully handle all cases >> nicely (ie add a targetElement in @Embedded), @MapKey should go to >> back the drawing board from a spec POV so we can think of something >> clean from the begining. > > I'm for 2., because @javax.persistence.MapKey is really completely > useless and has to be redesigned (looks like a legacy case that one > of the EG members had and thought that it would be useful). So > enhance @org.hibernate.annotations.MapKey and create a @Target that > works for @Embedded. > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev