BTW, the Album object is cached in the session. Michael
----- Original Message ----- From: "Michael Mogley" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Saturday, November 29, 2003 3:07 PM Subject: does PersistenceBroker.getCollectionByQuery use the cache? In my webapp, I've run across what may be a bug in Ojb. I have an Album class with a collection of Photos. I also have a jsp page, photoEdit.jsp, that retrieves a specific Photo by identity, modifies it, then does PersistenceBroker.store. I have another page, albumPhotos.jsp, that lists all the photos in a given album along with some of their attributes. When I make a change in photoEdit.jsp to a given Photo, then go to albumPhotos.jsp to to list all the photos in the album, the Photo I changed is listed with the old attributes. I am using ObjectDefaultCacheImpl and the app initializes and keeps a reference to a single PersistenceBroker instance. It seems to me that when the Albums.photos collection attribute is being initialized, the elements in the collection are not being cached. Is this true? If so, it seems this would be bug. Or could I doing something half-assed? Thanks in advance. Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
