Generic Question about Hibernate Development

travellingrants · **Joined:** Sun Oct 31, 2010 12:59 am **Posts:** 2

Hi All,

we are working on a web application where my team is responsible for the development of the core functionality of the application and development of ORM layer is the main area of concentration.

We have already pointed out all the major entities and other main component with respect to persistence layer and have started out implimentation for the same.
there is one area where we are still not able to find a good workaround,Since we are developing this core functionaity so we at some time willprovide this module as jar package to the other team who is responsible for other part of application,though we have already fingured alomost all required entities but still there are always chances that in future the other team needs to create some additional entities and we don't want them to have direct depedency on us.

Can some one suggest whats the best way so that when they create an new entity this should get register with out cfg file so that they need not to create any new cfg file.intentions are they only need to create the Entity class and its Mapping file(.hbm) and rest of the things should be taken care by out core module like identify new hbm file and registering it with configuration object etc.

Any help in this regard will be much appriciated

Thanks in advance
Travellingrants

sanne.grinovero · **Posted:** Sun Oct 31, 2010 7:21 am

you can start Hibernate programmatically from a Configuration object, in case you point it to all configuration files you want. You could have a conventional name for each of your .hbm files and have your startup code look for all resources having that name (which would load them from different jars), pass them all to the configuration object, and have your SessionFactory started.

second option, use annotations with autodiscovery of annotated entity classes (JPA)

travellingrants · **Joined:** Sun Oct 31, 2010 12:59 am **Posts:** 2

Thanks for the input..
Can you please give me a pointer about the first option that will help me to get the idea in better way

Thanks
Travellingrants

sanne.grinovero · **Posted:** Mon Nov 01, 2010 8:45 am

Programmatic configuration is powerful, there are many options you can use (shouldn't need all of them) :

Code:

new org.hibernate.cfg.Configuration.Configuration()
   .addDirectory( File directory ) //search all hbm.xml files from a directory
   .addJar( File jar ) //searches all *.hbm.xml files in the jar and adds them to configuration
   .addFile( File xmlFile ) //adds mapping from a specific file
   .setProperty( Environment.DRIVER, "jdbc driver name" )
   .setProperty( Environment.URL, "jdbc url" )
   .setProperty( Environment...., "more options )")
   .buildSessionFactory();

I think you could define some convention which is most practical for you use case.
Maybe some properties can be hard-coded in such a SessionFactory factory, but you could read some options from you own configuration properties file.