Hi,
The design approach generally used is:
Use session beans for listable data(using JDBC). entity beans do affect performane ,
so it is always better to use sessionbeans for listable data. But then we have to
guard against dirty reads . For if we are using Entity beans to access the same data
that we access using session beans, it may cause dirty reads.
For data that is to be updated use Entity beans.
Cheers,
Parikshit
_____________________________________________________________________________________________________________
Parikshit Pol
Systems Executive
KPIT System Ltd.
6,Mayur Colony,
Karve Road,
Pune-411029
e-mail :< [EMAIL PROTECTED] >
Phone : 91-020-5468654 ext. - 212
_______________________________________________________________________________________________
-----Original Message-----
From: Neal Kaiser [SMTP:[EMAIL PROTECTED]]
Sent: Monday, December 27, 1999 9:28 AM
To: [EMAIL PROTECTED]
Subject: Design Question - Entity Beans/Connection Pooling
I'm new to the EJB world, and I'm about to start designing a large
E-Commerce application.
>From what I've read, I can't tell if I should use Entity beans or just
have
a stateless session bean
which does JDBC queries? For example, lets say I have 30,000 product
items.
A product seems
to be a good candidate for an entity bean, but how would performance be
compared to a session
bean w/ JDBC?
And if I do go with the session bean/JDBC approach, is it a common
design
approach to have a
session bean as the connection pool manager? But I only want to have
one
instance of the connection
pooling manager (ie, at startup it makes X connections and all the other
session beans will get a connection
from it as needed).
If anyone has seen any articles on E-Commerce EJB design, please let me
know
=)
Thank you!
Neal
========================================================================
===
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".
�������������������������o 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".
