jbpm5 integration : Allow mappings from different parts of the message ---------------------------------------------------------------------- Key: JBESB-3866 URL: https://issues.jboss.org/browse/JBESB-3866 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Process flow Affects Versions: 4.11 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP2 From Martin Weiler : Looking at the jBPM 5 integration code, the mapping of ESB information into jBPM is now restricted to message properties: BpmParameterMapper: params.put(mappingsOfParams.get(esb), msg.getProperties().getProperty(esb)); In the jBPM 3 integration code, the generic esb ObjectMapper was used instead: JBpmObjectMapper: value = objectMapper.getObjectFromMessage(message, mapping.getEsb()); This approach offers much more flexibility, as it allows to extracts object from various locations of the message, not just from the message properties.

From Martin Weiler :

jbpm5 integration : Allow mappings from different parts of the message ---------------------------------------------------------------------- Key: JBESB-3866 URL: https://issues.jboss.org/browse/JBESB-3866 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Process flow Affects Versions: 4.11 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP2 From Martin Weiler : Looking at the jBPM 5 integration code, the mapping of ESB information into jBPM is now restricted to message properties: BpmParameterMapper: params.put(mappingsOfParams.get(esb), msg.getProperties().getProperty(esb)); In the jBPM 3 integration code, the generic esb ObjectMapper was used instead: JBpmObjectMapper: value = objectMapper.getObjectFromMessage(message, mapping.getEsb()); This approach offers much more flexibility, as it allows to extracts object from various locations of the message, not just from the message properties.

jbpm5 integration : Allow mappings from different parts of the message ---------------------------------------------------------------------- Key: JBESB-3866 URL: https://issues.jboss.org/browse/JBESB-3866 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Process flow Affects Versions: 4.11 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP2 From Martin Weiler : Looking at the jBPM 5 integration code, the mapping of ESB information into jBPM is now restricted to message properties: BpmParameterMapper: params.put(mappingsOfParams.get(esb), msg.getProperties().getProperty(esb)); In the jBPM 3 integration code, the generic esb ObjectMapper was used instead: JBpmObjectMapper: value = objectMapper.getObjectFromMessage(message, mapping.getEsb()); This approach offers much more flexibility, as it allows to extracts object from various locations of the message, not just from the message properties.

jbpm5 integration : Allow mappings from different parts of the message ---------------------------------------------------------------------- Key: JBESB-3866 URL: https://issues.jboss.org/browse/JBESB-3866 Project: JBoss ESB Issue Type: Bug Security Level: Public(Everyone can see) Components: Process flow Affects Versions: 4.11 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP2 From Martin Weiler : Looking at the jBPM 5 integration code, the mapping of ESB information into jBPM is now restricted to message properties: BpmParameterMapper: params.put(mappingsOfParams.get(esb), msg.getProperties().getProperty(esb)); In the jBPM 3 integration code, the generic esb ObjectMapper was used instead: JBpmObjectMapper: value = objectMapper.getObjectFromMessage(message, mapping.getEsb()); This approach offers much more flexibility, as it allows to extracts object from various locations of the message, not just from the message properties.