Mule
  1. Mule
  2. MULE-4985

No way to control when async REPLY_TO happens

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0-M4
    • Fix Version/s: Product Backlog
    • Component/s: Modules: CXF
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-5026Async Reply: If endpoint used by the async reply is set to "request-response" then AbstractAsyncRequestReplyRequester will wait for ever for reply
      MULE-5445No reply in async request-reply scenario
      MULE-4967The @Reply annotation in iBeans could be repurposed to offer a "Reply Callback" for async or chained responses
      MULE-4370async-reply throws IllegalStateException when reply has ExceptionPayload
      MULE-5735async-reply (services) and reqeust-reply (flows) fail in cluster
      MULE-5096Transformation result gets lost in a router chaining an async-reply service to a one-way service
      MULE-4116Synchronous invocation inside chaining router doesn't work with async-reply
      MULE-1987Reply-to property being handled to early in message flow
      MULE-7208foreach -> async -> foreach results in thread access control error
      MULE-380ChainingRouter sync/async behaviour

      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 ]

          People

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

            Dates

            • Created:
              Updated:

              Development