[
https://jira.jboss.org/jira/browse/JBESB-2317?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2317:
-------------------------------------
The CallbackCommand.execute method is where the lookup should occur, not where it is
currently being retrieved.
One of the other tasks we should have, if there is time, would be to simplify all this
integration code. Perhaps some time next week :)
Reduce verbosity of jBPM callback EPRs
--------------------------------------
Key: JBESB-2317
URL:
https://jira.jboss.org/jira/browse/JBESB-2317
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Daniel Bevenius
Fix For: 4.5
The EPR contains information such as variable mappings, information that can be retrieved
from the action rather than passed via the EPRs.
The configuration information is available through the action delegate, albeit as a
string needing to be parsed.
For example, one of the actions in the bpm_orchestration1 has the following
configuration
<esbCategoryName>BPM_Orchestration_Service1</esbCategoryName>
<esbServiceName>Service1</esbServiceName>
<bpmToEsbVars><mapping bpm="theBody"
esb="BODY_CONTENT"/></bpmToEsbVars>
<esbToBpmVars><mapping esb="BODY_CONTENT"
bpm="theBody"/></esbToBpmVars>
There are likely to be other parameters that can be removed from the generated EPR.
--
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