Jan Hoskens a écrit :

Christoph Hermann wrote:

Marc Salvetti schrieb:

Hello,


               <map:match pattern="*cruise*">
                   <map:call function="handleForm">



                       <map:parameter name="documentURI"
value="xdocs/planning/cruise{2}.xml"/>



When browsing, the cache system seems to get stuck on one of the docs
(ie : cruise1.xml) and from this moment, everytime the form is
called, it is binded to the same document, and the continuation ID
becomes invalid !

Anyone came across this kind of problem ?



Did you try {../2}?
Maybe the map:call adds one level to your sitemap (i don't know, just an Idea)


{../2} just gets the error "not so many levels"

HTH
Christoph


That's not the problem here, parameters are using the same level as it's parent, so {2} should do the trick. When you say the cache system, do you mean the cocoon caching? Or are you testing a remote setup with possibly caching systems (eg proxies) in between? When calling the form, do you see an access line in your logs?

I mean the cocoon caching, i didn't set up anything regarding the cache yet

If cocoon caches the form use
<map:pipeline type="noncaching">

Tried this one, didn't solve the pb

for your pipes that should not be cached. If a proxy or some caching system (between your cocoon and browser) hands a cached form, set your http-headers to non-caching:

<map:act type="set-header">
  <map:parameter name="Pragma" value="no-cache"/>
  <map:parameter name="Expires" value="-1"/>
  <map:parameter name="Cache-control" value="no-cache"/>
</map:act>

If that's the real problem of course...

It doesn't seem to be the pb, as i don't use any proxy or external caching system

Kind Regards,
Jan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to