We are currently upgrading an application to Axon 3.1 (from 3.0). We have a number of event handlers that have an argument of type UnitOfWork (we want to publish a message over a web socket after commit). The event handlers are assigned to tracking event processors. Before Axon 3.1, the event handlers were called but since 3.1 they are not. After some (ok, honestly, quite a bit of :)) debugging, I found out that the org.axonframework.commandhandling.CurrentUnitOfWorkParameterResolverFactory indicates a mismatch with the event message because CurrentUnitOfWork.isStarted() evaluates to false.
Not sure if this is an issue, or just intended behavior. The UnitOfWork is not listed in the docs as a supported parameter type, but is was in fact working in Axon 3.0. It would be very nice if we could keep using is in tracked event handlers.
Curious what you guys think, so any feedback is much appreciated
Martijn van der Woud