Eelco Hillenius wrote: > > About the session messages... well, they have a slightly different > meaning: display whenever there is a feedback component rendered on > any page. This is useful when writing generic software where you know > that a message should be displayed, but you just don't know the target > (e.g. at the end of a wizard). >
yeah, i don't know what i was thinking... threadlocal clearly doesn't work for session scoping. duh. ;-) Eelco Hillenius wrote: > > About per-page or per-request... yeah, we've been there too. If we > look back at the history we can say that the page is the correct place > to have it. > We chose that, yes. But would it be better to simply have all feedback messages stored in the session? That would solve all our scoping problems wouldn't it? Every feedback message would go into the session and then feedback panels could pull them out when they're ready to. If a feedback message is in the session for more than one request cycle and it is not cleared by a feedback panel, we would discard it (and maybe warn in debug mode). -- View this message in context: http://www.nabble.com/error%28...%29-No-page-found-for-component-tf3497125.html#a9773999 Sent from the Wicket - User mailing list archive at Nabble.com. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
