ACT_RE_PROCDEF modification behaviour

[rufini]

Hi:

I'm trying to understand in which cases ACT_RE_PROCDEF is updated to try to reproduce/avoid a bug I had in Activiti 5.6 as described in http://forums.activiti.org/en/viewtopic.php?t=1087&p=9293 (multiple key-version that block the whole app)

I see that a new entry is added when I modify a workflow xml and restart the server.
Also, an entry is added when I run an integration workflow test that load the context (even if the workflow xml wasn't modified)

There's another event that insert entries in that table?

I'm really worried about the possibility of a new duplicated entry on that table, so I would like to determinate that scenario.

Thanks!
rufini

[jbarrez]

The only way to get a process definition in the database is through the RepositoryService using the deployment.

The @Deployment annotation for unit tests also uses exactly the same code.

[rufini]

Thanks for your reply, Joram.

I'm now adding a constrain to avoid that a duplicate key+version halt my app in the future.

ALTER TABLE `ACT_RE_PROCDEF` ADD UNIQUE INDEX `KEY_VERSION` (`KEY_` ASC, `VERSION_` ASC) ;
Greetings,
rufini