You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Ate Douma (JIRA)" <pl...@jakarta.apache.org> on 2005/06/26 13:58:01 UTC
[jira] Updated: (PLUTO-132) incorrect VariableInfo scope specification for exported url variable from PortletURL Tags
[ http://issues.apache.org/jira/browse/PLUTO-132?page=all ]
Ate Douma updated PLUTO-132:
----------------------------
Attachment: patch.txt
Patch file containing fix described above
> incorrect VariableInfo scope specification for exported url variable from PortletURL Tags
> -----------------------------------------------------------------------------------------
>
> Key: PLUTO-132
> URL: http://issues.apache.org/jira/browse/PLUTO-132
> Project: Pluto
> Type: Bug
> Components: portlet container
> Versions: Current CVS, 1.0.1-rc1, 1.0.1-rc2, 1.0.1-rc3
> Environment: WindowsXP, WAS 5.1.1.3, Jetspeed-2.0-M4 (SVN trunk)
> Reporter: Ate Douma
> Attachments: patch.txt
>
> org.apache.pluto.tags.BasicURLTag.TEI defines the VariableInfo for the "var" attribute with a scope value of VariableInfo.AT_BEGIN (line 51).
> WAS 5.1.1.3 (rightfully) optimizes against this specification and retrieves the "var" named attribute value from the pageContext directly after the doStartTag().
> But of course this is wrong as the generated url is only stored in the pageContext attributes from org.apache.pluto.tags.BasicURLTag.doEndTag().
> Result: "null" values are written out instead of the generated PortletURL :-(
> Fix: change the VariableInfo.scope value for the "var" attribute to VariableInfo.AT_END (again: on line 51 in org.apache.pluto.tags.BasicURLTag.java)
--
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.atlassian.com/software/jira