[richfaces-issues] [JBoss JIRA] Commented: (RF-10794) a4j:status doesn't work with current myfaces implementation

Nick Belaevski (JIRA) jira-events at lists.jboss.org
Wed Mar 23 15:19:45 EDT 2011


    [ https://issues.jboss.org/browse/RF-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591376#comment-12591376 ] 

Nick Belaevski commented on RF-10794:
-------------------------------------

That's bug in MyFaces snapshot.

> a4j:status doesn't work with current myfaces implementation
> -----------------------------------------------------------
>
>                 Key: RF-10794
>                 URL: https://issues.jboss.org/browse/RF-10794
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.0.0.CR1
>            Reporter: Rene O
>            Priority: Minor
>         Attachments: jsf2testcase.war
>
>
> a4j:status doesn't work with current myfaces implementation (myfaces-impl-2.0.5-20110320.005844). Please note: it works with myfaces 2.0.4
> To reproduce this issue see attached testcase-war. Start with http//:localhost:8080/jsf2testcase/status.jsf
> Status-Image should appear after keyup-event in inputfield, but it doesn't with current myfaces implementation

--
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