[
https://jira.jboss.org/jira/browse/JBPM-2102?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-2102:
-----------------------------------
We discussed this topic in the developer meeting last friday. The outcome of that
discussion was this:
* first a deployment gets deployed
* resulting process definitions can be used. the deployment is active
* deployments can be suspended. suspending a deployment cascades to all process
instances. process definitions of suspended deployments should not show up in queries.
* the undeploy of jbpm's jboss deployer should be coupled to the suspend
* deletion of a .bar business archive in the jboss deploy directory should never delete
data from the database, but rather suspend the deployment
* deletion of a deployment should be offered as a mgmt/admin feature in the console. so a
list of suspended deployments should be available. possible operations on suspended
deployments are 'Delete' and 'Resume'.
Provide process definition lifecycle
------------------------------------
Key: JBPM-2102
URL:
https://jira.jboss.org/jira/browse/JBPM-2102
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: jBPM 4.0.0.CR1
Process definitions should get states that indicate their availablility. I.e.
"incomplete/complete" when jboss server shutdown de-asscociates the the
deployment unit.
--
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