| d2r diego's weblog |
myeclipse: wowAs it happens sometimes, I've now come full-circle on MyEclipse. To recap, I started thinking that, while nice, it was too slow for my needs. Then several comments on the entry pointed out that they were not seeing those problems. So after a few days, I decided to give it another try, and discovered that with the proper configuration it was actually not noticeably slower than Eclipse on its own. Now, after about 5 days of using it constantly, I have to correct myself and say that it is truly a fantastic addition to Eclipse. The hot deployment feature is the key to it all. Once all the proper deployment features are configured, you can be editing a file, make a change, save it, and then go to the browser and reload, and the changes are there, and this applies to both JSPs and servlets. Sometimes the hot deploy fails (usually when modifying static members or persistent classes) but that's not a big deal, and restarting the server is a span in those cases anyway. This, across pretty much every major application server that's out there, "out of the box". Other cool features include autocomplete on JSPs, support for JSTL and other JSP tag libraries. Anyway, if you use Eclipse and develop web apps and haven't tried MyEclipse yet, give it a try. Just make sure you configure it properly. :) Categories: soft.devPosted by diego on February 10 2005 at 2:47 PM | TrackBack (1) Comments (please see the comments & trackback policy).
MyEclipse is indeed a great piece of software to be added to Eclipse, the JSP Editor is really nice, though if you keep validation activated it might go mad on complicated jsp (they say on their forum it should be fixed in 3.9). As far as Hot Code Replacement is concerned, it is a must have!! You said it won't work in some case, it won't work when you change the signature of a method or of a class (new param, different return value, new static member etc etc) Posted by: Olivier Jaquemet at February 11, 2005 9:47 AMA way to expedite changes where Hot Code Replacement doesn't apply is to use the context reloading feature on containers that support it. This feature has been supported on Tomcat 4.x, for instance. I have found that a mid-sized application reloads within 10 seconds on an average PC, which a container restart still approaches 45 seconds or more (depending on the number of apps running on it.) I use 'Tomcat Manager' for eclipse to do this directly from within eclipse.. but the MyEclipse web browser with a bookmark to the manager app would work well .. as well. Cheers, Post a comment
Copyright © Diego Doval 2002-2007.
|
