Is it starting the smart client, loading the smart client or starting a solution that creates the error?
This is strange imho, unless I miss something. apache.wicket is about ajax and has nothing to do with a smart client and everything with the web client.