* Sebastian Klamar [2004-01-10 18:49 +0100] wrote:
<map:transformer type="bla"/> <!-- here the session attribute is generated --> <map:transformer type="myexaminer"/> <map:select type="session-attribute"> <map:parameter name="attribute-name" value="foo"/> <map:when test="okay"> <map:transform type="bar"/> <map:otherwise> <map:transform type="bar2"/> <map:otherwise> <map:select>
Given my example, is it right that the selector is evaluated at the beginning of the pipeline (after the match when the pipeline is constructed), that means BEFORE bla and myexaminor transformer? Why that?
Yes, first any matchers/selectors (they can be infinitely nested) are "executed" or better "evaluated", then the Generator->Transformer*->Serializer pipeline begins processing. So, your session attribute selector cannot rely on any side effects of the generator and transformers which preceed it when reading the sitemap. I think I've already given the answers about why but once again, a pipeline generator->transormer->serializer is generally thought of like the "model" and "view" of the well known "MVC" pattern and therefore are not designed to be used as a "controller". You have matchers, selectors, flow and actions for that.
Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
