André van Toly wrote:
Op 24-nov-2005, om 12:49 heeft Michiel Meeuwissen het volgende
geschreven:
Pieter Jelle wrote:
setMaxInactiveInterval(-1) on the session object.
However, since MMBase handles these sessions by itself, I call
<mm:cloud
logon="x" pwd="x" /> when a user logs on to the frontend, after
which a
session is created by MMBase.
As far as I can see there is no way to set the expire time for the
session with an attribute for mm:cloud. I tried catching the session
from the Request object and calling setMaxInactiveInterval(-1) on that
session, but no luck either.
mm:cloud does not do it's own session managment. It uses the default
session of a JSP. With a jsp:scriptlet you should be able to change the
max inactive interval. But you say that doesn't work....
Prolonging session-timeout can be done for the complete webapp in its
web.xml:
<!-- Define the default session timeout for your application,
in minutes. From a servlet or JSP page, you can modify
the timeout for a particular session dynamically by using
HttpSession.getMaxInactiveInterval(). -->
<session-config>
<session-timeout>30</session-timeout> <!-- 30 minutes -->
</session-config>
You're looking for a more permanent sollution, but i thought i should
mention it, just in case.
André, this solution looks ok for what I need (it doesn't really have to
be eternally, it's ok to lose the sessions when the server reboots), but
it doesn't seem to have any impact.
I suppose it basically does the same as calling
getMaxInactiveInterval(), which I already tried without any luck.
So I guess I'll have to use one of the workarounds by setting my own
cookie with a hashed password.
Thanks for all the replies, they have been of great help.
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
