[
http://issues.apache.org/jira/browse/MYFACES-1197?page=comments#action_12373037
]
Mike Youngstrom commented on MYFACES-1197:
------------------------------------------
>Mike Y: that is a tough problem: you don't have the current UIComponent to
>find from - which is unfortunate. If the target UIComponent had a "binding"
>associated, then life would be simple:
>
> <h:inputText binding="#{bean.someComponent}"/>
> <h:outputText rendered="#{myFaces.messagePresent[bean.someComponent]}"/>
That's exactly the only solution that I could come up with too. It gets really
messy when you have large forms with many input components.
There have been several cases where designers have layed out a form and
specified how error messages are to displayed and it turns out that by adding
the error message support html messes up the format of the form. So this was
really built as a way to help remove excess error message markup for a
component or small group of components.
Anyway, I think it is a fine solution that has its place and, gets the job
done, and doesn't muddle up backing beans with binding variables. So what do
you think Adam? Is it an acceptable solution? :)
Mike
> Docs for ifMessage component
> ----------------------------
>
> Key: MYFACES-1197
> URL: http://issues.apache.org/jira/browse/MYFACES-1197
> Project: MyFaces Core
> Type: Improvement
> Components: General
> Versions: 1.1.2-SNAPSHOT
> Reporter: Mike Youngstrom
> Attachments: ifMessageDocs.patch
>
> Here is a patch with docs for the ifMessage component I donated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
