Actually, I have yet to run into a cross version JVM serialization issue with my product which serializes Java object and sends them over the Internet. Now, I have run into the problem where the Java classes did not have the same SerialVerionID due to changes in the API. And as sunch I have hard coded the SerialVersionID to a set value and made sure that my Java classes are always backward compatible.
Paul Franz ----- Original Message ----- From: "H Shankaranarayanan" <[EMAIL PROTECTED]> To: "JDJList" <[EMAIL PROTECTED]> Sent: Thursday, November 07, 2002 7:20 AM Subject: [jdjlist] RE: JMS ObjectMessage > When using Object messages you might want to ensure that the JDK/JRE used at > both the sending and receiving ends are the same . This could be an issue > especially after the SerialVersionID concept was introduced in Java. > Worth a try in any case. Also do let us know if this was the issue :) > > Also i dont think u need to XMLise an object and use TextMessages, > ObjectMessages are plain vanilla messages that just wrap around any serializable > payloads. > > I cant shed any light on JRun , never used it before. > > --Shankar > > -----Original Message----- > From: Scot Mcphee [mailto:scot.mcphee@;tigerex.net] > Sent: Thursday, November 07, 2002 2:25 PM > To: JDJList > Cc: JDJList > Subject: [jdjlist] JMS ObjectMessage > > > > Is it normal for a JMS implementation to be really picky about what sort of > Object will be serialisable in an ObjectMessage? > > 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 JRun manual only has this to say about the Object Message (all examples > are with TextMessages); > > ObjectMessage > Contains a serializable Java object. > Use one of the JDK Collection classes. > > It's not explained what the cryptic reference to the Collections API means > but wrapping it in an ArrayList doesn't make any difference. Googling it > didn't seem to turn up anything useful. > > I would like to avoid having to XML-ise the object. I will refrain likewise > from manually churning the object into a ByteStream because the BytesMessage > comments look even worse than the ObjectMessage. If anyone has any insights > into the ObjectMessage either generally or specifically to this > implementation which might help me make it work I would appreciate it. > > Otherwise, what's the best JavaObject to XML and back package to use? What's > the name of the Sun one? > > regs > scot. > > ___________________________________________ > Scot Mcphee - Snr Developer > - (mobile) +61-412-957414 > ___________________________________________ > Tigerex - http://www.tigerex.net > - (bus) +61-2-82593613 > ___________________________________________ > > > > ____________________________________________________ > To change your JDJList options, please visit: > http://www.sys-con.com/java/list.cfm > > Be respectful! Clean up your posts before replying > ____________________________________________________ > > > ____________________________________________________ > To change your JDJList options, please visit: > http://www.sys-con.com/java/list.cfm > > Be respectful! Clean up your posts before replying > ____________________________________________________ ____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________
