Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
viewer-wicket-1.7.0
-
None
Description
I think this is all done via other tickets.
~~~
For example, configure the MemoryConstrainedCacheManager.
In Wicket viewer, set up a way to invalidate the session (this is easy enough to do, see eg the code that calls the SessionLogger), so that the cache can also be clear.
We also need some way to "log out" for RO viewer. However, perhaps that can be left to another day.