[jira] Commented: (GERONIMO-827) Change CMR mapping name elements to descriptions
[ http://issues.apache.org/jira/browse/GERONIMO-827?page=comments#action_12317104 ] Jeremy Boynes commented on GERONIMO-827: EJB supports non-navigable relationships that still require management by the container. These need to be mapped somehow and naming the relationship is one way of identifying them (the ID attribute is another). If we don't support these there is a bug in OpenEJB's mapping capabilities. Here's a somewhat contrived example: One Person Many Person One Person Many Person > Change CMR mapping name elements to descriptions > > > Key: GERONIMO-827 > URL: http://issues.apache.org/jira/browse/GERONIMO-827 > Project: Geronimo > Type: Improvement > Components: OpenEJB > Versions: 1.0-M4 > Reporter: Aaron Mulder > Fix For: 1.0-M5 > > Change the ejb-relation-name and ejb-relationship-role-name elements in > openejb-jar.xml at: > openejb-jar/relationships/ejb-relation/ejb-relation-name > openejb-jar/relationships/ejb-relation/ejb-relationship-role/ejb-relationship-role-name > To be description elements instead, since they're not actually used by the > server and are for documentation purposes only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-827) Change CMR mapping name elements to descriptions
[ http://issues.apache.org/jira/browse/GERONIMO-827?page=comments#action_12317107 ] Aaron Mulder commented on GERONIMO-827: --- I agree that your conclusion follows your premise. But I'm not sure I agree with the premise. Do you have a spec reference that indicates that entirely non-navigable relationships should be supported? Thanks, Aaron > Change CMR mapping name elements to descriptions > > > Key: GERONIMO-827 > URL: http://issues.apache.org/jira/browse/GERONIMO-827 > Project: Geronimo > Type: Improvement > Components: OpenEJB > Versions: 1.0-M4 > Reporter: Aaron Mulder > Fix For: 1.0-M5 > > Change the ejb-relation-name and ejb-relationship-role-name elements in > openejb-jar.xml at: > openejb-jar/relationships/ejb-relation/ejb-relation-name > openejb-jar/relationships/ejb-relation/ejb-relationship-role/ejb-relationship-role-name > To be description elements instead, since they're not actually used by the > server and are for documentation purposes only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-827) Change CMR mapping name elements to descriptions
[ http://issues.apache.org/jira/browse/GERONIMO-827?page=comments#action_12317112 ] Jeremy Boynes commented on GERONIMO-827: Do you have one that says they don't? The definition is valid and has semantic meaning (cascade-delete); we should either comply with the definition or reject the application. The name elements are not purely documentation - there are actually elements built into the schema for all these elements that can be used for that. The schema has a unique constraint on the relation name to ensure there are no duplicates, the purpose of which is to allow mapping tools to clearly identify them. > Change CMR mapping name elements to descriptions > > > Key: GERONIMO-827 > URL: http://issues.apache.org/jira/browse/GERONIMO-827 > Project: Geronimo > Type: Improvement > Components: OpenEJB > Versions: 1.0-M4 > Reporter: Aaron Mulder > Fix For: 1.0-M5 > > Change the ejb-relation-name and ejb-relationship-role-name elements in > openejb-jar.xml at: > openejb-jar/relationships/ejb-relation/ejb-relation-name > openejb-jar/relationships/ejb-relation/ejb-relationship-role/ejb-relationship-role-name > To be description elements instead, since they're not actually used by the > server and are for documentation purposes only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-827) Change CMR mapping name elements to descriptions
[ http://issues.apache.org/jira/browse/GERONIMO-827?page=comments#action_12317151 ] Gianny Damour commented on GERONIMO-827: Now, I see the purpose of these two optional elements. I knew that unique constraints were defined on them; yet I did not envisage that they were used for non-navigable relationships. I do not know if a lot of people are using this mechanism; yet, it seems fair to enhance our code to support this case. > Change CMR mapping name elements to descriptions > > > Key: GERONIMO-827 > URL: http://issues.apache.org/jira/browse/GERONIMO-827 > Project: Geronimo > Type: Improvement > Components: OpenEJB > Versions: 1.0-M4 > Reporter: Aaron Mulder > Fix For: 1.0-M5 > > Change the ejb-relation-name and ejb-relationship-role-name elements in > openejb-jar.xml at: > openejb-jar/relationships/ejb-relation/ejb-relation-name > openejb-jar/relationships/ejb-relation/ejb-relationship-role/ejb-relationship-role-name > To be description elements instead, since they're not actually used by the > server and are for documentation purposes only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
