以前老有人说 JRebel 调试的时候会出问题, 好像是需要配置一下才可正确调试, 这里转一篇官方的文章:
http://www.zeroturnaround.com/blog/how-to-install-and-use-jrebel-formerly-javarebel-in-tomcat-with-the-eclipse-ide/
September 9th, 2009 by Toomas Römer
Although this tutorial concerns the Tomcat container, exactly the same instructions also can be used for JBoss and Jetty containers.
Compared to other containers out there, the Tomcat web container is one of the fastest when it comes to startup and redeploy times. Still, in asurvey we conducted, developers estimate spending 18% of their coding time (about 145 hours annually, per developer – somewhere between 3-4, full, 40-hour workweeks) waiting for applications to redeploy. JRebel eliminates the need to redeploy in 80% of situations, and it’s easy to get started. In the embedded video you can take a quick look at how coding looks when using JRebel.
Tutorial
In this tutorial we explain how to install and use it step-by-step. We assume that you are using Eclipse 3.x with Tomcat 5.x or later. Most of the steps will be applicable to other versions as well, but it may look different from the screenshots included.
Contents:
STEP 1: Install JRebel
The latest stable version of JRebel can be downloaded here. Unpack it to a directory of your choice.
STEP 2: Installing JRebel Eclipse IDE plugin
The JRebel Eclipse IDE plugin was introduced with JRebel 2.0 and makes configuring and using JRebel considerably easier. You can install the plugin by going to Help » Software updates » Available software » Add site and use the http://www.zeroturnaround.com/update-site/ URL as the update site.
STEP 3: Make a rebel.xml for your application
In order to do it’s magic, JavaRebel needs to know where your classes and resources are. We’ll use a rebel.xml configuration file to tell it. This is mandatory when you deploy your app as a WAR/EAR. You’ll need to have one rebel.xml file per module. This includes both web and EJB modules. The rebel.xml configuration file should be placed in your WEB-INF/classes directory in the case of a web module and in the jar root in the case of an ejb module. Put it in the root of a source or resource folder in your project (the same place where the .properties files are).
If you use Maven you can use the JavaRebel Maven plugin that will generate the rebel.xml in accordance with the module pom.xml as described in theMaven Plugin configuration manual.
In 99% of cases, you probably use one module per project. In these cases, the JavaRebel Eclipse IDE plugin can generate the rebel.xml file for you, on a per project basis. If your project is one of the exceptions, edit the file manually as described in the Installation manual, otherwise generate the rebel.xml like this:
Click on your project and pick Generate rebel.xml.
Repeat this for all projects that you’d like to update with JRebel.
If you’d like to use one rebel.xml for your whole team, start with the generated rebel.xml, then replace the absolute paths to your workspace with a system property. JavaRebel will expand expressions like “${myProject.root}” in rebel.xml
to a system property that you can pass to the application container as -DmyProject.root=c:/myWorkspace/myProject
. This allows to you to use a single configuration for everyone and then customize it when starting the server.
STEP 4: Configuring the Eclipse WTP IDE
You may skip this step if you run Tomcat outside of the Eclipse IDE.
Open the Servers View and double click the Tomcat Server that your application is deployed to (if you don’t see the Servers View go to Window » Show View » Servers).
Open Publishing and choose Never publish automatically.
It may seem strange to disable automatic publishing, but as JRebel will take care of updates from now on it would just slow you down.
Open JavaRebel Integration and check Enable JavaRebel agent.
STEP 5: Configuring the Eclipse IDE
Go to Window » Preferences and from there to Java » Debug » Step Filtering.
Check Use Step Filters, Filter synthetic methods, and Step through filters. Now check all the default filters and use the Add Filter button to add com.zeroturnaround.* and org.zeroturnaround.*.
Now go to Project » Build automatically and make sure it is checked.
STEP 6: Success!
To check that the installation was successful, access a page that uses a class, change that class in the IDE, press Save, access the page again and look for the following message in the console:
Now that you’re up and running, it’s time to enjoy coding without the need to redeploy. If you have any specific questions JRebel, the Forum is the best place to ask, so that other people get to hear the answer as well. Otherwise, you can contact us at support@zeroturnaround.com.
If you like what you see, please give us a quick mention on your blog or twitter (you can even follow us here).
Have a great day!
Find out more:
相关推荐
JRebel eclipse 热部署
jrebel 配置eclipse 热部署 属于网络资源,与本人无关,如有侵权,请联系删除
idea中项目jrebel热部署配置步骤,附有步骤截图,请测有效
jrebel6.4.3热部署 eclipse插件
将文件解压到\eclipse\plugins目录下,重启eclipse,若还是提示注册认证,忽略他,其实已经是认证了的,直接运行代码就可以了,记着运行前需要配置JRebel—>勾选Enabel Jrebel agent
自己整理的jrebel idea插件 有详细的安装文档,和插件安装文件,亲测可用
Eclipse Mars.2 Release (4.5.2),maven 3.3.9,tomcat7,JRebel6.4.3,包内包含JRebel与详细使用说明,纯手写,且亲测可用,eclipse,maven,tomcat可自行下载,JRebel为破解版,码字辛苦,望各位大神给1分辛苦费
Jrebel+IDE热部署
update-site-jrebel eclipse maven热部署插件
资源为破解版的Jrebel热部署插件,在eclipse中配置好了以后,修改java文件无需再重启项目
你是否有过为修改后台代码,项目重部署而出现的漫长等待而烦恼,JRebel就是这样一套解决修改后台代码快速实现热部署的开发工具,节省了大量重启时间,提高了个人开发效率。
JAVA热部署安装及配置,实现IDEA无需频繁重启服务。通过自己手动配置,绝对能用!
jrebel 热部署工具 破解版
Eclipse中使用tomcat 热部署 Jrebel6.4.3 不需安装插件
由于百度谷歌了很多都用不了,要么就是最新版本的,破解用不了,最后还是搞定了不过版本是6.4.3的,好东西不怕旧,在这里分享给大家,该文件包含以下内容----JRebel6.4.3离线安装文件和破解文件以及安装配置说明文档...
eclipse+jrebel热部署插件和破解(测试可用)包.zip
Rebel是一款JAVA虚拟机插件,它使得JAVA程序员能在不进行重部署的情况下,即时看到代码的改变对一个...本文通过图文并茂的形式给大家介绍了IntelliJ IDEA 中使用jRebel进行 Java 热部署教程图解,需要的朋友参考下吧
jrebel for idea2017热部署,jrebel for idea2017热部署
亲自测试能成功破解 破解很简单将相应的文件替换即可
myeclipse 插件热部署 jrebel6.5 亲测可用,资源下载到磁盘,然后打开myeclipse 路径为:Windows ---> Perferences --> MyEclipse -->Servers -->Tomcat --> Tomcat 7.x -->JDK 配置jvm参数: -...