Support #960
Component exception throwing is catched somewhere
| Status: | New | Start date: | 03/16/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
If I want a component to crash when it is requested to change in a component state that is not supported, I am not able to do this by means of throwing an exception. This exception is cathced somewhere in cca/rsb and the component still runs on.
Is this a bug? If not, what is the 'desired' way of stopping/crashing components?
History
#1 Updated by Anonymous about 12 years ago
The problem is, that the component state changed is triggered over RSB (when sent over network), so the thread catching the exception is just the event delivery mechanism. The component itself is decoupled from that and will continue running.
A workaround could be that you stop the component (calling this->stop()) before firing the exception.
But you are right, there should be a convenient solution (maybe a way to fire an exception, which fires the exception and stops the component) including error logging etc.