Raible Revisits Comparing Web Frameworks

2 (hopefully constructive) comments:

- I seriously miss Ext.JS or [insert your new favourite javascript widget library here] plus DWR combo as a valid future approach
- that pink stuff is horror :)

Otherwise, thanks for your work!

I agree that doing a comparison of SOFEA/SOUI frameworks would be very cool. However, none of the widget library+data interchange library approaches offer an "Application Download" feature - so it may be difficult (at this time) to develop a true SOFEA application (as described in Life above the Service Tier) with them.

The "counted" link above should be to this blog:
www.jamesward.org/wordpress/2007/11/15/matt-rai...

-James

I’m a bit surprised that Spring Web Flow was not mentioned.

In my experience, SWF has never been advertised as a web framework - but rather as a optional solution for those applications that need page flows. Since it integrates with JSF, Spring MVC and Struts1/2 - it doesn't seem like it should stand on its own as a competitor.

WingS is one of the most complete and powerful MVC for Java.
wingsframework.org/cms/

It is missed.

WingS is one of the most complete and powerful MVC for Java.

I like how you provide no foundation for this statement. ;-)

Care to elaborate? In particular, please provide an example of where tried another web framework (Struts 1.x doesn't count) and then switched to WingS. Please include specific use cases on why it's better and why the other framework failed.

I would like to see ItsNat included in your list someday. I know ItsNat is the new kid on the block but someday... :)

Good presentation, good job.

I don't know if I would go so far to say "SWF has never been advertised as a web framework". Certainly, by its very definition Spring Web Flow is a Java web application controller framework.

However, Matt is correct in summarizing Spring Web Flow 1.0's overall position in the market. Spring Web Flow 1.0 is used today within existing web frameworks Spring MVC, Struts, and JSF for handling navigation and state management concerns, typically in web applications with non-trivial view navigation rules. In this capacity, flows run happily alongside "plain" controllers such as stateless MVC Controllers or Struts Actions, freeing you from HTTP Session state management concerns and nasty if/else logic to figure out where you are so you can determine where to go next.

I should add, however, even in this complementary capacity, I do know of organizations that use Spring Web Flow to power the control flow of entire applications, favoring externalized flow definition exclusively. Orbitz Worldwide, for example, uses SWF to power their stateless search/shop site functionality and their linear trip booking processes. They did this because they wanted one consistent way of defining control flow that could scale as their application grew in complexity, and felt the externalized flow definition language offered by Spring Web Flow met that requirement better than anything else they evaluated.

Spring Web Flow 2.0, the next major release of the framework, will formally evolve the project's positioning. There is a desire in our community to have a single MVC framework capable of handling both stateless and stateful control flow--the same desire Orbitz had. The Spring Web Flow runtime is being evolved to provide the ideal foundation for that unified MVC framework. In addition, JavaServerFaces is being integrated as another supported view technology via the Spring Faces project.

Now, this doesn't mean everyone developing Spring web applications will be going off and defining XML flow definitions in the future. The Spring Web Flow 2.0 engine will run Spring 2.5 @Controllers, externalized XML flow definitions, and Java-based @Flows, initially: all using the same runtime underneath (which means one central runtime to hook in security management, exception handling, persistence context management, monitoring, tooling, and other features) The basic idea is this: provide one unified, next-generation MVC runtime with several natural programming models for defining and engineering control flow - from stateless operations on REST resources to stateful conversations - with support for all major view technologies, including JSF. You can read more about this vision here.

Keith
SpringSource Principal
Lead, Spring Web Flow
www.springframework.org

Note also that there are major enhancements in Spring MVC (a very popular web framework) in the recently released Spring Framework 2.5. The most important enhancement is a new annotation-based controller programming model, which can greatly reduce the amount of configuration required, and minimizes the need to depend on concrete inheritance. The classpath scanning feature of Spring 2.5 means that controller classes annotated with @Controller can be automatically detected by Spring, meaning that no XML or other external configuration is required to specify request mappings or identify controllers. This builds on the new annotation-based configuration options that Spring 2.5 offers overall.

As Keith pointed out, the Spring Web Flow and MVC models are converging. Ultimately everything will run on a Web Flow-based runtime under the covers, but the Spring MVC @Controller model will be fully supported, providing a smooth upgrade path.

Actually, Grails uses SWF internally to provide conversations. It also gives a nice convention-based approach to using SWF.