I think I'm misunderstanding how recipientList is being used. I want to send an email message to an arbitrary number of Users (e.g. tens) based on a change/message from hundreds of Projects. Should I be dynamically adding/removing endpoints for hundreds of project-users? The recipient list pattern is for dynamically specifying the route (out of hundreds) to take?
Maybe I should be doing something with Splitter instead? In the end, I start with one message and multiply it to tens of messages that have endpoints that notify the users. I don't understand the line between configuring components and writing code to access the database, etc. that provides all the logic on who gets notified. -- View this message in context: http://camel.465427.n5.nabble.com/Activity-feeds-and-email-notifications-tp5779279p5779417.html Sent from the Camel - Users mailing list archive at Nabble.com.
