Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Owned One-to-Many Relationships for GAE not supported by Roo

  1. Mar 3rd, 2011, 03:55 PM #11
    dd_angel
    dd_angel is offline Junior Member
    Join Date
    Feb 2011
    Posts
    8

    Default

    Well, for me, i'll wait until a stable version of spring roo will be avalaible.
    Here, it would seem it's in beta version yet with these recurrent errors for relation many to one (or many)...
    Reply With Quote Reply With Quote
  2. Mar 7th, 2011, 02:24 PM #12
    mrsvan
    mrsvan is offline Junior Member
    Join Date
    Sep 2010
    Posts
    3

    Default

    Roo 1.1.2 release is out, and there are still problems with One-to-Many relationships for GAE...

    I have opened a bug in Jira: https://jira.springsource.org/browse/ROO-2211

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

    :-(
    Last edited by mrsvan; Mar 7th, 2011 at 02:46 PM.
    Reply With Quote Reply With Quote
  3. Mar 8th, 2011, 03:12 PM #13
    fawzyj
    fawzyj is offline Senior Member
    Join Date
    May 2008
    Posts
    227

    Default

    this is related to a GAE limitation as it require encoded string for any serious entity relationship
    so ROO have to change the assumption that the primary key (ID field) is of type Long

    Joe
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules