[ 
https://issues.apache.org/jira/browse/ISIS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886400#comment-13886400
 ] 

ASF subversion and git services commented on ISIS-662:
------------------------------------------------------

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


> Provide a "contributions" service to add a PublishedEvents contributed 
> collection for the Interaction entity.
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-662
>                 URL: https://issues.apache.org/jira/browse/ISIS-662
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core, Objectstore: JDO
>    Affects Versions: objectstore-jdo-1.3.0, core-1.3.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: objectstore-jdo-1.4.0, core-1.4.0
>
>
> Building on an idea in ISIS-661, whereby BackgroundTask will have a similar 
> service. 
> The idea is that viewing Interaction can show all this associated information 
> (BackgroundTask, now also PublishedEvent).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to