Rapp manager does not shut down remaining caps

[bit-pirate]

If stopping a cap has returned an error.

The rapp manager should store the error, attempt to shutdown the remaining caps and then report back the issue through there service response.

[bit-pirate]

This is also related to #165.

[bit-pirate]

Question @stonier and @jihoonl:
If stopping a rapp returns an error, should it be considered running or stopped?

If it should be considered stopped, I would make sure the capabilities are stopped in this case as well.

[bit-pirate]

If stopping a rapp returns an error, should it be considered running or stopped?

Conclusion of our talk is, that for now we consider the rapp stopped.

There is currently nothing implemented in the rapp manager, which could handle the situation, where stopping a rapp returns an error.

If specific use cases turn up, where this is a problem, we will add better handling specific for those use cases. At this moment it is hard to find those cases and hence even hard to add proper error/exception handling for them.