[
https://issues.apache.org/jira/browse/ISIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886398#comment-13886398
]
ASF subversion and git services commented on ISIS-660:
------------------------------------------------------
Commit b99640031fd05002aefa455b201eff37656f1776 in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b996400 ]
ISIS-660,ISIS-661,ISIS-662,ISIS-663: background tasks and similar
ISIS-660:
- consistent pattern of services vs repository vs contributions for
each of interactions, background tasks, published events and audit entry
- refactored todo app, introducing new Admin service that delegates
- InteractionOutcome and InteractionOutcome.Type, capture any exception
- Interaction.Nature
- HasTransaction now defines transactionId property as a UUID, not a String
- can now use UUID as a @PrimaryKey (used by the HasTransaction implementations)
ISIS-661: BackgroundTask contributions service
ISIS-662: PublishedEvent contributions service
ISIS-663: AuditEntry contributions service
> Profiling support and also infrastructure for background (async job) support
> ----------------------------------------------------------------------------
>
> Key: ISIS-660
> URL: https://issues.apache.org/jira/browse/ISIS-660
> Project: Isis
> Issue Type: New Feature
> Components: Archetype: Simple WRJ, Archetype: ToDoApp WRJ, Core,
> Objectstore: JDO
> Affects Versions: archetype-simple-wrj-1.3.1,
> archtype-quickstart-wrj-1.3.1, objectstore-jdo-1.3.0, core-1.3.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: archetype-simple-wrj-1.4.0,
> archetype-quickstart-wrj-1.4.0, objectstore-jdo-1.4.0, core-1.4.0
>
>
> Two use cases envisaged:
> 1. profiling of the application
> 2. as a handle for long-running async calls. Can envisage a contributed
> collection that would list long-running async calls associated with a
> persisted Interaction.
> The request-scoped InteractionContext provides context information to the
> caller. By default this is an in-memory representation, discarded once done.
> The complementary InteractionFactory interface allows the instantiationof the
> Interaction to be delegated. So the other part of this ticket is a JDO
> implementation allowing the Interactions to be persisted and thereby queried.
> With this done, any action invocation will also be recorded as a persisted
> Interaction object.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
