We have html:submit fields that have XML Entities for German Umlaut in the value of the value attribute, for example
<html:submit property="..." value="Zurück"/>
The ü XML Entity should display German Umlaut ü on the page but instead the XML text is "Zur%uuml;ck" without replacing the XML Entity ü with German Umlaut ü.
The reason is that during rendering of the value of the value property the TagUtils.getInstance().filter(..) method is called which calls ResponseUtils.filter(). In ResponseUtils.filter() the input string is examined and if a '&' is found it is prepended with &. So in my case the input value of ResponseUtils.filter is "Zurück" and the return is "Zur&aml;ück" and as a result the ü XML Entity is not replaced with the German Umlaut.
From my point of view, the ResponseUtils.filter class should have a list of valid XML entities that are accepted and not escaped, so that the result string does not contain the XML Entity but the expected text.
We have html:submit fields that have XML Entities for German Umlaut in the value of the value attribute, for example
<html:submit property="..." value="Zurück"/>
The ü XML Entity should display German Umlaut ü on the page but instead the XML text is "Zur%uuml;ck" without replacing the XML Entity ü with German Umlaut ü.
The reason is that during rendering of the value of the value property the TagUtils.getInstance().filter(..) method is called which calls ResponseUtils.filter(). In ResponseUtils.filter() the input string is examined and if a '&' is found it is prepended with &. So in my case the input value of ResponseUtils.filter is "Zurück" and the return is "Zur&aml;ück" and as a result the ü XML Entity is not replaced with the German Umlaut.
From my point of view, the ResponseUtils.filter class should have a list of valid XML entities that are accepted and not escaped, so that the result string does not contain the XML Entity but the expected text.