struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Gary VanMatre)
Subject Re: [shale] framework questions
Date Thu, 15 Jun 2006 18:59:02 GMT
>From: "Craig McClanahan" <> 
> On 6/15/06, stephan opitz wrote: 
> > 
> > hello, 
> > 
> > shale has a lot of new features: 
> > 
> > View Controller: Backing bean for JSP with predefined events 
> > Validations: Client- and service-side validations 
> > JNDI: JSP access to properties in web.xml 
> > Dialog Manager: Web wizards (workflows) driven by XML configuration files 
> > Application Manager: An application-level controller to intercept all 
> > HTTP requests 
> > AJAX: A server-side service for AJAX support 
> > Spring, Tiles, and Clay framework integration and reusable views 
> > Test: Mock objects and base classes for JUnit-based tests 
> > 
> > 1. is the clay framework completely new developed? 
> Clay was pretty much an original effort, primarily developed by Gary 
> vanMatre, but you could also say it was inspired by the Facelets project at 
>, plus the way that Tapestry encourages users to develop pages with 
> static HTML and separate component definitions. 

Well, I think that Clay was posted in a bugzilla ticket before Facelets.

It wasn't until recently that we allowed multiple namespaces in the html 
templates like Facelets but the Clay Tapestry like views were David Geary's

The original thread ( 


> 2. is it possible to rebuilt the power of shale with existing 
> > frameworks (using the base jsf)? 
> Yes, but an important part of Shale's power (and simplicity) comes from the 
> fact that it presumes JSF is present, and uses JSF's controller 
> architecture. The typical approach to integrating JSF into existing 
> frameworks has been to use JSF's visual components, but not try to use its 
> controller. IMHO, this leaves you with a more complicated application 
> architecture, wth redundant implementations of basic features like 
> navigation, validation, and conversion. 
> On the other hand, you might also take a look at how Struts Action Framework 
> 2 (the upcoming work to merge in the WebWork framework and create a next 
> generation action oriented framework) attempts to meld the SAF/WW and JSF 
> controller capabilities together. Very powerful, but (for at least some use 
> cases), pretty complex. 
> stephan 
> Craig 
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message