Hi Steve,
If someone can give the new material a quick read and make sure it's accurate and that my adaptation of Emmanuel's code is
I read over it and it looks very nice, just made a couple of minor modifications.
the right way to do things, that'd be super. In particular I tried and failed to make the Account object use the RIFE user ID as its identifier, which I feel is the right data model since it's a one- to-one mapping. If there's some way to do foreign primary keys I wouldn't mind knowing, but I couldn't get RIFE to stop trying to assign a fresh ID value to my Account object.
I think this should be possible by adding a 'sparse' constraint to your identifier property. I haven't tried it out yet in this situation, but that's what its intention is: allowing you to manage the ID values yourself. I'll try it out once I get back from Barcelona, next week.
I also didn't see a more elegant way to do the many-to-one constraint between Account and RoleUser, but it's entirely possible there is one I'm not aware of. At the very least I imagine there's a more elegant way to look up the RoleUser table name.
Best regards, Geert -- Geert Bevin Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
