Frank wrote:
I copied the replace function from the source code into a test app and tried passing a \n character to be replaced and it worked fine, so there is nothing wrong with the replace function.
You can't stick Java escape conventions into JSPs like that. What I'd
suggest you do is add
Hans Bergsten wrote:
Mixing different versions can cause all kinds of problems, so use
only these combos:
JSTL 1.0
- A JSP 1.2 or 2.0 container
- A servlet 2.3/JSP 1.2 web.xml file
- A JSTL 1.0 or 1.1 implementation, e.g., Standard 1.0 or 1.1
- JSTL 1.0 taglib URIs, e.g.,
There's probably a few ways to do this:
c:set var=msgbean:message key=my.message//c:set
c:out value=${msg} escapeXml=false/
Quoting Menke, John [EMAIL PROTECTED]:
i am using the messages tag in a struts application and it doesn't let me
include html that is parsed correctly when displayed