>turning a plain-text stack trace into a XML >or JSON stack trace doesn't seem like a big win.
Some errors have business meaning. 'XML/JSON stack trace' IS a stack trace IIF it is not related to business rules violation. If it is a business rule violation - it is neither 'stack trace' nor HTTP error code. P.S. Do we send explicitly stack traces with SOLR-defined HTTP error codes for OutOfMemoryError, NullPointerException?
