I am so much more productive with Java, JPA and Spring (and JRebel) than i was with RoR the last months… It’s really fun again.

Every java dev should have a copy of #jrebel installed. Buy it yourself if your workplace is cheap. It’s soo worth it.

I was attracted to JRebel because of its transparency, simplicity and efficiency. It’s easy to set up and very nice to use!

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.

We were attracted to JRebel because we had grown very frustrated with starting JBoss app sever constantly. After seeing JRebel mentioned in several blogs recently, we gave it a try. While it doesn’t eliminate app server restarts completely, we only redeploy about 10% as much as before, saving both time and attention span!

JRebel is a real solution for build/deployment pain in Java EE. Good product. It just works and doesn’t need a 3 hour configuration phase :)

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

Working with JBoss, Seam, JSF and the Eclipse JBoss Tools…It’s very painful. I had read about JRebel a couple of times on theserverside.com and javalobby and decided to give it a try. It works great.

#IntelliJ and #JRebel combined cost less than your consultant’s daily wages, but will boost his productivity x10. Why hesitate?

Why isn’t JRebel part of the standard Java SDK?

JRebel is one of the best utility I’ve ever seen. We have just met JRebel and loved it.

Alterar método, adicionar atributos, criar classes, restart servidor, isso era um ritual a cada hora do meu trabalho. Com JRebel posso alterar qualquer código java que já é refletido na aplicação em funcionamento. Muito bom.