geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan (JIRA)" <>
Subject [jira] Updated: (GERONIMO-1759) getConsoleFrameworkServletPath broken
Date Wed, 29 Mar 2006 22:15:28 GMT
     [ ]

Paul McMahan updated GERONIMO-1759:

    Attachment: GERONIMO-1759.patch

The attached patch will determine the console framework servlet path as follows:

-  get the path info for the portlet from the portlet request
-  get the portlet name by splitting the path info on '/'
-  create a renderURL from the portlet response
-  truncate the renderURL at the first occurrence of the portlet name

> getConsoleFrameworkServletPath broken
> -------------------------------------
>          Key: GERONIMO-1759
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: console
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Paul McMahan
>      Fix For: 1.1, 1.2
>  Attachments: GERONIMO-1759.patch
> This function is used by the portlets to calculate the correct context path to the portal
so they can refer to images bundled with the portal WAR (as opposed to bundled with the portlet
> It works fine on pages where you click a navigation link and land there.  It does not
seem to work if one portlet page has a form that submits to another portlet page and the destination
calls the function.
> In my case, it was looking for an occurance of:
> /Security/Security_keystores/_st_Security_keystores_row1_col1_p1/normal/_rp_Security_keystores_row1_col1_p1_mode/1_list/_ps_Security_keystores_row1_col1_p1/normal/_pm_Security_keystores_row1_col1_p1/view/_pid/Security_keystores_row1_col1_p1/_md_Security_keystores_row1_col1_p1/view
> in
> /console/portal/Security/Security_keystores/_st_Security_keystores_row1_col1_p1/normal/_ps_Security_keystores_row1_col1_p1/normal/_pm_Security_keystores_row1_col1_p1/view/_pid/Security_keystores_row1_col1_p1/_md_Security_keystores_row1_col1_p1/view
> And (if you look carefully) there is clearly none there.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message