> -----Original Message----- > From: Sven Schliesing [mailto:[EMAIL PROTECTED] > Sent: 06 April 2004 18:03 > To: Cactus Users List > Subject: Re: Filter not used in JspTestCase > > You got it totally right. > I also tried to extend "FilterTestCase" to get around that issue. On the > one hand it didn't help and on the other it is not that I wanted to do.
Yep, it's not related to FilterTestCase which is only useful to unit test Filters... (not JSPs). Ah ok, I think I got it.... Your Filter must be configured to be triggered only on your specific JSP. However that JSP is probably not called by your test. Could you show us your test? What do you want to test BTW? The JSP itself or some taglib? If it's the JSP then you need to call it using forward() or include() and that should trigger the filter. Alternatively you could map the filter to be triggered on the Cactus JspTestCase redirector. Hope it helps, -Vincent > > Vincent Massol wrote: > > Hi Sven, > > > > If I understand correctly, you have a JSP that you'd like to test and > > you also have a filter that executes before the JSP gets called. You are > > trying to test this with Cactus and Maven and you're noticing that your > > filter does not get called. Right? > > > > I am not aware of this problem and it should be transparent for Cactus > > normally. > > > > -Vincent > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
