Please help me by pointing me in the right direction.
I'm looking for a J2EE design pattern that deals with caching data locally on the application server (app server currently is not using EJBs - just JDBC).
This data is in table form (rows and columns), only needs to be remotely retreived once a day because it changes so infrequently, but is accessed so frequently by the application that I'd like for it to be in memory and available to all users of the application.
Where is the best place for this to live ? application level (in a class?, properties file), user session level, in an xml file in a server dierctory ???
Trying to find a discussion of the pros and cons, and possibly alternative solutions.
Thanks in advance.