The functionality to automtaically remove messages cached in the
session was missing from Struts 1.3.x and only added recently in the
Struts 1.3.5 version:

   http://issues.apache.org/struts/browse/STR-2883
   http://svn.apache.org/viewvc?view=rev&revision=412834

Are you using Struts 1.3.5?

Also how are you configuring the ComposableRequestProcessor commands?
Are you letting it pick up the default chain-config.xml shipped in the
jar or do you have a custom (or tiles) one that you're specifying
through the web.xml?

If you have a custom one, does it include the new RemoveCachedMessages command?

Niall

On 8/25/06, Scott Van Wart <[EMAIL PROTECTED]> wrote:
Hi, I have something very close to the following in each of my pages
(actually, just in the layout page for tiles, but whatever).  Worked
fine in Struts 1.2.9 (even though I'm not so sure it's the best way to
print messages and errors, but oh well...)

    <logic:messagesPresent message="true">
        <bean:message key="header.notice" />
        <ul>
            <html:messages id="message" message="true">
                <li><bean:write name="message" /></li>
            </html:messages>
        </ul>
    </logic:messagesPresent>

    <logic:messagesPresent message="false">
        <bean:message key="header.error" />
        <ul>
            <html:messages id="error" message="false">
                <li><bean:write name="error" /></li>
            </html:messages>
        </ul>
    </logic:messagesPresent>

I store my messages in the session so they'll persist even after a
redirect.  Unfortunately, in 1.3, when I call saveMessages(
request.getSession(), messages ), the message appears properly, but
continues to appear on subsequent page requests.  Any ideas?

- Scott


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to