I think you'd either have to implement the User class yourself or if
possible create a View based upon your two tables and map the columns
needed.
We used the first solution for a application by simply excluding the
appfuse-data-common package, extraced this into our project and created (for
a modular archtype) a module named ${appname}-data-common which was a
dependency of the core module. Or you could just create a model class which
implements the UserDetails interface (AFAIR) and use this within your
application.On Thu, Jul 17, 2008 at 6:30 PM, nani2ratna <[EMAIL PROTECTED]> wrote: > > Hi, > > In our application , database design is different from the appfuse default > database tables for user and roles. > For user only we have 2 tables. > Tables design is like this--------> first tables is user table > which consists of following tables > a)ApplicationID (Foriegn key for application table). > b)Userid (Primary key for this table - GUID). > c)username (login id ) > and some other columns not important > > Second table name is membership > It has following columns > a)Applicationid (fk for application table) > b)USerID (pk and fk for user table) > c)Password > d)email > e)isapproved > f)islocked > and some other columns. > > What i want is for login, how to get find the user is valid or not by using > HIbernate,annotations > like how it was implemented in APpfuse. > can anybody help me in this. > > Thanks and REgards > Ratna > -- > View this message in context: > http://www.nabble.com/Help-in-Model-Layer-tp18512563s2369p18512563.html > Sent from the AppFuse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Mit freundlichen Grüßen / With kind regards Michael Dürgner
