David Smith schrieb:
Ok... you are wrong. An & by itself is wrong.
It's a hack, but you end up having to do &
Seems like these should be preserved instead of decoded when the
output is x/html. I can see it getting real ugly if you have to
process a document through several transforms. But that's just my
opinion.
-David
Leon Rosenberg wrote:
correct me if i wrong, but isn't & forbidden in xml anyway?
Leon
On 2/14/07, Stefan <[EMAIL PROTECTED]> wrote:
Hello,
for sure, the problem is well known. jspx pages turn the "&" in
simple "&" which causes a lot of problems. See
http://www.lunatech-research.com/archives/2006/01/20/jsp-xml-rant
for details.
How to avoid this problems? Or just live with it?
Thanks
--
Stefan
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
So to avoid the "double-amp" I have to write a filter, which transforms
a single "&" in "&" I'll try that but it is a strange behavior of
servlet engines. Usually you use jspx to generate XHTML or XML, as I
need to do.
Thanks for the participation
Stefan
--
Stefan
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
