-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added support for all serialization methods in Hazelcast #68
Added support for all serialization methods in Hazelcast #68
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had some minor comments
@@ -45,7 +45,7 @@ The latest tested versions are **6.0.39**, **7.0.40** and **8.0.36**. | |||
***Requirements*** | |||
|
|||
- Tomcat instance must be running with Java 1.6 or higher. | |||
- Session objects that need to be clustered have to be Serializable. | |||
- Session objects that need to be clustered have to be serializable on Hazelcast cluster. Please see <a href="https://docs.hazelcast.org/docs/latest/manual/html-single/#serialization" target="_blank">here</a> for how you can configure and implement serialization for Hazelcast. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a minor comment. Can the link provided here be broken over time? cc: @Serdaro
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it is mostly ok to use, since it redirects to the latest version.
objectDataOutput.writeObject(entryObject.getKey()); | ||
objectDataOutput.writeObject(entryObject.getValue()); | ||
} catch (Exception e) { | ||
LOG.warn("Unable to serialize object in session", e); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a warning or more severe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was also a warning when deserialising, I kept it the same for the serialisation exceptions. We can create an issue, if you think we should increase the severity level.
Fixes #38.