caching seems a better point than creating sessions while generating content...
I think this should be documented/added to the FAQ then. Just didn't why my urls weren't encoded when creating my session via create-session="true", until I found out about the way the pipeline was setup. another thing is to modify the request logicsheet accordingly so that a create-session="true" leads to corresponding code in the generated generator's ;-) setup() method. > -----Ursprungliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]Im > Auftrag von Carsten Ziegeler > Gesendet: Dienstag, 28. Januar 2003 16:42 > An: [EMAIL PROTECTED] > Betreff: RE: cvs commit: > xml-cocoon2/src/java/org/apache/cocoon/transformation > EncodeURLTransformer.java > > > With the recent changes, the encode url transformer does not support > caching anymore. In order to support caching the transformer *must* > know, if a session is available or not; otherwise you might get > wrong cached results or do not have the correct url encoding. > > I would really appreciate it if we could make the assumption > from above so the transformer can support caching again. > Apart from that, you will get problems if you create/destroy a > session when the processing of the xml pipeline has started, > therefore I can only give the advice to create a session > in actions and nowhere else. > > Any other ideas? > > Carsten > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
