Hi,
>way. The bug fix seems to indicate the any exception
>should be rethrown so I expected to see it. It seems
>that the old -v option (for verbose ouput, i.e. -v4,
>-v9, etc.) for jspc is no longer valid. Is there a
>new option that will possibly produce more output?
I don't know, you'd hav
Hi Yoav,
Thanks for the reply. I'm stuck using 4.1.18 so the
bug still applies to me :). However I did take my
webapp code and copy it into a 5.0.19 install I had
laying around. I then ran the compile under 5.0.19
and saw that no 0 length java file was created (this
version must have the bug fi
Hi,
>First off, the 0 length Java files are due to a bug in
>the Tomcat jspc compiler documented in this post:
>
>http://junlu.com/msg/41035.html
No. The post doesn't discuss why the files are 0-length, only the
consequences of them being 0-length (such as they're ignored by javac).
The bug ref
First off, the 0 length Java files are due to a bug in
the Tomcat jspc compiler documented in this post:
http://junlu.com/msg/41035.html
Secondly I discovered that if I keep the JSP around
and then simply access it through a browser Tomcat
compiles the JSP correctly and I end up with a valid
.jav