Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 93186 invoked by uid 500); 18 Apr 2001 20:32:29 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 93139 invoked from network); 18 Apr 2001 20:32:26 -0000 Message-ID: <3ADDF959.A39391BD@apache.org> Date: Wed, 18 Apr 2001 16:30:17 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [c2] problem with actions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Donald Ball wrote: > > On Wed, 18 Apr 2001, Berin Loritsch wrote: > > > > generaly nesting of actions is (as I understand it) something like > > > if-then-else clause, "if-then" -> go deeper, "else" go to next element at the > > > same level in the tree, am I wrong ?? > > > > You've pretty much got the concept. > > but it's not if/else - because the else branch is hit regardless, right? > that is to say > > > > if branch > > else branch> > > > if the something action return non-null, the if branch and the else branch > are hit, otherwise just the else branch is hit. right? to do a real > if/else branch, you have to use a selector, yes? If you redirect, or completely specify a pipeline before reaching the next element, then Cocoon will execute that. Otherwise, the other execution will happen regardless. For real selection, then use a selector. --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org