CookieGenerator.DEFAULT_COOKIE_MAX_AGE is no longer available. Not backwards compatible [SPR-6276]

[spring-projects-issues]

Mark Spritzler opened SPR-6276 and commented

After upgrading to Spring 3.0.0.RC the use of the CookieGenerator.DEFAULT_COOKIE_MAX_AGE constant no longer works. It has been removed from the class. This is breaking our code that worked with 2.5.2

// This probably should be another jira, but I am adding it to the contents here.
Since max age is an int and there isn't a way to set a coookie to never expire. Any value we are setting sets the expiration to that time, but also until session expires. We don't want the cookie to expire, especially if the session expires.

---

Affects: 3.0 RC1

Issue Links:

• CookieGenerator default max age value leads to expiration date back in 1977 [SPR-5835] #10505 CookieGenerator default max age value leads to expiration date back in 1977

Referenced from: commits 9d59db7

[spring-projects-issues]

Mark Spritzler commented

I mean mostly for backwards compatibility. It is very easy to just change to use Integer.MAX_VALUE, which I did.

[spring-projects-issues]

Juergen Hoeller commented

Following #10505, we are not setting Integer.MAX_VALUE as default anymore but rather set no max-age value at all in such a case. For that reason, the constant isn't needed anymore; I've nevertheless reintroduced it in deprecated form for binary compatibility.

Juergen