[
https://issues.apache.org/jira/browse/ISIS-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Keir Haywood updated ISIS-1046:
--------------------------------------
Fix Version/s: 2.0.0-M6
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.
was:
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.
Issue Type: Improvement (was: New Feature)
> Get rid of chatty Shiro messages about no CacheManager being set.
> -----------------------------------------------------------------
>
> Key: ISIS-1046
> URL: https://issues.apache.org/jira/browse/ISIS-1046
> Project: Isis
> Issue Type: Improvement
> Components: Isis Security Shiro
> Affects Versions: viewer-wicket-1.7.0
> Reporter: Daniel Keir Haywood
> Priority: Minor
> Fix For: 2.0.0-M6
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
