|
Problem |
When using the JspBatchCompiler, there is different
timestamp behavior on failed compiles depending on if the -filename option
is used. |
|
Cause |
If the compilation through the JspBatchCompiler is
successful, the code checks to see if the class files exist. If they do,
then it updates the timestamps of the class files so that they match the
timestamps of the JSPs.
If the compilation hits a failure, the compilation stops and does not
finish compiling the JSPs (which is the designed behavior). Even though
the compilation has failed, all class file timestamps are still modified
so that they match the timestamps of the corresponding JSP (if the class
files exist).
If the -filename parameter is used, only the specified file is
included. If there is a compilation failure it is understood that the
classfile was not generated, and the timestamps will not be updated. |
|
Solution |
This is working as designed. |
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|