The new machine is replaced, and the system is upgraded from XP to 64-bit win7. Some old tools cannot be used directly. The following is a brief introduction to the title content.
1. Non-generic container classes cannot be compiled after jdk1.7. For a class such as Java. util. arraylist, the system prompts that the introduction cannot be solved. OK, uninstall JDK and install JDK 6.
2. Eclipse's resin support seems to have a version compatibility issue. The incompatibility between the two parties in this region is not very clear. After the problem is solved, I will not be able to solve it any more, so let's briefly talk about the process:
2.1 First, install various plug-ins in the temporary workspace, including resin support (4.0.27)
2.2 switch to the old workspace, hot deployment has some problems (this may be caused by JDK 7 Compilation)
2.3 change the JDK and change the resin runtime directory from version 4.025 to resin4.0.32.
2.4. The problem is that JSP is not deployed during deployment.
2.5 download resin4.0.27, delete the old resin runtime, and create a new runtime Based on resin4.0.27. Then start the server and OK will return to the normal debugging track.
3. Let's talk about the configuration information of the local server and leave a file for future reference. This information is just a personal preference and may be different from others.
3.1 do not select Remote Deployment
3.2 Select Directory-based deployment in the three list options. The other two may be selected, especially the last one.
3.3 automatic release upon resource change of the release method
4. aside: A project needs to use the old eclipse3.0 version + the corresponding myeclispe. However, if version 3.0 does not have a 64-bit versionProgramWhen the file is started, a 32-bit DLL cannot be loaded on a 64-bit platform. Sometimes, in order to be lazy and stick to the original environment, but the operating system will not wait for you, until a certain stage, you will find that you must move forward.