I guess it makes sense, to make the merger a post JSF 2 project.
So all features, which are included in JSF 2 (e.g Remoting) should not move,
but just stay in Shale.
Also let's see where templating and component development goes before making
a decision about Clay.
So Shale is then the JSF 1.X add-on framework, when it comes to JSF 2 all
Add-Ons move to MyFaces.
Von: crai...@gmail.com [mailto:crai...@gmail.com]Im Auftrag
Gesendet: Montag, 22. Oktober 2007 01:48
An: MyFaces Development; Shale Developers List
Betreff: Re: Merging Shale into MyFaces
Unsure, as most of this can be done with PPR too.
+1 This is pretty useful and easy to use, and will affect JSF 2.0.
A secondary benefit is near-zero config for resource access,
particularly for resources provided in a jar file instead of as
exploded files in a WAR. Until JSF 2 comes along, that's pretty
useful all by itself.