1:57 p.m.
Walid KRIFI created RF-12610:
--------------------------------
Summary: a4j status never call onerror method
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
[
https://issues.jboss.org/browse/RF-12610?page=com.atlassian.jira.plugin.s...
]
Walid KRIFI updated RF-12610:
-----------------------------
Description:
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
a4j status never call onerror method
-------------------------------------
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 p.m.
[
https://issues.jboss.org/browse/RF-12610?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-12610:
-------------------------------
Description:
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
{code}
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
{code}
was:
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
a4j status never call onerror method
-------------------------------------
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
{code}
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 p.m.
[
https://issues.jboss.org/browse/RF-12610?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12610:
------------------------------------
What are you doing to trigger an error? The _onerror_ is fired when there is a n error in
the ajax communication, not an application error.
a4j status never call onerror method
-------------------------------------
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
Labels: waiting_on_user
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
{code}
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 p.m.
[
https://issues.jboss.org/browse/RF-12610?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-12610:
-------------------------------
Labels: waiting_on_user (was: )
a4j status never call onerror method
-------------------------------------
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
Labels: waiting_on_user
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
{code}
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:42 a.m.
[
https://issues.jboss.org/browse/RF-12610?page=com.atlassian.jira.plugin.s...
]
Walid KRIFI commented on RF-12610:
----------------------------------
I'm adding a FacesMessages with an error severity to the current context.
It's not an ajax error due to a communication issue but it is a functional
Exception.
a4j status never call onerror method
-------------------------------------
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
Labels: waiting_on_user
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
{code}
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 a.m.
[
https://issues.jboss.org/browse/RF-12610?page=com.atlassian.jira.plugin.s...
]
Walid KRIFI closed RF-12610.
----------------------------
Resolution: Rejected
This is not an issue but a4j:status not support functional Exception
a4j status never call onerror method
-------------------------------------
Key: RF-12610
URL: https://issues.jboss.org/browse/RF-12610
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.2.3.Final
Reporter: Walid KRIFI
Labels: waiting_on_user
When Error was added to to the current FacesContext onerror event is never fired with
a4j:status
{code}
<a4j:status
onstart="#{rich:component('waiting')}.show()"
onstop="#{rich:component('waiting')}.hide()"
onerror="alert(event.type);alert(status);" />
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4478
days inactive
4479
days old
richfaces-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Brian Leathem (JIRA) -
Walid KRIFI (JIRA)