Guys,
I have any of you used SingleThreadModel in this situation:
Suppose you have a
servlet, or
jsp document that creates many objects, initialises this objects, pass some parameters to these objects, than they do that processing returning some result needed to the page, in other words, this page uses lots of jsp actions (taglibs) and page scoped beans.
What do you think about notifing this page as SingleThreadModel (in servlets by implementing SingleThreadModel, in jsp pages by stating that the page isThreadSafe='false')? doing this, almost all containers will create instances of this page or servlet and pool them to the incoming requests. if we make these page scoped beans instance variables and make all initialization within jspInit() or init() methods do you think that this page creationg and pooling can make this page less havier than executing its service method, allocating memory for the beans, initializing these beans???
Thanks!