oh, but that's the nice part. It's not (of course it is, but I can't see it where yet) :-)
that's probably because I am running tomEE from inside eclipse, and its configuration is messing the class loading process and adding to this, I was serializing the messages before to JSON, so my code was using Enumeration<ActiveMQTextMessage> e = browser.getEnumeration(); instead of Enumeration<ActiveMQObjectMessage> e = browser.getEnumeration(); and guess what. It was working ;-) [comparing strings seems to be safer than comparing objects...] this is some sort of funny, I guess ;-) [] Leo [] Leo On Mon, Aug 19, 2013 at 11:56 AM, Romain Manni-Bucau <[email protected]>wrote: > different classloader > > don't put it in the webapp ;) > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* > > > > 2013/8/19 Leonardo K. Shikida <[email protected]> > > > my favorite activeMQ error message :-) > > > > java.lang.ClassCastException: > > org.apache.activemq.command.ActiveMQObjectMessage incompatible with > > org.apache.activemq.command.ActiveMQObjectMessage > > > > how could they be compatible? > > > > :-) > > > > [] > > > > Leo > > >
