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 namespace1.MyObject;
declare MyLocalType
val: namespace2.MyObject
end
rule "r1"
when
MyObject( attr1 == "foo" ) //Here, got a parsing error stating
"attr1" is not a field because it looks it up from namespace2.MyObject
then
MyLocalType $mlt = new MyLocalType();
$mlt.setVal( new namespace2.MyObject() );
insert( $mlt );
end
*Sample3 (continues Sample2 as the following is in the same DRL file):*
rule "r2"
when
MyObject()
//Here: there is no name conflict but, at execution time, the rule is
not activated;
//fully qualifying the fact type solved the issue (meaning activation
seems to wait for namespace2.MyObject to fire the rule...)
then
// ...
end
On 28 October 2011 13:34, abr <alexis.brouard(a)haulogy.net> wrote:
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 namespace where there was a name conflict resolved the
issues.
However, something seem to go wrong when parsing and, sometimes, executing.
Alexis
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Regression-5-1-5-2-with-con...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users