Don't know if this is of any help to you, but Facelets also corrects
the component tree rendering problem if you can use Facelets.
On 3/29/06, Cagatay Civici <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Thanks to Ed Burns, I've learned that this is a JSF issue, at first jsf
> creates the component tree "during rendering components", in JSF 1.2 they've
> fixed this by first creating the tree and then rendering it.
>
> Cagatay Civici,
>
>
> On 3/16/06, Cagatay Civici <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I wonder why this happens,
> >
> > public void encodeBegin(FacesContext context) throws IOException {
> > log.debug("ChildCount:" + getChildCount());
> > }
> >
> > public void encodeEnd(FacesContext context) throws IOException {
> > log.debug("ChildCount:" + getChildCount());
> > }
> >
> > For example in the jsp page, component's number of children is 3. At
> encodeBegin log gives me 0 but at encodeEnd it gives 3.
> >
> > Also when I override getRendersChildren to return true, encodeBegin log
> gives 3 this time.
> >
> > I'll be glad if you help me out,
> >
> > Regards,
> >
> >
> > Cagatay,
> >
>
>
