Hi Lon, Welcome to Wicket!
It seems you run your application in Production mode and that's why it shows this almost empty page. In Production it is recommended to not show detailed information about your application problems to your audience. If you change the configuration type to Development then the exception with its stacktrace is being shown also in the browser. I say "also" because in both cases the exception is logged in the server logs too. Always consult with the server logs because there might be some hints when you do something that is not optimal! ;-) Have fun and let us know if you face any issues! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Apr 21, 2016 at 3:22 AM, Lon Varscsak <lon.varsc...@gmail.com> wrote: > Hey all, I’m new to wicket and I got this horrendous error earlier today: > > > I had NO idea what it meant. :P I was able to debug it and see what was > left in queue, and that reminded me that I hadn’t finished the html for a > new component I had added in the constructor. My question is, isn’t there > a better way to explain to the developer what’s going on? It would be > super helpful to newbs like me. ;D > > Just a thought. > > Thanks, > > Lon >