For the price, and for how easy it is to get installed and running in a developers’ environment, using JRebel is pretty close to a no-brainer.

Setting up JRebel was completely painless and my questions on the support forum were answered quickly. The performance gains were immediately obvious to us, so after the evaluation period was over we decided to purchase licenses for all our developers.

Everyone who has tried it has fallen in love with it.

JRebel seems to be the only cost effective way to accelerate the compilation and startup of our projects, consisting of several EAR artifacts deployed on a JBoss App Server. We have been using it for a year, and my development team is very pleased with it.

Con JRebel, salvar un archivo en el IDE y ver mis cambios inmediatamente en la pagina sin tener que volver a hacer "deploy", no tiene precio.

JRebel has the ability to change code dynamically when the program is running or during a debug session, which I have been looking for a long time. I am sure it will save a lot of development time, especially when the size of the project is large.

Just a few compiles without having to deploy was enough to convince me to buy JRebel.

Jrebel is one those small non-intrusive pieces of software that you just can't live without!

Since introducing JRebel to our Java development teams, we have not only seen a 30% increase productivity, but also a marked decrease in service requests due to software faults. Our teams can now focus 100% of their attention on development without being hindered by the J2EE cycle Build and Redeploy steps.

So far, everybody I speak to about JRebel is satisfied with it - frankly, I cannot believe nobody thought of JRebel before.

I have been very impressed with JRebel, wish I had come across this product a lot sooner, would have saved me so much time/boredom waiting for so many container restarts.

You mean you haven't tried JRebel already! How could you have survived this long as a Java developer without it!