At this moment, this defect still needs some verification and qualification as
to what versions it applies to.
I noticed this using the latest Java 5 standard implementation of XPath capability.
If you feed some garbage string to an XPath object's "compile()" method, it will
throw (as expected) an XPathExpressionException. But when you call getMessage()
on that exception, it returns null. What I would expect here is a message
identifying what went wrong during the parsing or compiling, even if it is
Generally speaking, exceptions with no message are reasonable only if the class
name itself is all you need to know. In this case, anyone trying to craft an
XPath expression will need more information than just that it doesn't compile.
Where was the error? What type of error was it? What token was unexpected? Etc.