Use both.
Use entity to represent this table and stateless session to access this
entity.
-----Original Message-----
From: arun kumar [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 14, 2001 5:47 PM
To: [EMAIL PROTECTED]
Subject: [EJB-INT] Entity or Session
Hi all,
I am unable to decide to use stateless session bean or
entity bean, here my problem.
I have a table which has just one record( it will not
have more than one ), and based on some business logic
i need to update the record and return the value to
client each time a client request for it, there might
be lots of concurrent clients doing this request at
any point of time.
Since there is lots of read/write to this table, if i
pool the session bean - will the synchronization be a
bottleneck( store/load methods ) or use a stateless
session bean for this stuff.
Arun
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
===========================================================================
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".
