Hi, Yes, ThreadLocal, request attribute and request cycle's metadata won't do it. You can store this data in the Session but you must be careful because you may have several requests (e.g. Ajax) in the same session simultaneously. Using the request parameters is also possible but then this data will be visible to your end users ... Yet another way (a bit more hidden) is to use a cookie but again you should be careful to not mix the data for two separate requests.
You can also use the url from the second request (after the redirect) to extract which page would be responsible for it but this will add both CPU and memory to your end data. I think you can just ignore the requests that are handled by BufferedResponseRequestHandler. They are fast because they just write the buffered response (some markup in memory) to the http response. There is almost no processing here. Martin Grigorov Wicket Training and Consulting On Fri, Jun 13, 2014 at 10:51 AM, Hendy Irawan <he...@soluvas.com> wrote: > I also tried requestCycle.setMetaData() but the metadata is also gone for > the > next related request. :( > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-get-PageClass-from-BufferedResponseRequestHandler-And-how-to-link-related-requests-tp4666247p4666248.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
