Hi,
the delistment of services seems to have changed its behaviour from Slide 2.0 to Slide 2.1.
In method ExtendedStore.createObject() a new object is put into objectsCache. After executing delist() this object disappears from this cache in Slide 2.1. In Slide 2.0 it stays. More precisely the object disappears from the cache when transaction.delistResource(ExtendedStore, TMSUSPEND) was called in the delist() method.
Is there a possibility to change this behaviour back to Slide 2.0s by configuring? Has something changed with the transaction manager?
Please give me a hint what to do. I need to create objects with Slide 2.1 which is refused with an ObjectNotFoundException because the new object cannot be found in cache so it's looked up from physical place where it cannot be found, of course. I use the file based stores to store metadata and content.
Kind regards Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
