Geek Answers Handbook

Eclipse vs Netbeans Web Service Tooling

Some time ago (~ 4-5 months ago) I lectured on Java EE, and at some point, the lecturer started talking about web services and how difficult it is to create a good one, because all IDEs make them a little different (or something like that), and it’s generally better to use Netbeans to create them, since Eclipse has some problems, the fact is that it really didn’t say why Eclipse is bad. Now I wonder what he told the truth and why, is it really better to use Netbeans for web services and why?

+6
java eclipse web-services netbeans
source share
5 answers

We have an enterprise application using webservice (WS), and most of our colleagues use eclipse (I use Intellij, but this has nothing to do with WS).

In any case, we have no problems, and the reason is that we do not use the IDE for everything that is typical for WS. We use tools such as JBossWS, SOAP-UI, etc., to deal with what might be considered for specific WS tasks.

I believe this is the best approach; Use any third-party tools that are good and not depend on too many Eclipse / Netbeans features.

We also use maven to manage dependencies instead of the built-in eclipse, and that was a very good idea. We do not need eclipse to create the material, we can integrate the project without problems into the CI (Continuous Integration) server, and I can use my favorite Intellij IDE.

If we want to expel something, it is very convenient, because we do not need to worry about which plugins they use. Just say that this is a maven project, give them a source, and it's good for them to go.

To summarize, I suggest that you choose whatever IDE you want to use.

+5
source share

Well, if you want to create a client based on the completely obsolete Axis stack or use the not much better Axis 2, Eclipse helps a bit. But if you want to use JAX-WS and the advanced WSIT standards for reliable messaging, security, politics, etc., there is simply no competition. NetBeans has very good support (you understand that you have wizards), lots of tutorials , documentation , samples, etc., while Eclipse has nothing.

The problem is that Eclipse has been supporting and promoting Axis for too long (mainly for bad political reasons for IMO). Things could change in the future with Apache CXF support in Eclipse, but NetBeans is better at developing web services right now.

Make no mistake, I like Eclipse, but when it comes to developing JAX-WS web services, NetBeans is the right tool right now.

+6
source share

I write web services at work and used Axis2 / jaxws and Apache CXF (our defacto now) with eclipse. I do not use plugins or anything like that. Everything moves through ANT, and will soon become Maven. They have absolutely no problems, and also do not need to deal with all the bells and whistles, which is Netbeans.

+1
source share

It should be reiterated that the term “web services” does not have to be synonymous with SOAP and WSDL. You always have REST if you are ready to transfer the tools that the WS- * group sells. IDEs, tools, and wizards are much smaller if you take this approach.

I think this is part of the reason why the WS- * approach has gone as far as possible, despite the bloat: tool sellers love it.

0
source share

If you are using Oracle as the back end and JSF as the interface, go to OEPE. A great tool for integrating Glassfish and Eclipse.

0
source share

More articles:


All Articles