public interface IoRegistry
Graph. Providers should develop an implementation of this interface if their implementation requires custom serialization of identifiers or other such content housed in their graph. Consider extending from
AbstractIoRegistryand ensure that the implementation has a zero-arg constructor or a static "instance" method that returns an
IoRegistryinstance, as implementations may need to be constructed from reflection given different parts of the TinkerPop stack. The serializers to register depend on the
Ioimplementations that are expected to be supported. There are currently two core implementations in
GraphSONIo. Both of these should be supported for full compliance with the test suite. There is no need to use this class if the
Graphdoes not have custom classes that require serialization.
Copyright © 2013–2017 Apache Software Foundation. All rights reserved.