«« Next » « Previous
«« Next » « Previous

Link Details

Vote early, vote often! When you help pick the links, you'll like DZone better. Login and vote now.
Link 83551 thumbnail

By veerakm
via javabyexample.wisdomplug.com
Published: May 29 2008 / 23:55

Until recently any change to the source code would require you to stop the application, compile the classes and start your application again. Javarebel claims to change all that – you do need to restart your application if some classes are changed. Is it really so good?
  • 12
  • 3
  • 1226
  • 454

Comments

Add your comment
User 209464 avatar

willcode4beer replied ago:

1 votes Vote down Vote up Reply

With Eclipse WTP, just run tomcat in debug mode for this ;-)

User 107114 avatar

daniel replied ago:

0 votes Vote down Vote up Reply

Doesn't work as well as one would hope. I used to do that, but the Tomcat instance still has to spool a reload in order for certain changes to take effect. Jetty in debug mode works extraordinarily well, and JavaRebel makes it even better.

User 152955 avatar

Gregg Bolinger replied ago:

0 votes Vote down Vote up Reply

It's really not the same thing. Tomcat will reload the entire web app. JavaRebel reloads individual classes without the need to reload the entire app. Its not perfect, but it has its uses.

User 152955 avatar

Gregg Bolinger replied ago:

0 votes Vote down Vote up Reply

There is a bunch of talk about JavaRebel and webapps and yes, there are issues there. But during something like Swing development it can really save you a ton of time. Imagine a complex UI where getting to a particular form takes several steps. With JavaRebel you can save a lot of time not having to restart your GUI and stepping through all the fluff to get to the form you need and see changes. Close the form, let the IDE compile, open the form again.

User 196387 avatar

Jevgeni Kabanov replied ago:

0 votes Vote down Vote up Reply

It's actually quite the same with webapps.

User 152955 avatar

Gregg Bolinger replied ago:

0 votes Vote down Vote up Reply

No, it's not. Javarebel has very basic support for handling different framework specific API's and really each framework dev team would need to take the time to really make javarebel work well with it. For Servlet/JSP based web apps, sure, javarebel works as stated. But no one really does that anymore.

User 196387 avatar

Jevgeni Kabanov replied ago:

-1 votes Vote down Vote up Reply

The guy actually just went through our FAQ (http://www.zeroturnaround.com/javarebel/faq/) and copied stuff from there with mistakes. I don't think he actually tried using JavaRebel.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.