Skip to content
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

Demo Fails - "No enum constant knox.spring.data.neo4j.domain.Edge.Orientation.inline" #19

Open
Zackhardtoname opened this issue Jul 5, 2019 · 2 comments · May be fixed by #20
Open

Comments

@Zackhardtoname
Copy link

Windows 10
Steps to reproduce

  1. Download & Install Neo4j Browser
  2. Follow the same steps in README - Quickstart (except running KnoxApplication.java from IntelliJ)
  3. Run step 10 in Quickstart and it fails on joining test 1 with test 2, outputting the following errors in the console

`2019-07-05 13:59:50.619 ERROR 21664 --- [nio-8080-exec-6] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.dao.InvalidDataAccessApiUsageException: Error mapping GraphModel to instance of knox.spring.data.neo4j.domain.DesignSpace; nested exception is org.neo4j.ogm.exception.MappingException: Error mapping GraphModel to instance of knox.spring.data.neo4j.domain.DesignSpace] with root cause

java.lang.IllegalArgumentException: No enum constant knox.spring.data.neo4j.domain.Edge.Orientation.inline`

On the webpage:
image

Zackhardtoname added a commit to hicsail/knox that referenced this issue Jul 26, 2019
@Zackhardtoname Zackhardtoname linked a pull request Jul 26, 2019 that will close this issue
@dany-fu
Copy link
Collaborator

dany-fu commented Jul 31, 2019

Is this bug only in the demo files? I recall you had another example where this occurred?

@Zackhardtoname
Copy link
Author

Yes. They are all in the demo files. Since all the "orientation" property in neo4j had been in lower case, none of the operators would work. So it was really just one bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants