I was able to use M-N relationship in 1.5.3, although it did create 2 different tables and did not act as expected. But, I was able to have it working. With this version (1.5.4) it does not work, period. So, I cannot really move onto the 1.5.4 version until this problem is fixed.
-AP_ http://www.alexparansky.com Java/J2EE Architect/Consultant -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ray Harrison Sent: Saturday, February 16, 2002 5:10 PM To: Orion-Interest Subject: RE: Orion 1.5.4 - M-N Relationship chokes (?) I think 1.5.4 has enough stable changes in it to move forward (I was particularly interested in the JMS changes and a few other items), and the 1-N relationships still seem to work, but I would like to know how they tested the N-M feature. I used local interfaces, and ejb2.0 style CMP/R. Ray --- Alex Paransky <[EMAIL PROTECTED]> wrote: > I got the same result. At first, I thought it had something to do with the > fact that I was still using non Local interfaces (since 1.5.3 does not have > support for Local interfaces yet), however, trying a small example returned > the same exception. I am not sure how these guys tested their N-M > relationship support, but it does not appear to be working as of yet. > > For now, I am sticking with 1.5.3. > > -AP_ > http://www.alexparansky.com > Java/J2EE Architect/Consultant > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Phillip Ross > Sent: Friday, February 15, 2002 9:25 PM > To: Orion-Interest > Subject: Re: Orion 1.5.4 - M-N Relationship chokes (?) > > > Yeah i get the same thing... was wondering if i was just doing something > wrong. > > I'll send an update when i get it working. > > > --- Ray Harrison <[EMAIL PROTECTED]> wrote: > > Resend - it didn't post the first > > > time:----------------------------------------------------------------------- > ----------------- > > > -------------------------------------------------------------------------- -- > ------------------- > > > > Hello - > > For the hell of it I decided to test M-N relationships in the latest > release > > of Orion (1.5.4). I > > started by trying to work with some of Monson-Haefel's examples - the > result > > was the same as that > > below. To simplify it, I just created a couple of test entities, each with > a > > collection based > > reference to the other entity. Using local interfaces. The 1-N > relationships > > seem to work just > > fine. I am wondering if I am missing something in the M-N relationship > > construction. > > > > otest1Local: > > // Collection ref to otest2 > > public Collection getOtest2s( ); > > public void setOtest2s(Collection otest2s); > > > > otest1EJB: > > > > // abstract methods > > public abstract Collection getOtest2s( ); > > public abstract void setOtest2s(Collection otest2s); > > > > There is a similar setup for the other entity. The relationship references > > are (from ejb-jar.xml): > > > > > > <relationships> > > <ejb-relation> > > <ejb-relation-name>otest1-otest2</ejb-relation-name> > > <ejb-relationship-role> > > <ejb-relationship-role-name> > > otest1-has-many-otest2 > > </ejb-relationship-role-name> > > <multiplicity>Many</multiplicity> > > <relationship-role-source> > > <ejb-name>otest1</ejb-name> > > </relationship-role-source> > > <cmr-field> > > <cmr-field-name>otest2s</cmr-field-name> > > <cmr-field-type>java.util.Collection</cmr-field-type> > > </cmr-field> > > </ejb-relationship-role> > > > > <ejb-relationship-role> > > <ejb-relationship-role-name> > > otest2-has-many-otest1 > > </ejb-relationship-role-name> > > <multiplicity>Many</multiplicity> > > <relationship-role-source> > > <ejb-name>otest2</ejb-name> > > </relationship-role-source> > > <cmr-field> > > <cmr-field-name>otest1s</cmr-field-name> > > <cmr-field-type>java.util.Collection</cmr-field-type> > > </cmr-field> > > </ejb-relationship-role> > > </ejb-relation> > > </relationships> > > > > > > > > As I said earlier, the faithful 1-many relationships work. When changed to > an > > m-n relationship, as > > the entity jar is being deployed it comes back with the following: > > > > > > Auto-deploying testorion (New server version detected)... > > Auto-deploying server.jar (No previous deployment found)... > > java.lang.NullPointe > > rException > > at com.evermind._eh._hg(.:120) > > at com.evermind._eh._de(.:173) > > at com.evermind._ef._de(.:292) > > at com.evermind._em._nvc(.:395) > > at com.evermind._eq.<init>(.:63) > > at com.evermind._ed._aa(.:186) > > at com.evermind._ai._kmd(.:526) > > at com.evermind._aj._kmd(.:287) > > at com.evermind._aj._vxb(.:119) > > at com.evermind.server.ApplicationServer._sxc(.:1308) > > at com.evermind.server.ApplicationServer._ige(.:1265) > > at com.evermind.server.ApplicationServer._vxb(.:1003) > > at com.evermind._cxb.run(.:89) > > at java.lang.Thread.run(Thread.java:536) > > at com.evermind._bt.run(.:47) > > > > > > ===================================== > > and then doesn't deploy of course. Before I submit a bug for this - did I > > miss something somewhere > > or is this legit? > > > > Cheers! > > Ray > > > > __________________________________________________ > > Do You Yahoo!? > > Yahoo! Sports - Coverage of the 2002 Olympic Games > > http://sports.yahoo.com > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Sports - Coverage of the 2002 Olympic Games > http://sports.yahoo.com > > > __________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com
