Loading Data at app startup

[subhadeep chakraborty]

Hi,
I have a situation where on each login huge data is fetched from database and stored into the users session. I do not want the database query to run every time and want to load the data at application startup in applicaion scope thus making session contain less data and also decreasing the database query time. My whole application is getting the data currently from session and I donot want to change it. Is there a way to do this ?
Is it possible to override weblogic 10.3's HttpSession implementation and override getAttribute() to do my work.

Thanks,
Subhadeep

[Martin Vanyavchich]

If I understand you correctly you need just one copy of that data, and it should be fetched only once. You could put the data in a static variable, check if it's empty and fill it form DB.

[Sunil Kumar]

In a web application, people typically do this in servlet and load that servlet on startup using web.xml like

    <servlet-name>Init</servlet-name>
        <servlet-class>test.init.Init</servlet-class>
        <load-on-startup>1</load-on-startup>  

[David Newton]

A startup listener should be preferred to an init servlet

[Sunil Kumar]

Rather than servlet use listener. Read the comment from Ben Souther
https://coderanch.com/t/361567/Servlets/java/load-startup-tag-Vs-listener

[Sunil Kumar]

Yes, right David. https://coderanch.com/t/361567/Servlets/java/load-startup-tag-Vs-listener will help differentiate amongst the two as i said above.
Thanks David.

[Campbell Ritchie]

Moving to servlets forum.

[subhadeep chakraborty]

hi,
Thanks for you response.My existing application gets the data from session and if I store the data in application
context I shall have to go through the whole application and change.I do not want to do that.

Is it possible to override weblogic 10.3's HttpSession implementation and override getAttribute() to do my work.

Is there a different way?

Thanks,
SUbhadeep

[Bear Bibeault]

Applying a band-aid that will make your code fragile and confusing is not the best approach. Take the time to refactor the code properly.