[
https://jira.jboss.org/jira/browse/JBPM-2242?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-2242:
-----------------------------------
Notes from the dev meeting:
- Add suspend and resume to process instances
- Add suspend and resume to deployment
- A jboss undeployment will lead to suspending the deployment and the related process
instances
- Most important target before GA is to analyse the DB impact and try to get the
necessary columns in
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