Hi
Just a note that Jyrki did some more code contributions, so I have
just pushed his latest changes to the master branch.
Its this PR which has a summary of changes
https://github.com/apache/camel/pull/329
On Sun, Nov 9, 2014 at 9:42 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
There is
The OSGi way to specify the need for a component would be a requirement
and the component would offer a capability.
See http://wiki.osgi.org/wiki/Provide-Capability
On the component side it should be easy to add this.
On the client side the question is if people want to do this by hand ...
I just looked into the camel-scr component.
If found some design issues:
- Why do we need to @Reference to ComponentResolver. I think we should
do this under the covers so the user does not have to configure it himself.
The easiest way would probably be to do this using plain OSGi APIs.
- It
Hi
Christian sounds good if you have the time and willingness to dive
into improving the camel-scr code.
In camel-blueprint / camel-core-osgi is some code that gathers all the
component names, data formats, and languages that are define in the
Camel routes. And then use that to reference as the
Hi Claude
Thanks for the update. I will take a look ASAP.
Regards
JB
Sent from my Samsung Galaxy smartphone.
Original message
From: Claus Ibsen claus.ib...@gmail.com
Date:09/11/2014 09:42 (GMT+01:00)
To: users@camel.apache.org
Cc:
Subject: [HEADS UP] - camel-scr for
Great!
I'll sure have a look too!
regards
Grzegorz Grzybek
2014-11-09 11:02 GMT+01:00 Jean-Baptiste Onofré j...@nanthrax.net:
Hi Claude
Thanks for the update. I will take a look ASAP.
Regards
JB
Sent from my Samsung Galaxy smartphone.
Original message
From: Claus
