Community

Update Deployment Resource

reply from HuiSheng Xu in jBPM Development - View the full discussion

Hi Maurizio,

 

  I am sorry to say that, at this moment, the updateDeploymentResource() in RepositoryServiceImpl did not finished yet.  Maybe it is caused by the refactor work for id generate strategy.  The id of Lob didn't be initialized, so the value of id always be zero.  And there are still some problems for check confict for updated process definition,  e.g. if you update a already deployed process,  and the name or key of new processs is difference from the old one, then we will get a dead lock.

 

I think we could create a JIRA issue for this problem, and wait to see if other people has advanced advice.

Reply to this message by going to Community

Start a new discussion in jBPM Development at Community