Re: [rules-users] Web client-side rule testing - best practices

I thought I should clarify something. I am not looking for Drools to deal with such UI-specific issues as enabling and disabling fields, what screen to show next, etc. Rather, we are developing a rich set of rules on the server to validate fully populated data structures that we get from multiple sources. There is a subset of those rules which apply to the UI (e.g. regular expression, value ranges, etc). I am trying to: a) avoid having multiple versions of the rules (one for the server and a different one, in Javascript, for the client); b) avoid waiting until the user submits the data to the server to provide them feedback from the shared rules. The question is, are there best practices for: a) designing the rules such that they can handle both cases (field validation and record validation); b) connecting the Web browser to the server (e.g. Ajax) to support this testing. -- View this message in context: http://drools.46999.n3.nabble.com/rules-users-Web-client-side-rule-testin... Sent from the Drools: User forum mailing list archive at Nabble.com.