[hibernate-issues] [Hibernate-JIRA] Commented: (HV-421) Reconsider behavior of parameter validation for inheritance hierarchies

[ http://opensource.atlassian.com/projects/hibernate/browse/HV-421?page=com... ] Gunnar Morling commented on HV-421: ----------------------------------- The problem with conjoining all the preconditions of a method in a hierarchy is that a caller could get a constraint violation although he completely fulfilled the contract he has seen. So if a caller invokes foo() on a variable which's static type is A, a constraint violation might be the result if the variable's runtime is B and the precondition at B#foo() is stronger without any chance for the caller to know in advance. So most PbC implementations choose to disjoin the preconditions in a hierarchy, causing the weakest precondition in the hierarchy to apply. Other implementations choose to prohibit multiple preconditions in a hierarchy at all (e.g. Microsoft's Code Contracts). Given the complexity of the matter at hand and the chance we might get something wrong here, I feel we might well start with such a conservative approach in 4.2 and add support for the inheritence scenario later on. WDYT? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira