For some background the way pluto works is when a portlet action is executing pluto creates a portlet render URL for the portlet via PortalCallbackServiceImpl.getPortletURLProvider and then sets the window state, portlet mode and render parameters set during the action on that URL object. When the action completes the portlet container uses that URL object to generate the URL string to redirect the browser to. I'm guessing some more instrumentation of that URL generation process needs to be done so that when pluto requests a PortletURLProvider for a delegate portlet the information set is captured and included on the render url that is generated for the top-level portlet.
-Eric On 05/02/2011 07:51 AM, Steve Swinsburg wrote:
Yep 3.2.4 On 02/05/2011, at 10:39 PM, Eric Dalquist wrote:This is in 3.2 right? On 5/1/11 11:36 PM, Steve Swinsburg wrote:This has come up in another portlet we are working on and it's something we want to get addressed. Eric, can you send through the details of where in the code this is handled and we *might* be able to take a look.cheers, Steve On 02/03/2011, at 3:51 PM, Steve Swinsburg wrote:It's probably not a huge issue since it's only for administrators but if I get a chance (or a local bug report) I'll follow up.thanks, Steve On 02/03/2011, at 3:43 PM, Eric Dalquist wrote:It is likely a bug in the delegation support. CONFIG mode is a bit of a hack where Portlet A gets a custom delegation dispatcher object to delegate requests to Portlet B. Portlet A can still render content around what portlet B renders and for every action/render portlet B executes portlet A is executing one as well. My guess is there is just some missing logic somewhere in the delegation code that is failing to copy the render parameters from portlet B to the render URL that is generated when portlet A completes its execution.Unfortunately I'm not really going to have time to look into it much. If you think you'd be interested in digging in I can point you to the code that handles the delegation and URL generation.-Eric On 2/28/11 9:54 PM, Steve Swinsburg wrote:Hi all,It doesn't look like the CONFIG mode passes through render parameters on the ActionResponse, is this true? Because I am setting them when validation fails on portlet preferences and it's refreshing the page back to the same mode, but not sending through the error message I want to render when it does so.try { prefs.store(); response.setPortletMode(PortletMode.VIEW); } catch (ValidatorException e) {*response.setRenderParameter("errorMessage", e.getMessage() + ":" + e.getFailedKeys());*log.error(e); } catch (IOException e) {response.setRenderParameter("errorMessage", Messages.getString("error.form.save.error"));log.error(e); } catch (PortletModeException e) { e.printStackTrace(); } in JSP: <c:if test="${not empty errorMessage}"> <p class="portlet-msg-error">${errorMessage}</p> </c:if> It works fine when using the normal EDIT mode though... cheers, Steve -- You are currently subscribed [email protected] as:[email protected] To unsubscribe, change settings or access archives, seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev-- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
smime.p7s
Description: S/MIME Cryptographic Signature
