ng-annotations | angular wrapper based on annotations | Frontend Framework library

Without knowing much about the libraries you are using I can see you are creating these annotation objects and then assigning them to a global variable that is re-assigned later and thus you lose the right object to make it visible.

Instead you could keep the annotation objects into a dictionary and try to retrieve them later when you need them based on an object.

I used a list to show you the idea, but you need a dictionary I guess to identify the right objects.

I modified your code a bit and it shows the desired behaviour if you resize the window...I guess you have to find a way to refresh the plot also:

I fixed this by changing

Declare a response outside of an operation:

Indeed you have a clash in RestEasy (transitive) dependencies in your project:

Could you try with a clean ~/.m2/repository/ (just move yours away before trying)?

did you check the existence of AnnotationManager in your vendor? It should be under vendor/laminas/laminas-code/src/Annotation/AnnotationManager.php

Like you can see, it's located in a seperate package called laminas/laminas-code. Depending on your composer require statements it is not loaded by default.

Do you have any output with composer why laminas/laminas-code

This error popped up because, the only_move you have provided is a string, but it expects a dictionary. In the last line of your error screenshot you can see only_move.values(), from where the error pops up. PFB example:

Short answer:

you should divide your many to many association to two many to one association and use @Embedded annotation to define compound key for your intermediate entity look at below link for detail

https://vladmihalcea.com/the-best-way-to-map-a-many-to-many-association-with-extra-columns-when-using-jpa-and-hibernate/

Long answer:

Actually when you use @ManyToMany annotation to establish many to many association in hibernate it creates another table to establish ManyToMany association behind the scene this table is defined with @JoinTable annotation in your code, query to that table is completely managed by hibernate to achieve many to many association and you don't have entity which is mapped to that table. It is fine unless you need extra column in your intermediate table(here STUDENT_COURSE) or you want to execute some specific query to that table in a way that you behave with your other entity and you want to access the Id of your Course and Student table in CourseStudent table. because when hibernate creates intermediate table behind the scene you don't have entity in your program that maps to that table and therefore you can't have other column for that table and you can't behave to that table as an entity in your program. if you need extra column you can divide your @ManyToMany association to two @ManyToOne association. Here you should have another entity with name StudentCourse which has two @ManyToOne association one to Student entity and the other one to Course entity. However when you are defining your many to many association this way you should consider data integriry for instance the combination of student_id and course_id in your student_course table is unique and actually it should be a compound key in your student_course table. Fortunately there are some annotations in hibernate and jpa that provide this capability. Writing all the code for this sitiuation in this answer is redundant because there is already a good example in the link below .

https://vladmihalcea.com/the-best-way-to-map-a-many-to-many-association-with-extra-columns-when-using-jpa-and-hibernate/