Having the token persisted into DB seems bit complex to solve this 'dynamic'
resource issue.

The way I've implemented it right now, is to have this resource reference
unmounted, from AbstractRequestCycleListener#onRequestHandlerExecuted()
method, where I've access to IRequestHandler and the resource reference
object it self (checking for ResourceReferenceRequestHandler)

Do you see any issues with this approach ?


View this message in context: 
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

Reply via email to