MVEL has nothing to do with the possibility of using abcXyz in a constraint instead of the more cumbersome getAbcXyz(). Actually, abcXyz is the "native" way of accessing a fact's attribute from within DRL patterns. So, if getAbcXyz() works, but abcXyz does not, I suspect that something else is amiss, perhaps in the code of AnEvent.java, which hasn't been posted. -W On 09/05/2014, jlprat <jlprat(a)gmail.com&gt; wrote:

You are using a class called KnowledgeBuilder. With Drools 6, it is KieBuilder. Here is some simple code, good for testing (as I used it), although more sophisticated build procedures are recommended using maven and what not. - Both DRL versions (getAbxDef and abcDef) appear to work with 6.0.0 Final. KieServices kieServices = KieServices.Factory.get(); KieFileSystem kfs = kieServices.newKieFileSystem(); FileInputStream fis = new FileInputStream( "lostrule/lostrule.drl" ); kfs.write( "src/main/resources/lostrule.drl", kieServices.getResources().newInputStreamResource( fis ) ); KieBuilder kieBuilder = kieServices.newKieBuilder( kfs ).buildAll(); Results results = kieBuilder.getResults(); if( results.hasMessages( Message.Level.ERROR ) ){ System.out.println( results.getMessages() ); throw new IllegalStateException( "### errors ###" ); } KieContainer kieContainer = kieServices.newKieContainer( kieServices.getRepository().getDefaultReleaseId() ); KieBaseConfiguration config = kieServices.newKieBaseConfiguration(); config.setOption(EventProcessingOption.STREAM); KieBase kieBase = kieContainer.newKieBase( config ); kieSession = kieContainer.newKieSession(); On 09/05/2014, jlprat <jlprat(a)gmail.com&gt; wrote:

Repeated executions show varying results: sometimes it's OK, sometimes it isn't. I don't think it's a race condition in your code (although proper syncing on the map would be the "clean" way to go). I think that salience doesn't work properly )(6.0.0, OP used 6.0.1.), if a fact is matched unconditionally by a high salience rule and the same fact is matched using constraints in rules with lesser priority. (Wasn't this recognized before as a bug in 6.0.x?) -W On 12/05/2014, jlprat <jlprat(a)gmail.com&gt; wrote:

Hi Josep, probably there are 2 different issues here, but I am not sure because I haven't run your test case yet. I'll do it asap. The first issue could be something similar to what has been already reported here https://issues.jboss.org/browse/DROOLS-311 As for the different behaviour you found in using the property name vs. accessing it with the getter the only thing I can say at the moment is that Wolfgang is right when he wrote that it doesn't depend on mvel. At the moment I think that you're just experiencing a weird side effect of the problem reported in DROOLS-311, but again I cannot be sure until I haven't given a run to your test case. I'll keep you updated on my findings. Thanks for having reported this, Mario -- View this message in context: http://drools.46999.n3.nabble.com/Rules-don-t-execute-using-MVEL-syntax-i... Sent from the Drools: User forum mailing list archive at Nabble.com.

Hi Mario, is there any progress? Could you find anything? Best, Josep -- View this message in context: http://drools.46999.n3.nabble.com/Rules-don-t-execute-using-MVEL-syntax-i... Sent from the Drools: User forum mailing list archive at Nabble.com.

On 12/05/2014, jlprat <jlprat(a)gmail.com&gt; wrote: You have Map<String, Integer> ruleCalls, which is updated from the event handler from the thread running fireUntilHalt() and checked in the thread inserting the events. The sleeps should be long enough, but it's not comme-il-faut. -W