[esb-issues] [JBoss JIRA] Closed: (JBESB-1457) Store original replyTo when invoking jBPM process

[Kevin Conner (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBESB-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Conner closed JBESB-1457.
-------------------------------

    Resolution: Done


There is now support in the jBPM integration to enable the delivery of messages to the ReplyTo/FaultTo EPRs of the originating message (the one responsible for creating the process instance).

This can be enabled in jboss-esb.xml by defining the reply-to-originator property with a value of "true", for example

      <actions mep="OneWay">
        <action name="create_new_process_instance"
          class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor">
          <property name="command" value="StartProcessInstanceCommand"/>
          <property name="process-definition-name" value="jBPMReplyTest"/>
          <property name="reply-to-originator" value="true"/>
        </action>
      </actions>

This will cause the BpmProcessor to copy the ReplyTo/FaultTo EPRs into the jBPM so that they can be used in subsequent calls to EsbNotifier/EsbActionHandler.

The EPRs can be used in EsbNotifier/EsbActionHandler by setting the replyToOriginator to a value of "reply" or "fault", for example

      <event type="node-enter">
         <action name="notify" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbNotifier">
            <replyToOriginator>reply</replyToOriginator>
         </action>
      </event>

and

      <action name="sendToESB" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler">
         <replyToOriginator>fault</replyToOriginator>
      </action>

This has been committed in revisions 21219 and 21220.

> Store original replyTo when invoking jBPM process
> -------------------------------------------------
>
>                 Key: JBESB-1457
>                 URL: https://jira.jboss.org/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
>            Assignee: Kevin Conner
>            Priority: Optional
>             Fix For: 4.4
>
>
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira