Orders have been defined for some of nuxeo 5 listeners, please feel
free to add it on missing ones if you think it is important.
For now, listeners without any order set are notified first, then
notifications to the runtime layer are performed, then document
related notifications (uid generation, dublincore...), and jms
forwarding is done almost last: the context map attached to the
document is cleaned at the end.
I wasn't sure were to add versioning related listeners so their order
is not set right now.
In the interest of a refactoring in the future where we'd use
before/after dependencies instead of integers, could you please explain
why the given events have to be run before or after others? Could you
reformulate the ordering in terms of before/after ? For instance,
document-related must be after runtime because XXX, or JMS must be after
document because YYY.
Note that there is no dependency between existing listeners so the
ordering is more semantic than really needed here.
The runtime layer is notified first with no real reason because afaik
there are no listeners defined on it yet. I'm not sure for what purpose
it has been defined so I'll let others answer.
Jms forwarding is done near the end because it sends asynchronous messages.
The context map is cleant at the end because the map content needs to be
accessed by other listeners.
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
