cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helma van der Linden (JIRA)" <>
Subject [jira] Reopened: (COCOON-492) [PATCH] Caching problem with XSP, XSL and cocoon pseudo protocol
Date Tue, 25 Oct 2005 13:47:55 GMT
     [ ]
Helma van der Linden reopened COCOON-492:

reopened just to set the resolution to fixed

> [PATCH] Caching problem with XSP, XSL and cocoon pseudo protocol
> ----------------------------------------------------------------
>          Key: COCOON-492
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: - Components: Sitemap
>     Versions: 2.0.5-dev (Current CVS)
>  Environment: Operating System: All
> Platform: All
>     Reporter: Tuomo Lesonen
>     Assignee: Cocoon Developers Team
>     Priority: Blocker
>  Attachments: SitemapSource.patch
> Several cocoon users have reported a caching problem when
> using cocoon: pseudo protocol with ServerPagesGenerator. Here's an example
> pipeline:
> <map:pipeline type="noncaching">
>   <map:match pattern="foo">
>     <map:generate type="serverpages" src="cocoon:/bar"/>
>     <map:serialize type="html"/>
>   </map:match>
>   <map:match pattern="bar">
>     <map:generate src="foobar.xml"/>
>     <map:transform src="XSLwithXSP.xsl"/>
>     <map:serialize type="xml"/>
>   </map:match>
> </map:pipeline>
> The XSL page (XSLwithXSP.xsl) is used to extend the original XML page 
> (foobar.xml) with XSP instructions (ESQL etc.), and the result is fed to the 
> ServerPagesGenerator (resource "foo") using "cocoon:" pseudo protocol.
> Calling "bar" results to an updated page. No problem here. But calling "foo" 
> always results to a cached page. So it seems that the Java code generated by 
> the ServerPagesGenerator is not updated! The only thing that seems to help is
> to remove the work-dir and restart Tomcat. Doing this after every change
> is very frustrating and slow. Here's some experiments on the subject:
> If any of you developers can find and fix the problem, please do. I consider 
> this as a major blocker in the framework. This is because pipelines like the 
> example above can be used to create very flexible and general web applications. 
> (For example, a complete database management system with one descriptor file).
> Thanks A LOT in advance,
> Tuomo

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message