supermanhamuerto.com

User Tools

Site Tools

Trace:
java:hotdeploymenteclipse

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
java:hotdeploymenteclipse [2014/05/19 07:41] – rlunarojava:hotdeploymenteclipse [2022/12/02 21:02] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== The fastest way to make a deployment in eclipse ====== ====== The fastest way to make a deployment in eclipse ======
 +
 +<WRAP center round info 60%>
 +**Update about Tomcat**
 +
 +When I started this tutorial, I've found that every single change
 +in a web page under JBoss forces this to restart the application. 
 +
 +Unfortunately it is not the case with Tomcat: Tomcat ignores everything
 +else except web.xml, and this is a bit cumbersome if you are changing 
 +jsf or jsp pages frequently, because these changes aren't detected 
 +and refected by Tomcat. On the contrary, the pages appear unchanged. 
 +
 +With other J2EE servers I don't have an idea of what will happen....
 +</WRAP>
 +
  
 Although eclipse has a system to deploy applications to the application server of our choice (Tomcat, jboss, Web Sphere, etc.) I think that the system it uses is extremely slow. Other solutions that have appeared ([[http://zeroturnaround.com/software/jrebel/|jrebel]] (commercial), and others are depicted [[http://stackoverflow.com/questions/998737/integrating-tomcat-and-eclipse-as-a-hot-deploy-environment|here]], [[http://techblog.bozho.net/?p=1246|here]], [[http://stackoverflow.com/questions/2296387/jsf2-and-maven-hot-deploy|here]] and [[http://stackoverflow.com/questions/1793533/hot-deploy-of-development-changes-with-eclipse-tomcat-and-jetspeed|here]]) involve in some way keeping a synchronization of files between the deployed application and the developed application. Although eclipse has a system to deploy applications to the application server of our choice (Tomcat, jboss, Web Sphere, etc.) I think that the system it uses is extremely slow. Other solutions that have appeared ([[http://zeroturnaround.com/software/jrebel/|jrebel]] (commercial), and others are depicted [[http://stackoverflow.com/questions/998737/integrating-tomcat-and-eclipse-as-a-hot-deploy-environment|here]], [[http://techblog.bozho.net/?p=1246|here]], [[http://stackoverflow.com/questions/2296387/jsf2-and-maven-hot-deploy|here]] and [[http://stackoverflow.com/questions/1793533/hot-deploy-of-development-changes-with-eclipse-tomcat-and-jetspeed|here]]) involve in some way keeping a synchronization of files between the deployed application and the developed application.
Line 116: Line 131:
  
 === Tomcat 6 and Linux ===  === Tomcat 6 and Linux === 
 +
 +**Important:** You have to edit the ''context.xml'' file and set the "reloadable" feature as this: 
 +
 +<code xml>
 +<Context reloadable="true">
 +</code> 
 +
 +Also, as cited [[http://www.mulesoft.com/tcat/tomcat-reload|here]], you can add some //watched resources// that, upon change, will force tomcat to reload the application.
  
 Assumed you have the configuration of your project as described before, the only thing you have to do is create the symbolic link.  Assumed you have the configuration of your project as described before, the only thing you have to do is create the symbolic link. 
Line 187: Line 210:
  
 ~~DISQUS~~ ~~DISQUS~~
- 
  
  
  
  
java/hotdeploymenteclipse.1400485306.txt.gz · Last modified: 2022/12/02 21:02 (external edit)