When I deployed a test environment for the test group for the first time, I encountered a lot of problems. Almost all the pages could not be opened. The result showed that WebLogic was very strict with JSP verification, an error is reported when an nonstandard writing method or a non-existent class is introduced in the label. These problems are not found in Tomcat. The error is as follows:
1. XX labels introduced on the home page, while xx. tag in TLD has a class 2 that does not exist, in the struts tag introduced on the xxx page, <% @ taglib uri = http://jakarta.apache.org/struts/tags-template prefix = "template" %>, the tag is in struts. the jar package does not exist. Therefore, an error is returned when this label is introduced. 3. the JSP Import Statement is not properly written on the XXXX page. <% @ page import = "com. XXX. config. xxx;
An error will be reported in weblogic.Com. XX. XXX "%> 4. In XX multiple pages, you need to include other pages. On the parent page and child page, there is a character set setting statement <% @ page contenttype =" text/html; charset = GBK "%>. Fortunately, the subpage does not contain Chinese characters, so you can safely delete this statement. 5. The request object in Weblogic is different from the request object in Tomcat. There is no problem with the request. getlocaladdr () function in Tomcat, and there is no such method in weblogic. 6. On the xx Page, a tag in the TG tag is used. One of the attributes is not defined in the class, and the get and set methods are not used. As a result, the page cannot be displayed. Therefore, you must pay attention to the encoding in the future ~
