openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thierling, Marcus \(Salt Solutions\)" <Marcus.Thierl...@otto.de>
Subject AW: [jira] Commented: (OPENJPA-117) Collection of TransactionListeners registered to a Broker should be available as unmodifiable collection
Date Wed, 31 Jan 2007 10:49:25 GMT
Hello Abe,

in our use Case we need the Transactionlister to implement an audit-log on PC-Object and PC-Object-Attributelevel.
Because were a building a item/masterdata-Management-system. One of the main targets is to
track every change on the Masterdata and then to export the Change to over 100 other Systems.

In our case we want to use OPEN-JPA Broker-Listeners to replace a whole bunch of oracle Database
triggers, because they make us some headaches. If you want more details, feel free to ask
for.

regards

Marcus

-----Urspr√ľngliche Nachricht-----
Von: Abe White (JIRA) [mailto:jira@apache.org]
Gesendet: Dienstag, 30. Januar 2007 21:16
An: open-jpa-dev@incubator.apache.org
Betreff: [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_12468770
] 

Abe White commented on OPENJPA-117:
-----------------------------------

I don't see why listeners are some special case that require more isolation than all of the
other state we expose.  There are tons of things you can do with a broker,etc to screw other
users of that broker,etc.  I don't see how this is unique.

That said, I also think the proposed use case is weak.  I'd question the quality of an application
that had code paths that could result in the same listener being added twice.  Adding listeners
should generally either be done as an initialization step or as a temporary step where the
listener is removed immediately following a specific action.  It's hard to imagine a scenario
where listeners are added so haphazardly that duplicates could occur.  I'd be interested to
hear a more concrete use case.

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

Mime
View raw message