2 Replies Latest reply on Feb 26, 2009 9:27 AM by Willem Jiang

    camel-osgi vs camel

    Charles Moulliard Newbie

      Hi,

       

      I see that in one of the example proposed in Fuse ESB 4.0.0.4 folder, the spring DSL has been defined using schema camel-osgi and not camel

       

      e.g.

       

             http://activemq.apache.org/camel/schema/osgi http://activemq.apache.org/camel/schema/osgi/camel-osgi.xsd

             http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd">

       

           

                  <to uri="nmr:HelloWorldImplPort"/>

                   

       

      What are the advantages of camel-osgi over camel ? Is it used to handle camel context lifecycle through OSGI server ?

       

      Regards,

       

      Charles Moulliard

      SOA Architect

      Xpectis

        • 1. Re: camel-osgi vs camel
          Torsten Mielke Apprentice

          Hi,

           

          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.

          • 2. Re: camel-osgi vs camel
            Willem Jiang Master

            Hi Charles,

             

            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

             

            Cheers

             

            Willem