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 09:21:58 GMT
Hello,

the request from Pinaki regarding the transactionlistener also are in our business need. The
actual possibility of Transactionlistener API are to small in OPEN-JPA/Kodo. It would be great
when the folloing apsects could be considered.

1. Why could the Transactionlister not have the same structure of API as the Instancelifecycle
Listener. That mean configuring a Default Transactionlister with the brokerfactory, reading
actual transactionlistener's in the broker and manipulating actual transactionlisterners (that
means deactivating or changing)

2. I can understand your concerns Patrick, but I'm as a customer can tell you that KODO is
great becouse you can configure and change so much in the deep of brokers and factory's...The
responsibility not to build something what is not working, is at the teams which are using
Open-JPA. E.g. in our team  the code and Configuration which is making all the lister stuff
is "holy", that means almost untouchable (only for the priest's)(;-). So the normal developer
is not allowed to change something on the listener Configuration.

My post is not so on that technical Level, but I've understand the mailing list also as a
place for committing and discussing Changerequest. When it is wanted, I could give sometimes
a view from a OPEN-JPA user. Pinaki knows a little bit about our projects, because he was
involevd in Workshop in november in Hamburg. 

many Regards

Marcus Thierling


-----Urspr√ľngliche Nachricht-----
Von: Patrick Linskey (JIRA) [mailto:jira@apache.org]
Gesendet: Dienstag, 30. Januar 2007 19:38
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_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.

Mime
View raw message