I think it's the same as for request.putValue() and request.setAttribute(), the first one had a minor security bug, so they replaced it with setAttribute(). If you have a JSP that support setAttribute (i know for example that some of my projects don't do that) you should go with the .setAttribute() You should get a "Deprecated APIs are used" warning message under compiling if you use .putValue(), since it's deprecated
//Jan Arenö -----Ursprungligt meddelande----- Från: A mailing list about Java Server Pages specification and reference [mailto:[EMAIL PROTECTED]]För Miao, Franco CAWS:EX Skickat: den 12 november 2001 08:32 Till: [EMAIL PROTECTED] Ämne: session.putValue( ) vs session.setAttribute? what is the differenc between session.putValue( ) vs session.setAttribute? Looks like they are doing the same thing session.putValue sample: http://www.macromedia.com/support/ultradev/ts/documents/session.htm session.setAttribute : http://www.macromedia.com/support/ultradev/content/displaying_session_vars/d isplaying_session_vars03.html Franco =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
