Hi Claus,
this actually works only with a single route.
<route>
<from uri="activemq:filequeue?mapJmsMessage=false">
<to uri="bean:filehandler">
</route>
public class FileHandler{
@Handler
public void onMessage(Exchange exchange){
exchange.getIn().getBody().getClass() == ActiveMQBlobMessage
}
but with this routing(tested on single broker and network of 2 brokers):
<route>
<from uri="activemq:filequeue?mapJmsMessage=false">
<to uri="activemq:filequeue2?mapJmsMessage=false">
</route>
<route>
<from uri="activemq:filequeue2?mapJmsMessage=false">
<to uri="bean:filehandler">
</route>
The exchange.getBody().getClass() returns ActiveMQMessage
i don't understand this behaviour. Why does the actual class get lost?
--
View this message in context:
http://old.nabble.com/Recieving-BlobMessages-routed-with-Camel-tp28367084p28476460.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
