Hi Robert, > > Sorry, I forgot to add this: > > > dpkg -l | grep rhino > ii librhino-java 1.7.14-2 > ii rhino 1.7.14-2 > > I've upgraded (lib)rhino after reading the bug report but this did not help. > > Is there a way to debug Openrefine? I tried both -v debug and -v trace > but did not get more output (Maybe I have to configure log4j properly as > the warning suggests?)
I can't reproduce a 404 error at the moment. OpenRefine works as expected for me. Unfortunately it is not easy to debug openrefine because there is a separate Javascript based web application and the server module based on Java. The former can only be debugged via Chrome or Firefox console. I'm not sure how useful the log messages would be. I agree that there is currently a problem with configuring SLF4j and this is something which should work out-of-the-box. A 404 error indicates a web server (Jetty in this case) problem or a missing file but I don't know how this could help right now. Regards, Markus
signature.asc
Description: This is a digitally signed message part
__ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.
