-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Javers ReflectionUtils #860
Comments
Pleaae folow Guidelines for Bug Reporting and it would be nice if you disclose your name |
14327319
pushed a commit
to 14327319/javers
that referenced
this issue
Jul 17, 2019
14327319
pushed a commit
to 14327319/javers
that referenced
this issue
Jul 17, 2019
bartoszwalacik
added a commit
that referenced
this issue
Jul 22, 2019
bartoszwalacik
added a commit
that referenced
this issue
Jul 31, 2019
bartoszwalacik
added a commit
that referenced
this issue
Aug 1, 2019
fixed in 5.6.3 |
chioai1309
pushed a commit
to chioai1309/javers
that referenced
this issue
Sep 1, 2019
…ertiesProvider.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am using Javers with Spring Boot. I got this exception during my code execution:
Basically, I am trying to inspect data repository using @JaversSpringDataAuditable tag and I encountered with this error during this process.
As far as I inspected the Javers source code, interfaces and concrete classes are extracted in ReflectionUtil.calculateHierarchyDistance function for a given custom class and these are given to ManagedType as properties. Then, later, this information becomes a part of a node in the generated LiveGraph.
However, for me, createSnapshotState function checks properties and previously extracted interface and class types causes the exception above.
My main question is, does Javers handle interfaces along with class hierarchy for a given class for this situation and am I doing something wrong? Could you please suggest me a way to overcome this issue?
(I can provide more information if desired)
The text was updated successfully, but these errors were encountered: