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 2016/10/18 20:59:58 UTC

[jira] [Comment Edited] (JENA-1248) Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)

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

Andy Seaborne edited comment on JENA-1248 at 10/18/16 8:59 PM:
---------------------------------------------------------------

The only "at risk" structure is the ARQ global context.

Once a pointer to {{DataAccessPointRegistry}} is available, all Fuseki routing and processing is via objects found that way.

This only really matters for embedded Fuseki - the full server doesn't have the requirement for multiple instances but the {{ServletContext}} is a reasonable way to handle it anyway.


was (Author: andy.seaborne):
The only "at risk" structure is the ARQ global context.

Once a pointer to {{DataAccessPointRegistry}} is available, all Fuseki routing and processing is via objects found that way.

> Support multiple embedded Fuseki2 servers running in the same JVM (on different ports)
> --------------------------------------------------------------------------------------
>
>                 Key: JENA-1248
>                 URL: https://issues.apache.org/jira/browse/JENA-1248
>             Project: Apache Jena
>          Issue Type: Improvement
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 3.1.1
>
>
> This requires Fuseki2 to use the servlet context to store the server state, which is the DataAccessPointRegistry object.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)