Stopping and start my container 10 times a day is the most annoying thing in the Java world. Finally I hope I have found the solution with JRebel.

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

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.

I see JRebel as this "missing piece" in the whole picture where we could see Java-stack not only as a stable, well-tested environment to build applications on but also as a rapid development environment.

I like the way [JRebel monitors] the file system for changes and smartly reloads Java changes into Hot Swap/Hot code memory. It just eliminated by build time during development by 90%.

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

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 :)

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

We had a need for faster turnarounds since we have huge projects that take ages to build and deploy. Jrebel is an excellent tool to reduce that time:)

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

Life without JRebel is no fun...

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.