On 26/04/2012, bardelman <feki.ahmed.job(a)gmail.com&gt; wrote: You don't keep "state" in globals with a stateful session either, so your question is moot. If you don't have the need for a global, then don't use it. Probably, if I interpret your "request scope" correctly. -W

Think of a stateless knowledge session as being a statefull knowledge session, with the following adjustments: A stateless knowledge session cannot be manipulated prior the start of the session. A stateless knowledge session cannot be manipulated or queried after the end of the session. A stateless session begins when you execute the fireallrules method. A stateless session ends when the rule processing terminates. -- There is no pause, there is no restarting. The instant the rules stop firing, and return to your calling code, the knowledge session has been torn down. -----Original Message----- From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of bardelman Sent: Thursday, April 26, 2012 2:06 AM To: rules-users(a)lists.jboss.org Subject: [rules-users] Setting variables in a stateless session hi folks, this is a simple question , i just want to understand how is it possible that a stateless session have a setGlobal() method as it does not maintain a state. What's the point ?! i also have some confusion between a "request scope" and a "stateless session scope" i think it s the same.. -- View this message in context: http://drools.46999.n3.nabble.com/Setting-variables-in-a-stateless-sessio... 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