So I'm trying to create a framework for processing messages though Camel. I want to have a user customizable/configurable receiver, some internal routing for queue and logging, etc., it run through a custom processor, and then have an output message make a similar trip back to a customizable/configurable sender. I'm trying to figure out how to do this in Camel. Specifically:
1. Some of my connectors will need to be composites of camel concepts, like a timer with a setBody on it. Is there a good abstraction layer for this already? 2. I need to internally pass around some sort of reference to a connector. I assume I should use either an Endpoint or a URI. Which or should it be something else? 3. What is the best way to let someone easily create a new connector? Should I have them create the Component, the Endpoint, just a producer or consumer, or maybe a processor? I've read enough of the manual to see that Components are basically Endpoint factories, maybe I should provide that and let the users customize the producers and consumers. 4. What is the best way to let the users configure their routes? Is there a canned java method to parse Spring-style xml that I can call? I want to do this on-the-fly, so I don't think using spring/blueprint directly is what I'm after. I'm new to Camel, hence the somewhat rudimentary questions.
