You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/05/11 20:55:03 UTC
[jira] [Created] (TINKERPOP3-677) Auto-register All IoRegistry
Instances to Mapper.Builder
stephen mallette created TINKERPOP3-677:
-------------------------------------------
Summary: Auto-register All IoRegistry Instances to Mapper.Builder
Key: TINKERPOP3-677
URL: https://issues.apache.org/jira/browse/TINKERPOP3-677
Project: TinkerPop 3
Issue Type: Improvement
Components: io
Reporter: stephen mallette
In most cases a user will have a Graph instance handy and/or access to the {{IoRegistry}}. In those cases, construction of a {{Mapper}} instance will be straightforward. In cases where that is not known at development time it might be nice to have something like:
{code}
GraphSONMapper.build().findRegistriesOnPath(true).create()
{code}
That way the {{Mapper}} can be told to lookup {{IoRegistry}} instances via {{ServiceLoader}} to save a user from having to do it manually. Seems like there would be some issues to consider in terms of properly ordering those registries.
See TINKERPOP3-656 for related thoughts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)