These things where done in the encodeBegin method in the past. And that always caused troubles. Hmm, I do not know the exact answer by now. Has something to do with "isRendered" and "isRenderedIfEmpty" and caching backing beans and so on - sorry, it was long ago ;-) . What I know for sure: It cost me hours and hours to find this solution. So please be careful. Even if I cannot give you the exact explanation I have the very very strong feeling that we should not remove this listener. Another case study that shows us the importance of documentation *sh..* :-(
What is the exact problem with the alias bean? You said it was not there during the processing of the phase listener. Do you get an exception because of that? -Manfred 2005/5/30, Broekelmann, Mathias <[EMAIL PROTECTED]>: > Hi Manfred, > > > There is no way to make this sure other than by means of this phase > > listener, because the render phase can be initiated by different > > incidents (see Lifecycle). > > Is it not possible to use the HtmlDataTable.encodeBegin(FacesContext) in the > HtmlDataTable implementation? As far as I know this method is called before > rendering the component and it�s childs. > > regards, > Mathias >
