[
https://issues.apache.org/jira/browse/ISIS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361402#comment-17361402
]
ASF subversion and git services commented on ISIS-2726:
-------------------------------------------------------
Commit 8ff4407cc3e4a3f110120d1ecf43f28b99e0a81f in isis's branch
refs/heads/ISIS-2726 from danhaywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=8ff4407 ]
ISIS-2726: moves InteractionTracker to applib
... there's no reason not to expose this functionality, and it enables
simplifying SudoService
> Rationalize fixture applib's Clock singleton vs VirtualClock, and also
> command replay's TickingClockService
> -----------------------------------------------------------------------------------------------------------
>
> Key: ISIS-2726
> URL: https://issues.apache.org/jira/browse/ISIS-2726
> Project: Isis
> Issue Type: Improvement
> Affects Versions: 2.0.0-M5
> Reporter: Daniel Keir Haywood
> Assignee: Daniel Keir Haywood
> Priority: Minor
> Fix For: 2.0.0-M6
>
>
> For the TickingClockService, I am hopeful that we can get rid of it
> completely. Instead, just use InteractionFactory's ExecutionContext to open
> another AuthenticationLayer running with the desired user/time/locale etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
