[
https://issues.apache.org/jira/browse/ISIS-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509589#comment-14509589
]
Dan Haywood commented on ISIS-1061:
-----------------------------------
It seems that this upgrade to 6.19.0 is the root cause of the double logging
issue of the isis-module-sessionlogger, see
https://github.com/isisaddons/isis-module-sessionlogger/issues/6
The screenshots show where the stacktrace.
(The clue for regressing was Martin's recent note that Wicket 6.19 has also
broken "rememberMe". So I figured some refactoring had been done with
unintended side-effects; as seems to be the case for us...)
Martin... I reverted the commit, which also included reverting WB to 0.9.7.
But can/should we move WB back up to 0.9.8?
> Upgrade Wicket to 6.19.0
> ------------------------
>
> Key: ISIS-1061
> URL: https://issues.apache.org/jira/browse/ISIS-1061
> Project: Isis
> Issue Type: Task
> Components: Core
> Affects Versions: core-1.8.0
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 1.9.0
>
> Attachments: 1-logon.png, 2-then-a-logout-of-a-different-session.png,
> 3-then-another-logon-of-this-new-session.png
>
>
> Upgrade Wicket from 6.17.0 to 6.19.0 (latest stable release).
> I use 6.19 in the application I work on for few weeks now and I've no issues
> so far.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
