tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: definitive answer on JSPC?
Date Wed, 05 Feb 2003 21:48:27 GMT
I'm working off 4.1.18 and it appears it has been the same all through 
4.x, even through the jasper rewrite of 4.1.4.

I understand this is the problem I'm facing - I was hoping for a cleaner 
solution than to run javac individually for the 200 or so JSP files. 
That is what I'll do if needed, so I'd appreciate the work you've done. 
I'll check out the ant list of any mention of it - I didn't think of 
that originally but it makes sense.

Still, I'd hope one of the jasper developers might shed some light on 
the other points?


Chris McNeilly wrote:
> Don't know how 'definitive' this is, but here are my experiences.
> Its a bug/feature of jspc, depending on how you look at it.  As it loads
> all relevant jsp files into memory to compile, it only used the file
> name, not the full path, making the compiler see all your index.jsps as
> the same, which causes the error.  I believe there is a fix for this out
> there somewhere.  I found a pointer to the fix on an Ant message board. 
> I also added functionality to Ant that compiles each jsp in its own
> memory space, thus working around the bug.  Let me know if you can't
> find the fix (it might already be part of the next Tomcat build) and
> want to dork around with my effort.  The work I did on it was back about
> 3 months ago, so I don't know what has been done recently.
> Chris

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message