[
https://issues.apache.org/jira/browse/MYFACES-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903805#action_12903805
]
Werner Punz commented on MYFACES-2895:
--------------------------------------
Sure, I did not say we should not fix it, and yes rendering a placeholder like
a span with the correct id fixes the problem, we even can set it to
display:none so that it does not destroy any layout.
Btw. this problem does not only apply to h:messages but also to h:message
fields!!!
The main problem with the spec as I see it is that it defines what has to be
rendered for the standard components, hence I said this is a spec issue as well.
It might be that by rendering additional code we might break the TCK.
But I guess others have more insight into the issue here :-)
> Messages component cannot be updated by ajax without wrapping it
> ----------------------------------------------------------------
>
> Key: MYFACES-2895
> URL: https://issues.apache.org/jira/browse/MYFACES-2895
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.2-SNAPSHOT
> Reporter: Nick Belaevski
>
> When there are no faces messages generated, h:messages component does not
> render no HTML tags, so it cannot be updated by ajax.
> To reproduce:
> <h:messages id="messages" />
> <h:commandButton value="Invoke listener by
> type" action="#{bean.generateMessage}">
> <f:ajax render="messages" />
> </h:commandButton>
> No messages will appear. As a workaround messages component can be wrapped
> into h:panelGroup that's id will be specified in 'render':
> <h:panelGroup id="messages">
> <h:messages />
> </h:panelGroup>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
