Jrebel base code#
Jrebel base license#

There are some pitfalls which I had to resolve: Someone of the JRebel guys should extend and improve the documentation! My main criticism: The documentation is bad.

Jrebel base code#

You just have to add a JAR file and add one line of code to the configuration of the application server.

JRebel is installed (and also removed) within 10 minutes. It is excellent value for money! You can save a lot of time by investing this little amount of money.

Jrebel base license#

Open source and Scala projects do not have to pay any license costs. The support is fantastic! You get very quick responses with detailed explanations. The standard edition costs 189 USD for one year per developer. So you can start the application server in debugging mode, make some changes, set a breakpoint, and see the changes immediately. My colleagues also did not trust the promises at the product’s website, so I had to give them a live demo 🙂 I was very sceptical before trying out JRebel by myself. I would never ever think about developing a J2EE / JEE project without JRebel (especially if WebSphere is the used application server). I can confirm you: JRebel works as promised! You can save plenty of developtment time. IDE-Plugins are available for all major Java IDEs: Eclipse, NetBeans and IntelliJ IDEA.Īll features of JRebel are described and compared to other solutions at Does JRebel work? Spring, Hibernate, JBoss Seam and some further Web-Frameworks are also supported. Besides allowing simple changes such as adding methods, fields, classes or annotations, you can also change EJB interfaces, JSPs, JSF and JPA code, XML config files and so on. JRebel supports all important application servers such as WebSphere, Weblogic, Tomcat, Glassfish and so on. If you want to understand how it works technically (you do not need this knowledge to use the product), you can read a detailed explanation here: Features of JRebel You save your class, the IDE compiles the class, and you can see the changes within one second! JRebel is a product which promises to solve this problem.

Other application servers have the same problem, although they are probably not as lame as WebSphere.

So, sometimes you have to wait 50 percent of your working time until WebSphere is ready again. to add a ) takes about 15 minutes in our project for publishing the changes, because you always have to do a build and redeployment. Even changing a single line of code (e.g. If you develop with WAS, no matter if it is version 5 / 6 / 6.1 / 7, deployment takes a very long time. If you need some neutral information about this product to ease development with J2EE / JEE applications and application servers, this blog entry is for you! Problems with JEE Application Servers I want to share my experiences with JRebel ( ). Let’s look at an example.JEE Development using JRebel with IBM WebSphere (WAS) 6.1 and RAD 7.0 This service manages and loads the class and method versions using anonymous inner classes created for each version that is reloaded. In the case an application class is loaded, all method bodies will have a redirection using the runtime redirection service, as shown in Figure 2. Jrebel instruments the application and JVM classes to create a layer of indirection.

This is the closest reasoning I have read on how JRebel works by Simon, ZT Technical Evangelist.