You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2016/10/07 08:28:46 UTC
jena-persmissions updating
(Subject line changed to reflect the chnage of focus.)
On 07/10/16 01:40, Claude Warren wrote:
> While adding tests for the new Permissions methods I found that the Model
> read test was failing.
>
> I get
>
> org.apache.jena.riot.RiotNotFoundException: Not found:
> file:///home/claude/apache/jena/jena-permissions/jar:file:/home/claude/.m2/repository/org/apache/jena/jena-core/3.1.1-SNAPSHOT/jena-core-3.1.1-SNAPSHOT-tests.jar!/modelReading/based.n3
It looks like it is trying to read out of a jar.
> Anybody have any idea why it would be failing now and what I might need to
> do to get it to work again. I think this problem is outside of the
> permissions layer and back in the riot initialization code.
Do the jena-core tests run properly?
Try "mvn clean install -Pdev" at the top level.
jena-core and jena-permissions tests work for me using the code from
git, and both the Jenkins jobs are working.
How are you running the tests?
I also tried running the jena-core TestModelRead suite own its own and
testSimpleLoadImplictBase on it's own. I ran jena-pemissions tests from
Eclipse and from maven directly.
Andy
>
> Thx,
> Claude
>
>
>
> On Thu, Oct 6, 2016 at 10:35 PM, Andy Seaborne (JIRA) <ji...@apache.org>
> wrote:
>
>>
>> [ https://issues.apache.org/jira/browse/JENA-1238?page=
>> com.atlassian.jira.plugin.system.issuetabpanels:comment-
>> tabpanel&focusedCommentId=15553252#comment-15553252 ]
>>
>> Andy Seaborne commented on JENA-1238:
>> -------------------------------------
>>
>> An object with a language tag is a literal. It can't be a ResourceValue.
>>
>>> Add methods on Resource class that look for Properties in a specific
>> language
>>> ------------------------------------------------------------
>> -----------------
>>>
>>> Key: JENA-1238
>>> URL: https://issues.apache.org/jira/browse/JENA-1238
>>> Project: Apache Jena
>>> Issue Type: Improvement
>>> Components: Core
>>> Affects Versions: Jena 3.1.0
>>> Reporter: Ramiro Pereira de Magalh�es
>>> Assignee: Claude Warren
>>> Fix For: Jena 3.1.1
>>>
>>>
>>> It would be very convenient to have in the {{org.apache.jena.rdf.model.Resource}}
>> interface methods such as:
>>> {code}
>>> public Statement getProperty( Property p, String lang );
>>> public Statement getRequiredProperty( Property p, String lang );
>>> {code}
>>> They'd work like very much like {{org.apache.jena.rdf.model.
>> ModelCon.listStatements(Resource, Property, String, String)}}.
>>> This would simplify queries to a Resource's language-specific properties.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>
>
>
Re: jena-persmissions updating
Posted by Claude Warren <cl...@xenei.com>.
I was running from eclipse in the jena-permissions project.
good catch on the running from jar (01:40 is way to late to try to diagnose
these issues) ;) I think that points me in the correct direction.
I should have new code checked in sometime tonight.
Claude
On Fri, Oct 7, 2016 at 9:28 AM, Andy Seaborne <an...@apache.org> wrote:
> (Subject line changed to reflect the chnage of focus.)
>
> On 07/10/16 01:40, Claude Warren wrote:
>
>> While adding tests for the new Permissions methods I found that the Model
>> read test was failing.
>>
>> I get
>>
>> org.apache.jena.riot.RiotNotFoundException: Not found:
>> file:///home/claude/apache/jena/jena-permissions/jar:file:/
>> home/claude/.m2/repository/org/apache/jena/jena-core/3.1.
>> 1-SNAPSHOT/jena-core-3.1.1-SNAPSHOT-tests.jar!/modelReading/based.n3
>>
>
> It looks like it is trying to read out of a jar.
>
> Anybody have any idea why it would be failing now and what I might need to
>> do to get it to work again. I think this problem is outside of the
>> permissions layer and back in the riot initialization code.
>>
>
>
> Do the jena-core tests run properly?
>
> Try "mvn clean install -Pdev" at the top level.
>
> jena-core and jena-permissions tests work for me using the code from git,
> and both the Jenkins jobs are working.
>
> How are you running the tests?
>
> I also tried running the jena-core TestModelRead suite own its own and
> testSimpleLoadImplictBase on it's own. I ran jena-pemissions tests from
> Eclipse and from maven directly.
>
> Andy
>
>
>> Thx,
>> Claude
>>
>>
>>
>> On Thu, Oct 6, 2016 at 10:35 PM, Andy Seaborne (JIRA) <ji...@apache.org>
>> wrote:
>>
>>
>>> [ https://issues.apache.org/jira/browse/JENA-1238?page=
>>> com.atlassian.jira.plugin.system.issuetabpanels:comment-
>>> tabpanel&focusedCommentId=15553252#comment-15553252 ]
>>>
>>> Andy Seaborne commented on JENA-1238:
>>> -------------------------------------
>>>
>>> An object with a language tag is a literal. It can't be a ResourceValue.
>>>
>>> Add methods on Resource class that look for Properties in a specific
>>>>
>>> language
>>>
>>>> ------------------------------------------------------------
>>>>
>>> -----------------
>>>
>>>>
>>>> Key: JENA-1238
>>>> URL: https://issues.apache.org/jira/browse/JENA-1238
>>>> Project: Apache Jena
>>>> Issue Type: Improvement
>>>> Components: Core
>>>> Affects Versions: Jena 3.1.0
>>>> Reporter: Ramiro Pereira de Magalhães
>>>> Assignee: Claude Warren
>>>> Fix For: Jena 3.1.1
>>>>
>>>>
>>>> It would be very convenient to have in the {{
>>>> org.apache.jena.rdf.model.Resource}}
>>>>
>>> interface methods such as:
>>>
>>>> {code}
>>>> public Statement getProperty( Property p, String lang );
>>>> public Statement getRequiredProperty( Property p, String lang );
>>>> {code}
>>>> They'd work like very much like {{org.apache.jena.rdf.model.
>>>>
>>> ModelCon.listStatements(Resource, Property, String, String)}}.
>>>
>>>> This would simplify queries to a Resource's language-specific
>>>> properties.
>>>>
>>>
>>>
>>>
>>> --
>>> This message was sent by Atlassian JIRA
>>> (v6.3.4#6332)
>>>
>>>
>>
>>
>>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: jena-persmissions updating
Posted by Andy Seaborne <an...@apache.org>.
On 07/10/16 09:28, Andy Seaborne wrote:
> (Subject line changed to reflect the chnage of focus.)
>
> On 07/10/16 01:40, Claude Warren wrote:
>> While adding tests for the new Permissions methods I found that the Model
>> read test was failing.
>>
>> I get
>>
>> org.apache.jena.riot.RiotNotFoundException: Not found:
>> file:///home/claude/apache/jena/jena-permissions/jar:file:/home/claude/.m2/repository/org/apache/jena/jena-core/3.1.1-SNAPSHOT/jena-core-3.1.1-SNAPSHOT-tests.jar!/modelReading/based.n3
>>
>
> It looks like it is trying to read out of a jar.
No - that long string is the file name passed in.
That is the "url" parameter to model.read at:
org.apache.jena.permissions.model.impl.SecuredModelImpl.read(SecuredModelImpl.java:1696)
except that line number is a long way (~300 lines) from any
SecuredModelImpl.read() code in the code in front of me.
>
>> Anybody have any idea why it would be failing now and what I might
>> need to
>> do to get it to work again. I think this problem is outside of the
>> permissions layer and back in the riot initialization code.
>
>
> Do the jena-core tests run properly?
>
> Try "mvn clean install -Pdev" at the top level.
>
> jena-core and jena-permissions tests work for me using the code from
> git, and both the Jenkins jobs are working.
>
> How are you running the tests?
>
> I also tried running the jena-core TestModelRead suite own its own and
> testSimpleLoadImplictBase on it's own. I ran jena-pemissions tests from
> Eclipse and from maven directly.
>
> Andy
>
>>
>> Thx,
>> Claude
>>
>>
>>
>> On Thu, Oct 6, 2016 at 10:35 PM, Andy Seaborne (JIRA) <ji...@apache.org>
>> wrote:
>>
>>>
>>> [ https://issues.apache.org/jira/browse/JENA-1238?page=
>>> com.atlassian.jira.plugin.system.issuetabpanels:comment-
>>> tabpanel&focusedCommentId=15553252#comment-15553252 ]
>>>
>>> Andy Seaborne commented on JENA-1238:
>>> -------------------------------------
>>>
>>> An object with a language tag is a literal. It can't be a ResourceValue.
>>>
>>>> Add methods on Resource class that look for Properties in a specific
>>> language
>>>> ------------------------------------------------------------
>>> -----------------
>>>>
>>>> Key: JENA-1238
>>>> URL: https://issues.apache.org/jira/browse/JENA-1238
>>>> Project: Apache Jena
>>>> Issue Type: Improvement
>>>> Components: Core
>>>> Affects Versions: Jena 3.1.0
>>>> Reporter: Ramiro Pereira de Magalh�es
>>>> Assignee: Claude Warren
>>>> Fix For: Jena 3.1.1
>>>>
>>>>
>>>> It would be very convenient to have in the
>>>> {{org.apache.jena.rdf.model.Resource}}
>>> interface methods such as:
>>>> {code}
>>>> public Statement getProperty( Property p, String lang );
>>>> public Statement getRequiredProperty( Property p, String lang );
>>>> {code}
>>>> They'd work like very much like {{org.apache.jena.rdf.model.
>>> ModelCon.listStatements(Resource, Property, String, String)}}.
>>>> This would simplify queries to a Resource's language-specific
>>>> properties.
>>>
>>>
>>>
>>> --
>>> This message was sent by Atlassian JIRA
>>> (v6.3.4#6332)
>>>
>>
>>
>>