Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the asciidoc in the repository:


If you are using the Camel JBI integration to send a MessageExchange to another JBI component from within your Camel route, Camel uses the MEP of the underlying Camel Exchange to determine the MEP of the JBI MessageExchange. An example:

from(""timer://foo").to("jbi:endpoint:urn:translator:endpoint").to("log:test");                    //THIS WON'T WORK...

If the timer endpoint that starts the route sends a Camel exchange with an in-only MEP, the MEP for interacting with JBI will also be InOnly. Now imagine that the target JBI endpoint is in fact a servicemix-saxon xslt endpoint, that really expects an InOut MEP. This would break the Camel route above.


For this se case, you can override the MEP used from the Camel route like this, making sure that a JBI InOut MessageExchange is being used to interact with the "urn:translation:endpoint" endpoint.

from(""timer://foo").to("jbi:endpoint:urn:translator:endpoint?mep=in-out").to("log:test");        //...BUT THIS WILL
© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram