Hello! Could you please consider this pull-request?
My app is connected to a error-tracking service - rollbar.com
Rollbar's library is implemented as appender to Logback.
I've forwarded JUL logs to logback, it is not difficult.
But I've found that if my app code was inside CoapHandler#onLoad and it thrown some RuntimeException, it just was forwarded to stdout and rollbar could not have it.
Sure, now I have try/catched my handlers, but I wish also Californium's unhandled exceptions be forwarded to the rollbar too.
Is there any reason to have such printStackTrace calls?
Hello! Could you please consider this pull-request?
My app is connected to a error-tracking service - rollbar.com Rollbar's library is implemented as appender to Logback. I've forwarded JUL logs to logback, it is not difficult. But I've found that if my app code was inside CoapHandler#onLoad and it thrown some RuntimeException, it just was forwarded to stdout and rollbar could not have it. Sure, now I have try/catched my handlers, but I wish also Californium's unhandled exceptions be forwarded to the rollbar too. Is there any reason to have such printStackTrace calls?
Regards, Eugene.