| Key: |
MULE-3759
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Ross Mason
|
| Reporter: |
Ross Mason
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Labels: |
|
| User impact: |
High
|
| Effort points: |
1
|
| Affects Docs: |
Yes
|
| Migration Impact: |
Users need to be made aware that they need to explicitly configure the endpoint synchronous flag for every endpoint. The good thing now is that the configuration is indeed explicit, removing some of the "black art" of configuring routers in Mule.
Users need to be made aware that they need to explicitly configure the endpoint synchronous flag for every endpoint. The good thing now is that the configuration is indeed explicit, removing some of the "black art" of configuring routers in Mule.
|
|
Having this param in the API cause inconsistent routing behaviour since some routers use this param others use the synchronous flag on the endpoint being dispatched to (this is the correct behaviour). Removing this param (which comes from the inbound endpoint) ensures that routers behave in a consistent way according to the configuration of the endpoints.
|
|
Description
|
Having this param in the API cause inconsistent routing behaviour since some routers use this param others use the synchronous flag on the endpoint being dispatched to (this is the correct behaviour). Removing this param (which comes from the inbound endpoint) ensures that routers behave in a consistent way according to the configuration of the endpoints. |
Show » |
|
Remove the synchronous param from the Router.route API methods
