I wondered the same. That's what it was doing when I started working on the code. It seemed convoluted to me, but I figured there was a reason for it. Go ahead and change it as you see fit. Gail ----- Original Message ----- From: "Steve Ebersole" <steve(a)hibernate.org&gt; To: hibernate-dev(a)lists.jboss.org Sent: Monday, June 20, 2011 7:26:14 PM Subject: [hibernate-dev] EntityBindingState In looking at http://opensource.atlassian.com/projects/hibernate/browse/HHH-6338 I really started digging into this notion of "binding state" and specifically EntityBindingState. I ran into a question. I don't quite follow reasons for some of the details here. For example, I do not get why we: 1) instantiate an EntityBinding 2) instantiate an Entity, and pass it into the EntityBinding 3) instantiate a EntityBindingState and pass it into the EntityBinding. Given what I understand the point of the "binding state" to be, the step I specifically do not get is (2). Why not just make the information needed to create the Entity instance (name, supertype) part of the EntityBindingState contract and: 1) instantiate an EntityBinding2) 2) instantiate a EntityBindingState and pass it into the EntityBinding. Then the EntityBinding can create the Entity as it needs based on EntityBindingState. I did not want to just start making changes here without understanding the reasoning for doing it the way it is. -- Steve Ebersole <steve(a)hibernate.org&gt; http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev