That can happen when the UICommand component is not rendered in the component tree during apply request values phase and/or update model values phase. I.e. The rendered attribute of it or one of its parents has evaluated false at that point.
Sometimes I'm setProfilePage is totally absent. That can happen when the UICommand component is not rendered in the component tree during apply request values phase and/or update model values phase. I.e.
The rendered attribute of it or one of its parents has evaluated false at that point. The presence of @PostConstruct should not have any influence.
As BalusC indicates, having a rendered attribute set to false at a postback is quite often a cause for action methods not being executed. This typically happens when such attribute defaults to false and is only later in the JSF life-cycle (i.e. After apply request values) set to true.
Defaulting to true (if possible) or remembering the value of this attribute by using the view scope or something like the Tomahawk saveState tag often gets you around this problem. In addition I would like to mention that next to PostConstruct, AJAX also should have nothing to do with this problem.
In fact I don't have a rendered attribute set to false. You can see the example of my issue here stackoverflow. Com/questions/4292330/… – markzzz Nov 27 '10 at 20:56.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.