By the way, you realise that your filter blocks the following servlet (which is legal of course) because it doesn't invoke filterChains doFilter method?
Have you checked the logs? It's not because the response is already committed is it?
Joined: Mar 13, 2006
Daniel, i reckon the catch is in the Filter code.This is what i'm getting in the console log
"SEVERE: Error filterStart"
becoz of this application is not getting deployed.
Joined: Mar 20, 2005
after some experimenting, I believe that your filter doesn't work due to your constructor. If you either remove your constructor, or put a call to super() into it, it works for me (using apache geronimo).
I'll admit that I don't understand this one. Filter is an interface, so by giving your class a constructor and not calling super(), you aren't preventing a container supplied superclass constructor from running.
Can anyone explain?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com