cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Ratcliffe" <>
Subject RE: Help with redestructuring of sitemaps and URI space
Date Mon, 17 Jan 2005 09:30:21 GMT
Hi Mark,

Yes, that's a lot tidier. Thanks very much for your help.


-----Original Message-----
From: Mark Lundquist []
Sent: Monday, 17 January 2005 7:29 p.m.
Subject: Re: Help with redestructuring of sitemaps and URI space

On Jan 16, 2005, at 2:18 PM, Adam Ratcliffe wrote:

> Another issue occurs with sendPageAndWait() and showForm() calls where
> the pipeline matching the continuation URI in the customer
> sitemap needs to redirect to a pipeline in the top-level sitemap where
> the flowscript is included:
>       <map:match pattern="continue.*">
>          <map:redirect-to uri="cocoon://continue.{1}"/>
>       </map:match>
> If the continuation is not matched by the customer sitemap but instead
> matched by the top-level sitemap, using a form action like:
> '../../continue.#{$continuation/id}' the contextPath will be that of
> the top-level sitemap and relative URLs in the output page will no
> longer be relative to the customer directory.

Right.  You don't want to use a form action that looks like that!  Use
something like

	<form action="#{$continuation/id}.continue">

Then, use these two matchers (just in the top-level sitemap):

     <match pattern="*.continue">
       <call continuation="{1}"/>
     <match pattern="**/*.continue">
       <call continuation="{2}"/>

...or replace both of them with this:

     <match type="regexp" pattern="(.*/)?([^/].*)\.continue">
       <call continuation="{2}"/>

...or, do like some people like to do: take the continuation out of the
form action, and pass it as a hidden form parameter instead.  Search
the list archives for examples of how to do that (or maybe it's on the


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message