One intresting concern was that if the backend throw their own custom BackendInvalidationException, that the frontend experienced an unmarshalling error trying to deserialize that BackendInvalidationException instance. Therefore, it made sense that both the frontend and backend used the same Exception class for invalidation errors - and it was in the shared classpath.