The ability to model the idea of catching an exception in a UML activity diagram is pretty simple - but what about an exception due to an exception? The closest I can find is metal activity, sending a signal with a stereotype <<exception>>, and then the final node stream hits, but I do not know that this is considered best practice. Any thoughts?
Thank.
source
share