[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597619#comment-12597619
]
Mano Swerts commented on RF-7351:
---------------------------------
Hi Nick,
I created the minimalistic page I referred to in my previous comment. So I do
not use any styling, custom facelet components or template in this example.
I packed the files that I think you will need: the simple xhtml page, the
parent pom of the project, the web.xml file and the faces-config.xml file. I
attached the zip and a screenshot.
I also noticed on my simple page, that when I clicked submit, the component
error message appeared in the global messages for a second and then
disappeared. When the validation is executed on blur, it remains in the global
error messages. If I do both, the message appears 2 times in the global
messages.
I hope that this is enough information for you.
> Regression: "messages: globalOnly does not work properly"
> ---------------------------------------------------------
>
> Key: RF-7351
> URL: https://issues.jboss.org/browse/RF-7351
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> 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: Jan Jamrich
> Attachments: example-globalOnly-bug.zip
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
