[richfaces-issues] [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"

[Lukáš Fryč (JIRA)]

    [ https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612839#comment-12612839 ] 

Lukáš Fryč commented on RF-7351:
--------------------------------

Hi Mano, the sample you have attached can't be simply built and contains Spring dependencies in web.xml.

Could you please try to minimize to a form of valid maven sample (and do not include external dependencies) so it would be simple to reproduce issue for us?

Basically these external dependencies can influence behavior and may be reason that we are not able to reproduce it.

> 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, 4.0.0.Final
>         Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA
>            Reporter: Joseph Miller
>            Assignee: Ján Jamrich
>             Fix For: 4.1.0.Final
>
>         Attachments: example-globalOnly-bug.zip, example-globalOnly-bug.zip, Screen shot 2011-04-22 at 16.22.11.png, Screen shot 2011-04-27 at 08.51.26.png, Screen shot 2011-04-27 at 08.52.49.png
>
>          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