cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: sunrise context question
Date Tue, 20 Aug 2002 08:53:15 GMT
Barbara Post wrote:
> Hello, back to work :-)
> 1. what is the persistence of a sunshine context I define ? i.e. 
> I have one
> pipeline and two xsl :
> map:transform src="xsl1.xsl"
> map:transform type="sunShine"
> map:transform src="other.xsl"
> map:transform src="xsl2.xsl"
> map:transform type="sunShine".
> I want xsl2 to use something stored in context by xsl1. If I use
> "MyContext", will it work ?
Yes, but be carefull with SAX event handling, which means you must ensure
that the first sunShine transformer creates the context and stores the
information before you try to read this.

> 2. Is "sunRise" context reserved or can I write into ?
It is reserved, by you can write into it.

> 3. if now I have two pipelines with a redirect-to for example, how is
> context persistence managed ?
A custom context requires a session on the server. The context is "stored"
in the session, so as the redirect-to preserves the session, the context
is still available.

> In fact I tried to use a java bean and xalan java extension, but how can
> xsl2 know which bean (created by xsl1) to use ?
> I need to pass info that I cannot get directly when I am in xsl2, 
> so I need
> to store them as I am in xsl1...
If you don't use a redirect and only want to pass information "temporarily"
in the processing of one pipeline, you can use the "temp" context - this is
a reserved context which acts like a custom one with the exception that no
session is created to store the context and the context is only valid for
one pipeline - when the pipeline is processed the context is deleted


Carsten Ziegeler     Chief Architect     Open Source Group, S&N AG
             Cocoon Consulting, Training and Projects

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message