I have a jsp where I use jsp:useBean. I only get the exception in the JSP after I try to update the bean in the session data (in a struts action class). Should beans only be read only, set up once never to be changed ?
I am getting this error on Jrun4.
If I initialize the bean with some initial values things work fine. It is only after I do an update to the session data that I get the error.
Now I see why sun came up with the ejb session beans. You know they work and they are reliable.
Are their undocumented scope restrictions on the jsp:useBean tag ? What application servers does this work best with.