Niclas Hedhman wrote: >> One question is what should happen if an incorrect value is created? The >> current ConstraintViolationException extends IllegalArgumentException >> which doesn't seem to make sense. What exactly would the semantics be, >> and what should you do with the exception if you get it? > > Logically speaking it is an InternalError in the implementation. And I > think we should create an RuntimeException for the purpose > (ContractViolationException?), and have these checks before execution > of the Concerns return path, so that one can plugin generic Concerns > doing something with it.
See your point. But it is also important to do the checks right after all concerns are executed, because they are not allowed to "screw it up". So: after mixin execution and after concerns execution. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
