Chuck,
We have tracked down the cause of our encoding problem to an apparent
bug in the Jakarta Response Tag Library. Apparently setting the HTTP
Header Content Type to:
text/html; charset=UTF-8
is parsed as
text/html;charset=UTF-8
The elimination of the space is the killer. The specification calls
for the space, and without it, the charset is ignored. By the way,
this library has been deprecated, do you know what library has
replaced its functionality?
Thank you (and others) for your assistance.
Stephen Caine
CommonGround Softworks, Inc.
