Hello,
Leon Messerschmidt wrote:
>
> In your case the new NGMBT would add a getTransactions() method to the
> Customer dataobject that returns a vector of Transaction dataobjects
> corresponding to that particular customer. The getTransactions() method
> will call TransactionPeer with a criteria object containing the CustomerID.
>
> Essentially the new methods will only be utility methods in the dataobjects
> that wraps around existing peer functionality - The peer classes will stay
> exactly the same. If I understand you right this is not exactly what you
> had in mind.
>
No, not exactly, but the modifications you propose sound very useful.
Thanks for your help in understanding them.
>
> Just a thought - I haven't worked on Peer long enough to give you a
> meaningful answer - I can see how this might be useful, but isn't this going
> a bit beyond the design of Peer and more towards something like Castor?
>
Yes, you're correct. :) I had a look at the castor material, jdo seems
like it could give the desired O-R persistance with caching, etc.,
without rewriting that stuff for the peers.
Regards,
~Eric
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
