Of course, you could just create multiple get/set methods for an attribute.
String myConstraint;
getPredefinedConstraint() {
return myConstraint;
}
setPredefinedConstraint(String predefinedConstraint) {
this.myConstraint = predefinedConstraint;
}
getUnrestrictedConstraint() {
return myConstraint;
}
setUnrestrictedConstraint(String unrestrictedConstraint) {
this.myConstraint = unrestrictedConstraint;
}
Then you can define an enumeration for the ‘predefined’ constraint and not for the
‘unrestricted’ constraint. That way your users can choose to define a constraint on a
random value of their choosing if they feel that they know better.
This whole idea does rather defeat the point of enumerations though...
Steve
On 13 Jan 2014, at 11:31, abhinay_agarwal <abhinay_agarwal(a)infosys.com> wrote:
I want the rules to be written by the business users, not by the
developers.
In my scenario, the developers have no idea about the conditions that the
business user may write.
Regards,
Abhinay
--
View this message in context:
http://drools.46999.n3.nabble.com/Using-both-Drop-Down-Enumeration-and-Te...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users