Mark,

 

Thanks for the reply. Are there any plans to make this functionality available directly via the API, rather than having to add a "dummy" rule into a rulebase in order to get workflow to work with stateless sessions?

 

I can see how to make the change myself to ReteooStatelessSession  by adding a setRuleFlow method that sets a private processId instance that all the execute methods can start if set (I guess an unset method wouldn't be needed for stateless sessions). An alternative might be to add variants of the existing execute and executeWithResults that also takes a Ruleflow processid, but I think this would add too many variations of execute. I'll probably have to make this change to use drools with the current application I'm writing, as modifying the rules will not be an option - I'm happy to submit the changes if you think this is worthwhile.

 

Shahad

 

 

On 8/10/07, Mark Proctor <mproctor@codehaus.org> wrote:

you would have to call drools.getWorkingMemory().startProcess(id) from inside of a consequence.

Mark
Shahad Ahmed wrote:

Does anyone know if it's possible to use a ruleflow with a StatelessSession?

 

The current documentation and API seem to show examples with StatefullSessions i.e.:

 

statefullSession.startProcess(id);

statefullSession.fireAllRules();

etc...

 

However, there doesn't seem to be anything equivalent in the API for StatelessSesssion's. I'd really like to be able to use the new sequential mode (i.e. with a StatelessSession) and ruleflow.

 

Regards,

Shahad

 

 

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
  

 

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users