Re: [rules-users] Field value is different when and then section, very strange. Is it mvel vs java issue

This is a list for support of the drools product, but there is some expectation that you will figure out some basic functionality by reading the docs and putting some thought into it. :) In general, though, the "next rule" is whatever rule matches the objects currently in working memory.  If you don't want a given rule to fire you should make sure that the objects altered no longer match it after they are changed.  In your original example the Account object matched in Rule1 has no conditions on it at all, meaning any Account in working memory will be matched, so it's no wonder that it's being matched repeatedly. Also, I'm puzzled by your calls to StringUtils.equals() in the rule conditions.  Did you not try this? account : Account(accountStatus == "NEW") Again, in the docs, this is the recommended way to test object properties. ________________________________ From: kina06 <reachkn6(a)gmail.com&gt; To: rules-users(a)lists.jboss.org Sent: Tuesday, October 30, 2012 10:12 AM Subject: Re: [rules-users] Field value is different when and then section, very strange. Is it mvel vs java issue This looks like such a basic functionality and I'm not getting any help. I can't seem to understand why update function keep calling the function, is there no way to let drools know that I modifed an object values so it gives me the updated object in next rule. Please help, this is such a basic step without which I cna't proceed any further. -- View this message in context: http://drools.46999.n3.nabble.com/Field-value-is-different-when-and-then-... 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