10:24 a.m.
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://jira.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 a.m.
New subject: [JBoss JIRA] Updated: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://jira.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.syst...
]
Nick Belaevski updated RF-9722:
-------------------------------
Assignee: Nick Belaevski
Fix Version/s: 4.0.0.Milestone5
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://jira.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Nick Belaevski
Fix For: 4.0.0.Milestone5
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:30 p.m.
New subject: [JBoss JIRA] Commented: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://jira.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.syst...
]
Nick Belaevski commented on RF-9722:
------------------------------------
http://java.net/jira/browse/JAVASERVERFACES-1887
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://jira.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Nick Belaevski
Fix For: 4.0.0.Milestone5
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] Updated: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://jira.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.syst...
]
Nick Belaevski updated RF-9722:
-------------------------------
Fix Version/s: 4.0.0.CR1
(was: 4.0.0.Milestone5)
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://jira.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Nick Belaevski
Fix For: 4.0.0.CR1
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 p.m.
New subject: [JBoss JIRA] Updated: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://issues.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski updated RF-9722:
-------------------------------
Component/s: compatibility
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://issues.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Nick Belaevski
Fix For: 4.0.0.CR1
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:38 a.m.
New subject: [JBoss JIRA] Assigned: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://issues.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski reassigned RF-9722:
----------------------------------
Assignee: Pavel Yaschenko (was: Nick Belaevski)
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://issues.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Pavel Yaschenko
Fix For: 4.0.0.CR1
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:07 a.m.
New subject: [JBoss JIRA] Commented: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://issues.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.sy...
]
Nick Belaevski commented on RF-9722:
------------------------------------
Need to add 'onsuccess' event?
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://issues.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Pavel Yaschenko
Fix For: 4.0.0.CR1
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
New subject: [JBoss JIRA] Resolved: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://issues.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.sy...
]
Pavel Yaschenko resolved RF-9722.
---------------------------------
Resolution: Done
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://issues.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukas Fryc
Assignee: Pavel Yaschenko
Fix For: 4.0.0.CR1
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:21 a.m.
New subject: [JBoss JIRA] Updated: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
[
https://issues.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč updated RF-9722:
---------------------------
Labels: (was: needs-qe)
a4j:status - error handling - lifecycle broken (MyFaces)
--------------------------------------------------------
Key: RF-9722
URL: https://issues.jboss.org/browse/RF-9722
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility
Affects Versions: 4.0.0.Milestone4
Environment: RichFaces 4.0.0.20101107-M4 r.19981
Metamer 4.0.0.20101107-M4 r.19986
Mojarra 2.0.2-FCS
Apache Tomcat 6.0.28
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 7.0.517.44@ Win32, Firefox 3.6.12 @ Linux
Reporter: Lukáš Fryč
Assignee: Pavel Yaschenko
Fix For: 4.0.0.Milestone6
When binding event handlers to status, you can see following lifecycle using Mojarra:
1. start
2. success
3. stop
But using MyFaces, you will see:
1. start
2. error
3. stop
4. success
5. stop
but only one request was actually done.
Also the status are showing STOP facet instead of ERROR.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4989
days inactive
5164
days old
richfaces-issues@lists.jboss.org
8 comments
4 participants
participants (4)
-
Lukas Fryc (JIRA) -
Lukáš Fryč (JIRA)
-
Nick Belaevski (JIRA)
-
Pavel Yaschenko (JIRA)