I am using an aggregator with a custom repository that extends
MemoryAggregationRepository.
I am doing this to implement some fuzzy logic in my key matching. For
example:
message 1, key = 1234#abc#def
message 2, key = 1234#xxx#def
So long as the first and last tokens match then I need to combine them.
To achieve this I've overridden the get method and implemented my matching
logic there. I suspect that this may be causing my problem as I keep getting
duplicate messages in my aggregation strategy (e.g. multiple copies of
message #1, or multiple copies of message #2).
What has me confused as well is the fact that when I compare these 2 objects
in the aggregation strategy:
String oldBody = oldExchange.getIn().getBody( String.class );
String newBody = newExchange.getIn().getBody( String.class );
They come back as not equal, despite the fact that the show as equal in the
log (I dump the whole exchange out to the log).
Has anyone encountered something like this before or have any ideas on where
I might have made a mistake?
--
View this message in context:
http://camel.465427.n5.nabble.com/aggregator-duplicate-messages-tp5738848.html
Sent from the Camel - Users mailing list archive at Nabble.com.
