“The Eclipse Foundation will make the Eclipse Web Tools Platform 1.0 release generally available the week of Dec 19th, 2005. Eclipse WTP 1.0 is an extensible, standards-based tool platform for developing J2EE and Web applications. This full version release solidifies the platform API for 3rd party extension, and accompanying major documentation improvements make WTP ready for the next-level of vendor adoption.”
“The planned release date for WTP 1.0 is 2005-12-23. In the absence of any late-breaking severe problems, this release will be identical to RC5 which you can download now.”
So this is only *hopefully* v1.0 not definite yet …
I’ve seen a few other news sites post this under similar headlines. The article they’re quoting from clearly says in the first sentence that it hasn’t been released yet, but sites keep linking to it claiming that it has been.
The funny thing about the Eclipse community is watching them thrash on shipdates while the folks over at Netbeans.org get their act in gear (from having fallen behind). Matisse is very cool, and the J2ME support is outstanding. WTP will be good, but they’ve got more competition than they’d like.
Your IP is a DSL address out of San Jose. Sure you don’t work for Sun…maybe on the NetBeans team? Just checkin’.
Service implementation in Eclipse/WST has serious problem: You cannot change Service parameters once you created it. I tried both cases:
Top-down model (first create wsdl interface and then generate WS project from there). Subsequent changes of wsdl only produced errors, classes were not re-generated.
Bottom-up model (first create WS functions and then generate WS project from that). Subsequent changes of function parameters again created broken project, classes were not re-generated.
Am I missing something? If not, this plugin will hardly impress any serious developer. You never create ideal service with ideal parameters in a first attempt.
I’ve been using all of the release candidates and have finally just quit after using RC5.
WTP has become so slow that it’s entirely unusable. For example. If you’ve got validation turned on and you automatically compile when you save…it can take several seconds before you regain control of eclipse. If you then publish to tomcat…on a very new, very powerful PC, you can wait 10-15 seconds before it publishes and reloads the Tomcat application context.
Eclipse is a great tool if you don’t need anything specific…but when you stack it up against Netbeans 5.0..there’s just no comparison.
NB 5.0 has Matisse…a fantastic new layout manager for Swing…building rich-client apps couldn’t be easier…and it’s fast!! Eclipse has the Visual Editor. It is insanely slow…buggy…and worthless in its current form. NB has fantastic support for J2EE “out-of-the-box” and simply does what you expect an IDE to do – let you get down to work and not worry about constantly managing a project’s files and deployment.
I think Eclipse has a long way to go before it can compete w/ Netbeans 4.1/5.0…and 5.0 is due to ship a final release by the end of January! However, I’m using a nightly build that is quite stable & fast…a few small problems here and there but much better than expected!
I think people need to be clear. Netbeans has great support for EJB. I have found that, even the 5.0 release, has very limited support for J2EE in general.
That being said, I like Eclipse because I can use all the open source lightweight J2EE components (thing: hibernate, spring, axis, tapestry, hivemind). MyEclipse is great for all that stuff.
So…yeah…
I’m a long time programmer, using Java among others. I’m farily new to J2EE and the big open source IDEs.
I’ve been playing extensively with both NetBeans and Eclipse recently, being a complete noob to both, and not having any preconceived notions about either, other than the fact that Eclipse has become so popular.
My experience with the two has been like night (Eclipse) and day (NetBeans).
Eclipse has been pretty good for basic Java stuff and SWT stuff – the plugins for both are already installed and preconfigured. However, for visual editing and web stuff and EJB stuff, Eclipse is a nightmare. I’ve downloaded all the plugins (including the WTP and the visual editor), and while it’s not too hard to get a very basic project structure built, it never runs and is never debuggable. I’ve followed several tutorials to the letter, and always ran into a snag, which caused futile Google searches, and coutless wasted hours trying to get it to work. Another friend of mine, an experience J2EE developer, who’s used JBuilder and JDeveloper successfully, ran into the same problems. I also found the Eclipse interface/environment to be cluttered with too many options. And I did not like the perspectives feature. Also, I found documentation for Eclipse to be very limited and incomplete. It has a lot on developing plugins, which is great if you’re making Eclipse plugins. But it’s not great if you simply want an IDE to do your Java and/or J2EE app.
NetBeans, by contrast, has been a pure pleasure to use. Everything works, works well, and works very very intuitively and easily. All tutorials end up in success. The visual editor is a dream. Doing web apps (with servlets and jsps and javabeans) is a breeze. Enterprise apps, with EJBs and a Web Tier is surprisingly simple. The documentation that ships with NetBeans is awesome and complete and easy to understand. NetBeans also looks great, it’s fast for a big Swing app, and presents an easy, intuitive, and non cluttered interface.
So being new to both NetBeans and Eclipse, and not having any bias’ or preconceived notions, I’d have to say that NetBeans is nothing less than totally spectacular, and that Eclipse is a complete nightmarish mess.
Thus, based on my (limited) experience, I really hope NetBeans garners some more mindsare. It’s eons ahead of Eclipse.
Spend 8 hrs. w/ both Netbeans and Eclipse and you’ll realize…any basic (sane) end-user would have to agree. Then again, there are those folks out there who like to inflict pain on themselves.
If you start with bare Eclipse or the WTP, you are in for a painful experience, but most people normally use MyEclipse or another commercial plugin for J2EE, and that is a different league.
On the other hand MyEclipse is 30$ per year while Netbeans is free.
But Netbeans is not without faults either, JSF support is rather basic, and while JSC which now is free has a very good JSF support, its generated code routes into com.sun left and right and MyFaces support is not that well either.
But I agree Netbeans has caught up tremendously lately and I am seriously considering it again for development, but for now MyEclipse does more for me than Netbeans has to offer (yet)
I like Eclipse, it works very well for me, but I don’t do J2EE stuff.
I have checked out IntelliJ IDEA and NetBeans, but I didn’t go too far testing them. I couldn’t stand the fonts (Swing’s?) used by these IDEs. Eclipse on Windows using ClearType looks much better:
NetBeans:
http://www.netbeans.org/images/screenshots/5.0/errorstripe.png
Eclipse:
http://www.eclipse.org/screenshots/fullscreenXP/QuickFix.gif
I tried, but I went back to Eclipse. Call me shallow, but good fonts are very important when you look at text / source code all day.
BTW, I tried a beta versión of the JDK which has a better font rendering engine, but it still looks like crap 🙁