New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem on a new install on windows #186
Comments
Yes, this is a problem of running on a completely empty database (see below). For the immediate problem,
Populating the base, see For the encoding problem in the web page , this seems related to running on windows. The I18N files are in UTF-8 . We will investigate this . |
leverage on the auto-load capability of semantic_forms : click on the form specification ( forms#loginForm )
click on the class appearing there (forms.owl.ttl#specification )
|
Normally you should have this : forms.owl.ttl#specification RDF Resource Description Framework Flyer Icon forms.owl.ttl#specification, at URI http://raw.githubusercontent.com/jmvanel/semantic_forms/master/vocabulary/forms.owl.ttl#specification Have you retried login ? |
After populating the base, it works better, but it doesn't work |
Sorry, I just tested with the release zip, FYI, the issue here was that this URI for form spec. is not downloabable : So, after running And then , doing "Create an account" worked fine ( on Ubuntu ! ), However, there seems again to be a Windows specific issue :( . |
Not very nice. I just discover that the password I give when creating an accound is clearly visible in the traces (and, I suppose, in the log!!!) |
The end of the traces when creating an account and/or trying to log in |
Of course , logging of password will be removed. For the login failure, So, I added more login for everything that could possibly fail. Can you confirm that you get a 400 Bad Request ? Many thanks for you report and patience. |
I have no log file. here is a opy of a trace when starting SF and then trying to authenticate as admin As you can see at the begining, we have and near the end we have |
"Illegal reflective access "This is a recent report from october: I guess you use Java 9 too ? ERROR StatusLoggerERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. This is a unpleasing message, but it's not a problem. Message 404 HTTPrequest GET http://raw.githubusercontent.com/jmvanel/semantic_forms/master/vocabulary/forms#registerForm Again, this is a unpleasing message, but it's not a problem. |
yes for Java 9: I use it |
So we tested on Windows (with Java 8 update 151), We first ran populateRDFCache.sh , as indicated in the doc. I think that the workaround that I gave whithout running populateRDFCache.sh may be problematic, P.S. I restructured the wiki today https://github.com/jmvanel/semantic_forms/wiki . |
Removing TDB, TDB2, TDB3 |
Black to initial problem ! The only way I see to reproduce the issue is to use also Java 9 on windows. Tomorrow we will try also Java 9 on windows. |
1 similar comment
Black to initial problem ! The only way I see to reproduce the issue is to use also Java 9 on windows. Tomorrow we will try also Java 9 on windows. |
So, we tried with Java 9 from sources, with the build tool SBT. Then I saw that Java 9 support for Scala itself is not effective yet ! _A summary page on "scala java 9 support": https://www.reddit.com/r/scala/comments/78u6xk/is_scala_ready_for_java_9/ The Scala issue is still open: scala/scala-dev#139 So SBT, Play, and SF can not work! We know, according to Andy, that Jena is walking in pure Java 9. I just have to remove the log of the passwords , |
So Java 9 is an issue for Scala and SBT and PLay , not SF . |
I've just installed the last released on a windows 10
I run the application and go to localhost:9000
then I attemps to create an instance of http://schema.org/Museum or of a foaf:Person
and it get always the same form (see joined image)
It seems similar to a old problem I had; it was something about a problem accessing a file necessary to generate the form or something about populating the base, I don't remember very well
(note that some chars are badly rendered, without the good chars family)
The text was updated successfully, but these errors were encountered: