Deepak, As I mentioned in the previous posting, if our AppServer has exclusive access to the database (i.e. only one instance of the AppServer and not a cluster or a legacy app), then caching in the context you are talking about is very much possible.
If you have legacy applications modifying the database and/or other instances of our AppServer modifying data in the entity bean, then obviously you cannot use commit Option A. -krish > Krish, > > I have a CMP entity bean that associated with table in database. > This table has one filed called STATUS. In this table some rows are read > only (if status is marked CLOSED or CANCEL) and some rows can be modify (if > status is OPEN). > Also application also inserts rows with status OPEN. > > I would like to cache those rows that have a status CLOSED or CANCEL. > Do your AppServer support this kind of caching? > > Deepak =========================================================================== 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".
