I second that problem.
Switching from Drools 5.1 to 5.2 or 5.3 brought issues that were resolved by
fully qualifying fact names.
Here are samples illustrating the problem:
*Sample1:*
*Sample2:*
*Sample3 (continues Sample2 as the following is in the same DRL file):*
Like thomas, adding
Added code examples...
*
Sample1:*
import namespace1.MyObject;
rule r
when
namespace2.MyObject( value == 3 )
MyObject( attr1 == foo ) //Here, got a parsing error stating
attr1 is not a field because it looks it up from namespace2.MyObject
then
// ...
end
*Sample2:*
import
I'm in the progress of updating from Drools 5.1 to 5.2 in the hope of solving
problems we are having with intermittent mysteriously missing activations.
I've found a regression with the compiler which I don't know whether anybody
else has noticed before.
In our application we've got two
