• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Glassfish V3.0.1 Filter initialization problem

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

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.
 
Lookout! Runaway whale! Hide behind this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic