[
https://issues.apache.org/jira/browse/JENA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371476#comment-16371476
]
Andy Seaborne commented on JENA-1490:
-------------------------------------
{noformat}
MyExtension ext = conn.getExtension(MyExtension.class)
{noformat}
This is a nice idea for the future though at the moment I'm being less
ambitious and just wanting to get the ticket description done.
I don't think that blocks future work. What I am cautious about is whether it
is the right approach for 3rd parties and also to make sure the responsibility
for the extensions remains with the 3rd party. My impression of the
integrations is that they are not exposing special functions but assume the
user goes to their product interfaces.
> Working with Blank Nodes with Fuseki
> ------------------------------------
>
> Key: JENA-1490
> URL: https://issues.apache.org/jira/browse/JENA-1490
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 3.6.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Major
>
> Be able to work with blank nodes between client and Fuseki server.
> This ticket is mainly about pulling together existing mechanisms.
> This would be a new {{RDFConnectionFactory}} function to return a
> {{RDFConnection}} with the right settings for presevring blank node id.
> Having a new {{RDFConnectionFuseki}}, subclass of {{RDFConnectionRemote}}, to
> handle the right settings and not simply option for {{RDFConnectionRemote}},
> because it is than a place for future Fuseki-specific operations.
>
> When working with a Fuseki remote:
> * Use RDF Thrift (RDF and Result set forms) for efficiency
> * Preserve blank node ids.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
