If you put @Embed on an entity in 4.0rc1, it's not possible to store this
entity @Serialize(d) in another entity.
And Entity can fullfill both the serialize and the embed requirements and thus
also should be able to use both versions without chaning the class.
I propose that @Serialize on class fields overwrites @Embed (which is put on
the class itself), so you can use both.
Original issue reported on code.google.com by aurelian...@gmail.com on 2 Sep 2013 at 9:49
Original issue reported on code.google.com by
aurelian...@gmail.com
on 2 Sep 2013 at 9:49