[rules-users] XML rule: Wrongly interpreted Numeric String to Number

Dear all, System is generating XML rule file with literal-restriction like that: ... field-constraint field-name=myStringTypeField literal-restriction evaluator=== value=0020 / /field-constraint ... I am expecting the

Re: [rules-users] Object activiates same rule many times

Thanks to Wolfgang and Vincent in pointing the problem. Appreciated! -- View this message in context: http://drools.46999.n3.nabble.com/Object-activiates-same-rule-many-times-tp4000630p4004294.html Sent from the Drools: User forum mailing list archive at Nabble.com.

Re: [rules-users] Object activiates same rule many times

In the RHS of the rule, the function calling by insert only return ChargeDetailRefSeqEntity but not ChargeDetailEntity. That's why I think it is not the area causing recursive activation of the rule. Is that right? -- View this message in context:

[rules-users] Object activiates same rule many times

Hi all, I find an odd pattern in the audit log. When an Object is inserted to the working memory, activation is created many times on same rule. The more objects are inserted, the duplicated activations are growing exponentially which degrade the performance a lot. Here attached part of the

Re: [rules-users] Question about in XML: literal-restriction on null value

Finally, I pick the 1st option because the 2nd option, using return-value-restriction, is not allowed in a MultiRestrictionFieldConstraint (UnsupportedOperationException is thrown). Thanks at all. -- View this message in context:

[rules-users] Question about in XML: literal-restriction on null value

Dear all, My system is transforming internal data structure to drools rule language XML file. For particular evaluation on a string field, how can I do so happen the evaluating value is one of the keywords? For example, I need to check if keyValue==null In rule language in XML,