Workaround with cookies

Hi everyone!

Since OPS will be integrated into a more complex webapp, there is needed the main session to be kept alive while working on xforms screen, and to be able to handle user-side cookies. This means that session must expire exactly when enclosing will do. And, pushing a LOGOUT button must invalidate the main session too. I guess the last is possible simply via calling a JSP servlet. Tried but doesn't work! Also, is there possible to access webapp's beans and other stuff?

Regards, Al.Haziz.



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 3/28/06, [hidden email] <[hidden email]> wrote:
> Since OPS will be integrated into a more complex webapp,
> there is needed the main session to be kept alive while working
> on xforms screen, and to be able to handle user-side cookies.
> This means that session must expire exactly when enclosing will do.

PresentationServer stores information in the standard servlet session.
So if you invalidate the session in your code, this should invalidate
the PresentationServer session, because it should be the same session.
Is your application deployed in the same war file?

In our code, to invalidate the session we are simply doing a
session.invalidate(). If you want to do this in a pipeline, you can
call the session-invalidator processor.

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws