Thanks for the reply Thomas.
Properties are still there in M3, and Roo still generates them. May
be they are gone in M4? Or simply they are not necessary in M3. I'll
try to get rid of them.
Regarding one-to-many: for now I use many-to-one and service methods
to retrieve collections. Will be looking forward to RC1's support of
one-to-many.
Yuri
On Oct 5, 3:23 pm, Thomas Broyer <t.bro...@gmail.com> wrote:
> On 5 oct, 18:54, Y2i <yur...@gmail.com> wrote:
>
> > An Entity class participates in one-to-many relationship:
>
> > @OneToMany
> > private Set<SomeClass> someClass = new HashSet<SomeClass>();
>
> > How would I implement an EntityRecord?
>
> > Property<XXX> someClass = new Property<XXX>("someClass",
> > SomeClass.class);
>
> Hmm, M2? FYI, properties are gone in M3.
>
> > abstract XXX<SomeClassRecord> getSomeClass();
>
> > What should go instead of XXX above? I tried looking at what Roo does
> > but it fails to generate correct records for one-to-many
> > relationships.
>
> Even M3 does not support lists and sets, but trunk does support both
> java.util.List and java.util.Set; it'll be in the upcoming RC1.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
