JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-135  -  Provide a more flexible mechanism for custom serialization extension
Posted Apr 06, 2013 - updated May 01, 2013
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Customization
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.0
Issue description
Many serialization mechanisms that can be found (see a list here) do not rely on ObjectInputStream and ObjectInputStream, which makes them impossible to use as a custom serialization scheme in JPPF.

I propose to define an alternative, more generic interface for this customization, so that many (hopefully all) serialization frameworks for the JVM can be used.

#2
Comment posted by
lolo4j
May 01, 10:28
This is now implemented, including updated documentation and a new sample using Kryo for serialization.

Last changes committed to SVN: trunk revision 2722

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.