The example in the docs uses the EmbeddedOnly annotation on the component class so perhaps give that a try. You should be able to embed more than one instance of the same class so this sounds like a bug. From the docs "If you have more than one field on the object whose type is an embedded class, you must rename the fields of one so they do not conflict with another."

http://code.google.com/appengine/docs/java/datastore/dataclasses.html#Embedded_Classes

So for the second class you need to specify field names manually for every field.

With Twig you can also embed collections of objects without any of that boiler plate config. http://code.google.com/p/twig-persist/

JD

On 19 Jan 2010, at 09:54, Nick Bonatsakis wrote:

Hi All,

I just updated to version 1.3.0 and I am now getting a runtime
datanucleus exception complaining about having two @Embedded fields of
the same type on an @Entity class. It seems like

Error message is:

"class has multiple relationship fields of type.  This is not yet
supported"

Should this really be happening, these are not @Entity objects, they
are @Embeddable and the fields are declared as @Embedded.

Thanks!
--
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 .



--
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.

Reply via email to