Details
Major Description
Google App Engine does not allow applications to spawn threads. But Wicket's ModificationWatcher does so. So, deploying Wicket applications on GAE will not work in debug mode, even when deploying on the local app engine development environment.
It would be nice, if it would be possible to use a different ModificationWatcher that does not spawn Threads. The Problem is, that
A) ModificationWatcher is not an Interface but a concrete class
B) ModificationWatcher is final
As a bonus it would be nice to have an optional ModificationWatcher implementation in the wicket core that does not rely on threads, but instead checks Resources before every request, for example.