On Sat, Dec 4, 2010 at 2:04 AM, ext2 <x...@tongtech.com> wrote: > Hi, Claus: > > It's a exciting feature. Hoping it will be available sooner; > > By the way, it seems the camel 3.0 decide to introduce some new features; > While I am using camel, I often meet some requirement which I think if camel > support it, things will be better; > > I always feel embarrassed to raise these question in camel community. Because > these questions is somewhat coupling with OSGI environment, and they seems go > too faraway from camel.
Dont be. We are all still learning the OSGi beast and how its best used in the enterprise integration space. And with Camel we integrate with OSGi out of the box, so we want it to work well together. Despite that OSGi isn't on everybody's love list. > > But if the camel is gathering requirement, so I am wonder if I could post > these questions freely in Camel Community? Following is some examples: > Yeah of course. I suggest that you post a new thread on each question / idea you have. Then its easier to keep discussion focused on that particular idea. > 1) Dynamic Configurable Component based on OSGI Configuration Admin: > By change the OSGI Configuration at runtime, we could change the behavior of > Camel Component(Even Endpoint)。 > > 2) Dynamic Expression Service Processor: A Transformer, which could using a > expression which is compiled from file's content; and even detecting the > file's changing at runtime. When file changed, the language will be reload > and recompiled; (just like JSP). > > 3)OSGI Component: which can directly expose camel route as a OSGI service. > If so, we can using OSGI Framework as Service Infrastructure, and using camel > as message mediator; and we could leave the JBI (a more heavily Service > Infrastructure than OSGI) aside; > > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
