The reason you use setAttribute or putValue is due to differences in the
servlets spec. The 2.2 spec. depractaed putValue in favour of setAttribute,
to a) make it more 'bean' like, and b) to bring it in-line with the other
classes in the spec. (Tomcat is 2.2 compliant JSWDK is at best 2.1)
As to the question about ServletContext - the interface will be the same
regardless of the engine used (assuming they all work to the same spec), the
internal implementation will obviously vary,
Kevin Jones
DevelopMentor
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of espen dall�kken
> Sent: 20 January 2000 12:39
> To: [EMAIL PROTECTED]
> Subject: Application management in JSP
>
>
> I read in an article that you can manage applications in a ASP
> like fashion
> in JSP using the ServletContext object.
> My question is if the ServletContext object is implemented in the same way
> in most servlet engines or if there are differences simular to the
> differences in using the HttpSession object. Using the HttpSession on the
> Tomcat engine I had to use get and setParameter, but in JSWDK 1.0.1 I have
> to use set and putValue, so is the ServletContext object handled
> differently
> also ?
>
> Jsp for the ASP programmer article:
> http://www.asptoday.com/articles/19991022.htm
>
> | || ||| || r a z o r f i s h
> espen dall�kken
>
> ==================================================================
> =========
> 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
===========================================================================
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
