-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That is good point to think about. I have looked at the known issues and generally it is not designed to be optimized and integrated technology as it has got different process flow from JSF2. I found this short and nice recommendation in a nutshell: Use JSTL to control flow of JSF result. Use JSF to control flow of HTML result. Do not bind attributes of view scoped beans to JSTL tag attributes, or you must turn partial state saving off. One additional thing is that JSTL namespace has changed from xmlns:c=”http://java.sun.com/jstl/core” to xmlns:c=”http://java.sun.com/jsp/jstl/core” I would say we will have to create a big warning with that information in documentation. P.S. Adding also seam-dev mailing list, some JSF2 expert can add some important point too ;-) On 02/05/2012 04:38 AM, Daniel Hinojosa wrote: - -- Marek Novotny - -- WFK and Seam Product Lead Red Hat Czech s.r.o. Purkynova 99 612 45 Brno