On 07/01/2008, Carsten Krebs <[EMAIL PROTECTED]> wrote: > > 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
FWIW currently BeanInvocation implements Externalizable so it should work fine when used as the body of a JMS message. Though this is based on trunk; so you might want to try that (or 1.3.0 when its released) -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
