I am noticing some inconsistencies in packages that i wanted us all to talk through. Mainly what I have seen has related to services and that sometimes they are put in o.h.services and sometimes in more "natural" packages. Though, also, I think that some of this boils down to what "engine" means as in o.h.engine. For example, take JDBC-related stuff. Yes, dealing with JDBC is just a lot of code for us. But we have JDBC related code spread throughout multiple packages. org.hibernate.jdbc - I am not too concerned with as it is somewhat special, because it is JDBC related stuff that we expose to the use (API). But org.hibernate.engine.jdbc and org.hibernate.service.jdbc feel like they should be in the same package structure. Initially I had intended o.h.services to be home for just the code related to the registry and service infrastructure, but not home for actual services. Not sure why we got off track with that tbh. I remember initially putting some "essential" services (what eventually became bootstrap services) in here because they did not seem to fit anywhere else (though we do now interestingly have org.hibernate.boot). Just wanted to get a discussion started about it... -- steve(a)hibernate.org http://hibernate.org