I tried that but it seems that setting a global on a Stateless session simply
sets a value in a Map without doing any validation, hence no Exception.
What I am doing now is to set the value in the Stateless session. It seems that
those variables are made available to the StatefulSession that sls
But you can
try{ ks.setGlobal(...) } catch( Exception e ){ }
-W
On 14/02/2012, Chris Selwyn wrote:
> Is there a way to test for the existence of a global variable in a
> StatelessKnowledgeSession before inserting a SetGlobal command into a
> BatchExecutionCommand?
>
> I am trying to write a r
Is there a way to test for the existence of a global variable in a
StatelessKnowledgeSession before inserting a SetGlobal command into a
BatchExecutionCommand?
I am trying to write a rules executor class that may execute some rulesets that
need a particular global variable and some that don't.
