BEA uses Catalina, which is Tomcat, inadvertently found a very hidden BUG, in the JSP, if the label somewhere is performed, there is no abnormality when outputting the buffer in front of the buffer, not Error exception is issued in real error locations.
10:45 points: I found that FormTAG did an abnormally exit, and the error log did not have any output; so I decided to turn to see what is going on. Very strange, even if you enter a breakpoint in DoendTag, the error log still does not output. The final examination result is not a wrong program, but under certain conditions, TAG does not respond to Output, and the VAILDATORScript requested is only half.
This tag integrates Struts.validator's JavaScriptStatAg. I don't know if anyone does this: I don't want to take time to rewind the code to dissect it, and I don't want to let the front desk. Several TAGs need to be configured; so directly with the super-level FormTag Set to it, then call it DostartTag () - Actually, do you call your method in the JSP container? This error was found before, but it returned to normal. Since the abnormality disappears, the error log has not been recorded, and it cannot be discovered. This reappear, causing me to pay attention, and the error duration is relatively long, so you can set a breakpoint in the program to track the position of its error.
As a result, the error source is concentrated in not what I wrote, from the Validator from Struts. For the intermediate components such as Struts, my current attitude is if I can't finish understanding the code, I can set the breakpoint record to output to the error log Degbug, so I don't add, so now I have struts in my hands. Component function, usage method is completely different from the generally seen Struts, which also includes this JavaScripStatAg. For its usage, I hope it as part of the program, when I choose to verify a client client, it automatically completes the required code output, and doesn't need me to set up this TAG. To match its call function name. This integration is successful, has been running for a long time, often has a certain strength test, but it is flat, and I still haven't deeply in which I have code.
After the error, I intend to output breakpoints to the buffer, because this program is to output the JavaScript code in validator-rules.xml to the page, but it is not successful, and many breakpoints have no output; indicate that the program output is interrupted. However, the output process is normal, otherwise the error log will record. Further validation indicates that the program operation and JavaScript obtained from the memory record are complete, eliminating the possibility of reading XML errors, and also proves that the operation of the Java program is completely normal, error is not in the developer program, and The platform itself, there is no abnormality when the buffer is output! ! ! Since JavaScriptTAG is used to use StringBuffer last toString to output to the buffer, or because this amount is too large, it overflow? ? So I divided it into a para segment, but the result is exactly the same. Perhaps because I don't have the container for its call, the buffer allocation is minimized by the Parent-TAG call method? ? So it is changed to the getString method, and the output is output by the Parent, but the result is still the same. Finally, I plan to cross this step, see how the execution result is found, found that BSelectTAG Since the debated BaseIF interface was configured last night, the error was abnormal, so after recompilation, then executed, and found that the above error disappears. . Re-recover this error, exception reappears. This also discovered it. In fact, BEA uses a CatlineaJSP container to explain a JSP page is a unified process. This exception indicates that the output text generation before and after JSP is associated, and the program is running in the latter run error, like Methodnofound (I estimate) when running in the back, because even the server log does not find error records) It also makes this interpretation execution process, resulting in half of the buffer text to output halfway.
I rarely handle JSP, this is an experience. If this buffer exception output does not capture any error logs, first compile this page, exclude this possible.
This problem spent two hours for two hours, indeed concealed, some side effects were familiar with the code of Validator.javascript, and the project was a little time, just output it, only output this needed verification method Script : I always think that it has output too much, and all Script methods in validator_rules.xml are all sent.
