Mario Ivankovits wrote:
Unhappily this doesnt work as it seems the model update is AFTER the
fireing of the valueChangeListeners.
Thus my change will be overwritten by the model update.
Is there a way around it?
Well, I found this is the case.
Workaround is to update the value through the component binding.
But I think this is VERY bad.
Could it be somehow possible to have a valueChange method and also
associate a phase to it?
Something like
<f:valueChangeListener type="#{myBean.myMethod}"
phase="UPDATE_MODEL_VALUES" />
maybe by implementing a tomahawk extension?
---
Mario
