[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jan Jamrich commented on RF-7351:
---------------------------------
I have made some additional messages into Metamer
(
http://anonsvn.jboss.org/repos/richfaces/modules/tests/metamer/trunk/), but I'm still
not able simulate this.
I should try to create new RichFaces 4.x project (from archetype:
http://docs.jboss.org/richfaces/latest_4_0_X/Developer_Guide/en-US/html/c...),
but there are some important differences (such as in your web.xml you require servlet v3
while v2.5 is set in web.xml you get from archetype), so its quite difficult create
appropriate application to test your env.
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, example-globalOnly-bug.zip, Screen shot
2011-04-22 at 16.22.11.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