> > On Thu, 29 Nov 2001, Alexander Smirnoff wrote: > > > How to invalidate session after pipline executes? > > > > If I put <map:act type="session-invalidate"/> inside pipline no matter > > where, it executes invalidation before execution of pipline. > > This is itentional. Look, the sitemap is collecting components > (Generator, Transformers, Serializer, Reader) to build up a pipeline. This > is done by use of Matcher, Actions, and Selectors. Now, do you see when
I've got the idea. I think it's a simplistic approach. Matchers, Actions and Selectors must me used as construct components to build a transformation tree (simple analogy with Abstract Semantic Trees), but not as constructors to produce only one pipe. This way you could implement action in any part of pipeline. > each components are executed? The later ones need to tell the sitemap > what's the case while the former will produce the resource. > > Matcher, Actions, and Selectors are alway executed as soon as they get > evaluated by the sitemap engine whereas the other components (Generator, > Transformer, Serializer, Reader) gets executed when a pipeline is complete > (usually when the sitemap engine selects a Serializer or a Reader). > > > If I put it > > after <map:serialize/> - it never reaches the invalidation code because > > there is funny > > This case should also be explained now. > > > > > if(true) > > return true; > > This is because of the code generation using xslt. There are places where > a xslt template should write a return but previous templates already > produced a return and thus one is tagged as "not reachable code" and will > result in compilation errors of the sitemap. That's why I don't like "preprocessing" approach with XSLT to build sitemap. > > Giacomo > > > > piece of code before invalidation action... > > > > Any Ideas? So, is there workaround way to invalidate Session? Calling invalidate() at the end of XSP - no good. Making custom SessionInvalidate transformer - sounds ugly... > > > > Thanks, > > Alex. > > > > > > --------------------------------------------------------------------- > > Please check that your question has not already been answered in the > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > > For additional commands, e-mail: <[EMAIL PROTECTED]> > > > > > > > > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
