[jira] [Closed] (TINKERPOP3-677) Auto-register All IoRegistry Instances to Mapper.Builder

["stephen mallette (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP3-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP3-677.
---------------------------------------
    Resolution: Won't Fix
      Assignee: stephen mallette

This probably isn't going to work.  While we can now find registries pretty easily the issue of ordering is a problem.  How they order on one system isn't necessarily how they will order elsewhere so it won't help for remoting or similar usages.  Manual registration still seems like the best way to do this as users will know their data.

> 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
>    Affects Versions: 3.0.0-incubating
>            Reporter: stephen mallette
>            Assignee: 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)