Issue Details (XML | Word | Printable)

Key: MULE-4985
Type: Bug Bug
Status: Open Open
Priority: To be reviewed To be reviewed
Assignee: Unassigned
Reporter: Dan Diephouse
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

No way to control when async REPLY_TO happens

Created: 29/Jul/10 11:54 PM   Updated: 29/Jul/10 11:54 PM
Component/s: Transport: CXF / XFire
Affects Version/s: 3.0.0-M4
Fix Version/s: None

Time Tracking:
Not Specified

Labels:
User impact: Medium
Affects Docs: Yes
Similar Issues:


 Description  « Hide
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.



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.