-
Notifications
You must be signed in to change notification settings - Fork 3
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
Several errors #3
Comments
Regarding the last points, the flow that you described is one correct flow, yes.
Otherwise, the SQL dump can be found here: https://zenodo.org/record/2652356 I don't recall ever encountering the Hibernate error you're describing, in my setup, I don't need the dependency you suggested. From my experience, this kind of errors is created either by a different Java version, either by the inability of Hibernate to find a connection to the database. I would be interested in seeing if adding this new dependency, you solved this problem. |
Alright, it was my understanding the databasefiller project was required aswell. I got it working now by adding the hibernate-validator dependency. What Java version do you compile with? I used OpenJDK 13. I believe the spring-boot-starter-data-jpa dependency default to the 6.1.2.Final version of the Hibernate validator which seems incompatible for the target Docker JVM? I'm not sure. |
That's the problem, Spring with Hibernate works well only with Java 8, it creates errors in my system with higher versions. |
When trying to start the project I run into several errors, among them are:
Steps to reproduce:
Docker containers start, web application results in error:
I believe youre missing this dependency:
Also the file inchiPet.jar is not build into the target directory (you copy it from the root of the project in the NPdatabaseFiller project). Therefor the docker container can not be build
In the readme the following line is mentioned:
In order to run the web application properly I assume the following steps must be performed:
Is this the correct flow?
The text was updated successfully, but these errors were encountered: