Well, I think I could but that's a tomcat internal class, so I should recompile the entire tomcat source tree and then run those tests against that.
I'd rather try configuring wicket as a servlet and see if the problem is still there, but I'd like to know that are the drawbacks of doing it in that way. Of course I can also try the terrible kludge of just mapping an empty servlet to the address of the wicket page and see if the situation would improve, but I wouldn't really like to bring that orrible kludge to any production system. If you think it would help I can provide you both the test wars I've used. Thanks, -Roberto Serkan Camurcuoglu wrote: > > can you put a breakpoint in ProxyDirContext and check what name is being > looked up? > -- View this message in context: http://www.nabble.com/Problem-with-using-wicket-as-a-filter-tp20171597p20183861.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
