Currently the component discovery mechanism relies on a file inside
  META-INF/services/org/apache/camel/components/xxx
where xxx is the uri protocol used by the component.
This file is a properties file containing:
   class=xxx

This kind of discovery makes optimization kinda hard because there is
no simple way to know the components handled by a jar easily unless
going through all the entries in the jar.

Hence, I'd like to change the mechanism to have a single file named
   META-INF/services/org/apache/camel/components
which would contain several entries
   pojo=org.apache.camel.components.pojo.PojoComponent
   direct=org.apache.camel.components.direct.DirectComponent

This would be very usefull in OSGi instead of having to scan all the
bundles each time a component has to be created.
Thoughts ?

-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to