You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by "matt.payne" <ma...@gmail.com> on 2008/09/07 20:58:11 UTC
Struts 2.1.2(an previous releases) vs 2.1.3 in regards to
actionMessages in a sitemesh decorator
There seem to be some type of regression that has happen with regards to
actionMessage/actionErrors.
In the current build snapshots of 2.1.3 actionErrors/message are no longer
exposed my to the sitemesh decorator(I am using freemarker result
types/decorators). However that are still available to the direct result,
just not within the decorators.
This is an example of a snippet used with a decorator.
<div id="middlebox">
<#if (actionMessages?exists && actionMessages.size() > 0)><#include
"/WEB-INF/decorators/msg.ftl"/></#if>
<#if (fieldErrors?exists && actionErrors?exists) &&
(fieldErrors.size() > 0 || actionErrors.size() > 0)>
<#include "/WEB-INF/decorators/error_msg.ftl"/>
</#if>
${body}
</div>
Any idea what could have caused this regression?
I the decorator I can still refer to ${action.actionMessages.size()}
Thanks,
Matthew Payne
--
View this message in context: http://www.nabble.com/Struts-2.1.2%28an-previous-releases%29-vs-2.1.3-in-regards-to-actionMessages-in-a-sitemesh-decorator-tp19361286p19361286.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 2.1.2(an previous releases) vs 2.1.3 in regards to actionMessages
in a sitemesh decorator
Posted by Jeromy Evans <je...@blueskyminds.com.au>.
matt.payne wrote:
> There seem to be some type of regression that has happen with regards to
> actionMessage/actionErrors.
>
> In the current build snapshots of 2.1.3 actionErrors/message are no longer
> exposed my to the sitemesh decorator(I am using freemarker result
> types/decorators). However that are still available to the direct result,
> just not within the decorators.
>
In 2.1.3 there have been some changes around the FilterDispatcher and
ActionContextCleanup.
You may notice the FilterDispatcher is deprecated.
See the struts-dev "New Filter Strategy RFC" thread started on 22 June 08.
I haven't paid attention to what's changed and have some code running
with the older filters and some on the new. I'm certain none of my code
uses action messages inside decorators though.
In 2.1.2, the resolution of WW-2167 also carried some risk for sitemesh
decorators:
https://issues.apache.org/struts/browse/WW-2167
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org