Github user papegaaij commented on the issue:
https://github.com/apache/wicket/pull/233
I don't see why the current implementation uses `AtomicBoolean`. The
current implementation could just as well use a normal boolean. If we need to
take concurrent access into account (and I think we do), we should probably use
a `ThreadLocal`. Of course this assumes that the servlet container will call
(un)bound from the same thread, but the current implementation already has that
assumption. If a container decides to make the calls async, there is no way of
telling if it will happen between the setting and clearing of the boolean.
---
