Start/Stop/Undeploy commands are not well handled wher trying to perform corresponding commands if the deployable is already started/stopped/undeployed.
The improvement based on implementation of List command for Tomcat - pelase see http://jira.codehaus.org/browse/CARGO-322.
When you stop deployable which is not already deployed cargo throws exception and exit. The same happens when starting deployable which is already started and the same with undeploy when deployable is not deployed. Here is attached improvement allowing to continue performing the code after performing the command for any current state of the deployable in the container.