You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/01/28 08:02:38 UTC

[jira] [Resolved] (ISIS-660) Profiling support and also infrastructure for background (async job) support

     [ https://issues.apache.org/jira/browse/ISIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood resolved ISIS-660.
------------------------------

    Resolution: Fixed

> 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)