The Servlet 2.1 spec says, under ServletContext.setAttribute and ServletRequest.getAttribute # # Attribute names should follow the same convention as package names. Then the JSP 1.0 spec says in 2.13.1, paragraph 1: # # A <jsp:useBean> action associates an instance of a Java # object defined within a given scope available with a given # id via a newly declared scripting variable of the same id. These conflict nicely. Even when the scripting language is Java, the proposed attribute naming convention doesn't work. (Fwiw, the servlet 2.2 spec maintains this recommendation for ServletRequest attributes, but I don't see a mention of it for ServletContext attributes.) Is this a known inconsistency? There is little choice but to ignore the servlet spec, as far as I can see, though that does raise concerns of naming clashes, particularly with specific JSP implementations. John L =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". FAQs on JSP can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html
