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

Posted to dev@jena.apache.org by afs <gi...@git.apache.org> on 2016/10/18 21:09:42 UTC

[GitHub] jena pull request #180: JENA-1248: Fuseki registry update

GitHub user afs opened a pull request:

    https://github.com/apache/jena/pull/180

    JENA-1248: Fuseki registry update

    Also includes the test server control code ported from jena-fuseki-core.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/afs/jena fuseki-registry

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jena/pull/180.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #180
    
----
commit 661b5de173517b8eb9e395ee1d71556c30eca994
Author: Andy Seaborne <an...@apache.org>
Date:   2016-10-18T20:56:42Z

    JENA-1248: Put the registry in the servlet context.

commit 0185b890b32920908f5998e07f97c03f806d708b
Author: Andy Seaborne <an...@apache.org>
Date:   2016-10-18T21:00:08Z

    JENA-1248: Tests for multiple embedded Fuseki servers.

commit be7c1793d85b1e49bd16be92cdc2d9dffb5df448
Author: Andy Seaborne <an...@apache.org>
Date:   2016-10-18T21:01:49Z

    Getter for the server's DataAccessPointRegistry. 
    
    start() to return "this".

commit c03d7d590de6686f3da9e22773e64dbb0bda5dc4
Author: Andy Seaborne <an...@apache.org>
Date:   2016-10-18T21:02:08Z

    ServerCtl ported from Fuseki2.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena pull request #180: JENA-1248: Fuseki registry update

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

    https://github.com/apache/jena/pull/180


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #180: JENA-1248: Fuseki registry update

Posted by afs <gi...@git.apache.org>.

Github user afs commented on the issue:

    https://github.com/apache/jena/pull/180
  
    (rebased to Apache master branch)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #180: JENA-1248: Fuseki registry update

Posted by rvesse <gi...@git.apache.org>.

Github user rvesse commented on the issue:

    https://github.com/apache/jena/pull/180
  
    Looks good to me
    
    My only concern is how Shiro behaves in a environment where each invaded server may have a different security configuration.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] jena issue #180: JENA-1248: Fuseki registry update

Posted by afs <gi...@git.apache.org>.

Github user afs commented on the issue:

    https://github.com/apache/jena/pull/180
  
    Embedded Fuseki does not use Shiro.
    
    Fuseki (full) uses Shiro setup via the servlet context (not that Fuseki)full is aimed at multiple servers per JVM: better either 2 ports, one server, one JVM or multiple servers, multiple JVMs.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---