is there a road map/milestone for Shale developemnt ? I am pretty comfortable with Struts now but would like to explore Shale in the next project.
thanks lixin On 8/18/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 8/17/05, Joe Germuska <[EMAIL PROTECTED]> wrote: > > At 11:49 AM +0100 8/17/05, John Atherton wrote: > > >Okay I've found the place to go for all things Shale but my other two > > >questions still stand. > > > > first, a disclaimer: I've never written a JSF app let alone a Shale app. > > > > > > Then I came across Shale. I've never used JSF so firstly, is this now > > > the > > >> way to go? > > > > Roughly, Shale is to JSF as Struts is to JSP: it provides a framework > > which supports best-practices application development with features > > that are outside of the scope of the basic Sun technology. > > > > "Roughly" that's pretty accurate :-), although there is one level of > internal difference that you will want to be aware of. JSF includes a > controller servlet (like Struts and other MVC frameworks), and > supports other controller features like navigation, itself. Shale > builds around the edges to add value (functionality and/or ease of use > improvements), without any attempt to redundantly implement features > that JSF provides by itself. > > One place I *don't* see Shale going, by the way, is to become yet > another library of JSF components. There will be a few such > components that integrate directly with Shale features (like the ones > that integrate the Commons Validator facilities), but the whole idea > of a standard component API is that you should be able to use > *anyone's* components with it. > > > If you're going to use JSF, you should probably check out Shale. > > I would agree with this ... especially for new app development. > > > You can use struts-faces to connect JSF to Struts, but if you have no > > deep Struts experience, you wouldn't be gaining much of anything, and > > in fact you'd lose all the benefits that Shale has by virtue of > > learning from several years of Struts development experience. > > > > The integration library should be primarily considered as a tool > useful in a migration strategy. > > > >Secondly, where can I find out more? And finally how steep is > > >> the learning curve? There doesn't appear to be the Shale equivalent of > > >> http://struts.apache.org > > > > Shale's website, by the way, is at: > > http://struts.apache.org/shale/ > > The feature descriptions have not all been fleshed out yet, but the > javadocs are pretty thorough for those cases. > > > I'm not sure what the second question was: about the learning curve? > > I'm not the one to answer that. But since Shale is a subproject of > > Struts, there is no "shale.apache.org" > > > > Since there has not been a full release of Shale, the struts-dev list > > is generally considered the more fruitful place for discussions about > > it. > > > > Hope this helps, > > Joe > > > > Craig > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
