Hi I sent the answer already over the mail
but just for history reasons
you have the use the full client id
of the component which is
<formid>:<viewid>:<suvbviewid>:<componentid>
you can use componentbindings to get it programmatically
component.getClientId(facesContext)
alternatively, but this is a bad method, you can look up the markup and
check which id has been generated, but if your nesting changes the ids
will change also every component within this nesting has to have an id set!
for convenience purposes you also can use forceId="true" on the tomahawk
components, they enforce an id, but also then you have to have one
single id with this name in the entire page.
Werner
[EMAIL PROTECTED] schrieb:
> I am using the following JSF code snippet:
>
> <f:view>
> ...
> <f:subview>
> <h:messages />
> ...
> </f:subview>
> ...
> </f:view>
>
> and in the backing bean I am adding an error message such as
>
> FacesContext.getCurrentInstance().addMessage("myClientId", new
> FacesMessage("error"));
>
>
> The error message is not showing up. I have tried all sorts of
> combinations of addMessage() and new FacesMessage() and attributes with
> <h:messages />, but nothing works. Any advice?
>
