Tinder

JID serialization fails by default.

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1 - Concurrency
  • Component/s: None
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

The JID class implements the Externalizable inteface. This indicates that JID instances should be serializable. Out of the box, they are not.

Serialization is done through the ExternalizableUtil class. The strategy used can be modified (this allowed Jive to ship a non-Open Source serialization strategy to customers who bought their clustering support, based on Oracle Coherence).

By default, the strategy used is DummyExternalizableUtil. This implementation does not serialize any data. Instead, empty or null values are used. Because of this, JID instances do not serialize, even though the class indicates otherwise.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Guus der Kinderen added a comment -

A unit test has been added to SVN that exposes the bug.

Show
Guus der Kinderen added a comment - A unit test has been added to SVN that exposes the bug.
Hide
Permalink
Guus der Kinderen added a comment -

Removing the pluggable externalization implementation prevents the problem from occuring. Alternatively, the dummy strategy could be replaced by one that performs default serialization.

Show
Guus der Kinderen added a comment - Removing the pluggable externalization implementation prevents the problem from occuring. Alternatively, the dummy strategy could be replaced by one that performs default serialization.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.