Bluelock/camel-spring-amqp — pull request #3 by poshhamster (2012-01-17 17:11:47+00:00)
Title: Fixed URI parsing to handle default exchange

I have been learning Camel using Camel in Action and attempted to integrate the books JMS examples into RabbitMQ using your component.

I have preferred using the default exchange when getting the example running and ran into problems, e.g. spring-amqp::queue1:routingKey1 for consumer and spring-amqp::routingKey1 for producer

The parsing using StringTokenizer dropped the default exchange token and instead I was getting exchanges created using the queue name.

I have added 2 unit tests to demonstrate the problem and updated the code to use String.split to resolve the issue.

Please note, there are continuing problems with the component as RabbitMQ doesn't like attempts to declare the default exchange nor a binding on it. I have resolved the problem locally by commenting out the declarations, but am considering raising an issue on spring-amqp project to handle the default exchange internally and not declare it or any bindings on it, i.e. perform a noop.

This is my first time using github so please shout if this isn't expected or I have got something wrong.