SDA India is an online resource for Software, Development,IT, Architecture, Open Source, Mobile, Security, Databases, Delphi, C, OS, Asp, .Net, Php, Xml, Java
From the News Desk
Monday, 27. August 2007
Users Quitting Eclipse
While a large section of developers are migrating to Eclipse and singing hosannas about its benefits, there are always a handful who are quitting Eclipse. Take the case of Wilhelm, who's so far been pleased with using Eclipe with Java projects and has been trying to use for Rails development, has decided to dump Eclipse because it occupies 140MB of his machine's 512MB of RAM. Further, he has switched to command line SVN and the bug in Rinari -- an emacs mode for Rails -- got fixed. "So the two reasons to stay with Eclipse is no longer around," says Wilhelm.
Another user, an Eclipse beginner, listed even more reasons to quit. Pai, a NetBeans 5.5/Sun Application Server user, found Eclipse Europa's WTP feature for Web Application development tempting enough to learn a new IDE along with learning the Spring framework. After configuring Eclipse Europa to work with the Sun Application server, he created a dynamic web project in Europa making it compatible for running in Sun App Server and made a Controller and a view page in JSP. Once the configuration files were made he ran the project only to see this error:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
After spending a couple hours trying to debug the application, he was still stuck with the error the the Logger was missing although he had not added it anywhere in his code. The solution was to add the appropriate JAR but Pai did not have any of them, such as Log4j. Next, he put learning Spring on hold, and use the JAX-WS with the Eclipse IDE. The user then found out that there was no provision for making a web service project in the IDE unless he set up the SOA Tools Platform (STP). The next thing he found out was that STP should be configured with Apache Celtix Fire although JDK 1.6 is shipped with JAX WS.
He tried to get by using the JWSDP 2.0 web services developer pack from SUN, instead of installing CXF, which did not work. So he downloaded CXF, configured it with Eclipse. The IBM tutorial said that once the interface with the annotations is saved, the proxies and WSDL would be created automatically. Try as he might Pai could not rid of this irregular behavior. The other grief he had was that Eclipse does not allow to switch between the servers; that is the Sun Application Server and Tomcat for running the same application. Finally, after spending one day trying to use the Eclipse IDE, Pai went back to using Spring with NetBeans.
Another user, an Eclipse beginner, listed even more reasons to quit. Pai, a NetBeans 5.5/Sun Application Server user, found Eclipse Europa's WTP feature for Web Application development tempting enough to learn a new IDE along with learning the Spring framework. After configuring Eclipse Europa to work with the Sun Application server, he created a dynamic web project in Europa making it compatible for running in Sun App Server and made a Controller and a view page in JSP. Once the configuration files were made he ran the project only to see this error:
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
After spending a couple hours trying to debug the application, he was still stuck with the error the the Logger was missing although he had not added it anywhere in his code. The solution was to add the appropriate JAR but Pai did not have any of them, such as Log4j. Next, he put learning Spring on hold, and use the JAX-WS with the Eclipse IDE. The user then found out that there was no provision for making a web service project in the IDE unless he set up the SOA Tools Platform (STP). The next thing he found out was that STP should be configured with Apache Celtix Fire although JDK 1.6 is shipped with JAX WS.
He tried to get by using the JWSDP 2.0 web services developer pack from SUN, instead of installing CXF, which did not work. So he downloaded CXF, configured it with Eclipse. The IBM tutorial said that once the interface with the annotations is saved, the proxies and WSDL would be created automatically. Try as he might Pai could not rid of this irregular behavior. The other grief he had was that Eclipse does not allow to switch between the servers; that is the Sun Application Server and Tomcat for running the same application. Finally, after spending one day trying to use the Eclipse IDE, Pai went back to using Spring with NetBeans.
Posted by: Jens E. on August 29, 2007
MyEclipse solves most of the above worries posted by developers. The difference, they will be quick to point out, is that MyEclipse is not "free" like Eclipse is. However, if the price of $30 for a year of fully configured servers and databases, Spring and AJAX technologies among others is not more valuable than a full day debugging environments and switching IDEs, I don't know what is.