[rules-users] Rule tasks and gwt-console

[Kris Verlaenen]

Juan,

By default the gwt-console server instantiates one session that is
reused for executing all process instances.  This is however just one
possible architecture.  I think you can easily adapt the current code
(take a look at DroolsFlowCommandDelegate in the drools-gwt-console module).

1) register the session that is created (or a registry of sessions) for
example to JNDI

2) use a session registry to create one session per process instance and
look up or create the session on request.

If you would try to make the existing code more powerful so it can be
configured / instantiated in different setting, we would gladly accept
this and add to the project ;)

Kris

Quoting Juan Ignacio Barisich <juan.barisich at fluxit.com.ar>:

> Hello,
> I'm working with the gwt-console, and I have two questions:
> 1) How to get access and add facts the knowledge session ?
> 2) Is there only one knlowledge session for all the process instances
> ?
> 
> I have a process with a "Rule Task" node. Within the rule I have to
> access
> to the process variables. So, I want to add the process instance to
> the
> knlowledge session.
> Then, the rule (in this consecuence) inserts a fact to the knowledge
> session, so a later gateway can take a desicion rule-based. But, is
> there
> only one knlowledge session for all the process, this logic will
> fail. In
> this way, it would be better to have one knowledge session instance
> per
> process instance.
> 
> Thanks in advance.
> -- 
> 
> *Juan Ignacio Barisich*
> juan.barisich at fluxit.com.ar
> www.fluxit.com.ar
> 53 n366, piso 9
> La Plata / Buenos Aires / Argentina
> (54)-221-427-5781 int:308
> 




Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm