[
https://issues.apache.org/jira/browse/GEODE-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489818#comment-17489818
]
Mario Salazar de Torres commented on GEODE-10026:
-------------------------------------------------
Hi [~echobravo],
You've got a good point, and I don't like it either. But the problem is that
the current way that exceptions are handled inside the native client is not
acceptable at all.
Eitherway I'll let rest the exceptions part for now, and come back with some
alternatives in the future.
BR,
Mario.
> Implement java deserialization
> ------------------------------
>
> Key: GEODE-10026
> URL: https://issues.apache.org/jira/browse/GEODE-10026
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Mario Salazar de Torres
> Priority: Major
>
> Currently, the native client does not support deserializing Java serialized
> objects.
> I.E exceptions are sent as Java serialized and also a message is sent, so if
> the Java serialized object could be read instead of the exception message,
> this would solve several issues while parsing exceptions.
> Java (de)serialization is an
> [standard|https://docs.oracle.com/javase/8/docs/platform/serialization/spec/protocol.html]
> so and has not changed in a while, so adding this would require so little
> maintenance.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
