The new camel-osgi schema definition currently only defines its own camelContext:
<xs:element name="camelContext" type="tns:camelContextFactoryBean"/> <xs:complexType name="camelContextFactoryBean"> <xs:complexContent> <xs:extension base="camel:camelContextFactoryBean"> <xs:sequence></xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>
This is to allow registration of an OSGI version of CamelContextFactoryBean with the OSGI target name space.
Since there are lots of difference of class and resource finding between OSGI and normal class path. The resource utils of camel can't work rightly in the OSGI environment. You may get the component not found complain even you install the relates component feature if you are using the camel context directly.
So we add the camel-osgi model to resolve this kind of problem