https://bz.apache.org/bugzilla/show_bug.cgi?id=64023
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Christopher Schultz <ch...@christopherschultz.net> ---
(In reply to Christopher Schultz from comment #5)
> [...] there is no sense in writing the null-valued attribute to the
> serialized session, ever.
... except that in your case, it's writeReplace which is causing the null to be
written. There is no way for the session manager to know that will happen
without speculatively writing every session value to a scratch-area before
writing the object to the real output stream. This could be very expensive, so
it's best to simply leave the nulls in the serialized output.
Fixed in 9f98e7126a26283c9cc260232fd3fbd59900ef29 for 9.0.31.
Fixed in 50dacc525502387a326c3f47de53c0742b8a478b for 8.5.51.
Fixed in 9f98e7126a26283c9cc260232fd3fbd59900ef29 for Tomcat 7.0.100.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
