I was thinking it was some artifact from previous changes to files, but it’s persistent and won’t leave after reopenings the file. I use Netbeans 6.9 and Grails 1.3.3.

I have also next question – I need to make adding two, connected object with as one List element added to “parent” object. I have main class ( Author counterpart ) Wniosek that has many Osobowosc ( Identity ) and TypOsobowosci ( Type of Identity ), both as sperate classes, but both needed, as one “record” in List. How to make the similar solution to yours for two models object as one “record”? Make two rendering files I guess, but what inside the class itself?

End result should be like this:

Create Wniosek:

Typ:

Osobowosci: –

–

–

etc.

A couple of issues I found when I tried the example (might be because I used Grails 1.3.1):
(1) After saving an author with books, I couldn’t delete books from the list (they’d remain in the database). After debugging I found that the “authorInstance.properties = params” was not working correctly (the “_deleted” request parameter would be set to true, but the corresponding “authorInstance._deleted” property was always set to false). I changed “_deleted” to “deleted” (i.e. removed the underscore in the domain class & corresponding GSPs) then the code worked fine. I’m not sure why the underscore was causing an issue but it could be something weird relating to Grails 1.3.1.
(2) After I got (1) working, I ran into another issue. If I created, say, 3 NEW books (BookA, BookB and BookC in that order), then immediately remove BookB BEFORE hitting “save/update”, Grails actually persists BookA with an index field of 0 and BookC with an index field of 2 (instead of shifting BookC up to position 1 which would make more sense since B never really existed). I found the index “gap” was then causing issues when going to re-edit that particular author since Grails starts trying to retrieve book[2] from a collection of just two items.

There are a couple of ways round the 2nd issue – what I did was treat new books the same as existing ones (i.e. instead of calling “.remove()” in the GSP like you’d done, I kept a hidden “deleted” field for both existing AND new books, then called “hide()” in both cases when a book needed to be marked for deletion). Only thing is this means you DO have to ensure you include the same “authorInstance.books.removeAll(_toBeDeleted)” logic in your controller “save()” method as well (otherwise you can potentially end up with index “gaps” again).

Instead of (in main.gsp under layouts) –

It should be -

Thanks.