Hi, You can look at them as roles and implements all business methods in user class and protect them by roles. You can do this either through xml or by using annotations.
Ramzi On Mon, Feb 8, 2010 at 2:15 PM, Arash <rakhs...@gmail.com> wrote: > > Hi, > > This is general design question related to the tools Appfuse provide that > might support or conflict with what you have in mind. My application needs > to have several different users i.e. Manager, Accountant, Buyer, Seller. > Each of which could be treated as a person or user and might have extra > attributes. > > I already have the Manager extending from User class. Manager has clearly > more fields and mapping than User. Now the confusion comes where I don't > know how to look at these different users. Are they only roles and should > follow appfuse structure or should I leave them as extending the User > object. I have a feeling that I need to take advantage of Role table and > User, Role relationship in AppFuse could satisfy what I need but then again > I can't only suffice to tag a Manager as a role. Basically: Where would I > utilize the Role table and where would I define a separate class like > Manager extending the User. > > > Thank you very much in advance for your help > Arash > -- > View this message in context: > http://n4.nabble.com/Different-types-of-User-tp1473383p1473383.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net > For additional commands, e-mail: users-h...@appfuse.dev.java.net > >
