OK, I understand what you're doing now. It sounds like you have a couple
of options. You could override processCachedMessages() as you suggest,
which may be the easiest solution. Alternatively, since you need custom
message setup logic, perhaps it would make sense to provide a reciprocal
message teardown function -- i.e., have an application-specific
mechanism both for storing and for retrieving/removing your 'flow scope'
messages.
That also suggests another possibility, which would be to look at
flow-oriented extensions like Struts Flow or Spring's Web Flow; those
may provide out-of-the-box scope management you could use for this.
L.
Kevin Maeer wrote:
Spoke too soon. The reworked pages/actions don't work...
Say I have 3 pages - page1, page2 and page3 with actions between them.
The action between page1 and page2 uses saveMessages to save a message on the
session for page3 to display (with property="page3-messages").
The next page shown - page2 - has a <html:messages property="page2-messages"...>
to display any messages specifically for it. Using this however will always set
the ActionMessages.isAccessed flag to true and the RequestProcessor's
processCachedMessages will remove it from the session even though there is a
message on it for page3.
So back to my original question. Is there a simpler/more standard way of doing
this? If I do have to put the messages into the session using custom keys (one
for each destination page I guess) is there a cleaner way of tidying up that
doesn't involve subclassing RequestProcessor and overriding the
processCachedMessages to get rid of any accessed ActionMessages from the
session?
Cheers,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
