SerialVersionUID on class MessageHistory Breaking change : from version 5.5.2 to latest

[german22]

In what version(s) of Spring Integration are you seeing this issue?

After the version 5.5.2 until now

bug

The Class MessageHistory is a serializable class that doesn't have a SerialVersionUID defined, because of that it was taken the default SerialVersionUID created with the previous version.

Now this class was updated in the commit :
af9e69c

Where the equals/hashCode was implemented
Because of that, after the version 5.5.2 the serialVersionUID changed

This change of serialVersionUID makes the previos version incompatible with the new one, because the serialVersionUID matching fails when it tries to deserialize the class.

To Reproduce

Use spring integration with the version 5.5.1 to store a new record, and then update the version to the 5.5.2 or latest to read this record, and it will fails

Expected behavior

Deserialize the class MessageHistory stored in previous versions to the 5.5.2

Is it possible to fix this problem ?
Is there any workaround that we can implement in the meantime ?

Thanks a lot

[artembilan]

We can and an explicit serialVersionUID as a fix, but I guess it won't help you.

As a workaround I only see a way to copy/paste a 5.5.1 MessageHistory class to your project or separate jar and make it to be loaded before spring-integration-core.

WDYT?

[onobc]

I think we can set the explicit serialVersionUID to the value it had in 5.5.1. We can use the serialver tool to tell us what that value is.

Thoughts?

[artembilan]

Thanks, @onobc !

I think this is brilliant.

Here is a result of that command for me:

C:\Java\jdk-8\bin>serialver.exe -classpath c:\spring-integration-core-5.5.1.jar;c:\spring-messaging-5.3.8.jar;c:\spring-jcl-5.3.8.jar org.springframework.integration.history.MessageHistory
org.springframework.integration.history.MessageHistory:    private static final long serialVersionUID = 1426799817181873282L;

@german22 ,

would you mind to confirm from your side?
if that is the same, then we indeed can use that value for the current 5.5.10 version we are going to release on March 22th.