Is JSF 2.0 going to favor REQUEST scope more than we currently see with 1.2? Colleagues and I find JSF to be quite geared towards SESSION scope and it causes a lot of issues in regard to life cycles, we almost always need to obtain values directly from the request rather than relying on setters - which has to be there though in a dummy fashion, in order to satisfy JSF. And how come there is no "EMBEDDED" scope, which would work much like SESSION scope but serialize (and encrypt) context out onto an inputHidden field and get deserialized again upon each REQUEST transparently? Anyway, just something we've been wondering about. //

1 Comments

  • 392 Guest Newbie

    392 Guest Oct 22, 2008 9:16 PM

    Is JSF 2.0 going to favor REQUEST scope more than we currently see with 1.2? Colleagues and I find JSF to be quite geared towards SESSION scope and it causes a lot of issues in regard to life cycles, we almost always need to obtain values directly from the request rather than relying on setters - which has to be there though in a dummy fashion, in order to satisfy JSF. And how come there is no "EMBEDDED" scope, which would work much like SESSION scope but serialize (and encrypt) context out onto an inputHidden field and get deserialized again upon each REQUEST transparently? Anyway, just something we've been wondering about. //