Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.0.0-RC1
-
Fix Version/s: 2.0.0-RC2
-
Component/s: Core: Configuration
-
Labels:None
-
User impact:Medium
-
Similar Issues:
MULE-2839"inbound-router" element name seems wrong
MULE-4168 A wiretap filter affects all inbound routersMULE-2078inbound endpoints within <router> tags do not get registered as listenersMULE-3170Inconsistent configuration of Inbound vs. Outbound routersMULE-3410idempotent-receiver-router should have "disablePersistance" and "storePath" attributes in schemaMULE-5298Creating Custom Routers topic mentions inbound routersMULE-3585recipient-list-routerMULE-4731Mule sends Transfer-Encoding header when used with servlet transport, confusing the servlet containerMULE-2901abstractConnectorType does not have a name attributeMULE-4100Support failOnTimeout option for all inbound aggregator routers
Description
Some thoughts on the inbound router element and type names (note that some my confusion could very well be due to my lack of understanding of what these routers do)
idempotent-receiver-router : idempotentReceiverType
- Type name should end with "RouterType" to be consistent.
- Is "Receiver" in element and type name unnecessary?
- If it is necessary, would "Inbound" be more consistent that "Reciever"?
idempotent-secure-hash-receiver-router : filteredInboundRouterType
- Should this be of type idempotentReceiverType?
- See above, can "Receiver" be removed?
message-chunking-aggregator-router : correlationRouterType
correlation-resequencer-router : correlationRouterType
correlation-aggregator-router : correlationAggregatorRouterType
- Should message-chunking-aggregator-router be of type correlationAggregatorRouterType?
- Or should aggregator be removed and the name be correlation-message-chunking-router?
Ted, I can comment on the general naming convention. The major point is that those are standard names for EIP and people quickly get an idea when they see the familiar name. This applies to idempotent-receiver and aggregators with resequencers. The router suffix is added to hint what it is in Mule internal terms.