On Wed, Jan 12, 2005 at 08:34:22PM +0100, Erik Bruchez wrote:
Easy one: you can use the Session Invalidator processor:
<p:processor name="oxf:session-invalidator"/>
This raises a new question:
When is this processor scheduled in a pipeline? What if I want to do some new initializations *after* resetting the session scope?
The order is as follows:
o Run all the processors that do not have any outputs, in the order they appear.
o As usual, run the rest of the processors depending on what pipeline outputs are read.
We are currently working on a formal XPL specification that should clarify aspects such as the order of processing. This will make things clearer, and maybe raise some valid questions about the current execution order.
In your case, you can put oxf:session-invalidator first, and then perform other tasks.
-Erik
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
