Message Translator
Camel supports the Message Translator from the EIP patterns by using an artibrary Processor in the routing logic or by using a bean in the Bean Integration to perform the transformation. You can also use a Data Format to marshal and unmarshal messages in different encodings.
Using the Fluent Builders
or you can add your own Processor
Or you could use a named bean from your Registry such as your Spring XML configuration file as follows
from("activemq:SomeQueue"). beanRef("myTransformerBean"). to("mqseries:AnotherQueue");
Where the "myTransformerBean" would be defined in a Spring XML file or defined in JNDI etc.
For further examples of this pattern in use you could look at one of the JUnit tests
Using This Pattern
If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.