Hi Christopher,
I think I've got it now. My apologies, the first time I was using a
local OWLIM repository and not deploying to Tomcat.
However, now that I have done this I can reproduce your problem.
Furthermore, the problem also occurs when using a remote Sesame
in-memory repository, so this leads me to believe that there is a bug in
Sesame's HTTP Client/Server code.
I hope you don't mind, but I have created an issue in the Sesame JIRA
project:
http://www.openrdf.org/issues/browse/SES-995
and added your source code to demonstrate the problem. Jeen is usually
quite quick to respond to issues, but we can discuss further if this is
a blocker issue for you.
Best,
barry
On 12/05/12 21:49, Lott, Christopher M wrote:
I'm just baffled that my test program fails for me but works for you. I dug
out a bit more version info: I've deployed Owlim into Apache Tomcat version
6.0.35 (completely unmodified, just unpacked the downloaded tar.gz file). The
machine has a slightly old java 6, here are the details:
$ java -version
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.7) (rhel-1.39.1.9.7.el6-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
_______________________________________________
Owlim-discussion mailing list
[email protected]
http://ontomail.semdata.org/cgi-bin/mailman/listinfo/owlim-discussion