> For me wireTap is still as if only you could tab the wire once, eg only add > one extra endpoint, >where as multicast I would know I can add more > endpoints. Also the wiretap is categorized as > a System Management pattern. Not the category I would at first for such a > need. > > +1 for recipentList > I do think we should support the existing <recipientList> to handle both > dynamic and static lists of endpoints.
Recipient list as a general solution would work, but it would be good if we could have some kind of indicator that the developer intended an n-part static recipient list was to actually to be a wire tap, with maybe multiple outputs (i.e. they were specifically looking at a system management pattern). >From the perspective of the executable language DSLs, this might be awkward to express, but in the JAXB serialization, a <description/> element containing metadata about the intent would be a useful container for some kind of convention. My angle here is that I'm writing tools that express to the user the intent of the route, and I'd like to be able to round trip a visual model of the route through the XML configuration and back without intent or visual annotation lossage :) I'm not so sure that this is important to the operation of the runtime, which is more concerned about the execution than the intent... --oh
