@Anatoly,
<br><br>Thanks for the feedback.
<br><br>&gt;&gt;    If they have access to globals, they would become always stateful, which is not _always_ the desired behavior. 
<br><br>I don't see this, any more than with any other data. &nbsp;If the WorkItem or WorkItemManager interface supplied a getGlobal(String name), and the WorkItemHandler doesn't stuff it away in a field or otherwise retain it as state, then it's not stateful - unless I'm missing something.
<br><br>&gt;&gt;    But you can map all the variables into the handler, can't you? 
<br><br>Yes, if I must. &nbsp;But some resources used by workitems need to be configured by either the process initiator or a process participant, yet don't make sense in the variable domain. &nbsp;Consider, e.g., a process where multiple workitems need to access a database - but the selection of database is up to the process initiator. &nbsp;The connection credentials don't really belong in a variable, at least as I understand the intended uses for globals and variables.
<br><br>-Ed
<br>
<br><hr align="left" width="300">
View this message in context: <a href="http://n3.nabble.com/Access-to-globals-from-WorkItemHandlers-tp732460p732724.html">RE: Access to globals from WorkItemHandlers?</a><br>
Sent from the <a href="http://n3.nabble.com/Drools-User-f47000.html">Drools - User mailing list archive</a> at Nabble.com.<br>