Quoting Rickard Öberg <[email protected]>:
Return-value: after the last concern has been executed, and before
side-effects are called. If the value is wrong, then the
side-effects will get an IllegalArgumentException rather than the
value as result.
Method-constraints: before everything, even parameter constraint
checks. This is to check whether the entity is in a legal state to
be called at all, for the given method. However, for myself the main
usage of this will actually be that client code should be able to
ask if a method on an entity is valid, so that I can change the
actual client UI to have enabled/disabled controls for that method.
In other words, typically invoking a method that is not valid will
be a bug, rather than normal operation.
Sounds good. I hope the core-team approves this and it will get
implemented soon! :)
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
