Modeling: User's Guide

Previous: 3.2.2 Within classes Up: 3. Functionalities for Object Next: 3.3.1 Integrity constraints derived

---

 
3.3 Automatic validation of referential and business-logic constraints

A major part of the checks made at runtime are validation operations -for example, you want to verify that a zipCode has a valid format, that the age of a person is a positive integer, etc.

The framework defines an interface, Validation, which allows you and the framework as well to trigger these validations when needed, in a defined scheme. You automatically get these functionalities when your class inherits from Modeling.CustomObject and corresponds to an entity defined in a model.

There is, roughly, two kinds of validation checks. The first one consists in checking individual properties of an object (such as: check that a value for a given key is of the proper type, that its width is ok if it is a 'string', etc.); the second one considers objects as a whole: its checks are like post-conditions, or consistency checking. We will see in the following how both can be adjusted and triggered.

• 3.3.1 Integrity constraints derived from the underlying model
• 3.3.2 Checking constraints: key by key
  • 3.3.2.1 Return code
  • 3.3.2.2 How to define your own validation logic
• 3.3.3 Validation.ValidationException: the list of error-codes
• 3.3.4 Validating an object ``as a whole''
  • 3.3.4.1 validateForSave()
  • 3.3.4.2 validateForDelete()
• 3.3.5 Misc.

---

Modeling: User's Guide

Previous: 3.2.2 Within classes Up: 3. Functionalities for Object Next: 3.3.1 Integrity constraints derived

---

Release 0.9, documentation updated on March 4, 2006.

Comments are welcome: Sebastien Bigaret / Modeling Home Page
Hosted by: