David Sean Taylor wrote: > On Thursday, April 1, 2004, at 12:34 PM, <[EMAIL PROTECTED]> wrote: > >> I just noticed that a portlet render method is called twice as result >> of an >> ActionRequest. > > That shouldn't happen. > Im in the middle of refactoring and componentizing the navigation and > URL code, so its very likely things will break. > Im putting in unit tests around all the components > Very much appreciate your help here, but please bear with me for a few > days while I transition the code to a more manageable state > and decouple the navigational state from Pluto's implementation. > I've just updated the issue I created for this: http://nagoya.apache.org/jira/browse/JS2-5
Turns out the problem is that the ActionValveImpl doesn't account for the fact that Pluto will redirect the client after PortletAction processing. I've created a patch which checks if the response has been committed after the action processing (only a redirect is allowed to do that I think). If so, no further pipeline processing is needed. I also noted that the processPortletAction method of org.pluto.PortletContainer doesn't give any feedback about this redirection of the client which I think would be much clearer as all portal implementor will face the same problem. I will also post a message on the Pluto developers list concerning this issue. Ate --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
