Hi Tijs,
Just to give you an update, here's what I did (to give me expected behavior):
1) I chose a new H2 DB schema (a clean, fresh one with no tables in it initially)
2) Created a maven project with Activiti 5.13 as the jar version in the .pom file and wrote some code to deploy a sample bpmn20 process definition file to the aforesaid H2 DB.
3) As part of deployment, I could see console messages saying that create scripts were executed. Subsquently, the process file got deployed successfully. To confirm this, I logged into H2's web-console and checked the ACT_HI_PROCINST table for valid entries.
4) I deployed activiti-explorer (ver 5.13) on Tomcat 7, booted-up the server, logged into the explorer (kermit/kermit) and was able to view my deployments. Prior to this, I updated the DB entries in the war file's WEB-INF\activiti-standalone-context.xml & WEB-INF\classes\db.properties so as to point to my H2 database URL.
5) Also, in ACT_GE_PROPERTY, the schema.version value was 5.13 & schema.history was create(5.13)
So, in a case like this (where the version of activiti engine in the maven project is the same as the one inside the activiti-explorer war), no upgrade script is being executed.
However, in the earlier case (where the version of activiti engine in the maven project was 5.9 whereas that of the one inside activit-explorer was 5.13), something went wrong during the boot-up of activiti explorer and the upgrade steps just did not go through as expected, As a result, the activiti-explorer didn't start at all.
That said, can you please give your insight into the following areas that are still grey for me?
1) How to deal with this case (when the project requires a new activiti jar to be used during the middle of development, like 5.9 originally and 5.13 later, mid-way)?
2) Will similar problems occur even when the version of the DB changes (like from Oracle 10 to Oracle 11)?
3) Most importantly, it is somewhat clear that programmatic deployment (through java code) compares versions and decides if an upgrade script has to be called. On the other hand, why does the activiti-explorer too do this? And how does it decide when to call the upgrade scripts?
Since I'm a newbie, please dont mind the sheer number of questions coming from me!
-
A M Bharath
Just to give you an update, here's what I did (to give me expected behavior):
1) I chose a new H2 DB schema (a clean, fresh one with no tables in it initially)
2) Created a maven project with Activiti 5.13 as the jar version in the .pom file and wrote some code to deploy a sample bpmn20 process definition file to the aforesaid H2 DB.
3) As part of deployment, I could see console messages saying that create scripts were executed. Subsquently, the process file got deployed successfully. To confirm this, I logged into H2's web-console and checked the ACT_HI_PROCINST table for valid entries.
4) I deployed activiti-explorer (ver 5.13) on Tomcat 7, booted-up the server, logged into the explorer (kermit/kermit) and was able to view my deployments. Prior to this, I updated the DB entries in the war file's WEB-INF\activiti-standalone-context.xml & WEB-INF\classes\db.properties so as to point to my H2 database URL.
5) Also, in ACT_GE_PROPERTY, the schema.version value was 5.13 & schema.history was create(5.13)
So, in a case like this (where the version of activiti engine in the maven project is the same as the one inside the activiti-explorer war), no upgrade script is being executed.
However, in the earlier case (where the version of activiti engine in the maven project was 5.9 whereas that of the one inside activit-explorer was 5.13), something went wrong during the boot-up of activiti explorer and the upgrade steps just did not go through as expected, As a result, the activiti-explorer didn't start at all.
That said, can you please give your insight into the following areas that are still grey for me?
1) How to deal with this case (when the project requires a new activiti jar to be used during the middle of development, like 5.9 originally and 5.13 later, mid-way)?
2) Will similar problems occur even when the version of the DB changes (like from Oracle 10 to Oracle 11)?
3) Most importantly, it is somewhat clear that programmatic deployment (through java code) compares versions and decides if an upgrade script has to be called. On the other hand, why does the activiti-explorer too do this? And how does it decide when to call the upgrade scripts?
Since I'm a newbie, please dont mind the sheer number of questions coming from me!
-
A M Bharath
