Since Sysdeo doesn't let me debug JSP, I subscribed to MyEclipse which, at $31 a year, seems like a good deal considering the range of features it offers. What I didn't like was that MyEclipse tries to be too smart, too helpful, and makes too many assumptions about how MyEclipse would be used. MyEclipse assumes it's users are J2EE developers and it's features are arranged to support that. In my case, I just want to debug JSPs in existing projects. But when I tried to add WebProject capability to my webapps, it wouldn't let me because the root of my project is the web root directory instead of using a subdirectory as WebRoot.
MyEclipse also disables features until certain conditions are met. Since the conditions are not visible, figuring out how to enable the feature ends up being a game of hide and seek. For example, Struts capability is grayed out until WebProject capability is enabled. While this makes sense logically, it's being unnecessarily helpful since addition of Struts capability doesn't actually depend on anything to be added.
Anyway, I am going to create a blank WebProject and figure out what the WebProject wizard does so I can manually convert my projects.
I am giving up on MyEclipse for now. They said they will looking into supporting projectroot==webroot in the future so I'll try MyEclipse again when that happens. Meanwhile I wasted $31. Oh, well. Its a nice bundle of functionalities though. I particularly like the Struts flow modeler although I suspect it is a good way to mess things up pretty badly with a few errant drag and drop.
I did try changing the layout to the way MyEclipse likes it but still found lots of little annoying overly helpful 'features' and hastily/half implemented features. It's a nice looking half-finished cruise boat in motion IMHO. Now I am hoping Sysdeo 3.0 final will have JSP debugging fixed.