[
http://jira.jboss.com/jira/browse/JBRULES-1165?page=comments#action_12375691 ]
Mark Proctor commented on JBRULES-1165:
---------------------------------------
setGlobal and setGobal resolver is already there, but getGlobal isn't. In general
I'm not too happy about people retrieving information from a stateless session, as it
is after all stateless.
I think if we do this it should at least only be on the StatelessSessionResults. The
confusion comes because we allow session re-use, including re-use of the GlobalResolver -
to save continual re-populating. Also if the user kicks off another exececute(...) those
global values could be altered, this is another caveat. There really isn't any clean
way of doing this other than adding complexity to make the user specify what globals can
be retrieved and cloning them in the session results - which isn't something I think
we want to do.
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