better way to get the JMS connection ID that would be
> great.
> I'm using Camel 2.0 with AMQ 5.2
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/Cahnging-endpoint-from-SEDA-to-direct-causes-ClassCastException-tp25487639p25487639.html
> Sent from
Message
I understand that SEDA causes things to be async but what can be the reason
for the type change ?
PS If there is a better way to get the JMS connection ID that would be
great.
I'm using Camel 2.0 with AMQ 5.2
Thanks.
--
View this message in context:
http://www.nabble.com/Cahnging-endpoi
