Tapestry for Nonbelievers
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
- Java,
Tracking change and innovation in the enterprise software development community
Posted by Scott Delap on Jul 31, 2006 04:34 AM
The RIFE Java web framework has released version 1.5. RIFE is a full-stack web application framework with tools and APIs to implement most common web features. Each of its toolkits is usable by itself or together as a full application stack. The RIFE framework promotes itself as having many key differentiators versus other Java web frameworks including:
Highlights in version 1.5 include:
InfoQ recently caught up with Geert Bevin, RIFE project lead, to ask him about this latest release.
The Java web framework space is very crowded with project such as Struts, Spring MVC, Tapestry, etc. Geert commented on RIFE compared to other frameworks:
RIFE is pretty unique in the Java landscape in that it has a solution for every major layer in the stack without introducing any dependencies. The fact that the layers have been designed with interoperability in mind makes it possible to dramatically reduce boiler-plate code and offer unique meta-programming features. You are however still able to use any other Java library for each layer, it will just be less integrated and the features will differ.
Specifically in regards to SEAM and the Web Beans JSR:
I don't know the details of what their exact advantages are, but it seems to me that they externalize flow handling as a BPM solution with an accent on orchestration and long-lived flows. RIFE takes quite an opposite approach, native Java continuations allow a developer to leverage the power of Java without having to learn anything new. You can look at this as implicit and internalized flow support. We however also support externalized flows through data links and flow links in RIFE's site structure. These are designed to make it as easy as possible to create RESTful applications, while still relying on continuations-like state handling and program execution (similar to Spring Web Flow). Again however, the external flow is driven through Java inside your controllers instead of through an externalized flow scripting language. Also, Seam builds on top of JSF. For any functionalities that are not part of Seam, you need to learn and rely on JSF. The JSF programming model doesn't seem to be suitable for many people since they focus more on toolability than on developer comfort. The latter is one of RIFE's main focusses throughout the entire stack.
One of RIFE's key features it is its support of continuations. Geert explained how this works in respect to RIFE:
Continuations allow you to leverage the Java language to write your web application flow. You can literally write a user-interactive program in a similar fashion as when writing DOS programs years ago. Whenever you need input, you just request it and the execution will pause. When the user submits data, you'll receive it and your program will continue exactly where it left off, having preserved it's local state. All this happens over the HTTP barrier and works seamlessly with the browser back button.
When asked about the usage sweet spot for RIFE, Geert responded that in his opinion the full stack nature of RIFE provides "90% of what all the others deliver with 10% of the effort". RIFE revisits numerous concepts redesigning them with web application development in mind adding features such as "...continuations, run-time POJO-driven CRUD generation, scalable component-oriented architecture, state handling without sessions, etc". Geert sees RIFE as well suited for public web sites that are developed by a team of people who want to deliver quickly.
RESTful todo list sample tutorial with Groovy & Project Zero
Info 2.0: IBM's vision for the world of Web 2.0 and enterprise mashups (Webcast)
IBM Web 2.0 Developer eKit: Free Tutorials, Webcasts, Whitepapers
Thanks for having posted our release announcement and my interview here. For those that are interested in reading about recent user testimonials, some were posted at the release announcement at TheServerSide
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.
Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.
Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.
Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.
David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.
Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.
In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.
1 comment
Reply