We have implemented multiple Object specific observation events in the past (e.g. NavigationCreatedEvent, BlogCreatedEvent, CalendarCreatedEvent etc.).

This could be generalised with (local) Object events, matching on the XClass via an ObjectEventFilter:

The ObjectListener listens on Document events, analyses to object changes and then notifies Object events:

• ObjectCreatingEvent on DocumentCreating/UpdatingEvent if an object is being added

• ObjectCreatedEvent on DocumentCreated/UpdatedEvent if an object was added

• ObjectUpdatingEvent on DocumentUpdatingEvent if an object is being updated

• ObjectUpdatedEvent on DocumentUpdatedEvent if an object was updated

• ObjectDeletingEvent on DocumentUpdating/DeletingEvent if an object is being deleted

• ObjectDeletedEvent on DocumentUpdated/DeletedEvent if an object was deleted

If multiple objects for one class are modified, should multiple Events be thrown? If yes, objNb has to be handed over, e.g. in the data.