As far as I know there is nothing in the EJB spec itself that will address this for you. In my opinion, if you are planning to use CMP, and you are interested in using some sort of home grown cache, you are at the mercy of the Container provider.
If the container provider provides you hooks to leverage this cache you have implemented you are in luck, otherwise ... - Chinmay On Thu, 3 Feb 2005 18:30:21 +0530, Deepak Saini <[EMAIL PROTECTED]> wrote: > > > > Hi everyone, > > I am working on a task which requires creating a cache(using hashtables > probably) so that the components donot need to invoke the finder methods of > the CMP beans all the time. > > Reason for doing this: > > 1. the finders cannot utilize CMP cache because there are not > findByPrimaryKey > 2. a large number of calls are being made to these finder methods. > > Query: > > 1. Is it correct that we cannot have CMP cache because these finders are not > findByPrimaryKey? > 2. If I create cache, is there any mechanism to make sure that the cache > information is not inconsistent with the database? > > Regards > Deepak > > > > > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you have > received it in error, please notify the sender immediately and delete the > original. Any other use of the email by you is > prohibited.=========================================================================== > 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".
