[richfaces-issues] [JBoss JIRA] Resolved: (RF-7351) Regression: "messages: globalOnly does not work properly"
Andrey Markhel (JIRA)
jira-events at lists.jboss.org
Fri Jun 19 15:31:56 EDT 2009
[ https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Markhel resolved RF-7351.
--------------------------------
Resolution: Cannot Reproduce Bug
Assignee: Tsikhon Kuprevich (was: Andrey Markhel)
Not reproduced.
My code:
test.xhtml:
<h:form>
<rich:messages globalOnly="true">
</rich:messages>
<h:inputText id="my-control-id" required="true" value=""></h:inputText>
<rich:message for="my-control-id" id="my-control-id-message">
</rich:message>
<a4j:commandButton actionlistener="#{controller.generateErrors()}" value="Submit"/>
</h:form>
Controller.generateErrors(){
UIComponent root = FacesContext.getCurrentInstance().getViewRoot();
UIComponent component = root.findComponent("mainform:my-control-id");
FacesContext.getCurrentInstance().addMessage(component
.getClientId(FacesContext.getCurrentInstance()),new FacesMessage(FacesMessage.SEVERITY_ERROR, "input error", "input error"));
}
> Regression: "messages: globalOnly does not work properly"
> ---------------------------------------------------------
>
> Key: RF-7351
> URL: https://jira.jboss.org/jira/browse/RF-7351
> Project: RichFaces
> Issue Type: Bug
> Components: component, regression
> Affects Versions: 3.3.1
> Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA
> Reporter: Joseph Miller
> Assignee: Tsikhon Kuprevich
> Fix For: 3.3.2.CR1
>
> Time Spent: 4 hours
> Remaining Estimate: 0 minutes
>
> Looks like a regression of RF-615... I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page.
> My page template has:
> <rich:messages globalOnly="true" id="page-messages">
> ...
> </rich:messages>
> and the controls have:
> <rich:message for="my-control-id" id="my-control-id-message">
> ...
> </rich:message>
> I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :(
--
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
More information about the richfaces-issues
mailing list