Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-users@xml.apache.org
Date: Tue, 22 Jan 2002 12:26:36 +0100
From: Christian Haul <haul@dvs1.informatik.tu-darmstadt.de>
To: cocoon-users@xml.apache.org
Subject: Re: question about failed actions
Message-ID: <20020122122636.F21907@london.dvs1.informatik.tu-darmstadt.de>
Reply-To: haul@informatik.tu-darmstadt.de
References: <3C4C8102.3000404@terralab.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <3C4C8102.3000404@terralab.com>;
 from bryan@terralab.com on Mon, Jan 21, 2002 at 02:58:42PM -0600
Organization: Databases and Distributed Systems Group,
 Darmstadt University of Technology

On 21.Jan.2002 -- 02:58 PM, Bryan Murphy wrote:
> 
> Now, what do you do if you want to action fails, yet you still want to 
> modify the pipeline based on that failed action?  Well, of course, you 
> could always write the action as a selector.  But what if you want to 
> reuse some code already written as an action?  You could of course write 
> a wrapper selector, but I don't see why that should be necessary.  Why 
> not something along these lines::

Bryan, there's another way to communicate with the rest which is
request attributes. So set such a beast in your action containing the
results and have your other components act accordingly. If you need to
change the pipeline it would mean to use a selector that works on
request attributes. There's one supplied with Cocoon. 

	Chris.

-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
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: <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail: <cocoon-users-help@xml.apache.org>