myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Robinson (JIRA)" <...@myfaces.apache.org>
Subject [jira] Resolved: (TRINIDAD-1469) returnListener behaves differently when immediate=true in commandButton
Date Thu, 07 May 2009 19:18:46 GMT

     [ https://issues.apache.org/jira/browse/TRINIDAD-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Robinson resolved TRINIDAD-1469.
---------------------------------------

    Resolution: Invalid

This is not a bug. If you use immediate=true, then submitted values will be rendered, not
the values. If you must use immediate, you need to clear the input components if you programmatically
change their values

> returnListener behaves differently when immediate=true in commandButton
> -----------------------------------------------------------------------
>
>                 Key: TRINIDAD-1469
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1469
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.10-core
>         Environment: Ubuntu 9.0.4, Tomcat 5.5.27
>            Reporter: Walter MourĂ£o
>         Attachments: testetrinidadfacelets.zip
>
>
> The following code works as expected when the commandButton has immediate="false" but
fails (the "input1" does not show the new value) when immediate="true". Using partialSubmit="true"
in both cases.
>     public void returnListener(ReturnEvent event){
>         CoreInputText i=(CoreInputText)FacesContext.getCurrentInstance().getViewRoot().findComponent("input1");
>         i.setValue("passou no returnListener");
>         RequestContext.getCurrentInstance().addPartialTarget(i);
>     }

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


Mime
View raw message