DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36541>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36541 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-07 22:40 ------- Well at least ApplicationContext.java and ApplicationRequest.java are synchronizing their attributes in both cases put/get. So, that is one thing not to worry about, but there are other issues, and I'm betting the EL accessing code isn't synchronizing because looking at the code for jasper2 and looking at the runtime file PageContextImpl.java in the scoped getAttribute which calls the scoped doGetAttribute it does not synchronize the code either. So, basically what that says is if a JSP developer were to use jsp:useBean and creates a session bean then there are going to be problems because as soon as this happens an unsynchronized call is taking place. Thing that makes this debate over whether to change it or not silly is that in the scoped calls the application and request code is already synchronized at the class level so synchronizing only on the session at this point seems weird. Regardless....if this tiny three line change doesn't take place then there are more lines in Tomcat that apparently need to be changed, because this bug causes other issues. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
