You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2013/03/17 18:45:14 UTC

[jira] [Commented] (JENA-398) Extract NodeFactory.

    [ https://issues.apache.org/jira/browse/JENA-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604685#comment-13604685 ] 

Andy Seaborne commented on JENA-398:
------------------------------------

com.hp.hpl.jena.sparql.util.NodeFactory renamed as NodeFactoryExtra for now.

                
> Extract NodeFactory.
> --------------------
>
>                 Key: JENA-398
>                 URL: https://issues.apache.org/jira/browse/JENA-398
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Jena
>            Reporter: Andy Seaborne
>
> One core feature of Jena is that Node and Triple are universal.  A node or triple (or quad) from one subsystem can be passed to another system.
> Currently graph-level Nodes are their own factory - there are a bunch of Node.create* statics.
> This is a proposal to have a NodeFactory. This will given us more design freedom should we wish to introduce interfaces although given that nodes are universal (and, for the most part, simple) the need to use interfaces is not so significant.
> I propose (using the wonders of Eclipse) extracting the statics to create NodeFactory, leaving deprecated placeholders.  The refactoring of the rest of the codebase will happen automatically.
> This should break nothing, not even external code using Node directly
> There is already is a "com.hp.hpl.jena.sparql.util.NodeFactory" - this needs sorting out as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira