Hi, I have a use case where we would like to have end users define BAM rules that can be read by Camel. I would like to persist their criteria to a database and then build the BAM rules dynamically at runtime. I might have the need to do this with routes as well, but I am not entirely sure yet.
I was investigating approaches for handling this, and I was thinking something like: 1. GUI writes rules to the database and publishes a message to a topic saying that rules have changed 2. Have a subscriber read the rules from DB 3. Get the CamelContext from the container and remove any rules that are have changes or are deleted 4. Add the rules to the CamelContext This all certainly seems possible from an API standpoint, but can you alter the CamelContext while you have active brokers processing messages? If yes, are there any pitfalls to this approach? Thanks. -- View this message in context: http://www.nabble.com/Adding-Components-Dynamically-tp14317514s22882p14317514.html Sent from the Camel - Users mailing list archive at Nabble.com.
