Included JSP

[Pilho Kim <ph...@math.soongsil.ac.kr>]

Hi, 

I am using Tomcat 3.2.1.

Suppose that a.jsp includes b.jsp.
First visit http://localhost:8080/a.jsp and then modify b.jsp.
Then although reload the page http://localhost:8080/a.jsp,
the included part of b.jsp, is not changed.

But http://localhost:8080/b.jsp is the new one.

Why?

Thanks,
Kim

Re: Included JSP

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Pilho Kim wrote:

> Hi,
>
> I am using Tomcat 3.2.1.
>
> Suppose that a.jsp includes b.jsp.
>

There are two kinds of includes -- compile time (<%@ include file="b.jsp" %>)
and runtime (<jsp:include page="/b.jsp".).  Which did you use?

> First visit http://localhost:8080/a.jsp and then modify b.jsp.
> Then although reload the page http://localhost:8080/a.jsp,
> the included part of b.jsp, is not changed.
>

If you are using compile time includes, Jasper does not notice changes in
dependent files -- it would only recompile if a.jsp was changed.  For runtime
includes, this should work correctly.

>
> But http://localhost:8080/b.jsp is the new one.
>
> Why?
>
> Thanks,
> Kim
>

Craig

Re: Included JSP

[cm...@yahoo.com]

> I am using Tomcat 3.2.1.
> 
> Suppose that a.jsp includes b.jsp.
> First visit http://localhost:8080/a.jsp and then modify b.jsp.
> Then although reload the page http://localhost:8080/a.jsp,
> the included part of b.jsp, is not changed.
> 
> But http://localhost:8080/b.jsp is the new one.

The problem will be resolved in 3.x - JspInterceptor and the
improved class reloading ( DependClassLoader ) can deal with that.

I don't know any workaround for 3.2, and I don't think a fix would be
easy.

-- 
Costin