[
https://issues.apache.org/jira/browse/ISIS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308162#comment-15308162
]
ASF subversion and git services commented on ISIS-1414:
-------------------------------------------------------
Commit bbdc9fca438d9f2d2cf19128e5f9f2a471e831ea in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=bbdc9fc ]
ISIS-1414: introduced sequence for chg.xsd so that PublishedObjects can have a
sequence; promoted WithTransactionScope interface to applib; QueryResultsCache
now implements this interface.
The "transactionId" is really an interaction id, and there could be multiple
transactions within a single such interaction. Therefore any PublishedObjects
(= set of dirtied objects within a transaction) needs to have a sequence number
to distinguish from other transactions, and also from any interaction
executions.
> nextTransaction can cause null pointers with the new MetricsService.
> ---------------------------------------------------------------------
>
> Key: ISIS-1414
> URL: https://issues.apache.org/jira/browse/ISIS-1414
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.12.1
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.13.0
>
>
> The reason is that request-scoped services are implemented as transaction
> services. Most of the time the scope of a request and the scope of a
> transacion are one and the same: there is just one transaction per scope.
> However, TransactionService#nextTransaction admits for there being multiple
> transactions per request.
> This bug is that the current implementation for RequestScoped does the
> init/close as part of the Transaction management. Instead, this should be
> part of the PersistenceSession#open/close (a PersistenceSession wraps a JDO
> session, so basically corresponds to the request).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
