This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

Owned One-to-Many Relationships for GAE not supported by RooPage Title Module

Comment

It is very unclear for me HOW this problem has been solved in the latest release (1.1.1). Nothing in the JIRA ticket, nor in the different posts of this forum, nor in ANY document gives a clear guidance about how to proceed. The use of com.google.appengine.api.datastore.Key doesn't work.
Could you give any guidance/link about how to REALLY manage owned OneToMany relationships in GAE ?

Comment

I've dug into it and it seems there is a regression in 1.1.2.BUILD-SNAPSHOT [rev 6c006f1].
I tried with 1.1.1.RELEASE [rev 156ccd6] and I don't get the Long id error.
(but I do get the hardcoded Employee error )

@cyrille : unfortunately, it is said in the JIRA ticket that the chosen solution is to make all relationships unowned.

There is no easy work-around, since when you set an entity's id type to Long, it breaks the gae.encoded-pk requirement, and if you set the id type to String, you break other code that is expecting Long ids (such as *MobileListView.java's primaryRenderer)...