[EMAIL PROTECTED] wrote:
No, I don't thik so, since the object is not instantiated by OJB. If I takeIf you look into the RowReaderDefaultImpl, you'll see that there is no cache handling in there at all. This is because the cache works with java objects regardless of where they come from (see the ObjectCache implementations). Therefore, in your case it should not matter where the object comes from.
again the example of the Car and its Owner, the Car object is instantiated
by OJB, because the data is stored in the RDBMS and retrieved using the
PersistenceBroker.
The Owner object must be read from an external application and cannot by
retrieved by OJB. To do that, I overwrite RowReader.readObjectFrom() to add
a couple of instruction that access the external application, create the
owner instance and set it to the car.
I would like to add the owner to the OJB cache so it would be cleared at
the same time that all other objects of the application, regardless if they
have been retrieved through OJB or not.
Please check whether your external objects are cached, e.g. build the debug OJB version via the jar-debug Ant target and add a breakpoint in the lookup method of the cache impl that you're using.
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
