DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16958>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16958 caching pipeline serves wrong content Summary: caching pipeline serves wrong content Product: Cocoon 2 Version: Current CVS Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The pipeline configuration looks like this: <map:match pattern="protected/data/*"> <map:aggregate element="root"> <map:part src="xml/status-ok.xml" strip-root="true"/> <map:part src="cocoon:/data/{1}" strip-root="true"/> </map:aggregate> </map:match> [...] <map:match pattern="data/*"> <map:select type="request-parameter"> <map:when test="data"> <map:generate src="descriptors/{1}.xml"/> </map:when> <map:when test="filter"> <map:generate src="descriptors/{1}-filter.xml"/> </map:when> <map:otherwise> <map:generate src="data/{1}.xsp" type="serverpages"/> <map:transform src="stylesheets/default.xsl"/> </map:otherwise> </map:select> <map:serialize/> </map:match> request parameter selector is : <map:selector logger="sitemap.selector.request-parameter" name="request-parameter" src="org.apache.cocoon.selection.RequestParameterSelector"> <parameter-name>descriptor</parameter-name> </map:selector> The logic behind that is: if user requests http://host/cocoon/protected/data/somedata - xml data from database is provided if user requests http://host/cocoon/protected/data/somedata?descriptor=file or http://host/cocoon/protected/data/somedata?descriptor=data static xml files are sent that describe the rowset. While working with cocoon after Tomcat restarts it works well (sometimes 30 minutes sometimes even 2 hours), when suddenly logs say that cached response has been found and since then only the static descriptor "descriptors/somedata.xml" is being served no matter what parameters in the URL are sent. I am using default pipeline configuration I'm also sure that is not due to the client side caching. The problem did not occur in HEAD compilation dated somewhere at the beginning of the year (I think I have checked out 2003-01-01 state to compile but I'm not sure) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
