Hi Jim, you are correct. the answers are both yes.
You cannot checkin a node with pending transient changes [0]. You first need to save it, which will fire events for those changes. Regards Marcel [0] http://www.day.com/specs/jcr/2.0/15_Versioning.html#15.2%20Check-In:%20Crea ting%20a%20Version On 20/02/15 00:39, "Jim.Tully" <[email protected]> wrote: >I¹ve come up with something unexpected, and would like some clarification. > >I¹ve registered an event listener for property changes on nodes that are >mix:versionable. As expected, an event is fired whenever a node with >property changes is saved. However, the event frequently fires before >the node is checked in, which means that trying to retrieve the node when >the event is fired results in the ³old² version of the node being >retrieved. > >Two questions: >Is my assumption that a node should be saved before being checked in >correct? >Should the event fire if the check-in hasn¹t occurred? > >I suspect that the answers are both yes, but confirmation would be >appreciated. > >Thanks, > >Jim Tully >
