Why don't methods in JsonPath throw PathNotFoundException with the not-found path in the message?

[erizzo-cfa]

The set, put, map, add, delete methods in JsonPath all throw PathNotFoundException with no details in the exception message. This make it very hard to troubleshoot, not having any context to go with the error. Is there a reason the default PathNotFoundException is used instead of providing details in the exception message? Other places in the code include details about the offending path.

[ghostg00]

+1