-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Continuing on the same issue, it seems that the cause is not JSF2 design
mismatch with Seam2, but more likely a bug -
http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-787
and that bug aims to JSF 2.2 :-(
So workaround is to handle the restoring of PageContext content in Seam2.
On 03/22/2012 04:18 PM, Marek Novotny wrote:
Hi Seam devs,
I am fighting with the design mismatch between Seam 2 Conversation
init/restore and JSF2 new logic in Restore view.
The original issue
https://issues.jboss.org/browse/JBSEAM-4898 was
created as "Page scope components are not available in Postback
request". But as we have migrated Dvdstore example to JSF2/JPA 2, I see
that issue also as Conversation scope components are not available
(specifically outjected components) in case of long running and nested
conversations.
I have attached patch which is more than a fix a wicked hack, it
alongside changes jsf dependency from Optional to Required.
I would appreciate any help/advice.
Cheers,
--
Marek Novotny
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
- --
Marek Novotny
- --
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org/
iEYEARECAAYFAk9sfYwACgkQU4HO8G8hNxW40wCeIwEc1A7rsoBK/pujSjHYzCvF
W80AoORbdLuD96Na58JNXWXy062GMSYY
=Uc/j
-----END PGP SIGNATURE-----