This is actually a problem with using Drools Flow in stateless sessions in
general, regardless of the Drools-Server.
See this post for details:
http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-within-St...
This may be fixed in the trunk. I am not sure.
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/RuleFlow-only-calling...
Sent from the Drools - User mailing list archive at
Nabble.com.