[jira] [Created] (ISIS-1372) Change BackgroundCommandService to work with Aim DTO; centralize logic for creating Aim DTOs within new domain service (CommandMementoService)

["Dan Haywood (JIRA)" <ji...@apache.org>]

Dan Haywood created ISIS-1372:
---------------------------------

             Summary: Change BackgroundCommandService to work with Aim DTO; centralize logic for creating Aim DTOs within new domain service (CommandMementoService)
                 Key: ISIS-1372
                 URL: https://issues.apache.org/jira/browse/ISIS-1372
             Project: Isis
          Issue Type: New Feature
          Components: Core
    Affects Versions: 1.12.0
            Reporter: Dan Haywood
            Assignee: Dan Haywood
            Priority: Minor
             Fix For: 1.13.0


Currently the ActionInvocationFacetForDomainEventAbstract - to support background commands - calls the non-API method on BackgroundServiceDefault.  The returned ActionInvocationMemento is serialized and persisted by BackgroundCommandService impl.  To actually run in the background, the command object is rehydrated and passed to BackgroundExecution.

We also want to be able to republish events (via PublishingService2); this requires that the command memento holds ActionInvocationMementoDtos rather than the current "legacy" ActionInvocationMemento.

Currently the logic to pass to relevant info to the PublshingService - namely, the EventMetadata object - is hard-wired within IsisTransaction.  

This ticket is to move the responsibility to create command action invocation memento DTOs into a new service, CommandMementoService, and have it also be able to create EventMetadata objects too.  Thus the IsisTransaction becomes much thinner, and also allows PublishingServiceMq to reuse the CommandMementoService.

~~~
said another way: move code from IsisTransaction (to create the Event metadata) and also the code in PublishingServiceMq (to create action invocation memento DTOs from an event metadata) into this new service.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)