JBoss Community

Hi Roxy,

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:

1. git clone jbpm ...
2. modify files in jbpm-installer/db (which I actually ended up not using)
3. ant install.demo
4. ant start.demo
5. git clone git://github.com/Salaboy/Drools_jBPM5-Training-Examples.git
6. import and modify example 04 in demo eclipse to use MySQL
   1. mvn eclipse:eclipse (maven 3, of course)
   2. Modify persistence.xml so that it has the following properties:

      <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"/>

      ...

   3. Attach MySQL driver to project (via build path in Eclipse)
7. 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.