This was tested with JRebel 4.6.2 + Eclipse Helios + Tomcat 7.0.22 + Maven 1.6.0-31.
#JREBEL ECLIPSE CODE#
Here are the steps I followed to get JRebel replace the included HotSwap JVM capability to allow remote hot code replacement. Clearly the second advantage of this method is that when you are in needs to debug your real deployment environment you follow the same procedure: Just prepare your server to listen to a debug port and connect to it from Eclipse. I also debug all of them and in some cases at the same time without an IDE crashing or giving me extra trouble.
I prefer my local environment to be as close as possible to the production environment, so I run SSL, Apache with mod-jk, different IPs for different website projects etc.
I personally do not like servers running in IDEs. Sure JRebel is not free but for a buck a day you can get a floating license for 10 team members, or for a buck per three days get your personal license, or if you do not have a company and are trying to get in business with zero capital there is also an option for you: Just open source your project and get JRebel for free, then provide consulting services, make money and pay for JRebel: It is worth it. The JVM Hot Swap misses a lot of features provided by JRebel. However if you are serious about agility in Java as I said you must consider JRebel. As I have posted before there are ways to do agile Java Web development through hot code replacement so you do not have to say "Java sucks because you need to recompile to see your changes, that is why I code in you-name-it language".
0 kommentar(er)
