[
https://jira.jboss.org/jira/browse/JBPM-2242?page=com.atlassian.jira.plug...
]
Tom Baeyens resolved JBPM-2242.
-------------------------------
Resolution: Done
To implement suspend and resume on deployments and cascade it to executions, jobs and
tasks, I started with synchronizing following properties:
* Deployment.state
* Execution.state
* Job.state
* Task.state
(some of those had an isSuspended boolean) So i switched to all state (String)
properties.
Two operations are added to the repository service: suspendDeployment and
resumeDeployment. This cascades to all the related executions, jobs and tasks.
add deployment state
--------------------
Key: JBPM-2242
URL:
https://jira.jboss.org/jira/browse/JBPM-2242
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Critical
Fix For: jBPM 4.0.0.CR1
initially the only supported states of a deployment should be active and suspended.
it must be able to suspend deployments.
jboss un deployment should be bound to suspending a deployment. that way the jbpm
runtime engine will not see it any more, but the data is not deleted from the db.
deleting the deployments should only be possible from the admin consoles (our web console
or jopr) and maybe from an ant task
--
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