geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [geode-native] branch develop updated: Added caveats for use of DataSerializable
Date Wed, 22 Aug 2018 16:53:42 GMT
This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch develop
in repository

The following commit(s) were added to refs/heads/develop by this push:
     new 15208f3  Added caveats for use of DataSerializable
15208f3 is described below

commit 15208f3e094ad9304fdce3f05a3518a7f1444ab9
Author: Dave Barnes <>
AuthorDate: Wed Aug 22 09:53:36 2018 -0700

    Added caveats for use of DataSerializable
 .../serialization/cpp-serialization/ | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/geode-native-docs/serialization/cpp-serialization/
index 780210c..1e49872 100644
--- a/docs/geode-native-docs/serialization/cpp-serialization/
+++ b/docs/geode-native-docs/serialization/cpp-serialization/
@@ -79,3 +79,7 @@ but the user has registered the class with the `registerType` API.
 <span class="tablecap">**Table 1.** Serialization Options—Comparison of Features</span>
+## Important points to remember when using DataSerializable
+1. Make sure to register the proper typeId when registering custom classes that have a corresponding
server side jar (e.g. Portfolio and Position)
+2. Make sure to register any custom types in each process that uses those types. The cppcache
framework uses four separate processes.

View raw message