[ http://issues.apache.org/jira/browse/GERONIMO-1009?page=comments#action_12324518 ]
Gianny Damour commented on GERONIMO-1009: ----------------------------------------- This is a mapping problem. I attach an updated version of the DD. In a few words, only one <ejb-relationship-role> element must be specified for OTO and OTM relationships. I think that the implementation should be improved to detect when two <ejb-relationship-role> elements are specified for a OTO or OTM and warn that only one of them will be used. > CMR One-Many Primitive in Trade is not working correctly. > --------------------------------------------------------- > > Key: GERONIMO-1009 > URL: http://issues.apache.org/jira/browse/GERONIMO-1009 > Project: Geronimo > Type: Bug > Versions: 1.0-M5 > Environment: All > Reporter: Matt Hogstrom > Priority: Critical > Attachments: Table.ddl, dayTrader-plan.xml > > I have been testing Trade with Geronimo and had a problem with CMRs not > appearing to work correctly. I have forwarded the required into to Gianny to > re-create the problem. I got Trade Deployed on another non-WebSphere > AppServer today and confirmed that it is work there as well. > The steps to get Trade working are: > Create the Derby Database: > connect 'jdbc:derby://localhost:1527/tradedb;create=true'; > run 'Table.ddl'; > commit; > deploy the year dayTrader.ear with plan dayTeader-plan.xml > Go to configure and populate the database > Then Select Primitives and run the PingServlet2CMROne2Many -- 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
