[
https://issues.apache.org/jira/browse/JENA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798958#comment-16798958
]
A. Soroka edited comment on JENA-1687 at 3/22/19 12:18 PM:
-----------------------------------------------------------
[~jmkeil], I'm trying to understand why you are using the SPI (which is
normally meant for implementation by new backends or the like) instead of the
API. That is to say, why are you manipulating \{{Graph}} s and not \{{Model}}
s, \{{Node}} s and not \{{Resource}} s, etc.?
was (Author: ajs6f):
[~jmkeil], I'm trying to understand why you are using the SPI (which is
normally meant for implementation by new backends or the like) instead of the
API. That is to say, why are you manipulating {{Graph}}s and not {{Model}}s,
{{Node}}s and not {{Resource}}s, etc.?
> Precise return types of NodeFactory methods
> -------------------------------------------
>
> Key: JENA-1687
> URL: https://issues.apache.org/jira/browse/JENA-1687
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Jan Martin Keil
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I propose to precise the return types of the NodeFactory methods, e.g. to set
> NodeFactory#createURI return type to Node_URI. This makes the developers life
> easier, as there is no longer a need to cast after creating a Node, if one
> need a specific node type. I can not see any disadvantages and it should be
> backward compatible (except of classes that override these methods).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
