-----BEGIN PGP SIGNED MESSAGE-----
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
I would say we will have to create a big warning with that information
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:
Is jstl still supported for Seam 2.3 since JSF 2 I think is only
supported in XHTML (actually I don't know that for sure, but going to check)
Programmer, Instructor, and Consultant
WFK and Seam Product Lead
Red Hat Czech s.r.o.
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----