abhijithumbe opened a new issue, #2368:
URL: https://github.com/apache/incubator-kie-issues/issues/2368

   Not able to use kcontext in the onEntry/onExit script of custom workItems. 
Process execution is failing with error:
   
   
ERROR|9db0cd03-f1be-45ef-9868-dddb8982a670|org.jbpm.workflow.instance.impl.NodeInstanceImpl|Error
 Process instance with id 9db0cd03-f1be-45ef-9868-dddb8982a670 failed because 
of [Error: unresolvable property or identifier: kcontext] [Near : {... 
;System.out.println(kcontext.getVariable("var1")); ....}] ^ [Line: 1, Column: 
62] executing node instance 'd23ef41a-0751-455d-9548-5a54b72a23da' (node 
'Start' id: '_82EB49D3-0596-4565-A360-F03E937DA2D4') in process instance 
'9db0cd03-f1be-45ef-9868-dddb8982a670' (process: 'Test') in a transactional 
environment (Wrapping) 2026-04-17 
13:18:46.632|ERROR||io.quarkus.vertx.http.runtime.QuarkusErrorHandler|HTTP 
Request to /Test failed, error id: b8278c8d-aa36-4402-94e3-9841d27aecad-1: 
org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException: 
Cannot invoke 
"org.kie.kogito.process.workitems.InternalKogitoWorkItem.getStringId()" because 
"this.workItem" is null at 
org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(E
 xceptionHandler.java:107) at 
org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:344)
 at 
org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:205)
 at 
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:452)
   
   
   Change the default expression format from mvel to java


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to