[jbpm-dev] [Design of JBoss jBPM] - Re: db properties reorg

heiko.braun@jboss.com do-not-reply at jboss.com
Wed Feb 4 05:31:51 EST 2009


anonymous wrote : 
  | Ideally i would like to move to the following situation: 
  | 
  | * a config module that has the default persistence configuration and produces it in a jar file in the repo.
  | 

right, that something we agree upon. Just that the current configuration resides with the jpdl module which produces a a config jar that goes into the repo: jbpm-jpdl-4.0.0-SNAPSHOT-config.jar

Another requirement is to switch between hibernate managed connections (simple tests, jdbc properties) to container managed connections (intgeration tests, datasources). This is something we already did in jBPM3
and I simply wanted to leverage the existing build, which is non trivial.

Hence the change from hibnerate.cfg.xml+hibernate.properties to a single hibernate.cfg.xml which includes the connection settings. 

So basically, the db.properties (i.e. mysql.properties) disappeared and have been replaced by hibernate.mysql.cfg.xml, which ship with the jpdl-config.jar.

Currently this get's expanded into every module that needs db connection settings and is used by the installer to finally create hibernate.cfg.xml and *-ds.xml for deployment into the AS.

The build is driven by profiles.xml which contains the connection properties (i.e. Qa on your local box vs. jboss QA environment) and by the 'mvn -Ddatabase=mysql' switch, that defaults to hsqldb.

Does that answer your question?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206862#4206862

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4206862



More information about the jbpm-dev mailing list