As this patch includes changes to core classes I will need to have votes on this in order to check it into the HEAD branch.

Oliver

Daniel Florey wrote:

Hi,
I've attached an improved version of the event patch. Now the events can be configured in a sophisticated way to enable just the events you are interested in.
You can enable groups of events (e.g. only content events or lock events) or event single methods (e.g. only store content).
The event mechanism can be easily extended by adding custom events without changing any class in the share packages.
I'll write a detailed documentation soon...


Daniel

I hope for some votes so that Oliver can check it in without fear ;-)

Am Donnerstag, 29. Januar 2004 17:10 schrieb Daniel Florey:

Ok,
so this is the patch + the classes I've added.
If someone want's to give it a try, please add the following to your
Domain.xml to check if events are generated:
<slide>
...
  <!-- Event configuration -->
   <events>
       <listener classname="org.apache.slide.util.event.EventLogger" />
       <listener classname="org.apache.slide.event.VetoableEventCollector"
/> <listener classname="org.apache.slide.event.TransientEventCollector" />
   </events>
</slide>

The event logger will log all events using the domain logger.
The event collectors can be added to generate events called
EventCollection. The contain all events that are fired inside one single
transaction. So if you want for example update the search index for all
resources that changed in a transaction you can use the collections for
this.
You can add custom listeners that have to implement one of the listener
interfaces or have to extends the given adapters.
I'll document the package as soon as possible.

Daniel

Am Donnerstag, 29. Januar 2004 15:36 schrieb Oliver Zeigermann:

I'd like to have the proposal on the list as soon as possible :)

Oliver

Daniel Florey wrote:

Hi,
In the last days I've been working on events for slide. It is really
not yet perfect, nor is it well documented - but they are working So
there is a lot of work for me to do.

Nevertheless I'd like to send the patches and classes to the list as
soon as possible to let all of you participate in the earliest possible
stage as I don't want to go into the wrong direction.
What do you think? Send now or do some documentation/implementation
improvements first?

Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


.

--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to