[Bug 64023] New: Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 Bug ID: 64023 Summary: Session serialization does not support values that (de)serialize to null Product: Tomcat 9 Version: unspecified Hardware: PC OS: Li

[Bug 64023] Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 --- Comment #1 from Christopher Schultz --- We'll look at this, as this should not fail, but there is another way to fix this perhaps faster: use a wrapper object that has a single transient member instead of writing null in writereplace(). --

[Bug 64023] Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 --- Comment #2 from Bernhard Frauendienst --- I'm afraid that won't help, because the attribute in question belongs to a session-scoped spring bean, and I need the session to contain null in order for the factory method to be invoked anew after

[Bug 64023] Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 --- Comment #4 from Christopher Schultz --- Created attachment 36926 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36926&action=edit Don't put null-valued attributes into the session attributes when deserializing -- You are receiving

[Bug 64023] Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 --- Comment #3 from Christopher Schultz --- Gotcha. I have a patch for this ready to go that I'll attach to the bugin case you want to build your own for testing. -- You are receiving this mail because: You are the assignee for the bug. -

[tomcat] branch master updated: Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=64023

This is an automated email from the ASF dual-hosted git repository. schultz pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/master by this push: new d9f243a Fix https://bz.apache.org/bugzilla/sho

[Bug 64023] Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 --- Comment #5 from Christopher Schultz --- Fixed in d9f243aa49. I'm leaving this open because I think it makes sense to avoid serializing the null values in the first place. Having the null-check in the deserialization process is a good sanit

[tomcat] branch 8.5.x updated: Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=64023

This is an automated email from the ASF dual-hosted git repository. schultz pushed a commit to branch 8.5.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/8.5.x by this push: new 50dacc5 Fix https://bz.apache.org/bugzilla/show_

[tomcat] branch 7.0.x updated: Fix https://bz.apache.org/bugzilla/show_bug.cgi?id=64023

This is an automated email from the ASF dual-hosted git repository. schultz pushed a commit to branch 7.0.x in repository https://gitbox.apache.org/repos/asf/tomcat.git The following commit(s) were added to refs/heads/7.0.x by this push: new 9f98e71 Fix https://bz.apache.org/bugzilla/show_

[Bug 64023] Session serialization does not support values that (de)serialize to null

https://bz.apache.org/bugzilla/show_bug.cgi?id=64023 Christopher Schultz changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

javax -> jakarta rename

I've watched with great interest the recent list discussions surrounding javax -> jakarta renaming and the draft release numbering plan. I'm curious: Would the Tomcat team consider making a Tomcat release that supports BOTH the javax and jakarta package names? Please hear me out before dismiss