[
http://jira.jboss.com/jira/browse/JBESB-1457?page=comments#action_12394265 ]
Kevin Conner commented on JBESB-1457:
-------------------------------------
The specification of any reply is part of the business process defined and executed
through jBPM. The jBPM process is also responsible for driving all interactions with the
ESB.
The external application knows nothing about the ESB and nor should it, it is sending a
request to a defined service without any knowledge of it's implementation. All
external interactions with the ESB are adapted using the incoming gateway and any response
service, it should be a simple matter to configure these gateways/services to adapt the
incoming request/response onto the jBPM service.
Store original replyTo when invoking jBPM process
-------------------------------------------------
Key: JBESB-1457
URL:
http://jira.jboss.com/jira/browse/JBESB-1457
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Optional
Fix For: 4.3
The jBPM process use now be default requires to use async processing. The problem is that
there is now no way for the caller how to specify reply address. The replyTo/faultTo
headers are used for internal jBPM message sending.
I think that there should exist standard mechanism that will store original
replayTo/faultTo values and allow to route them final response.
This is so common and basic functionality that customer should not be required to invent
and implement its own mechanism.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira