Hi!
Jim Richards wrote:
> > What about the performance in doing so.Is it not better to invoke the
> >entity beans from the session bean & then retrieve the data.
>
> Each invokation of the entity bean is another connection to the
> database, a JNDI lookup and a few othe things. If you only
> want the data for read only purposes this is a massive over
> kill. I use entity beans only when I know the data needs to be
> updated, if it is only for display then the overhead of an entity bean
> is not really required.
This is not true. To be precise:
> Each invokation of the entity bean is another connection to the
> database,
JDBC connections are *always* pooled (if they're not; get another
EJB-server that gets it right).
> a JNDI lookup
Cache the home interface stub and no lookup is necessary.
> a few othe things
Such as?
If used properly EntityBeans can be a very efficient cache of object-ish
data. It's just that "proper use" is not easy, but that doesn't mean
that it isn't possible.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
