Tss Translation: select a Java Web development framework for me

Tss: select a Java Web development framework for me.

Theserverside.com has been frequently discussed in the previous article. For the address, see chose a Web Client framework.

Chester Chen (cchen@ascentmedia.com) needs are simple:

Their company's basic environment is:
Development Environment: mix of Linux and Windows, Java, EJB (2 and 3 );
Deployment environment: Linux, glassfish for the new project (ui only), existing projects using WebLogic Server 10.3.

His expectation for the new framework is:
The learning curve should not be too steep. At the same time, it is mature enough to have good support for Ajax, so it is easy to develop and there are no strict restrictions on backend data models.

Currently, they are considering the following frameworks: wicket, seam, and struts2.

I think it took about five minutes for Chester Chen to write a post on the TSS homepage, which also attracted a long discussion.

Among these discussions, there are GWT pump owners, flex salesmen, and some people are still tired of the recommended: wicket and stripes (a simpler, lighter, cleaner version of struts 2 ), there are also zkoss, lift, and so on.

There are also very professional consultants, such as Anil kommareddi, which lists the following four points to consider:

1. Whether the development team is perfect. 2. technical information of the development team. 3. Framework developer community and support. 4. framework components.

While Daniil S is probably an angry youth. Let's look at his comments. Every one he looks at (probably switched from MS ):

I 've spent about 3 months looking for framework. The biggest issues
That came up were the learning curve, role of installation and
Simplicity. Some thoughts:
* Struts-skipped this one due to a lot of negative bias
Friends/developers. Everyone I know has some kind of an issue with it,
Installation or development hurdles.
* Tapestry-the learning curve was too great. Hard to find some simple
Example of a simple task such as login/logout. Too much restriction on
Correctness of HTML.
* Wicket-loved it, but installation process was a bit hard and
Required a lot of mizmizations on IDE part. html pages were in
Weird directories and our HTML guy got confused.
* Spring-learning curve is too steep.

Java developers generally have a deep understanding that more gains can be gained. Let's take a look at the luxury lineup of Pablo Krause:

Extjs: For a rich Internet application front end
DWR: Direct Web remoting, for communicating with Java backend.
Acegi: For security stuff (now part of spring)
Hibernate: for object relational mapping
Spring: For gluing it all together.

If you do not know about stripes (I do not know it now), read this article: stripes... and Java Web development is fun again.

Other resources:

Main Site: http://www.stripesframework.org
Quick Start: http://www.stripesbook.com/blog/index.php? /Archives/19-stripes-quickstart.html
Plug-in: http://www.stripes-stuff.org
Mail List: http://news.gmane.org/gmane.comp.java.stripes.user

Before you get dazzled, end with Web frameworks of the future: Flex, GWT, grails and rails.

(This article was translated very early (I don't seem to be a translator). I posted it today. The new csdn editor is not easy .)