[
https://issues.apache.org/jira/browse/TINKERPOP3-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523699#comment-14523699
]
stephen mallette commented on TINKERPOP3-640:
---------------------------------------------
Just changed the {{IoRegistry}} to an interface that vendors implement.
Vendors will registered the serializers to this registry such that {{Io}}
implementations like Gryo and GraphSON can consult it for the custom
serializers the {{Graph}} has. {{GryoPool}} and the other classes above that
directly instantiate {{Io}} instances (or {{GraphReader}} / {{GraphWriter}}
instances for that matter), need to use reflection to dynamically instantiate
an {{IoRegistry}} from configuration. In this way, it will become possible to
properly instantiate as follows:
{code}
IoRegistry vendorIoRegistry = loadFromReflection(config);
Mapper mapper = GryoMapper.build().addRegistry(vendorIoRegistry).create()
GryoReader/Writer.build().mapper(mapper).create()
{code}
> GryoPool Not Getting Vendor Serializer Registrations
> ----------------------------------------------------
>
> Key: TINKERPOP3-640
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-640
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: io
> Reporter: stephen mallette
> Assignee: Marko A. Rodriguez
> Fix For: 3.0.0.GA
>
>
> {{GryoPool}} is currently creating {{GraphReader}} and {{GraphWriter}}
> interfaces with the standard builder:
> {{GryoReader/Writer.build().create()}}. Since they are not being created
> with {{g.io()}} they are not getting custom serializers registered. Need to
> figure out how to get those serializers from the source {{Graph}} registered
> to the builders.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
