Hi Scott. Reading the servlet API documentation shows that passing null as the second parameter of HttpSession::setAttribute() is a valid operation, and should have the same affect as calling removeAttribute():
http://java.sun.com/products/servlet/2.3/javadoc/javax/servlet/http/HttpSession.html#setAttribute(java.lang.String,%20java.lang.Object) It's been the unwritten policy to not make changes to the repository for bugs in specific vendor's software. As adding that null check would actually change the fucntionality of the code below, this change will not be incorporated. Please contact Sybase and have them fix the bug in their app server. - Dan "Scott Tavares" <[EMAIL PROTECTED]> writes: > Sybase EAServer throws an exception if you try to put a null object into the > session. I'm not sure if the is correct behavior and at my best guess, it > probably is not, but this was easier to do then digging into all that. > > Index: src/java/org/apache/turbine/services/rundata/DefaultTurbineRunData.java > =================================================================== > RCS file: >/home/cvspublic/jakarta-turbine-3/src/java/org/apache/turbine/services/rundata/DefaultTurbineRunData.java,v > retrieving revision 1.13 > diff -c -r1.13 DefaultTurbineRunData.java > *** src/java/org/apache/turbine/services/rundata/DefaultTurbineRunData.java 23 Apr >2002 16:05:52 -0000 1.13 > --- src/java/org/apache/turbine/services/rundata/DefaultTurbineRunData.java 28 Apr >2002 18:10:39 -0000 > *************** > *** 1085,1092 **** > { > session.setAttribute( > User.SESSION_KEY, new SessionBindingEventProxy(user)); > ! session.setAttribute( > ! AccessControlList.SESSION_KEY, (Object) acl); > } > > /** > --- 1085,1094 ---- > { > session.setAttribute( > User.SESSION_KEY, new SessionBindingEventProxy(user)); > ! > ! if(acl != null) > ! session.setAttribute( > ! AccessControlList.SESSION_KEY, (Object) acl); > } > > /** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
