-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James,

On 10/12/12 12:18 PM, James Lampert wrote:
> Reversing the flow to
>> od -t x1a web.xml | head -n 5
> 
> shows the correct hex values. But then it shows the character
> values as if interpreting them in EBCDIC.
> 
> This suggests that there's a good reason why "head" and "od" aren't
> in the manuals for QSHELL (the "unix-like" interface that was added
> to OS/400 when Java support was added).
> 
> At any rate, the weirdest part of all is that everything does come
> up properly, even after the exceptions are thrown.

It's possible that he "real" web.xml parsing does not consider this to
be a fatal error. The exception you get is during parsing of the
web.xml for TLDs. IIRC, Tomcat scans web.xml more than once per
deployment. I have not looked at the code, though, so I may be wrong.

Another possibility is that your web.xml doesn't add much, and that
failing to read it doesn't negatively impact your webapp. Do you use
lots of annotations and stuff for deployment, or mostly web.xml?

Something else that might be happening is that Tomcat might be griping
about your (global) conf/web.xml instead of the one for the webapp. I
didn't read the TldConfig code closely enough to see if it loads
conf/web.xml and then your webapp's or what. I suspect that
conf/web.xml is the stock one and so doesn't have anything weird in it
(other than the surprise EBCDIC encoding that seems to jump out at you
when you least expect it).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB4RMgACgkQ9CaO5/Lv0PDV4wCcCmT2KaUTpqrll+sQzPEo1Fc7
TuAAn2dnZOaRUXH/6JUVhrQhv4BLh9Vx
=S6OY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to