4 Replies Latest reply on May 26, 2009 2:15 AM by oisin

    Integration Designer 1.1 Camel namespace problem

    willy.goldgewicht

      The camel-debugger-tmpXXX.xml refers to a schemaLocation :

       

      http://activemq.apache.org/camel/schema/spring

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

       

      which cannot work because the targetNamespace in this file is now : http://camel.apache.org/schema/spring (change camel1/camel2)

       

      So I am not able to run my diagram.

      Thank's for a fix.

        • 1. Re: Integration Designer 1.1 Camel namespace problem
          oisin

          The FID 1.1 download just works with the older 1.5 version of Camel I'm afraid - we're releasing an update (version 1.2) later this month that is designed to work with Camel 1.5 and 1.6.

           

          Camel 2 is on the radar, but not ready just yet!

           

          --oh

          • 2. Re: Integration Designer 1.1 Camel namespace problem
            willy.goldgewicht

            yes but why FID refers to the camel-spring.xsd on the web and not on a local one?

            In the com.iona.fuse.spring.ide.custom.namespaces.camel_1.1.0.200901271115.jar the olders camel-spring 1.3 & 1.4 are but not used.

             

            Does that mean that FID 1.1 does not work at all yet?

            • 3. Re: Integration Designer 1.1 Camel namespace problem
              oisin

               

              yes but why FID refers to the camel-spring.xsd on the web and not on a local one?

               

               

              Schema locations are usually fed through a local-defined resolver which maps the location to a place where the schema can be found. The means that even if the location is stated as remote, it can still be picked up from the local disk by the action of the resolver.

               

               

              Does that mean that FID 1.1 does not work at all yet?

               

               

              No, the FID 1.1 does work in general EIP cases - it doesn't support all of the Camel's extra goodies.

               

              The good news is we are rolling out an FID 1.2 very soon, which should cover vastly more Camel usecases, including those not limited to EIP-pure solutions.

              • 4. Re: Integration Designer 1.1 Camel namespace problem
                oisin

                Just an update on this - the 'activemq' namespace is used for pre-2.0 versions of Apache Camel - there is a FAQ Entry about this.