That's done the trick, thanks. So if I understand correctly, 1 - In the dvdstore app, hibernate.cfg.xml effects only jBPM. It has no impact on how the entity beans are persisted. 2 - jboss-beans.xml is not relevant at all for the dvdstore example (I've deleted it with no apparent side-effects). 3 - each deployed SEAM (with jBPM) application can provide its own jBPM database with a separate *-ds.xml (as long as it uses a unique jndi name). 4 - the app-server (jboss/hibernate/seam ...) will try to run import.sql against all persistence-units that are loaded (?). This is good for my dvdstore database but no good for the jBPM database (throws an exception when it can't delete from one of the domain tables (ORDERLINES)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031332#4031332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031332 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
