Solve the problem that no prompt information is displayed in the Struts configuration file. The struts configuration file

Solve the problem that no prompt information is displayed in the Struts configuration file. The struts configuration file

(1) When writing the struts2 configuration file, you may not be prompted for all the information. After "<" is entered in the configuration file, there is no prompt information (use the shortcut key Alt +/or no prompt)

The reason is the following "http://struts.apache.org/dtds/struts-2.0.dtd" this is the need to get online!

If there is no Internet connection, there is no way to obtain information!

<span style="font-size:14px;"><!DOCTYPE struts PUBLIC    "-//Apache Software Foundation//DTD Struts Configuration 2.0//EN"    "http://struts.apache.org/dtds/struts-2.0.dtd"></span>

(2) There are two solutions:

First, you can directly connect to the internet!

Second manual Configuration

Step 1: window ---------- preferences ------------- myeclipse ------- files and editors --------- xml -------- xml Catalog

Step 2: click Add --------- File System

Then find your struts-2.0.dtd file (which is stored in struts-2.1.8 ----- \ struts-2.1.8 \ src \ core \ src \ main \ resources)

After selecting the Key Type, click the URI option!

Enter http://struts.apache.org/dtds/struts-2.0.dtd in the Key below and click OK

Close the page and open it again!

This is done!

In the struts2 configuration file, why is the tag property value not prompted?

It indicates that the plug-in is not completely reliable.

Don't rely too much on plug-ins. Reading the API documentation is a good way and a good habit.

Struts configuration file forwarding

1) struts. the jar file struts. jar has no source attachment. you can attach the source by clicking attach source below .) no error is reported, indicating that you cannot see the source code. Because you reference a jar package, you can't see it, and you can't learn English well.
2) org. apache. struts. action. requestProcessor. This is the real error reported by the background. This is also a normal Exception because it does not find the corresponding request processing node and cannot find the next processing place.
3) If BeanUtils. populate returns an error, you can search for it carefully. This is the key. Generally, your bean file or XXXForm. java file does not match the type of the access return value of the defined attribute.