JSF 2.0 has done nothing to change this AFAIK. There are several
problems with this. First off, the hidden field which stores the state
is spec'd to have an id and a name which is equivalent to a constant.
Although most browsers handle this for the purposes of submission,
having two items with the same id is invalid HTML. When PPRing
something, you need to replace this value in all locations is exists
and, if the ID's are the same, then accessing these elements through
javascript is not always possible. There are certainly some ways of
getting around this (for instance, using a consistent "token" based
state param and whatnot), but Trinidad hasn't implemented any of these
mechanisms.
Secondly, Trinidad's lightweight popup will 'move' elements around in
the dom structure. This mechanism does not have multiple for support
either.
Scott
On 10/04/2011 09:15 AM, Walter Mourão wrote:
Hi folks,
before JSF 2 there was some advice we should use only one<tr:form> and many
enclosed<tr:subform> for each submittable part of the view. When using JSF
2, should I continue following this advice or I can use many<tr:form> in
the same view ?
Thanks,
Walter Mourão
http://waltermourao.com.br
http://arcadian.com.br
http://oriens.com.br
