Created attachment 829653 [details] the process definition with a rest task Description of problem: I have a process with a REST task, for which the Rest work item handler is registered in business-central.war/.../META-INF/CustomWorkItemHandlers.conf : "Rest": new org.jbpm.process.workitem.rest.RESTWorkItemHandler() But when I want to start this process, I receive WorkItemHandlerNotFoundException: Could not find work item handler for Rest This is the element for the webservice task <bpmn2:task id="_4" tns:taskName="Rest" name="Any Rest Operation"> but I'll attach the whole process definition. I also noticed that the rest service is not available in BPMN web designer, so it might mean something. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start a process containing a rest task 2. See WorkItemHandlerNotFoundException in the server log Actual results: Expected results: Additional info:
This issue is very similar to BZ 1035256 where a web service work item handler cannot be found.
problem was caused be not found CustomWorkItemHandlers.conf file due to not using correct class loader. Since the BPMS uses EAP modules it was not using the web app class loader to look up for resources and thus these work item handlers were not registered. fixed by ensuring that the context class loader is used to look up resources as well which in EAP is the web application class loader. droolsjbpm-knowledge master: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/3aa65069b5b2169603341d5c3cf95a603de4ad1f 6.0.x: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/6a97078da7ebe799f44baebefd762287fc1c1c1d
*** Bug 1035256 has been marked as a duplicate of this bug. ***
Workaround: go to bpms-6.0.0.ER5/jboss-eap-6.1/standalone/deployments/business-central.war/WEB-INF/classes/META-INF and move the following two files to your home directory: drools.session.conf CustomWorkItemHandlers.conf
Kris, thank you... I didn't know about this feature :) I can confirm that it works with this workaround.
Verified in BPMS 6.0.0.ER7