One solution would be to continue to use a second transformer, but instead of setting your variable, foo, in the first transformer as a session variable, have the first transformer create an XML element which contains the value for foo. Then, the second (xsl) transformer can use an if statement on the value of foo.
-----Original Message----- From: Sebastian Klamar [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 4:53 AM To: [EMAIL PROTECTED] Subject: Re: Why a Selector is evaluated at beginning of pipeline? Geoff, thanx for your answer. * Geoff Howard [2004-01-12 03:56 +0100] wrote: > 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. But the controller, say matchers, selectors, flow and actions, all they have no access to the model (except the new PipelineUtil.processTo{DOM,SAX})! So how to achieve control of flow? This border results in workarounds like using xinclude to call the next pipeline step (see Conal's first mail in the father thread) or my currently preferred way: after the examination in a transformer, I store the result via WriteDOMSessionTransformer, evaluate the status in my flow script and afterwards call the next pipeline (using the SessionAttributeGenerator). This leads to a fragmentation of the pipeline (as in my example) to 3 pipelines (one for processing till evaluation, the other two for the map:when and map:otherwise) :-( IMO this is not a good solution. You are right, flow script is destined for controlling the flow, but I find my �wish example� better because it better shows flow of data compared with the fragmentation into 3++ pipelines and using session attributes (or the new xmodule). Sebastian -- Die letzten Worte... des Ehemannes: "Ok!" (Auf die Frage: reparierst Du mal das B�geleisen, Schatzi?) ************************************************************************ PGP Key: 0x1E727CE6 / 9085 48BD 8332 4BFC D80C A6CF D162 20BB 1E72 7CE6 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
