2 Replies Latest reply on May 5, 2008 7:36 AM by Roger Joelsson

    JBI destination name of Camel BC?

    Roger Joelsson Novice

      Hi,

       

      I'm having an inbound file BC (servicemix-file), from which I want a static route to an Apache Camel router (servicemix-camel) for further routing to other outbound BC's. Questions:

       

      1. Is the idea correct in terms of JBI "best-practice"?

       

      2. What is the destination name of my Camel router BC? I've tried to refer to it as "jbi:", but I cannot find out how to refer to it. How do I name it (I suppose in jbi.xml) and how do I name the Camel's endpoint?

       

      Please could anyone help me out?

       

      Regards,

      Roger Joelsson

        • 1. Re: JBI destination name of Camel BC?
          Bruce Snyder Novice

           

          1. Is the idea correct in terms of JBI "best-practice"?

           

           

          If you're asking whether routing from the servicemix-file component to the servicemix-camel component is a good idea, then yes, it's a great idea! Camel is an extremely powerful mediation and routing framework that has become especially popular.

           

           

          2. What is the destination name of my Camel router BC? I've tried to refer to it as "jbi:<ns>:<service>:<endpoint>", but I cannot find out how to refer to it. How do I name it (I suppose in jbi.xml) and how do I name the Camel's endpoint?

           

           

           

          When creating a service using the servicemix-camel component, the service's name is defined using the Camel URI format. This URI format is defined in the from() method of your RouteBuilder (or from element if you're using XML configuration). To see an example of this, I encourage you to walk through a tutorial about using Camel with ServiceMix named Using Apache Camel inside ServiceMix.

           

          Bruce

          • 2. Re: JBI destination name of Camel BC?
            Roger Joelsson Novice

            Bruce,

             

            Thanks for your help, that helped me out! I also noticed that specifying a "jbi:endpoint" URI rather than "jbi:service" automatically publishes the specified endpoint (and thus relieving me of a routing Warning message).

             

            Regards,

            Roger