OK, sorry for not looking further! I was just pessimistic that the whole
ResultConfig must have been made read-only.
Thanks
Adam
Musachy Barroso on 26/01/09 15:43, wrote:
I think just need to pass a string, instead of an object in the value param.
musachy
On Mon, Jan 26, 2009 at 10:37 AM, Adam Hardy
<ahardy.str...@cyberspaceroad.com> wrote:
Hi,
got a compilation error after upgrading from 2.0.11 to 2.1.6 due to changes
in com.opensymphony.xwork2.config.entities.ResultConfig
I am doing this:
public boolean addRedirectParameter(String resultName, String paramName,
Object paramValue)
{
Map<String, ResultConfig> resultsMap =
ServletActionContext.getActionContext(getRequest())
.getActionInvocation().getProxy().getConfig().getResults();
ResultConfig config = resultsMap.get(resultName);
if (config == null)
{
return false;
}
else
{
config.addParam(paramName, paramValue); // 2.1.6 COMPILE ERROR
return true;
}
}
which I can call in my actions in order to put another parameter onto the
redirect URL of my result.
In 2.1.6, ResultConfig has no addParam() method anymore.
After checking the upgrade troubleshooting guide and the user lists, it
seems nobody else is suffering from this problem. Could somebody give me an
idea how to deal with this?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
