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