>From: Julián García <[EMAIL PROTECTED]>
>
> Hi,
>
> I am using Hibernate + Spring + Myfaces. It's been working but I think
> that I am writing a LOT of code in the view layer. I have a small custom
> validation framework of my own, and my own init mechanisms in my beans.
> I use tiles.
>
> I'd like to do more templating, and reuse some code out there....I was
> thinking of:
>
> Facelets: to do templating
> Shale: init mechanisms in beans, client-side validation, Spring integration
>
> Any experiencies you want to share combining or using separately this 2
> frameworks with MyFaces 1.1.1
>
> Do they have overlapping features? Would you use them both for production?
>
 
Facelets and Shale Clay do have overlap.  Both allow templating, and alternative to JSP.  Clay's HTML full view templating allows you to use old school html.  I believe that Facelets requires well formed XML.  Clay is also unique in that it provides metadata inheritance and symbol replacement overlapping with tiles generic layout features.  The Clay full XML veiws could compare to tiles.   Clay is based on a component so it can be use within JSP too. 
 
The key point is that you have to choose if you are using JSP, XML or HTML for view composition and it's not wise to try to switch between view technologies.  The Shale use case example does this with moderate success.  This has to do with how you define the entry point resource that defines the page.  Maybe this will change in JSF x.x.
 
I'm a bit bias on the Clay versus Facelets comparison but Shale and Facelets would be a good technology stack too.
 
I think that JSF and Spring have some overlap.  They both provide IoC.  So, if you wanted to reduce the layers in your stack you might go with Shale+Myfaces/Hibernate or iBatis.

> Thanks for your comments.
>
> Julian
 
Gary
 

Reply via email to