Changing the SessionAware interface would certainly break backward
compatibility, plus it would affect action testability.
If you don't like the downcast to SessionMap, I would rather consider
creating an additional interface, something like:
public interface SessionMapAware {
public void setSessionMap(SessionMap map);
}
then you can safely add any methods you like to the SessionMap class.
Gabriel
2007/7/1, Srinivas.N. <[EMAIL PROTECTED]>:
Wouldn't it be cleaner if
(1) the setSession(Map session) signature of SessionAware was changed to
setSession(SessionMap session) and
(2) the implementation of the invalidate method on internally took care of
dealing with already timed out sessions? (if one really wanted to know if
the session was already invalidated, it can probably return that as a
boolean)
- Srinivas
newton.dave wrote:
>
> --- Ray Clough <[EMAIL PROTECTED]> wrote:
>> Then to invalidate the Session, I do this [code]
>
> Oh, I had no idea! If you have wiki karma maybe add a
> FAQ entry, otherwise with your permission I'll do it.
>
> d.
>
>
>
>
>
____________________________________________________________________________________
> Moody friends. Drama queens. Your life? Nope! - their life, your story.
> Play Sims Stories at Yahoo! Games.
> http://sims.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/-S2--Session-Invalidation-through-SessionAware-interface-tf4003103.html#a11385428
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
