This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Please be sure to take the time to compose descriptive subjects for your posts. You will attract people who will can give you better and faster answers when your posts have good, descriptive subjects. For more information, please click this link ⇒ UseAMeaningfulSubjectLine.
Using a title of "jsp" in a forum completely dedicated to questions on JSP isn't going to attract the attention of those who can best help you.You can change your subject line by clicking the button on your post.
Ankit Tripathi wrote:By default JSP is not thread safe.
I wouldn't phrase it like that. Many JSPs are thread-safe without the developer doing anything to make them so - simply because they do not use shared mutable state. However, I'd agree to a statement like "Any given arbitrary JSP can not be considered thread-safe until it is inspected and found to be so (or made so)."
Indeed, if JSPs are written to modern standards (in other words, no scriptlets and no Java code within them), it's rather hard to make them non-thread-safe. Modifying properties willy-nilly on shared scoped variables in session and application context is about the only place you could get yourself into trouble.