Christopher Oliver dijo: > If you don't mind, can you explain how it fixes the problems reported by > Unico and Antonio? What was happening before your fix and what will > happen now when you have > > request: > --> map:call > --> sendPage() > --> map:call > --> sendPage() > > Thanks, > > Chris
Hi Chris, I just starting my work again. I will try the Sylvain solution and inform about the archievement. As Sylvain explained it seems to be related to redirects, like the redirect are lost or something similar. I will try the sylvain code and inform on the list if this helps. Best Regards, Antonio Gallardo Best Regards, Antonio Gallardo. > > > > Sylvain Wallez wrote: > >> Christopher Oliver wrote: >> >>> I looked into this but I don't quite understand why it's occurring. >>> The change I made to sendPage() makes it behave uniformly with >>> processPipelineTo(), so it seems like this was an existing problem >>> (i.e. it would have occurred anyway with processPipelineTo()). Can >>> someone explain what's going on here? >> >> >> >> I just updated the behaviour of Redirector.forward() so that >> processing of "cocoon:" forwards occurs immediately. >> >> This is likely to be the solution to these problems, as it allows to >> rollback AbstractInterpreter.forwardTo() to how it was implemented >> before you added the 3rd parameter to sendPageAndWait(). >> >> Hope this helps, >> Sylvain >> > >
