You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Nicolas Dutertry (JIRA)" <je...@portals.apache.org> on 2007/08/09 17:01:43 UTC

[jira] Created: (JS2-767) Portlet Action not working when using JetspeedPowerTool

Portlet Action not working when using JetspeedPowerTool
-------------------------------------------------------

                 Key: JS2-767
                 URL: https://issues.apache.org/jira/browse/JS2-767
             Project: Jetspeed 2
          Issue Type: Bug
    Affects Versions: 2.1.2
            Reporter: Nicolas Dutertry


When a portlet is included in a decorator using $jetspeed.renderPortletEntity, the action urls generated by this portlet doesn't work.

This bug is due to the following code in class org.apache.jetspeed.container.ContainerValve : 

    public void invoke(RequestContext request, ValveContext context) throws PipelineException
    {
        ...
               window = state.getPortletWindowOfAction();
                if (window != null && page.getFragmentById(window.getId().toString()) == null)
                {
                    // target window doesn't exists anymore or the target page is not accessible (anymore)
                    // remove any navigational state for the window
                    state.removeState(window);
                    // as this is an action request which cannot be handled, perform a direct redirect after sync state (for the other windows)
                    redirect = true;
                }
        ...
    }

Indeed, in this case, the valve should not perform a redirect because even if the portlet is not in the page (but in the decorator), the action have to be performed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


[jira] Assigned: (JS2-767) Portlet Action not working when using JetspeedPowerTool

Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
     [ https://issues.apache.org/jira/browse/JS2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Sean Taylor reassigned JS2-767:
-------------------------------------

    Assignee: David Sean Taylor

> Portlet Action not working when using JetspeedPowerTool
> -------------------------------------------------------
>
>                 Key: JS2-767
>                 URL: https://issues.apache.org/jira/browse/JS2-767
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.1.2
>            Reporter: Nicolas Dutertry
>            Assignee: David Sean Taylor
>
> When a portlet is included in a decorator using $jetspeed.renderPortletEntity, the action urls generated by this portlet doesn't work.
> This bug is due to the following code in class org.apache.jetspeed.container.ContainerValve : 
>     public void invoke(RequestContext request, ValveContext context) throws PipelineException
>     {
>         ...
>                window = state.getPortletWindowOfAction();
>                 if (window != null && page.getFragmentById(window.getId().toString()) == null)
>                 {
>                     // target window doesn't exists anymore or the target page is not accessible (anymore)
>                     // remove any navigational state for the window
>                     state.removeState(window);
>                     // as this is an action request which cannot be handled, perform a direct redirect after sync state (for the other windows)
>                     redirect = true;
>                 }
>         ...
>     }
> Indeed, in this case, the valve should not perform a redirect because even if the portlet is not in the page (but in the decorator), the action have to be performed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


[jira] Resolved: (JS2-767) Portlet Action not working when using JetspeedPowerTool

Posted by "David Sean Taylor (JIRA)" <je...@portals.apache.org>.
     [ https://issues.apache.org/jira/browse/JS2-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Sean Taylor resolved JS2-767.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.3

see Woonsans commits:

http://svn.apache.org/viewvc?view=rev&revision=589933

> Portlet Action not working when using JetspeedPowerTool
> -------------------------------------------------------
>
>                 Key: JS2-767
>                 URL: https://issues.apache.org/jira/browse/JS2-767
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.1.2
>            Reporter: Nicolas Dutertry
>            Assignee: David Sean Taylor
>             Fix For: 2.1.3
>
>
> When a portlet is included in a decorator using $jetspeed.renderPortletEntity, the action urls generated by this portlet doesn't work.
> This bug is due to the following code in class org.apache.jetspeed.container.ContainerValve : 
>     public void invoke(RequestContext request, ValveContext context) throws PipelineException
>     {
>         ...
>                window = state.getPortletWindowOfAction();
>                 if (window != null && page.getFragmentById(window.getId().toString()) == null)
>                 {
>                     // target window doesn't exists anymore or the target page is not accessible (anymore)
>                     // remove any navigational state for the window
>                     state.removeState(window);
>                     // as this is an action request which cannot be handled, perform a direct redirect after sync state (for the other windows)
>                     redirect = true;
>                 }
>         ...
>     }
> Indeed, in this case, the valve should not perform a redirect because even if the portlet is not in the page (but in the decorator), the action have to be performed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org