[
https://issues.apache.org/jira/browse/JENA-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265266#comment-16265266
]
Andy Seaborne commented on JENA-1435:
-------------------------------------
At least initially, this extensibility is only supported for the programmatic
Fuseki server and have a programmatic configuration API. (No classpath
problems.)
> Provide extensibility of Fuseki with new services.
> --------------------------------------------------
>
> Key: JENA-1435
> URL: https://issues.apache.org/jira/browse/JENA-1435
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Jena 3.5.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> This ticket is to provide a mechanism so that application code can add custom
> operations.
> The built-in set includes the operations usually in {{/dataset/sparql}},
> {{/dataset/update}} etc. as configured by {{fuseki:service*}}. These are also
> available as requests on the dataset directly as {{/dataset}}. For query,
> either parameter {{?query=}} or a content type {{application/sparql-query}}.
> Example extensions:
> * An RDF Patch processor
> * Upload and convert non-RDF formats
> * Extract custom output formats
> * Filtering requests before passing onto the general operation
> This extension point would support:
> * dispatch by operation name
> * dispatch by Content-Type
> Dispatch by HTTP parameters will be designed for but not enabled.
> See also JENA-1400 (extensible operation names).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
