both reasons are very valid!
regards,
Martin
On 9/21/06, Michael Youngstrom <[EMAIL PROTECTED]> wrote:
> Seems like we should be discussing this on dev rather than in the issue
tracker. Few people are going to be following the issue.
Done
>
> In my opinion, I don't see why you wouldn't use
>
> <h:panelGroup rendered="#{myfacesContext.ifMessage['someForm:name']}">
>
> That's far less limiting that having to set something with a taghandler.
>
Some of the problems I see right off the bat with having to put the
entire client id into the ifMessage expression are:
1. If these elements or this form is included in multiple places with
different base client ids it would cause some problems.
2. How would something like that work with input components placed
inside a UIData?
Mike
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
