I have a custom Filter with the main purpose of user login checking. If a user is not logged in the request will be redirected to a login page. Another purpose is initialization of server side logfiles. This second step we do in the init method of the Filter. Now the weird thing is that with Tomcat the Filter.init method is called directly on startup, with Glassfish v3 prelude this is also the case, so starting op the application calls the Filter.init method even before an URL request is done by the client.
With Glassfish V3.0.1 however this is not the case, the init method is not called on startup. Does anybody know why this is or how I can change this behaviour? Maybe there is an option in Glassfish to influence this behaviour, but I could not find it. Also checked the glassfish issue tracker and could not find anything about this.
Any help is appreciated.
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
subject: Glassfish V3.0.1 Filter initialization problem