> We're using a solution somewhat like this but we only cache for a
> session/transaction and has no need for the invalidating. But we do
retrieve
> data "lazily" from the EJBs.
> Better solution is: Keep as little code as possible in the JSP-page, that
> coding is often subject to much change, instead build a JavaBean which
> automagically retrieves fresh data if invalidated.
>
> This performs "extremely" well since compiled JSP communicating with
> JavaBeans is extremely fast (of course depending on servlet-engine
> implementation).
>
This is basically what we came up with. All of our JSP beans would
communicate with one central caching bean that was stored in the
ServletContext. This way all of our JSP beans would be for displaying
content and we could eliminate all of the extra code inside the actual JSP
pages.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
