But you might want to perform the login process through a stateless
session bean that returns some UserData object (from the entity), since
referring to an entity directly from the client can give you transaction
difficulties.
danch
Alvin Yap wrote:
>
> User object should be Entity Bean since needs to persist somewhere.
>
> You normally use session bean when you need a task or action to be done
> that needs one or more entity bean to complete the task.
>
> Alvin
> Cokorda Raka Angga Jananuraga wrote:
>
> > Hello, I'm Raka.
> >
> > Ok, the question... : after user log into my webstore, I should create User
> > object on the server side. Should it be stateless session bean or stateful
> > session bean..????
> >
> > or even, perhaps, an entity bean (since login process is performed against
> > the records in database.....) ???
> >
> > What are the considerations ?
> >
> > Thanks very very much, love you all,
> > -Raka-
> >
> > _________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
