...
Starting with Camel 2.5, Camel supports 3rd party UUID generator(s). This is useful, if e.g. your messaging provider does not support UUID's with a length of 36 characters (like Websphere MQ). Another useful scenario is to use a simple counter for testing purpose. With this it is easier to correlate the exchanges in the log/debugger.
Camel uses UUIDs in the exchange and message ids, and other unique ids it uses.
You only have to implement org.apache.camel.spi.UuidGenerator and tell Camel, that it should use your custom implementation:
Configuring from Java DSL
![]() Code Block |
getContext().setUuidGenerator(new MyCustomUuidGenerator());
|
...
Camel will configure this UUID generator by doing a lookup in the Spring bean registry to find the bean of the type org.apache.camel.spi.UuidGenerator.
![]() Code Block |
<bean id="activeMQUuidGenerator" class="org.apache.camel.impl.ActiveMQUuidGenerator" />
<camelContext id="camel" xmlns="http://camel.apache.org/schema/spring">
<route>
<from uri="direct:start" />
<to uri="mock:result" />
</route>
</camelContext>
|
...
