There's probably about half a dozen ways to do this. Perhaps one of
the simplest is just to create your own caching generator and use aggregation
(with any other XML you may need) in the pipeline.
In the
generator you'll need to implement the setup method to see the objectModel,
something like the following:
private gunk mySessionData = null;
public
void setup( SourceResolver resolver, Map objectModel, String src, Parameters
parms )
throws ProcessingException, SAXException, IOException { if (mySessionData == null )
{
super.setup(
resolver, objectModel, src, parms );
Request request =
(Request)ObjectModelHelper.getRequest(objectModel);
Session session = request.getSession(false); if (session != null) { //
save a pointer to your session data for use in the generate
method
mySessionData = ....
} }
} Now in
your generate method just pick up whatever data hangs off of "mySessionData" and
away you go
-----Original Message-----
From: Christian Kurz [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 17, 2002 11:26 AM To: [EMAIL PROTECTED] Subject: ServerPageAction: XMLFragment reuse in XSL transformer Hello cocoon-users,
|
- RE: ServerPageAction: XMLFragment reuse in XSL transform... ROSSEL Olivier
- Re: ServerPageAction: XMLFragment reuse in XSL tran... Christian Kurz
- Re: ServerPageAction: XMLFragment reuse in XSL tran... Hunsberger, Peter
- Re: ServerPageAction: XMLFragment reuse in XSL ... Christian Kurz
- ServerPageAction: XMLFragment reuse in XSL transfor... Christian Kurz
- RE: ServerPageAction: XMLFragment reuse in XSL tran... Hunsberger, Peter
- Re: ServerPageAction: XMLFragment reuse in XSL ... Christian Kurz
- cvs-version Wolle
- Re: ServerPageAction: XMLFragment reuse in XSL tran... Christian Kurz