hi;
i have many applicataion scope managed beans that act as a cache.
up until now, creating them lazily through the managed bean creation facility 
was fine.
as my application grew bigger i noticed it was better to have these beans 
populated on startup.
the problem began when i noticed the managed bean creation facility only 
supports lazy creation.
i had to leave the managed bean creation facility (which i love) and go with a 
servlet context listener instead.

can someone please explain the rational of not providing an 'application scope 
beans creation on startup' functionality build into the managed bean creation 
facility of JSF?
thanks.

Reply via email to