Hibernate the configuration file detailed

Hibernate's configuration file, the default is 2: Hibernate.properties,hibernate.cfg.xml, either, optional, can also be combined to use. If there is a definition of the same attribute, the XML file overwrites the contents of the properties file, as the "Hibernate in Action" says.

These days, encountered a problem, that is, the site has several WebApp have started to use Hibernate, if Bbs.war first released, but if the Blog.war first released, then the BBS in addition to the public with the blog online users, nothing else can be read from the database.

Read the log, know that because of this release order, then Bbs.war in the Forum.cfg.xml, Thread.cfg.xml and so on, have no effect. Why is that?

It turns out that all 2 packages use Hibernate.cfg.xml, and the Hibernate configuration file is explicitly invoked in hibernateutil other ways.

Package token
Import net.sf.hibernate.*;
import net.sf.hibernate.cfg.*;
public class Hibernateutil {
Private static final sessionfactory sessionfactory
Static {
try {
/* method One */
//Sessio Nfactory = new Configuration (). Configure (). Buildsessionfactory ();
/* Method Two */
* sessionfactory = new Configuration ()
. addclass (Counter.class)
. addclass (Online.class)
. Buildsessionfactory ();
*/
/* Method three */
Sessionfactory = new Configuration (). Configure ("/token.cfg.xml"). Buildsessionfactory ();
} catch (Hibernateexception ex) {
throw new RuntimeException ("Exception Building sessionfactory:"
+ ex.getmessage ( ), ex);
}
}
public static final ThreadLocal sessions = new ThreadLocal ()
public static session currentsession () t Hrows Hibernateexception {
Session s = (sessions) session.get ();
//Open A new session, if this Thread has none yet
if (s = = null) {
S = sessionfactory.opensession ();
Session. set (s);
}
return s;
}
public static void CloseSession () throws Hibernateexception {
Sessions s = (session) Session.get ();
session.se T (NULL);
if (s!= null)
S.close ();
}
}

Originally I always use method one, and method one is simple, but must call Hibernate.cfg.xml to initialize hibernate, if two packages all use such hibernateutil, then 2 Hibernate.cfg.xml only the first function.

Method Two, you can solve the problem that a method may bring. But if you have a new pojo, you still need to modify Hibernateutil.java.

So, I tried to use the method three, also succeeded.