Some other techniques:<br><br>(1) Authors must avoid &quot;magic numbers&quot;. Define constants such as MAX_MINOR_AGE in Java. Compiled rules could be inspected to detect literals.<br><br>(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.)<br>
<br>(3) You could use Property Change Listener, which could also be used to inform the engine about fact changes.<br><br>(4) Listening for Working Memory Events in combination with Activation Events could be used in combination with Java reflection to detect duplicate updates.<br>
<br>-W<br><br><br><br><br><br><br><br><div class="gmail_quote">On 11 March 2011 11:35, AlisterC <span dir="ltr">&lt;<a href="mailto:alister.crepy@dps-fr.com" target="_blank">alister.crepy@dps-fr.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks a lot, Thomas. I am going to test this decoupled approach.<br>
<br>
Alister<br>
<font color="#888888"><br>
--<br>
View this message in context: <a href="http://drools-java-rules-engine.46999.n3.nabble.com/Conflict-detection-problem-tp2664121p2664253.html" target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/Conflict-detection-problem-tp2664121p2664253.html</a><br>


</font><div><div></div><div>Sent from the Drools - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
rules-users mailing list<br>
<a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-users" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</div></div></blockquote></div><br>