[richfaces-issues] [JBoss JIRA] Updated: (RF-9722) a4j:status - error handling - lifecycle broken (MyFaces)
Nick Belaevski (JIRA)
jira-events at lists.jboss.org
Wed Dec 8 11:04:31 EST 2010
[ https://jira.jboss.org/browse/RF-9722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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
More information about the richfaces-issues
mailing list