On Wed, Nov 10, 2010 at 19:29, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
What about creating an EventLogger component with
implementations for
each of the events that need to be logged by the activity stream? When
an event is triggered you lookup the corresponding EventLogger. If there
is no EventLogger for the specific hint then ignore the event.
(Which is exactly what I proposed and what remote observation manager
system is doing except that it's sending the event on network instead
of saving it in database but it's the same constraint: serializable
data)
Hope this helps,
Marius
On 11/10/2010 10:08 AM, Stefan abageru wrote:
Hi devs !
I thought about adding some changes in Events and Activity Stream.
First of all, I want to remove all the listeners from Activity Stream
and make this class listen to AllEvent, making it capable of cathcing
all events that occur in the wiki (and this way, when adding a new
event, you wouldn't need any modifications to this class in order to
catch it).
Secondly, I would like to modify onEvent function in the class so that
it uses the simpleClassName of the event occurred in order to log the
event (the eventType would be this simpleClassName...for example
DocumentSavedEvent, AnnotationAddedEvent and so on).
And thirdly i thought about adding one field in AbstractFilterableEvent
called /identifier/ and make all events extend directly this class. And
that /identifier/ would be used in a different way by the events
themselves. But it would be used to retrieve infos about that events.
And so, when logging an event, we could use classname + identifier.
For example
AnnotationAddedEvent + "This is my annotation" .
CommentAddedEvent + "This is my comment" or the number of the comment.
WDYT ?
Stefan
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne