[jboss-jira] [JBoss JIRA] Commented: (JBRULES-1165) StatelessSession does not have the ability to set globals.

[Mark Proctor (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBRULES-1165?page=comments#action_12376017 ] 
            
Mark Proctor commented on JBRULES-1165:
---------------------------------------

ok, I have done this locally now. A user user can specify a GlobalExporter strategy, if not supplied no globals are exported. We provide two default export impl, at the moment. One creates a new map based GlobalResolver based on the provided identifiers, and copies from he original global resolver, if no identifiers given it copies all identifies given in the RuleBase. The other one just does a straight reference copy to the original GlobalResolver.


session.setGlobalExpoert( new CopyIdentifiersGlobalExporter( new String["List", "People"] );

then when they do the session.executeWithResults the returned StatelessSessionResult will have it's own GlobalResolver as created by the GlobalExporter impl.

Sound ok? Will commit tomorrow.

> StatelessSession does not have the ability to set globals. 
> -----------------------------------------------------------
>
>                 Key: JBRULES-1165
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-1165
>             Project: JBoss Rules
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions: 4.0.1
>            Reporter: Michael Neale
>         Assigned To: Mark Proctor
>             Fix For: 4.0.2
>
>
> Most likely an oversight. However, to keep the stateless nature of the API - there isn't another way to do this other then add more methods to the interface, unfortunately. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira