[
https://issues.apache.org/jira/browse/ISIS-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17234854#comment-17234854
]
ASF subversion and git services commented on ISIS-2464:
-------------------------------------------------------
Commit 4100884930322010ef6b37621b36f17ec424d872 in isis's branch
refs/heads/master from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=4100884 ]
ISIS-2464: splitting Publishing into 2 separate concerns
1. capturing Executions
2. capturing changing Entities
// renaming SERVICES
AuditerDispatchService -> EntityAuditDispatcher
PublisherDispatchService -> ExecutionDispatcher &
ChangingEntitiesDispatcher
PublisherDispatchServiceDefault -> ExecutionDispatcherDefault &
ChangingEntitiesDispatcherDefault
CommandServiceInternal -> CommandDispatcher
PublisherServiceLogging -> ExecutionLogging & ChangingEntitiesLogging
PublishedObjectsDefault -> SimpleChangingEntities
// renaming API/SPI
AuditerService -> EntityAuditListener
PublishedObjects -> ChangingEntities
PublisherService -> ExecutionListener & ChangingEntitiesListener
CommandServiceListener -> CommandListener
// renaming LOGGING
AuditerServiceLogging -> EntityAuditLogging
PublisherServiceLoggging -> ExecutionLogging & ChangingEntitiesLogging
> Application Layer Overhaul for v2
> ---------------------------------
>
> Key: ISIS-2464
> URL: https://issues.apache.org/jira/browse/ISIS-2464
> Project: Isis
> Issue Type: Improvement
> Components: Isis Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Critical
> Fix For: 2.0.0-M5
>
>
> In preparation of integrating Spring Data JPA, simplify if possible, aspects
> of
> * Command/Auditing/Publishing Infrastructure ... separation of concerns via
> well documented interfaces, then could use a single dispatcher service
> instance to implement them all
> * WrapperFactory Interaction nesting in coexistence with the SudoService
> * Async Wrapping to spawn its own InteractionSession (must not share its
> InteractionSession with the calling thread: potential ThreadLocal collision
> when run with common ForkJoinPool?)
> Also provide new tests, to verify correct implementation of these aspects.
> Also overhaul corresponding ref-doc chapters and add sequence diagrams for
> these aspects.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
