Mark,
If this is inside DefaultRightMemory, it might be related to
indexing, but the DefaultRightMemory itself is not indexed. I will take
a look.
[]s
Edson
Mark Proctor wrote:
I wonder if this is to do with the new indexing stuff? If we can
isolate the issue we should produce a unit test to track this issue
for regression.
Mark
Alexander Bagerman wrote:
Michael,
It is very easy to see if you run
org.drools.examples.waltz.ReteooWaltzTest as JUnit test. If I remember
it correctly it start failing DefaultRightMemory.remove(WorkingMemory
workingMemory, ObjectMatches matches) with matches being null. not
null check uncovers another place on stack that has similar problem. I
might be off in terms of the exact location but I suggest you run and
see it for yourself.
Thanks
-Alex
-----Original Message-----
From: Michael Neale [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 3:32 PM
To: [email protected]
Cc: Mark Proctor
Subject: Re: [drools-dev] Re: New ClassFieldExtractor
are these nulled out node references?
On 3/14/06, Alexander Bagerman <[EMAIL PROTECTED]> wrote:
Mark,
Somebody should definitely take a look at waltz under reteoo. I
started going up the stack of NullPointerException and found several
places on the stack where exception can be thrown. I gave up after
third place where I put if ( != null) { without getting into what is
going on in that part of the code.
-Alex
--
---
Edson Tirelli
Auster Solutions do Brasil
@ www.auster.com.br
+55 11 5096-2277 / +55 11 9218-4151
