-
15. Re: Gravitation and POJO Cache
Well it looks like the option won't be necessary. Due to implementation details find will try and load an FQN as an internal id if it is not a reference. Since I am forcing internal id gets to use gravitation this will trigger the interceptor. So since it is already triggered, I also force reference lookups to gravitate as well.
However, POJO operations (including reads) will NOT force gravitation. So applications must still ensure that a pojo is not gravitated after a call to find().
-Jason -
16. Re: Gravitation and POJO Cache
At some point we did change this so gravitation only occurs for gets, since like Brian correctly pointed out earlier, using BR requires that the app guarantees session affinity and as such, for put() calls, we assume we already have the data - or we're creating new data.