[
https://issues.apache.org/jira/browse/OPENJPA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468735
]
Patrick Linskey commented on OPENJPA-117:
-----------------------------------------
The problem is that this lets party A get what party B set. So if one bit of
code added a particular listener, a different bit of code could then get the
listener and remove it. Is this something that we want to make easy for people
to do? It seems like different listeners should be relatively isolated from
each other.
> Collection of TransactionListeners registered to a Broker should be available
> as unmodifiable collection
> --------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-117
> URL: https://issues.apache.org/jira/browse/OPENJPA-117
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Reporter: Pinaki Poddar
> Assigned To: Pinaki Poddar
> Priority: Minor
>
> Currently TransactionListeners can be added/removed to a broker but the list
> of transaction listeners registered to a particular broker is not available.
> Such a collection can be made available in read-only mode so a caller can
> determine whether to add a new listener or not, or whether a particular
> listener is already registered.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
