-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thom,
Thom Burnett wrote: > First, I found my error and it's (of course) not in any of the code listed. > I had neglected the import statements in the jsp pages. :-( That always helps. So, your JSPs weren't compiling or something? It's odd that it would "work", and yet, not work. > Is there a way to get warnings or error messages when I've made a mistake > like this in the jsp? JSP compilation errors should show up right in the page. When something like this happens, it's best to shutdown Tomcat, kill your "work" directory and any expanded WAR files (usually killing the work dir does that), and re-starting. It doesn't happen often, but sometimes TC goes brain-dead and you just have to lobotomize it. > In my build there was no compiler error or warning. Finding this type of > error by inspection is very time consuming. Certainly, and this is not the way it should work. I suspect that there was a datestamp issue so it looked like the already-compiled version of your JSP was more up-to-date than your new version. Do a clean build and re-start and I think you'll find that TC will report those compilation errors. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFUk1/9CaO5/Lv0PARAjLXAJ9/xvNULda5/ULRXnMbHlImlkzghACcD1PL Ky8IDaNaMIAELu37uNl38Sc= =INdL -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
