I realized with my usage of logFaces-HTTP locally that having the Error objects not be included in the message by default was rather confusing.
The first error object will still be sent using Error.toString which looks like Error: message, whereas everything after that will end up serialized with it's full stack and all.
I realized with my usage of logFaces-HTTP locally that having the Error objects not be included in the message by default was rather confusing.
The first error object will still be sent using
Error.toStringwhich looks likeError: message, whereas everything after that will end up serialized with it's full stack and all.