Finally after seeing that JRebel won the JAX most innovative Java technology award, I am giving it a try. Sick of all the tomcat restarts.

Our normal build-deploy cycle would take about 25 seconds. On average, JRebel saves one developer from 10-12 builds per hour. That's roughly five minutes per working hour or 30-35 minutes a day per developer.

I'm afraid our developers might go for a strike if we say to them, ‘Hey, we're not going to use JRebel anymore.

It used to take 5 mins to rebuild and restart the server - now we see changes pretty much instantaneously. I saw the value right away.

Every delay sucks, so whatever causes less delays rocks.

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.

Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.

JRebel saves a lot of frustration from dealing with JSF, JPA and Tomcat. One big thing is I don't need to start Tomcat every time to see my code!

To whomever tells me 'I don't have time to lose trying to use JRebel', I would say 'You're actually losing time by NOT using it'

Jrebel is so awesome it almost hurts. Or rather, not using it hurts.

Saving time with JRebel is so amazing. No more redeployments... Refactoring classes, Refresh the page and that's it! Amazing stuff!

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