From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta
Sent: Wednesday, April 11, 2007
6:45 AM
To: Corona
development
Subject: RE: [corona-dev] FW:
Repository Update Events
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Everitt, Glenn
Sent: 10 kwietnia 2007 18:51
To: Corona
development
Subject: [corona-dev] FW:
Repository Update Events
Here is the event message that everyone ignored
;-)
Glenn
From: Everitt, Glenn
Sent: Friday, February 16, 2007
5:18 PM
To: 'Corona development'
Subject: Repository Update Events
I think every Repository Update Event should include the
Repository URI as well as the resource URI that triggered the Repository update
event. In addition if there is way to know the URI of the user or the
tool that triggered the event I think that should be added to the event
For example if Harry added Sally to the Team Member
Repository
The event should include:
the Team Member Repository URI
the URI for Team Member Harry (he triggered the event)
the URI of the added Team Member Sally
If a new log file was added to Jackrabbit Repository by a
Chat Server
The event should include
the Jackrabbit Repository URI
the URI of the Chat Server since it triggered the event
the URI of the log file that was added.
Any comments?
How
jackrabbit adapter creating and posting event would know the URI of chat
server?
Edyta
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.