Hello all,

I'm using Hibernate 3.0.

I have a J2EE application - it's a ear file (containing a war and a jar). The hibernate.cfg.xml file is located inside the ear. The problem is that our application is supposed to work with multiple databases - meaning multiple dialects and different database connection parameters - which is specified inside the hibernate.cfg.xml file inside the ear. We don't want to have to "blow up" our ear file, modify the hibernate.cfg.xml file every time we want to use a different dialect (and different database connection parameters). And we don't want to have to build a different ear file (really the same ear file - but containing a custom hibernate.cfg.xml file) for every db.

Our application DOES use an external xml-based config file. We'd love to put these hibernate options inside THAT file. Is there anything we can do to keep our ear file "hermetically sealed" for your sanitation? Can we make hibernate look for "dialect", "connection.driver_class". etc. - somewhere besides the hibernate.cgf.xml file?

Thanks!

-john

Read the Javadoc for org.hibernate.cfg.Environment class. It may have what you need.

We had a similar need. Effectively, we had username/pwd settings in a separate config file and didn't want them to be redundant in the hibernate.cfg.xml.

To accomplish this, it looks something like:

Configuration cfg = new Configuration().configure(<hibernate.cfg.xml>);

cfg.setProperty("connection.url", ...);
cfg.setProperty("connection.username", ...);
cfg.setProperty("connection.password", ...);

cfg.setProperty("hibernate.connection.url", cfg.getProperty("connection.url"));
cfg.setProperty("hibernate.connection.username", cfg.getProperty("connection.username"));
cfg.setProperty("hibernate.connection.password", cfg.getProperty("connection.password"));

hibernateSessionFactory = cfg.buildSessionFactory();

-----------------------

The trick is in knowing what properties need to be set.

If you've got an application server, isn't a JNDI based SessionFactor an option? We're using JNDI based datasource for running applications on multiple servers, our only problem is setting the correct dialect.