[jira] [Commented] (JENA-1580) Provide a better message when the port for Fuseki basic is already in use.
[ https://issues.apache.org/jira/browse/JENA-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561155#comment-16561155 ] ASF GitHub Bot commented on JENA-1580: -- GitHub user afs opened a pull request: https://github.com/apache/jena/pull/452 JENA-1580: Better error message when port in use You can merge this pull request into a Git repository by running: $ git pull https://github.com/afs/jena fuseki-port Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/452.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #452 commit fab78b8fcda5372b202b9d0af387ec2fa862668e Author: Andy Seaborne Date: 2018-07-29T16:20:53Z JENA-1580: Better error message when port in use > Provide a better message when the port for Fuseki basic is already in use. > -- > > Key: JENA-1580 > URL: https://issues.apache.org/jira/browse/JENA-1580 > Project: Apache Jena > Issue Type: Improvement >Affects Versions: Jena 3.8.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (JENA-1580) Provide a better message when the port for Fuseki basic is already in use.
Andy Seaborne created JENA-1580: --- Summary: Provide a better message when the port for Fuseki basic is already in use. Key: JENA-1580 URL: https://issues.apache.org/jira/browse/JENA-1580 Project: Apache Jena Issue Type: Improvement Affects Versions: Jena 3.8.0 Reporter: Andy Seaborne Assignee: Andy Seaborne -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] jena pull request #452: JENA-1580: Better error message when port in use
GitHub user afs opened a pull request: https://github.com/apache/jena/pull/452 JENA-1580: Better error message when port in use You can merge this pull request into a Git repository by running: $ git pull https://github.com/afs/jena fuseki-port Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/452.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #452 commit fab78b8fcda5372b202b9d0af387ec2fa862668e Author: Andy Seaborne Date: 2018-07-29T16:20:53Z JENA-1580: Better error message when port in use ---
[jira] [Resolved] (JENA-1577) RIOT skips part of jsonld file (regression) and ignores @base
[
https://issues.apache.org/jira/browse/JENA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1577.
-
Resolution: Not A Problem
Assuming the discussion has resolved.
> RIOT skips part of jsonld file (regression) and ignores @base
> -
>
> Key: JENA-1577
> URL: https://issues.apache.org/jira/browse/JENA-1577
> Project: Apache Jena
> Issue Type: Bug
> Components: RIOT
>Reporter: Vladimir Alexiev
>Priority: Critical
>
> 1. RIOT ignores "base":
> {noformat}
> curl -s
> https://gist.githubusercontent.com/VladimirAlexiev/7b26962f9000a22fc25e8d180c716067/raw/7923f25be672294433dc95b48523573429781ecb/eg.jsonld|riot
> -syntax jsonld -formatted ttl
> ...
>
> a stix:attack-pattern ;
> ...
> {noformat}
> However, that jsonld includes base:
> {noformat}
> "@base": "http://attack.mitre.org/enterprise/;,
> {noformat}
> and the jsonld playground http://tinyurl.com/yd25vasq does take it into
> account: in n3 output see URLs like
> {noformat}
>
> {noformat}
> 2. Inexplicably, if I take the same jsonld content from a file, I get only
> triples rooted at blank nodes!
> This is a regression, it was not present in an older RIOT (I from a year ago,
> something like 3.1)
> {noformat}
> curl -s
> https://gist.githubusercontent.com/VladimirAlexiev/7b26962f9000a22fc25e8d180c716067/raw/7923f25be672294433dc95b48523573429781ecb/eg.jsonld>eg.jsonld
> riot -syntax jsonld -formatted ttl eg.jsonld
> ...
> [ stix:external_id "T1066" ;
> stix:source_name "mitre-attack" ;
> stix:url
> ] .
> {noformat}
> If I just add an input redirection to the command line (<), I see a lot more
> triples.
> {noformat}
> riot -syntax jsonld -formatted ttl < eg.jsonld
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (JENA-1577) RIOT skips part of jsonld file (regression) and ignores @base
[
https://issues.apache.org/jira/browse/JENA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-1577.
---
> RIOT skips part of jsonld file (regression) and ignores @base
> -
>
> Key: JENA-1577
> URL: https://issues.apache.org/jira/browse/JENA-1577
> Project: Apache Jena
> Issue Type: Bug
> Components: RIOT
>Reporter: Vladimir Alexiev
>Priority: Critical
>
> 1. RIOT ignores "base":
> {noformat}
> curl -s
> https://gist.githubusercontent.com/VladimirAlexiev/7b26962f9000a22fc25e8d180c716067/raw/7923f25be672294433dc95b48523573429781ecb/eg.jsonld|riot
> -syntax jsonld -formatted ttl
> ...
>
> a stix:attack-pattern ;
> ...
> {noformat}
> However, that jsonld includes base:
> {noformat}
> "@base": "http://attack.mitre.org/enterprise/;,
> {noformat}
> and the jsonld playground http://tinyurl.com/yd25vasq does take it into
> account: in n3 output see URLs like
> {noformat}
>
> {noformat}
> 2. Inexplicably, if I take the same jsonld content from a file, I get only
> triples rooted at blank nodes!
> This is a regression, it was not present in an older RIOT (I from a year ago,
> something like 3.1)
> {noformat}
> curl -s
> https://gist.githubusercontent.com/VladimirAlexiev/7b26962f9000a22fc25e8d180c716067/raw/7923f25be672294433dc95b48523573429781ecb/eg.jsonld>eg.jsonld
> riot -syntax jsonld -formatted ttl eg.jsonld
> ...
> [ stix:external_id "T1066" ;
> stix:source_name "mitre-attack" ;
> stix:url
> ] .
> {noformat}
> If I just add an input redirection to the command line (<), I see a lot more
> triples.
> {noformat}
> riot -syntax jsonld -formatted ttl < eg.jsonld
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (JENA-1576) Is it possible to create an index for predicates (properties) from other schemas besides rdf-syntax?
[
https://issues.apache.org/jira/browse/JENA-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-1576.
---
> Is it possible to create an index for predicates (properties) from other
> schemas besides rdf-syntax?
>
>
> Key: JENA-1576
> URL: https://issues.apache.org/jira/browse/JENA-1576
> Project: Apache Jena
> Issue Type: Question
>Reporter: Alysson Gomes de Sousa
>Priority: Major
>
> I'm trying to create a text search index for other predicates, as the example
> shows. Is it possible to create such an instance, or did I misunderstand?
> *Example:*
> {noformat}
> <#entMap> a text:EntityMap ;
>text:defaultField "first" ;
>text:entityField "uri" ;
>text:map ([
> text:field "first" ;
> text:predicate <[http://dbpedia.org/property/first]>
>]).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1576) Is it possible to create an index for predicates (properties) from other schemas besides rdf-syntax?
[
https://issues.apache.org/jira/browse/JENA-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1576.
-
Resolution: Information Provided
> Is it possible to create an index for predicates (properties) from other
> schemas besides rdf-syntax?
>
>
> Key: JENA-1576
> URL: https://issues.apache.org/jira/browse/JENA-1576
> Project: Apache Jena
> Issue Type: Question
>Reporter: Alysson Gomes de Sousa
>Priority: Major
>
> I'm trying to create a text search index for other predicates, as the example
> shows. Is it possible to create such an instance, or did I misunderstand?
> *Example:*
> {noformat}
> <#entMap> a text:EntityMap ;
>text:defaultField "first" ;
>text:entityField "uri" ;
>text:map ([
> text:field "first" ;
> text:predicate <[http://dbpedia.org/property/first]>
>]).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JENA-1579) NPE with xsd:QName validation.
[
https://issues.apache.org/jira/browse/JENA-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1579.
-
Resolution: Fixed
Fix Version/s: Jena 3.9.0
> NPE with xsd:QName validation.
> --
>
> Key: JENA-1579
> URL: https://issues.apache.org/jira/browse/JENA-1579
> Project: Apache Jena
> Issue Type: Bug
> Components: Datatypes
>Affects Versions: Jena 3.8.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: Jena 3.9.0
>
>
> The parse/value code for two XSD datatypes got damaged in the migration of
> Xerces datatype handling code.
> xsd:QName and xs:NOTATION
> Test case: this will print two stacktraces with Jena 3.8.0.
> {code:java}
> public static void main(String... args) {
> TypeMapper typeMapper = TypeMapper.getInstance();
> try {
> System.out.println("XSDDatatype.XSDQName");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDQName.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> try {
> System.out.println("XSDDatatype.XSDNOTATION");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDNOTATION.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JENA-1579) NPE with xsd:QName validation.
[
https://issues.apache.org/jira/browse/JENA-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561137#comment-16561137
]
ASF subversion and git services commented on JENA-1579:
---
Commit bbe1123952bd58d3ac5083d504f84cfd9103a431 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=bbe1123 ]
JENA-1579: Merge commit 'refs/pull/450/head' of https://github.com/apache/jena
This closes #450.
> NPE with xsd:QName validation.
> --
>
> Key: JENA-1579
> URL: https://issues.apache.org/jira/browse/JENA-1579
> Project: Apache Jena
> Issue Type: Bug
> Components: Datatypes
>Affects Versions: Jena 3.8.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> The parse/value code for two XSD datatypes got damaged in the migration of
> Xerces datatype handling code.
> xsd:QName and xs:NOTATION
> Test case: this will print two stacktraces with Jena 3.8.0.
> {code:java}
> public static void main(String... args) {
> TypeMapper typeMapper = TypeMapper.getInstance();
> try {
> System.out.println("XSDDatatype.XSDQName");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDQName.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> try {
> System.out.println("XSDDatatype.XSDNOTATION");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDNOTATION.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] jena pull request #450: JENA-1579: Add Xerces code for xsd:QName, also used ...
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/450 ---
[jira] [Commented] (JENA-1579) NPE with xsd:QName validation.
[
https://issues.apache.org/jira/browse/JENA-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561136#comment-16561136
]
ASF subversion and git services commented on JENA-1579:
---
Commit c724aa89a264d1fcfa416499099657f79f38b8e4 in jena's branch
refs/heads/master from [~an...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c724aa8 ]
JENA-1579: Add Xerces code for xsd:QName, also used for xsd:NOTATION.
> NPE with xsd:QName validation.
> --
>
> Key: JENA-1579
> URL: https://issues.apache.org/jira/browse/JENA-1579
> Project: Apache Jena
> Issue Type: Bug
> Components: Datatypes
>Affects Versions: Jena 3.8.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> The parse/value code for two XSD datatypes got damaged in the migration of
> Xerces datatype handling code.
> xsd:QName and xs:NOTATION
> Test case: this will print two stacktraces with Jena 3.8.0.
> {code:java}
> public static void main(String... args) {
> TypeMapper typeMapper = TypeMapper.getInstance();
> try {
> System.out.println("XSDDatatype.XSDQName");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDQName.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> try {
> System.out.println("XSDDatatype.XSDNOTATION");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDNOTATION.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] jena pull request #451: Deprecate low level non-application operations
Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/451 ---
[jira] [Commented] (JENA-1579) NPE with xsd:QName validation.
[
https://issues.apache.org/jira/browse/JENA-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561138#comment-16561138
]
ASF GitHub Bot commented on JENA-1579:
--
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/450
> NPE with xsd:QName validation.
> --
>
> Key: JENA-1579
> URL: https://issues.apache.org/jira/browse/JENA-1579
> Project: Apache Jena
> Issue Type: Bug
> Components: Datatypes
>Affects Versions: Jena 3.8.0
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> The parse/value code for two XSD datatypes got damaged in the migration of
> Xerces datatype handling code.
> xsd:QName and xs:NOTATION
> Test case: this will print two stacktraces with Jena 3.8.0.
> {code:java}
> public static void main(String... args) {
> TypeMapper typeMapper = TypeMapper.getInstance();
> try {
> System.out.println("XSDDatatype.XSDQName");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDQName.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> try {
> System.out.println("XSDDatatype.XSDNOTATION");
> RDFDatatype datatype =
> typeMapper.getTypeByName(XSDDatatype.XSDNOTATION.getURI());
> datatype.isValid("foo");
> System.out.println("... OK");
> } catch (NullPointerException ex) {
> ex.printStackTrace(System.out);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
