[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1855) Provide a FacesMessages.instance().addToControlById() or equivalent

[Moritz Winter (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12483718#action_12483718 ] 

Moritz Winter commented on JBSEAM-1855:
---------------------------------------

Don't you think the Priority of this should be set to a higher level? For us this is a showstopper because we can't show validation messages for one or more properties of mulitple instances of a class. Imho a very often used feature.

> Provide a FacesMessages.instance().addToControlById() or equivalent
> -------------------------------------------------------------------
>
>                 Key: JBSEAM-1855
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1855
>             Project: Seam
>          Issue Type: Feature Request
>          Components: JSF Integration
>    Affects Versions: 1.2.0.GA
>            Reporter: Andy Bosch
>            Priority: Minor
>             Fix For: The future
>
>         Attachments: FacesMessages patch.txt
>
>
> It is possible do add FacesMessages via the Seam functionality with FacesMessages.instance().addToControl. In the parameters you have to pass the component id. In the plain JSF way, you can add FacesMessages via FacesContext ... addMessage. In the JSF-way you have to pass the client-id.
> With normal input components you can use both ways. But when you work with datatables, you MUST work with the client-id, the Seam-way with using only the component-id does NOT work.
> Explanation: When using a datatable-tag, you only have one component. The renderer generates the various rows. In the component-tree there is yet only one component! If you want to add a FacesMessage to one row, you can only work with client-ids (because you have to include the row-index). 
> My wish: Please change FacesMessages.instance().addToControl. for using with client-ids.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira