Re: [TOMCAT 4.1.18] StandardSession.setId() found incohesive

[Remy Maucherat]

jean-frederic clere wrote:

Daniel Rall wrote:

Developers, I'd like your input on why setId() has the side effects
that it does, and your suggestions on what solution I should implement
which would be acceptable to both Tomcat 4 and 5, and cleanly usable
by myself.  The issue I filed includes the Valve implementation which
excercises the setId() method, and hacks around its side effects.



TRACKING ISSUE: http://issues.apache.org/bugzilla/show_bug.cgi?id=16822


OBSERVED BEHAVIOR: ManagerBase.createSession() calls
StandardSession.setId() as the last thing it does before returning a
newly created session.

In Tomcat5 I have added a createEmptySession() that should solve the problem.

It's a question of timing. Since I've allowed Glenn's API changes for the deployer in 4.1.19, then it's probably ok to backport your fix now, as we're not trying to stabilize in preparation for a new stable release (yet).

Remy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]