[jira] [Comment Edited] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
[
https://issues.apache.org/jira/browse/JENA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464199#comment-16464199
]
Andy Seaborne edited comment on JENA-1541 at 5/4/18 5:57 PM:
-
[~ajs6f] – Ask on dev@?
While the project has the code, no one has come forward to maintain it. "has
not been released" is still true.
"com.hp.hpl.jena" shows how old it is.
[~edward18], nowadays there are other ways to validate RDF such as W3C SHACL
and ShEX.
There is a Jena 3.7.0 compatible SHACL implementation is available in Maven
central as {{org.topbraid:shacl:1.1.0 }} and the documentation at
https://github.com/TopQuadrant/shacl/. It uses the Apache License, but is
separate project.
was (Author: andy.seaborne):
[~ajs6f] – Ask on dev@?
While the project has the code, no one has come forward to maintain it. "has
not been released" is still true.
"com.hp.hpl.jena" shows how old it is.
[~edward18], nowadays there are other ways to validate RDF such as W3C SHACL
and ShEX.
There is a Jena 3.7.0 compatible SHACL implementation is available in Maven
central as {{org.topbraid:shacl:1.1.0 }} and the documentation at
https://github.com/TopQuadrant/shacl/.
> Jena Eyeball - ant test fails with TestCase Error
> -
>
> Key: JENA-1541
> URL: https://issues.apache.org/jira/browse/JENA-1541
> Project: Apache Jena
> Issue Type: Question
> Components: Eyeball, Jena
>Reporter: Edward
>Priority: Major
> Labels: ant, eyeball, fail, jena, test
>
> Hello,
> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
> [https://jena.apache.org/documentation/tools/eyeball-getting-started.html]
> but it failed with following error:
> {code:java}
> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
> [junit] Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit] junit.framework.AssertionFailedError: Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit]
> [junit]
> BUILD FAILED
> /**/Downloads/eyeball-2.3/build.xml:146: Test
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
> {code}
> The tutorial says if the ant test doesn't pass, I should file a Jira Issue.
> So that's what I am doing.
> Help would be much appreciated!
>
> Greetings,
> Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
[
https://issues.apache.org/jira/browse/JENA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464199#comment-16464199
]
Andy Seaborne edited comment on JENA-1541 at 5/4/18 5:56 PM:
-
[~ajs6f] – Ask on dev@?
While the project has the code, no one has come forward to maintain it. "has
not been released" is still true.
"com.hp.hpl.jena" shows how old it is.
[~edward18], nowadays there are other ways to validate RDF such as W3C SHACL
and ShEX.
There is a Jena 3.7.0 compatible SHACL implementation is available in Maven
central as {{org.topbraid:shacl:1.1.0 }} and the documentation at
https://github.com/TopQuadrant/shacl/.
was (Author: andy.seaborne):
[~ajs6f] -- Ask on dev@?
https://jena.apache.org/documentation/tools/eyeball-getting-started.html points
tot he code in SVN and also says "has not been released under the Apache
Software License."
"com.hp.hpl.jena" shows how old it is.
[~edward18], nowadays there are other ways to validate RDF such as W3C SHACL
and ShEX.
There is a Jena 3.7.0 compatible SHACL implementation is available in Maven
central as described at https://github.com/TopQuadrant/shacl/.
> Jena Eyeball - ant test fails with TestCase Error
> -
>
> Key: JENA-1541
> URL: https://issues.apache.org/jira/browse/JENA-1541
> Project: Apache Jena
> Issue Type: Question
> Components: Eyeball, Jena
>Reporter: Edward
>Priority: Major
> Labels: ant, eyeball, fail, jena, test
>
> Hello,
> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
> [https://jena.apache.org/documentation/tools/eyeball-getting-started.html]
> but it failed with following error:
> {code:java}
> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
> [junit] Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit] junit.framework.AssertionFailedError: Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit]
> [junit]
> BUILD FAILED
> /**/Downloads/eyeball-2.3/build.xml:146: Test
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
> {code}
> The tutorial says if the ant test doesn't pass, I should file a Jira Issue.
> So that's what I am doing.
> Help would be much appreciated!
>
> Greetings,
> Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
[
https://issues.apache.org/jira/browse/JENA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464202#comment-16464202
]
A. Soroka commented on JENA-1541:
-
Right, I'll let [~edward18] do the asking. There is also a [ShEx implementation
with Jena bindings|https://github.com/iovka/shex-java] and [a project that
intends to support both ShEx and SHACL with Jena
bindings|https://github.com/labra/shaclex].
> Jena Eyeball - ant test fails with TestCase Error
> -
>
> Key: JENA-1541
> URL: https://issues.apache.org/jira/browse/JENA-1541
> Project: Apache Jena
> Issue Type: Question
> Components: Eyeball, Jena
>Reporter: Edward
>Priority: Major
> Labels: ant, eyeball, fail, jena, test
>
> Hello,
> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
> [https://jena.apache.org/documentation/tools/eyeball-getting-started.html]
> but it failed with following error:
> {code:java}
> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
> [junit] Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit] junit.framework.AssertionFailedError: Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit]
> [junit]
> BUILD FAILED
> /**/Downloads/eyeball-2.3/build.xml:146: Test
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
> {code}
> The tutorial says if the ant test doesn't pass, I should file a Jira Issue.
> So that's what I am doing.
> Help would be much appreciated!
>
> Greetings,
> Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
[
https://issues.apache.org/jira/browse/JENA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464199#comment-16464199
]
Andy Seaborne commented on JENA-1541:
-
[~ajs6f] -- Ask on dev@?
https://jena.apache.org/documentation/tools/eyeball-getting-started.html points
tot he code in SVN and also says "has not been released under the Apache
Software License."
"com.hp.hpl.jena" shows how old it is.
[~edward18], nowadays there are other ways to validate RDF such as W3C SHACL
and ShEX.
There is a Jena 3.7.0 compatible SHACL implementation is available in Maven
central as described at https://github.com/TopQuadrant/shacl/.
> Jena Eyeball - ant test fails with TestCase Error
> -
>
> Key: JENA-1541
> URL: https://issues.apache.org/jira/browse/JENA-1541
> Project: Apache Jena
> Issue Type: Question
> Components: Eyeball, Jena
>Reporter: Edward
>Priority: Major
> Labels: ant, eyeball, fail, jena, test
>
> Hello,
> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
> [https://jena.apache.org/documentation/tools/eyeball-getting-started.html]
> but it failed with following error:
> {code:java}
> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
> [junit] Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit] junit.framework.AssertionFailedError: Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit]
> [junit]
> BUILD FAILED
> /**/Downloads/eyeball-2.3/build.xml:146: Test
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
> {code}
> The tutorial says if the ant test doesn't pass, I should file a Jira Issue.
> So that's what I am doing.
> Help would be much appreciated!
>
> Greetings,
> Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1542) Allow addition of transaction components after initial setup.
[
https://issues.apache.org/jira/browse/JENA-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464191#comment-16464191
]
A. Soroka commented on JENA-1542:
-
Okay, cool, and definitely that sounds like a good constraint to start with.
> Allow addition of transaction components after initial setup.
> -
>
> Key: JENA-1542
> URL: https://issues.apache.org/jira/browse/JENA-1542
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB, TDB2
>Affects Versions: Jena 3.7.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Currently:
> * TDB1: the set of {{TransactionLifecycle}} components is fixed
> * TDB2: the set of {{TransactionComponents}} is frozen during creation of a
> dataset.
> In order to be able to add a text index into the transaction handling, allow
> new items to be added (carefully) into the transaction subsystem for a
> dataset.
> This is necessary for JENA-1302.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1542) Allow addition of transaction components after initial setup.
[
https://issues.apache.org/jira/browse/JENA-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464189#comment-16464189
]
Andy Seaborne commented on JENA-1542:
-
Not while the transaction is in progress! Its really for reconfiguring the
initial setup of the dataset and its TransactionManager (TDB1) or
TransactionCoordinator (TDB2) before general use.
Probably the safe way is to only allow change in "exclusive mode" (no
transactions active).
> Allow addition of transaction components after initial setup.
> -
>
> Key: JENA-1542
> URL: https://issues.apache.org/jira/browse/JENA-1542
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB, TDB2
>Affects Versions: Jena 3.7.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Currently:
> * TDB1: the set of {{TransactionLifecycle}} components is fixed
> * TDB2: the set of {{TransactionComponents}} is frozen during creation of a
> dataset.
> In order to be able to add a text index into the transaction handling, allow
> new items to be added (carefully) into the transaction subsystem for a
> dataset.
> This is necessary for JENA-1302.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1542) Allow addition of transaction components after initial setup.
[
https://issues.apache.org/jira/browse/JENA-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464150#comment-16464150
]
A. Soroka commented on JENA-1542:
-
Is the goal of this ticket to be able to add components to a transaction in
progress, or only to be able to add transaction components to a dataset after
the dataset has been created, but not necessarily while a transaction is in
progress?
> Allow addition of transaction components after initial setup.
> -
>
> Key: JENA-1542
> URL: https://issues.apache.org/jira/browse/JENA-1542
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB, TDB2
>Affects Versions: Jena 3.7.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Currently:
> * TDB1: the set of {{TransactionLifecycle}} components is fixed
> * TDB2: the set of {{TransactionComponents}} is frozen during creation of a
> dataset.
> In order to be able to add a text index into the transaction handling, allow
> new items to be added (carefully) into the transaction subsystem for a
> dataset.
> This is necessary for JENA-1302.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (JENA-1542) Allow addition of transaction components after initial setup.
[
https://issues.apache.org/jira/browse/JENA-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1542:
Description:
Currently:
* TDB1: the set of {{TransactionLifecycle}} components is fixed
* TDB2: the set of {{TransactionComponents}} is frozen during creation of a
dataset.
In order to be able to add a text index into the transaction handling, allow
new items to be added (carefully) into the transaction subsystem for a dataset.
This is necessary for JENA-1302.
was:
Currently:
* TDB1: the set of {{JenaLifecycle}} components is fixed
* TDB2: the set of {{TransactionComponents}} is frozen during creation of a
dataset.
In order to be able to add a text index into the transaction handling, allow
new items to be added (carefully) into the transaction subsystem for a dataset.
This is necessary for JENA-1302.
> Allow addition of transaction components after initial setup.
> -
>
> Key: JENA-1542
> URL: https://issues.apache.org/jira/browse/JENA-1542
> Project: Apache Jena
> Issue Type: Improvement
> Components: TDB, TDB2
>Affects Versions: Jena 3.7.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> Currently:
> * TDB1: the set of {{TransactionLifecycle}} components is fixed
> * TDB2: the set of {{TransactionComponents}} is frozen during creation of a
> dataset.
> In order to be able to add a text index into the transaction handling, allow
> new items to be added (carefully) into the transaction subsystem for a
> dataset.
> This is necessary for JENA-1302.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1302) Intermittent Lucene prepareCommit exception during heavy read/write load
[
https://issues.apache.org/jira/browse/JENA-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464061#comment-16464061
]
Andy Seaborne commented on JENA-1302:
-
JENA-1542 should apply to both TDB1 and TDB2.
> Intermittent Lucene prepareCommit exception during heavy read/write load
>
>
> Key: JENA-1302
> URL: https://issues.apache.org/jira/browse/JENA-1302
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki, TDB, Text
>Affects Versions: Jena 3.3.0
> Environment: CentOS 7.3 inside VM, 2 cores, OpenJDK 1.8.0_121
> (64-bit), 1GB JVM heap, Fuseki running as service
>Reporter: Vilnis Termanis (Iotic Labs)
>Assignee: Andy Seaborne
>Priority: Major
> Attachments: Jena1302_LuceneCommit.java, netstat.log,
> prepareCommit_error.tgz, visualvm_thread_dump.log
>
>
> (*Note*: Could not add Fuseki 2.6.0 as affected version although I assume
> this is a TDB/text rather than Fuseki-related issue.)
> *Steps:*
> # Start with plain Fuseki + given configuration (TDB store + lucene text
> indexing)
> # Import 1k.ttl
> # Run lockup.py (same host, mix of multiple parallel updates & single select)
> *Result:*
> Every now and again one of the update queries fails with a 500 server error
> which is logged as:
> {{DatasetGraphText ERROR Exception in prepareCommit: prepareCommit was
> already called with no corresponding call to commit}}
> *Notes:*
> - Not reproducible without fix for JENA-1296 (and discovered during fix
> verification for said issue)
> - Run with
> [apache-jena-fuseki-2.6.0-20170228.233930-10.tar.gz|https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena-fuseki/2.6.0-SNAPSHOT/apache-jena-fuseki-2.6.0-20170228.233930-10.tar.gz]
> - From cold-start of Fuseki, occurs within 30s of script run
> - Supplied test script required Python 3, {{rdflib>=4.2.2}} &
> {{SPARQLWrapper>=1.8.0}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (JENA-1542) Allow addition of transaction components after initial setup.
Andy Seaborne created JENA-1542:
---
Summary: Allow addition of transaction components after initial
setup.
Key: JENA-1542
URL: https://issues.apache.org/jira/browse/JENA-1542
Project: Apache Jena
Issue Type: Improvement
Components: TDB, TDB2
Affects Versions: Jena 3.7.0
Reporter: Andy Seaborne
Assignee: Andy Seaborne
Currently:
* TDB1: the set of {{JenaLifecycle}} components is fixed
* TDB2: the set of {{TransactionComponents}} is frozen during creation of a
dataset.
In order to be able to add a text index into the transaction handling, allow
new items to be added (carefully) into the transaction subsystem for a dataset.
This is necessary for JENA-1302.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
[
https://issues.apache.org/jira/browse/JENA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463911#comment-16463911
]
A. Soroka commented on JENA-1541:
-
I'm not sure whether Eyeball is maintained at all any more (it is _not_ part of
the Apache Jena releases). But let's see what we can do. Can you tell us where
you got the source code with which you are working? Did a plain build (using
{{ant}}) work? It looks a bit like you have a problem with your build
classpath.
[~andy.seaborne] do you know know if there are any active committers left with
expertise in Eyeball?
> Jena Eyeball - ant test fails with TestCase Error
> -
>
> Key: JENA-1541
> URL: https://issues.apache.org/jira/browse/JENA-1541
> Project: Apache Jena
> Issue Type: Question
> Components: Eyeball, Jena
>Reporter: Edward
>Priority: Major
> Labels: ant, eyeball, fail, jena, test
>
> Hello,
> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
> [https://jena.apache.org/documentation/tools/eyeball-getting-started.html]
> but it failed with following error:
> {code:java}
> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
> [junit] Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit] junit.framework.AssertionFailedError: Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit]
> [junit]
> BUILD FAILED
> /**/Downloads/eyeball-2.3/build.xml:146: Test
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
> {code}
> The tutorial says if the ant test doesn't pass, I should file a Jira Issue.
> So that's what I am doing.
> Help would be much appreciated!
>
> Greetings,
> Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
[
https://issues.apache.org/jira/browse/JENA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward updated JENA-1541:
-
Description:
Hello,
I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
[https://jena.apache.org/documentation/tools/eyeball-getting-started.html] but
it failed with following error:
{code:java}
[junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
[junit] Class
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
public constructor TestCase(String name) or TestCase()
[junit] junit.framework.AssertionFailedError: Class
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
public constructor TestCase(String name) or TestCase()
[junit]
[junit]
BUILD FAILED
/**/Downloads/eyeball-2.3/build.xml:146: Test
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
{code}
The tutorial says if the ant test doesn't pass, I should file a Jira Issue. So
that's what I am doing.
Help would be much appreciated!
Greetings,
Edward
was:
Hello,
I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
[here|[https://jena.apache.org/documentation/tools/eyeball-getting-started.html],]
but it failed with following error:
{code:java}
[junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
[junit] Class
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
public constructor TestCase(String name) or TestCase()
[junit] junit.framework.AssertionFailedError: Class
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
public constructor TestCase(String name) or TestCase()
[junit]
[junit]
BUILD FAILED
/**/Downloads/eyeball-2.3/build.xml:146: Test
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
{code}
The tutorial says if the ant test doesn't pass, I should file a Jira Issue. So
that's what I am doing.
Help would be much appreciated!
Greetings,
Edward
> Jena Eyeball - ant test fails with TestCase Error
> -
>
> Key: JENA-1541
> URL: https://issues.apache.org/jira/browse/JENA-1541
> Project: Apache Jena
> Issue Type: Question
> Components: Eyeball, Jena
>Reporter: Edward
>Priority: Major
> Labels: ant, eyeball, fail, jena, test
>
> Hello,
> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
> [https://jena.apache.org/documentation/tools/eyeball-getting-started.html]
> but it failed with following error:
> {code:java}
> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
> [junit] Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit] junit.framework.AssertionFailedError: Class
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
> public constructor TestCase(String name) or TestCase()
> [junit]
> [junit]
> BUILD FAILED
> /**/Downloads/eyeball-2.3/build.xml:146: Test
> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
> {code}
> The tutorial says if the ant test doesn't pass, I should file a Jira Issue.
> So that's what I am doing.
> Help would be much appreciated!
>
> Greetings,
> Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (JENA-1541) Jena Eyeball - ant test fails with TestCase Error
Edward created JENA-1541:
Summary: Jena Eyeball - ant test fails with TestCase Error
Key: JENA-1541
URL: https://issues.apache.org/jira/browse/JENA-1541
Project: Apache Jena
Issue Type: Question
Components: Eyeball, Jena
Reporter: Edward
Hello,
I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on
[here|[https://jena.apache.org/documentation/tools/eyeball-getting-started.html],]
but it failed with following error:
{code:java}
[junit] Testcase: warning(junit.framework.TestSuite$1): FAILED
[junit] Class
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
public constructor TestCase(String name) or TestCase()
[junit] junit.framework.AssertionFailedError: Class
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no
public constructor TestCase(String name) or TestCase()
[junit]
[junit]
BUILD FAILED
/**/Downloads/eyeball-2.3/build.xml:146: Test
com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed
{code}
The tutorial says if the ant test doesn't pass, I should file a Jira Issue. So
that's what I am doing.
Help would be much appreciated!
Greetings,
Edward
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1537) Remove requirement for Apache Xerces.
[ https://issues.apache.org/jira/browse/JENA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1537. - Resolution: Done Fix Version/s: 3.8.0 > Remove requirement for Apache Xerces. > - > > Key: JENA-1537 > URL: https://issues.apache.org/jira/browse/JENA-1537 > Project: Apache Jena > Issue Type: Improvement > Components: Datatypes, RDF/XML >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: 3.8.0 > > > Apache Xerces is used for parsing and also for dataype support. > We can switch to the JDK built-in XML parser (which is actually a forked > Xerces). > For jena-core datatype, we can extract the necessary code from Xerces and put > it in Jena (repackaged). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (JENA-1037) jena-osgi
[
https://issues.apache.org/jira/browse/JENA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1037.
-
Resolution: Fixed
Fix Version/s: 3.8.0
> jena-osgi
> -
>
> Key: JENA-1037
> URL: https://issues.apache.org/jira/browse/JENA-1037
> Project: Apache Jena
> Issue Type: Bug
> Components: OSGi
>Affects Versions: Jena 3.0.0
> Environment: Karaf
>Reporter: Ben Gould
>Priority: Major
> Fix For: 3.8.0
>
>
> I'm trying to create a simple interface/impl that will generate Prov-O RDF
> and place it on a JMS queue. This object will live in an OSGi environment
> and be injected into various operating services working in a workflow. I
> call the following piece of code:
> {noformat}
> public static OntModel createModel(final String ontologyUri) {
> final OntModel model =
> ModelFactory.createOntologyModel(OntModelSpec.OWL_MEM);
> model.read(ontologyUri);
> return model;
> }
> {noformat}
> with the ontologyUri="http://www.w3.org/ns/prov-o;; but when it gets to the
> ModelFactory.createOntologyModel(...) it chokes with the following stack
> trace.
> {noformat}
> java.lang.IncompatibleClassChangeError: Class
> org.apache.jena.rdfxml.xmlinput.impl.RDFXMLParser$SAXParserWithEncodingCheck
> does not implement the requested interface org.xml.sax.XMLReader
> at
> org.apache.jena.rdfxml.xmlinput.SAX2RDF.installHandlers(SAX2RDF.java:171)
> at
> org.apache.jena.rdfxml.xmlinput.impl.RDFXMLParser.(RDFXMLParser.java:63)
> at
> org.apache.jena.rdfxml.xmlinput.impl.RDFXMLParser.create(RDFXMLParser.java:127)
> at org.apache.jena.rdfxml.xmlinput.JenaReader.(JenaReader.java:69)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)[:1.8.0_11]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)[:1.8.0_11]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.8.0_11]
> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:408)[:1.8.0_11]
> at java.lang.Class.newInstance(Class.java:433)[:1.8.0_11]
> at
> org.apache.jena.rdf.model.impl.RDFReaderFImpl.getReader(RDFReaderFImpl.java:120)
> at org.apache.jena.rdf.model.impl.ModelCom.read(ModelCom.java:279)
> at
> org.apache.jena.ontology.OntDocumentManager.findMetadata(OntDocumentManager.java:892)
> at
> org.apache.jena.ontology.OntDocumentManager.initialiseMetadata(OntDocumentManager.java:850)
> at
> org.apache.jena.ontology.OntDocumentManager.(OntDocumentManager.java:198)
> at
> org.apache.jena.ontology.OntDocumentManager.(OntDocumentManager.java:180)
> at
> org.apache.jena.ontology.OntDocumentManager.(OntDocumentManager.java:164)
> at
> org.apache.jena.ontology.OntDocumentManager.getInstance(OntDocumentManager.java:242)
> at
> org.apache.jena.ontology.OntModelSpec.getDocumentManager(OntModelSpec.java:320)
> at
> org.apache.jena.ontology.impl.OntModelImpl.getDocumentManager(OntModelImpl.java:189)
> at
> org.apache.jena.ontology.impl.OntModelImpl.loadImports(OntModelImpl.java:1964)
> at
> org.apache.jena.ontology.impl.OntModelImpl.(OntModelImpl.java:151)
> at
> org.apache.jena.ontology.impl.OntModelImpl.(OntModelImpl.java:131)
> at
> org.apache.jena.rdf.model.ModelFactory.createOntologyModel(ModelFactory.java:288)
> ...
> {noformat}
> What's triggering this exception is the following snippet of code:
> {noformat}
> public static OntModel createModel(final String ontologyUri) {
> final OntModel model =
> ModelFactory.createOntologyModel(OntModelSpec.OWL_MEM);
> model.read(ontologyUri);
> return model;
> }
> {noformat}
> I'm basically creating an OntModel and then pulling the OntClass and
> OntProperty fields out of the model for creating some Models.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1037) jena-osgi
[
https://issues.apache.org/jira/browse/JENA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463601#comment-16463601
]
Andy Seaborne commented on JENA-1037:
-
Apache Xerces is no longer a dependency requirement for Apache Jena. JENA-1537
extracts the Xerces validation code for Jena's use and removes the dependency
on Xerces as the XML parser.
Any XML parser can be used with Jena (defaulting to the JDK-provided one)
through the usual mechanism for adding to the application.
> jena-osgi
> -
>
> Key: JENA-1037
> URL: https://issues.apache.org/jira/browse/JENA-1037
> Project: Apache Jena
> Issue Type: Bug
> Components: OSGi
>Affects Versions: Jena 3.0.0
> Environment: Karaf
>Reporter: Ben Gould
>Priority: Major
> Fix For: 3.8.0
>
>
> I'm trying to create a simple interface/impl that will generate Prov-O RDF
> and place it on a JMS queue. This object will live in an OSGi environment
> and be injected into various operating services working in a workflow. I
> call the following piece of code:
> {noformat}
> public static OntModel createModel(final String ontologyUri) {
> final OntModel model =
> ModelFactory.createOntologyModel(OntModelSpec.OWL_MEM);
> model.read(ontologyUri);
> return model;
> }
> {noformat}
> with the ontologyUri="http://www.w3.org/ns/prov-o;; but when it gets to the
> ModelFactory.createOntologyModel(...) it chokes with the following stack
> trace.
> {noformat}
> java.lang.IncompatibleClassChangeError: Class
> org.apache.jena.rdfxml.xmlinput.impl.RDFXMLParser$SAXParserWithEncodingCheck
> does not implement the requested interface org.xml.sax.XMLReader
> at
> org.apache.jena.rdfxml.xmlinput.SAX2RDF.installHandlers(SAX2RDF.java:171)
> at
> org.apache.jena.rdfxml.xmlinput.impl.RDFXMLParser.(RDFXMLParser.java:63)
> at
> org.apache.jena.rdfxml.xmlinput.impl.RDFXMLParser.create(RDFXMLParser.java:127)
> at org.apache.jena.rdfxml.xmlinput.JenaReader.(JenaReader.java:69)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)[:1.8.0_11]
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)[:1.8.0_11]
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)[:1.8.0_11]
> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:408)[:1.8.0_11]
> at java.lang.Class.newInstance(Class.java:433)[:1.8.0_11]
> at
> org.apache.jena.rdf.model.impl.RDFReaderFImpl.getReader(RDFReaderFImpl.java:120)
> at org.apache.jena.rdf.model.impl.ModelCom.read(ModelCom.java:279)
> at
> org.apache.jena.ontology.OntDocumentManager.findMetadata(OntDocumentManager.java:892)
> at
> org.apache.jena.ontology.OntDocumentManager.initialiseMetadata(OntDocumentManager.java:850)
> at
> org.apache.jena.ontology.OntDocumentManager.(OntDocumentManager.java:198)
> at
> org.apache.jena.ontology.OntDocumentManager.(OntDocumentManager.java:180)
> at
> org.apache.jena.ontology.OntDocumentManager.(OntDocumentManager.java:164)
> at
> org.apache.jena.ontology.OntDocumentManager.getInstance(OntDocumentManager.java:242)
> at
> org.apache.jena.ontology.OntModelSpec.getDocumentManager(OntModelSpec.java:320)
> at
> org.apache.jena.ontology.impl.OntModelImpl.getDocumentManager(OntModelImpl.java:189)
> at
> org.apache.jena.ontology.impl.OntModelImpl.loadImports(OntModelImpl.java:1964)
> at
> org.apache.jena.ontology.impl.OntModelImpl.(OntModelImpl.java:151)
> at
> org.apache.jena.ontology.impl.OntModelImpl.(OntModelImpl.java:131)
> at
> org.apache.jena.rdf.model.ModelFactory.createOntologyModel(ModelFactory.java:288)
> ...
> {noformat}
> What's triggering this exception is the following snippet of code:
> {noformat}
> public static OntModel createModel(final String ontologyUri) {
> final OntModel model =
> ModelFactory.createOntologyModel(OntModelSpec.OWL_MEM);
> model.read(ontologyUri);
> return model;
> }
> {noformat}
> I'm basically creating an OntModel and then pulling the OntClass and
> OntProperty fields out of the model for creating some Models.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1288) Reduce dependency on the Xerces jar.
[
https://issues.apache.org/jira/browse/JENA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463598#comment-16463598
]
Andy Seaborne commented on JENA-1288:
-
Further update:
Apache Xerces is no longer a dependency requirement for Apache Jena. JENA-1537
extracts the Xerces validation code for Jena's use and removes the dependency
on Xerces as the XML parser.
> Reduce dependency on the Xerces jar.
>
>
> Key: JENA-1288
> URL: https://issues.apache.org/jira/browse/JENA-1288
> Project: Apache Jena
> Issue Type: Task
>Affects Versions: Jena 3.2.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Minor
> Fix For: Jena 3.3.0
>
>
> There are facilities in the standard JDK that can be used instead of directly
> calling Xerces, specifically {{DatatypeConverter}}. With these changes, only
> one class relies on Xerces directly, {{XSDDatatype}}.
> We have to be careful though - it is not perfect. I found that {{parseByte}}
> calls {{parseInt}} and casts the result to a java {{byte}} so it passes "300"
> and "3000" which are not valid byte lexical forms.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-914) Get Jena working on Android
[ https://issues.apache.org/jira/browse/JENA-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463600#comment-16463600 ] Andy Seaborne commented on JENA-914: Apache Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces as the XML parser. > Get Jena working on Android > --- > > Key: JENA-914 > URL: https://issues.apache.org/jira/browse/JENA-914 > Project: Apache Jena > Issue Type: Improvement > Components: ARQ, TDB > Environment: Android >Reporter: Sören Brunk >Priority: Minor > Labels: android > > Currently, Jena can't be used on Android as is, due to multiple issues caused > by differences between the standard JVM and Android's Dalvik VM. > The main issues are > # Package conflicts > ## The StAX API (javax.xml.stream is missing on Android). It's not possible > to just provide the classes as including packages from core Java namespaces > doesn't work. > ## Android provides an ancient version of httpclient that is incompatible > with version 4.2 required by Jena. > # TDB uses java.lang.ManagementFactory in ProcessUtils which isn't available > on Android. It's possible to use android.os.Process instead but that requires > a dependency on the Android SDK. > There is a [project|https://github.com/seus-inf/jena-android] that does some > post-processing on the Jena packages to create a variant that runs on > Android. Some of it might be of use to get Android support into mainline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (JENA-1364) Jena-core has dependency on vulnerable Xerces version
[
https://issues.apache.org/jira/browse/JENA-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463593#comment-16463593
]
Andy Seaborne edited comment on JENA-1364 at 5/4/18 9:10 AM:
-
Apache Xerces is no longer a dependency requirement for Apache Jena. JENA-1537
extracts the Xerces validation code for Jena's use and removes the dependency
on Xerces as the XML parser.
Any XML parser can be used with Jena (defaulting to the JDK-provided one)
through the usual mechanism for adding to the application.
was (Author: andy.seaborne):
Apaxche Xerces is no longer a dependency requirement for Apache Jena. JENA-1537
extracts the Xerces validation code for Jena's use and removes the dependency
on Xerces as the XML parser.
Any XML parser can be used with Jena (defaulting to the JDK-provided one)
through the usual mechanism for adding to the application.
> Jena-core has dependency on vulnerable Xerces version
> -
>
> Key: JENA-1364
> URL: https://issues.apache.org/jira/browse/JENA-1364
> Project: Apache Jena
> Issue Type: Bug
> Components: Core
>Affects Versions: Jena 3.3.0
>Reporter: Yev Bronshteyn
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.8.0
>
>
> jena-core pulls in Xerces 2.11.0, which has a known vulnerability
> CVE-2013-4002 (exploitable, resulting in DOS).
> {code}
> [INFO] +- org.apache.jena:apache-jena-libs:pom:3.3.0:compile
> [INFO] | +- org.apache.jena:jena-tdb:jar:3.3.0:compile
> [INFO] | | \- org.apache.jena:jena-arq:jar:3.3.0:compile
> [INFO] | | +- org.apache.jena:jena-core:jar:3.3.0:compile
> [INFO] | | | +- xerces:xercesImpl:jar:2.11.0:compile
> {code}
> A potential fix would be to pull in xerces 2.11.0.SP1 or later from one of
> the Red Hat repositories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (JENA-341) Jena breaks with Xerces 2.11.0 (XML Schema 1.1 branch)
[ https://issues.apache.org/jira/browse/JENA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463591#comment-16463591 ] Andy Seaborne edited comment on JENA-341 at 5/4/18 9:10 AM: Apache Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces as the XML parser. Any XML parser can be used with Jena (defaulting to the JDK-provided one) through the usual mechanism for adding to the application. was (Author: andy.seaborne): Apaxche Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces as the XML parser. Any XML parser can be used with Jena (defaulting to the JDK-provided one) through the usual mechanism for adding to the application. > Jena breaks with Xerces 2.11.0 (XML Schema 1.1 branch) > -- > > Key: JENA-341 > URL: https://issues.apache.org/jira/browse/JENA-341 > Project: Apache Jena > Issue Type: Bug > Components: Jena >Reporter: Radu Coravu >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.8.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Running Jena with a Xerces 2.11.0 build which is XML Schema 1.1 aware (the > xerces-java-xml-schema-1.1-dev branch) breaks with a NPE: > ERROR [my.package.MyClass:105] An exception occured during data loading > java.lang.NullPointerException > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.getActualValue(Unknown > Source) > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.validate(Unknown > Source) > at com.hp.hpl.jena.datatypes.xsd.XSDDatatype.parse(XSDDatatype.java:272) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.setValue(LiteralLabelImpl.java:213) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.setLiteralLabel_1(LiteralLabelImpl.java:107) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.(LiteralLabelImpl.java:96) > at > com.hp.hpl.jena.graph.impl.LiteralLabelFactory.createLiteralLabel(LiteralLabelFactory.java:28) > at com.hp.hpl.jena.graph.Node.createLiteral(Node.java:101) > at com.hp.hpl.jena.rdf.arp.JenaReader.convert(JenaReader.java:120) > at com.hp.hpl.jena.rdf.arp.JenaReader.convert(JenaReader.java:143) > at com.hp.hpl.jena.rdf.arp.JenaHandler.statement(JenaHandler.java:89) > at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.triple(XMLHandler.java:86) > at > com.hp.hpl.jena.rdf.arp.impl.ParserSupport.triple(ParserSupport.java:228) > at > com.hp.hpl.jena.rdf.arp.states.WantDescription.aPredAndObj(WantDescription.java:116) > at > com.hp.hpl.jena.rdf.arp.states.WantPropertyElement.theObject(WantPropertyElement.java:213) > at > com.hp.hpl.jena.rdf.arp.states.WantTypedLiteral.endElement(WantTypedLiteral.java:50) > at > com.hp.hpl.jena.rdf.arp.impl.XMLHandler.endElement(XMLHandler.java:133) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown > Source) > at org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(Unknown > Source) > at org.apache.xerces.impl.XMLNamespaceBinder.endElement(Unknown Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at > com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:155) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:173) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:160) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:232) > at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:235) > at my.package.MyClass.load(MyClass.java:97) > The org.apache.xerces.impl.validation.ValidationState you are passing to the > Xerces XSSimpleTypeDecl has a NULL TypeValidatorHelper and the Xerces build > which is XML Schema 1.1 aware looks a lot in the TypeValidatorHelper to see > if it is running in XML Schema 1.1 compatibility mode like: > final String options = context.getTypeValidatorHelper().isXMLSchema11() ? > "Xbh" : "X"; > The class org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl is an internal Xerces > class. Maybe you should
[jira] [Comment Edited] (JENA-341) Jena breaks with Xerces 2.11.0 (XML Schema 1.1 branch)
[ https://issues.apache.org/jira/browse/JENA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463591#comment-16463591 ] Andy Seaborne edited comment on JENA-341 at 5/4/18 9:08 AM: Apaxche Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces as the XML parser. Any XML parser can be used with Jena (defaulting to the JDK-provided one) through the usual mechanism for adding to the application. was (Author: andy.seaborne): Apaxche Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces. Any XML parser can be used with Jena (defaulting to the JDK-provided one) through the usual mechanism for adding to the application. > Jena breaks with Xerces 2.11.0 (XML Schema 1.1 branch) > -- > > Key: JENA-341 > URL: https://issues.apache.org/jira/browse/JENA-341 > Project: Apache Jena > Issue Type: Bug > Components: Jena >Reporter: Radu Coravu >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.8.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Running Jena with a Xerces 2.11.0 build which is XML Schema 1.1 aware (the > xerces-java-xml-schema-1.1-dev branch) breaks with a NPE: > ERROR [my.package.MyClass:105] An exception occured during data loading > java.lang.NullPointerException > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.getActualValue(Unknown > Source) > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.validate(Unknown > Source) > at com.hp.hpl.jena.datatypes.xsd.XSDDatatype.parse(XSDDatatype.java:272) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.setValue(LiteralLabelImpl.java:213) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.setLiteralLabel_1(LiteralLabelImpl.java:107) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.(LiteralLabelImpl.java:96) > at > com.hp.hpl.jena.graph.impl.LiteralLabelFactory.createLiteralLabel(LiteralLabelFactory.java:28) > at com.hp.hpl.jena.graph.Node.createLiteral(Node.java:101) > at com.hp.hpl.jena.rdf.arp.JenaReader.convert(JenaReader.java:120) > at com.hp.hpl.jena.rdf.arp.JenaReader.convert(JenaReader.java:143) > at com.hp.hpl.jena.rdf.arp.JenaHandler.statement(JenaHandler.java:89) > at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.triple(XMLHandler.java:86) > at > com.hp.hpl.jena.rdf.arp.impl.ParserSupport.triple(ParserSupport.java:228) > at > com.hp.hpl.jena.rdf.arp.states.WantDescription.aPredAndObj(WantDescription.java:116) > at > com.hp.hpl.jena.rdf.arp.states.WantPropertyElement.theObject(WantPropertyElement.java:213) > at > com.hp.hpl.jena.rdf.arp.states.WantTypedLiteral.endElement(WantTypedLiteral.java:50) > at > com.hp.hpl.jena.rdf.arp.impl.XMLHandler.endElement(XMLHandler.java:133) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown > Source) > at org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(Unknown > Source) > at org.apache.xerces.impl.XMLNamespaceBinder.endElement(Unknown Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at > com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:155) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:173) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:160) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:232) > at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:235) > at my.package.MyClass.load(MyClass.java:97) > The org.apache.xerces.impl.validation.ValidationState you are passing to the > Xerces XSSimpleTypeDecl has a NULL TypeValidatorHelper and the Xerces build > which is XML Schema 1.1 aware looks a lot in the TypeValidatorHelper to see > if it is running in XML Schema 1.1 compatibility mode like: > final String options = context.getTypeValidatorHelper().isXMLSchema11() ? > "Xbh" : "X"; > The class org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl is an internal Xerces > class. Maybe you should try breaking
[jira] [Resolved] (JENA-1364) Jena-core has dependency on vulnerable Xerces version
[
https://issues.apache.org/jira/browse/JENA-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1364.
-
Resolution: Fixed
Assignee: Andy Seaborne
Fix Version/s: Jena 3.8.0
Apaxche Xerces is no longer a dependency requirement for Apache Jena. JENA-1537
extracts the Xerces validation code for Jena's use and removes the dependency
on Xerces as the XML parser.
Any XML parser can be used with Jena (defaulting to the JDK-provided one)
through the usual mechanism for adding to the application.
> Jena-core has dependency on vulnerable Xerces version
> -
>
> Key: JENA-1364
> URL: https://issues.apache.org/jira/browse/JENA-1364
> Project: Apache Jena
> Issue Type: Bug
> Components: Core
>Affects Versions: Jena 3.3.0
>Reporter: Yev Bronshteyn
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.8.0
>
>
> jena-core pulls in Xerces 2.11.0, which has a known vulnerability
> CVE-2013-4002 (exploitable, resulting in DOS).
> {code}
> [INFO] +- org.apache.jena:apache-jena-libs:pom:3.3.0:compile
> [INFO] | +- org.apache.jena:jena-tdb:jar:3.3.0:compile
> [INFO] | | \- org.apache.jena:jena-arq:jar:3.3.0:compile
> [INFO] | | +- org.apache.jena:jena-core:jar:3.3.0:compile
> [INFO] | | | +- xerces:xercesImpl:jar:2.11.0:compile
> {code}
> A potential fix would be to pull in xerces 2.11.0.SP1 or later from one of
> the Red Hat repositories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-341) Jena breaks with Xerces 2.11.0 (XML Schema 1.1 branch)
[ https://issues.apache.org/jira/browse/JENA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-341. Resolution: Fixed Assignee: Andy Seaborne Fix Version/s: Jena 3.8.0 Apaxche Xerces is no longer a dependency requirement for Apache Jena. JENA-1537 extracts the Xerces validation code for Jena's use and removes the dependency on Xerces. Any XML parser can be used with Jena (defaulting to the JDK-provided one) through the usual mechanism for adding to the application. > Jena breaks with Xerces 2.11.0 (XML Schema 1.1 branch) > -- > > Key: JENA-341 > URL: https://issues.apache.org/jira/browse/JENA-341 > Project: Apache Jena > Issue Type: Bug > Components: Jena >Reporter: Radu Coravu >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.8.0 > > Original Estimate: 3h > Remaining Estimate: 3h > > Running Jena with a Xerces 2.11.0 build which is XML Schema 1.1 aware (the > xerces-java-xml-schema-1.1-dev branch) breaks with a NPE: > ERROR [my.package.MyClass:105] An exception occured during data loading > java.lang.NullPointerException > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.getActualValue(Unknown > Source) > at org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl.validate(Unknown > Source) > at com.hp.hpl.jena.datatypes.xsd.XSDDatatype.parse(XSDDatatype.java:272) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.setValue(LiteralLabelImpl.java:213) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.setLiteralLabel_1(LiteralLabelImpl.java:107) > at > com.hp.hpl.jena.graph.impl.LiteralLabelImpl.(LiteralLabelImpl.java:96) > at > com.hp.hpl.jena.graph.impl.LiteralLabelFactory.createLiteralLabel(LiteralLabelFactory.java:28) > at com.hp.hpl.jena.graph.Node.createLiteral(Node.java:101) > at com.hp.hpl.jena.rdf.arp.JenaReader.convert(JenaReader.java:120) > at com.hp.hpl.jena.rdf.arp.JenaReader.convert(JenaReader.java:143) > at com.hp.hpl.jena.rdf.arp.JenaHandler.statement(JenaHandler.java:89) > at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.triple(XMLHandler.java:86) > at > com.hp.hpl.jena.rdf.arp.impl.ParserSupport.triple(ParserSupport.java:228) > at > com.hp.hpl.jena.rdf.arp.states.WantDescription.aPredAndObj(WantDescription.java:116) > at > com.hp.hpl.jena.rdf.arp.states.WantPropertyElement.theObject(WantPropertyElement.java:213) > at > com.hp.hpl.jena.rdf.arp.states.WantTypedLiteral.endElement(WantTypedLiteral.java:50) > at > com.hp.hpl.jena.rdf.arp.impl.XMLHandler.endElement(XMLHandler.java:133) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown > Source) > at org.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(Unknown > Source) > at org.apache.xerces.impl.XMLNamespaceBinder.endElement(Unknown Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at > com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:155) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:173) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:160) > at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:232) > at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:235) > at my.package.MyClass.load(MyClass.java:97) > The org.apache.xerces.impl.validation.ValidationState you are passing to the > Xerces XSSimpleTypeDecl has a NULL TypeValidatorHelper and the Xerces build > which is XML Schema 1.1 aware looks a lot in the TypeValidatorHelper to see > if it is running in XML Schema 1.1 compatibility mode like: > final String options = context.getTypeValidatorHelper().isXMLSchema11() ? > "Xbh" : "X"; > The class org.apache.xerces.impl.dv.xs.XSSimpleTypeDecl is an internal Xerces > class. Maybe you should try breaking dependencies to internal classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1537) Remove requirement for Apache Xerces.
[ https://issues.apache.org/jira/browse/JENA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463584#comment-16463584 ] ASF GitHub Bot commented on JENA-1537: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/413 > Remove requirement for Apache Xerces. > - > > Key: JENA-1537 > URL: https://issues.apache.org/jira/browse/JENA-1537 > Project: Apache Jena > Issue Type: Improvement > Components: Datatypes, RDF/XML >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > > Apache Xerces is used for parsing and also for dataype support. > We can switch to the JDK built-in XML parser (which is actually a forked > Xerces). > For jena-core datatype, we can extract the necessary code from Xerces and put > it in Jena (repackaged). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1537) Remove requirement for Apache Xerces.
[ https://issues.apache.org/jira/browse/JENA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463582#comment-16463582 ] ASF subversion and git services commented on JENA-1537: --- Commit 2e917bd07fb8963f09f39921553e8e2909cc8fb1 in jena's branch refs/heads/master from [~andy.seaborne] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=2e917bd ] JENA-1537: Merge commit 'refs/pull/413/head' of https://github.com/apache/jena This closes #413. > Remove requirement for Apache Xerces. > - > > Key: JENA-1537 > URL: https://issues.apache.org/jira/browse/JENA-1537 > Project: Apache Jena > Issue Type: Improvement > Components: Datatypes, RDF/XML >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > > Apache Xerces is used for parsing and also for dataype support. > We can switch to the JDK built-in XML parser (which is actually a forked > Xerces). > For jena-core datatype, we can extract the necessary code from Xerces and put > it in Jena (repackaged). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1537) Remove requirement for Apache Xerces.
[ https://issues.apache.org/jira/browse/JENA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463581#comment-16463581 ] ASF subversion and git services commented on JENA-1537: --- Commit 44f751b5d65d528a65756608fbea5b3ef43a2ea0 in jena's branch refs/heads/master from [~andy.seaborne] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=44f751b ] JENA-1537: Update NOTICE to include NOTICE items from Apache Xerces source > Remove requirement for Apache Xerces. > - > > Key: JENA-1537 > URL: https://issues.apache.org/jira/browse/JENA-1537 > Project: Apache Jena > Issue Type: Improvement > Components: Datatypes, RDF/XML >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > > Apache Xerces is used for parsing and also for dataype support. > We can switch to the JDK built-in XML parser (which is actually a forked > Xerces). > For jena-core datatype, we can extract the necessary code from Xerces and put > it in Jena (repackaged). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena pull request #413: JENA-1537: Remove dependency on Apache Xerces.
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/413 ---
[jira] [Closed] (JENA-1514) Class cast exception with BigInteger literals.
[
https://issues.apache.org/jira/browse/JENA-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-1514.
---
Resolution: Not A Bug
This is major change.
The datatype handling code from Xerces is now incorporated into Jena (see
JENA-1537).
Longer term, it may be better to replace with a more focused approach specific
to the needs of Jena. https://github.com/afs/xsd4ld is an example of this.
Large scale changes could also combine the needs of ARQ, specifically
{{NodeValue}}.
See also Jena-1402 (JDK provided {{Duration}} does not get the right answers in
subtraction).
> Class cast exception with BigInteger literals.
> --
>
> Key: JENA-1514
> URL: https://issues.apache.org/jira/browse/JENA-1514
> Project: Apache Jena
> Issue Type: Bug
> Components: Jena
>Affects Versions: Jena 3.6.0, Jena 3.7.0
>Reporter: Claude Warren
>Priority: Minor
> Attachments: BigIntIssue.java
>
>
> When saving a BigInteger as a literal it is converted into an
> XSDBaseNumericType.
> When that type is read back it is converted into the smallest numeric data
> type that can hold the value; a narrowing if you will.
> While this works fine for primitive and primitive wrapping types (e.g. int
> and Integer) there is no automatic boxing available for BigInteger so
> attempting to retrieve the value of a BigInteger that is smaller than the
> Long.MAX_VALUE will result in a class cast exception when the primitive type
> is cast to the BigInteger.
> I suspect the similar issues arise when BigDecimal is also used but I have
> not tested.
> Should we address this issue by creating a BigInteger and BigDecimal type
> that perhaps extends XSDBaseNumericType? Should we address this issue at all
> and just post a warning?
> Test code is included to show the issue.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1532.
-
Resolution: Fixed
Assignee: Anuj Kumar (was: Andy Seaborne)
Fix Version/s: Jena 3.8.0
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Anuj Kumar
>Priority: Major
> Fix For: Jena 3.8.0
>
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1539) Improve compatibility rules for Txn inside a Transaction.
[ https://issues.apache.org/jira/browse/JENA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1539. - Resolution: Done > Improve compatibility rules for Txn inside a Transaction. > - > > Key: JENA-1539 > URL: https://issues.apache.org/jira/browse/JENA-1539 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.7.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > Running Txn inside an existing transaction can be made less restrictive. > This is not full nested transactions. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (JENA-1538) Include TDB2 in jena-osgi module
[ https://issues.apache.org/jira/browse/JENA-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1538. - Resolution: Fixed > Include TDB2 in jena-osgi module > > > Key: JENA-1538 > URL: https://issues.apache.org/jira/browse/JENA-1538 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.7.0 >Reporter: Aaron Coburn >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > The jena-tdb2 packages are not included in the jena-osgi module. Should they > be? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463561#comment-16463561
]
ASF subversion and git services commented on JENA-1532:
---
Commit 77058de86a6a85f6bdffc5b0b733572cac1d84b1 in jena's branch
refs/heads/master from Anuj Kumar
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=77058de ]
JENA-1532 | fix for date based text query search
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Andy Seaborne
>Priority: Major
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1538) Include TDB2 in jena-osgi module
[ https://issues.apache.org/jira/browse/JENA-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463564#comment-16463564 ] ASF subversion and git services commented on JENA-1538: --- Commit 18eb495c788c77a623536787d8342440e4836344 in jena's branch refs/heads/master from [~andy.seaborne] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=18eb495 ] JENA-1538: Merge commit 'refs/pull/411/head' of https://github.com/apache/jena This closes #411. > Include TDB2 in jena-osgi module > > > Key: JENA-1538 > URL: https://issues.apache.org/jira/browse/JENA-1538 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.7.0 >Reporter: Aaron Coburn >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > The jena-tdb2 packages are not included in the jena-osgi module. Should they > be? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1539) Improve compatibility rules for Txn inside a Transaction.
[ https://issues.apache.org/jira/browse/JENA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463565#comment-16463565 ] ASF subversion and git services commented on JENA-1539: --- Commit ec7221176e131b34bfc1ac8cdfc5251b3daaddbe in jena's branch refs/heads/master from [~andy.seaborne] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ec72211 ] JENA-1539: Merge commit 'refs/pull/412/head' of https://github.com/apache/jena This closes #412. > Improve compatibility rules for Txn inside a Transaction. > - > > Key: JENA-1539 > URL: https://issues.apache.org/jira/browse/JENA-1539 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.7.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > Running Txn inside an existing transaction can be made less restrictive. > This is not full nested transactions. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena pull request #412: JENA-1539: Txn nesting compatibility
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/412 ---
[GitHub] jena pull request #390: Bugfix Tutorial 6: Missing "/" at the end of an URI ...
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/390 ---
[jira] [Commented] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463560#comment-16463560
]
ASF subversion and git services commented on JENA-1532:
---
Commit 7f4915ee6c94b1044155110fe4612147a9e8de91 in jena's branch
refs/heads/master from Anuj Kumar
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=7f4915e ]
JENA-1532 | fix for date based text query search
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Andy Seaborne
>Priority: Major
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] jena pull request #406: JENA-1532 | Added support for escaping special chara...
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/406 ---
[jira] [Commented] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463563#comment-16463563
]
ASF subversion and git services commented on JENA-1532:
---
Commit 81fedb16a4869783ff3dc3eb40f65ebd0c5fe13e in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=81fedb1 ]
JENA-1532: Merge commit 'refs/pull/406/head' of https://github.com/apache/jena
This closes #406.
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Andy Seaborne
>Priority: Major
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463559#comment-16463559
]
ASF subversion and git services commented on JENA-1532:
---
Commit c2a3bac147a786210b1ba4125a4be9edc66719c4 in jena's branch
refs/heads/master from Anuj Kumar
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c2a3bac ]
JENA-1532 | fix for date based text query search
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Andy Seaborne
>Priority: Major
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463566#comment-16463566
]
ASF GitHub Bot commented on JENA-1532:
--
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/406
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Andy Seaborne
>Priority: Major
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1539) Improve compatibility rules for Txn inside a Transaction.
[ https://issues.apache.org/jira/browse/JENA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463567#comment-16463567 ] ASF GitHub Bot commented on JENA-1539: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/412 > Improve compatibility rules for Txn inside a Transaction. > - > > Key: JENA-1539 > URL: https://issues.apache.org/jira/browse/JENA-1539 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.7.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > Running Txn inside an existing transaction can be made less restrictive. > This is not full nested transactions. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1539) Improve compatibility rules for Txn inside a Transaction.
[ https://issues.apache.org/jira/browse/JENA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463562#comment-16463562 ] ASF subversion and git services commented on JENA-1539: --- Commit dbce176ad7f9a422198c24f8b7b79cb3c1fe5d9f in jena's branch refs/heads/master from [~andy.seaborne] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=dbce176 ] JENA-1539: Txn nesting compatibility > Improve compatibility rules for Txn inside a Transaction. > - > > Key: JENA-1539 > URL: https://issues.apache.org/jira/browse/JENA-1539 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.7.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > Running Txn inside an existing transaction can be made less restrictive. > This is not full nested transactions. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena pull request #411: Include TDB2 in the jena-osgi module
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/411 ---
[jira] [Commented] (JENA-1538) Include TDB2 in jena-osgi module
[ https://issues.apache.org/jira/browse/JENA-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463568#comment-16463568 ] ASF GitHub Bot commented on JENA-1538: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/411 > Include TDB2 in jena-osgi module > > > Key: JENA-1538 > URL: https://issues.apache.org/jira/browse/JENA-1538 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.7.0 >Reporter: Aaron Coburn >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > The jena-tdb2 packages are not included in the jena-osgi module. Should they > be? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena issue #390: Bugfix Tutorial 6: Missing "/" at the end of an URI resulte...
Github user afs commented on the issue: https://github.com/apache/jena/pull/390 Hi @supergitacc -- the data has been fixed in all the vc-db files. Thanks for the report. ---
[jira] [Commented] (JENA-1540) Bugfix Tutorial 6: Missing "/" at the end of an URI
[ https://issues.apache.org/jira/browse/JENA-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463528#comment-16463528 ] Andy Seaborne commented on JENA-1540: - The problem is with the data - all the URIs for people have a trailing slash. > Bugfix Tutorial 6: Missing "/" at the end of an URI > --- > > Key: JENA-1540 > URL: https://issues.apache.org/jira/browse/JENA-1540 > Project: Apache Jena > Issue Type: Bug >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.8.0 > > > Reported in [PR#390|https://github.com/apache/jena/pull/390] > h3. *supergitacc* commented [on 4 > Apr|https://github.com/apache/jena/pull/390#issue-179386524] > |I found a bug in tutorial 6 and propose a fix for it. > Without "/" at the end of the URI of JohnSmith > ([http://somewhere/JohnSmith/]) an exception occurs in line 51 because no > resource vcard could be found. The exception was: "Exception in thread "main" > java.lang.NullPointerException". Adding the slash at the end fixes the issue > because rdf:about="[http://somewhere/JohnSmith/;>|http://somewhere/JohnSmith/%22%3E]| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1540) Bugfix Tutorial 6: Missing "/" at the end of an URI
[ https://issues.apache.org/jira/browse/JENA-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463529#comment-16463529 ] ASF subversion and git services commented on JENA-1540: --- Commit 1830886 from [~andy.seaborne] in branch 'site/trunk' [ https://svn.apache.org/r1830886 ] JENA-1540: Fix tutorial data > Bugfix Tutorial 6: Missing "/" at the end of an URI > --- > > Key: JENA-1540 > URL: https://issues.apache.org/jira/browse/JENA-1540 > Project: Apache Jena > Issue Type: Bug >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.8.0 > > > Reported in [PR#390|https://github.com/apache/jena/pull/390] > h3. *supergitacc* commented [on 4 > Apr|https://github.com/apache/jena/pull/390#issue-179386524] > |I found a bug in tutorial 6 and propose a fix for it. > Without "/" at the end of the URI of JohnSmith > ([http://somewhere/JohnSmith/]) an exception occurs in line 51 because no > resource vcard could be found. The exception was: "Exception in thread "main" > java.lang.NullPointerException". Adding the slash at the end fixes the issue > because rdf:about="[http://somewhere/JohnSmith/;>|http://somewhere/JohnSmith/%22%3E]| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (JENA-1540) Bugfix Tutorial 6: Missing "/" at the end of an URI
[ https://issues.apache.org/jira/browse/JENA-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1540. - Resolution: Fixed Fix Version/s: Jena 3.8.0 > Bugfix Tutorial 6: Missing "/" at the end of an URI > --- > > Key: JENA-1540 > URL: https://issues.apache.org/jira/browse/JENA-1540 > Project: Apache Jena > Issue Type: Bug >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 3.8.0 > > > Reported in [PR#390|https://github.com/apache/jena/pull/390] > h3. *supergitacc* commented [on 4 > Apr|https://github.com/apache/jena/pull/390#issue-179386524] > |I found a bug in tutorial 6 and propose a fix for it. > Without "/" at the end of the URI of JohnSmith > ([http://somewhere/JohnSmith/]) an exception occurs in line 51 because no > resource vcard could be found. The exception was: "Exception in thread "main" > java.lang.NullPointerException". Adding the slash at the end fixes the issue > because rdf:about="[http://somewhere/JohnSmith/;>|http://somewhere/JohnSmith/%22%3E]| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (JENA-1540) Bugfix Tutorial 6: Missing "/" at the end of an URI
[ https://issues.apache.org/jira/browse/JENA-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne reassigned JENA-1540: --- Assignee: Andy Seaborne > Bugfix Tutorial 6: Missing "/" at the end of an URI > --- > > Key: JENA-1540 > URL: https://issues.apache.org/jira/browse/JENA-1540 > Project: Apache Jena > Issue Type: Bug >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > > Reported in [PR#390|https://github.com/apache/jena/pull/390] > h3. *supergitacc* commented [on 4 > Apr|https://github.com/apache/jena/pull/390#issue-179386524] > |I found a bug in tutorial 6 and propose a fix for it. > Without "/" at the end of the URI of JohnSmith > ([http://somewhere/JohnSmith/]) an exception occurs in line 51 because no > resource vcard could be found. The exception was: "Exception in thread "main" > java.lang.NullPointerException". Adding the slash at the end fixes the issue > because rdf:about="[http://somewhere/JohnSmith/;>|http://somewhere/JohnSmith/%22%3E]| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JENA-1540) Bugfix Tutorial 6: Missing "/" at the end of an URI
Andy Seaborne created JENA-1540: --- Summary: Bugfix Tutorial 6: Missing "/" at the end of an URI Key: JENA-1540 URL: https://issues.apache.org/jira/browse/JENA-1540 Project: Apache Jena Issue Type: Bug Reporter: Andy Seaborne Reported in [PR#390|https://github.com/apache/jena/pull/390] h3. *supergitacc* commented [on 4 Apr|https://github.com/apache/jena/pull/390#issue-179386524] |I found a bug in tutorial 6 and propose a fix for it. Without "/" at the end of the URI of JohnSmith ([http://somewhere/JohnSmith/]) an exception occurs in line 51 because no resource vcard could be found. The exception was: "Exception in thread "main" java.lang.NullPointerException". Adding the slash at the end fixes the issue because http://somewhere/JohnSmith/;>|http://somewhere/JohnSmith/%22%3E]| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (JENA-1538) Include TDB2 in jena-osgi module
[ https://issues.apache.org/jira/browse/JENA-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne reassigned JENA-1538: --- Assignee: Andy Seaborne > Include TDB2 in jena-osgi module > > > Key: JENA-1538 > URL: https://issues.apache.org/jira/browse/JENA-1538 > Project: Apache Jena > Issue Type: Improvement > Components: TDB2 >Affects Versions: Jena 3.7.0 >Reporter: Aaron Coburn >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 3.8.0 > > > The jena-tdb2 packages are not included in the jena-osgi module. Should they > be? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (JENA-1532) Jena Text Elastic Search Does not perform proper date comparison during query
[
https://issues.apache.org/jira/browse/JENA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne reassigned JENA-1532:
---
Assignee: Andy Seaborne
> Jena Text Elastic Search Does not perform proper date comparison during query
> -
>
> Key: JENA-1532
> URL: https://issues.apache.org/jira/browse/JENA-1532
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
>Affects Versions: Jena 3.7.0
>Reporter: Anuj Kumar
>Assignee: Andy Seaborne
>Priority: Major
>
> Jena Text Elastic Search is an implementation of the text query capability of
> Jena to perform text based searching and Filtering of data. It uses [Query
> String
> Query|https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html]
> capability of elastic search to perform searches.
> We found a bug in the implementation where searching on date values does not
> work properly. For example, if we have a following text query:
> {code:java}
> SELECT ?s { ?s text:query ('2016-12-01T15:31:10-05:00') ;{code}
> then the implementation threw exception because there are unescaped ":"
> (colon) in the value. Since ":" is a reserved character in the Query String
> Query capability of Elastic search, we have to escape the character.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
