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 > -----Original Message----- > From: Bernhard Huber [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 27, 2003 11:12 PM > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: > xml-cocoon2/src/java/org/apache/cocoon/transformation > EncodeURLTransformer.java > > > hi, > > [EMAIL PROTECTED] wrote: > > cziegeler 2003/01/26 23:43:33 > > > > Modified: src/java/org/apache/cocoon/transformation > > EncodeURLTransformer.java > > Log: > > - Fixing caching logic for encode url transformer > > > > - turning off caching, because you get wrong cached content, > *if* the session is created during processing > > > thx for fixing the fix.... > bernhard > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
