Details
-
Improvement
-
Status: Closed
-
High
-
Resolution: Fixed
-
None
-
None
-
None
Description
Ard recommeded this:
> If we want to gain some real 'short-term' improvements without having
> to wait for fundamental model changes, what do you think if we try to
> get the HippoSession method disposeVirtualStates() into the Hippo
> repository. Then, I think we can do with quite some less Session
> refreshes
>
> HippoSession extends Session
>
> This way, all our 'read-only' jcr sessions in the default session pool
> never need a refresh, but just a disposeVirtualStates() call when
> there was an event below /content caught
>
I think the BasicPoolingRepository#SessionFactory#activateObject() could
do it optionally (this can be the default configuration through
SpringComponentManager.properties by the way). The proxy session could
implement #disposeVirtualStates() to enable this.
Attachments
Issue Links
- relates to
-
HSTTWO-2006 Dispose Virtual States option only via HippoSession#disposeVirtualStates() in the session pool when content change events triggered
- Closed
-
REPO-305 We need to be able to only 'refresh' the virtual states of a JCR session
- Closed
- waits for
-
REPO-305 We need to be able to only 'refresh' the virtual states of a JCR session
- Closed