[ 
https://issues.apache.org/jira/browse/GEODE-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16930748#comment-16930748
 ] 

ASF subversion and git services commented on GEODE-7175:
--------------------------------------------------------

Commit 0ed63431d2a56a10a085f503793b7ff767fa961c in geode's branch 
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0ed6343 ]

GEODE-7175: fixing goofy serialization code in DistTxEntryEvent

committing missing SHA that renames RemoteEntryData.toData, which
claimed to be a DataSerializableFixedID method but was not.


> Convert toData/fromData in other modules to use new serializers
> ---------------------------------------------------------------
>
>                 Key: GEODE-7175
>                 URL: https://issues.apache.org/jira/browse/GEODE-7175
>             Project: Geode
>          Issue Type: Sub-task
>          Components: membership, serialization
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Major
>             Fix For: 1.11.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The serialization context API provides ObjectSerializer and 
> ObjectDeserializer instances in toData/fromData methods for 
> DataSerializableFixedID classes.  Most implementations of 
> DataSerializableFixedID in geode-core and other subprojects are still using 
> the old DataSerializer.writeObject/readObject API to read and write objects.  
> That should be changed to use the serialization context API.
> DataSerializer.readObject() -> context.getDeserializer().readObject()
> DataSerializer.writeObject() -> context.getSerializer.writeObject()



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to