The JSR-94 specificaion has stateful and stateless rule sessions; Drools' implementation covers both of these. The difference is basically in interface layer more than anything else: is it an API that expects conversational state to be maintained across multiple interactions with a rule engine, or is it an interface wherein the entire rule-engine interaction is encapsulated in a single method call.
Is this what you're asking about? On 3/27/06, Susan G Lee <[EMAIL PROTECTED]> wrote: > > Hi, > > Can you provide an example of having drools as a stateful and stateless > engine? > > > Thanks, > Susan G. Lee > > Distribution and New Ventures > Depository Trust and Clearing Corporation > 55 Water Street, New York, NY 10041 > Phone: 212-855-2883 > E-mail: [EMAIL PROTECTED] > -- Geoffrey Wiseman
