Summary: | NullPointerException processing Realm in Context | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | David Goodenough <david.goodenough> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 5.5.9 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other |
Description
David Goodenough
2005-09-28 12:14:45 UTC
Please go and try the GlassFish project, instead of of wasting real developers time with really stupid reports like this. Believe me, you won't be missed :). XML parsing is, was, and always will be case-sensitive. Now actually read the FM, and specify your Realm as className="...". OK, so there was a simple mistake on my part which mis-encoded an attribute, that is fine and obviously my fault. BUT, this should NOT have lead to a NullPointerException, and the error messages are totally misleading as they state that the problem is in the "default web.xml" when actually it was is the application specific context file. The following has been added: When a web.xml parsing error occurs, - ContextConfig will report the full web.xml file URL that it was trying to parse - ContextConfig will report the line number and column number where the error occured, assuming the SAXParseException contains that information. - ContextConfig will log the full stack trace (this is already happening) The following was already available: - Setting DEBUG-level logging on the ContextConfig class or the catalina startup package will cause a logging message to be emitted from processContextConfig for each context with its name/URL. The following was added: - Setting DEBUG-level logging on the ContextConfig class or the catalina startup package will casue a logging message to be emitted from applicationWebXml before it starts parsing the web.xml file with its full URL. |