Re: Help with redestructuring of sitemaps and URI space

[Mark Lundquist]

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>
    <match pattern="**/*.continue">
      <call continuation="{2}"/>
    </match>
...or replace both of them with this:
    <match type="regexp" pattern="(.*/)?([^/].*)\.continue">
      <call continuation="{2}"/>
    </match>
...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 
wiki)

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