2:12 a.m.
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
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
5:55 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Nick Belaevski updated RF-7351:
-------------------------------
Fix Version/s: 3.3.2.CR1
Assignee: Andrey Markhel
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: Andrey Markhel
Fix For: 3.3.2.CR1
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
3:16 p.m.
New subject: [JBoss JIRA] Work logged: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Andrey Markhel logged work on RF-7351:
--------------------------------------
Author: Andrey Markhel
Created on: 19/Jun/09 03:15 PM
Start Date: 18/Jun/09 03:14 PM
Worklog Time Spent: 4 hours
Work Description: Done
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes
Time Spent: 4 hours
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: Andrey Markhel
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
3:31 p.m.
New subject: [JBoss JIRA] Resolved: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
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
12:38 a.m.
New subject: [JBoss JIRA] Reopened: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Joseph Miller reopened RF-7351:
-------------------------------
Hi,
I've reduced my application down to small size, demonstrating the problem:
http://joff.googlehax.com/MessagesExample.zip
You can trigger the behaviour by clicking in any of the input boxes on the page and then
clicking/tabbing out of them, triggering the validation messages.
Hope this is useful.. ?
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
9:45 a.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Nick Belaevski reassigned RF-7351:
----------------------------------
Assignee: Andrey Markhel (was: Tsikhon Kuprevich)
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: Andrey Markhel
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
10:04 a.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Tsikhon Kuprevich reassigned RF-7351:
-------------------------------------
Assignee: Inna Shchibrya (was: Andrey Markhel)
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: Inna Shchibrya
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
10:10 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Nick Belaevski commented on RF-7351:
------------------------------------
Demo app was downloaded to \\E******-PDC\projects\Richfaces
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: Inna Shchibrya
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
8:25 a.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Nick Belaevski reassigned RF-7351:
----------------------------------
Assignee: Alex Kolonitsky (was: Inna Shchibrya)
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: Alex Kolonitsky
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
8:31 a.m.
New subject: [JBoss JIRA] Work started: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Work on RF-7351 started by Alex Kolonitsky.
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: Alex Kolonitsky
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
11:41 a.m.
New subject: [JBoss JIRA] Resolved: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Alex Kolonitsky resolved RF-7351.
---------------------------------
Resolution: Done
Assignee: Tsikhon Kuprevich (was: Alex Kolonitsky)
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
6:23 a.m.
New subject: [JBoss JIRA] Closed: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://jira.jboss.org/jira/browse/RF-7351?page=com.atlassian.jira.plugin...
]
Alexander Dubovsky closed RF-7351.
----------------------------------
Assignee: Nick Belaevski (was: Tsikhon Kuprevich)
Verified
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: Nick Belaevski
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
2:58 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
This issue seems to remain in version 4 of Richfaces. Can this be verified?
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: Nick Belaevski
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:36 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski updated RF-7351:
-------------------------------
Fix Version/s: (was: 3.3.2.CR1)
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: Nick Belaevski
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
8:36 a.m.
New subject: [JBoss JIRA] Reopened: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski reopened RF-7351:
--------------------------------
Reopened due to user's request
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: Nick Belaevski
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
4:42 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
Is there additional any news on this?
Thanks.
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: Nick Belaevski
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
4:42 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts edited comment on RF-7351 at 4/11/11 4:42 AM:
----------------------------------------------------------
Is there any additional news on this?
Thanks.
was (Author: mano.swerts):
Is there additional any news on this?
Thanks.
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: Nick Belaevski
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
9:50 a.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas reassigned RF-7351:
-------------------------------
Assignee: Prabhat Jha (was: Nick Belaevski)
Prabhat - please verify if this is an issue in the 4.0, and if so update the affects
version.
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: Prabhat Jha
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
1:51 p.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Prabhat Jha reassigned RF-7351:
-------------------------------
Assignee: Jan Jamrich (was: Prabhat Jha)
Please see the comment above.
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
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
1:51 p.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Prabhat Jha commented on RF-7351:
---------------------------------
Jan Jamrich worked last week on adding rich:message to Metamer. He plans to finish it this
week so we should know if this is the case still.
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: Prabhat Jha
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
3:22 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
Hi guys,
Is there already any news on this issue?
Thanks.
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
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
7:44 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jan Jamrich commented on RF-7351:
---------------------------------
I have checked this issue with Metamer (v4.1.0-SNAPSHOT), and didn't get validation
messages for components in rich:messages component with globalOnly="true".
So, seems that this issue doesn't appear in current RichFaces.
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
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
6:45 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski commented on RF-7351:
------------------------------------
Mano,
What is RichFaces version you use: 3 or 4?
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
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
7:12 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
Jan, I will try to create a minimalistic page to test this further, but we are still
experiencing this problem.
Nick, we are using 4.0.0.Final through Maven.
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
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
7:14 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski commented on RF-7351:
------------------------------------
Mano,
Example that reproduces the issue will be very helpful!
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
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
10:22 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
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
10:22 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts updated RF-7351:
----------------------------
Attachment: example-globalOnly-bug.zip
Packed example as referred to in my comment.
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
10:31 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts edited comment on RF-7351 at 4/22/11 10:30 AM:
-----------------------------------------------------------
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 relevant snippet
from the parent pom of the project, the web.xml file and the faces-config.xml file. I also
attached the relevant pieces of the backing bean, services and domain classes. 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.
was (Author: mano.swerts):
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, 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
10:31 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts updated RF-7351:
----------------------------
Attachment: example-globalOnly-bug.zip
Updated version
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
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
10:33 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts edited comment on RF-7351 at 4/22/11 10:31 AM:
-----------------------------------------------------------
Updated version (I cannot seem to remove the old one)
was (Author: mano.swerts):
Updated version
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
10:33 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts updated RF-7351:
----------------------------
Attachment: Screen shot 2011-04-22 at 16.22.11.png
Screenshot packed example.
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
9:51 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
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
11:19 a.m.
New subject: [JBoss JIRA] Resolved: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Pavol Pitonak resolved RF-7351.
-------------------------------
Resolution: Cannot Reproduce Bug
We cannot reproduce the bug in our testing application Metamer. Please reopen if more
information is available.
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
1:50 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts updated RF-7351:
----------------------------
Attachment: Screen shot 2011-04-27 at 08.51.26.png
Screen shot 2011-04-27 at 08.52.49.png
Hi guys,
We investigated the issue further by debugging the RichFaces JavaScript code.
We noticed that both the <rich:messages globalOnly="true" /> component and
the <rich:message for="inputField" /> component bind to an
"onMessage" event.
When the event is triggered on tab, the "onMessage" function in
"message.js.faces" is triggered for both components.
As you can see in the attached screenshots the function is called twice: once for both
components. Other <rich:message /> components which have a "for" attribute
related to other fields are not triggered, just as expected.
In the JavaScript code, we can see that a check is performed on the availability of the
"forComponentId" attribute. If this attribute is available, a validation message
is rendered for the specified component id. If this is not available, a global message is
rendered.
But when a global message is rendered, we cannot see any check on the globalOnly
attribute. So any message is rendered, regardless of this attribute. The attribute is
nowhere to be found in the JavaScript code.
We were wondering if this is the bug or if there is an other piece of code that is
responsible for checking whether only global error messages may be displayed?
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, 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
5:59 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
Can anybody provide an answer to my previous comment or reopen this issue for me please?
Thanks.
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, 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
6:37 a.m.
New subject: [JBoss JIRA] Reopened: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Pavol Pitonak reopened RF-7351:
-------------------------------
Assignee: Lukáš Fryč (was: Jan Jamrich)
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: Lukáš Fryč
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
6:52 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč commented on RF-7351:
--------------------------------
Hi Mano, thanks for your points, I will investigate it closely.
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: Lukáš Fryč
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
10:32 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Fix Version/s: 4.1.0.Milestone1
Affects Version/s: 4.0.0.Final
We will investigate and resolve this as part of 4.1 development. Thanks a lot for the
time and effort on this issue.
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: Lukáš Fryč
Fix For: 4.1.0.Milestone1
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
4:40 a.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč reassigned RF-7351:
------------------------------
Assignee: (was: Lukáš Fryč)
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
Fix For: 4.1.0.Milestone1
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
4:01 p.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Fix Version/s: 4.1.0.Final
(was: 4.1.0.Milestone1)
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: Pavol Pitonak
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
4:01 p.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas reassigned RF-7351:
-------------------------------
Assignee: Pavol Pitonak
Please verify against RichFaces 4 using the provided example, or the your own tests.
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: Pavol Pitonak
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
6:23 a.m.
New subject: [JBoss JIRA] Assigned: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Pavol Pitonak reassigned RF-7351:
---------------------------------
Assignee: Ján Jamrich (was: Pavol Pitonak)
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
6:17 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
Hi all,
Any update on the progress?
Kind regards.
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
8:03 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
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
9:10 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Fix Version/s: 4.Future
(was: 4.1.0.Final)
Assignee: Lukáš Fryč (was: Ján Jamrich)
Moving to 4.Future until we can get a sample to reproduce the issue.
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: Lukáš Fryč
Fix For: 4.Future
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
5:29 a.m.
New subject: [JBoss JIRA] Commented: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Stephane Daviet commented on RF-7351:
-------------------------------------
Can confirm the bug too under RichFaces 4.0.0.Final. It seems the problem comes from this
part of JS code that doesn't take {{isGlobalOnly}} into account:
{code:javascript|title=messages.js, lines 31-49}
var onMessage = function (event, element, data) {
var content = $(rf.getDomElement(this.id));
var sourceId = data.sourceId;
var message = data.message;
if (!this.options.forComponentId) {
if (!message) {
// rf.csv.clearMessage
var element;
while(element=rf.getDomElement(this.id+':'+sourceId)){
$(element).remove();
}
} else {
renderMessage.call(this,sourceId,message);
}
} else if (this.options.forComponentId === sourceId) {
content.empty();
renderMessage.call(this,sourceId,message);
}
}{code}
Actually, can't find occurence of {{globalOnly}} in any JS.
Using Spring too, it's difficult to extract a sample. But can confirm while debugging
both JS and Java that Spring doesn't seem to play any role in this bug.
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: Lukáš Fryč
Fix For: 4.Future
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
6:02 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč updated RF-7351:
---------------------------
Fix Version/s: 4.1.0.Milestone2
(was: 4.Future)
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: Lukáš Fryč
Fix For: 4.1.0.Milestone2
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
6:06 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč updated RF-7351:
---------------------------
Fix Version/s: 4.1.0.Final
(was: 4.1.0.Milestone2)
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: Lukáš Fryč
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
9:31 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Assignee: (was: Lukáš Fryč)
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
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
8:33 a.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Final)
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
Fix For: 4.1.0.CR1
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
8:22 p.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Fix Version/s: 4.1.0.Milestone3
(was: 4.1.0.CR1)
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
Fix For: 4.1.0.Milestone3
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
3 p.m.
New subject: [JBoss JIRA] Updated: (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Fix Version/s: 4.1.0.Tracking
(was: 4.1.0.Milestone3)
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
Fix For: 4.1.0.Tracking
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
1:02 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Brian Leathem updated RF-7351:
------------------------------
Labels: spring (was: )
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
Labels: spring
Fix For: 4.1.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Brian Leathem updated RF-7351:
------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Tracking)
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
Labels: spring
Fix For: 4.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:27 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Jay Balunas updated RF-7351:
----------------------------
Component/s: component-output
(was: component)
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-output, 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
Labels: spring
Fix For: 4.1.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:49 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Brian Leathem updated RF-7351:
------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Tracking)
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-output, 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
Labels: spring
Fix For: 4.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:03 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
david vieira commented on RF-7351:
----------------------------------
There is a workaround:
rendered="#{!empty facesMessages.currentGlobalMessages}"
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-output, 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
Labels: spring
Fix For: 4.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:45 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Mano Swerts commented on RF-7351:
---------------------------------
Thanks David,
Some extra info on the workaround.
The workaround as described above doesn't work in our case since facesMessages is not
available (we don't have a seam-application like the reporter of this issue
described).
However, we got the workaround to work by doing something similar.
{code}
.hidden {
display: none !important;
}
styleClass="#{workaroundForGlobalMessagesBug.showMessages() ? '' :
'hidden'}"
public boolean showMessages() {
Iterator<String> clientIds =
FacesContext.getCurrentInstance().getClientIdsWithMessages();
while (clientIds.hasNext()) {
String clientId = clientIds.next();
if (clientId == null) {
return true;
}
}
return false;
}
{code}
The thing I don't completely get is that it doesn't work using the rendered
property on rich:messages, we have to hide it with css.
Not sure why, but it seems to mess up the whole render-response part.
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-output, 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
Labels: spring
Fix For: 4.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:48 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
david vieira commented on RF-7351:
----------------------------------
Hi Mano ! I'm glad to help you :)
Try to reRender a outer element, or to put a a4j:outputPanel
ajaxRendered="true":
<a:outputPanel ajaxRendered="true" id="messagesOuter">
<rich:messages id="richMessages"
rendered="#{workaroundForGlobalMessagesBug.showMessages()"/>
</a:outputPanel>
If you reRender 'richMessages' the rendered is not reavaliated, only the
children's 'rendered' is reavaliated.
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-output, 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
Labels: spring
Fix For: 4.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:53 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč commented on RF-7351:
--------------------------------
Hi Mano, David,
it would be very appreciated if you could provide testing sample minimized to show your
case, since 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-output, 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
Labels: spring
Fix For: 4.1.0.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:35 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Brian Leathem updated RF-7351:
------------------------------
Fix Version/s: 4.2.0.Tracking
(was: 4.1.0.CR1)
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-output, 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
Labels: spring
Fix For: 4.2.0.Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:41 p.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
burak sarac commented on RF-7351:
---------------------------------
Hi All, I had small temporary workaround for this issue. Maybe it can help:
http://stackoverflow.com/a/9184935/706695
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-output, 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
Labels: spring, waiting_on_user
Fix For: 4.3-Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:30 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč commented on RF-7351:
--------------------------------
I have run into the same issue with following sample:
https://github.com/lfryc/quickstart/tree/quickstart-28/richfaces-validation
The issue occurs when using {{<rich:validator />}}.
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-output, 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
Labels: waiting_on_user
Fix For: 4.3-Tracking
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč updated RF-7351:
---------------------------
Fix Version/s: (was: 4.3-Tracking)
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-output, 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
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč edited comment on RF-7351 at 3/20/12 6:38 AM:
---------------------------------------------------------
I have run into the same issue with following sample:
https://github.com/lfryc/quickstart/tree/quickstart-28/richfaces-validation
The issue occurs when using {{<rich:validator />}},
it means it can be reproduced only when using Client-Side Validation.
was (Author: lfryc):
I have run into the same issue with following sample:
https://github.com/lfryc/quickstart/tree/quickstart-28/richfaces-validation
The issue occurs when using {{<rich:validator />}}.
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-output, 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
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:24 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč updated RF-7351:
---------------------------
Fix Version/s: 4.2.1.CR1
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-output, 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
Fix For: 4.2.1.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:24 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč reassigned RF-7351:
------------------------------
Assignee: Lukáš Fryč
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-output, 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: Lukáš Fryč
Fix For: 4.2.1.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] (RF-7351) Regression: "messages: globalOnly does not work properly"
[
https://issues.jboss.org/browse/RF-7351?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč resolved RF-7351.
----------------------------
Resolution: Done
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-output, 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: Lukáš Fryč
Fix For: 4.2.1.CR1
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4412
days inactive
5432
days old
richfaces-issues@lists.jboss.org
67 comments
19 participants
participants (19)
-
Alex Kolonitsky (JIRA) -
Alexander Dubovsky (JIRA)
-
Andrey Markhel (JIRA)
-
Brian Leathem (Updated) (JIRA)
-
burak sarac (JIRA)
-
david vieira (Commented) (JIRA)
-
Jan Jamrich (JIRA)
-
Jay Balunas (JIRA)
-
Jay Balunas (Updated) (JIRA)
-
Joseph Miller (JIRA)
-
Lukáš Fryč (Commented) (JIRA)
-
Lukáš Fryč (JIRA)
-
Mano Swerts (Commented) (JIRA)
-
Mano Swerts (JIRA)
-
Nick Belaevski (JIRA)
-
Pavol Pitonak (JIRA)
-
Prabhat Jha (JIRA)
-
Stephane Daviet (JIRA)
-
Tsikhon Kuprevich (JIRA)