I'm not sure what the spec says, but functionally I've been successfully
putting things such as connection pools in the application context for
exactly the same purpose you suggest. I guess you're right with your
suggestion of the jsp reasoning for the bean restriction...
cheers
dim
On Fri, 27
Hi,
Maybe this is a naive question, but why must objects that are attached
to a session, request etc. scope be Java Beans? All requests for one
server are handled by the same OS-process so they share the same memory
(there should be only one JVM per webapp, true?) So virtually any object
can be s
