[
https://issues.apache.org/jira/browse/ISIS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-1472.
-------------------------------
Resolution: Fixed
> Any attempts to schedule a background job via the RO viewer fail, due to
> incomplete state. (In fact: actions with commands cannot be invoked via RO
> viewer).
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-1472
> URL: https://issues.apache.org/jira/browse/ISIS-1472
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.13.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 1.13.1
>
>
> The issue is that regular commands are not being persisted, at all, under the
> RO viewer.
> This is because I've made it the responsibility of the viewer to get hold of
> the current Command (using CommandContext#getCommand()) and to update the
> "Executor" of the Command to be "USER". This is done by the Wicket viewer.
> And, similarly, in BackgroundCommandExecution adapter the Executor gets set
> to "BACKGROUND".
> But in the RO viewer I've not updated this field, so it remains set to its
> default, "OTHER". This then causes the initialization of the Command (when
> the initial action is invoked) to be skipped, resulting in no
> memberIdentifier.
> So, the fix is just for RO viewer to set this field in
> DomainObjectResourceServerside and DomainServiceResourceServerside.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
