Re: [uportal-dev] Render parameters in CONFIG mode

[Eric Dalquist]

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.

-Eric

On 2/28/11 9:54 PM, Steve Swinsburg wrote:

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.

Hi all,



try {
prefs.store();
response.setPortletMode(PortletMode.VIEW);
} catch (ValidatorException e) {

log.error(e);
} catch (IOException e) {

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 to uportal-dev@lists.ja-sig.org as: 
eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

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. *response.setRenderParameter("errorMessage", e.getMessage() + ":" + e.getFailedKeys());* response.setRenderParameter("errorMessage", Messages.getString("error.form.save.error"));

smime.p7s
Description: S/MIME Cryptographic Signature