Well, that kind of works. That is, it works great, unless you have
bidirectional references that you want refreshed, in which case you get a
Stack Overflow....
|---------+--------------------------->
| | Ron Gallagher |
| | <[EMAIL PROTECTED]|
| | uth.net> |
| | |
| | 04/02/2003 11:48|
| | AM |
| | Please respond |
| | to "OJB Users |
| | List" |
| | |
|---------+--------------------------->
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: RE: Default Cache - bug? design catostrophe? user error?
|
|
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
David --
It's not used by the cache. It's used by the PersistenceBroker when it
retrieves an object. If the 'target' object is found in the cache, then
any reference/collection descriptors that are marked with refresh="true"
are re-populated before the 'target' is returned to the caller.
Ron Gallagher
Atlanta, GA
[EMAIL PROTECTED]
>
> From: [EMAIL PROTECTED]
> Date: 2003/04/02 Wed AM 11:44:27 EST
> To: "OJB Users List" <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: RE: Default Cache - bug? design catostrophe? user error?
>
>
> No, I haven't. I will take a look at that, but the code I saw in the
cache
> didn't look like it would do that....
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
