Abe White commented on OPENJPA-117:

I don't think we should encourage use of user objects for tracking state we 
could trivially expose ourselves.  Most of our APIs allow you to "get" anything 
you can "set", so I agree with Pinaki's approach of exposing the listener 
collection unless our internal bookkeeping mechanism in this case makes it 
inefficient for some reason.

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

Reply via email to