GitHub user newkek opened a pull request:
https://github.com/apache/tinkerpop/pull/523
Add ResponseMessage deserializer for GraphSON2.
Motivation:
`ResponseMessage` used to be deserialized manually via a method on
GraphSONMessageSerializerV2d0 (deserializeResponse). Which prevented from using
the `Mapper` directly to deserialize a response.
Modification:
Deserialization of `ResponseMessage` is done in a deserializer registered
by the `GremlinServerModule` and the GraphSONMessageSerializerV2d0 has been
changed accordingly. Also added tests of ser/de for `RequestMessage` and
`ResponseMessage` from the `ObjectMapper`.
Result:
Calls like `objectMapper.readValue(jsonString, ResponseMessage.class)` work
now.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/newkek/incubator-tinkerpop
fix-graphson2-responsemessage
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/523.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #523
----
commit 5ba605bf67fe6c46cdb874b63703cf65aa25fa6a
Author: Kevin Gallardo <kevin.galla...@datastax.com>
Date: 2017-01-05T16:57:32Z
Add ResponseMessageDeserializer for GraphSON2.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
