Hi Reij, I agree with Claus, you should avoid Java's build-in serializer since it has a number of drawback, tight coupling being one of them.
I've you interested in high performance messaging I suggest you take a look at the JVM serialization benchmark at https://github.com/eishay/jvm-serializers/wiki. It compares different serialization and marshaling techniques. I think Kryo is the fasted one out there. If you want both speed and (language neutral) compatibility I suggest using JSON (http://camel.apache.org/json.html). As you can see in the benchmark Jackson is pretty fast. Regards, Richard On Thu, Jan 16, 2014 at 10:42 AM, contactreji <contactr...@gmail.com> wrote: > Hi Claus > > Thanks a lot! I had the exact copy of annotated class at both server and > client end. But sadly I didn't notice that package name was different. > Once was com.example.Student and other was com.queueshifter.Student > > After renaming the package with the same name as the other, it worked like > charm. > > I would also love to know what is the approach you take to avoid > performance > overhead while converting object->xml and xml->object back while using > them > in jms. > > What type of jmsMessageType should i use for high performance systems? > > Pls suggest > > Regards > Reji > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Moving-Objects-between-Active-MQ-queues-using-Camel-Routes-tp5746020p5746037.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
