[jboss-jira] [JBoss JIRA] Resolved: (JBPORTAL-2189) New JBPM process definitions in portal-identity.sar are not picked up

[Stephen Houston (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBPORTAL-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Houston resolved JBPORTAL-2189.
---------------------------------------

    Resolution: Rejected


Rejecting my own feature request. By setting "overwrite-workflow" to true the new version of the process was picked up and a new definition instance was created in JBPM.

Would suggest that the documentation be modified for this option to something along the lines of:

overwrite-workflow: Set to true this will create new instances of the process definitions found in the conf/processes directory each time the server is started. 

Set to false it will only create new instances of the process definitions in the jbpm database if they did not already exist. This means that on first time a process is deployed in the conf/processes directory it will be defined in the process database, but subsequent updates to that definition file not be reflected in the database unless this option is set to true.

Note: when set to true all processes in conf/processes regardless of whether or not they have changed, or if they are referenced in identity-ui-configuration.xml, will have their definitions updated in the database. Therefore for production systems it is recommended that this option be set to false at all times other than when intentionally updating the process definitions.

> New JBPM process definitions in portal-identity.sar are not picked up
> ---------------------------------------------------------------------
>
>                 Key: JBPORTAL-2189
>                 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2189
>             Project: JBoss Portal
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Portal Identity
>    Affects Versions: 2.6.6 Final
>         Environment: JDK 1.6.07, JBoss AS 4.2.3.GA (using the all server config), JBoss Portal 2.6.6 HA, CentOs 5.1
>            Reporter: Stephen Houston
>         Attachments: com.test-0.0.1-SNAPSHOT.jar, com.test.tar.gz, def1.zip, def2.zip
>
>
> New process definitions copied to the server/all/deploy/jboss-portal-ha.sar/portal-identity.sar/conf directory are not picked up. The original definition is used.
> Steps to reproduce
> * Stop the portal if its running
> * Copy the attached com.test-0.0.1-SNAPSHOT.jar to jboss-portal-ha.sar/lib. This contains two handler definitions, Handler1 prints out 1s and Handler2 prints out 2s
> * Extract def1.zip to portal-identity.sar/conf/processes. This creates a new process definition testprocess.xml
> * Modify portal-identity.sar/conf/identity-ui-configuration.xml , adding the line <admin-subscription-mode>testprocess</admin-subscription-mode>
> * Start the portal. Login as admin, create a new user account. When submitted to the process you will see 10 lines of 1's written to the console
> * Stop the portal
> * Extract def2.zip to portal-identity.sar/conf/processes. This will overwrite testprocess.xml with one that uses Handler2 instead of handler 1.
> * Start the portal. Login as admin, create a new user account. When submitted to the process you will see 10 lines of 1's written to the console indicating that the old process version was used instead of the updated on.
> To work around the problem you need to change the process name, rename the file, and update identity-ui-configuration.xml. It would be more desirable if the portal could determine that the process has changed and that it needs to be picked up and redeployed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira