Sep 18th, 2011, 10:39 PM
I have made some minor changes to improve the situation, but the general improvement to have Roo detect cyclic references has not been addressed. In fact it appears the community is not voting much on this issue (https://jira.springsource.org/browse/ROO-325). I think this can be resolved in many cases with a few minor tweaks by the developer rather than trying to automatically detect cyclic references in Roo.
Apr 28th, 2012, 05:43 PM
Hopefully this will clear things up a little (doesn't look to be related to cyclic references).
1) The hibernate behavior of many-to-many relationships only allows for changes to the relationship to be persisted from the controlling side (the non-mappedBy side).
2) Spring Roo currently allows the user to try and modify this relationship from either side via the UI (even though it is only successfully persisted from the controlling side).
Until Roo changes the UI for the non-controlling side, try this workaround -
Modify the non-controlling side's jspx pages to not allow for changing relationships in two pages:
* Edit create.jspx to remove the line for the controlling entity - or set render="false" (you can't persist it, so why show it?)
* Edit update.jspx to add disabled="true" to the line for the controlling entity (show the current relation, but don't allow for any changes - they won't persist anyways)
Last edited by chrisdowden; Apr 28th, 2012 at 05:50 PM.
Dec 20th, 2012, 10:24 AM
This post was really usefull , now I understand better how works the manytomany relationship