Eclipse RCP Meets Spring: A Perfect Thick-Client Match
Eclipse Rich Client Platform (RCP) is fast becoming the framework of choice for building thick client applications. Get a step-by-step guide to leveraging Eclipse RCP with Spring.
by Stephen Lum
June 22, 2006
ven though Web 2.0 and rich Internet applications (RIAs) are all the rage these days, building a rich Web front end for your stakeholders is not the answer when thick-client functionality is what you really need. I stated as much in my previous article, "Building a Java App Server Foundation for Thick-Client Deployment," which showed how to leverage a traditional Java Web server architecture to easily deploy thick clients.
But if you indeed eschew the RIA craze and opt for a practical thick-client solution, where do you go from here? Answer: You choose a Rich Client Platform (RCP) that will handle much of the work for you. Essentially, the RCP concept brings a framework to the world of Java desktop applications. The J2EE/Java EE world has long had the luxury of frameworks on which to standardize its best practices (see Spring, Struts, WebWork, etc.). Now, the Java desktop world is benefiting from that experience.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ven though Web 2.0 and rich Internet applications (RIAs) are all the rage these days, building a rich Web front end for your stakeholders is not the answer when thick-client functionality is what you really need. I stated as much in my previous article, "
