Cacheing of Portlet Content?
We've programmed a portlet-channel that calls the banner database and retrieves/displays a students status.
For the most part it works well, but occassionally we get users complaining the that system gave them different data (applicants saying they see an "accepted" status, and then a few minutes later seeing the correct status of "still processing").
Has anyone else seen a behavior like this? None of the data is stored in a static variable, so there shouldn't be hold over from a preivious instance of the portlet. -- could somehow the whole portlet instance be cached and showed to the next user to login?
tracked to instance variables
http://www.coderanch.com/t/451902/JSP/java/session-mix-up
Still have to update the code to see, but it looks like we were being a little too generous with the use of instance variables. Didn't know each servlet wasn't a whole new instance.
Guess we'll have to read our manuals better
, but intuitively, it seems to me servlet instance variables behave in the expected manner of a static variable.