Issue 7398: Provide exception handling for all behaviors. (uml2-rtf) Source: Missouri University of Science and Technology (Dr. Thomas Weigert, weigert(at)mst.edu) Nature: Clarification Severity: Minor Summary: UML2 has added the capability of dealing with exceptional behavior. Exception handling can occur at various levels of the model. Unfortunately, the exception handling mechanism has not been systematically developed. Any kind of behavior should support the mechanism of catching and handling an exception that was raised somewhere within that behavior. Unfortunately, currently only activities allow for this. Similar capabilities should be available for interactions and statemachines, and even for use cases. Recommendation: Provide exception handling for all behaviors. Resolution: Revised Text: Actions taken: May 30, 2004: received issue Discussion: Disposition: Deferred to UML 2.4 RTF End of Annotations:===== m: webmaster@omg.org Date: 30 May 2004 14:47:00 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Thomas Weigert Company: Motorola mailFrom: thomas.weigert@motorola.com Notification: No Specification: UML Section: 15 FormalNumber: ptc/03-08-02 Version: 2.0 RevisionDate: 02/08/2003 Page: 455 Nature: Clarification Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description UML2 has added the capability of dealing with exceptional behavior. Exception handling can occur at various levels of the model. Unfortunately, the exception handling mechanism has not been systematically developed. Any kind of behavior should support the mechanism of catching and handling an exception that was raised somewhere within that behavior. Unfortunately, currently only activities allow for this. Similar capabilities should be available for interactions and statemachines, and even for use cases. Recommendation: Provide exception handling for all behaviors. Issue 7398: Provide exception handling for all behaviors. Issue summary UML2 has added the capability of dealing with exceptional behavior. Exception handling can occur at various levels of the model. Unfortunately, the exception handling mechanism has not been systematically developed. Any kind of behavior should support the mechanism of catching and handling an exception that was raised somewhere within that behavior. Unfortunately, currently only activities allow for this. Similar capabilities should be available for interactions and statemachines, and even for use cases. Recommendation: Provide exception handling for all behaviors. Discussion This issue, while important, requires further study. Revised Test Resolution