[jira] [Created] (JENA-573) HTTPS homepage (change jQuery link to https)
Barry Coughlan created JENA-573: --- Summary: HTTPS homepage (change jQuery link to https) Key: JENA-573 URL: https://issues.apache.org/jira/browse/JENA-573 Project: Apache Jena Issue Type: Bug Components: Web site Environment: Firefox with HTTPS Everywhere Reporter: Barry Coughlan Priority: Trivial The Jena navigation dropdown and links are broken with HTTPS, e.g. see: https://jena.apache.org/help_and_support/bugs_and_suggestions.html Issue is that the link to code.jquery.com is HTTP when it should be HTTPS (as HTTPS pages will not load HTTP content). This may seem minor, but plugins like HTTPS Everywhere are likely popular among devs! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (JENA-572) ARQ should provide a convenient way to set the User-Agent for HTTP requests
[ https://issues.apache.org/jira/browse/JENA-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805475#comment-13805475 ] Hudson commented on JENA-572: - SUCCESS: Integrated in Jena_Development_Test #1016 (See [https://builds.apache.org/job/Jena_Development_Test/1016/]) Add support for configuring User-Agent header via HttpOp, set a sensible default value for general usage (JENA-572) (rvesse: rev 1535776) * /jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/web/HttpOp.java > ARQ should provide a convenient way to set the User-Agent for HTTP requests > --- > > Key: JENA-572 > URL: https://issues.apache.org/jira/browse/JENA-572 > Project: Apache Jena > Issue Type: Improvement > Components: ARQ >Affects Versions: Jena 2.11.0 >Reporter: Rob Vesse >Assignee: Rob Vesse > Fix For: Jena 2.11.1 > > > As discussed over at https://github.com/pyvandenbussche/sparqles/issues/9 as > of 2.11.0 ARQ provides centralised HTTP operations which allows for setting > global HTTP configuration. > One thing that it would be particularly useful to set is the User-Agent > header so that people using ARQ to write RDF/SPARQL robots can assign an > appropriate User-Agent to their requests. > Currently we do not change the header at all so sites will see the generic > Apache HttpClient User-Agent header. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (JENA-572) ARQ should provide a convenient way to set the User-Agent for HTTP requests
[ https://issues.apache.org/jira/browse/JENA-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Vesse resolved JENA-572. Resolution: Fixed Marking as Fixed, have added support for this functionality and existing HTTP usage tests in Fuseki continue to pass > ARQ should provide a convenient way to set the User-Agent for HTTP requests > --- > > Key: JENA-572 > URL: https://issues.apache.org/jira/browse/JENA-572 > Project: Apache Jena > Issue Type: Improvement > Components: ARQ >Affects Versions: Jena 2.11.0 >Reporter: Rob Vesse >Assignee: Rob Vesse > Fix For: Jena 2.11.1 > > > As discussed over at https://github.com/pyvandenbussche/sparqles/issues/9 as > of 2.11.0 ARQ provides centralised HTTP operations which allows for setting > global HTTP configuration. > One thing that it would be particularly useful to set is the User-Agent > header so that people using ARQ to write RDF/SPARQL robots can assign an > appropriate User-Agent to their requests. > Currently we do not change the header at all so sites will see the generic > Apache HttpClient User-Agent header. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (JENA-572) ARQ should provide a convenient way to set the User-Agent for HTTP requests
[ https://issues.apache.org/jira/browse/JENA-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805440#comment-13805440 ] ASF subversion and git services commented on JENA-572: -- Commit 1535776 from [~rvesse] in branch 'jena/trunk' [ https://svn.apache.org/r1535776 ] Add support for configuring User-Agent header via HttpOp, set a sensible default value for general usage (JENA-572) > ARQ should provide a convenient way to set the User-Agent for HTTP requests > --- > > Key: JENA-572 > URL: https://issues.apache.org/jira/browse/JENA-572 > Project: Apache Jena > Issue Type: Improvement > Components: ARQ >Affects Versions: Jena 2.11.0 >Reporter: Rob Vesse >Assignee: Rob Vesse > Fix For: Jena 2.11.1 > > > As discussed over at https://github.com/pyvandenbussche/sparqles/issues/9 as > of 2.11.0 ARQ provides centralised HTTP operations which allows for setting > global HTTP configuration. > One thing that it would be particularly useful to set is the User-Agent > header so that people using ARQ to write RDF/SPARQL robots can assign an > appropriate User-Agent to their requests. > Currently we do not change the header at all so sites will see the generic > Apache HttpClient User-Agent header. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (JENA-572) ARQ should provide a convenient way to set the User-Agent for HTTP requests
[ https://issues.apache.org/jira/browse/JENA-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805430#comment-13805430 ] Rob Vesse commented on JENA-572: I will commit a fix shortly, it adds a setUserAgent() method to HttpOp for configuring the desired User-Agent string. It applies the configured User-Agent header to all requests, by default if not otherwise configured the value "Apache-Jena-ARQ/VERSION" where VERSION is read from ARQ.VERSION will be used. Users can choose to disable sending a User-Agent header by calling HttpOp.setUserAgent(null); > ARQ should provide a convenient way to set the User-Agent for HTTP requests > --- > > Key: JENA-572 > URL: https://issues.apache.org/jira/browse/JENA-572 > Project: Apache Jena > Issue Type: Improvement > Components: ARQ >Affects Versions: Jena 2.11.0 >Reporter: Rob Vesse >Assignee: Rob Vesse > Fix For: Jena 2.11.1 > > > As discussed over at https://github.com/pyvandenbussche/sparqles/issues/9 as > of 2.11.0 ARQ provides centralised HTTP operations which allows for setting > global HTTP configuration. > One thing that it would be particularly useful to set is the User-Agent > header so that people using ARQ to write RDF/SPARQL robots can assign an > appropriate User-Agent to their requests. > Currently we do not change the header at all so sites will see the generic > Apache HttpClient User-Agent header. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (JENA-572) ARQ should provide a convenient way to set the User-Agent for HTTP requests
Rob Vesse created JENA-572: -- Summary: ARQ should provide a convenient way to set the User-Agent for HTTP requests Key: JENA-572 URL: https://issues.apache.org/jira/browse/JENA-572 Project: Apache Jena Issue Type: Improvement Components: ARQ Affects Versions: Jena 2.11.0 Reporter: Rob Vesse Assignee: Rob Vesse Fix For: Jena 2.11.1 As discussed over at https://github.com/pyvandenbussche/sparqles/issues/9 as of 2.11.0 ARQ provides centralised HTTP operations which allows for setting global HTTP configuration. One thing that it would be particularly useful to set is the User-Agent header so that people using ARQ to write RDF/SPARQL robots can assign an appropriate User-Agent to their requests. Currently we do not change the header at all so sites will see the generic Apache HttpClient User-Agent header. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (JENA-566) Strange behaviour of Jena in OSGi Blueprint
[
https://issues.apache.org/jira/browse/JENA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805395#comment-13805395
]
Andy Seaborne commented on JENA-566:
I'm not sure what you are asking - it looks like the OSGi setup is wrong (maybe
jena-core and jena-arq not bundled so as to use the same classloader?). This
does not look like a Jena issue - the project does not distribute an OSGi
bundle. Did you bunle it or get the bundle from elsewhere? Have you tried a
group who do use Jena as an OSGi bundle? (Apache Clerezza perhaps?)
(If someone were to help in providing the bundling, I'm sure the project would
be delighted to provide a bundle)
> Strange behaviour of Jena in OSGi Blueprint
> ---
>
> Key: JENA-566
> URL: https://issues.apache.org/jira/browse/JENA-566
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Environment: OSGi blueprint ARQ 2.11.1-SNAPSHOT
>Reporter: Izaskun
>Priority: Minor
> Labels: jena, osgi, riot, sdb
> Fix For: Jena 2.11.1
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Everytime I do a:
> *model.read(input, null);*
> I get:
> {quote}com.hp.hpl.jena.shared.ConfigException: Reader not found on classpath
> at
> com.hp.hpl.jena.rdf.model.impl.RDFReaderFImpl.getReader(RDFReaderFImpl.java:108)
> ClassNotFoundException:
> org.apache.jena.riot.adapters.JenaReadersWriters$RDFReaderRIOT_RDFXML{quote}
> I'm working in an OSGi blueprint environment. When I test this in a normal
> environment, everything works ok.
> My source code is:
> {quote}final String modelText = "\n"
> + " + "xmlns:res=\"http://www.w3.org/2005/sparql-results#\";
> xmlns:rdf=\"http://www.w3.org/1999/02/22-rdf-syntax-ns#\";> \n"
> + " rdf:about=\"http://www.w3.org/2005/sparql-results#ResultSet\";>\n"
> + "\n"
> + "\n"
> + "\n"
> + " \n" + "";
> final Model model = ModelFactory.createDefaultModel();
> model.read(new ByteArrayInputStream(modelText.getBytes()), null);
> model.close();{quote}
> I also add this in my pom, but it seems to do nothing:{quote}
>
>
>
> wrap_mvn_org.apache.jena_jena-arq_2.11.1-SNAPSHOT;resolution:=optional
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (JENA-566) Strange behaviour of Jena in OSGi Blueprint
[
https://issues.apache.org/jira/browse/JENA-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-566:
---
Priority: Minor (was: Major)
> Strange behaviour of Jena in OSGi Blueprint
> ---
>
> Key: JENA-566
> URL: https://issues.apache.org/jira/browse/JENA-566
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Environment: OSGi blueprint ARQ 2.11.1-SNAPSHOT
>Reporter: Izaskun
>Priority: Minor
> Labels: jena, osgi, riot, sdb
> Fix For: Jena 2.11.1
>
> Original Estimate: 5h
> Remaining Estimate: 5h
>
> Everytime I do a:
> *model.read(input, null);*
> I get:
> {quote}com.hp.hpl.jena.shared.ConfigException: Reader not found on classpath
> at
> com.hp.hpl.jena.rdf.model.impl.RDFReaderFImpl.getReader(RDFReaderFImpl.java:108)
> ClassNotFoundException:
> org.apache.jena.riot.adapters.JenaReadersWriters$RDFReaderRIOT_RDFXML{quote}
> I'm working in an OSGi blueprint environment. When I test this in a normal
> environment, everything works ok.
> My source code is:
> {quote}final String modelText = "\n"
> + " + "xmlns:res=\"http://www.w3.org/2005/sparql-results#\";
> xmlns:rdf=\"http://www.w3.org/1999/02/22-rdf-syntax-ns#\";> \n"
> + " rdf:about=\"http://www.w3.org/2005/sparql-results#ResultSet\";>\n"
> + "\n"
> + "\n"
> + "\n"
> + " \n" + "";
> final Model model = ModelFactory.createDefaultModel();
> model.read(new ByteArrayInputStream(modelText.getBytes()), null);
> model.close();{quote}
> I also add this in my pom, but it seems to do nothing:{quote}
>
>
>
> wrap_mvn_org.apache.jena_jena-arq_2.11.1-SNAPSHOT;resolution:=optional
> {quote}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (JENA-571) GraphTDB fails to implements .close() but fails to pass this up to GraphBase.
[ https://issues.apache.org/jira/browse/JENA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805320#comment-13805320 ] Hudson commented on JENA-571: - SUCCESS: Integrated in Jena_Development_Test #1015 (See [https://builds.apache.org/job/Jena_Development_Test/1015/]) JENA-571 (andy: rev 1535724) * /jena/trunk/jena-core/src/main/java/com/hp/hpl/jena/graph/Graph.java * /jena/trunk/jena-tdb/src/main/java/com/hp/hpl/jena/tdb/store/GraphTDB.java > GraphTDB fails to implements .close() but fails to pass this up to GraphBase. > - > > Key: JENA-571 > URL: https://issues.apache.org/jira/browse/JENA-571 > Project: Apache Jena > Issue Type: Bug > Components: TDB >Affects Versions: TDB 1.0.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 2.11.1 > > > from: > http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3CCALvhUEWRutgUOMqKpFaqK38Lr5ZKhUpAhoYVDEvMarEKaWtPKQ%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: Graph not closing
On 25/10/13 08:33, Reto Bachmann-Gmür wrote:
Hello,
I'm running into a problem closing a graph (I get from TDB).
According to:
http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/graph/Graph.html#isClosed%28%29
idClosed should return true as soon as close is called. Howver for me it
doesn't return true even after waiting a while:
jenaGraph.close();
for (int i = 0; !jenaGraph.isClosed() && (i < 100); i++) {
try {
Thread.sleep(10);
} catch (InterruptedException ex) {
Thread.currentThread().interrupt();
}
}
if (!jenaGraph.isClosed()) {
throw new RuntimeException("hmmm");
}
Any idea where the problem lies?
Cheers,
Reto
Bug in GraphTDB - it's failing to pass the "close()" call up the
inheritance chain. Just fixed it (JENA-571).
((
Closing a TDB graph is a bit of a no-op because a GraphTDB is a
stateless view of the dataset. The only way in which it affects the
dataset is that it may cause a sync() on the database.
))
Andy
[jira] [Closed] (JENA-571) GraphTDB fails to implements .close() but fails to pass this up to GraphBase.
[ https://issues.apache.org/jira/browse/JENA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne closed JENA-571. -- > GraphTDB fails to implements .close() but fails to pass this up to GraphBase. > - > > Key: JENA-571 > URL: https://issues.apache.org/jira/browse/JENA-571 > Project: Apache Jena > Issue Type: Bug > Components: TDB >Affects Versions: TDB 1.0.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 2.11.1 > > > from: > http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3CCALvhUEWRutgUOMqKpFaqK38Lr5ZKhUpAhoYVDEvMarEKaWtPKQ%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (JENA-571) GraphTDB fails to implements .close() but fails to pass this up to GraphBase.
[ https://issues.apache.org/jira/browse/JENA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated JENA-571: --- Summary: GraphTDB fails to implements .close() but fails to pass this up to GraphBase. (was: GraphTDB fails to implements .close() btu fails to pass this up to GraphBase.) > GraphTDB fails to implements .close() but fails to pass this up to GraphBase. > - > > Key: JENA-571 > URL: https://issues.apache.org/jira/browse/JENA-571 > Project: Apache Jena > Issue Type: Bug > Components: TDB >Affects Versions: TDB 1.0.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 2.11.1 > > > from: > http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3CCALvhUEWRutgUOMqKpFaqK38Lr5ZKhUpAhoYVDEvMarEKaWtPKQ%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (JENA-571) GraphTDB fails to implements .close() but fails to pass this up to GraphBase.
[ https://issues.apache.org/jira/browse/JENA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-571. Resolution: Fixed > GraphTDB fails to implements .close() but fails to pass this up to GraphBase. > - > > Key: JENA-571 > URL: https://issues.apache.org/jira/browse/JENA-571 > Project: Apache Jena > Issue Type: Bug > Components: TDB >Affects Versions: TDB 1.0.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 2.11.1 > > > from: > http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3CCALvhUEWRutgUOMqKpFaqK38Lr5ZKhUpAhoYVDEvMarEKaWtPKQ%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (JENA-571) GraphTDB fails to implements .close() btu fails to pass this up to GraphBase.
[ https://issues.apache.org/jira/browse/JENA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805284#comment-13805284 ] ASF subversion and git services commented on JENA-571: -- Commit 1535724 from [~andy.seaborne] in branch 'jena/trunk' [ https://svn.apache.org/r1535724 ] JENA-571 > GraphTDB fails to implements .close() btu fails to pass this up to GraphBase. > - > > Key: JENA-571 > URL: https://issues.apache.org/jira/browse/JENA-571 > Project: Apache Jena > Issue Type: Bug > Components: TDB >Affects Versions: TDB 1.0.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 2.11.1 > > > from: > http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3CCALvhUEWRutgUOMqKpFaqK38Lr5ZKhUpAhoYVDEvMarEKaWtPKQ%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (JENA-571) GraphTDB fails to implements .close() btu fails to pass this up to GraphBase.
Andy Seaborne created JENA-571: -- Summary: GraphTDB fails to implements .close() btu fails to pass this up to GraphBase. Key: JENA-571 URL: https://issues.apache.org/jira/browse/JENA-571 Project: Apache Jena Issue Type: Bug Components: TDB Affects Versions: TDB 1.0.0 Reporter: Andy Seaborne Assignee: Andy Seaborne Priority: Minor Fix For: Jena 2.11.1 from: http://mail-archives.apache.org/mod_mbox/jena-dev/201310.mbox/%3CCALvhUEWRutgUOMqKpFaqK38Lr5ZKhUpAhoYVDEvMarEKaWtPKQ%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.1#6144)
Graph not closing
Hello,
I'm running into a problem closing a graph (I get from TDB).
According to:
http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/graph/Graph.html#isClosed%28%29
idClosed should return true as soon as close is called. Howver for me it
doesn't return true even after waiting a while:
jenaGraph.close();
for (int i = 0; !jenaGraph.isClosed() && (i < 100); i++) {
try {
Thread.sleep(10);
} catch (InterruptedException ex) {
Thread.currentThread().interrupt();
}
}
if (!jenaGraph.isClosed()) {
throw new RuntimeException("hmmm");
}
Any idea where the problem lies?
Cheers,
Reto
