Hi,

We've hit a rather nasty classloading issue during Wicket's deserialization, 
for which Martijn and I have a proposed fix. However, due to the complexity of 
classloading it's near to impossible to write a testcase for it, so we would 
really appreciate it if this could be reviewed. The change itself is not that 
big.

Best regards,
Emond

Reply via email to