Hi all,
after millions of test cycle I found the (main) problem. It's caused by the collection proxy implementations in conjunction with an ObjectCache implementation different than the ObjectCacheDefaultImpl, e.g. with "empty cache" or with TLCache.
Say we have an object with circular reference A1 -1:1-> B1 -1:n-> [A1,C] and the 1:n is a collection proxy.
Now user lookup A1 and get [EMAIL PROTECTED]>[EMAIL PROTECTED]>[EMAIL PROTECTED] He wants to remove the C object in the 1:n reference in [EMAIL PROTECTED] Because B has an proxy collection, the proxy materialize on
B.getC's().remove(1) ==> remove C
call.
While materialization of the collection proxy OJB lookup again an A1 instance. Because the previous materialzed [EMAIL PROTECTED] instance isn't in the cache, so OJB lookup a new instance for A1 ==> [EMAIL PROTECTED] and a new [EMAIL PROTECTED]
Thus we have [EMAIL PROTECTED] --> [EMAIL PROTECTED] -->[EMAIL PROTECTED]@22[-->[EMAIL PROTECTED]>[EMAIL PROTECTED] !!!! Needless to say this will cause problems on update.
Any suggestions?
regards, Armin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
