Which database are you using?
It might have to do with transaction support (at the JDBC jar level) for the database: I've encountered a couple problems with that.
Thanks for replying. I am using MySQL.
For now I am kind of exploring jbpm 5. My only objective of changing the db for now is to see the backend structure. But i think it aint as distinguishable and structured as jbpm 4.
I tried to invoke the db manager through jmx-console. But I am not very sure whether the connection I see there is correct. But there must be a better way of checking out the h2 manager. Can you help me with that? or with the migration. Thanks again
1 of 1 people found this helpful
I think it has to do with how you're executing the process -- I ended up doing the following in order to look at the table structure:
- git clone jbpm ...
- modify files in jbpm-installer/db (which I actually ended up not using)
- ant install.demo
- ant start.demo
- git clone git://github.com/Salaboy/Drools_jBPM5-Training-Examples.git
- import and modify example 04 in demo eclipse to use MySQL
- mvn eclipse:eclipse (maven 3, of course)
- Modify persistence.xml so that it has the following properties:
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/>
<property name="hibernate.connection.url" value="jdbc:mysql://localhost:3306/jbpm5" />
<property name="hibernate.connection.username" value="jbpm5" />
<property name="hibernate.connection.password" value="jbpm5"/>
- Attach MySQL driver to project (via build path in Eclipse)
- Run example (PersistentEmergencyProcessTest jUnit test.)
The problem I started noticing with the demo is that the jbpm-gwt-console-server.war that's deployed to the demo jBoss server that's started up has it's own (for H2) configured JPA configuration (persistence.xml).
Salaboy's persistence example only modifies the SessionInfo table, but I think that if you extend it more, it'll be possible to to get a good idea of what's modified in the database.
I think that getting the demo to work fully with the database is basically more work than is worth it -- especially if you're just exploring jBPM 5 at the moment.
This is helpful.. Thanks a lot.