How to operate JGeometry object 2 and spatialjgeometry provided by Oracle Spatial in the back-end JSP file

How to operate JGeometry object 2 and spatialjgeometry provided by Oracle Spatial in the back-end JSP file

I have written an article to record some of the problems I encountered. This time I updated my new host and encountered some problems. Now I have solved them and I will record them. Because of these problems, people who know it can quickly solve them. People who don't know it can spend a lot of time doing it. People who don't know it can still be confused.

See this for previous articles.

The main errors are as follows:

1. click a button to call 1. after the jsp file, it is normal that the corresponding HTTP Status values are 0 to 200 to 200 to 200 during the State process from 1 to 2 to 3 to 4; an error occurs here. The State goes from 1 to 4, and the HTTP Status values are both 0.

After reviewing the web page elements, the following error occurs:

Although the error "No 'access-Control-Allow-origin' header is present on the requested resource" is reported here, the following sentence is added to the called JSP file:

Response. addHeader ("Access-Control-Allow-Origin", "IP addresses: 8888 ");

In addition, the IP address that follows is changed to the correct IP address of the new machine.

Click the URL after cannot load in the error message to open the following page:

We can see that some types are not defined. Therefore, it should be a package import error.

In this way, I copy the required ojdbc-related jar files and several imported sdoapi and sdoutl. jar files to the lib folder under Tomcat 7.0. Note the lib folder in the Tomcat 7.0 folder. It is not the directory where the current jsp file is located, nor the lib folder under the directory where the jsp file is located. The jar related to ojdbc already exists in the latter two, or the above error is reported. Copy to the lib folder under Tomcat 7.0 to solve the problem.

Note: The required and imported packages must be placed in the lib folder under Tomcat 7.0. Restart Tomcat. (I am not familiar with Tomcat deployment .)

Refer to this page, but the problem is not the same.