You're outjecting the user object into a conversation scope. If your DataModel is in the session scope, it won't be updated, I guess...
Thanks mjek2 for your answer.
My DataModel is in the conversion scope, too. But I don't think that this is real problem, because my 2nd example works.
Ah, ok, got your point know. Well, you say that you see the changed object in the next page after outjection, so it seems like correct behaviour to me. I think the DataModel holds the old reference. Maybe you could force DataModel update instead of working with temporary object as alternative.
Ok. I will try to reload the DataModel.
But this means also that the references of the object in the DataModel and in the conversation scope are not the same.