[
https://issues.apache.org/jira/browse/ISIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917030#comment-13917030
]
ASF subversion and git services commented on ISIS-660:
------------------------------------------------------
Commit 7cf52292dac95305cb2044d2c65b2846e5bd513a in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7cf5229 ]
ISIS-726, ISIS-660 etc: audit entries associated with implicitly scheduled
background jobs
Previously the transactionId of an implicitly scheduled background job was not
used in the transaction
created to execute said job. This resulted in audit entries and published
events that were orphaned from
the background command.
This fix addresses the problem by pushing down the creation of the transaction
(via
transactionManager.executeWithinTransaction(...)) until after the command has
been set on
the commandContext (using commandContext.setCommand(...))
In addition, a few other related fixes/tidy-ups:
* new commandServiceJdoContributions to lookup parent action (for audit entries
and published events)
* tidy-up/minor changes in todo example app
> 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)
