Thanks Siva,
U said an imp. thing. What i understand is an instance of entity bean can
be accessed by more than 1 person. Hence its imp. to use Session Beans which
keeps track of the identity of the user...And Session Beans can in turn
contact the entity beans...Am i right?
Prateek.
-----Original Message-----
From: Sivakumar_Subramanian <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, June 12, 2000 9:50 AM
Subject: Re: Session and Entity Bean
>Hi Prateek,
> In fact u'r project shoudl use both session and entity beans if u
>want to maintain client's details in any sesssion or something like that.
in
>fact entity beans are usually tied up with the database in tact and the
>session beans will call these entity beans.
>
>cheers,
>sivakumar
>
>
>> ----------
>> From: Prateek[SMTP:[EMAIL PROTECTED]]
>> Reply To: A mailing list for Enterprise JavaBeans development
>> Sent: Tuesday, June 13, 2000 6:27 AM
>> To: [EMAIL PROTECTED]
>> Subject: Session and Entity Bean
>>
>>
>>
>> HEllo Everybody,
>> Here in my proj. we are using EJB. I would like to know under
>> what situations can an Entity and Session Bean combination be used?
>>
>> Thanking in advance,
>> Prateek.
>>
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
