[
https://issues.apache.org/jira/browse/TOBAGO-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485887
]
Volker Weber commented on TOBAGO-337:
-------------------------------------
I just looked at field1 and field4:
you have at field4 disabled="#{bbg.f1double lt 100.0}", this is true if the
'modelvalue' of field1 is < 100.
if now the value of field1 is changed, on the client, to less than 100 on the
client, the form is submitted.
The lifcycle runs normaly until update modelPhase. at this point all submited
values are stored in the components as submitedValues. At next the model value
of f1 is updated, now is field4 disabled and not updated,
this means also the submitedvalue is not cleared. So on the next rendering the
previous submited value is rerendered.
Until the disabled attribute of field4 evaluates to true, or a new view is
created, always the previous submited value is rerendered for field4.
This is no bug, this is jsf lifecycle behavior.
If you move the field1 tag behind the others you app will work as expected.
> field value can't be setted or cleared if state changes from enabled to
> disabeld
> --------------------------------------------------------------------------------
>
> Key: TOBAGO-337
> URL: https://issues.apache.org/jira/browse/TOBAGO-337
> Project: MyFaces Tobago
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.10
> Environment: winxp prof, tomcat 5.5.20, myfaces 1.1.6 snap
> (23.03.2007), tobago 1.0.11 snap (17.03.2007)
> Reporter: Guido Dubois
> Fix For: 1.0.11
>
> Attachments: disabled.war
>
>
> if field state changes from enabled to disabled it is not possible to set or
> clear the fields content
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
