Hi Stefan, thanks a lot for this overview.
Getters and setters are optional for Ammentos. So you don't need to add them for the primary key for example or for the list in Machine. You only define those accessors that you need in you application. That leads to much nicer APIs on your entities.
This is something that I'm planning to add to RIFE's persistence, you're not the first one that asked for it. Also, allowing static constraints to be declared with annotations is planned too.
Please note that I'm not the big expert in persistence, so I may be totally wrong in every regard. But on the other hand, maybe this provides some ideas to make persistence easier in RIFE. I did not look at RIFE constraints in-depth yet, but from what I saw, references to other objects are more complex than in this example.
One thing I'm wondering about is the loading of the object references. Does Ammentos automatically load all the references to other objects? Does it do so recursively?
Best regards, Geert -- Geert Bevin Uwyn bvba GTalk: [EMAIL PROTECTED] "Use what you need" Avenue de Scailmont 34 Skype: gbevin http://www.uwyn.com 7170 Manage, Belgium AIM: geertbevin gbevin at uwyn dot com Tel: +32 64 84 80 03 Mobile: +32 477 302 599 PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9 Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
