| d2r diego's weblog |
myEclipse: slowAnd continuing with the "Eclipse" theme this morning... :) In contrast to PHPEclipse, myEclipse actually has a nice, straightforward installer, and at the beginning everything seems to be fine. But eventually things st-art-to-slow-down. The pages I was editing include JSP tags, that seemed to confuse the JSP editor to no end, and over about two days things started to get slower. The only reason I can think of for why this started happening is that the JSP pages I was editing got progressively bigger, with more tags and commands to verify. Restarting Eclipse didn't help. Changing the memory settings (giving Eclipse 384, 512 megs of RAM) didn't help either. The "hot deploy" feature of myEclipse is nice: it allows you to specify a variety of app servers and hot deploy to them. But. But. It severly constrains you from actually tailoring what is deployed and how, pretty much forcing you to create a certain structure in your source tree so that the deployment process works well. If you do that, however, you get some pretty good functionality. Slow though, very slow. At least on my P4 with 1 gig of RAM. It was slo slow in fact, and I was getting so little benefit from it (I couldn't use the hot deploy, etc) that I just had to uninstall it and go back to just Eclipse. Btw, when I say "go back to Eclipse" I mean that I had to reinstall Eclipse, since myEclipse left trash everywhere in the .metadata and .plugin directories and was making certain things fail (e.g., the Ant build) in Eclipse after the uninstall. In particular, the Ant build problem had to do with invalid settings under the workspace removing the directory workspace/.metadata/.plugins/org.eclipse.debug.core/.launches solved that. Next up to try: Eclipse Web Tools project. For now, though, back to work. Bonus: Over at the PHPEclipse site I learned about the "-clean" Eclipse launch option (There's also "-initialize"). Good for when you change install directories, etc., and it is not documented in the page I generally end up at when looking for Eclipse command line options (is is mentioned here though). Update (a week later): Here's a follow-up to this entry, where I finally got myEclipse to run properly. Categories: soft.devPosted by diego on January 30 2005 at 9:42 AM | TrackBack (0) Comments (please see the comments & trackback policy).
Sounds fishy. We're using MyEclipse every day and have none of the problems you are talking about. Only speed issue I can come to think of is when doing a clean build of the project since it validates all JSPs which seems to be taking some time. As for the project structure, yes it imposes some restrictions, but actuelly you can change most of it. (the web root etc.) It just defaults to some stuff. The most important thing when creating projects is the "nature" such that MyEclipse can add the correct properties and know how to deploy each project. The hot deploy is extremely nice. I can't even count how many hours the ability to debug and change code in my Struts Actions and classes without redeployment/reloading webapp has saved me. You should give it another try. :) Anders, Posted by: Anders Sveen at January 30, 2005 4:13 PMThanks Anders, I wonder if it's the machine... Eclipse runs perfectly fine on this system, but maybe adding myEclipse was too much. I'll definitely give it another try when I can! Posted by: Diego at January 30, 2005 6:02 PMI am also using MyEclipse everyday and am having a great time with it except for wasting a lot of time guessing and fiddling with deployment options. Eclipse itself causes funky build issues as well, particularly with automatic rebuild feature. I am using Eclispse+MyEclipse on two systems, a desktop with 2G of RAM and a laptop with 1/2G of RAM. Laptop version is a little sluggish but not to the point of being unusable. So the problem might be either that particular machine or the difference in responsiveness between your previous IDE and MyEclipse. Posted by: Don Park at January 30, 2005 10:50 PMDon, my previous IDE *is* Eclipse. :) And my machine is better than your laptop spec... I wonder if it's the JSTL I'm using. Are you using plain JSPs or tag libraries in any of your JSPs? Have you used JSTL or the Struts tag libraries without problem in complex JSPs in myEclipse? Thanks! Posted by: Diego at January 30, 2005 11:57 PMI use JSP, taglibs, struts, and JSTL. Weird. Posted by: Don Park at January 31, 2005 3:47 AMDiego, check this article out and see if it helps. http://java.about.com/od/eclipseplatform/a/perform_tips.htm Posted by: mal at February 1, 2005 5:38 PMThanks mal! I'll give it a try when I can. Posted by: Diego at February 1, 2005 5:40 PMDiego, Once the taglibs are corrected and MyEclipse can verify them it should be smooth sailing for you. Also as far as the strict project structure and deployment requirements are concerned, the user that followed up is right. "out of the box" it may seem restrictive, but as you start customizing the project directories and adding dependent projects to your existing projects (e.g. a Web Project depends on a Library Project you are working on) and noticing that MyEclipse starts auto-packaging and deploying all that for you, it seems less restrictive. You might want to check out the Windows > Preferences > MyEclipse > J2EE Project > Web Project settings. Also as you found out -clean is a great way to clean out ulgy crap from your metadata folder (sorry to hear you rain into some problems after uninstalling) Lastly, if you have any more questions or run into trouble like this again, we would be more than happy to help you either via email (support@myeclipseide.com) or visiting our Forums (http://www.myeclipseide.com/PNphpBB2+main.html). Our turn around time for answers is usually in the realm of 30mins/1hr (assuming we are awake) so you won't have to wait long. Best, Okay, I'm convinced, I'm trying it again today. :) Posted by: Diego at February 2, 2005 9:38 AMPost a comment
Copyright © Diego Doval 2002-2007.
|