Hi, I have a similar issue with 1.3.0 however it arises when the types are the same and not related to inheritance of any type.
The work around suggested doesn't seem to work. Is the workaround valid for 1.3.0? thx, Conor On Dec 4 2009, 9:52 pm, "Max Ross (Google)" <maxr [email protected]> wrote: > SDK 1.2.8 contains a new check that detects if one of your JDO or JPA model > objects has two relationship fields of the same type. For example: > > class A { > List<B> bList; > List<B> anotherBList; > > } > > Unfortunately I was a little too aggressive with this check, so the > following also run afoul of the check: > > abstract class B {} > > class C extends B {} > class D extends B {} > > class A { > List<C> cList: > List<D> dList; > > } > > If you get an exception that says > > Class XXX has multiple relationship fields of type YYYY. This is not yet > supported. > > and your class hierarchy resembles the one above, you can disable this check > by with the following config property: > > <property name="datanucleus.appengine.multipleRelationsOfSameTypeAreErrors" > value="true"/> > > We'll get this fixed shortly. > > Sorry for the trouble, > Max
-- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
