[
https://issues.apache.org/jira/browse/TINKERPOP3-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634860#comment-14634860
]
stephen mallette commented on TINKERPOP3-778:
---------------------------------------------
Do you see this as an additional way one could support {{GraphFactory}}? In
other words, we would keep the existing method and have this in addition to
that?
> Support GraphFactory location via annotation.
> ---------------------------------------------
>
> Key: TINKERPOP3-778
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-778
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: structure
> Affects Versions: 3.0.0-incubating
> Reporter: Bryn Cooke
> Assignee: stephen mallette
> Priority: Minor
>
> When using GraphFactory vendors have to use a concrete class with a static
> 'open' method on it.
> However, I would expect many vendors will want to expose an interface.
> {code:java}
> Map config = new HashMap<>();
> config.put(Graph.GRAPH, MyGraph.class.getName()); //MyGraph is an interface
> MyGraph graph = GraphFactory.open(config);
> {code}
> I realise that class name of the factory needn't match the class that is
> returned to the user, but it would be nice if it did.
> Adding an annotation to specify the factory class would fix this.
> {code:java}
> @GraphFactory(MyGraphFactory.class) //Graph factory uses this to locate the
> graph factory class
> interface MyGraph extends Graph{
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
