Hi, I stepped a little bit through the code and suppose, that the spring remoting I used is not suitable for JMS transport. Calling the say method on SayProxy leads to creating an BeanExchange with a BeanInvocation. At some point later, this BeanInvocation is passed to JmsBinding.createJmsMessage(...), which tries to translate this into a JMS message. Since the BeanInvocation is not serializable, an emtpy message is created and transfered to the remote side, which in turn leads to the IllegalStateException
Carsten -- View this message in context: http://www.nabble.com/spring-remoting-over-jms-tp14640388s22882p14666207.html Sent from the Camel - Users mailing list archive at Nabble.com.
