Mule
  1. Mule
  2. MULE-4985

No way to control when async REPLY_TO happens

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: 3.0.0-M4
    • Fix Version/s: None
    • Component/s: Modules: CXF
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      None

      Description

      Currently the Service is responsible for executing the async reply to when it is done invoking the component. However, there are many people who want to reply later in the flow - for instance after a web service is done generating the response XML. Currently there is no way to do so. Also, there is no way to do a reply to from a <flow> (Yes, I recognize flow is quite new, but perhaps they can use the same mechanism which is just a MessageProcessor)

      This worked for CXF/Axis in Mule 2.x because they each had two components - one which invoked the WS engine and one which invoked the real component.

        Activity

        Dan Diephouse created issue -
        Daniel Feist made changes -
        Field Original Value New Value
        Issue Type Bug [ 1 ] New Feature [ 2 ]
        Fix Version/s Product Backlog [ 10440 ]
        Priority To be reviewed [ 6 ] Major [ 3 ]
        Ramiro Rinaudo made changes -
        Workflow Fixed Main Mule Workflow (after JIRA upgrade) [ 77754 ] Main Mule Workflow v1.0 [ 137198 ]
        Hide
        Matias Baldini added a comment -

        Mule issues cleanup.

        Show
        Matias Baldini added a comment - Mule issues cleanup.
        Matias Baldini made changes -
        Resolution Won't Fix or Usage Issue [ 2 ]
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s Product Backlog [ 10440 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        To Do To Do Closed Closed
        2076d 13h 20m 1 Matias Baldini 05/Apr/16 01:14 PM

          People

          • Assignee:
            Unassigned
            Reporter:
            Dan Diephouse
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development