Hi,
> So, I'm not quite clear on how you are going to chain the objects together or
> have the Peer model conceptually do it for you. I'm open for education here
> though so feel free to explain to me how you would like to see it implemented.
The POEM solution does it by defining the relationships in the schema - so that the
code that is generated then has the ability to navigate those relationships.
For example, the POEM schema for your example would be; (I think this is the
relationship you intended...)
table Member {
String firstName;
String lastName;
Access access;
}
table Access {
String role;
}
This would generate code that would have get/setAccess methods on a member object -
so, given a member object, you could set its access and get its access and behind the
scenes it gets the access object into memory.
For more info - see
http://melati.org/cgi-bin/cvsweb.cgi/~checkout~/org/melati/poem/doc/UserGuide.html
or for other examples; http://vg.morefire.com/docs/persistence_poem.html
Obviously the business code of when to combine the 2 still needs to be written - but
the persistence of the related items is automagic.
Hope this helps explain what I understand is trying to be achieved.
Chris
---
"surely it is madness to accept life as it is and not as it could be"
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
