If those lists are not user-dependant, you can put them in application
context. This way, they will be shared by all your users.
If they are user-dependant, I think I would have done a bean that
provides properties that get data from db on the fly.
Of course, if an error occur, it will be in jsp rendering ...
Maybe you can also put in request (not in session) frequently used
values with an interceptor ?
Mike
Daniel Chacón Sánchez a écrit :
Hi all, I'm using struts framework on my application, but I have a
perfomance question.
When my application starts I load objects in session that may or may not
will be used (depends on what the user does), for example I load the
health
centers, hospitals, countries, etc, that will be available for the
users in
html:selects, I know that to had many objects in session is not good, in
fact each time the user click on one application option (menu) all the
objects in session are erased, except the ones that I load on the
start of
the application. Is there a way (maybe a pattern) to load this objects in
the moment that are needed, and not load all at the start of the
application. This object are use on differents modules so I load them
on the
start of the aplication and put them in sesion for not to go to the
database
each time I need to load them on a html:select.
any solution, idea? or that is the only way?
--
Mike Baroukh
---
Cardiweb - 31 Rue de Mogador Paris IXeme
06 63 57 27 22 - 01 53 21 82 63 - Jabber: [EMAIL PROTECTED]
http://www.cardiweb.com
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
