[#MULE-3950] Filtering Router improvements

Mule

Filtering Router improvements

Created: 15/Nov/08 01:36 PM Updated: 30/Nov/08 10:18 AM

Component/s:

Core: Routing / Filters

Affects Version/s:

2.1.1

Fix Version/s:

2.2

Time Tracking:

Not Specified

Issue Links:

Block

This issue is blocked by:

~~MULE-2554~~ Consider deleting the MessageBuilder component

Labels:
User impact:	High
Affects Docs:	Yes
Migration Impact:	We'd need to document the preferred approach for configuring this router. I wouldn't change the current behaviour in order to maintain backward compatibility

Description

« Hide

1) The filter should be honoured on the endpoint instead of configuring it on the Router itself. This is a throwback to how the router was originally implemented
2) The router should only allow a single endpoint to be configured

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Ross Mason added a comment - 30/Nov/08 10:18 AM

I have made the restrictions to the number of endpoints in the schema, but not the code since that would mean introducing a new router base class, which is a bigger job and not really necessary.

Also the Filter behaviour is as before, since the filter on the router determines if the router will actually be used. For routers that support multiple endpoints the filter on the endpoint is then used to determine in the current message should be routed through the endpoint.