[ 
https://issues.apache.org/jira/browse/MYFACES-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574694#action_12574694
 ] 

imario edited comment on MYFACES-1831 at 3/3/08 11:31 AM:
--------------------------------------------------------------------

Hmmm ... for what I have seen in my special case the 
UIComponentClassicTagBase.getCreated returned false and that's why the 
UpdateActionListenerTag did not configure the parent accordingly. If getCreated 
would have returned true, it would have worked.

Anyway, if there is a bug in the Tag base-class it is worth fixing it, but 
please do not spend a single hour in fixing the updateActionListener as there 
is a working JSF standard replacement. Ok, I can't influence what you do in 
your spare free time ;-)

      was (Author: imario):
    Hmmm ... for what I have seen in my special case the 
UIComponentClassicTagBase.getCreated returned false and that's why the 
UpdateActionListenerTag did not configure the parent accordingly. If it would 
have returned getCreated it would have worked.

Anyway, if there is a bug in the Tag base-class it is worth fixing it, but 
please do not spend a single hour in fixing the updateActionListener as there 
is a working JSF standard replacement. Ok, I can't influence what you do in 
your spare free time ;-)
  
> JSF12 UIComponentClassicTagBase.getCreated is broken, breaking 
> t:updateActionListener
> -------------------------------------------------------------------------------------
>
>                 Key: MYFACES-1831
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1831
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Simon Kitching
>
> In testing I have found that t:updateActionListener works fine with MyFaces 
> 1.1.x but is ignored with MyFaces 1.2.3-SNAPSHOT
> After debugging, I found that UIComponentClassicTagBase.getCreated is always 
> returning true. This means that UpdateActionListenerTag always thinks its 
> parent component is already configured, so does not attach an 
> UpdateActionListener instance to it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to