You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Claude Warren (JIRA)" <ji...@apache.org> on 2012/11/19 16:33:00 UTC

[jira] [Created] (JENA-350) Remove session requirement for out of the box Fuseki

Claude Warren created JENA-350:
----------------------------------

             Summary: Remove session requirement for out of the box Fuseki
                 Key: JENA-350
                 URL: https://issues.apache.org/jira/browse/JENA-350
             Project: Apache Jena
          Issue Type: Improvement
          Components: Fuseki
    Affects Versions: Fuseki 0.2.4
            Reporter: Claude Warren
            Priority: Minor


Fuseki requires a session to track the dataset the user has chosen.  The dataset id is also part of a URL for the SPARQL endpoints.  This proposal is to remove the session requirement for the out of the box fuseki.

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

[jira] [Commented] (JENA-350) Remove session requirement for out of the box Fuseki

Posted by "Andy Seaborne (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JENA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501896#comment-13501896 ] 

Andy Seaborne commented on JENA-350:
------------------------------------

It's a bit easier if the pages and the dataset URLs are in different parts of the name tree so that the services names are not stamped on by a page (unlikely = most uses I have seen use the default names for services).  At the moment *.tpl differentiates.

(Aside: maybe all the pages should be under /_/... to avoid clashes)


A direct way to do this would be to use query strings to name the dataset:

/sparql-form?dataset=/ds

where /sparql-form is a small servlet that check parameters and calls the velocity template.  At the moment the template calls into Fuseki to get the dataset name (hence the use of the session).

The control panel page can be a bunch of links to each dataset with the right ?querytstring, not a drop down.

This use of Velocity as an internal page generator, not via the *.tpl URLs, has worked well in another project.  MVC-style.  Writing the front end servlet is trivial as they are short - do some sanity checking, choose which template to call (error template, operation template).

Velocity has a helper tool 'ParameterParser' that could be used - the velocity set up is more complicated and would not have Fuseki-specific checking.  Seems like both are possible.

                
> Remove session requirement for out of the box Fuseki
> ----------------------------------------------------
>
>                 Key: JENA-350
>                 URL: https://issues.apache.org/jira/browse/JENA-350
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Fuseki 0.2.4
>            Reporter: Claude Warren
>            Priority: Minor
>
> Fuseki requires a session to track the dataset the user has chosen.  The dataset id is also part of a URL for the SPARQL endpoints.  This proposal is to remove the session requirement for the out of the box fuseki.

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

[jira] [Commented] (JENA-350) Remove session requirement for out of the box Fuseki

Posted by "Stephen Allen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JENA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500467#comment-13500467 ] 

Stephen Allen commented on JENA-350:
------------------------------------

I assume you are referring to the management web interface.  If so, I agree, there isn't really a need for the session.
                
> Remove session requirement for out of the box Fuseki
> ----------------------------------------------------
>
>                 Key: JENA-350
>                 URL: https://issues.apache.org/jira/browse/JENA-350
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Fuseki 0.2.4
>            Reporter: Claude Warren
>            Priority: Minor
>
> Fuseki requires a session to track the dataset the user has chosen.  The dataset id is also part of a URL for the SPARQL endpoints.  This proposal is to remove the session requirement for the out of the box fuseki.

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

[jira] [Commented] (JENA-350) Remove session requirement for out of the box Fuseki

Posted by "Paolo Castagna (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JENA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500501#comment-13500501 ] 

Paolo Castagna commented on JENA-350:
-------------------------------------

I had similar thoughts while ago, maybe it's possible (and easy) to use part of the URL to identify a dataset.
                
> Remove session requirement for out of the box Fuseki
> ----------------------------------------------------
>
>                 Key: JENA-350
>                 URL: https://issues.apache.org/jira/browse/JENA-350
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Fuseki 0.2.4
>            Reporter: Claude Warren
>            Priority: Minor
>
> Fuseki requires a session to track the dataset the user has chosen.  The dataset id is also part of a URL for the SPARQL endpoints.  This proposal is to remove the session requirement for the out of the box fuseki.

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