At the beginning, I wrote JSP + JavaBeans and habitually used the default package. After the result is published to Tomcat 5.5.17, the corresponding JavaBeans class cannot be found on the JSP page in any way. The same web app is packaged into A. War and tested on the Resin server for a friend. In the script snippet on the JSP page (<%>), I explicitly call getclass (). getclassloader (). loadclass (clazzname) can load my JavaBeans class successfully, but jaspercompiler cannot find this class.
The world is full of Google, but all Chinese posts are vague .. Later, I saw the class not found issues section in the Tomat FAQ. I found that the JavaBeans must be located in a package, so I suddenly realized that. Modify my JavaBeans and test. Everything passes.
The strange thing is that this bug exists from Tomcat 3. Why does it remain unchanged from 5.5.17? Or is there no intention to change the tomcat-specific behavior?