[
https://issues.apache.org/jira/browse/TINKERPOP3-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-765.
---------------------------------------
Resolution: Implemented
In 3.0.0, implementers typically used {{AbstractTransaction}} as a starting
point for their {{Transaction}} implementation. As a result of this change,
they will need to extend from {{AbstractThreadLocalTransaction}} to get the
same functionality as before. Not making this change will likely manifest
itself as compile errors in their {{Transaction}} implementations.
There is also a {{AbstractThreadedTransaction}} which takes a global approach
to raising events on commit. This would be useful for those graphs
implementing threaded transactions (i.e. for the {{Graph}} returned from
{{Transaction.newThreadedTx()}}..
> Decompose AbstractTransaction for different transactional contexts
> ------------------------------------------------------------------
>
> Key: TINKERPOP3-765
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-765
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process, structure
> Affects Versions: 3.0.0-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Labels: breaking
> Fix For: 3.1.0-incubating
>
>
> {{EventStrategy}} uses the listeners available on {{Transaction}}
> implementations to know when events should be fired (i.e. per transaction).
> Validate that there are no listener leaks in this model and consider methods
> for improvement if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
