Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Message-ID: <7690014.1170179433266.JavaMail.jira@brutus>
Date: Tue, 30 Jan 2007 09:50:33 -0800 (PST)
From: "Patrick Linskey (JIRA)" <jira@apache.org>
To: open-jpa-dev@incubator.apache.org
Subject: [jira] Commented: (OPENJPA-117) Collection of TransactionListeners
 registered to a Broker should be available as unmodifiable collection
In-Reply-To: <25089842.1170179073249.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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.