Websphere is our corporate standard -- as is WSAD.

I've been very happy with eclipse/myeclipse combo.

Anybody have a comparison between WSAD and eclipse/myeclipse? Other than one is $30 and one is $2000.

Lee

Lee,

I think if you do an apples-to-apples comparison on features, you'll find that WSAD has a very substantial advantage. Its feature set is truly immense, as are its runtime requirements and price. ;-) The feedback we've received from several of our enterprise customers that are WSAD shops is that most of their users don't use 80% of the features in WSAD anyway, so why pay for them. What I'd encourage you to do as a WSAD user is to see what features you use regularly and then see if there is a similar capability in MyEclipse as this will give you a better idea if the different feature sets really matter for the way you use the tools. For example, while I may have Microsoft Word installed on my machine, I use about 3 font sizes and three fonts for 99% of everything I do. So, I figured out that Open Office worked great for me, even though it doesn't have the exact same feature set. :-)

If I used WSAD, I might be able to do that :) We have a new project team and WSAD is the corporate standard, but the company doesn't pay for the liscenses. Ergo -- the attractiveness of eclipse/Myeclipse. I just was looking for some kind of "what we won't get if we go with myEclipse".

I fully understand the bloatware concept. I just need something to communicate to my managers who make the purchasing decisions.

Lee

Lee,
Is this helpful: http://www.myeclipseide.com/ContentExpress-display-ceid-15.html, so its atleast something for them to go from?

Yes, that helps -- just need to have the "list o' features" for WSAD, such that a "what we get for a mere $1970 more" list could be derived :)

If no one has done this, I can understand -- was just asking.

Lee

Can you see WSAD and MyEclipse coexisting? As WSAD is also built on Eclipse -- I wonder if we could use both at the same time.

FYI -- hare are some WSAD features that would probably appeal to our team that are not currently in MyEclipse:

1. Collaborate and share assets across the team using the included IBM Rational ClearCase LT version control.
2. Manage complex code using the Unified Modeling Language (UML) Visual Editor for Java and EJB to graphically visualize and edit J2EE code with standard UML diagrams.
3. Detect performance issues early with graphical performance profiling and trace tools.
4. Streamline application testing with visual debuggers and built-in unit test environments for IBM WebSphere Application Server, WebSphere Portal and Apache Tomcat.

WSAD featrues found: http://www-306.ibm.com/software/awdtools/studioappdev/

Lee

Lee,

If you're principally a WebSphere shop, and it appears you are, then WSAD's feature set really can't be beaten. To your points:
1) You can get this by downloaded the Eclipse plugin for clearcase from Rational. It's available separately.
2) Editing code off of diagrams is quite an advanced feature. The question then becomes do all your developers work this way, or just a small subset of them? If it's all, then you really need WSAD.
3) At present, we don't include perf and trace tools, but we'll be looking at adding them in the future. There is a set already available for Eclipse separately as part of the Hyades project. I believe WSAD's capabilities are an extension to these base features.
4) For using WebSphere almost exclusively, WSAD is it if you can afford it.

Quote:

Can you see WSAD and MyEclipse coexisting?

Yes, at least as far as web projects are concerned as our project structure is very similar. However, for EJB and EAR projects they differ quite a bit so you really have to choose which tool you'll use at this point. Going forward, full interoperability on the project structure is one of the things we're pushing through our involvement in the Eclipse board and web tools projects.

From your post, it sounds like you might have some developers that really require some of the advanced features that WSAD offers and perhaps others that principally use Tomcat that might not.