I'm afraid I haven't used JRun - only Weblogic's JMS implementation, with which I've had no problems using custom objects in ObjectMessage.
> Is it normal for a JMS implementation to be really picky > about what sort of Object will be serialisable in an ObjectMessage? No, you should be able to use any object that implements java.io.Serializable. > I've got a real boring plain old data bean which I can easily > serialise and transmit via usual methods e.g. RMI. But when I > stick the same object into an ObjectMessage on > *deserialisation* the implementation (JRun 4) throws > javax.jms.MessageFormatException. > It does this as soon as I call; > Object o = objectmsg.getObject(); > > It doesn't complain on the way in. It works real dandy with > simple Java objects like java.util.Date. The only thing I can think of is that the class of object that you're storing in the message isn't on the classpath for the receiving/deserialisation end. I would have thought you'd be more likely to get a NoClassDefFoundError if this was the case, but it'll depend on the JMS implementation. Is the receiver in a different ear / war? Sorry I can't shed more light. Al. ____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________
