> Why did the commons-validator support go directly into > the Shale Core rather into MyFaces Extensions? There > are a couple of nice non-JSF-core Validators in the > MyFaces extensions, but the Shale commons-validator > support appears to be more flexible and more useful to > those who still have to work with both Struts and JSF > apps (and don't have the luxury of using Shale yet).
Shale and MyFaces are two entirely different projects started by two entirely different groups of people. The only thing they have in common in JSF. Most of us MyFaces people have used Struts for a long time now so we all know each other from the Strus mailing lists but they are two different projects. Craig can speak best as to why he is doing what he is doing with Shale. If you like the commons validator stuff for JSF then you are going to have to end up using Shale. One thing I can say for 100% sure is that there is no point in MyFaces adding something that is already available in Shale. MyFaces is really two things: #1) Its an open source JSF implementation (awaiting formal certification) #2) Its a set of components and other goodies for JSF Shale seems to be two things: #1) A pluggable controller adding enhanced lifecycle methods and other controller functionality to JSF #2) Some components and other goodies (ex. commons validator and <s:token>) There's more to Shale then that but its best to let the Shale team describe their own project There is some potential overlap in item #2 of both projects. Certain things like commons validator might very well have gone into MyFaces (had the MyFaces team taken the lead and done the work) but the Shale guys got to it first. Both projects are new and are finding their feet right now. JSF itself is just really emerging. Over time the two teams will naturally communicate more and users will find themselves using both technologies (MyFaces + Shale) interchangeably (IMO.) This should lead to more cooperation and planning between the two project teams to avoid duplication of effort. Down the line, I can see the advantage of the two projects merging or parts of one project joining the other. This subject came up a while ago and we've agreed that its not pratical to discuss this at the moment. > Can we expect to see an equivalent flexible > commons-validator in the MyFaces project/extensions > lib anytime soon? No (see above.) > For those using straight-JSF for the time-being, it > would be much nicer to be able to pull in a simple > extension JAR that includes the validator than to pull > in all of Shale Core or to have to convince their mgmt > that including a sample from a book verbatim in an app > is ok (mgmt tends to be comfortable with apache sw > these days, but not necessarily book samples > maintaining the book's package names and > copyright...). Shale is new techonology but then again so is MyFaces and JSF for that matter. Shale is Apache software just like MyFaces so you have the Apache "name" backing both of them. Maybe you could remind "management" that Shale is being developed by the person who created Struts and one of the lead designers of JSF. If a book with the name Shale on it will make them feel better, then ask David Geary (I hear he is working on one.) sean
