Re: Strange request.setAttribute() problem

2003-07-28 Thread Charles So
Thx Mike!!! I got the problem fixed!!! Thx! On Tuesday, July 29, 2003, at 01:22 AM, Mike Curwen wrote: <%! private int itemnumber = -1; %> Using a ! makes it scoped globally to all requests. If you check the source file of your JSP you'll see it's declared outside the service method. That'

RE: Strange request.setAttribute() problem

2003-07-28 Thread Mike Curwen
inal Message- > From: Charles So [mailto:[EMAIL PROTECTED] > Sent: Monday, July 28, 2003 12:11 PM > To: Tomcat Users List > Subject: Re: Strange request.setAttribute() problem > > > > > > I believe each browser (Opera, Netscape, or whatever) *creates* a > uniq

Re: Strange request.setAttribute() problem

2003-07-28 Thread Charles So
mnumber now = 0 [correct] Browser B now displays BillingShippingHome.jsp itemnumber = 0! [should be -1] What gives? -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 07:53 To: Tomcat Users List Subject: Re: Strange request.setAttribute()

RE: Strange request.setAttribute() problem

2003-07-28 Thread Moraes, Fabio
em +55 21 3088 9548 -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 07:53 To: Tomcat Users List Subject: Re: Strange request.setAttribute() problem This is the correct behavior. In this scenario, you are operating on the requ

Re: Strange request.setAttribute() problem

2003-07-28 Thread Tim Funk
This is the correct behavior. In this scenario, you are operating on the request, not the session. request.getParameter --> Get stuff from the query string (or input stream if post) - a per request thing request.setAttribute --> Set an attribute in the life of this particular request -Tim Cha