[
https://issues.apache.org/jira/browse/JENA-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055892#comment-15055892
]
ASF GitHub Bot commented on JENA-1085:
--------------------------------------
Github user ajs6f commented on the pull request:
https://github.com/apache/jena/pull/108#issuecomment-164419995
If it's a problem with the fact that the former `commitLock` is now being
used for other transaction moments as well, I get that. But `systemLock` is
pretty generic and I would assume that it was meant to support `getLock`
(`system` being "the rest of the system outside this class" and not "the system
and not the application"). How about `lifecycleLock` or `transactionLock`?
> Review transaction finishes for DatasetGraphInMemory
> ----------------------------------------------------
>
> Key: JENA-1085
> URL: https://issues.apache.org/jira/browse/JENA-1085
> Project: Apache Jena
> Issue Type: Task
> Components: ARQ
> Affects Versions: Jena 3.0.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Fix For: Jena 3.1.0
>
>
> This JIRA is for a review of the transaction finishing code.
> Some of the code works because of the nature of specific implementations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
