Re: [rules-users] Regression 5.1-5.2 with conflicting ClassNames

2011-10-28 Thread abr
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-conflicting-ClassNames-tp3268164p3460816.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


Re: [rules-users] Regression 5.1-5.2 with conflicting ClassNames

2011-10-28 Thread Michael Anstis
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.brou...@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-conflicting-ClassNames-tp3268164p3460816.html
 Sent from the Drools: User forum mailing list archive at Nabble.com.
 ___
 rules-users mailing list
 rules-users@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/rules-users

___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users


[rules-users] Regression 5.1-5.2 with conflicting ClassNames

2011-08-19 Thread Swindells, Thomas
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 Content classes in different packages, and 
unfortunately one of our rule files has to reason over both of them.
In drools 5.1 this was fine, we imported one of them and then used the fully 
qualified name for the other.

I'm just upgrading to 5.2.0-Final and this no longer works. When resolving the 
unqualified class name drools/mvel(?) was choosing the package that we hadn't 
imported!
This obviously then gave us loads of misleading error messages about not being 
able to find fields.

Fully quallifiying all references to both classes fixed the issue but something 
obviously isn't behaving properly.

Thomas



**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**
___
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users