Whilst this issue is reported and possibly caused by Kryo I think it's my
understanding of how Jena is or is not serializing...
I'm using Jena 3.2.0-SNAPSHOT and Kryo(Net) to serialize Jena nodes but
Kryo baulks when asked to handle a (the) Node_ANY;
Exception in thread "Server"
Lorenz, question arises then how to cope with it?
On Fri, Jan 20, 2017 at 8:39 PM, Lorenz Buehmann <
buehm...@informatik.uni-leipzig.de> wrote:
> Rules do not replace values - that's the nature of Jena rules and also
> other rule languages like SWRL - called monotonicity.
>
> More is not to say.
Rules do not replace values - that's the nature of Jena rules and also
other rule languages like SWRL - called monotonicity.
More is not to say.
On 20.01.2017 17:29, tina sani wrote:
> I am asking why the Jena rules some times lead to duplicate values. By
> duplicate values, I mean it does not
See Stian's message.
On 20/01/17 13:54, Reihaneh Amini wrote:
Hi Osma,
Could you please help me more?
I load the data into an directory by TDB modeler and now I have 20-30 files
with .dat and .idn prefix.
Could you please help me out ? how can I load them into fuseki now?
I am asking why the Jena rules some times lead to duplicate values. By
duplicate values, I mean it does not over write the old values when certain
new values comes in.
I have a rule which says if an employee salary exceeds 10k usd, the emplyee
should be assigned to a Manager class else to
OK, so I will catch the train at station jena-3.1.2 :) .
2017-01-20 12:25 GMT+01:00 Andy Seaborne :
>
>
> On 20/01/17 08:33, Jean-Marc Vanel wrote:
>
>> Haaa, I got it !
>> jena-3.1.0 brings the exception, jena-3.1.1 does not .
>>
>
> I used the head of development.
>
> So
Hi Osma,
Could you please help me more?
I load the data into an directory by TDB modeler and now I have 20-30 files
with .dat and .idn prefix.
Could you please help me out ? how can I load them into fuseki now?
On 20/01/17 08:33, Jean-Marc Vanel wrote:
Haaa, I got it !
jena-3.1.0 brings the exception, jena-3.1.1 does not .
I used the head of development.
So whatever it is, it is working now.
Andy
cd ~/apps/apache-jena-3.1.0 ; JENA= ; for f in lib/*; do JENA=$JENA:$f;
done ; javac -cp $JENA
According to [1] the default RDF accept header in 3.1.0 and 3.1.1 is
text/turtle,application/n-triples;q=0.9,application/rdf+xml;q=0.7,
application/trig,application/n-quads;q=0.9,text/x-nquads;q=0.8,application/x-trig;q=0.7,application/ld+json;q=0.6,
*/*;q=0.5
that means Turtle is always the
I trusted so much Jena that I took for granted that no regression would
happen, but no software is without regression, and testing error catching
is of course the last thing people do, if ever !
So for my release of semantic_forms , I'll simply revert to 3.1.0 , with
priority to RDF/XML when
Ah sorry, right. I tried it with version 3.1.0.
I don't know which changes in the code lead to the different behavior.
Especially not that you get 0 triples in 3.1.1 which looks more like no
triple has to be parsed at all
> Haaa, I got it !
> jena-3.1.0 brings the exception, jena-3.1.1 does not
Haaa, I got it !
jena-3.1.0 brings the exception, jena-3.1.1 does not .
cd ~/apps/apache-jena-3.1.0 ; JENA= ; for f in lib/*; do JENA=$JENA:$f;
done ; javac -cp $JENA ReadMgr.java ; java -cp $JENA ReadMgr
log4j:WARN No appenders could be found for logger (Jena).
log4j:WARN Please initialize the
2017-01-19 22:26 GMT+01:00 Andy Seaborne :
> I get the parse error message with that code.
>
This is strange. I can't think of a reason for this difference in
execution. My impression is that the exceptions worked some weeks or a few
months ago. And what has changed since is the
13 matches
Mail list logo