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

ASF subversion and git services commented on MARMOTTA-325:
----------------------------------------------------------

Commit 9b9f68565f7228db1ef975c9e4b90ef4b622085d in branch refs/heads/develop 
from [~p_ansell]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-marmotta.git;h=9b9f685 ]

MARMOTTA-325 : Deprecate APIs that make it difficult to extend formats

After deprecating both SPARQLGraphResultWriter, and the API methods that
rely on every type of query being applicable to a QueryResultWriter, the
code is substantially simpler, including removal of private methods in
SparqlWebService that are no longer required.

QueryResultWriter is only relevant to Tuple and Boolean results, so
hacking it to work with Graph results instead of using RDFHandler makes
it difficult to integrate with other API methods. Referencing RDFHandler
isn't even necessary in SparqlService if you only want to output to a
document, as
QueryResultIO.write(GraphQueryResult,RDFFormat,OutputStream) does the
resolution and handling automatically, as long as you can deal with
RDFHandlerException.
                
> Support arbitrary Tuple and Boolean results formats
> ---------------------------------------------------
>
>                 Key: MARMOTTA-325
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-325
>             Project: Marmotta
>          Issue Type: Improvement
>          Components: Platform
>            Reporter: Peter Ansell
>            Assignee: Peter Ansell
>             Fix For: 3.2
>
>
> The SPARQL Service currently hardcodes its supported Tuple and Boolean 
> results formats, partially in order to support special requirements of the 
> SPARQLResultsHTMLWriter.
> In order to allow arbitrary formats to be used, plugged in at runtime using 
> the Sesame service registries, the TemplatingService dependency in the 
> constructor can be bypassed and replaced with a setting that is checked at 
> runtime, to enable the standard WriterConfig method to be used.

--
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

Reply via email to