|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1065 | minor | always | 04-20-06 08:18 | 06-27-06 14:49 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.20 | ||
|
|
|||||
| Summary: | 0001065: JSP precompile and batching | ||||
| Description: |
(rep by Bill Au) I had forgotten all about this until I was hit by this problem again yesterday. It seems to me that adding code to catch JavaCompileException in the compileBatch() method so that it will continue onto the next batch would be straight forward. Can that be added? With that fix in place. I am still face with the problem that one bad JSP will cause the while batch (64) of JSPs not to be precompiled. I guess we will have to live with that since that's how the Java compiler works. We have a webapp that contains JSPs whose sole purpose are to be included into other JSPs. They don't compile on their own. So they are causing other JSPs being compiled in the same batch not to be precompiled. I thought a way to get around this would be to make the JspPrecompileListener look for a <fileset> in is configuration to specify a set of JSPs for the precompiler listener to skip. But if the list if large that the overhead of figuring out which JSPs to skip may be to much. Do you guys see any good way to get around this? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||