I don't have much preference for either (just didn't like to add 4 bytes to all components). Both have their merits:
- separate message queue (thread local) that stores in pages (you can get to the page by performing component.getPage()) at the end of the request - store in session Both have their pro's and con's. I'd suggest that we just choose the one with the least problems, make sure we keep current functionality working. Any fancy stuff can go into the next release. If we want to 'upgrade' our validation messages. I could use a generic message mechanism in Wicket, with user controlled removal of the messages (for todo's, messages that need to stay for several pages until the issue is resolved, etc). But that doesn't have to be in wicket 1.3 imo, if at all. Martijn On 4/1/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Can I please get some opinions on https://issues.apache.org/jira/browse/WICKET-442 ? The session option is attractive to me, though I'd like to be sure component specific messages get cleaned up in a fashion that will still work with redirects to pages etc. In case of the session option, I'd like to get rid of the getFeedbackMessages methods of Page altogether. Eelco
-- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
