[jira] [Created] (JENA-1609) Jena master does not build under JDK10

2018-10-01 Thread Lewis John McGibbney (JIRA)
Lewis John McGibbney created JENA-1609:
--

 Summary: Jena master does not build under JDK10
 Key: JENA-1609
 URL: https://issues.apache.org/jira/browse/JENA-1609
 Project: Apache Jena
  Issue Type: Improvement
  Components: Build, Documentation
 Environment: Apache Maven 3.5.4 
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T11:33:14-07:00)
Maven home: /usr/local/Cellar/maven/3.5.4/libexec
Java version: 10.0.2, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
Reporter: Lewis John McGibbney
 Fix For: Jena 3.9.0


When I attempt build under Oracle JDK 10 there are several issues which cause 
the build to fail. The following PR addresses these issues and enables me to 
build and run Jena master under JDK 10.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (JENA-503) Implement redirect for Fuseki once triples have been uploaded

2013-08-28 Thread Lewis John McGibbney (JIRA)

 [ 
https://issues.apache.org/jira/browse/JENA-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JENA-503:
--

Attachment: JENA-503.patch

Patch for trunk.
Most likely some improvements to be mode however this is much more convenient 
than heading to the URL bar.

 Implement redirect for Fuseki once triples have been uploaded
 -

 Key: JENA-503
 URL: https://issues.apache.org/jira/browse/JENA-503
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Reporter: Lewis John McGibbney
Priority: Minor
 Fix For: Fuseki 0.2.8

 Attachments: JENA-503.patch


 When users use the sparql.tpl form [0], they are presented with an html page 
 which provides some simple output specifying success, with number of triples 
 (in the case where the file(s) upload was successful) or else an HTTP status 
 code with a brief error message (in the case where it was not successful). 
 Regardless of the case, it would be nice to set up a redirect (say after 5 or 
 10 seconds) to get them back to sparql.tpl with the previously selected 
 dataset.
 Additionally, it would be nice to allow backwards navigation to other forms 
 from this form as it would save folks having to hit http://localhost:3030 
 every time they wish to navigate Fuseki.
 I don't have a patch yet, this was something which just crept in to my head 
 right now.
 [0] http://svn.apache.org/repos/asf/jena/trunk/jena-fuseki/pages/sparql.tpl 

--
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-201) Deliver Fuseki as a WAR file.

2013-08-27 Thread Lewis John McGibbney (JIRA)

[ 
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13751611#comment-13751611
 ] 

Lewis John McGibbney commented on JENA-201:
---

bq. The pages are always available.
bq. The pages are fixed.

For my use case this is exactly what I require Andy :)


I am going to work towards obtaining the 400 and presenting the index page upon 
startup. I think getting a web app (war packaging) which can be dropped in to 
Tomcat or some other container is certainly a start to overhauling the Fuseki 
interface. I will work on this anyway.

Separate Fuseki logging is certainly useful. A mish mash of Fuseki and Catalina 
INFO to catalina.out is not going to be particularly helpful as have numerous 
other applications spewing forth logging on this test server as well. I'll try 
to work towards separate logging for Fuseki as well. I am not having much joy 
obtaining any of the static files via my browser yet, even though they are 
included in the generated war however I should be able to sort this one out.  


 Deliver Fuseki as a WAR file.
 -

 Key: JENA-201
 URL: https://issues.apache.org/jira/browse/JENA-201
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Reporter: Andy Seaborne
Priority: Minor
  Labels: gsoc2013, mentor
 Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar




--
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-201) Deliver Fuseki as a WAR file.

2013-08-26 Thread Lewis John McGibbney (JIRA)

[ 
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750636#comment-13750636
 ] 

Lewis John McGibbney commented on JENA-201:
---

Hi Andy, what work is required to get HTML pages supported here?
For my own web app I have forked Fuseki but ideally would like to make it 
available as a webapp from my Tomcat web server... currently this doesn't seem 
to be possible with the default Jetty implementation therefore I am keen to get 
HTML support as part of transitioning towards WAR packaging for Fuseki. 
I can put time in to this is guided. In the mean time I will try to hack the 
code on my part and monitor this thread as well. 

 Deliver Fuseki as a WAR file.
 -

 Key: JENA-201
 URL: https://issues.apache.org/jira/browse/JENA-201
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Reporter: Andy Seaborne
Priority: Minor
  Labels: gsoc2013, mentor
 Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar




--
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-201) Deliver Fuseki as a WAR file.

2013-08-26 Thread Lewis John McGibbney (JIRA)

[ 
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750660#comment-13750660
 ] 

Lewis John McGibbney commented on JENA-201:
---

Hi Rob, just the man. I will try this out after work and write here my results. 
I am also on users@ so I may see you there. Thanks for feedback. 

 Deliver Fuseki as a WAR file.
 -

 Key: JENA-201
 URL: https://issues.apache.org/jira/browse/JENA-201
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Reporter: Andy Seaborne
Priority: Minor
  Labels: gsoc2013, mentor
 Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar




--
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-201) Deliver Fuseki as a WAR file.

2013-08-26 Thread Lewis John McGibbney (JIRA)

[ 
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13750832#comment-13750832
 ] 

Lewis John McGibbney commented on JENA-201:
---

OK doke. Well after configuring Tomcat to use Log4j for fine grained logging I 
realized that config-fuseki.ttl needed to be under /usr/share/fuseki/ for the 
web app to run within Fuseki.
I am seeing traces (which I suspect are down to the config file). I post the 
logging below for the record.
I am working towards getting the pages working within Tomcat. I will post how I 
get on with this.
Thanks
Lewis

{code}
Aug 26, 2013 5:49:23 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive 
/home/law/Desktop/tomcat7/webapps/apache-jena-fuseki.war
17:49:24 INFO  Config   :: Init - Context path: 
'/apache-jena-fuseki'
17:49:24 INFO  Config   :: Service: 
file:///usr/share/fuseki/config-fuseki.ttl#service1
17:49:24 INFO  Config   ::   name = ds
17:49:24 INFO  Config   ::   query = /ds/query
17:49:24 INFO  Config   ::   query = /ds/sparql
17:49:24 INFO  Config   ::   update = /ds/update
17:49:24 INFO  Config   ::   upload = /ds/upload
17:49:24 INFO  Config   ::   graphStore(RW) = /ds/data
17:49:24 INFO  Config   ::   graphStore(R) = /ds/get
17:49:24 INFO  Config   :: Register: /ds : /ds
Aug 26, 2013 5:49:28 PM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: list: Listing contexts for virtual host 'localhost'
17:49:29 INFO  FusekiServlet:: Apache Jena Fuseki Server
17:49:29 INFO  FusekiServlet:: URI = 
'/apache-jena-fuseki/
17:49:29 INFO  FusekiServlet:: Context path= 
'/apache-jena-fuseki'
17:49:29 INFO  FusekiServlet:: Servlet path= '/'
17:49:29 INFO  FusekiServlet:: ServletContext path = 
'/apache-jena-fuseki'
17:49:29 INFO  Fuseki   :: [1] GET 
http://localhost:8080/apache-jena-fuseki/
17:49:29 INFO  Fuseki   :: [1] All: GET  :: '' :: none ? 
17:49:29 WARN  Server   :: Exception on counter inc
java.lang.NullPointerException
at 
org.apache.jena.fuseki.servlets.SPARQL_ServletBase.incCounter(SPARQL_ServletBase.java:203)
at 
org.apache.jena.fuseki.servlets.SPARQL_ServletBase.executeLifecycle(SPARQL_ServletBase.java:173)
at 
org.apache.jena.fuseki.servlets.SPARQL_UberServlet.executeAction(SPARQL_UberServlet.java:169)
at 
org.apache.jena.fuseki.servlets.SPARQL_ServletBase.execCommonWorker(SPARQL_ServletBase.java:153)
at 
org.apache.jena.fuseki.servlets.SPARQL_ServletBase.doCommon(SPARQL_ServletBase.java:73)
at 
org.apache.jena.fuseki.servlets.SPARQL_UberServlet.doGet(SPARQL_UberServlet.java:320)
at webapp.FusekiServlet.doGet(FusekiServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at 
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
at 
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
17:49:29 WARN  Server   :: Exception on counter inc
java.lang.NullPointerException
at 
org.apache.jena.fuseki.servlets.SPARQL_ServletBase.incCounter(SPARQL_ServletBase.java:203)
at 
org.apache.jena.fuseki.servlets.SPARQL_REST.doGet$(SPARQL_REST.java:208)
at 
org.apache.jena.fuseki.servlets.SPARQL_REST.dispatch(SPARQL_REST.java:185)

[jira] [Updated] (JENA-501) Make stylesheet options obvious in dropdown.

2013-08-04 Thread Lewis John McGibbney (JIRA)

 [ 
https://issues.apache.org/jira/browse/JENA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JENA-501:
--

Attachment: JENA-501.patch

Patch for trunk.

 Make stylesheet options obvious in dropdown.
 

 Key: JENA-501
 URL: https://issues.apache.org/jira/browse/JENA-501
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Reporter: Lewis John McGibbney
Priority: Trivial
 Fix For: Fuseki 0.2.8

 Attachments: JENA-501.patch


 Anyone unfamiliar with Fuseki .xsl sheets will not know which options are 
 available out of the box for styling results streams in the browser.
 This small patch addresses that an allows users to pick which one they woyld 
 rather... or as by default retains nothing for no stylesheet at all.

--
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] [Updated] (JENA-483) Improve Javadoc for Fuseki artifact.

2013-07-02 Thread Lewis John McGibbney (JIRA)

 [ 
https://issues.apache.org/jira/browse/JENA-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JENA-483:
--

Attachment: JENA-483.patch

This is a documentation patch as promised. Based on the feedback on the list, I 
am not sure if I need to use the Fuseki API to achieve what I actually want to 
achieve... none-the-less I will continue documenting what I can where I can.
There are some fields which I did not immediately understand/recognize 
therefore the patch needs some QC/QA.  

 Improve Javadoc for Fuseki artifact.
 

 Key: JENA-483
 URL: https://issues.apache.org/jira/browse/JENA-483
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Affects Versions: Fuseki 0.2.7
Reporter: Lewis John McGibbney
 Fix For: Fuseki 0.2.8

 Attachments: JENA-483.patch


 I am currently using the Fuseki 0.2.7 artifact via it's Java API.
 It is very unclear what should be going on and how I should be using the API.
 With help from you guys on list ;), I am going to make it a priority to 
 document as much of the module as I can. I will upload the patch here once I 
 have finished. 

--
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] [Created] (JENA-483) Improve Javadoc for Fuseki artifact.

2013-07-01 Thread Lewis John McGibbney (JIRA)
Lewis John McGibbney created JENA-483:
-

 Summary: Improve Javadoc for Fuseki artifact.
 Key: JENA-483
 URL: https://issues.apache.org/jira/browse/JENA-483
 Project: Apache Jena
  Issue Type: Improvement
  Components: Fuseki
Affects Versions: Fuseki 0.2.7
Reporter: Lewis John McGibbney
 Fix For: Fuseki 0.2.8


I am currently using the Fuseki 0.2.7 artifact via it's Java API.
It is very unclear what should be going on and how I should be using the API.
With help from you guys on list ;), I am going to make it a priority to 
document as much of the module as I can. I will upload the patch here once I 
have finished. 

--
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] [Updated] (JENA-484) Upgrade Lucene and Solr versions to 4.3.1

2013-07-01 Thread Lewis John McGibbney (JIRA)

 [ 
https://issues.apache.org/jira/browse/JENA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated JENA-484:
--

Attachment: JENA-484.patch

Patch for trunk.

 Upgrade Lucene and Solr versions to 4.3.1
 -

 Key: JENA-484
 URL: https://issues.apache.org/jira/browse/JENA-484
 Project: Apache Jena
  Issue Type: Improvement
  Components: LARQ
Reporter: Lewis John McGibbney
Priority: Trivial
 Fix For: LARQ 2.0.0

 Attachments: JENA-484.patch


 Today I tried to do mvn eclipse:eclipse and my build for some reason stalled 
 on download of lucene-core-4.2.1 deps.
 This trivial patch updates to 4.3.1 which is pulled fine. 

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