you can also miss logs if your logging setup is incorrect.. it may happen because of conflicting commons-logging or log4j jars, or if you have multiple log4j.properties files in your classloader hierarchy.. I don't know how these logging frameworks work exactly, but I had a similar problem and it was corrected (I started seeing more wicket logs) when I deployed my application into a clean tomcat with only the necessary jars..
Thomas Singer-4 wrote: > > On our webserver I'm getting WicketNotSerializableException in the log, > but > I never got them locally. What should I do to trigger them in my local > test > server? > > Thanks in advance, > Tom > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View this message in context: http://www.nabble.com/WicketNotSerializableException-tp21543331p21550303.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
