I'd still try it without it, because that's just the way I am ;) I mean, it's obviously there if you're enumerating over it...
----- Original Message ---- From: "Slattery, Tim - BLS" <[EMAIL PROTECTED]> To: Struts Users Mailing List <user@struts.apache.org> Sent: Monday, April 16, 2007 4:04:50 PM Subject: RE: Struts in Servlet 2.4 > > <%@ page session="false"%> > > Whoa. > > "session="true | false" > > Whether the client must join an HTTP session in order to use > the JSP page. If the value is true, the session object refers > to the current or new session. > > If the value is false, you cannot use the session object or a > <jsp:useBean> element with scope=session in the JSP file. > Either of these usages would cause a translation-time error. Now THAT's interesting. This setting is an office standard (I don't know why). It's always worked in WL 7 and WL 8 (and Jboss 3.2.5, for that matter). I put debug print in the JSP page, just before the failing tag. That print proves that the session is available, that the "Contact" bean is there, and that it has the correct value. That being the case, I can't believe that this is the problem. It would require me to believe that the Java code in the page can see the session and its attributes, but because of this setting, the tag cannot. -- Tim Slattery [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
