Hi, Billy,
When you ask a question, you should read the answers (although they
sometimes contains mistakes like telling you to make your method protected).
You didn't solve your problem. You only found a workaround. You should
search why synchronizing your method apparently solves the problem. When you
find this, you should try to rewrite it in such a way that synchronizing the
method would not be needed.
Pierre-Yves
-----Message d'origine-----
De : A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]De la part de
Graham, Billy
Envoy� : mercredi 19 septembre 2001 11:24
� : [EMAIL PROTECTED]
Objet : Re: Inconsistent behaviour in Servlet output
Thanks to all!
As requested by a few people, I was just about to send a sample of my
'dodgy' code when I read an e-mail suggesting I use a 'Protected' doGet()
method. I tried this but it didn't work - however it did remind me about the
'Synchronized' keyword (as I stated earlier, I am new to java but have read
extensively on it - so somewhere in the basement of my brain the facts are
there). I made the doGet() method both Synchronized and Protected and Hey
Presto! everything works - no more dodgy variables. I still don't quite
understand what was changing the variables as there was only one request
being made to the server for the servlet, though as I outlined in an earlier
e-mail the server feedback seemed to indicate there were 2 Get() requests
being made. Anyway - it's working A OK now, so I'm off for a coffee!
Many thanks for all the contributions.
Best Regards, Billy Graham.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
