[
https://issues.apache.org/jira/browse/JENA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-1607.
-
Resolution: Fixed
> Java util logging closes stdout or sterr if they are the output route.
>
[
https://issues.apache.org/jira/browse/JENA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627972#comment-16627972
]
ASF GitHub Bot commented on JENA-1607:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/472
---
[
https://issues.apache.org/jira/browse/JENA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627971#comment-16627971
]
ASF subversion and git services commented on JENA-1607:
---
Commit
[
https://issues.apache.org/jira/browse/JENA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627969#comment-16627969
]
ASF subversion and git services commented on JENA-1607:
---
Commit
On 25/09/18 12:35, Claude Warren wrote:
Adding the equals() and hashCode() overrides does not work as the code
calls Object.equals().
"the code" - where?
See LiteralLabelImpl.equals.
it calls Objects.equals (line ~375) so overrides work.
Objects.equals is the code:
public static boolean
Dave,
I figured this might be the case. Thus my "Don't Do That" note at the
beginning. Thx for the note.
I am beginning to suspect that they should be isomorphic but are not due to
historical development decisions.
Claude
On Tue, Sep 25, 2018 at 1:26 PM Dave Reynolds
wrote:
> It has been a
It has been a while since I had any involvement in this area of the code
and it may have all changed in the interim but ...
There used to be an assumption that data types are always registered and
that the same instance of a datatype object will be used by all literals
with that datatype. So
Adding the equals() and hashCode() overrides does not work as the code
calls Object.equals().
My base question is should the two literal nodes be considered "equal" for
isomorphic purposes?
In my test case I do the following:
1. register the datatype
2. create a model
3. add a the
On 25/09/18 09:48, Claude Warren wrote:
I have a case that I know falls under Don't Do That (DDT), but it got me
wondering.
Background:
We have created a custom data type that extends AdhocDatatype and provides
a data type for an enum. The parse() and unparse() methods work as
expected.
I
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/472
JENA-1607: Protect stdout, stderr from being closed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena logging-fix
Alternatively you can
[
https://issues.apache.org/jira/browse/JENA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627021#comment-16627021
]
ASF GitHub Bot commented on JENA-1607:
--
GitHub user afs opened a pull request:
I have a case that I know falls under Don't Do That (DDT), but it got me
wondering.
Background:
We have created a custom data type that extends AdhocDatatype and provides
a data type for an enum. The parse() and unparse() methods work as
expected.
I have a test case that managed to create 2
[
https://issues.apache.org/jira/browse/JENA-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16627016#comment-16627016
]
Andy Seaborne commented on JENA-1607:
-
Note: JUL initialization happens when the first logger is
Andy Seaborne created JENA-1607:
---
Summary: Java util logging closes stdout or sterr if they are the
output route.
Key: JENA-1607
URL: https://issues.apache.org/jira/browse/JENA-1607
Project: Apache
15 matches
Mail list logo