Edson Tirelli was heard to exclaim, On 06/24/09 15:43:
Drools 5 is mostly backward compatible with Drools 4. You don't need
to migrate to the new API, although it is recommended.
Ahh, that's good to know. You might want to mention that somewhere in the
release notes, or on the website. It
Oh, ok. Then it is shadow proxy related. :)
Shadow proxies can't override final methods, and if they can't override
them, they can not safely prevent hashcode changes at unsafe points... and
that causes all kind of problems with hashmaps that are used internally.
Drools 5 no longer
I'm running into an NPE using Drools 4.0.7, and I'm stumped by it (stacktrace
below). I made some changes to seemingly unrelated code, and this error started
showing up. It would help me to understand what's going on if someone could
tell me roughly what's going on here. Since the error is
Dirk,
The problem seems not related to shadow facts, but to constraint
resolution and fact data extraction. It might be a bug or not... need more
info.
In any case, the offending rule is not the one you showed. The
offending rule contains a double beta constraint in a join:
Edson Tirelli was heard to exclaim, On 06/24/09 06:14:
The problem seems not related to shadow facts, but to constraint
resolution and fact data extraction. It might be a bug or not... need
more info.
I've also seen the following stacktrace:
java.lang.ArrayIndexOutOfBoundsException:
Dirk
Drools 5 is mostly backward compatible with Drools 4. You don't need to
migrate to the new API, although it is recommended.
Anyway, I understand your concern. My wild wild guess is that the
memberOf operator is complaining about a null in that constraint. If that is
the case, it
