[
https://issues.apache.org/jira/browse/JENA-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790176#comment-13790176
]
Claude Warren commented on JENA-530:
------------------------------------
perhaps the solution here is something along the lines of the transaction
handling in Spring where the transaction manager effectively keeps track of
wether or not a transaction is already in effect. If the transaction is in
effect the current transaction request "joins" that transaction if there is no
transaction in effect then the transaction is started.
Or is this problem addressing the interface between graph implementations (e.g.
inference graph to base graph)?
> Transactions (model and dataset) need to propagate through wrappers such as
> inference graphs.
> ---------------------------------------------------------------------------------------------
>
> Key: JENA-530
> URL: https://issues.apache.org/jira/browse/JENA-530
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 2.10.1
> Reporter: Andy Seaborne
>
> Complicated stacks of functionality do not propagate transactions. A common
> case is where the wrappers add functionality but do not add additional
> persistent state. In such cases, transactions can be passed to the base
> storage. An example of this is the inference graphs.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
