[JBoss JIRA] Created: (RF-11415) Metamer: rich:messages: doesn't display all messages (@globalOnly problem)
by Ján Jamrich (JIRA)
Metamer: rich:messages: doesn't display all messages (@globalOnly problem)
--------------------------------------------------------------------------
Key: RF-11415
URL: https://issues.jboss.org/browse/RF-11415
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk
Affects Versions: 4.1.0.Milestone2
Environment: RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79
Metamer 4.1.0.20110910-M2 r.unknown
Mojarra 2.1.2-FCS
Apache Tomcat 7.0.19
Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0
Reporter: Ján Jamrich
Example page for rich:messages contains 2 messages (ok, really there are 3 messages components).
First with @for, second with @globalOnly (to avoid interference between functionality of each of them). Then third rich:messages component is without any attribute set.
Next, there is button on page which set couple of FacesMessages in actionListener method.
Following FacesMessages are added to FacesContext:
- 1 with SEVERITY_ERROR and without binding to any component (global)
- 1 with SEVERITY_WARN and without binding to any component (global)
- 2 with SEVERITY_ERROR, and bound to input1 and (second) to input2
- 2 with SEVERITY_WARN and bound to input1 and (second) to input2
When set attributes to following values:
- @globalOnly=false
- @for=''
and click on button which generates FacesMessages, then expect in second messages (with attribute @globalOnly, and without @for attribute) all messages displayed (all messages bound to component + global messages since @globalOnly=false tells that we are not expecting only global messages).
But in fact, there is displayed only one message - without binding to component (global). It mean we are missing all messages bound to some component, and secondly, we are missing messages with SEVERITY_WARN at all!
What is important, in third rich:messages component without any attributes (except ID) are not displayed these messages as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (RF-10473) Push: invalid 'Max re-connection reached.' error
by Nick Belaevski (JIRA)
Push: invalid 'Max re-connection reached.' error
------------------------------------------------
Key: RF-10473
URL: https://issues.jboss.org/browse/RF-10473
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.0.0.CR1
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Fix For: 4.0.0.CR1
Open push-demo in Chrome & FF. Toggle arbitrary channel in Chrome in fast temp & many times -> Firefox stops receiving messages after some time, console contains 'Max re-connection reached.' message.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] Created: (RF-11081) Dynamically created tabs: tab switch doesn't work with switchType "ajax" or null
by Ján Jamrich (JIRA)
Dynamically created tabs: tab switch doesn't work with switchType "ajax" or null
--------------------------------------------------------------------------------
Key: RF-11081
URL: https://issues.jboss.org/browse/RF-11081
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT r.22533
Metamer 4.1.0-SNAPSHOT r.22533
Mojarra 2.0.4-b09
Apache Tomcat 7.0.12
Java(TM) SE Runtime Environment 1.6.0_19-b04 @ Linux
Chrome 12.0.718.0 @ Linux i686
Reporter: Ján Jamrich
With swithType set to "ajax" or not set (null) tab switch doesn't work (tab don't get switched).
With option "server" tab switching works, but another issue influences behavior.
Its important note that this happens only for dynamically created tabs. (For statically created tabs works tab switching correctly).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (RF-12401) ViewExpiredException caused by Queues
by Michael Heinen (JIRA)
Michael Heinen created RF-12401:
-----------------------------------
Summary: ViewExpiredException caused by Queues
Key: RF-12401
URL: https://issues.jboss.org/browse/RF-12401
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.2.Final
Environment: myFaces 2.1.8
Tomahawk 6.0.35
Reporter: Michael Heinen
a4j:queue does not work if number of views in session is set to 1.
I assume that the viewState of queued requests is simply not updated correctly!
org.apache.myfaces.NUMBER_OF_VIEWS_IN_SESSION must be set to 1.
{code:xml}
<a4j:queue name="myQueue" ignoreDupResponses="true" requestDelay="100"/>
<h:inputText value="#{myController.expression}">
<a4j:ajax execute="@form"
listener="#{myController.dummyListener}"
event="keyup"
render="expLength">
<a4j:attachQueue name="myQueue"/>
</a4j:ajax>
</h:inputText>
{code}
--
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 years, 2 months