For those who might be interested, I've posted a Camel component based on Spring AMQP for those who wish to use more AMQP semantics instead of a JMS->AMQP interface via Qpid. Source is now available at https://github.com/Bluelock/camel-spring-amqp
While the Qpid component is great for those who might be migrating from JMS to AMQP, a few on the list have suggested that they were interested in having more direct access to native RabbitMQ features, leveraging header exchanges, etc. This camel-spring-amqp component was created to expose RabbitMQ features natively within a Camel endpoint but still provide a path towards a vendor-independent implementation. After receiving feedback from the Camel team I decided to implement the component using Spring AMQP. Since Spring AMQP performs JSON marshalling with Jackson, I've also included an XStream marshaller with this component so that messages can be formatted using the XStream JSON libraries prior to being sent over the wire. You could of course do the same thing with the Camel dataFormat filters as well, but this offers another way to do object wire marshalling within the Spring AMQP framework. I'm open to any feedback, testing or pull requests for camel-spring-amqp. If you find the URI format to be a bit odd let me know - I'm open to new ideas on how to better format the endpoint string. Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/Spring-AMQP-Apache-Camel-Component-Released-tp5027785p5027785.html Sent from the Camel - Users mailing list archive at Nabble.com.
