You don't need managers for each object unless you have business logic you want
to add for the object that isn't handled by the generic manager.
You should first try to use the generic managers and dao's then if you need add
a manager and/or dao for the object with most specialization required and last
if each object needs its own set of business logic or hibernate query logic add
managers and/or daos for them.
HTH
----- Original Message ----
From: Richard G. Reyes <[EMAIL PROTECTED]>
To: users@appfuse.dev.java.net
Sent: Thursday, April 5, 2007 11:20:30 PM
Subject: [appfuse-user] Re: Managers For Nested objects
Hi All,
Any comments?
Hope someone can point me to a direction where I can find some answers.
Thanks
Richard
On 4/5/07, Richard G. Reyes <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Can I get your opinions on how to design or access my nested objects.
> To illustrate:
>
> I have objects A, B and C.
>
> public class A {
> Set<B> bs = new TreeSet();
> }
>
> public class B {
> Set<C> cs = new TreeSet();
> }
>
> Please note that I'll be using hibernate.
> All 3 objects would be entities since they would be member of other
> objects as well and both objects B and C are abstract classes.
> I think it will be correct to create DAOS for A,B and C. But what I am
> not sure is
> if its better to create a manager for each or just for obj A. I am
> assuming that if I already retrieved A then I will also have the
> nested B and C.
>
> Comments please...
>
> TIA!
>
> Richard
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
