The update to the message context has broken serialisation with older versions ------------------------------------------------------------------------------ Key: JBESB-2445 URL: https://jira.jboss.org/jira/browse/JBESB-2445 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The message context was previously unused but was modified, by me I must admit, so that we could usefully distinguish between message context and message contents. Unfortunately this breaks when an old version of a serialized message is read by the new version. The fix is straight forward, add the following into the ContextImpl for the serialized format. /** * Deserialise the object, checking for old versions. * @param ois The object input stream. * @throws IOException For IO exceptions during object deserialisation. * @throws ClassNotFoundException If dependent classes cannot be found. */ private void readObject(final ObjectInputStream ois) throws IOException, ClassNotFoundException { ois.defaultReadObject() ; if (context == null) { context = new HashMap<String, Serializable>() ; } } The XML variant is correct. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira