An example error message:
I think this is a don’t fix. The entities are correctly escaped XML inside an XML document Element. When they are displayed inside of any of the numerous HTML error pages generated by Hyrax the escaping is correctly moved. Removing the content escaping inside the XML document will just result in a broken XML Error response as it will un-parseable.
but you did check in a change for this, yes? Removing the content escaping inside the XML document will just result in a broken XML Error response as it will un-parseable. Yes, of course. My point was to find a way to make messages people can understand.
I did not. There was nothing to change. The JSP error pages produce the correct HTML content. The example error message above is an excerpt from a BES XML error message which is processed by the front end JSP error pages and the result is a readable message. If you are seeing this when using besstandalone or bescmdln then if you want that output to be different we have to change that code. And I do not recommend making that change because it is very very useful for besstandalone and bescmdln to spit out exactly what is transmitted to the OLFS.