[jbpm-issues] [JBoss JIRA] Updated: (JBPM-2750) need delete the duplicated field 'state' in TaskImpl

[Tom Baeyens (JIRA)]

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

Tom Baeyens updated JBPM-2750:
------------------------------

    Fix Version/s: jBPM 4.x
                       (was: jBPM 4.4)


> need delete the duplicated field 'state' in TaskImpl
> ----------------------------------------------------
>
>                 Key: JBPM-2750
>                 URL: https://jira.jboss.org/jira/browse/JBPM-2750
>             Project: jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Runtime Engine
>    Affects Versions: jBPM 4.3
>         Environment: Windows XP, JDK1.5.0_15, Maven-2.2.1
>            Reporter: Huisheng Xu
>             Fix For: jBPM 4.x
>
>
> How could we find out this bug?
> If you invoke repositoryService.suspendDeployment(deploymentDbid), you will find out that the state of relative tasks is still 'open'.
> Because there is a duplicated field 'state' in both TaskImpl and ScopeInstanceImpl. when we invoke 'taskImpl.suspend()' method, this method is defined in ScopeInstanceImpl.
> in this method, the 'state' of ScopeInstanceImpl field will be changed to 'suspend', but the 'state' of TaskImpl field still be 'open', so in the end, no matter how we invoke the suspend() method, the TaskImpl is still open, it won't be suspended.
> So I think we should delete the duplicated field 'state' of TaskImpl.

-- 
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