Hi, I really could use some advice on how to solve this problem:
In our webapp, we have a wicket filter as well as a couple of other
servlets. The url pattern for the wicket filter is the usual /*. The problem
is that because of this, all urls, including those of the other servlets, go
through
Hi Julian,
I'm not quite understanding your setup. How did your non-Wicket servlet get
a Wicket-proxied Spring bean?
Dan
On Mon, Aug 8, 2011 at 12:14 PM, Julian Sinai jsi...@gmail.com wrote:
Hi, I really could use some advice on how to solve this problem:
In our webapp, we have a wicket
Hi Dan
I don't understand the reason either, but clearly it's happening. My best
guess is what I said in my original post: the non-wicket servlets are going
through the wicket filter.
Julian
On Mon, Aug 8, 2011 at 12:23 PM, Dan Retzlaff dretzl...@gmail.com wrote:
Hi Julian,
I'm not quite
the web.xml might help
Am 08.08.2011 um 21:29 schrieb Julian Sinai:
Hi Dan
I don't understand the reason either, but clearly it's happening. My best
guess is what I said in my original post: the non-wicket servlets are going
through the wicket filter.
Julian
On Mon, Aug 8, 2011 at 12:23
If Wicket doesn't have a mount for a given URL, the WicketFilter doesn't do
anything more than pass the request through as if it weren't even there. So
I don't think your problem is filter configuration.
Your non-Wicket servlet is probably instantiating a Wicket component or
using
On second thought, both instantiating a Component and requesting injection
would blow up immediately without an Application set. So I have to think
something in your Wicket application is putting the proxy somewhere the
servlet can access it.
On Mon, Aug 8, 2011 at 12:46 PM, Dan Retzlaff
Dan, thanks for your reply. You may be right, though I can't imagine what
could be putting the proxy somewhere the servlet can access it. I'll take
another look. And your suggestion to put a breakpoint in the
SpringComponentInjector is a good one.
Julian
On Mon, Aug 8, 2011 at 12:49 PM, Dan
You should just be able to see where that TrustedHostMgr variable is coming
from.
On Mon, Aug 8, 2011 at 1:39 PM, Julian Sinai jsi...@gmail.com wrote:
Dan, thanks for your reply. You may be right, though I can't imagine what
could be putting the proxy somewhere the servlet can access it. I'll
