Community
Participate
Working Groups
The only way I could think of to set a ManyToMany to read-only is to set insertable/writeable to false on the joinTable's join columns. These tags are ignored though on ManyToMany's. This means the only way to set a M:M as read-only is to used the mapped by, so only one side of a bidirectional M:M can be set as read-only. Either we need a new way to specify a ManyToMany is read-only, or the insertable/writable flag should be taken into account when building the mappings from orm.xml.
I put this as blocking 200040 since it was found in relation to work done on it, but it probably should be handled as a separate bug with a different priority.
Updating priority due to revised bug categorization process. See the following page for details: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines#Priority_and_Target_Milestone If you feel the updated priority is incorrect, please send an email to eclipselink-users@eclipse.org.
See Bug 280436 for a fix that could be adapted to fix this issue
This needs to be reverified
Removing from blocks 227219 as this bug is outside the scope of that bug.
This is still valid as there is no current way to specify that the relation table is read-only from this ManyToMany mapping without using the mappedby field. The mappedby requires that the other side also have a ManyToMany that is writable which may not be the case. This is a feature request to get a Unidirectional M:M read only support accessable through eclipselink orm.xml and/or annotations.
2.1 Bug scrubbing, deferring to 2.1.1.
I should not ave oved this to 2.1.1, as no schema changes are to be made. 2.2.0
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink