|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
Web tier: servlets, JSP, Web frameworks
Web tier: servlets, JSP, Web frameworks
Web tier: servlets, JSP, Web frameworks
|
Messages: 1
Messages: 1
Messages: 1
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
What is a suitable web framework?
Hi,
I am planning to build an online web application that will be hosted using a 3rd party cloud service provider.
At this stage I am deciding on which Java web framework to use to build this application. I know that there a lot of popular java based web frameworks out there such as Spring, Struts 2, Stripes, Wicket, Tapestry, etc...
I am considering various factors such as
a) Learning curve and the amount of code to write
b) Books and learning material on the subject
c) Scalability
d) Size of the community
e) ORM facility
f) AJAX support
I would appreciate any advise or links that you can provide.
Thanks
|
|
|
Message #327478
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: What is a suitable web framework?
It is easy to give recommendations on Framework to use for projects. It would however be based on individual experience and bias. Furthermore you must recognize that there is no framework that could satisfy all needs.
For instance if you want a lot of client side validations and scripting; this could be for many reasons, including removing some activities from the server to the client. You would simply find out that some component based architectures are not client scripting friendly.
If your application is page oriented, with user interaction events and post back, you would discover that this requires a lot of work on request/response or non-component based platform. Whereas, this is the main stay of the component based frameworks.
One perspective that would serve you well is the concentration on what business solution you are trying to build first, and then worry about the framework that could deliver this solution.
One way available to achieve this, is by capturing the specification with dWebSpec. Once the requirement is captured, you could then evaluate how it translates to various platforms using the dictionary.
Some of the criteria that you already set could easily be discerned through this process.
Learning Curve and Amount of Code to Write
By flipping through the dictionary you could verify the implementation for the various platforms. Verifying the ease of implementation, and whether there are in-built facilities for items in your specification, or whether simple or extensive custom code would be needed.
AJAX
The support for AJAX could also be verified, either the retrieval of JASON, XML, etc data, or simple partial page refresh.
There is no doubt that making a commitment on which framework to invest in is not easy. Furthermore, making subsequent changes could be expensive.
However, utilizing the specification and definition of the problem domain would buy insurance for the success of this process. First, you have the benefit of platform independent specification. Then is the concrete means of platform evaluation.
|
|
|
|
Hot threads
Hot threads
Hot threads
|
More hot threads
More hot threads
More hot threads
|
|
Brian Goetz continues to lift the lid and peak into the inner workings of Java in Java Urban Performance Legends. In this article he exposes the fallacy behind some of the more common performance myths found in the annals of the JVM.
(93 comments,
last posted
February 06, 2009)
Bruce Tate, author of Better, Faster Lighter Java and Bitter EJB has come out with a new book called Beyond Java. Bruce has an epiphany about the future of software development. Does it include Java?
(770 comments,
last posted
September 23, 2009)
Looks like today AJAX concept have several interpretations. We can distinguish different approaches of AJAX integration. Can they co-exist within the same application? Can we talk about layered AJAX integration?
(68 comments,
last posted
May 08, 2008)
Artima has published a short article describing the Design-Time API for JavaBeans, which was recently approved as JSR 273. This API promises to bring VB-like ease to Java development, but may face a cultural bias among Java developers who tend to think more in terms of class libraries than components.
(225 comments,
last posted
November 19, 2009)
There is plenty of speculation today regarding a potential buyout of Sun Microsystems by Scott McNealy and Silver Lake Partners. How would privatization of Sun affect Java?
(16 comments,
last posted
May 15, 2009)
More hot threads »
|
|
