Issue 15412: OCL Constraint violation messages (ocl2-rtf) Source: Model Driven Solutions (Dr. Edward Willink, ed(at)willink.me.uk) Nature: Uncategorized Issue Severity: Summary: OCL supports definition of constraints, but it is difficult for tools to offer better error messages to a user than 'Constraint <constraint-name> violated for <constrained-element-name>'. It would be helpful if Constraints had an additional String-valued expression to be evaluated in the context of the error, so that tools could evaluate it and present the result to the user. Suggest add an optional argument to the (not-optional) constraint name. e.g. inv ConstraintName('Unable to find ' + self.target.name): ... Resolution: Revised Text: Actions taken: August 11, 2010: received issue Discussion: End of Annotations:===== ronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuMFAH4CYkxUXeb0/2dsb2JhbACTOo0Bcbs8hToE Date: Wed, 11 Aug 2010 09:55:58 +0100 From: Ed Willink User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 To: issues@omg.org Subject: OCL Constraint violation messages Hi OCL supports definition of constraints, but it is difficult for tools to offer better error messages to a user than 'Constraint violated for '. It would be helpful if Constraints had an additional String-valued expression to be evaluated in the context of the error, so that tools could evaluate it and present the result to the user. Suggest add an optional argument to the (not-optional) constraint name. e.g. inv ConstraintName('Unable to find ' + self.target.name): ... Regards Ed Willink