Deploy the same process twice without changes

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-26-2014 03:03 AM
Hello, the activiti user guide states the following:
Suppose we now deploy an updated version of the same process (e.g. changing some user tasks), but the id of the process definition remains the same. The process definition table will now contain the following entries:
Now, what if I deploy the same process twice, without making any changes to the model. The XML is identical. Will activiti increment the version and create a new deployed version in the database or will it ignore the call to deployment and retain the current version since nothing has changed?
Suppose we now deploy an updated version of the same process (e.g. changing some user tasks), but the id of the process definition remains the same. The process definition table will now contain the following entries:
Now, what if I deploy the same process twice, without making any changes to the model. The XML is identical. Will activiti increment the version and create a new deployed version in the database or will it ignore the call to deployment and retain the current version since nothing has changed?
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2016 01:45 PM
Maybe, for this: https://activiti.atlassian.net/browse/ACT-4024
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2016 02:13 AM
> Will activiti increment the version and create a new deployed version in the database
Yes, every time you call the deploy action, a new deployment is made and stored in the database.
If you don't want that, you'll have to add some 'duplicate checking' yourself before handing it over to be deployed.
Yes, every time you call the deploy action, a new deployment is made and stored in the database.
If you don't want that, you'll have to add some 'duplicate checking' yourself before handing it over to be deployed.
