Has anything changed lately with caching and non caching pipelines? I am using
cocoon as xml data provider from MSSQL/Sybase/Pervasive database.
My pipeline 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>
It works like that:
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.
The problem is that using cocoon HEAD only some days old I started getting
"descriptors/somedata.xml" 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.
regards
LG
--
__
| / \ | Leszek Gawron // \\
\_\\ //_/ [EMAIL PROTECTED] _\\()//_
.'/()\'. Phone: +48(600)341118 / // \\ \
\\ // recursive: adj; see recursive | \__/ |
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
