Matthias Kahlau wrote:
Actually, I didn't ask for practical solutions, because I have a solution for the problem already. I hope that someony can tell me, why the ValueChange event is fired before that Update Model Value Phase. Is there a practical reason, or is it caused by accident?
I asked, and still have the same question.
And I would like to ask if it is possible to create a tag simmilar to valueChangeListener but with an "phase" attribute.
<f:valueChangeListener type="#{myBean.myMethod}" phase="UPDATE_MODEL_VALUES" />
other than the default valueChangeListener "type" should not point to a class, but might point to a method.
I think this could be possible. --- Mario
