> If your servlet container has a broken implementation of > get/set attributes on an HttpSession, there is nothing that > Struts can do to protect you from problems ... even providing > synchronized locks around get/set calls would still not avoid > problems caused by application logic, or logic inside the > container itself, that would bypass it. > > Sounds like you need to get after the folks providing your > container to fix this.
since the Servlet spec leaves it up to the webapp to implement thread safe setting and update of session objects I don't think I will find a safe container out there :-( Sure, struts can't save you from this, but struts could give you tools to right cleaner webapps. And it would be 20 lines of code. Regards Leon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
