I have a general idea of what you're talking about. Can you be more precise. How can I bufferize the stages ?
> >provided it is not needed > >for the following stage any earlier than the tag that causes the > >parameter to be set.
I didn't understand that.
wrote:
On 05.Sep.2003 -- 03:30 PM, Reinhard Poetz wrote: > > From: Lionel Crine [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 05, 2003 1:33 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Easy way to transformer parameters into a pipeline ?? > > > > > > At 10:54 05/09/2003 +0200, you wrote: > > >Do you have two different pipelines and you want to exchange > > parameters > > >or do you have one pipeline and you want to pass *within* it? > > > > The second case is the most important. (on pipeline). > > > > > > I supposed that in the second case I can use <map:file></map:file> > > > > > > So any idea ? > > > I would use the request object: > > request.setAttribute( "attrName", object );
Passing parameters down the pipe out-of-band (IOW by not adding a tag that travels down the pipe in-band like the rest of the data) is a dangerous thing as you have no idea about the actual schedule. Usually, a SAX event callback is completely propagated down the pipe before the next callback is invoked. However, by using buffers one pipeline stage may complete before the next is started.
So, you can use request attributes (or session attributes, an external file, ...) to pass parameters out-of-band, provided it is not needed for the following stage any earlier than the tag that causes the parameter to be set.
Chris. -- C h r i s t i a n H a u l [EMAIL PROTECTED] fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
--------------------------------------------------------------------- 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]
