[Seaside] object validation pattern?

[Paul DeBruicker]

The VW validation framework discussed in this paper is MIT licensed but 
hasn't yet been ported to Pharo:

http://www.caesarsystems.com/resources/caesarsystems/files/Extreme_Validation.pdf


The framework is the 'Assessments' package (parcel?) by Andres Valoud.


On 10/15/2012 07:39 AM, sergio_101 wrote:
> hey, all..
>
> i was wondering what the current best practice is for handling object
> validation..
>
> how do we define if an object is valid, and if not, what happens to
> that object?
>
> with my current day job framework, the validity of an item is directly
> tied to the model. if you try to save an invalid object, it fails.
>
> i know we can use magritte for this,  but this seems a little heavy
> weight of a solution for something i need at all times.
>
> is there a best practice or anything on how to handle this?
>
> thanks!
>