Hello Dave,
> Whats the negetive with using Stateless session beans to do the actual
query
> itself, and then have the EntityBeans make calls into them?
Do you want to encapsulate the data access within session beans and call
them by entity beans? Maybe I missed the point but I believe it's better to
use DAO then because of the expensive remote method calls. I think it's not
a suitable solution especially if you consider the rule of thumb that a
remote call is 1500 times slower than a direct method call and that could
lead to performance problems in a heavy load enviroment. Okay you could try
to deploy your beans in the same container and use something like IIOP over
shared memory but than you have to take care of the fail-over and
load-balancing aspects as a bean provider in your bean design and that's not
the goal of EJB.
What do you think?
--
[EMAIL PROTECTED]
MATHEMA Software GmbH
N�gelsbachstra�e 25 b
91052 E r l a n g e n
D e u t s c h l a n d
Tel +49(0)9131/8903-0
Fax +49(0)9131/8903-55
http://www.mathema.de
===========================================================================
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".
