Return-Path: Delivered-To: apmail-struts-dev-archive@www.apache.org Received: (qmail 71858 invoked from network); 15 Jun 2006 18:12:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2006 18:12:52 -0000 Received: (qmail 81324 invoked by uid 500); 15 Jun 2006 18:12:48 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 81292 invoked by uid 500); 15 Jun 2006 18:12:48 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 81281 invoked by uid 99); 15 Jun 2006 18:12:48 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 11:12:48 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of craigmcc@gmail.com designates 64.233.182.188 as permitted sender) Received: from [64.233.182.188] (HELO nf-out-0910.google.com) (64.233.182.188) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 11:12:47 -0700 Received: by nf-out-0910.google.com with SMTP id l35so288593nfa for ; Thu, 15 Jun 2006 11:12:26 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=G1eLhrb/YCuZJ/nDhfHUtKSiRAPvOmRrj2U3V34yuqHNP7BabUE7wTj1QgUTbqhwvXyhE5SgCmqI7KJq3FF0oDA10YO6YBiXabQCRfBB2U6x9YFlPGUzeHpxYC6K+IIEgTxsgZ/0uHE6mcgjF45aBKvT+xxqn0T29ZzxQtfjirY= Received: by 10.49.19.14 with SMTP id w14mr1635545nfi; Thu, 15 Jun 2006 11:12:26 -0700 (PDT) Received: by 10.49.32.15 with HTTP; Thu, 15 Jun 2006 11:12:26 -0700 (PDT) Message-ID: Date: Thu, 15 Jun 2006 11:12:26 -0700 From: "Craig McClanahan" Sender: craigmcc@gmail.com To: "Struts Developers List" Subject: Re: [shale] framework questions In-Reply-To: <975473fa0606150401m7ce340e4h18badc8f6f4dbd0f@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11872_29107411.1150395146434" References: <975473fa0606150401m7ce340e4h18badc8f6f4dbd0f@mail.gmail.com> X-Google-Sender-Auth: 94ccdf91052704f3 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_11872_29107411.1150395146434 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 java.net, plus the way that Tapestry encourages users to develop pages with static HTML and separate component definitions. 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 ------=_Part_11872_29107411.1150395146434--