Add somekind of caching mechanism to ActionProcessingPipeline for jBPM to improve performance. ---------------------------------------------------------------------------------------------- Key: JBESB-3224 URL: https://jira.jboss.org/jira/browse/JBESB-3224 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow, Rosetta Affects Versions: 4.7 CP1 Reporter: Marek Baluch Priority: Critical Each time an ESB service is invoked from a jBPM node a jUDDI lookup is made to find the endpoint reference for JBpmCallback Service. This reference will be used as the target to which the response will be sent. The JBpmCallback Service is represented inside the message as LogicalEPR and for each LogicalEPR a new ServiceInvoker is created. This is the place where jUDDI is accessed. Each such jUDDI lookup takes about 200-300 ms. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira