Hello,
I would like your opinion on the following.
I have a method defined in the life-cycle interface of an entity
bean which returns a large collection of pks (severeal hundreds,
potentially thousands).
I habe to go through all the objects, so the app server does
an ejbLoad for each pk, so several thousands ejbLoad.
Perf is crap. Session bean with JDBC code a lot faster obviously
because I do a SELECT * and that's finished. With the entity bean
I have a remote call + SELECT * ... WHERE PK=MyPK...
Do you think it would be nice to have a cache on the app server so that
for a findLargeXXX, the app server creates EJBobjects instances the
first time, and do not go to the database when I am dealing with them.
It implies to have a smart and nice cache in the app server.
What do u think gurus?
-- Thierry
