Hello everyone, two issues which are kind of bothering me right now, hopefully somebody can help.
1. depending on whether a request was handled successfully or not (i.e. validation failed) I use the redirect-after-post pattern. In particular that means that for successful operations I redirect to the next page, while with unsuccesful ones I use forwards as to not lose any information in my validation delegate (which is not persistent and would therefore go lost if I used redirects). Right now I am doing these forwards/redirects directly from my listeners. However, I think it would be much nicer if I could always use cycle.activate(nextPage) and then the logic in the request cycle would decide whether to forward or to redirect depending on the validation delegate being in error. Where would I hook in, in order to achieve this (if it is possible at all)? 2. My second question is more like a feature request. I think it would be nice to have something like client:page persistence for server properties as well (i.e. session:page). I can probably roll my own, but this is something which imo really belongs into the core framework. Thanks for any help in advance Mark Lehmacher --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
