I wonder how another filter could alter the behavior for this issue.. The call fails at org.apache.wicket.core.util.lang.WicketObjects.resolveClass(WicketObjects.java:72), surely the class name to be resolved is solely at Wicket's control?
On Sun, Dec 14, 2014, 01:18 Ernesto Reinaldo Barreiro-4 [via Apache Wicket] <ml-node+s1842946n4668756...@n4.nabble.com> wrote: There are more filters, besides wicket filter, on the filter chain. Did you check those? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/java-lang-ClassNotFoundException-lowercased-class-name-tp4668754p4668757.html Sent from the Users forum 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
