[rules-users] Intercept event handling / why rule salience does not affect execution order?

jpullmann jaroslav.pullmann at fit.fraunhofer.de
Fri Oct 26 11:46:24 EDT 2012


 Wolfgang, 

  here comes an Eclipse/Maven project with simplified sources. I'd expect to
 see messages from higher ranked intercepting rules for any of the events
sent, 
 which is not the case... 

rule "Intercept context creation"
    salience 10
    when        
       	$start : StartCommand() from entry-point "events/context"
       	not( Context( name == $start.name ) )
    then    	    
    	System.out.println("Context "+$start.getName()+" to be created");
end

rule "Intercept context removal"
    salience 10
    when        
       	$end : EndCommand() from entry-point "events/context"
       	Context( name == $end.name )
    then    	    
    	System.out.println("Context "+$end.getName()+" to be removed");
end

		Context Context_0 to be created
		Context Context_0 to be removed
		Context Context_1 to be removed --
		Context Context_2 to be removed --
		Context Context_3 to be removed --
		Context Context_4 to be created
		Context Context_4 to be removed --

  Best regards 
   Jaroslav



Example.zip <http://drools.46999.n3.nabble.com/file/n4020513/Example.zip>  



--
View this message in context: http://drools.46999.n3.nabble.com/Intercept-event-handling-why-rule-salience-does-not-affect-execution-order-tp4020506p4020513.html
Sent from the Drools: User forum mailing list archive at Nabble.com.


More information about the rules-users mailing list