That said, I agree that data shouldn't be duplicated. We should
provide a simple mechanism on the PortletContainer interface for
portals to retrieve the contents of the portlet descriptor. I'm
envisioning a getPortalApplicationDescriptor(String context) method
or something like that on the public interface.
Thanks for that David. I've been working on PLUTO-233 and current
mechanisms for getting a handle on the portlet descriptor are brittle.
I'll try to implement your suggestion above, if you're not already
working on it (no need to duplicate effort).
Elliot
David DeWolf (JIRA) wrote:
[
http://issues.apache.org/jira/browse/PLUTO-252?page=comments#action_12433104
]
David DeWolf commented on PLUTO-252:
------------------------------------
Portlet Modes should be fixed per PLUTO-233 (or if it's different,
broken out into a different JIRA issue). Let's keep this bug limited
to the one issue with endcoding the url.
That said, I agree that data shouldn't be duplicated. We should
provide a simple mechanism on the PortletContainer interface for
portals to retrieve the contents of the portlet descriptor. I'm
envisioning a getPortalApplicationDescriptor(String context) method
or something like that on the public interface.
Custom Tags with response.encodeUrl( url ) and Render hidden
portlet mode.
--------------------------------------------------------------------------
Key: PLUTO-252 URL: http://issues.apache.org/jira/browse/PLUTO-252
Project: Pluto Issue Type: New Feature Components: portal driver,
portlet container taglibs Affects Versions: Current CVS Reporter:
Simone Federici Fix For: 1.1.0
Attachments: PatchPluto1.1.beta.txt
This patch modify the Custom Tags <pluto:url /> <portlet:actionURL
/> <portlet:renderURL /> for don't lose the session if the browser
don't support cookies. and permitted to specify in the
pluto-portal-driver-config.xml the portlet modes that you don't
wont to see.
