Jul 6th, 2010, 03:51 AM
I had the same problem; When you have a oneToMany relation then the child member attribute is probably a set.
suppose you have Invoice -> InvoiceDetails; Then replace everywhere in the generated code "SetRecord" with "InvoiceDetailRecord" and you're set. Apparently a bug.
Aug 6th, 2010, 06:17 PM
There's already a bug report for this, please upvote it!
Aug 20th, 2010, 04:25 PM
I think there are problem to create a class for Set and HashSet, I create a project to see the diferents between Roo 1.0.2 vs 1.1.0M2, and the relations that use Set has no created by gwt after the run of the command "gwt setup"
name.tuliopa.gwt.request.SetRecord cannot be resolved.
Aug 23rd, 2010, 04:44 AM
Set support for Roo/GWT
Originally Posted by Ben Alex
Long time no see.
has there been any update on the Set support for gwt setup ? do you think it will be in the forthcoming M3 release ?
Another on this thread mentioned that it is just a build issue, and that the GWT framework is supporting it. (Perhaps a question for Ray .. ) Is there an example of it working, all be it static ? Would love to get cracking on a Roo/Gwt app, GWT being what I always use these days and Roo just seems to fit well.
Ramon (ex Sydney)
Aug 23rd, 2010, 12:22 PM
Please Follow ASAP
Same as rBuckland, I'd really like someone to pass any information about this issue onto the user community...
I'm using GWT 2.1.0.M2 and Roo 1.1.0.M2 and still experiencing the same issue
Is it fixed somewhere on some branch, that I could use...?
thanks in advance
Tags for this Thread