DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11934>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11934 web.xml security-constraint is parsed incorrectly [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2002-09-09 13:42 ------- :-) Well, let's see. The definitions from the Servlets 2.3 Deployment Descriptor DTD is in my opriginal description. According to the security-constraint ELEMENT definition the very first element that optionally may be present is a display-name. Now the actual example, that I just retested with 4.1.10: <security-constraint> <display-name>Constraint Name</display-name> <web-resource-collection> <web-resource-name>Web Reasource Name</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>role1</role-name> </auth-constraint> </security-constraint> With this we have (with 4.1.10 it's slightly different) the exception: SEVERE: Parse Error at line 92 column 25: The content of element type "security-constraint" must match "(web-resource-collection+,auth-constraint?,user-data-constraint?)". org.xml.sax.SAXParseException: The content of element type "security-constraint" must match "(web-resource-collection+,auth-constraint?,user-data-constraint?)". As you see 4.1.10 has somewhat different idea about security-constraint than the specification. It does not want to see display-name there at all. So according to its internal DTD display-name is out of place, but that is not what 2.3 spec is saying. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
