On Tue, May 13, 2008 at 3:29 PM, Rickard Öberg <[EMAIL PROTECTED]> wrote: > Michael Hunger wrote: > > The phases were: > > 1) syntax check (i.e. input formats) > > 2) mandatory checks (not null) > > 3) property check (business validation per property) > > 4) entity checks for depenedend property for the whole entity or even > > encompassing related entities > > > > we used an reflection based mechanism to provide the validation code per > > property or bean having the property name in the method name and giving > > enough context needed for the validation. > > Sounds reasonable. Constraints in Qi4j can be used for 1-2, and some of > 3, and should explicitly NOT be used for 4.
Shouldn't the "Business Rule Violation" scenario be modeled using some type of workflow?? And if so, what kind of support would we need in Core, to allow BR workflows to be easily implemented? Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
