Hi,
I tried some user and role exceptions in both tradional and reactive. Found some unexpected behaviour.
specific user exceptions
loose specificity across producer-consumer relation. You couldn't even write a handler in consumer if you wanted, as the exceptions don't have the option of being made public, so the consumer module doesn't know about their existence. In Traditional they get caught in UserException Handler, in Reactive in AllExceptions Handler. Very sad that there isn't even consistency.
Not Registered exception
very good in traditional, gets handled by notRegistered handler, even if raised in producer module. Very disappointing in Reactive, both notRegistered raised in own module as in other module, get handled by SecurityException handler. In other words, there is never a point in using the notRegistered handler in reactive.
not role X exception
It is possible to write a notRoleX handler, even if this role is from producer, as it can be made public. So this looks promising, and in reactive it also works as expected, unfortunately, in traditional it doesn't, it gets handled by the more generic notRegistered handler if set in a producer module, which really doesn't make sense, as user is registered, he just doesn't have the right role.
conclusion, beware when setting up some fancy exception handling, as things might not work quite as expected.
Dorine