3

Reading about Hibernate I came across warning buildSessionFactory being deprecated in Hibernate 4 and above. As per this stackoverflow post and the docs, I used buildSessionFactory(serviceRegistry).

But why has it been deprecated? What are the advantages of using ServiceRegistry over the old way?

Community
  • 1
  • 1
ykesh
  • 1,199
  • 2
  • 21
  • 33
  • 1
    question to their API designer – jmj Dec 30 '14 at 06:32
  • One of the benefits I found is, even when using Annotations instead of XML configurations, I can still use the same API to build the SessionFactory, instead of using `AnnotationConfiguration`. – ykesh Dec 30 '14 at 12:38

1 Answers1

0

Please check here for more details.

Currently a SessionFactory is built by throwing a bunch of stuff into a Configuration object, stirring it, letting it come to a boil, and then pulling out the SessionFactory. In seriousness, there are a few problems with the way we currently operate within a Configuration and how we use it to build a SessionFactory: The general issue that there is no "lifecycle" to when various pieces of information will be available. This is an important omission in a number of ways:

  1. Consider schema generation. currently we cannot even know the dialect when a lot of db object names are being determined. this would be nice because it would allow us to transparently handle table/column names which are also keywords/reserved-words in the dialect, for example.
  2. static-ness of types and the type-mappings. Because we currently have nothing to which to scope them. Ideally a type instance would be aware of the SessionFactory to which it is bound. Instead, what we have now is to change API methods quite a lot of the time to add in the SessionFactory as a passed parameter whenever it is discovered that it is needed.
  3. also, most (all?) of the "static" configuration parameters in Hibernate are currently required to be so because of their use from within these static types; thus scoping types would allow us to also scope those config parameters (things like bytecode-provider, use of binary streams, etc). Ideally what I see happening is a scheme where users build a org.hibernate.cfg.Settings (or something similiar) instance themselves. Additionally they would apply metadata to a registry of some sort (lets call it MetadataRegistry for now). Then in order to build a SessionFactory, they would supply these two pieces of information (via ctor? via builder?). The important aspect though is that the information in MetadataRegistry would not be dealt with until that point in time, which would allow us to guarentee that resolving schema object names, types, etc would have access to the runtime Settings (and specifically the dialect)
M. Deinum
  • 115,695
  • 22
  • 220
  • 224
lalithark
  • 107
  • 9