Configuration is the normal legacy means most Hibernate users build a SessionFactory. Moving forward into 5.0 the way to build a SessionFactory will be much different to allow for people to hook into all phases of building the SessionFactory.
However, we can still allow most users to use Configuration. Configuration in that sense should be viewed as a means to build the SessionFactory in one big shot (aka, "here is all my config info, not build me a SessionFactory"). To that end we would need to remove some problematic methods that allow access to the in-flight state inside the Confirguration.
Please do not actually remove Configuration yet.
, I know most of this is already completed. Anything left?
Not from my end/expectation. Was waiting to see if there is anything to hear from:
1) as she integrates metamodel into envers, which was a major Configuration user
2) as he integrates spatial
3) others (search, etc)
To be honest, we likely won't hear from (3) others until after we start doing releases. Gail, Karel, if you do find discrepancies or things we should discuss with regards to the Configuration contract lets discuss on IRC or just open a new issue linked to this one. I'll resolve this one.