Please do! We will all thank you.
Regarding checking all the conditions in the LHS, that's what the engine
does best, so always avoid "if"s in the RHS... in the LHS they get indexed,
shared, hashed, etc, whenever possible, improving the performance of the
whole system.
[]s
Edson
2007/7/
Edson,
Thank you very match. I've found a lot of ideas from your response. I didn't
think about moving all conditions to LHS first and planned to use LHS only as a
filter to find object to validate in RHS. I'll try to implement prototype and
share experience in a list if you don't mind.
Oleg.
Oleg,
As I mentioned to you, it is perfectly fine and easy to use the rules
engine to validate your object tree as long as you instruct your users that
they must write structured rules. What I mean is: as much as DSL templates
allow you to write rules that resemble natural language, it is not
Hi.
I've got a lot of domain objects represented as instances of classes generated
from XSD using Castor. My goal is to implement validation framework for whole
tree which contains complex "when" conditions (see bellow). Furthermore, rules
definitions should be very easy for unexperienced user
