On Tue, 15 Mar 2005 13:43:08 +0100, Matthias Wessendorf [snip]
> Fine! Working together should be the best JSF user could get, > independent from which Impl of JSF Spec they might use. > Absolutely. > It is very important, that Shale works with MyFaces > (it does, I am "playing" with both during learning Shale ;)) > Shale tries to make zero non-spec assumptions about the underlying implementation, so working with both MyFaces and the RI will keep me honest too :-). > Also MyFaces' extra components should work with Shale; > haven't looked at the remote thing in Shale. "Only" looked > in "ViewController" and I am fascinated about that! But > session scoped "DialogController" seams also to be very usefull. Word of caution -- DialogController is likely to be undergoing some revisions. > > As you also pointed out, that we are discussing the subproject > issue, does it make sense for you, to host Shale at MyFaces? If the scope of MyFaces had been "We want to create a JSF spec-compliant implementation, *and* we want to build other things that depend on JSF" it might be a good fit. Since the scope actually seems to be "We want to create a JSF spec-compliant implementation, and oh by the way here are some cool components" that wasn't as good a fit as Struts, where the mission is to create a web app framework. For now, Shale got accepted as a Struts sub-project. Whether it stays there, or migrates here, or graduates to its own status in the future -- that's going to depend on what actually happens. In the mean time, we can work together on value adds, and figure out how to share as we go. > > Shale should be build on top of JSF API, like our components. > Yep. > Since Shale is a framework that tries to leverages JSF, > I see some "overlap" in MyFaces' custom components and Shale (and its > components). Also both "teams" will have some util classes, that do the > same stuff for providing helper methods, independent from a specific > implementation. > > see: http://tinyurl.com/4zhd7 > Although, as I remarked in reponse to this particular post, I'm tired of getting burned by implementing static helper classes :-). But your point is well taken. Where does one create components that have Shale dependencies, for example? > or the mentioned "client side validation" or "file upload component" > for instance. It's going to be interesting to work these things out. > > -Matthias > Craig
