The source of this article: http://www.cnblogs.com/superjt/p/3724968.html
When developing Web projects, are you still bothered by the pain of repeatedly starting web containers? Someone might say, with debug mode. But if it involves a configuration file or service class, you still have to restart the Web container, and occasionally there will be convulsions, not in effect (this time will make you feel that it is not effective? Or is there a problem with the code? is not very tangled).
Here's how the next resin is handy when developing Web projects
Unless you modify the Web. xml file and other Java files are modified, resin will automatically refresh-similar to hot deployment no longer requires a new code environment to be restarted in order to be able to get up-to-date coding environments---can save most of your development time
Resin and Tomcat are recommended for normal development. Do eclipse detailed debugging time with Tomcat (of course can also use resin do this function), do the Web debugging time with resin more convenient, the following detailed talk about eclipse in resin configuration bar
For resin debug Mode online introduction of quite little, almost no posts or articles about the integration of Eclipse and resin, most of them are simple to write the Eclipse plug-in way to start resin, about debugging mode start is simple several commands to end, It's not as handy as Tomcat!
It took a long time to find a way to integrate and eventually found:
Of course, you can see the interface--this is definitely using the plug-in behind the introduction of resin official Push plugin
Before you need a corresponding version of resin,: http://www.caucho.com/download/
Plug-in Installation: Http://caucho.com/eclipse
You can see this text to show that this URL is not a problem, can be updated as an Eclipse plug-in source
Open Eclipse Select Help-Software Updates ... Click on the ADD site on the right ...
Enter Http://caucho.com/eclipse in the pop-up dialog box (note that the blank space is deleted)
I do not know why I updated the name of the display is changed, the self-groping can also understand
After adding a site, click on the left tree to select Resin then the install in the upper right corner will lighten (my installation is so dark)
OK behind is the Internet download Update plugin ... (see here, if you say you do not have the Internet, then I will not say anything, hurriedly find a hammer to the computer smashed it ...) )
Window-show view-servers show up Server box
Then in the Servers box, right-click New a server this time will appear the top first picture of the resin, choose your own need for the version ... Here, just 3 and 4 with 2 ... 2 is 2. No way 2 of people have been buried ... Ha ha!
Resin 3.1 and temporary directory deploy will first package the project war and then copy it to the project's publishing folder, which is located under the workspace of your project. metadata\.plugins\ Org.eclipse.wst.server.core\tmp0\wtpwebapps folder) Disadvantage, the original war file will not be deleted when the project is changed for development ... Manual removal required
The other one (in space) is not packaged and copied directly into the Publish directory and publishes the project (recommended)
The second part of the installation needs to choose the JDK environment, which is chosen by the system or by its own designation.
The third step needs to specify your extracted Resin folder (above said download file, recommended to extract to the D-disk, such as D:\Resin)
I used to have a Tomcat server, and then I tried 2 different Resin on the back.
This shows the 3 boot servers, of course, which version you need to run first select then click on the right green run button!
============================= Ornate Split Line ============================================
1. Be aware that eclipse requires more than 3.6 versions to support.
2, for Resin 4.x configuration after the start will be error
' Default ' is a unknown server in the configuration file.
3. Configuring the Resin.xml File
<!---Resin 4.0 configuration file.-<Resinxmlns= "Http://caucho.com/ns/resin"Xmlns:resin= "Urn:java:com.caucho.resin"><!--property-based Resin Configuration-<Resin:propertiesPath= "${__dir__}/resin.properties"Optional= "true"/><Resin:propertiesPath= "Cloud:/resin.properties"Optional= "true"Recover= "true"/><Resin:ifTest= "${properties_import_url}"><Resin:propertiesPath= "${properties_import_url}"Optional= "true"Recover= "true"/></Resin:if><!--Logging configuration for the JDK Logging API-<Log-handlerName=""Level= "All"Path= "stdout:"Timestamp= "[%y-%m-%d%h:%m:%s.%s]"Format= "{${thread}} ${log.message}"/><!---Alternative PSEUDO-TTCC log format--<log-handler name= "" level= "All" path= "stdout:"-timestamp= "%y-%m-%d%h:%m:%s .%s "-format=" [${thread}] ${log.level} ${log.shortname}-${log.message} "/>-<!---level= ' info ' for production-' fine ' or ' finer ' for development and troubleshooting-<LoggerName=""Level= "${log_level?: ' Info '}"/><LoggerName= "Com.caucho.java"Level= "Config"/><LoggerName= "Com.caucho.loader"Level= "Config"/><!---Default configuration applied to all clusters, including-http, HTTPS, and/resin-admin configuration.-<Resin:importPath= "${__dir__}/cluster-default.xml"/><!---Health Configuration-<Resin:importPath= "${__dir__}/health.xml"/><!---Remote management requires at least one enabled Admin user.-<Resin:adminauthenticator><UserName= "${admin_user}"Password= "${admin_password}"/><Resin:importPath= "${__dir__}/admin-users.xml"Optional= "true"/><Resin:importPath= "Cloud:/admin-users.xml"Optional= "true"Recover= "true"/></Resin:adminauthenticator><!---For clustered systems, create a password in as Cluster_system_key-<Cluster-system-key>${cluster_system_key}</Cluster-system-key><!---For production sites, change Dependency-check-interval to Something-like 600s, so it is only checks for updates every 10 Minutes.-<Dependency-check-interval>${dependency_check_interval?: ' 2s '}</Dependency-check-interval><!--For resin.properties Dynamic cluster joining-<Home-cluster>${home_cluster}</Home-cluster><Home-server>${home_server}</Home-server><Elastic-server>${elastic_server}</Elastic-server><Elastic-dns>${elastic_dns}</Elastic-dns><!---Configures the main application cluster. Load-balancing Configurations-will also has a Web cluster.-<ClusterId= "App"><!--Define the servers in the cluster-<Server-multiId-prefix= "app-" Address-list= "${app_servers}" port= "6800"/>
4. Configuring the Host File
Detail Catalog: C:\WINDOWS\system32\drivers\etc\hosts
After the file is added
127.0.0.1 www.xxxx.com
5, directly can be entered in the browser
http://www.xxxx.com:8080/
Configuring Resin 4.x in Eclipse