Differences

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

--- java:hotdeploymenteclipse [2014/05/17 23:47] – rlunaro
+++ java:hotdeploymenteclipse [2022/12/02 22:02] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== 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.
@@ Line 74: / Line 89: @@
 === Jboss 5 and Windows XP ===
-<WRAP center round todo 60%>
+Assumed you have the configuration of your project as described before, the only thing you have to do is create the symbolic link.
-Pending work
-</WRAP>
+For this example, I've have my Jboss installation under ''c:\jboss'', and I will refer it as JBOSS_JOME.
+To make the symbolic link you need first to install ''junction'' command, where you can get it [[http://technet.microsoft.com/es-es/sysinternals/bb896768.aspx|here]].
+After installing, you should issue a command like this:
+<code>
+junction "JBOSS_HOME\server\default\deploy\myTest.war" "c:\workspace\myTest\WebContent"
+</code>
+== Start the business ==
+The only thing you have to do to start the application is the following:
+  * Please, before of everything, remove all the "servers" in eclipse: remember that running the application through eclipse will spoil everything because eclipse will try to overwrite the deployment directory, and because it is the same directory as your webContent directory, everything will be mixed up and spoiled. You have been warned.
+  * Start the Jboss application server, manually, ''JBOSS_HOME/bin/run.bat''. It is a good measure to have a look to the logs, you can issue a ''tail -f LOGFILE'', but the detailed instructions are for another chapter
+  * Start your eclipse application: you can easily verify that every change in the application is reflected instantly in the Jboss directory and Jboss redeploy automagically your application reflecting every change
+== Debugging ==
+**You can also debug your application.** To do so, edit the file ''JBOSS_HOME\bin\run.conf.bat'' and add the following line:
+<code>
+rem # Sample JPDA settings for remote socket debugging
+set "JAVA_OPTS=%JAVA_OPTS% -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n"
+</code>
+This will make Jboss to hear from the port 8000 for debugging interruptions. Who will interrupt JBoss?? Properly configured, eclipse will do.
+In your eclipse click on run -> debug configurations. Under "Remote Java application" click on "new":
+{{:java:20140519_1.png|}}
+Configure it with the apropiate values (remember, port 8000) and you will have an entry like this:
+{{:java:20140519_2.png|}}
+Whenever you want to debug your application you only have to start the remote debug option you have created. This will make your application to stop in the step points you have set.
 === 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.
@@ Line 151: / Line 210: @@
 ~~DISQUS~~