Tomcat PK Resin, tomcatpkresin
Features |
Tomcat |
Resin |
Company |
Apache |
CAUCHO |
Number of users |
Multiple |
Less |
See the documentation |
Multiple |
Less |
Complexity of integration with Eclipse |
Moderate |
Complex. |
Debugging and development under Eclipse |
Easy to use |
Complex: automatically restarts after the class is updated. |
Start the deployment Environment |
Bloated |
Human Nature |
Hot deployment support for development environment |
Better, you can configure as needed. When modifying Jsp or java files, you can configure whether to restart the service. |
Poor. When the class and jsp files are updated, the system will automatically re-deploy and restart the system. It is troublesome to develop programs when Session is configured. |
Hot deployment support in production environment |
Average. When updating the configuration file, you must restart it manually. When updating other files, most of them do not need to be restarted. However, when too many files are updated at a time, Tomcat restart may often fail. |
Better. When the configuration file is updated, Resin restarts automatically. |
Cluster deployment |
Supported |
Supported |
The difference between resin and tomcat jsp
For jsp, resin and tomcat are nothing more than different servlet servers. From the perspective of jsp writing, there is basically no material difference, from the perspective of practical applications, resin may have better performance than tomcat (I heard that it has not been tested), but tomcat is purely open-source and free, while resin commercial applications are charged.
How does tomcat go to resin?
JSP files are not written on the server software. As long as there is no syntax problem in writing, No matter Tomacat, Resin, or WebSphere, you just need to put the file you have written in the corresponding folder of Resin from the Tomcat folder.