[rules-users] Conflict detection problem

[Wolfgang Laun]

Some other techniques:

(1) Authors must avoid "magic numbers". Define constants such as
MAX_MINOR_AGE in Java. Compiled rules could be inspected to detect literals.

(2) getters can be written to compare the old value against the argument.
(This may mean that simple types have to be avoided in fact classes to have
null as an indication.)

(3) You could use Property Change Listener, which could also be used to
inform the engine about fact changes.

(4) Listening for Working Memory Events in combination with Activation
Events could be used in combination with Java reflection to detect duplicate
updates.

-W







On 11 March 2011 11:35, AlisterC <alister.crepy at dps-fr.com> wrote:

> Thanks a lot, Thomas. I am going to test this decoupled approach.
>
> Alister
>
> --
> View this message in context:
> http://drools-java-rules-engine.46999.n3.nabble.com/Conflict-detection-problem-tp2664121p2664253.html
> Sent from the Drools - User mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20110311/1af6b354/attachment.html