Created: (FOR-804) using redirect-to in dispatcher doesn't work

using redirect-to in dispatcher doesn't work
--------------------------------------------

         Key: FOR-804
         URL: http://i
ssues.apache.org/jira/browse/FOR-804
     Project: Forrest
        Type: Bug
  Components: Dispatcher (aka views)  
    Versions: 0.8-dev    
    Reporter: Tim Williams
    Priority: Minor


The dispatcher doesn't seem to like map:redirect-to's as in:

      <map:match
pattern="gallery/**/index.xml">
        <map:redirect-to
uri="gallery//index_1.xml"/> 
      </map:match>

This is fixed in the photogallery by changing it to:
      <map:match
pattern="gallery/**/index.xml">
        <map:generate
src="cocoon://gallery//index_1.xml"/>
        <map:serialize type="xml" />
      </map:match>

I'm really not sure what the benefit of the map:redirect-to
is in this instance.  It seems like the cocoon protocol
might be more appropriate anyway but it highlights that
there may be an issue with using redirect-to's in
Dispatcher.  Further testing is required to make sure it's
really an issue, but it's not my major concern at the moment
and I didn't want to get sidetracked.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

-
For more information on JIRA, see:
   http://www.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/F
OR-804?page=comments#action_12364403 ] 

Thorsten Scherler commented on FOR-804:
---------------------------------------

What is the error message?

> using redirect-to in dispatcher doesn't work
> --------------------------------------------
>
>          Key: FOR-804
>          URL: http://i
ssues.apache.org/jira/browse/FOR-804
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: Tim Williams
>     Priority: Minor

>
> The dispatcher doesn't seem to like map:redirect-to's
as in:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:redirect-to
uri="gallery//index_1.xml"/> 
>       </map:match>
> This is fixed in the photogallery by changing it to:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:generate
src="cocoon://gallery//index_1.xml"/>
>         <map:serialize type="xml" />
>       </map:match>
> I'm really not sure what the benefit of the
map:redirect-to is in this instance.  It seems like the
cocoon protocol might be more appropriate anyway but it
highlights that there may be an issue with using
redirect-to's in Dispatcher.  Further testing is required to
make sure it's really an issue, but it's not my major
concern at the moment and I didn't want to get sidetracked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

-
For more information on JIRA, see:
   http://www.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/F
OR-804?page=comments#action_12364404 ] 

Tim Williams commented on FOR-804:
----------------------------------

It is the standard error if a page isn't found.  I can
change it back and get the exact error if you'd like but
it's the standard Cocoon file not found error with the path
of the redirect.  

> using redirect-to in dispatcher doesn't work
> --------------------------------------------
>
>          Key: FOR-804
>          URL: http://i
ssues.apache.org/jira/browse/FOR-804
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: Tim Williams
>     Priority: Minor

>
> The dispatcher doesn't seem to like map:redirect-to's
as in:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:redirect-to
uri="gallery//index_1.xml"/> 
>       </map:match>
> This is fixed in the photogallery by changing it to:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:generate
src="cocoon://gallery//index_1.xml"/>
>         <map:serialize type="xml" />
>       </map:match>
> I'm really not sure what the benefit of the
map:redirect-to is in this instance.  It seems like the
cocoon protocol might be more appropriate anyway but it
highlights that there may be an issue with using
redirect-to's in Dispatcher.  Further testing is required to
make sure it's really an issue, but it's not my major
concern at the moment and I didn't want to get sidetracked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

-
For more information on JIRA, see:
   http://www.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/F
OR-804?page=comments#action_12364406 ] 

Thorsten Scherler commented on FOR-804:
---------------------------------------

No, no need. I think the problem lies in the
contracts/structurer. 

We need to track the contracts which are not working. 

I guess 
<forrest:contract name="content-main"
dataURI="cocoon://#{$getRequest}.body.xml"/>
this kind of links can break on a redirect.




> using redirect-to in dispatcher doesn't work
> --------------------------------------------
>
>          Key: FOR-804
>          URL: http://i
ssues.apache.org/jira/browse/FOR-804
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: Tim Williams
>     Priority: Minor

>
> The dispatcher doesn't seem to like map:redirect-to's
as in:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:redirect-to
uri="gallery//index_1.xml"/> 
>       </map:match>
> This is fixed in the photogallery by changing it to:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:generate
src="cocoon://gallery//index_1.xml"/>
>         <map:serialize type="xml" />
>       </map:match>
> I'm really not sure what the benefit of the
map:redirect-to is in this instance.  It seems like the
cocoon protocol might be more appropriate anyway but it
highlights that there may be an issue with using
redirect-to's in Dispatcher.  Further testing is required to
make sure it's really an issue, but it's not my major
concern at the moment and I didn't want to get sidetracked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

-
For more information on JIRA, see:
   http://www.atl
assian.com/software/jira

    [ http://issues.apache.org/jira/browse/F
OR-804?page=comments#action_12364499 ] 

Thorsten Scherler commented on FOR-804:
---------------------------------------

I forget to ask which version of the dispatcher? 

I saw that you have checked in the photogallery plugin with
the v2 plugins.

> using redirect-to in dispatcher doesn't work
> --------------------------------------------
>
>          Key: FOR-804
>          URL: http://i
ssues.apache.org/jira/browse/FOR-804
>      Project: Forrest
>         Type: Bug
>   Components: Dispatcher (aka views)
>     Versions: 0.8-dev
>     Reporter: Tim Williams
>     Priority: Minor

>
> The dispatcher doesn't seem to like map:redirect-to's
as in:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:redirect-to
uri="gallery//index_1.xml"/> 
>       </map:match>
> This is fixed in the photogallery by changing it to:
>       <map:match
pattern="gallery/**/index.xml">
>         <map:generate
src="cocoon://gallery//index_1.xml"/>
>         <map:serialize type="xml" />
>       </map:match>
> I'm really not sure what the benefit of the
map:redirect-to is in this instance.  It seems like the
cocoon protocol might be more appropriate anyway but it
highlights that there may be an issue with using
redirect-to's in Dispatcher.  Further testing is required to
make sure it's really an issue, but it's not my major
concern at the moment and I didn't want to get sidetracked.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

-
For more information on JIRA, see:
   http://www.atl
assian.com/software/jira