The only difference i know, is that jsp:include actually creates a new
context for each page, so the included page writes directly to the
outputstream, and bean:include caches the result of the included page and
writes it out at once.
So if you are playing with flush-attribute or having uncaught
Dave Newton <[EMAIL PROTECTED]> wrote on 08/17/2005 02:33:03 PM:
> Laurie Harper wrote:
>
> > sajith kumar wrote:
> >
> >> In our proj we were using bean:include to include alternative jsp's
> >> based on some conditions thru action class
>
> I would also ask how was replaced by
> and sinc
Laurie Harper wrote:
sajith kumar wrote:
In our proj we were using bean:include to include alternative jsp's
based on some conditions thru action class
But when Concurrent users were acessing the system the application
didnt respond
We changed our logic by replacing bean:include with logic:eq
sajith kumar wrote:
Hi all,
Is bean:include thread safe?
In our proj we were using bean:include to include alternative jsp's based on
some conditions thru action class
But when Concurrent users were acessing the system the application didnt respond
We changed our logic by replacing bean:include
4 matches
Mail list logo
