I think that the idea is that WI should be isolated from the context itself. WI receives parameters, and do some work. When someone completes the WI (that someone could be the WI itself, or some other async process from outside) output parameter could be included. So if you need to read a context variable to make some kind of decision inside your WI, map it to the WI's parameters. If you need to modify a context variable, you could use the WI's output parameters in conjunction with another process node.

Best, 

On Tue, Jun 1, 2010 at 12:47 AM, blackrosey <blackrosezy@gmail.com> wrote:

How do I access kcontext in custom workItem?

public void executeWorkItem(WorkItem i, WorkItemManager m) {
   // I want kcontext variable here
}

Thanks.
--
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/RuleContext-aka-kcontext-in-workItem-tp860256p860256.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users



--
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Esteban Aliverti