I think the way JBPM manage support for all the different databases is pretty good in that you can generate the DDL from there Hibernate configuration. They maintain a separate DB project where they manage all the different versions of JBPM database schemas. One common problem that I find working with customers with JBossMQ and JBM is that I often need to provide DBA the DDL for the messaging tables rather than let them get created automatically. So I normally run them into a dev or test environment then you a DB tool to extract the DDL scripts from that. I think it would be better to just run an ant script to generate it from the hibernate/JPA config. Is the plan you to use the JPA EntityManager or just use JPA to provide the metadata to describe the mapping and then use pure JDBC to access the tables. I have often spoken to the hibernate team about using hibernate/JPA persistence for JBM and the feedback I get from them is it may not be the right fit. I think using Hibernate to provide the DDL for any database is a good idea for managing support for many different databases. If you do go down the route of using JPA/Hibernate I would take a look at using the Hibernate stateless session as it may prove to provide better performance for this type of persistence requirements. well that's just my two cents for what it's worth...:) --Aaron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111491#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...