As part of my development cycle, I periodically drop and create the database schema. This is in preparation to a migration to Oracle and as a way to remove the countless process instances and tasks I have created during the normal course of testing.

I have noticed that when I reload a process definition, references to classes by some action handlers remain. This came to light when I dropped and created the DB schema and then loaded a process definition that changed from the version loaded before the DB drop/create.

Has anyone noticed this behavior? I?d attribute it to Hibernate caching but I don?t know how to force Hibernate to ?forget? the previous data. I did try a jbpmSession.getSession().flush() during the DB schema drop/create but that didn?t clear up the issue.

Any thought?
-fm