[rules-users] activationCancelled() not being executed?

[Edson Tirelli]

   It is really difficult to answer that since your understanding seems
correct. Is it possible for you to provide a self contained test showing the
problem?

   []s
   Edson

2007/10/11, Fermion <henss at physik.uni-wuppertal.de>:
>
>
> It's been a while since I had time to investigate this problem.
>
> I followed your advice and hooked up the DebugAgendaEventListener to my
> workingMemory instance.
>
> This clearly shows, that my activations are created but never canceled. So
> at least it is consistent with what I'm observing in my application.
>
> But before I start even considering it being a bug (I'm quite sure it is
> not), maybe it's better to understand what is happening in my code:
>
> I think that I nailed my problem down to an issue with my fact IDs:
>
> If I have, for example, a real world value (lets say a temperature) that
> is
> connected to a java bean, my understanding is, that the fact ID of this
> value inside the workingMemory should not change, even if I change the
> real
> world value (temperature rises)(and thus the java beans value).
> In fact the change is propagated to the working memory (as I call
> "firePropertyChange" inside my bean), but a NEW rule is activated by the
> changed fact, having a DIFFERENT fact ID!
>
> I'm quite sure that this is the reason for my problem with the missing
> cancellations. I'd assume that for a rule to be canceled the fact with the
> CORRECT fact ID would have to be changed.
>
> Now, in my application, it seems that every modification creates a NEW
> fact
> inside the working memory (which is of course not, what I want).
>
> I had the hope, that calling the firePropertyChange from inside the beans
> "setters" would notify the working memory automatically about the correct
> fact-ID.
>
> I checked my "equals()" and "hashCode()" methods but the hash code is
> always
> constant and equals is correspondingly true. I also checked that I don't
> accidentally re-assert the fact on modification.
>
> So what I don't understand is WHY the working memory thinks that the fact
> ID
> has changed...
>
> See you,
>
> fermion
> --
> View this message in context:
> http://www.nabble.com/activationCancelled%28%29-not-being-executed--tf4348054.html#a13158335
> 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
>



-- 
  Edson Tirelli
  Software Engineer - JBoss Rules Core Developer
  Office: +55 11 3529-6000
  Mobile: +55 11 9287-5646
  JBoss, a division of Red Hat @ www.jboss.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20071011/e622008a/attachment.html