[
https://issues.apache.org/jira/browse/ISIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887624#comment-13887624
]
ASF subversion and git services commented on ISIS-660:
------------------------------------------------------
Commit 49c7c05dd57be56f6d272329c3a4693a996d8a09 in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=49c7c05 ]
ISIS-657,ISIS-660,ISIS-661,ISIS-662,ISIS-663,ISIS-667,ISIS-668,ISIS-670: JDO
services
ISIS-657:
- appsettings / usersettings entities also now use "Isis" as prefix to table
names
ISIS-660:
- renamed InteractionFactory to InteractionService
- renamed InteractionRepository to InteractionServiceJdoRepository
- InteractionDefault and InteractionJdo now have a next() method, to create
sequences of numbers
(as used to generate the PKs for PublishedEventJdo and BackgroundTaskJdo, see
below)
- Interaction#startedAt renamed to Interaction#timestamp (and #startedAt now a
derived property)
- Interaction now defines a #transactionId property
- IsisTransaction now picks up its transactionId from passed-in Interaction
object (if available)
- and defers to Interaction for generation of next pub/sub event sequence if
it can (else previous behaviour)
- IsisTransaction#guidId renamed to #transactionId
ISIS-661: (background service mementos, background task service)
- renamed BackgroundTaskContributions to BackgroundTaskServiceJdoContributions
- renamed BackgroundTaskRepository to BackgroundTaskServiceJdoRepository
ISIS-662: published events contributions
- renamed PublishedEventRepository to PublishingServiceJdoRepository
- renamed PublishedEventContributions to PublishingServiceJdoContributions
ISIS-663: audit entry contributions
- rename AuditEntryCountributions to AuditingServiceJdoContributions
- rename AuditEntryRepository to AuditingServiceJdoRepository
ISIS-667:
- added JdoColumnLength as central location for standard column lengths of JDO
entities
- renamed AuditEntry to AuditEntryJdo
- renamed PublishedEvent to PublishedEventJdo
- changed PK for PublishedEventJdo entity to be application-defined:
(transactionId,sequence)
- change to datatype of some PublishedEventJDO entities
- changed PK for BackgroundTaskJdo entity to be application-defined:
(transactionId,sequence)
- factored out Util class for JDO entities
- renamed UserSettingPrimaryKey to UserSettingJdoPK
ISIS-668:
- improvements to ServicesInstallerFromConfiguration
- improved formatting of isis.properties in the todo app & simple app
ISIS-670:
- removed AuditingService, AuditingService2 APIs
- introduced replacement AuditingService3 API
> 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)
