[rules-users] Re: Upgrading from 3.x to 4.0.7
Edson -
Thanks, this is EXACTLY what I was looking for...
-tk
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org
[mailto:rules-users-bounces@lists.jboss.org] On Behalf Of
rules-users-request(a)lists.jboss.org
Sent: Thursday, November 13, 2008 10:38 AM
To: rules-users(a)lists.jboss.org
Subject: rules-users Digest, Vol 24, Issue 48
------------------------------
Message: 4
Date: Thu, 13 Nov 2008 09:02:36 -0500
From: "Edson Tirelli" <tirelli(a)post.com>
Subject: Re: [rules-users] Upgrading from 3.x to 4.0.7
To: "Rules Users List" <rules-users(a)lists.jboss.org>
Message-ID:
<e6dd5ba30811130602i23247e76ub235a3557818121(a)mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Following API call (or equivalent property conf) will make Drools 4
behave like Drools 3.
RuleBaseConfiguration.setRemoveIdentities( true );
[]s
Edson
2008/11/12 Knych, Thomas <thomas.knych(a)citi.com>
Hi -
I'm upgrading a large base of rules from 3.x to 4.0.7. However there
seem to be a few semantic differences. I have rules like the below in
a few places:
rule "All items should have a unique external id"
when
new_item : Item( exId : externalId )
old_item : Item( externalId == exId )
then
LOG.warn( "DUPE Detected: new:" + new_item + " old:"
+
old_item );
retract( new_item );
end
And this all worked fine because 3.x would never assign the same
object to both new_item and old_item. I know my new/old seem arbitary
- but I'm just getting down to the minimal reproducing case. 4.x now
will assign one instance of an object to both new_item and old_item.
Is there any way to disable this behaviour?
thanks,
-Tom
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Edson Tirelli
JBoss Drools Core Development
JBoss, a division of Red Hat @ www.jboss.com