...
Eric James and Unknown User (escowles@ucsd.edu) are proposing that we make our messages more efficient and clear
Observer converts JCR event bus messages to JMS, receives batches (Eventiterator)
We currently trigger an event for only the first property for a node within a batch.
Proposal: just send a single message w/the node id and not the property
We can either report every single property event separately or report a summary of changes
Proposal to make it configurable: summary or separate events or both
Proposal to add property ids to summary message: include which properties changed from the event iterator (requires no additional JCR lookup)
Question from Stefano Cossu: Is it possible to make it easier to add types to a resource when they incur constraints or allow new properties/children?
...