I'll definitely take a look as soon as I get some time (currently busy working through some JPA 2.1 stuff). But in the meantime maybe you could do a plain English write-up describing the differences you see here between hbm and annotations that led you to look to these strategies so that we can comment and get you moving forward more quickly...
In general, the thing we need to guard against here is duplicating code. The existing binders duplicate tons of stuff and its a maintenance nightmare. So for example, the end-game determination for unsaved-value in hbm is to instantiate the entity an reflect its actual newly-instantiated value. I think annotations does the same. So that code should be outside of hbm/annotations. Unless we decide as a group that its "ok" for sources (hbm/annotations) to share that code (subclass, delegation, etc) from its particular strategy. On Thu 29 Mar 2012 02:25:35 AM CDT, Gail Badner wrote: > At the team meeting in Austin, I remember discussion about cases where > different "strategies" were needed to process values obtained from > annotations and hbm.xml sources. I can't remember if we discussed unsaved > values, but it seems to me that this is one case where this is needed. > > I created a pull request for dealing with unsaved values: > https://github.com/hibernate/hibernate-orm/pull/298. > > Please take a look and provide feedback to let me know if I'm on the right > track. > > Thanks, > Gail > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- st...@hibernate.org http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
