[jboss-jira] [JBoss JIRA] Commented: (JBPM-682) task forms are not reloaded when a process is reloaded

[David Lloyd (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-682?page=comments#action_12347327 ] 
            
David Lloyd commented on JBPM-682:
----------------------------------

I think that any process definition metadata should be keyed off of nothing but the process definition ID (since a new ID is assigned for every version of a process definition).  This is what i currently do internally on the web console... now the question is, why is that not working.

One other clue is that "view task form source" seems to find the updated task form.  Hmmm.

> task forms are not reloaded when a process is reloaded
> ------------------------------------------------------
>
>                 Key: JBPM-682
>                 URL: http://jira.jboss.com/jira/browse/JBPM-682
>             Project: JBoss jBPM
>          Issue Type: Bug
>          Components: Web Interface
>    Affects Versions: jBPM 3.2 alpha 1
>         Environment: JBoss 4.03, jBPM 3.2 cvshead, jdk 1.5
>            Reporter: Ronald van Kuijk
>         Assigned To: David Lloyd
>            Priority: Blocker
>             Fix For: jBPM 3.2 alpha 2
>
>
> tom: this has to do with the caching of the task forms.
> kukeltje: At first the forms seem to be 'versionable' like the process archive. When trying to use this, it does not work. 
> If I have an error in a form, correct it and deploy a new process, the new form is stored in the DB. If I start a new pi for the latest pd, the previous version of the form seems to be cached by something however and used for the new process (form name stays the same). If I stop the server and start it again, start a new instance of the latest process (or load one for which I'm sure a correct form is present, the correct form is used. The tasks in older instances which should use the old forms can now be executed as well (meaning they use the new form).

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