You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/01/30 18:50:33 UTC
[jira] Commented: (OPENJPA-117) Collection of TransactionListeners
registered to a Broker should be available as unmodifiable collection
[ https://issues.apache.org/jira/browse/OPENJPA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468711 ]
Patrick Linskey commented on OPENJPA-117:
-----------------------------------------
What's the use case for this? If someone were to write code that cannot track for itself what it's done, the code could always add a user object (Broker.putUserObject()).
> 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.